There are several others worth looking at; we've used workflow access (part of the Workflow module) to create draft states; for some sites, we have then created a "control panel" that completely removes the default workflow UI from end users.
There's also http://drupal.org/project/nodeaccess_userreference and http://drupal.org/project/nodeaccess_userreference - I don't know if they will fit your use case, but they can provide (yet another) way of looking at how people have solved issues related to node access.
Cheers,
Bill
On 7/7/10 7:06 AM, Metzler, David wrote:
No, I think you've hit the major ones. If you do roll your own, you might consider something form_alter based that leverages content_access or some other module. Think of it as simplifying the UI on another module. It might make the path shorter.
Dave
-----Original Message----- From: support-bounces@drupal.org [mailto:support-bounces@drupal.org] On Behalf Of Ivan Sergio Borgonovo Sent: Wednesday, July 07, 2010 3:46 AM To: support@drupal.org Subject: Re: [support] module to let user chose if a node is private
On Tue, 6 Jul 2010 09:00:59 -0700 "Metzler, David"metzlerd@evergreen.edu wrote:
I think content access module will do this for you.
Nice. Still I think I'll have to roll something on my own.
It doesn't fit for these reasons:
- content_access saves settings in a serialized field. I need to present statistics according to node visibility and this makes quite hard to write fast SQL.
- it is role based, that makes the interface too complicated for my needs
Before I start to roll my own module do you have any other suggestion?
I'm currently examining: http://drupal.org/project/nodeaccess http://drupal.org/project/simple_access http://drupal.org/project/private http://drupal.org/project/protected_node
thanks
-- Ivan Sergio Borgonovo http://www.webthatworks.it
-- [ Drupal support list | http://lists.drupal.org/ ]