subscriptions

I'm looking to build a simple subscriptions Drupal 7 site. The basic requirement is be able to buy a couple different products and then get recurring payments for the user on a month by month basis OR quarterly OR bi-annually OR annually. Ideally, I'd like some Rules integration but I can probably add this myself too.

Overview
Many publishers and media companies have shifted their Websites to Drupal. This DrupalCampNYC8 session explores why this is the case by examining current and future trends. We will present several case studies and host an open discussion about workflow tools, popular contributed modules, mobile publishing, and techniques for monetizing content, all of which are helping publishers rethink their businesses. From workflow management, multiplatform publishing, and subscription payments, to video integration, social media integration, and user generated content, this session will focus on how publishers and media companies are using Drupal to invite wider audience participation and ultimately improving their bottom line.

I would like to hear what mailing list solutions you use and how you integrate them with your Drupal site for subscription management (subscribe, unsubscribe) and distribution (content creation? list management?).

Please comment on how you are invoking email notifications, in general and for taxonomy subscriptions. Does anyone see a problem with workflow and drupal access model and/or 3rd party modules that supply that type of functionality?

With workflow, the natural point at which an announcement notification message should be sent is when the content changes to a certain workflow state -- e.g. "Posted". And the tools I see available for this task range from "send a tokenized email to a role" via the Token module (token_action.module) to the Subscriptions module.

Hi all. We're in the final stages of developing TheDigitel.com, a local news site, and I'm trying to decide on the best avenue to integrate e-mail and SMS subscriptions. Before I go installing a bunch on the test server, I thought I'd ask for your thoughts.

Ideally, we want to offer people the ability to subscribe to a daily or weekly digest (perhaps based of our RSS feed), or to subscribe to a particular topic (i.e. e-mail me when there's a new story tagged with "road development") or to say SMS me when there's a new top story or story tagged with "wreck".

After 3 months of intense work... I'm proud to announce first stable release of Organic Groups Subscriptions ! now available.

Special thanks to gustav, he is a wonderful mentor and project lead.

Hope you enjoy it...

Blessings!

Week one of Google SoC 2007 is already over and I'm off to a great start of my SMS Framework project. I've begun developing the gateway side of the API. I've designed it so that additional gateways can be created and install like standard modules. Gatway modules implement hook_smsframework_info(), which returns an array containing information about the gateway(s) the module enables. The information includes the gateway's name, callbacks (for validation, sending, ect.), and a form for configuration.

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:

I maintain the signup.module. This module has long struggled with the problem of how to flexibly define what fields are requested and/or required when a user signs up for something. I might have a slick solution, but I'm not sure if CCK can accomplish what I have in mind.

With 5.x CCK, you can assign any fields you want in whatever groups you need to any node type. My module could allow site admins to define the signup/reply form for any given node type as a specific group of arbitrary CCK fields. This field group would not show up on the node edit form. It would be displayed on the node view page itself, so each user could fill-in, submit, and optionally edit their own signup/reply. All fields would automatically be treated as "multiples" in terms of storage, 1 set of each field's values per user who replies, but displayed as single values for any given user viewing the node. When a user replies, the values of any fields in their reply would have to be associated with their identity (uid for auth users, email for anon).

Hallo Leute!

Ich bin hier mal wieder auf der Suche nach einer passen Lösung für Österreich.

Szenario:

• Abo-Verkauf mit regelmässigen Kreditkartenzahlungen
• Produkte sollen als Custom Node Module oder CCK gebaut, aber mit dem Cart von eCommerce3 verkauft werden

Ich weiß, dass eCommerce recurring products kann, aber es bis zur V3 noch immer nicht geschafft hat
mit einem Merchant-Account automatische Kreditkartencharges zu machen.

Das Argument, dass man die Kartennummern nicht speichern will ist ein schwaches Scheinargutment, weil das bei den meisten Anbietern