Hi!
This module is really great to be able to find nodes having a combination of certain vocabulary terms. But the site I am building has some public content, and some restricted content (knowledge base). I want the internal users to be able to use the module, while restricting the public from accessing it.
Because I use taxonomy access control, even if the public searches using this, they cannot find any nodes they should not see - but they are able to see the taxonomy that I am using, which I would like to avoid.
The way I have set up the (sub)menu, it's not possible for an user to arrive at the node for this module by browsing - it would actually have to be a hacker who tries /taxonomy_browser.
But for all that, I'd prefer if it was possible to restrict access to this from user permissions.
Thanks!
/Sifaan
Comments
Comment #1
nancydruI have to think about this one for a moment. If I just put in a permission, then everyone else who use the module will have it broken until they realize that there is now a permission.
Have you looked at the Menu-per-role or Taxonomy Role modules?
Comment #2
nancydruI am committing this to the -dev versions that will roll up at midnight GMT. Please try it out.
There is now a setting to turn on permission to access the page. Please read the description under the checkbox.
Comment #3
sifaan commentedRe: Menu-per-role, I have restricted the access to the menu page using Taxonomy Access Control (HEAD version) - so, anonymous people will not see the menu item... problem only really would occur with a hacker who enters the URL.
Re: Taxonomy Role, this would perhaps be convenient to avoid display of the Vocabulary that controls the access levels (Public, Client, Internal, etc) but I am not sure if this would actually prevent Taxonomy Browser from being able to display the list.
In any case, neither of the above seem available for 6.x.
Will try the -dev version and let you know how it goes.
Comment #4
sifaan commentedI tried the -dev version and enabled the permission setting. Works like I expected it (unauthorized user cannot access the page even by typing in the URL...)
Thanks!
/Sifaan
Comment #5
nancydruGreat. Thanks for the feedback.
Comment #6
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.