I got a nodetype -> "myspace". I would need a settings page where the admin can select, which nodetypes are private and which aren't. So it's not the user creating the node that decides if the node is private, but the admin.

Was that clear? :S

What do you guys think about that?

Comments

portaporpoise’s picture

portaporpoise commented

I want the same thing-- nodetype "Journal" so the users can create private journal entries. Admin would define journal as private; it would be exactly the same as a blog entry, but only the node creator and admins can read it.

greggles’s picture

greggles
he/him
Primary language English
Location Denver, Colorado, USA
commented
Title: Private Nodetypes » Provide admin control over default privacy state (and maybe prevent users from changing it)

Updating title.

I'm not sure this makes complete sense to do in the private module. It could be done with a small form_alter (to set the value and mark the field as disabled).

eaton’s picture

eaton commented
Status: Active » Fixed

This is now part of the D6 version - default privacy status can be controlled on a per-node-type basis, and users with the 'make nodes private' permission can override that default.

-Anti-’s picture

-Anti- commented

> default privacy status can be controlled on a per-node-type basis

How? When I go to the 'blog' content-type, for instance, I don't see any default setting for the 'private' module.
I do see the tick box when creating a blog post, but by default it is unchecked (ie. public)

I need it to work the other way - everything is private by default with a few nodes specifically marked 'public' by the authors.

Thanks.

Status: Fixed » Closed (fixed)

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