With node perm role, nodes are listed multiple times in workspace and in content list
bomarmonk - August 12, 2005 - 00:41
| Project: | Nodeperm_role |
| Version: | HEAD |
| Component: | Code |
| Category: | bug report |
| Priority: | critical |
| Assigned: | robb |
| Status: | closed |
Jump to:
Description
I'm getting redundant listings for nodes when running nodeperm_role with Drupal 4.6.2 and the workspace module. For example, I'll have uploaded a single image, but it will be listed around twenty times in the workspace list. The content list at admin/node lists nodes correctly. Any ideas?

#1
I had a been working on some patches for nodeperm and can't see how it could be doing that. Nodeperm maintains the node_access table which ONLY controls grants per node. I have not looked into the workplace module for a possible problem there. Do you still have this problem and if so do you have any additional information you could share about it?
#2
I have filed a problem report with the workspace module, as I did not know whether this was a problem with workspace or nodeperm_role. More information about my difficulties can be found here: http://drupal.org/node/27576
Any help in resolving this issue would be great, but I'm not sure which module needs fixing. Thanks for your response.
#3
Ah, I see the issue now.
Workplace and nodeperm both use the 'node_access' table. The node_access is an OR based permission system. In other words if a user is granted permission by ANY module using node_access then the user can access the node!
The following is a GUESS, I have not looked at workplace. I do not suspect a problem in node_perm since I use it daily with my extension that solves the above problem (see below for more details). The problem is that workplace probably is getting back an unexpected number of rows for a node and is NOT using a distinct statement or is making direct use of the node_access table. But fixing that will still leave you with a problem since most people expect an AND operation between the node_access modules.
For more details on a more general fix for this, see http://drupal.org/node/24868 and if interested grab the latest version in that thread. AL though it is stated as Alpha it is going to beta next week with only a few minor tweaks and is currently used on some live sites.
If this answers your question can you close this issue?
#4
Rob, I'm already using your latest node_access mod. I do have taxonomy access installed as well, but I don't remember seeing node_access settings that allow me to configure how workspace is interpreted. I'll double check. Right now I'm on a computer where I can't access my admin for my drupal site.
#5
Rob, I've played around with everything and made sure that the modules are the latest 4.6 versions (nodeperm_role, node_access, and taxonomy_access). Apparently, the nodes that were created by the author get repeated in that author's workspace multiple times. The ones that are just made editable through nodeperm_role do not get repeated multiple times, but appear to be listed correctly. Any ideas?
#6
I beleive this issue was corrected via changes to orkflow settings. If not please let me know.
#7
Robb, I will test with 4.7 and when you have node_access working. I'll let you know how it works.