constant PRIVATE_DISABLED in Private 7.2

Same name and namespace in other branches

1. 8.2 private_content.module \PRIVATE_DISABLED
2. 8 private_content.module \PRIVATE_DISABLED
3. 6 private.module \PRIVATE_DISABLED
4. 7 private.module \PRIVATE_DISABLED

STRATEGY 1) Node grants are not helpful for this module because they give extra access, whereas we need to remove it. 2) Hence use hook_node_access as far as possible. In this hook it's easy to selectively remove access with NODE_ACCESS_DENY. 3) However hook_node_access is not called for "node listings" - bulk read requests such as views. These must be handled via node grants.

1 use of PRIVATE_DISABLED

private_get_default in ./private.module

Apply default private settings to node based on the content type.

File

./private.module, line 18

A tremendously simple access control module -- it allows users to mark individual nodes as private; users with 'access private content' perms can read these nodes, while others cannot.

Code

define('PRIVATE_DISABLED', 0);