A user can't edit nodes created by another user, both with same role, for which the content type has default edit permissions set for that role.

node privacy by role works great set the same way for a custom page, + for book pages.

This case is using Janode node type, displayed using views module.
The role (editor), under access control, is granted Janode "create" + "edit own" permissions. Under settings / content types, the janode node type is set granting "editor" role default edit permissions (also view).

These permissions show "editor" is checked for "edit" when either editor is creating a node (patch not applied to not show form here).

The only way I can get it so a user can edit another user's node, is to give the role "administer nodes" permission, which is not ok.

Can't see how this is not a bug, so submitting as such, I welcome being corrected with a solution, if in fact, this is actually a support request, thanks!

Using 4.7.2 + npbr cvs 12/16/05

Comments

neuston’s picture

neuston commented

There have been many people (including me) encounter the same problems. I found it out in the forum. But... no solution yet. Any help here?

ajk’s picture

ajk commented

Hi there. I'm the maintainer of janode (but not the maintainer of node privacy byrole).

What you are describing is normal as far as I know. I've had a brief look at the node privacy byrole and don't see where "edit others posts" is an option.

It's normal for posts to be edited their creator or by an editor. Editors need "administer nodes" permission. This is how Drupal works. So, it's not a bug afaict, it's by design. If this issue were in my queue for Janode I'd set the status to "by design" and that would be that. But it's not my queue so I'm leaving it as "active", although I don't think it should be.

regards,
--AjK

jondoesdrupal’s picture

jondoesdrupal commented
Status: Active » Closed (fixed)

Tidying up old issues. Focus now is on Drupal 5 version of the module. If there is still demand for this to be resolved and it gets resumbitted then I'll look into finding a solution, however going on ajk's comments it looks like there's no issue after all.