Add node privacy

Currently this module is intended to be used to allow users to control access to their instance of things that every user has - a profile, for example, or a track page. An individual node is something that one user may have, but another user may not and so it would not make sense for a privacy setting to appear for it on every user's settings page. There are other modules that already allow you to control access to nodes, so no effort was made to include that functionality. Though it may be possible at some future point if it makes sense.

For the extra privacy states that you mention it should be fairly easy to add those. Look at the privacypu_flag_friend.module for an example of how to implement those. In the registered user example you would just load the global user object and then check whether that has the required role. Return true if it does, false if it does not. I haven't used user relationships, but I imagine the privacy state callback would look similar to the flag friend privacy state callback, a sql query that checks if a friend relationship exists for the two users and then returns true if it finds one of false if it does not.

Check out CCK privacy, node access, content access, and the user relationships node access modules. There may also be others. If none of those meet your needs for node privacy then feel free to turn this issue into a feature request. I can't promise anything would happen in any kind of reasonable timeframe, but that would be the first step in making it happen.

This sounds like a great module and exactly what I would need! However I am not exactly sure how to customize it for different content types. Let's say I have a node type called "album" and I want each user to have control over who has access to their albums. What's the best way to implement this? Thank you in advance!

At the moment the best way to do that is to turn this issue into a feature request, which I've just done. As mentioned above, per node privacy with this module might be a little tricky as it doesn't fit the current paradigm of setting privacy preferences in user settings. But per content type privacy, which is what it sounds like you are after, would be a much easier feature to implement and makes a lot of sense within the existing framework.

The way that might work would be to have settings on the content type edit form to select a privacy type that would govern the nodes of that content type. Alternatively settings could also be provided on the privacy type edit page in the form of checkboxes for each content type. The node author would set their privacy settings on the user settings page. Then when a node is viewed it would check the privacy settings of the node author for that privacy type and display or not accordingly.

To use your example, a user might have an 'Albums' privacy setting on their user settings page, then any album node that they create would be governed by that privacy setting. Does that sound like it would meet the requirements for your project?

Thank you for your quick response. Yes this is exactly what I was looking for. When do you think this feature can be released?