creating a node with pw works fine the first time but when the node is edited the pw stops working. has anyone experienced the same problem? if the pw is changed, the user can not access the node anymore, after entering the new pw. We use revisions and workflow when editing nodes, could that be related?.

Comments

AlexisWilke’s picture

AlexisWilke commented

The password information is saved using the node identifier (nid). So that means the revision is ignored.

I would think that something in the result is modified by one of those modules that prevents the protected node module from reacting properly. It should ignore the password if empty, but the protected node flag may not make it through properly.

When you say that you're using revisions and workflow, do you mean another 3rd party module? Or just the Core revision feature?

Thank you.
Alexis Wilke

luthien’s picture

luthien commented

I'm using the following modules:

http://drupal.org/project/revisioning
http://drupal.org/project/rules
http://drupal.org/project/workflow

every time an user edits a node, a new revision is created. When the revision is set up as the live version of the node, the pw stops working. If we don't create a revision, the pw will works fine with the original node. The revision system works fine with other modules, it is failing only for your module, maybe they changed something for the module that conflicts with yours. Any other ideas why this is happening?

thanks

AlexisWilke’s picture

AlexisWilke commented

I have rules and just tried revisioning.

The Rules do not do anything to a node getting updated so if yours does... I did not test in a similar environment.

The Revisioning module seems to work just fine.

So that leaves us with the workflow or something in the Rules menu if you tweak the node at the time it gets published by Revisioning.

Could you test without the Rules and/or workflow modules?

Thank you.
Alexis

luthien’s picture

luthien commented

Disabling the workflow module: the content permissions were rebuilt, creating a new revision and changing the pw, it worked out fine.
Enabling the workflow module back, rebuilt permissions, and it worked fine this time.

Perhaps it is a permission problem. The only workflow rules I have in place are:

1) When updating existing content, change Workflow to In-Draft
2) send an email for each state's change: draf-in review-live

AlexisWilke’s picture

AlexisWilke commented
Status: Active » Fixed

Protected nodes don't make use of the permission grants (which is what the rebuild permissions is about.)

This being said, if workflow uses them and there was a problem with that part of the system, then you could get such a problem, indeed.

At this point I'll mark this entry as fixed. Feel free to re-open if the problem returns.

Thank you for reporting back.
Alexis Wilke

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.