Suggestion: To have LIST access affect what appears in the tracker list. Consider if we set the following access options on a term using taxonomy access:

VIEW = Allow, LIST = Off

If we have a category named Audience with terms set to Public, Members and System. Nodes tagged as System would not need to be listed, but would still be viewable using the above access settings.

Why would we do this?

The above could eliminate static "page" nodes and 403/404 error nodes from displaying in the tracker list, which would make for a much cleaner site. The nodes would still be visible everywhere else, but removed from the Recent Posts a.k.a. tracker list.

Just a suggestion... thanks in advance for your consideration.

Comments

drubeedoo’s picture

drubeedoo commented

Hmmm... the issue seems to go deeper into other listings, such as taxonomy/vocabulary/1. Modules such as taxonomy_context open up a can of worms (by serving links) that taxonomy_access can't seem to close (by disallowing LIST for those links).

Any thoughts?

keve’s picture

keve commented
Priority: Normal » Minor
Status: Active » Closed (won't fix)

do you mean under tracker list: /tracker (recent posts)?

Sorry, this cannot be done. Because tracker page is rendered by drupal core (tracker.module).
I cannot change it with TAC module. I lists all nodes where $user have 'view' access.

You should write your own module for this, similar to tracker.module (it is a quite simple module), which can be configured that it does not show certain nodes (e.g nodes w/ given terms, or certain node-types).

Regarding your taxonomy_context idea, it is a different issue, you should file a bug report about it.

keve’s picture

keve commented

I submitted bug report for taxonomy_context:
http://drupal.org/node/61493

drubeedoo’s picture

drubeedoo commented

Thanks for your help, keve.