recurring

Hi everybody.

I'm currently trying to implement a subscription system that allows users to gain access to all content tagged under a certain category. My first thought was to do role-granting, but there will be at least 10-20 categories, and that would simply be cumbersome.

In addition to category subscriptions, I'd also like to do per-user subscriptions-- so if you like what Bob Smith has written, you can buy a monthly recurring subscription to his posts for $x.xx.

Hello there!
I´ve recently installed ecommerce, and frankly I think it´s just too much for what I need. It seems far too complex. But as I need a good, solid, stable module that can manage recurring payments and scheduled reminders (and only that), using eC seemed the obvious thing to do. :)

We administrate online courses in a Drupal Platform, and the student´s payments are manually managed outside Drupal.
We have courses that can be paid in two or three (monthy) times.

Hi,

im trying to implement module ec_autoplay to module ec_recurring which will work with module Worldpay and FuturePay. I need recurring
products which are automatically refreshed to be sold as membership products. Here are my ideas:

Not too long ago, Google announced FREE processing of your Google Checkout sales until the end of 2007. That's right - more than a year's worth of free processing!

From now through December 31, 2007, you can process Checkout transactions for free, even if you aren't an AdWords advertiser. If you're already an AdWords advertiser, you can process your Checkout transactions for free regardless of your AdWords spend.

This potentially affects folks who use Drupal's ecommerce and advertising modules. Wouldn't you like to use Google Checkout (GC) for your Drupal web site(s)? Before that's possible, we need someone to create a module. Unfortunately, GC currently works ONLY in the United States. Regardless, I'd like to see a developer step up and write a membership subscriptions-based, recurring credit card charges capable module and I'd be willing to make a small financial contribution. Here's a short GC video demo, but please read on for more info.

UPDATE (Jan 11): Code has been moved from the sandbox to ecommerce CVS pending full integration with the ecommerce system. I'm currently writing upgrade code to move products and the transaction records over to the new format. NOTE: If you are migrating custom solutions you will need to take special care with the upgrade. You may need to manually update the schema revision field in the system table to skip the upgrade and apply your own code instead.

Once the upgrade code is complete i'll be removing the old code from ecommerce. After this i'll send a mail to the ecommerce list to ask for testers.

You can get a copy of the alpha code by using the CVS tag DRUPAL-4-7--3. Alternatively download the tarball.

UPDATE (Oct 12): Thank you to the financial contributors. Code for all modules is now available in my sandbox. Please keep in mind that the code is still in beta and no upgrade code is available for you to upgrade your current 4.7 sites. It is not recommended that you use this code in production. Please post all issues to the Drupal issue queue and it would be very handy if you provided patches. I'd like to get hold of some anonymized production databases using the 4.7 default recurring product system. It'll help me build the upgrade code.

UPDATE (Sep 30): Still waiting on financial contributors. The ec_anon module is ready for trialling. It's available in my sandbox.

UPDATE (Sep 22): I'm excited to announce ec_recurring, ec_roles and ec_mail modules are ready for testing. There is a slight delay on ec_useracc due to some extra feature requirements on EC. That should be available very soon. Financial contributors please forward your second instalment and contact me to obtain code.

UPDATE (Sep 04): Feature Freeze in effect as of September 4, 2006. No more features will be added.
Scheduled UAT date: September 22, 2006. Scheduled completion date: September 30, 2006.

Hi everyone,

I've just finished writing up a specification document from which developers can see what is planned for E-commerce in relation to subscriptions, roles and user accounts being manipulated during checkout. These are highly sought after requirements and many people are scratching their own itch scratch scratch. My aim, though providing a specification document, is twofold. First, I want to make sure everyone knows what we're developing for 4.7 and then for 5.0 (after we do some major changes to E-Commerce core). Second, it provides a solid reference for any developer planning to write anything.