Administration Notifications 6.x-1.1

ConceptThis is a simple module that can be used for communication of site changes/updates between the site designer/developer, and the site owners.For example, if you maintain a drupal installation for another company, you can use this module to inform them when you have updated versions of the site (ex drupal 6.10 -> 6.11), updated modules on the site (i.e. Administration Notifications 6.x-1.0 -> 6.x-1.1), added new modules, or changed the site design in some manner.This module creates a content type called 'Administration Notification'. When a node is created using this content type, it posts to the site just like any other node, but it also automatically posts an email to to a specified email address, containing the contents of the node.Pages this module creates * node/add/admin-notification - this is the node creation page. * admin_notification - this is a page that shows a list of all past notifications. * admin/settings/admin_notification - this is the page where you set the destination email address for admin notifications.Post InstallationAfter installing this module, you should go to admin/settings/admin_notification and set the email address right away. It is set as a default to the site email address.WarningIf the notifications are shown as teasers anywhere (example: promoted to the front page), users will be able to see the teasers for the notifications, even when the user doesn't have permission to see the notifications themselves. To suppress teasers for users who aren't supposed to see them, you can use the Suppress Teasers module. This will prevent users without permissions to view a node (any node, not just nodes created by this module) from being able to see it's teaser.As of release 6x-1.1, this module has been brought into line with the Drupal access system by using hook_node_access_records() and hook_grants(). As such teasers will not be rendered if the user doesn't have permission to see the node itself. Therefore, the suppress teasers module is no longer necessary, and can safely be removed if you are only using it for this module.NOTE: The content access permissions should be rebuilt when upgrading to version 1.1. This can be done at admin/content/node-settings

Requirements:	No special requirements
Platforms:	PHP
Keyword:	Access,  Address,  Content,  Created,  Creates,  Doesn,  Drupal,  Email,  Module,  Modules,  Notifications,  Permissions,  Posts,  Site,  Suppress,  Teasers,  Updated,  Users
Users rating:	0/10