Maintainers strive to actively monitor issues and respond in a timely manner.

Profile Switcher

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
⋅ Categories: Actively maintained, Under active development, Developer tools

HyperDrupal

HyperDrupal is a distribution providing the basis for building a REST API server using Drupal 8. It derives its name from the use of hypermedia API responses, allowing REST API clients to traverse the API in much the same way a human traverses a web page.

The promise of a mature REST implementation is the API equivalent of a wiki walk, and Drupal 8 is poised to be the perfect framework for realizing this potential. Thanks to Web Services and Context in Core Initiative spearheaded by Larry Garfield, we now have a core REST module with an optional HAL module that allows us to format responses in one of the leading generic hypermedia types available (see the specification). We have also included Guzzle to serve as our HTTP client for consuming remote web services.

This distribution will be a sandbox of sorts for proving the use case of Drupal 8 as a REST API server and contributing to the development of tools that extend the functionality of core as both a server and client.

What does it do?

⋅ Categories: Actively maintained, Under active development

Welcome Gate

Conversion of the Welcome Gate WordPress plugin for Drupal: http://www.welcomegateapp.com/

⋅ Categories: Actively maintained, Maintenance fixes only, E-commerce

Style Guide Nodes

Provides example nodes for the Style Guide module.

Creates examples of each content type in selected variants.

⋅ Categories: Actively maintained, Under active development, Developer tools

Domain Individual Logo

Domain Individual Logo allows drupal to use a different Logo for each domain in use. It needs Domain Access module to run.

More to come...

⋅ Categories: Actively maintained, Under active development, Developer tools

TOA_B2C

Booking engine for Travel Open Apps.

⋅ Categories: Actively maintained, Under active development, E-commerce

Pages

Subscribe with RSS Subscribe to RSS - Actively maintained