This module allows you to limit the taxonomy terms listed in a term reference form element or in a views exposed filter.

Description

Based on a status field disabled terms will be removed from the options by a hook_field_widget_form_alter() implementation for term reference field widgets and by a hook_form_FORM_ID_alter() for views exposed forms.
The module allows you to enable/disable this limitation with permissions for each vocabulary.

Dependencies

It depends on the Taxonomy Publisher module (now part of the Taxonomy tools project), which
attaches a status field to the taxonomy terms of the vocabularies you select.

A link to project page:
http://drupal.org/sandbox/balintcsaba/1857296

Setting up this repository locally for the first time

git clone --recursive --branch 7.x-1.x http://git.drupal.org/sandbox/balintcsaba/1857296.git taxonomy_publisher_filter
cd taxonomy_publisher_filter

Reviews of other projects:

Comments

reszli’s picture

Status: Needs review » Needs work

Hi,
you need to move the project into a version branch.
See the docs here: http://drupal.org/empty-git-master
I will also do a code review once you're done

you can also remove the project page link form your project page

dydave’s picture

Hi balintcsaba,

Just a quick heads up on code review.
It seems your code has a few issues reported from the Automatic Review system:

Automated Review: http://ventral.org/pareview/httpgitdrupalorgsandboxbalintcsaba1857296git

Review of the master branch:

Drupal Code Sniffer has found some issues with your code (please check the Drupal coding standards). See attachment.
This automated report was generated with PAReview.sh, your friendly project application review script. You can also use the online version to check your project.

FILE: .../modules/pareview_temp/test_candidate/taxonomy_publisher_filter.api.inc
--------------------------------------------------------------------------------
FOUND 1 ERROR(S) AFFECTING 1 LINE(S)
--------------------------------------------------------------------------------
64 | ERROR | Last parameter comment requires a blank newline after it
--------------------------------------------------------------------------------

Source: http://ventral.org/pareview - PAReview.sh online service


I recommend you also try to run this validation again, after you have made the changes suggested by reszli in #1, related with the GIT Branch.
Run the validation again and try to fix the errors, then, change the status back to needs review, that will save you one not so useful review from another user who would have simply told you about the coding errors mistakes (more back and forth = more time). This is something very common that happens to all of us (and just for one whitespace at the end of the line... the status is changed back to needs work again, which seems to be the case with your code right now).


So far, that's all I could find, but I will try doing a manual review and certainly let you know if I can find anything else.
I hope these comments will help you to improve this nice module.

Cheers!

balintcsaba’s picture

Hi guys,

Thanks for the fast review , i made the modifications and error fix.

Respect,
B.Csaba

reszli’s picture

Status: Needs work » Needs review

removed

reszli’s picture

Issue summary: View changes

adding link for review bonus

reszli’s picture

Hi balintcsaba,

there are a couple more things I found:
1. you should change the 'Setting up this repository locally for the first time' section above to reflect the branch change (from master to 7.x.1.x)
2. Your README.txt contains no useful information about your project, you should add some.

balintcsaba’s picture

Hi reszli,

README.txt updated and the repository changed also added a new functionality to filter custom forms.
Thanks for your help.

balintcsaba’s picture

Issue summary: View changes

Changing git access

balintcsaba’s picture

Issue summary: View changes

Review bonus

balintcsaba’s picture

Issue summary: View changes

Review Bonus update

balintcsaba’s picture

Issue summary: View changes

Review bonus update

balintcsaba’s picture

Issue summary: View changes

Git acces update

balintcsaba’s picture

Issue summary: View changes

Review bonus update

reszli’s picture

Status: Needs review » Needs work

Hi balintcsaba,

while I reviewed the module on a clean new D7 install I found the following issue:
(which is why I',m marking it as needs work)

.info file
since taxonomy_tools_publisher is not a standalone module but part of the taxonomy_tools wrapper module
I think you should add both as the dependencies, otherwise neither Drush nor user will find the dependent projects on d.org

dependencies[] = taxonomy_tools
dependencies[] = taxonomy_tools_publisher

and a couple of personal suggestions:
(for the future - not necessarily for this review process)

you could extend a bit the "How to use" section of the project page
since it could pretty hard to follow those steps for a novice user
and you could also include that information in a hook_help()
implementation and the README.txt for a better UX

you could also add a small configuration UI for this module:
where the user can change currently hard-coded values such as the cache time period

creating a permission for who can configure the above mentioned options
would also solve the 'no permission' behavior when there is no vocabulary enabled to use the taxonomy_tools_publisher module on top of which you are building your permissions dynamically

balintcsaba’s picture

Status: Needs work » Needs review

Hi reszli,

I changed the .info file.
Thank you for your tips , the configuration UI it was my plan to , but it will be implemented in a future version with
auto complete widget support.
The permission fix and the hook_help() with the multiple role support is my next task but first i want to have the project lunched.
If you think that all is OK so far please sett RTBC for module.
Again a lot of thanks for your time.

With respect,
B.Csaba

klausi’s picture

Don't forget to add the PAReview: review bonus" tag as indicated in #1410826: [META] Review bonus, otherwise you won't show up on my high priority list.

klausi’s picture

Issue summary: View changes

Review Bonus List update

balintcsaba’s picture

Issue summary: View changes

Reviews of other projects

balintcsaba’s picture

Hi klausi,

I'm not sure what i did wrong, my review list was already there(here at the bottom of Issue Summary).

balintcsaba’s picture

Title: Taxonomy Publisher Filter » Issue tags
balintcsaba’s picture

Title: Issue tags » Issue tags: PAReview: review bonus
balintcsaba’s picture

Title: Issue tags: PAReview: review bonus » Issue tags:
Issue tags: +PAreview: review bonus

PAReview: review bonus

balintcsaba’s picture

Title: Issue tags: » Taxonomy Publisher Filter
klausi’s picture

Status: Needs review » Postponed (maintainer needs more info)

This sounds like a feature that should live in the existing taxonomy_tools project. Module duplication and fragmentation is a huge problem on drupal.org and we prefer collaboration over competition. Please open an issue in the taxonomy_tools issue queue to discuss what you need. You should also get in contact with the maintainer(s) to offer your help to move the project forward. If you cannot reach the maintainer(s) please follow the abandoned project process.

If that fails for whatever reason please get back to us and set this back to "needs review".

klausi’s picture

did not mean to remove the review bonus flag.

sreynen’s picture

Status: Postponed (maintainer needs more info) » Closed (won't fix)

balintcsaba is now maintainer of the Taxonomy Tools project, so I think this issue can be closed.

balintcsaba’s picture

Priority: Normal » Critical
Status: Closed (won't fix) » Needs review

Hi ,

I tried to add a new module to Drupla.org and i realized that can't add full projects.
I made the steps with this module , witch in the end was included to the Taxonomy Tools project.
In the next 2-3 months i will add 2 new module.
But now I'm a little confused why i can't create full projects ?

With Respect,
balintcsaba

klausi’s picture

Status: Needs review » Closed (fixed)

Just post the module as new project application again, mention your other contributions and your review bonuses. Usually we only grant the git vetted user role when a new project actually has to be created.

klausi’s picture

Issue summary: View changes

Edit description