Regardless of how role permissions are set for users (in terms of avalible catagories), all catagories are shown and avalible to select when a user is creating content (blog, story, page, etc.). I have disabled specific catagories for specific user roles, however this doesn't seem to make a difference when they are creating content. Although, when they do create the content they cannot view it afterwards because their role doesn't allow it. How can I prevent the user from even being able to view the optional catagories (that their role doesn't allow) during the content creation process?

Thanks

Comments

pyromanfo’s picture

Did you read the install instructions? Did you apply the taxonomy.module patch?

korey.ca’s picture

Yes, I installed it correctly - to the best of my knowledge. I also just applied the patch. The module seems to work fine otherwise. I can give role access to users and they cannot view content, etc. It's just when they try to create content, all the catagories are available (when some should not be).

Does the patch also require that I update my mySQL database with the new file as well?

pyromanfo’s picture

You have to install taxonomy_access.mysql as well, yes.

Are you talking about the taxonomy forms when making nodes under "create content"?

korey.ca’s picture

Hey again...

Ok, I re-installed the whole taxonomy_access module and mysql file into the database. I still get the same problem.

Example: I created two users 'public' and 'private'. I created two vocabularies 'public directory' with 'public term' under it; and 'private directory' with 'private term' under that. Then I created two roles 'public' and 'private'. I assigned the corresponding vocabularies and permissions to create some content (pages, blogs, etc.) to each of the roles. I then activated the assigned roles to the users. So, all is good - access, permissions, etc. are all in correct order.

Now, when I log in as the 'private' user I can create content (in the 'created content' area, yes) and assign the nodes I create to either 'public' or 'private' catagories (which I assigned in the permissions). That is all good. However, when I log in as the 'public' user and attempt to create content I get both 'public' and 'private' catagories to assign the node to. Then when the content is created (by the 'public' user) I cannot view content (any node) that was assigned under the 'private' catagory. This is how it should be, but the 'public' user should not even be ABLE to select the 'private' catagory in the first place.

I hope that wasn't too overly confusing. I tried re-create the problem and use the simplest user names, etc.

Any help with this issue would be most appreciated - I'm quite sure this isn't how the module was intended to work and I would like to resolve this.

Thanks.

pyromanfo’s picture

Yeah you're right it's not supposed to work that way.

Could you try the latest CVS module? The taxonomy_access.module and taxonomy.patch under the 4.5.2 subdirectory work with 4.5.2. Just get the CVS tarball from the download page.

I'll take another look when I get home, but last time I checked the form didn't have categories without the "create" permission listed.

One thing to make sure, you are seeing the private term in the box and not the private vocabulary, right?

korey.ca’s picture

Ok, I'll uninstall the module and install the CVS one. What exactly is the difference between the two anyway? Also, the taxonomy.patch simply goes in the modules directory, correct? That's all you need to do with it?

Yes, I'm seeing the terms I created, not the vocabularies, in the select box when creating content.

pyromanfo’s picture

Aha! That's the problem. You need to apply the patch.

On UNIX, type patch -p0 < taxonomy.patch while in the modules directory. On Windows, theres some program someone linked to in another issue that you can use.

korey.ca’s picture

Any idea where I'd find that windows program? I searched for 'applying patch with windows', etc.. but I can't seem to find anything.

pyromanfo’s picture

korey.ca’s picture

Great! Thanks!

Just for some clarification though... would I be using a windows GUI program (such as the ones you linked me to) to patch Drupal modules on MY local machine and then upload the modules to my server? Or does all the patching take place over the net directly to the module files on my server? I suppose I could be looking into it, but I'm at work and I'm just trying to get a grasp on all these details before I get home to work on it.

pyromanfo’s picture

You're just modifying a file. Whichever way you want to do it, whatever, but you're just modifying a file and making sure that modified file is on your webserver.

korey.ca’s picture

Alrighty, that's what I figured.

Thanks a lot for your help, much appreciated.

MrMattles’s picture

Version: » 4.6.x-1.x-dev

Currently on 4.6.0 yes the patch is applied....even double check the .bash_history........but same problem.....

nurlan.bayaman@bayaman.com’s picture

i have same problem.
installed:

latest drupal 4.6
TAC
i18n

applied patch provided here http://drupal.org/node/22834
and still a don't have access restrictions on my site.
even anonymous Users have 'view' access to all of the content, even though they don't suppose to have such an access.
BTW it worked till some magic point, and then it stopped to restrict access. what did i screw?

ps
may some other modules can harm TAC functionality?
a have many of them installed, but none of them concern to access permissions, exept core abilities of course.

nurlan.bayaman@bayaman.com’s picture

Title: All catagories shown regardless of permissions set » it restricts only terms' access, but not nodes'.

i've just noticed, that module works only with terms. but with nodes in that terms i doesn't.

igrcic’s picture

allthough im using module v4.6.0 users can still view all terms when posting content, but except that everything is ok; they cant see posted content, or content with that categories. isnt that patched in 4.6.0. ?
i guess only for mysql?!

maybe some tips so i could fix it for postgresql??

igrcic’s picture

It works fine when I applied a patch :)

But isnt it allready applied in 4.6.0?

pyromanfo’s picture

Nope, it isn't. That's why there's still a patch :)

keve’s picture

Status: Active » Closed (fixed)

You have to apply patch for version 4.5 and 4.6.