This CVS mess of branching and whatnot is totally confusing. I want to create a release that can be downloaded but I don't want it to look like it's a stable release that could be used in production. And how do I delete releases? I need someone to help me with this--please! =)
Please post a link here with some intro text explaining your concerns about your module not being a stable release, etc. ... I saw your earlier threads on this topic and am very interested in trying it out.
---------------------------------------------------------------------- http://www.bwv810.com/
I am a writer and researcher. In my spare time I build websites with Drupal.
Je peux communiquer en français. / Я могу общаться на русском языке.
Well there seeing as how I just launched it tonight and authorize.net lib is being funky and it just isn't ready yet. It needs to be tested and there's still some features needed to be added. You could certainly take it and make you own adjustments to it I suppose but considering that it involves taking ppl's money I've got to be sure it's ready before I start releasing major releases. I'm still figuring out drupal CVS which is what I really need help with.
I released a major version then realized that isn't what I wanted to do so I made it unavailable. I am going to have a webmaster delete it and then I'll delete the tag.
I was confused for a while bc a download link wasn't showing up for role_subscription 5.x-1.x-dev in "view all releases" but now it's there. It took a while for the drupal job to create that package, I thought I had done something wrong.
Now here's what I need help with. I thought I did everything right for "role_subscription 5.x-1.x-dev" but how do I make that the default release that shows on the project page in red with the little x by it? I don't see my dev version in "administer releases" - why is it not there? Somebody help!
I have already made some significant changes including adding a user subscription history but also a lot of bug fixes and I had to change out the Authorize.net SOAP library with a regular XML library unfortunately bc PHP 5 SOAP was having issues with their code. Anyways that could be swapped out again later if need be. My first priority was to get it to actually work. It does mean the authorize engine is a little more "light-weight".
I spent a lot of time today cleaning up the payment screens, making them look a little more like some of the ubercart screens which are sharp. I fixed a critical bug on the update payment screen.
A big thing and also surprisingly easy thing was adding SSL support thanks to the secure pages module. I now require the module as a dependency and all you have to do to get the payment pages to redirect to https is add the pattern "role_subscription*" - easy! And I've tested it locally and on our development server and it works great.
So now conceivably all the parts are there that it could go into production tho I still think it's too early. But now with SSL support, the updated (working) Authorize ARB library and all the features I wanted except for role subscription history which I will add soon, it's ab ready to go. I still have much to test again since changing back end libraries but it's coming along people!
I will endorse it's use in production after I've used it in production myself for a few months and worked out the kinks. The main thing I'm trying to do is add as many auditing tools to the application as possible. There will be times when things go awry so I want all issues traceable if possible. I will only endorse use of the module at first for developers who know how to troubleshoot code and know mysql. Maybe next year if it's been stable for a while I could endorse non-technical ppl to be able to use it if there's always a path for fixing a subscription through drupal without having to touch code or the database. The biggest thing are going to be timeouts in the API calls to authorize or other payment engines.
I might have a look at it, I probably won't branch it to 6 until I've got a stable version bc I don't want to have to keep up with a bunch of different versions. I don't know yet what all has to change to make it 6 compliant. I would prefer someone take that ball and run with it but we'll see. Now that 6 is stable I'll probably start creating sites with it and thus give me the motivation to upgrade the module to 6. So I guess my take is wait and see =)
I am revamping the payment screens to look pretty sexy and easier to use. We had a designer come up with some mockups. The mockups he did included some design specific to our website but I'm going to try to integrate some of the design as the basic style for the module. Hopefully we can get the official release of this module out this year. Wish me luck -J
Sounds like a great module, and I believe I'll be trying it out soon. I do hope you're going to use theme_something functions when you re-vamp the payment screens. Shout if you need help with that.
after working several days on it i came to the conclusion that my implementation of integrating the user registration and/or user login to the role subscription workflow was so different and jquery dependent that i would have to put that piece in my phptemplate template functions and pull the rest out into a separate module which i won't open source. That takes away what kind of sexiness I can add to the payment screens, however I will look at them and see what I put back that will still make the 'default' view look good. I also might add a default CSS files + a couple images that is easily modified for one's own purposes.
I wish drupal had a standard way of adding registration/or login to a workflow so that you could slap it on to any form or multi-form workflow but I haven't heard of any way of doing that so my solution for that includes embedded those forms in my template functions and using CSS + jquery to make it all look lovely but again it's not compatible enough with any theme to be able to throw it in my generic open source module.
And so I will leave the standard link that gives the user a way of registering and then returning to the workflow to complete the subscription process but of course that's just not as convenient bc you have to log back in vs my kind of hacky solution which lets you register and subscribe at the same time.
Maybe we need another module that let's you put an intermediary registration/login screen in between any workflow and stores the registration user id in the session so that you module can have the new user id even if the user has not logged in yet.
this is part of a larger website project so it's still in development but i've been spending time creating other custom modules for this project. this version is working but i don't feel comfortable with it being robust enough for a production environment yet, i hope to have a version out this year or early next year that is production ready.
if you notice I did update the dev tarball the other day. that is the version to download as the 1.0 version was a mis-fire by me as i didn't want to release a "stable" version but there was no way to undo it once i tagged a release as a stable release.
Recently I found out the ubercart now has authorize ARB support and somewhat integration with the recurring billing module. I found a thread discussing the same problem that have tried to solve with my own module:
Before I thought that it would be difficult to stretch ubercart's functionality with recurring billing (not invoicing) but with the recent revelation now I'm wondering if it would be better to use ubercart's recurring billing system with possibly a submodule for dealing with role promotion if I'm not entirely satisfied with it's default functionality.
It's definitely something I will research now, if it proves to be better to user ubercart then that would deprecate this module in my opinion. Ubercart has great functionality, I will need to test it's ability to handle recurring subscriptions.
Any thoughts out there? Feedback would be appreciated.
Comments
Alright first order of business
This CVS mess of branching and whatnot is totally confusing. I want to create a release that can be downloaded but I don't want it to look like it's a stable release that could be used in production. And how do I delete releases? I need someone to help me with this--please! =)
Please post a link here with
Please post a link here with some intro text explaining your concerns about your module not being a stable release, etc. ... I saw your earlier threads on this topic and am very interested in trying it out.
----------------------------------------------------------------------
http://www.bwv810.com/
I am a writer and researcher. In my spare time I build websites with Drupal.
Je peux communiquer en français. / Я могу общаться на русском языке.
OK
Well there seeing as how I just launched it tonight and authorize.net lib is being funky and it just isn't ready yet. It needs to be tested and there's still some features needed to be added. You could certainly take it and make you own adjustments to it I suppose but considering that it involves taking ppl's money I've got to be sure it's ready before I start releasing major releases. I'm still figuring out drupal CVS which is what I really need help with.
Alrighty here we go
I released a major version then realized that isn't what I wanted to do so I made it unavailable. I am going to have a webmaster delete it and then I'll delete the tag.
I was confused for a while bc a download link wasn't showing up for role_subscription 5.x-1.x-dev in "view all releases" but now it's there. It took a while for the drupal job to create that package, I thought I had done something wrong.
Now here's what I need help with. I thought I did everything right for "role_subscription 5.x-1.x-dev" but how do I make that the default release that shows on the project page in red with the little x by it? I don't see my dev version in "administer releases" - why is it not there? Somebody help!
http://drupal.org/project/role_subscription
Here's the project page: http://drupal.org/project/role_subscription
Changes on the way
I have already made some significant changes including adding a user subscription history but also a lot of bug fixes and I had to change out the Authorize.net SOAP library with a regular XML library unfortunately bc PHP 5 SOAP was having issues with their code. Anyways that could be swapped out again later if need be. My first priority was to get it to actually work. It does mean the authorize engine is a little more "light-weight".
SSL support people, and better looking payment pages!
I spent a lot of time today cleaning up the payment screens, making them look a little more like some of the ubercart screens which are sharp. I fixed a critical bug on the update payment screen.
A big thing and also surprisingly easy thing was adding SSL support thanks to the secure pages module. I now require the module as a dependency and all you have to do to get the payment pages to redirect to https is add the pattern "role_subscription*" - easy! And I've tested it locally and on our development server and it works great.
So now conceivably all the parts are there that it could go into production tho I still think it's too early. But now with SSL support, the updated (working) Authorize ARB library and all the features I wanted except for role subscription history which I will add soon, it's ab ready to go. I still have much to test again since changing back end libraries but it's coming along people!
I will endorse it's use in production after I've used it in production myself for a few months and worked out the kinks. The main thing I'm trying to do is add as many auditing tools to the application as possible. There will be times when things go awry so I want all issues traceable if possible. I will only endorse use of the module at first for developers who know how to troubleshoot code and know mysql. Maybe next year if it's been stable for a while I could endorse non-technical ppl to be able to use it if there's always a path for fixing a subscription through drupal without having to touch code or the database. The biggest thing are going to be timeouts in the API calls to authorize or other payment engines.
And there's my update, that's it for now.
can you make a version for
can you make a version for 6.x?
Well that all depends
I might have a look at it, I probably won't branch it to 6 until I've got a stable version bc I don't want to have to keep up with a bunch of different versions. I don't know yet what all has to change to make it 6 compliant. I would prefer someone take that ball and run with it but we'll see. Now that 6 is stable I'll probably start creating sites with it and thus give me the motivation to upgrade the module to 6. So I guess my take is wait and see =)
Payment screens are going to be revamped
I am revamping the payment screens to look pretty sexy and easier to use. We had a designer come up with some mockups. The mockups he did included some design specific to our website but I'm going to try to integrate some of the design as the basic style for the module. Hopefully we can get the official release of this module out this year. Wish me luck -J
Theme payment screens...
Sounds like a great module, and I believe I'll be trying it out soon. I do hope you're going to use theme_something functions when you re-vamp the payment screens. Shout if you need help with that.
Thx,
Rene
ok here's the tricky thing
after working several days on it i came to the conclusion that my implementation of integrating the user registration and/or user login to the role subscription workflow was so different and jquery dependent that i would have to put that piece in my phptemplate template functions and pull the rest out into a separate module which i won't open source. That takes away what kind of sexiness I can add to the payment screens, however I will look at them and see what I put back that will still make the 'default' view look good. I also might add a default CSS files + a couple images that is easily modified for one's own purposes.
I wish drupal had a standard way of adding registration/or login to a workflow so that you could slap it on to any form or multi-form workflow but I haven't heard of any way of doing that so my solution for that includes embedded those forms in my template functions and using CSS + jquery to make it all look lovely but again it's not compatible enough with any theme to be able to throw it in my generic open source module.
And so I will leave the standard link that gives the user a way of registering and then returning to the workflow to complete the subscription process but of course that's just not as convenient bc you have to log back in vs my kind of hacky solution which lets you register and subscribe at the same time.
Maybe we need another module that let's you put an intermediary registration/login screen in between any workflow and stores the registration user id in the session so that you module can have the new user id even if the user has not logged in yet.
subscribing
hey there,
the last version of the module is dated May 25 2008. Is there any news going on? Is the project still alive?
cheers
ya it's still alive
this is part of a larger website project so it's still in development but i've been spending time creating other custom modules for this project. this version is working but i don't feel comfortable with it being robust enough for a production environment yet, i hope to have a version out this year or early next year that is production ready.
if you notice I did update the dev tarball the other day. that is the version to download as the 1.0 version was a mis-fire by me as i didn't want to release a "stable" version but there was no way to undo it once i tagged a release as a stable release.
anywho if you can wait it's still cooking.
ubercart's authorize ARB support
Recently I found out the ubercart now has authorize ARB support and somewhat integration with the recurring billing module. I found a thread discussing the same problem that have tried to solve with my own module:
http://www.ubercart.org/forum/support/6791/expiring_roles_and_recurring_...
Before I thought that it would be difficult to stretch ubercart's functionality with recurring billing (not invoicing) but with the recent revelation now I'm wondering if it would be better to use ubercart's recurring billing system with possibly a submodule for dealing with role promotion if I'm not entirely satisfied with it's default functionality.
It's definitely something I will research now, if it proves to be better to user ubercart then that would deprecate this module in my opinion. Ubercart has great functionality, I will need to test it's ability to handle recurring subscriptions.
Any thoughts out there? Feedback would be appreciated.