I see some posts in this forum regarding recurring subscriptions and it *sounds* like that was something that you (Scott) were going to work on once they raised the money to do it.  It also appears as if enough people offered to contribute to the cause.

Just curious where this stands, if it will happen, when it will happen if so, etc.

The threads I was following:

http://www.ventrian.com/Support/ProductForums/tabid/118/forumid/14/postid/19673/view/topic/tpage/3/Default.aspx

http://www.ventrian.com/Support/ProductForums/tabid/118/forumid/14/postid/24971/view/topic/Default.aspx

Thanks!

Sweet!  I'm glad to hear that Scott, you rock!

Apologize for the repeat follow-up, but just trying to see if there is an ETA on this.  I need this functionality by the end of the month and will need to modify your source and add it myself (unfortunately invalidating any future updates from you because I wouldn't be compatible any more) to get it if it won't otherwise be available.

What with Christmas and all (and the increased complexity adding such functionality), it probably is safe to assume it won't be available, but I just wanted to get it straight from you so I can take the necessary action otherwise.

Thanks in advance, and I totally understand if this won't be happening sooner than later.

Unfortunately I just couldn't wait.  I ended up trying initially to modify his source but had some issues getting it imported into VS2k5 so I have created a project from scratch (scratch is relative, I've been looking at his stuff for a template, mostly on the UI and database structure) using .NET 2.0 and C#.  I have added the ability to map more than one role to a subscription plan, recurring subscriptions, and some other changes ($0 plan doesn't try sending to PayPal, for example).  I'm also adding an "unsubscribe" (or cancel) feature for the recurring which will take user to a comments section so they can provide feedback why they are cancelling but that won't be needed immediately so I am putting that on the back-burner while I get the core functionality all working.

It is *almost* finished and launched, I'm just doing some final testing on it.  I would have loved to be able to use his stuff but time was of the essence.

I'll have to check with Scott on his policy on things... except for some of the UI and portions of the database structure, I have essentially rebuilt this module from the ground up.  I have plans on changing even what little is still similar to his module when I get the chance, I just needed to get something up sooner than later so I used his UI as a template.

Part of his license agreement (which may or may not apply in this situation -- need some clarification Scott) states that I cannot redistribute the module to other developers or administrators.  Technically this is no longer the same module as the one which I have purchased through my subscription and his license agreement does not talk about modifications or derivative works and their redistributability so this is some gray area that needs to be made more clear. 

I don't want to step on his toes but in the end his product didn't deliver what I needed so I had to build my own version of it.

Possibilities:

• I already have a couple modules that I created and maintain, have for sale on SnowCovered -- this could possibly be added to them if it is not in violation of Scott's license agreement (even being a separate product, I have initially used his code as a template).
• Put it up for people to use just because I'm nice (again, this could have some repercussions based on the license agreement, so this would need clarification)
• Send to Scott out of the goodness of my heart and let him rebuild his module using my modifications.
• Other?

So I really don't know.

Scott,

Here's what I'll do -- I really don't want to step on your toes and I don't want to create problems so when I finish up my changes I'm going to email you a copy of the source.  I'll let you determine how similar or not it is and what course of action you want to take.  My development methodology is VERY different from your own so I don't think my changes would be "easily" implemented into your own module, it would take a little work. 

I didn't change anything re: providers... I probably will in the future when I have "spare" time to dedicate, but my requirements needed PayPal and that was all right now.  The control structure currently is pretty much the same because I needed to spit something out sooner than later, though I had some notes about how things would change when I got the chance to do so.  It still uses receipts (I prefer the terminology "invoice") and I haven't created the reminder system yet but I liked that feature as well so planned on having the reminders in there.  They would send "x" days before a recurring subscription was set to renew or "x" days before a non-recurring is going to need renewal.

I probably will have it "ready" by this time next week and send you a copy of my code.

Thanks,

Fooberichu

We also need to give our members the ability to choose auto-renewal of their subscriptions (or to enable that ourselves). Any prediction on when this feature would be added to the otherwise wonderful module?

It is precisely this lack of feedback and support by Scott (in regard to this module) that led me to have to develop my own version of it.  I have been testing it live with a client for a little under a month now and after I get a few additions into it I plan on releasing my own version of it on SnowCovered.  I have seen it mentioned in the forums that his baby seems to be the "Property Agent" and that is just fine if he wants to pick a module as his champion, but completely ignoring this module isn't exactly good business.

I would much rathered NOT have written my own version that will compete directly with his product but the fact that these requests have been there since June of 06 (maybe earlier?) and he just ignores them... well... not cool.

Subscription tools was developed for the ventrian site to manage subscriptions. It was then offered to other users at the same time. I have not been "ignoring" the module, but besides recurring subscriptions, this is the only major feature missing. In fact, I did use the core subscriptions which were "recurring" and found them problematic to billing as people often forgot the subscription was still active so I opted for the non-recurring model.

The sometimes abusive emails that I have received over this module have to stop, I offer modules at a reasonable price and I add features over time. When I focus on another module, I am often criticised for spending too much time on it, sometimes it's a lose-lose scenario.

I apologize for the previous comments and appreciate your feedback and explanation to us.  I also apologize for the assumption I made that since people were willing to pay to sponsor the changes that those changes would be put into a higher priority slot.