I can access a node-list organized by a "vocabularly," but not a "term."

When I use my vocabulary id, I get the correct nodelist. However, when I use a term id, I get: "Access denied. You are not authorized to access this page."

I have checked my access permissions with the node-access and taxonomy-access (I have this module installed) and everything is wide-open for my user role.

I'm not sure why I am having trouble with this. I've turned off path-auto, taxonomy-context, and url aliasing to see if there was a conflict, but I still can't access my node-list with a term.

CommentFileSizeAuthor
#4 nodelist-nestedterms.patch561 byteswmostrey

Comments

bomarmonk’s picture

bomarmonk commented

Clarification: listing by term does seem to work, however, using a parent term does not list nodes associated with child terms of that parent. Should this be the default behavior?

njivy’s picture

njivy commented

There is not yet a way to include nodes from nested terms. taxonomy.module can do things like that, although the output is a simple list of node teasers. I do not yet know how to easily imitate taxonomy.module's behavior. Let me think about it.

hansfn’s picture

hansfn commented

Have you made any progress on "including nodes from nested terms."? That would make this very nice module great! I would prefer not switching to taxonomy.module...

wmostrey’s picture

wmostrey commented
Version: 4.6.x-1.x-dev » 4.7.x-1.x-dev
Assigned: Unassigned » wmostrey
Status: Postponed » Active
StatusFileSize
new nodelist-nestedterms.patch561 bytes

This is the patch for the 4.7 version. I will add this to the official version once I get an option ready to check this in the administer settings.

wmostrey’s picture

wmostrey commented
Category: bug » feature
Status: Active » Fixed

This feature has now been contributed to 4.7, with a checkbox option in the settings.
Thanks for bringing up the idea.

Anonymous’s picture

(not verified) commented
Status: Fixed » Closed (fixed)