Actively maintained

WorldPay Business integration for the Drupal Commerce payment and checkout system.

The module implements WorldPay's Payment Response/Notification system which allows Commerce to update the order status as well as serve the Shopper response for the success and cancel result pages.

Security

WorldPay's MAC Sig and callback password are fully supported and WorldPay's communication can be done securely over SSL (recomended for protecting the callback password. Note an SSL certificate is not required) while still allowing your users to return to a non-ssl version of the site.

Theming

The payment notification shopper response pages are theme-able using templates.
It comes with a set of sample WorldPay pages files that roughly implements the look of Drupal's Bartik theme for a relatively consistent look throughout the checkout process when using Bartik for the site's theme. See the README.txt file in the "worldpay page example" folder for further details on usage.

Worldpay accounts

For more information on how to setup a worldpay business account please have a look at www.worldpay.com

The Commerce Paypoint module integrates Paypoint.net's payment services with Drupal Commerce.

Feeds Tamper provides a small plugin architecture for Feeds to modify data before it gets saved. Several plugins are available by default and are described in the examples section below. Additional plugins can be added in separate modules or through the issue queue.

This module adds the "Git instructions" tab to certain pages on Drupal.org. This includes modules, themes and installation profiles.

This module provides a new Processor for the Feeds module. It allows for the consumption of Atom/NodeRDF feeds generated by the Views Atom module.

That's right, this pair of modules allows for full node replication between Drupal sites over Atom!

There is no mapping table for received fields. Rather, CCK fields and taxonomy terms present in nodes represented in the incoming feed will be mapped to identically named CCK fields and taxonomy terms on the receiving side. Fields that are not present will be ignored.

That is, if you are receiving a node with a field named "field_bob", and the node type you've selected to save to in the Feeds configuration has a "field_bob" on it, it will be populated identically to the remote node. If not, that incoming field will be ignored.

File transfer is also supported! The Feeds Atom module will call back to the original site and download files stored in a filefield field as needed. There is also duplicate checking so that an incoming file that is repeated multiple times will only be downloaded and stored once, and then referenced multiple times. Hook-based implementation allows for additional processing to be added by 3rd party modules.

This module provides two Views plugins: An Atom style plugin and a custom NodeRDF row style plugin. Although intended to be used together they should work independently of each other, too.

The Atom style plugin is an alternate Feed-type plugin that generates an Atom feed rather than RSS feed. It only works with the "Feed" display type. It does use row configuration, but only to allow the site administrator to customize the fields that will populate the various fields of the atom feed itself. Each record will be wrapped in an atom

element. If the PuSH Hub module is installed, the Atom feed will also be Pubshubhubbub-enabled.

The RDF (Node) row style plugin generates a standard XML representation of any arbitrary node, including attached CCK fields and taxonomy terms. Hooks allow for additional data to be injected into the XML, although you really should just be using fields. :-) The XML format itself is custom and documented in the drupal_node.xml file, but is wrapped in RDF tags to allow for later revision into more standard RDF vocabularies.

Rules integration allows Atom Views to be rendered at arbitrary times and syndicated using PuSH Hub.