Setting to 'enabled, private by default' is broken
q0rban - June 25, 2009 - 14:03
| Project: | Private |
| Version: | 6.x-1.x-dev |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
Description
Steps to reproduce:
- Edit a content type, and set the privacy settings to 'Enabled (private by default)'
- Go to create a new node of that content type.
- No privacy option is set, and when you save the node, it is publically visible.
Marking as critical, as people may assume that the nodes are private when they aren't.
| Attachment | Size |
|---|---|
| private_private_default.patch | 762 bytes |
#1
Nevermind, I think this was actually due to a typo in the Constant name for that setting, which looks like it's been fixed in dev. I had a bunch of variables stored as s:17:"PRIVATE_AUTOMATIC" instead of s:1:"2".
There still should be something in a hook_update_N() call to fix old variables that have been saved that way. I'm going to take down from critical, though, since the user should be able to just re-edit the node type and save again to fix it.
#2
I can replicate this on my site - neither 'Enabled by default' or 'hidden' will mark items private at creation time. You can easily go into the 'content' list and mark them private afterwards, but the defaults are not working.