Under active development

The Parents module will create a family member entity for accounting for family relationships. A family member can be associated with a Drupal user.

This module provides a Drush command to switch between install profiles found in /profile directory:

drush switch:profile [new-profile]

This is useful for moving an existing site to distribution or moving from an abandoned distribution back to a standard Drupal core install.

Profiles can become disabled for a number of reasons (see #1170362: Install profile is disabled for lots of different reasons and core doesn't allow for that. Beta 2 or > of Profile Switcher can also be used to re-enable the active profile. The profile may become disabled again if the underlying issue (like a dependency defined in the profile's .info being disabled) ins't resolved, but this will at least resolve the issue temporarily.

IMPORTANT WARNINGS:

• Switching profiles is NOT a trivial change like switching a theme.
• ALWAYS test before using on a live site and ALWAYS have a backup
• Switching Profiles does NOT run the profile's .install. This will not work for all distributions.
• Modules, themes, and libraries included in a distribution are only available when using the distribution. Modules, themes, and libraries in sites/all are available to when using any profile... AND OVERRIDE THE VERSION IN THE PROFILE EVEN IF THE SITES/ALL VERSION IS OLDER
• Because some modules register absolute paths to files in Drupal's registry table, you may run into issues when switching profiles even if the version of the module is the same. (Tips for fixing registry related issues).
• If the Profile Switcher module was included in a /profile/[profile_name]/modules and you switch to a profile that doesn't include the Profile Switcher module, you will get a page not found error after the switch not be able to switch back until adding the Profile Switcher module to sites/all/modules

Features module used for community at large elections on ADO site.

The scope of this project is simple: to provide an entity wrapper to the watchdog table created by dblog in order to expose access to that table via projects that utilize the entity api. This was developed for integration with the operations available as a webservice via the restWS module so that there could be a site that centrally manages the watchdog messages being generated by a series of related sites instead of having to enable dblog on each site.

In practice

This module was built for use with the Remote Watchdog distribution. The CIS Connector library of connection modules has support for connecting to systems running this module thanks to hook_watchdog so you can route messages that were generated to your central site, running this module to expose RESTful API operations via Entity API.

Difference from Better Watchdog UI

• Better watchdog has views, rules, and other UI integrations
• This module is purely for developers and is tested to work with RestWS to allow for webservice integration

Provides example nodes for the Style Guide module.

Creates examples of each content type in selected variants.