Very simple module which does nothing more than automaticly add the appropiate timestamp values for the fields 'created' and 'changed' of an entities base table if they exist.
This module fills the address-fields given in the admin-section of the module with values from the Pro6PP database. A license from Pro6PP is required.
This is a Drush extension that pings http://dgo.to to retrieve user ids from user names or IRC nicks.
Project status is an extension for drush which takes a list of Drupal platforms as arguments and returns a list of modules which are in use or not in use by the sites within these platforms. It is able to list all modules, or only those which are in use, by platform and site. By default it only reports on modules within sites/all/ or sites/default/, but it can optionally report on modules within site directories as well. Results are grouped by project (for example, the modules views and views_ui are shown together as views) unless an option is given to list each module separately.
In brief, this module was written to answer the question, "which modules in this shared platform are actually in use, and by which sites?"
This is a module that migrates the jQuery imageLens library for Drupal.
The module has an admin interface (admin/config/user-interface/imagelens) where you can enable including of the JavaScript file each time to the site.
Otherwise you can include it manually via a simple function callback:
This is a Git pre-commit hook that, when put in a local repo, will alert you when you are about to commit a dsm(). I created this for #819900: Create a pre-commit hook(s) that checks for common oopsies.
Semantic Fields (formerly Semantic CCK in Drupal 6) was created to give users the abilility of customizing and enhancing the HTML output of a field. With Semantic Fields enabled, users can specify the HTML wrapper element and classes for:
This allows users to quickly create semantically rich and meaningful HTML markup for fields, such as:
Provides a UI for site builders to quickly and easily search for and install modules and themes from within the admin area of their site. This is similar to how WordPress works.
The reasoning behind this project is to lower the barrier for new Drupal users to quickly and easily find and install modules and themes on their sites, without needing to know how to use Drush or using the current process of searching for a module on Drupal.org, downloading it, unzipping it, uploading it to the correct directory, and finally enabling it.
This module is used to create a blacklist of passwords that will be restricted from being used. So for instance if you don't want weak common passwords like "password", "123", "god", "love", etc. Then you can add them to the list of blacklisted passwords.
If you are looking for a way to put more constraints or conditions that need to be met for a password to be excepted please visit Password Policy module.
This module is still in development and should not be used on production sites.
Add close buttons to Drupal's status messages to allow manually hiding them.
