Configurable Priority

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!

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.

Not that I can get the module to work :-(

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.

Can this settings patch be updated for Drupal 6? Thank you; this is a much needed feature.

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?

Nevermind: it's under workflow! Bingo!

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?

As the screenshot on the project page shows, the second part of this feature is already part of the latest 6.x release.

What isn't currently active is the ability to change Private's node access priority to a higher value.

The general motivation for this feature is that folks may have Private installed on as site with multiple node access modules and wish for Private's node access restrictions to trump the other modules when a node has been marked as private. This seems like a fairly common use case.

Depending on maintainer preference, I will roll a patch to either default to a high priority, which would probably work for a majority of use cases, or add a configuration option to set the priority.

Thoughts, @eaton?

For a project I'm working on, we have Forum Access and Private sometimes working on the same nodes and forum_access's priority control is insufficient to produce the desired results because of the way that it interacts with ACL. Another use case could be when site builders want privacy to supersede Organic Group node access restrictions (http://drupal.org/node/119729).

Closing ancient D6 issue that doesn't seem to apply any more.

You can configure per content type in D7 code.