Still on Drupal 7? Security support for Drupal 7 ended on 5 January 2025. Please visit our Drupal 7 End of Life resources page to review all of your options.
This module allows you to associate multiple vocabularies to a term-reference field. Standard drupal term reference fields allow you to reference terms in a single vocabulary only.
Use case
Let's say you have a free tagging field on a node which your editors would like to use to tag content with. They would like to tag content with terms from different vocabularies. For e.g. content could be an article of type Insight, and be also tagged with category philosophy. It could further be tagged with a personality Freud. In this case, these three are terms from different vocabularies.
Insight - is an Article type term.
Philosophy - is a Category term.
Freud - is an unassociated random Tag.
Article type, Category and Tag are vocabularies.
It makes sense to have a term reference field referencing these vocabularies instead of just one to avoid creation of duplicate terms. In the present case (without multiple vocab term reference), all terms would get stored into the Tag vocabulary. There would also be duplicate terms in the Article type & Category vocabularies. This would also lead to term URLs like /insight & /insight-0 if you are using pathauto to alias your term pages with the term name.
Regcheck is a super lightweight and simple module that adds a hidden checkbox on the user registration form, and kills the registration process if it is checked.
This module provides a credit card payment method for Drupal Commerce that encrypts credit card information using the PHP: GnuPG extension. The encrypted card data may then be sent via email for manual processing and is stored in the DB for archival/backup.
A common use case would be for shops that would prefer to use an existing hardware or virtual terminal for manual card processing or have an accounting system that handles card processing.
Operation
The module takes the credit card information supplied at checkout and encrypts it using your GPG public key. The original, unencrypted input is then replaced by the encrypted block and stored with the other order data in the commerce_order table.
A commerce order token is created by the module that contains the encrypted block. You may embed this token into an email that is triggered by "Send an order notification e-mail" rule to cause it to be emailed to an account of your choice.
There are various email client plugins for decrypting GnuPG blocks embedded in email messages, such as Outlook Privacy Plugin and gpg4o. Please refer to Google for others.