I have a taxonomy hooking together different content types, everything is working as expected. However, I never want non-Admins to see the taxonomy pages, just names or other related fields in views on other pages. How can hide all of this taxonomies pages from non-authenticated users?

Specific example:

  • Sales Contact (Node Type) - Sales contact name, address, phone, etc.
  • Products (Node Type) - All sorts of assorted Product Details
  • Sales Classifications (Taxonomy) - Types of contracts we have with Sales Contacts, and what products they cover.

Product pages and Sales Contact pages are public, but a Sales Classification page makes no sense to show end users. That said, on Product detail pages I'd like to show some of the Sales Classification fields to end users.

Taxonomy Access Control looked promising, but you can ether lock down the whole term (including related nodes) OR set it to do node permissions separately.

Any recommendations would be appreciated.



I ended up using Rabbit Hole, it seams to do everything I was looking for. More details from the module's project page:

Rabbit Hole is a module that adds the ability to control what should happen when an entity is being viewed at its own page.

Perhaps you have a content type that never should be displayed on its own page, like an image content type that's displayed in a carousel. Rabbit Hole can prevent this node from being accessible on its own page, through node/xxx.

|improve this answer|||||

Enable the drupal taxonomy views and set as one of the filters the admin role.

|improve this answer|||||
  • Do you mean Taxonomy Views Integrator? I've never used it before, but will try it out. – summerg Oct 31 '14 at 16:56

You can use Panels to override the taxonomy path, then make one variant for authenticated users and another variant for anonymous users. (control access using selection rules)

Panels adds some setup overhead but will give you complete control over the information shown on the page.

|improve this answer|||||
  • Panels seems a little over kill... – summerg Oct 31 '14 at 16:58
  • @user327046 Sure, it might be overkill for this particular use case-- if your requirements don't change. But if the requirements change later and you have to make it work in a different way, Panels will most likely have the options you need. If you use another module, you may have to switch modules, which will be a lot more work in the long run. – Patrick Kenny Nov 1 '14 at 2:47

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.