http://drupal.org/project/commerce_mailchimp
old info:
Integrates MailChimp into the Drupal Commerce checkout process.
Commerce Mailchimp Checkout pane
This sandbox will contain some examples of how to use the api of the AddThis module (4.x and up)
Fork of 7.x-dev filefield podcaster needs to be able to parse link fields to create an enclosure, instead of filefields...
Adds Ubercart Attribute options for node import.
I originally built this for some immediate needs. When I was using this module on the project for which I created it, it was working great. It's definitely not production-ready, so be sure to perform a database backup before using it!
I've moved to Drupal 7 for all development and have moved to Drupal Commerce. That said, I'd be happy to help with any minor tweaks, bugfixes, etc., but I won't be able to devote much time to this module.
This module makes Login Toboggan user moderation a little easier for administrators.
This module updates the logintoboggan_register_pending_approval_admin email to include an "approve / reject" link for the new account that is pending approval. This link will take the administrator to a new "Moderate" tab on the user's page. You can get to this tab if you have the appropriate permissions. On this page there is a simple set of buttons to either Approve or Reject the user account.
Store entities created within different Drupal instances of a same project to ensure that their IDs will be uniques and permit the download of the content (add/update).
This server module is actually developped to handle the "Term" entity type first cause the taxonomy could often be structurant for a project, Views can be build on certain terms, etc. Developpement for other types of entities will be possible.
The Drupal instance will send is content via the "Entity client" (entity_client) module.
Note: As of 15-01-2014, this module appears to no longer be supported. If you are interested in taking this module over, please reply to the issue.
This module makes a flag only usable on one node (for each user). Think of having a node flagged as a "default."
I originally wrote the module because there are so many good modules that use the Flag module's API, and I needed a way for users to "set a default research point."
The module may not be production-ready, so please look over the code before implementing it.
When an entity is created, a server (Drupal with "entity_server" installed on it) will be ask for a unique ID and the entity itself will be send. Locally, the entity will be delete and recreate with the new unique ID.
Work only for "Term" entity type.
This module builds a form for toggling flags on nodes in bulk.
This code is probably not production-ready, so use with caution. I'm posting the code because maybe the ideas/code within will help others with similar needs.
Note: I'm posting this project long after I wrote the code, which is provided mainly for reference purposes. I've undoubtedly learned better ways to do things in Drupal/PHP since writing this code, but I do not intend to update/modify this code unless I have specific requests to do so.
