It would be best to add a couple of lines to the module description (and to the readme file) to explain that edit permissions from the Taxonomy module on the desired vocabularies still need to be checked to be able to access the admin/structure/taxonomy page.

See my comment #3 at #1533668: Doesnt work.

Comments

antiorario’s picture

antiorario commented
Title: Needs explanation on » Needs documentation on correct permissions

(It seems I forgot part of the title.)

rudiedirkx’s picture

rudiedirkx commented

I completely missed this one. Better explanation is always a good idea. However, changing the readme would require a new release for it to be downloaded/seen and a new release just to add a few lines of explanation seems silly.

What I can do, is be more clear on the project page. That's something everybody sees. (Who's gonna read the readme?)

Suggestions for better text?

(Good etiquette note in your comment btw!)

Leeteq’s picture

Leeteq commented
Title: Needs documentation on correct permissions » Specify permissions (configuration steps) to get started with the module

Here is my suggestion:

"In order to access the admin/structure/taxonomy page, you must first set permissions for the desired vocabularies."

It would be practical to add such a sentence to the project page anyway, but should absolutely find its way into the next readme.txt version (eventually). IMO, as long as such a sentence is present on the project page, it is no need to push a new release, just put it in the readme.txt of the -dev version awaiting a suitable release point depending on the other improvements.

rudiedirkx’s picture

rudiedirkx commented
Status: Active » Fixed

I've updated the project page: http://drupal.org/project/taxonomy_access_fix

Agreed? If not, reopen this issue.

antiorario’s picture

antiorario commented

Sounds good to me. But make sure it goes into the readme file as well.

Leeteq’s picture

Leeteq commented
Status: Fixed » Reviewed & tested by the community

Great, thanks.
Since this issue is a "documentation task", lets keep it open until it has been committed to the readme.txt file.
And where is the 1.x-dev release, anyway? (this issue should be filed against 1.x-dev)

rudiedirkx’s picture

rudiedirkx commented

I don't do dev releases. Dev shouldn't be a release. Dev is dev.

I'm looking for co-maintainers.

antiorario’s picture

antiorario commented

Then this may prompt a 1.1 release, if you changed the readme file. Just a suggestion.

rudiedirkx’s picture

rudiedirkx commented
Status: Reviewed & tested by the community » Fixed

Release 1.1 http://drupal.org/node/1791504

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.