Under certain conditions, if a book node has terms from more than one vocabulary assigned to it, and a user has access to it from the role settings of both those terms, then duplicate entries occur.

If a node has no vocabulary terms, then despite what the read_me says, these book pages do not appear at all, even to user #1, and cannot be viewed or administrated.

Comments

axel’s picture

Assigned: Unassigned » axel

Probably problem here: http://drupal.org/node/view/8418
But also I look now on my book.patch and find in it traces of my experiments with 'groups' module :( (some patches for 'term_access' was reworked from patches for 'groups', :) because of similar ideology of these modules). I will upload clean book.patch to CVS soon.

dmjossel’s picture

Actually, the problem seems to be in particular that the DISTINCT option seems to be missing from all the modified SELECT statements in book.module. Adding it seems to remove the problem of duplicates.

auctmore’s picture

After an out-of-the-box installation of the taxonomy access module certain nodes are displayed more than once on summary pages for certain users. In my case the superuser isn't bothered with this *feature*, but ie. anonymous users are. The problem seems to be related to the book module. In my setup each book has its own taxonomy and the forums are categorized into a separate taxonomy. The summary page of the forums doesn't repeat its nodes, whereas the one of the books does.

Does the patch that comes with the taxonomy access module solve this problem? Does the book module need a patch too? If so, when will those patches be incorporated into the officially downloadable versions of these modules?

Please don't tell me that I have to dive into the code myself , because I don't want to end up with a personally forked Drupal to which I can't apply any official upgrades and patches anymore without loosing my own code changes. Moreover, I don't want to have to remember which patches I made for every fresh Drupal installation I intend to perform.

axel’s picture

Status: Active » Closed (won't fix)

Obsoleted by newer Drupal permissions API. Module for old Drupal versions not supported anymore.