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.

CommentFileSizeAuthor
private_private_default.patch762 bytesq0rban

Comments

q0rban’s picture

q0rban commented
Priority: Critical » Normal
Status: Needs review » Active

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.

esmerel’s picture

esmerel commented

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.

esmerel’s picture

esmerel commented

so, in messing around today, I discovered this: the private flag does work if you're creating a node via create content >some content type" but NOT if the content - like, say, an image - is done via image import.

adamps’s picture

adamps commented
Issue summary: View changes
Status: Active » Fixed

Fixed in 7.x-2.0-beta1. Testing of that release would be welcome.

daggerhart’s picture

daggerhart commented

Tested and working in version 7.x-2.0-beta1 when creating new nodes via rules.

Status: Fixed » Closed (fixed)

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