Модули
Exports Webform data to Triple-S format (survey interchange standard).
Variations of the Mind Games theme for use in different contexts
This module adds the rules event to send formatted e-mail message to CRM Contacts.
The form of the mail parameters has some UI improvements.
The module is merged with Shield!
Sendgrid is a transactional email service that is used by several large companies to handle delivery of messages.
Some experimental code to extend top_searches.module.
uc_client
View mode field let's you refer to view modes through a field. It then provides a Panels content pane that let's you render an entity using the selected view mode in the field.
Note
This is a placeholder for the project which will be committed after massive code clean up.
Introduction
This module combine two tools:
OVERVIEW
This small module provides a possibility to disapprove comment by adding a "disapprove" link (same as "approve" link, but oposite). Views integration is also provided.
Provides integration between Party and
"Text Format Access" provides an ability to configure global or per-role access to text formats of particular field.
This is a very simple project created to extend Aegir frontend features. It adds a button to access one time only to a website and perform maintenance on it.
Downloads instagram media by tag(s) on cron run or manually, stores them in local database. Administrator has a possibility to manage downloaded media.
This module adds Masonry for Panels style.
Why Masonry?
When you have multiple arbitrary size block contents in the Panel region, Masonry optimizes layout of these contents within a display area of a specific width. The program acts like a good tetris player arranging blocks. By proper implementation, you can effectively maximize the number of arbitrary size contents that can be shown within the specific display area.
It is useful in any one or more of these circumstances:
- Each content is of different block size.
- Each content block size change dynamically.
- Display area is small, or with arbitrary resolution. (e.g. display in mobile devices), and you want to maximize the space used for display, dynamically.
- You do not want (or lazy) to fix the layout in the panel.
This module expands upon the Commerce Paypal module that Website Payments Standard and Website Payments Pro, by providing an option for
Allows you to take cell phone numbers and updates Amazon's SMS with the phone number provided to a pre-configured topic.
Requires Amazon Web Services account.
Overview
Date Reminder allows a registered user to request an email reminder to be sent at a specified time before an event. Generally these would be calendar events, but any node type that has a CCK datetime can support reminders.
Features
- When reminders are enabled for a node, registered users (with the appropriate privilege) can request reminders to be sent before each occurrence of the date/time. The user specifies how long before the date/time to send the reminder.
- When reminders are enabled for a node type, anyone who can edit the node can enable or disable reminders for that node.
- Reminders are sent using the Messaging system. The usual reminder method is email, but other messaging transports should work. (Well, not Drupal 7. The Drupal 7 version just uses straight email.)
-
System administrator can control:
- Which node types allow reminders, and which date field (if there are several) in a type to use as the basis of reminders.
- Which (registered) users can request reminders.
- Which users can request reminders to arbitrary email addresses instead of their own.
- Which users can see or administer other users' reminders.
- Content of reminder messages.
- If and how long reminders should be kept after last date occurrence.
- The list of allowed lead times for reminders from which users can select.
An effort is under way to move much of the documentation here to the Date Reminder section of the Site Builders Guide. Currently that document is very incomplete, but watch there. Information on this module page will gradually be moving there.
Summary
This module allows seamless redirection between viewing content on a public-facing website and editing it on a separate, centralized administrative site. It is designed for use with the Deployment and Universally Unique ID modules, as part of a comprehensive content-staging solution.
The simplest functionality it provides is for an administrator browsing the public-facing site ("Viewing Site") and clicking a standard "edit" link on their content to be automatically transported to the correct page on the administrative site ("Editing Site") at which that content is edited.
It has additional flexibility, however; it can be configured to perform similar redirects for any Drupal entity (e.g., taxonomy terms and users, rather than just node content) and for any path associated with that entity (not just the standard /edit path). It also has support for redirecting only certain "bundles" (e.g., node types); for example, if your use case requires Page nodes to be edited on the Editing Site site but not Article nodes, you can configure the module to only redirect edit links for Page nodes but leave the Article nodes alone.
