Actively maintained

A transport layer for Drupal-to-Drupal data, which aims to provide a common base on which to build services-based applications between Drupal sites.

In (reasonably) plain English:

• with Services, you can make XMLRPC calls to a remote Drupal site and get back data, provided you first connect, log in, and pass keys and hashes and tokens and so on in ever call.
• with Clients, you can just make a remote method call of, say, 'node.load' with a parameter of X and get back data, much like calling a normal function; all the complex stuff with Services is done for you.
• with Transport, you need only say 'get me node X from Client Y', and you not only get the node, but the user who authored it, its attached files, taxonomy terms, and comments (well the last two are TODO, but that's a minor point). Transport does the work of calling the right methods, figuring out dependencies, saving everything it retrieves, and maintaining a record of correspondences between local and remote object IDs. Transport can work with multiple remote sites, and is agnostic of Drupal version: Transport on a Drupal 6 site can retrieve nodes from either a Drupal 5 or 6 site.

The idea behind this project is to follow the great example of Examples module, but for

The Node Ownership module provides an ability for users to claim an ownership of the node.

This module will provide for the ability to you to create invoices and send them via email to allow payment via the payment methods you have on your e-Commerce installation.

This module is an replacement for the Cookie Cache Bypass module that is a part of the Drupal 6 Pressflow distribution.

The purpose of the module is to set a short-lived NO_CACHE cookie on form submissions so that when using a reverse-proxy (such as Varnish) you could be certain that your site visitors would get dynamic pages after form submissions.

This module performs the same function, but adds some customizations for users.

1. Rather than taking the minimum cache lifetime and adding 300 seconds to it as the lifetime for the NO_CACHE cookie (this could be anywhere from 10 minutes to 1 day + 5 minutes) we allow the user to set the time they would like that cookie to persist for.
2. Rather than setting the cookie path for / (the entire site) we allow users to choose to set for / or the value of request_uri() followed by a trailing slash. This means that if your form is at URL /foo and your post-form pages are always /foo/something-else, then this setting will increase your cache hits. See http://php.net/setcookie and read the information on the 'path' parameter for more information.

Plans module or Product Plans is simply used to store and display different plans, offers or packages of your product, what ever you call them.