Private node module update
Bèrto ëd Sèra - January 29, 2007 - 01:30
| Project: | Book Expand |
| Version: | 5.x-1.0.x-dev |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | dwees |
| Status: | closed |
Jump to:
Description
Hi! By using the private module (http://drupal.org/project/private) one can have hidden groups. My need would be to have all the stuff belonging into such hidden groups kept away from public (as you do when filtering OGs), while the rest could happily remain filtered by 'none' and allow books made of material from any source. Would that be possible?
Maybe you could use the "listed in directory" feature from OG to get the same result with no need to check for too many modules.
#1
I think that if you have a private group it should have its own lead book page, and then when you filter by group, only the pages from the private group should show up. However, I don't have the private group module enabled on my site. Could you (with a fresh install as my module suggests) test to see if this is true?
Dave
#2
Oh sorry I misread your initial post. Yes it should be possible, basically I would need to not include nodes which are marked as private. I can certainly look into it. The eventual plan is to allow for the mixing and matching of different filters.
#3
Basically all I need is
- to be able to use "none" AND
- not to see stuff belonging into OGs with the "list in groups directory" box unchecked.
I'm in the process of deciding what I'll do with OGs, so it really takes some thought to find out what can be easy and solid at the same time. Basically what I'd like to have is "invisible by default" materials for sysops, editors, Board of Tustees, etc.
I could have another approach by using roles, but I like the OG idea and I'd rather would use one tool for all my needs (once you start to pick up 3rd party modules your site grows tremendously complicated anyway).
Thanks
#4
It now works with the Private node module as requested, except you need to update all of your current public nodes (easiest is with a direct database query) in the private table so that every node is either public or private. Please test to see if this works.
#5
Okay everything just GREAT, thanks :) I modified Private.module a bit, to make sure it meets your needs here (see http://drupal.org/node/114040).