Home ›
Using Taxonomy Access ControlUsing Taxonomy Access Control
Submitted by Benjamin Melançon on April 27, 2007 - 3:12pm
You can enable taxonomy access control and nothing will go haywire. However be sure to set every existing category and the defaults to what you want -- generally, allowing all roles to view (or anonymous and authenticated, and non-authenticated if applicable, as other roles will inherit from these)
Otherwise, once you save the settings for that role, watch out. Goodbye site content! All posts (nodes) in those categories can disappear.
The solution of course is just to define everything correctly for anonymous and authenticated users especially and save again for each of those.
(Agaric likes the power of the taxonomy_access module!)
You can enable taxonomy access control and nothing will go haywire. However be sure to set every existing category and the defaults to what you want -- generally, allowing all roles to view (or anonymous and authenticated, and non-authenticated if applicable, as other roles will inherit from these)
Otherwise, once you save the settings for that role, watch out. Goodbye site content! All posts (nodes) in those categories can disappear.
The solution of course is just to define everything correctly for anonymous and authenticated users especially and save again for each of those.
(Agaric likes the power of the taxonomy_access module!)
Comments
Question: taxonomy_access supersede 'edit node' permissions?
Agaric wants to know...
Does Taxonomy Access Control supersede 'edit content type' and 'edit own node' privileges?
Post new comment