module to let user chose if a node is private
Hi, I'm looking for a module that will add a checkbox/radio/dropdown to the edit/add form of "selected" content types that will control visibility of a node: - private only owner (and admin) could see the node - apply usual hook_access policies thanks -- Ivan Sergio Borgonovo http://www.webthatworks.it
I think content access module will do this for you. http://drupal.org/project/content_access Dave -----Original Message----- From: support-bounces@drupal.org [mailto:support-bounces@drupal.org] On Behalf Of Ivan Sergio Borgonovo Sent: Tuesday, July 06, 2010 8:43 AM To: support@drupal.org Subject: [support] module to let user chose if a node is private Hi, I'm looking for a module that will add a checkbox/radio/dropdown to the edit/add form of "selected" content types that will control visibility of a node: - private only owner (and admin) could see the node - apply usual hook_access policies thanks -- Ivan Sergio Borgonovo http://www.webthatworks.it -- [ Drupal support list | http://lists.drupal.org/ ]
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
If you want to use taxonomy... http://drupal.org/project/taxonomy_access http://drupal.org/project/tac_lite Also, make sure to check the 'related projects' block on drupal.org while you are researching. -Benj On Wed, Jul 7, 2010 at 4:45 AM, Ivan Sergio Borgonovo <mail@webthatworks.it>wrote:
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/ ]
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/ ]
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/ ]
On Wed, 7 Jul 2010 07:06:04 -0700 "Metzler, David" <metzlerd@evergreen.edu> 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. Some comments on what I've found for future reference: > http://drupal.org/project/nodeaccess - it installed cleanly on postgresql - it support aliases for roles. Nice to map anonymous users -> everyone, unfortunately I can't see how to add multi-language support - you can't disable "grant per users", this is a problem in terms of interface and information leak. I can't use form_alter since there is a theme_ form and it has some hard coded html > http://drupal.org/project/simple_access - it seems very similar to the nodeaccess - it has a bad track for supporting postgres. - nice it has a beta for D7 > http://drupal.org/project/private - could be the best fit, but I bet sooner or later I'll need features just the above modules have > http://drupal.org/project/protected_node - a bit different in scope (nodes are protected with a password) content_access has a nice feature: it support buddylist but as said it has a confusing UI for my needs and fixing it with form_alter won't solve its unfriendliness to SQL (settings is a serialized field). I'll take some time to understand if I really need the extra features of nodeaccess vs. private and in case I decide for the former I'll see if I can tweak nodeaccess and if maintainers are willing to accept some patches. -- Ivan Sergio Borgonovo http://www.webthatworks.it
participants (4)
-
Benj Fredrick -
Bill Fitzgerald -
Ivan Sergio Borgonovo -
Metzler, David