Helped sites that were deployed directly from a CVS workspace, as opposed to sites built via packages downloaded from drupal.org. This module is obsolete now that drupal.org uses Git not CVS. Instead, you should use Git deploy.
This module provides a powerful interface for managing taxonomies. A vocabulary gets displayed in a dynamic tree view, where parent terms can be expanded to list their nested child terms or can be collapsed.
The Taxonomy Manager has following operations and key features:
Oct 20th 2010 - The name of this module, could cause confusion to those using drupal core functions. Additionally there is currently a function name conflict with the ftp code used in the backup_migrate module. This is discussed here: #803964: function name conflicts with drupal_ftp
Menu Block Split has moved to Github
USE THE NEW 1.6 RELEASE - it should be stable and contains bug fixes. Looking for co-maintainer. See message in issue queue.
This module adds the ability to have several different membership types, each collecting different data from the user for registration by using custom content types and the combination of nodeprofile and pageroute modules (both required). The accounttypes module is recommended but not required. See each required module for any dependencies that they might have.
What this module does is:
When a user attempts to register for your site, they will first be presented with a drop down selector of membership types which you as admin have previously defined. They will read instructions for proper membership type selection that you previously wrote. After selecting and submitting this form, they will be presented with the standard Drupal registration form. Depending on whether you require admin approval of new accounts and/or email verification, the user will then either - a) be immediately presented with pageroute consisting of nodeprofile pages which will collect further data from them, b) be logged out so they can verify their email, then when they return be presented with the pageroute for their membership type as in (a), or c) after the admin has unblocked their account and/or the user has verified their email, when they return they will be presented with the pageroute as in (a).
In all cases, if you require that certain pages of the pageroute be filled out before the user can use the site, they will be routed to the next unfilled page at each login, or each attempt to browse to another page until they do. In other words, they will be stuck until they complete registration, except that they can logout at any time.
See the USAGE example in the README for how to setup nodeprofile, pageroute, and your content types. [Note: this needs updating in one respect. When you create your pageroutes, you must now specify tabs, not buttons or you won't see the return link from the 'Personal data' section of the user profile back to the main profile area.
Optionally, if you use my Account Types module (http://drupal.org/project/accounttypes), you can assign/associate an account type with a membership type. The README explains the difference between these two concepts and how they can work together.
This module is also aware of OG and my Content Type Administration by Organic Group module (http://drupal.org/project/og_content_type_admin). See the README for how this module interacts with these others.
The README contains the following:
--CONTENTS--
REQUIREMENTS
SETUP/INSTALL
FEATURES
USAGE (Example)
UNINSTALL
CREDITS
See the documentation link below.
This module is complicated to setup and use because of its dependencies. You must read AND UNDERSTAND all documentation for the nodefamily, nodeprofile and pageroute modules before attempting to use this one. Oh, and understanding CCK is a must as well. This precludes use by casual users, whether newbie or not. I'm willing to help, but I won't hold your hand.
Contact me via my Drupal profile if you'd like to hire me to set this module up, modify it for your particular use, or other Drupal/PHP work.
This module provides an alternate way to manage blocks. If you have many blocks that are displayed in different configurations across your site's pages, managing them through the standard blocks admin interface can be tedious. For example, say you decide you want to add six blocks to three different pages based on request URI and four blocks (including two of the original six) to three other pages based on node type. This quickly becomes a frustrating exercise as you think through writing logic per block that will handle the overlap correctly. Block Assign simply provides another approach to organizing blocks.
Please be very sure to read the release notes before installing. They warn of (intentional) potential data loss as a result of configuring the module.
Extends the administrative interface for Drupal core's "Update status" module (added to core in 6.x).
DAST is a set of build projects, tasks and other extensions created on the Phing framework for automating a wide variety of Drupal deployment and staging scenarios. The goal of DAST is to provide a formal, repeatable, reusable process for 'building' a Drupal site using a formal build tool and build language. DAST applies the concept of the software build to creating Drupal sites...Phing build files are syntactically identical to Ant build files and provide tasks for downloading Drupal core and modules from CVS, copying and deleting files and directories, creating the Drupal database and user, writing to configuration files, and generally any of the manual steps that users / developers / testers / admins repeatedly perform to bootstrap a new Drupal site.
Admin Message provides an easy way to show short messages to users via the creation of Admin Message nodes which are displayed in a block. The messages can be individually closed by users (both logged in and anonymous via a cookie).
Examples could be "Welcome to this site...", "Temporary downtime...", "Important security announcement...", "New feature...", etc.
This module augments Views by allowing bulk operations to be executed on the displayed rows. It does so by showing a checkbox in front of each node, and adding a select box containing operations that can be applied. Drupal Core or Rules actions can be used.
7.x-3.x requires Entity API.
