Closed (outdated)
Project:
Protected Node
Version:
6.x-1.7
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
14 Feb 2012 at 19:50 UTC
Updated:
27 Feb 2016 at 13:31 UTC
Jump to comment: Most recent
Comments
Comment #1
sw3b commentedSame for me, have to disable the module to have the node back !
Comment #2
AlexisWilke commentedWell... strange. Protected node does not manage its own node type nor uses grant.
Does that happen with all public nodes or just those where you setup a password?
Thank you.
Alexis Wilke
Comment #3
oxyd commentedSome protected nodes... Mostly does created after having install the module.
Comment #4
AlexisWilke commentedThere is a setting available in each node type that gives you a way to set the node protection on a per type basis. This protection settings use a drop down with:
1) Never protected
2) Protected when user edits (this should be the default)
3) Always protected
I just wanted to make sure you did not select "Always protected" in your node type, because if you did then what you describe is normal.
Thank you.
Alexis Wilke
Comment #5
oxyd commentedDidn't change the default setting...
Comment #6
grimreaperHello,
I close this issue because Drupal 6 is no more supported. https://www.drupal.org/drupal-6-eol
If this issue is present in Drupal 7, feel free to re-open it.
Comment #7
grimreaper