Private settings
Luca Lenardi - March 3, 2007 - 17:28
| Project: | Private |
| Version: | 6.x-1.x-dev |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | needs review |
Jump to:
Description
This patch allows the configuration of the following settings under admin/content/private:
- Select a priority value to define 'private' behaviour against other node access module (e.g. organic groups). See this issue: http://drupal.org/node/119729
- Select which content-types are private enabled
| Attachment | Size |
|---|---|
| private_settings_configuration.patch | 11.56 KB |
#1
i wanted to choose which content type should have the private checkbox but i have tan error when trying to apply the patch:
patching file private.module
Hunk #1 succeeded at 2 with fuzz 1.
Hunk #2 FAILED at 35.
Hunk #3 FAILED at 228.
2 out of 3 hunks FAILED -- saving rejects to file private.module.rej
i suppose the patch is not up to date.
and i cant help with it
i am not enough php guru
someone can help?
thanks!
#2
You need to patch against the right version in this case 1.1.2.2 from the cvs repo (http://cvs.drupal.org/viewvc.py/drupal/contributions/modules/private/pri...)
Cheers
Mark.
#3
Not that I can get the module to work :-(
#4
Yes, I was able to get the patch applied using the linked version of the module, but privacy does not work. I check "private" on the node, and the node is still visible to anonymous visitors. I am using Taxonomy Access and Content Access as well, so maybe this has something to do with it. But I tried setting the weight of the "privacy" to both highest and lowest settings.
#5
Can this settings patch be updated for Drupal 6? Thank you; this is a much needed feature.
#6
Alright, it looks like this is already available in 6.x, but where do you change the setting for each content type? Editing the content type, I see no privacy setting?
#7
Nevermind: it's under workflow! Bingo!
#8
Is the 5.x version being supported anymore? Maybe a message should be posted that only 6.x is being currently supported, that way the issue queue can be cleared?