Update November 2016: This module is now deprecated. A next generation Drupal - Magento connector module will be released soon. Check out our Drupal Magento integration guide.
The Magento Integration module integrates -- you guessed it -- Drupal and Magento. There are three modules:
This module is a proof of concept method to utilize CiviCRM Contribute to make payments for a Reservation.
This is a DEVELOPMENT/SANDBOX fork of https://www.drupal.org/project/webform_rules
It attempts to rewrite the tokens used by webform_rules into line with the tokens that the base webform project uses.
The conflict (and the reason why this is neccessary) is described in https://www.drupal.org/node/1947906 - and was set "won't fix" there.
Delete All Taxonomies provides a hassle-free link to delete all taxonomies of a vocabulary on the vocabulary listing page. It also provides small enhancements to the vocabulary listing/overview page, like display the vocabulary ID(vid) of each row of vocabulary
This allows you to delete all the taxonomies under a vocabulary without having to delete the vocabulary itself.
Current features implemented
Planned features
Original description:
Provides features for soil health management.
Note: Configuration Packager has been merged into the Features module and all future development will take place there. If you were using Configuration Packager, please consider uninstalling it and using the latest Drupal 8 release of Features instead.
Whilst principally an exercise in coding and adhering to Drupal standards, the endgame is a module that will allow change logs, patch notes, and manually configuration changes to be easily tracked, and to pass information between user and developers about the status of a given Drupal environment.
Further documentation and notes to follow.
Allows a language to specify an alternative language. If a node translation for a specific language does not exist, Drupal will try to load the translation for the alternative language before throwing a 404.
This module is useful if you have multiple languages and only one language is typically translated. Rather than create all of the other translations and maintain those, the non-translated languages can load the node from the alternative language.
For example, you have the following language configuration:
Input filter to enforce addition or removal of attributes on specified HTML elements.
Note: This module is usable in its current state. I don't intend to publish it, as I have no interest in maintaining it. Get in touch if you want to become maintainer or owner of this project.
