Minimally maintained

Synopsis

A module to log more things during a Feeds import.

Features:

Helper module for Swift Mailer.

Takes care of inline WYSIWYG images that are inserted in body text using relative paths (default behaviour for most WYSIWYG editors).

This module allows Drupal users to subscribe to Stripe Plans and to in turn be granted one or more roles within Drupal.

Dependencies

• Stripe API module

Assumptions

Each user will have only one subscription, active or otherwise.

This module permits users to purchase licenses for viewing entities using Stripe.

Installation & Configuration

• Install dependencies
• Add Stripe Checkout field to the entity type that you would like to license
• Configure the default license type to apply to said entity type at /admin/structure/license_type/default/edit

Now, when an authenticated user purchases an entity via the Stripe Checkout field, they will be granted a license for that entity.

Integration with Drupal 7 Webform 4.x and Lasso CRM Register API.

Can also be found on: https://github.com/Huskyninja/Lasso-Drupal-Integration

Requirements

• Drupal 7.x
• Webform 4.x
• cURL

Quick Start

This module allows for simple submissions to Constant Contact. The method used
does not require an API key as described here: http://techblog.constantcontact.com/api/release-updates/announcing-a-new...

Summary
This module makes indexing in body (and other text fields) possible using the Apache Solr Attachments module.
It works by using a REGEX to find all files embedded in text fields of type:

• text_with_summary
• text_long
• text_formatted

This also includes field collection fields.

The managed Drupal file is stored in a seperate field (field_inline_attachments). This makes indexing
with the solr attachment module possible.

Requirements:

Provide generic migrate destinations for fields and field instances.

Dependencies

1. Migrate

Services entity dynamic resource controller

Introduces a Services Entity resource controller which invokes a hook at request-time to determine which resource controller to use.

It is designed to facilitate the creation of multiple endpoints which expose the same entities but have a different behaviour to each other.

When to use this module

When you want to tweak the query-time behaviour of an existing operation for one endpoint but not the other, where both endpoints are exposing identical resources. For example:

Lightweight module that contain 4 fields in one. There is field for a title, weight for the title, alignment of the title and the H Tag of this title. Currently this only support data storing and a very basic FieldFormatter, which will need more improvements. The main benefit of using this module instead of Entity Reference or Field Collection is that you do not need to load an entire new entity. Another benefit is that everything is store in one table.