CVS messages for Restricted content
April 30, 2009
-
#441400 by Dave Reid: Add API function for checking restricted node access.
January 28, 2009
-
Bugfixes
January 3, 2009
-
- Changed my mind about the token substitute. Only replace values if token is available.
-
- Backup token replacement when token module is unavailable.
-
Restricted content: /modules/restricted_content/restricted_content.admin.inc 1.3
Restricted content: /modules/restricted_content/restricted_content.info 1.2
Restricted content: /modules/restricted_content/restricted_content.module 1.5- Token module integration! - Commented out the 403 handling for now. Not sure if it's a good idea yet.
-
- Change restricted_content_node_form() for reuse.
-
Restricted content: /modules/restricted_content/restricted_content.admin.inc 1.2
Restricted content: /modules/restricted_content/restricted_content.install 1.2
Restricted content: /modules/restricted_content/restricted_content.module 1.3- Added restricted_content_variables() and restricted_content_var(). - Added uninstall for variables. - Added administration settings form with customizable messages.
-
- Changed access restriction to an inclusion instead of exclusion. - Fixed link to node URL.
-
Restricted content: /modules/restricted_content/restricted_content.admin.inc 1.1
Restricted content: /modules/restricted_content/restricted_content.info 1.1
Restricted content: /modules/restricted_content/restricted_content.install 1.1
Restricted content: /modules/restricted_content/restricted_content.module 1.1- Initial commit of restricted_content module.
-
Create module Status: Vendor Tag: vendor-tag Release Tags: release-tag No conflicts created by this import
