Maintenance fixes only

This module logs user agents for nodes and comments. It also adds a "view user agents" permission that can be used in themes to show the user agent a given post was made with. This may be useful for sites with support forums pertaining to browsers or to web sites themselves, in which knowing a user's user agent might help resolve issues. The module adds "useragent" property to $node and $comment objects that can be used anywhere the fully-loaded nodes are available.

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.

What is Content Access?

Yet another content access module.

This module allows you to manage permissions for content types by role and author. It allows you to specifiy 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.

Why Do I Need It?

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.

Ever design a site and happen on a nifty trick that you may want to use again? You wrote it down and lost the paper, didn't you.

You designed a great site for someone else, and the first thing they do is call you up and say "How do I do...?"

You can't remember all the modules, themes, and CSS changes you made and it's time to upgrade...

You'd love to put all that stuff on the web site, some place easy to find, but safe from casual hackers...

Well, here you go... Introducing SiteNotes. A simple module lots of uses.

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.

Registration role lets an administrator select a role to automatically assign to new users. The selected role will be assigned to new registrants.

Be sure this role does not have any privileges that should not be given out to just anyone who registers. Because we shouldn't give away any real abilities above an authenticated user by default, this module really has only a few known useful applications:

A Drupal module that allows donations via Paypal to buy beer, coffee, tea, water or whatever. The module is heavily inspired by Ankesh Kothari's Buy Me a Beer Wordpress plugin.

This Drupal module offers a trouble ticketing system similar to the ancient PHPHelpDesk. It authenticates users from Drupal and classify them to user groups and department units. It provides the following features:

Version Control API is an engine for Drupal integration with a variety of version control systems. The focus is primarily on working with canonical, server-side repositories. It provides basic tools that allow for things like history listings, commit access controls, triggered actions when new code comes in, and direct on-disk repository management.

This module is a core engine and does nothing on its own without a "backend" module that provides integration with a specific VCS (e.g. git, bzr, svn). This module provides a consistent base interface (UI and API) for interacting with all the different backends.

Version Control API is the system that drives all of Drupal.org's Git integration.