Can you tell a green field from a cold steel rail? A smile from a veil?
Do you think you can tell?
New Drupal Modules
This module integrates MangoPay with Funds submodule of Commerce Marketplace project.Intro
This module fully integrates Commerce Marketplace Funds with MangoPay Payments.
It supports deposit, transfer, payment and withdraw transactions.
MangoPay transactions are duplicated on Drupal database for making things
faster, but queries are made to MangoPay to validate local data before doing
sensitive operations like transfers or payments.
The module provides two new Commerce Payment Methods:
- MangoPay Payment Method
This is an offsite payment method which redirects the user to MangoPay
for handling the payment.
Once the user makes an offsite payment, her credit card information is saved
in MangoPay, and she'll be able to use One Click Payments for her later
orders. To make this possible, the module asks MangoPay to make a
contribution transaction from the user credit cart to her (newly created)
MangoPay e-wallet and then transfers the money from the e-wallet to the
website e-wallet when she's redirected back to the website from MangoPay.
- MangoPay One Click Payment
Once the user has made a payment using the offsite MangoPay Payment Method,
She'll be able to utilize One Click Payments by selecting one of her credit
cards that MangoPay has saved in her previous offsite payments. This time,
the module asks MangoPay to charge the customer credit card and transfer the
money directly to the website's MangoPay account.
MangoPay needs Email, First name, Last name, Nationality, and Person type to
create new e-wallets for users. Therefore, this module adds the following
fields to Marketplace Funds Account owner entity types (e.g. user and
commerce_store entity types by default):
It also adds `mango_user_id' field to the Marketplace Funds Account entity type
To keep track of MangoPay transactions in Drupal, we save payer (originator) and
beneficiary (destination) account ids on transactions in `payer_id' and
`beneficiary_id' fields on the Marketplace Funds Transaction entities.
To handle withdraw requests, the module creates a new Funds Withdraw Method
bundle, named 'MangoPay', with the following fields:
When the Funds Account owner creates her instance of this withdraw method,
A request is made to MangoPay to register this withdraw method for her and
saves the withdraw method id in `mango_beneficiary_id' field which is used
later for creating Commerce Marketplace Funds Withdraw Transactions.
Funds Withdraw Transactions are created in Pending status and are not sent to
MangoPay until their status is changed to "Success". You can do this manually,
or using Rules Scheduler to process withdraw requests at predefined time periods
Module configuration form can be found at admin/commerce/mangopay.
If you already have a MangoPay e-wallet that you want to use with this module,
check "I have a Mangopay account" checkbox and enter your MangoPay User ID and
Wallet ID. Otherwise enter your first name, last name, email address and person
type and the module will create a MangoPay account and e-wallet for you which
will be used as the master account for the marketplace.
The YouTube Connect module allows you to add your youtube user name and you'll get a page with playlist listing.
This enables content from social media websites to be imported as nodes.
Content can be pulled from the following sites:
Tweets can be pulled from a user account and/or hashtag. The OAuth module is a dependency in order to authenticate with Twitter.
Instagram posts can be pulled from a user account and/or hashtag.
Facebook posts can be pulled from a Facebook page.
These are all separated into individual modules within the project so you can just enable the ones that you want to use.
Sponsored by Catch Digital.
Generates customizeable and themeable Views to expose information about site architecture. Similar to the Architecture module but taking a Views-based approach that offers all the power of Views' UI.
Many thanks to becw for code review and help.
Das "PaX content" Modul ist für PaX Händler bestimmt die Inhalte des Herstellers PaX auf ihrer eigenen Internetseite einbinden wollen.
Das Modul ruft verschiedenste Inhalte rund um die Themen Fenster und Türen von einer entsprechenden Schnittstelle, die PaX bereitstellt, ab und gibt diese unter einer eigenen Adresse aus (z.B. www. ihreseite.de/pax-fenster).
Aktualisierungen / Optimierungen der Inhalte werden automatisch über die Schnittstelle erledigt. Bei neuen Inhalten wird entsprechend eine Meldung ausgegeben. Alle verfügbaren Inhalte können von Ihnen selbst gezielt aktiviert / deaktiviert werden.
Zur Nutzung muss ein API Schlüssel in den Einstellungen des Moduls hinterlegt werden, den Sie als PaX Händler über Ihren MyPaX Zugang beziehen können.
Weitere Infos zu PaX gibt es unter www.pax.de
This project creates a content type out of users. Every time a user gets added, updated or deleted, the user-node also gets updated.
Instead of showing a standard "404 Page not found", this module
shows a childfocus missing poster
The Restricted Node Display module allows you to replace the "Full content" view mode for one or more content types with another view mode. This change is controlled by a Drupal permission allowing you to, for example, display "full content" to registered site users but only "teaser" content to anonymous users.Documentation
See the README.txt file in the module for configuration instructions.Future enhancements
- #2071567: Allow restriction to be set for individual nodes
- #2071609: Display login form to anonymous users
- #2071615: Administration interface for defaults configuration variables
This module was sponsored by Digital Garden Web Design Sydney.
Don't use the sandbox, just use this.projects[socialitejs][type] = "module"
projects[socialitejs][download][type] = "git"
projects[socialitejs][download][url] = "http://git.drupal.org/project/socialitejs.git"
projects[socialitejs][download][branch] = "7.x-1.x"
projects[socialitejs][patch] = https://drupal.org/files/Support_for_Display_Suite-1816514.patch
projects[socialitejs][patch] = https://drupal.org/files/socialitejs-2065883-checkbox-3.patch
projects[socialitejs][patch] = https://drupal.org/files/socialiatejs-2065889-socialite.min_.js_.patch
projects[socialitejs][patch] = https://drupal.org/files/socialitejs-1838560-block_display.patch
projects[socialitejs][patch] = https://drupal.org/files/socialiatejs-2065893-coding_standards.patch ; Socialite.js
libraries[socialitejs][download][type] = get
libraries[socialitejs][download][url] = https://raw.github.com/dbushell/Socialite/master/socialite.min.js
libraries[socialitejs][directory_name] = socialitejs
libraries[socialitejs][destination] = libraries
libraries[socialitejs][filename] = socialite.js
Provides a new Gittip giving field type to help organizations that want to allow their members to contribute or decide Gittips that get rolled up and donated through the organization's funds. Basically this allows you to implement the Khan Academy grant model on your Drupal intranet site.Set-up
Add a new Gittip giving field by adding this field to user account on admin/config/people/accounts/fields, adding your organization's Gittip username and API key to the field.
You can also set a maximum amount that each 'value' of the field can donate, so you can limit each person to $5 in Gittips.
This is the administrative centre of WetKit based heavily on the work done in Panopoly Admin.
- Customized Content Editing Experience
- Custom Style for the Media Browser
- Creates WetKit Administrative Section (admin/wetkit) for WetKit Configuration
- Provides Pane Library, Layout Library, and Page Library Administrative Pages
- Packages Several Different Administrative Toolbar Options (Admin Menu, Admin, Navbar, Toolbar)
This module provides convenient default on node translation forms. It is only useful if you have a hierarchical menu, and the menu is maintained properly in the site's default language.
When a new translation node is created, it checks the default language, crawls the menu structure, and finds the plid that your new node should likely have. The user is able to change it, but since users often overlook menu settings this module can help keep menus maintained properly.
Requires: menu_nodeNot supported in any way
The code is currently just a prototype, should be considered untested, and makes the following assumptions:
Provides a backport of the new caption filter in Drupal 8.
Will also look to integrate with the Media module as well.
Delivers an email that contains an entire node's content.
As an alternative, this can be accomplished by creating an email and entering field tokens, but when you have a massive amount of fields, this can get redundant. This module adds a drupal_mail hook to send a rendered node via email. This also provides a rules action to send node content via email.