Allows creation of new drupal sites from a central drupal site without the creator having access to database info. The new site is installed either in the same database with a different prefix or if the drupal db_user has access to create a database and grant privileges, then possibly there.
Unfortunately Drupal does not include the powers of immortality or invincibility. You may someday get hit by a truck, or even just decide that you no longer want to maintain the site. So someone else may have to take over.
Where do they start? I know you documented the site really well, but the next person doesn't want to read those 14 binders of documentation you left behind. They can always go through all the administration screens and look for the information, but that can take a lot of time and even those pages don't tell you everything. Some things you're only going to get by looking directly into the database.
This is what the Site Documentation module is designed to do. In addition, it will detect some problems that may exist in your installation, and optionally correct some of them.
Content Access allows you to manage permissions for content types by role and author. It allows you to specify custom view, edit and delete permissions for each content type. Optionally you can enable per content access settings, so you can customize the access for each content node.
Disclaimer: This module has not been reviewed by any religious organization. No guarantee of its suitability for any particular religious purpose is implied.
The time that the sabbath begins and ends changes throughout the year because, historically, a full day began at sunset. The Sabbath module provides the sabbath start and end times for any week and any latitude, longitude, and time zone.
This returns an object containing the sabbath start and end timestamps, the time zone offset for each, and the beginning of the next week. $future can be set to 'day' or 'time' and specifies whether to show the sabbath that ends after the given time or after the day in which the time occurs.
The D6 core filters system allows an admin to restrict the type of input format available to a user by user role. It does not, however, allow the admin to restrict the available input formats by node type. So if you e.g. want to allow for node bodies with embedded images and others without, you will be stranded with just core functions.
Features
This module fills that gap. It provides a simple checkbox-based interface where an administrator can restrict what input filters are available to what node types. These rules are applied after the role-based restrictions, so it can never offer more input formats than the default role-based input formats would.
As of 6x-1.5, this functionality is extended towards each node type's comments. You may chose to restrict them the same way as the corresponding node type (default), to a different scheme or not at all.
Quick reference
Install the module.
Note the additional options on each node type settings page (sections submission and comments (if comment module is active).
Optionally set the new bypass filter restrictions user permission for each role.