Integrates Drupal Commerce and MoIP, a payment services provider from Brazil, with a high level API and an easy to use interface, enabling an out-of-box solution for payments with e-commerce in Bra
The module comes with an integration to PhantomJS which allows you to take screenshots or PDFs of a URL.
The module comes with an administration interface that allows you to configure the location of PhantomJS and a default destination folder. It also has a test function to test if your configuration works. PhantomJS works by giving phantom an JavaScript file that tells phantom what to do and this module comes with a default JavaScript file that renders full HD size screenshots.
For more information about PhantomJS possibilities you should look at the wiki pages and the examples that comes with PhantomJS.
Usages
To use this module in your code the phantomjs_capture_screen can be called after you have saved its configuration.
The $url is the page to capture and the $dest is an URI to where the image should be stored and the $filename to store it under.
This is a supplementary module to the Calendar, Date and Date Repeat modules. It allows users to own and manage their own calendars, and provides a UI for managing complicated date repeat patterns.
Core concepts
Dates as Entities
A core concept presented in this module suite is "Dates as entities." The dates as entities are referred to "Date sets," and are managed from a user-specific calendar-based UI. An administrative user can create numerous "date set" bundles, which can each have their own fields. The end users then place "date sets" onto their calendars. Each new "date set" bundle automatically has fields attached that help sort the instance onto one or more schedules, and into "repeating patterns." The date sets then utilize entity view modes on the calendar output.
Repeating Patterns as Entities
The Date Repeat module provides a Date Repeat UI for managing a repeating date field. This module provides a Date Repeat UI that manages numerous entity instances that can each be of different bundles. It pulls the pattern out of a field formatter and puts into its own entity. The pattern has a title, is fieldable, and integrates with a user's schedule.
Drupal utilizes draggable tables to handle multiple value forms. It's quite convenient for most simple field types. However, for complex field types such form can be cumbersome.