Remote content user interface

Component type

module

Maintenance status

Development status

Downloads

1269

Component created

Component changed

This project extends the Drupal user interface from a "local" site to allow for the visual design and edit of content stored in one or more "remote" databases. This project defines a remote database as a database:
- other than the primary (or a slave) database for the "local" site
- associated with another site, often as its primary database

Commerce Billy

Component type

module

Categories

Maintenance status

Development status

Downloads

28899

Component created

Component changed

Commerce Billy is a lightweight approach for a billing system for Drupal Commerce (Billy = Billing Light). It uses the commerce order entity to hold invoice information, including a separate "invoiced" status. The order number property is used for the invoice number.

See this webinar by Commerce Guys for a in-depth look at Commerce Billy.

Mobilizer

Component type

module

Maintenance status

Development status

Downloads

9224

Component created

Component changed

Overview
Mobilizer provides a fast and easy way to create a mobile version of your Drupal 7 website no matter how large or complex it is today. Mobilizer’s easy-to-use GUI makes it simple to customize the layout, add color scheme and prioritize content for a more appealing mobile look.

How it works

Apache Screen

Component type

module

Categories

Maintenance status

Development status

Component created

Component changed

Mark paths as accessible internal-only--a tool for configuring apache.

This module writes out Apache htaccess configurations to automatically redirect site visitors based on their IP address.

Inline Conditions

Component type

module

Categories

RDF

Maintenance status

Development status

Downloads

81702

Component created

Component changed

This module allows conditions to be defined on the entity add / edit form, and
 those conditions are later mapped to rules conditions when the rule is generated.

Inline Conditions are specially defined (hook_inline_condition_info()) and
 consist of a configure callback (provides a user-facing form) and a build
callback (adds the actual condition to the rule).


Integration consists of creating a field of the "inline_conditions" type on the
 entity, and later calling inline_conditions_build() from the implementation 
of hook_default_rules_configuration().