Developer Module that assists with code review and version upgrade. The module supports a plug-in extensible hook system so contributed modules can define additional review standards.

The 5.x-2.x version adds a new UI, core support, theme support, and a cache for faster display of unchanged files. Also supports rule #severity of "minor", "normal", and "critical".

The 5.x-dev version includes the 6.x upgrade review. The HEAD version also includes this review and works with Drupal 6.x.

Built-in support for:

• Drupal Coding Standards and a first attempt on the Drupal Commenting Standards
• Converting 5.x modules to 6.x (best), 4.7.x modules to 5.x (better), 4.6.x modules to 4.7.x (basic)
• Handle text in a secure fashion (very basic, need works, but what it finds is good), Performance Review (under development)

The views_fastsearch module provides a faster functionally equivalent alternative to the views "Search: Index" filter. This search is considerably faster (than the search in views_search.inc), supports OR terms, exception terms, and sorting by score.

1. It is noticeably faster - 5-20x faster
2. defaults to AND terms, but supports the OR keyword
3. implements exception terms using the – prefix (i.e., “global warming –ocean” searches for nodes that include “global” and "warming" but do not include “ocean”)
4. implements a sort by the search word score, when there are multiple terms, it sums them up – this presents results where the search words are in the title or header tags higher up in the list

This module is also a proof of concept of a solution using alternative search SQL that could be used as a basis for a patch to core.

The views_filterblock module basically moves the horizontal filter from the views page content area into a (vertical) block. This differs from the views block option which displays the view exposed filters AND a limited number of rows from views content. It themes the block using collapsible fieldsets rather than the table currently used by views, and it uses some logic to decide which fieldsets should be collapsed or not collapsed based on whether the filter form has a value.

The daterange module provides a programatic extension for date ranges that can be used by other module developers. It creates new filters for node times, 'Node: Created Time Between' and 'Node: Changed Time Between', as well as new date range filters for CCK date (but not datestamp) fields.

If jscalendar is installed and enabled the date fields are augmented with the jscalendar button for selecting a date.

The supported operators are 'Custom date range', 'Outside date range', 'Before', 'After', 'within the past week', 'within the past month',
'within the past 3 months', 'within the past year'. When the the operator doesn't need both input fields, JavaScript attempts to undisplay the unused fields.

The date fields understand the words 'today' and 'yesterday' and sutraction of days, months, or years.

The views_alpha_pager is a simple module that implements an alphabet pager (A B C) instead of a numeric pager (1 2 3) for views. This module relies upon a reasonable alpha sort order defined in the view. When one is not defined, it reverts to the numeric pager.

This is a module, not a theme. It extends the Drupal admin theme page options (admin/settings/admin) to allow settings of custom CiviCRM user and admin themes.

This module is developed (and partially supported) by CivicActions.

Implements a Views plugin that adds a "View Type" to the Views page and block named "Tagadelic" (in addition to "Teaser", "Full Page", etc...). When selected, the nodes returned by the view are themed as a "Tagadelic" block in the same vain as the tagadelic module. At least one vocabulary field should be added to the Field List.

Application Module that imports and manages Bills from the U.S. Library of Congress website as CCK nodes. It imports Representatives, Committees, Bills, and Bill Actions. It creates these CCK types when the module is installed, and imports this data on cron runs. It manages the automatic updating of this data as it changes.

Assign permissions to vocabularies by user role.

The core taxonomy system allows vocabularies to be assigned to node types. This module extends that by allowing the editing and/or display of the vocabulary to be controlled by user role. It attaches itself to the vocabulary add/edit form and gives the administrator three options for each role - (1) edit and view, (2) view only, and (3) none.

This module makes it possible to create a vocabulary for administrator purposes, hide this category from most users, and then use the category as a views filter.

Here are two use cases:

Create short form's from any form, mostly to place in a block.

It does this mostly through jquery:

• removing the field title, and if the field has no value, and when the field does not have the focus, displays the field's title as it's value.
• removing fieldsets
• removing non-required textarea's

Short Form can be used by module developer's:

• $form['#theme'] = 'shortform';
• shortform_alter($form);

Short Form can be used by site builder's:

• on admin/settings/shortform, enable the "spy"