Hi,
very interested in using this module - but have a few questions...firstly does it integrate with rules at all? This would be very useful for sending emails to customers and for adding/removing roles for subscriptions etc. Would the webform pay module be the place to look for rules stuff?
Also, what would be the best setup for recurring payments? Based in the uk so like the look realex - but not sure how it all slots together...
Perhaps it would be better to use the donations module rather than webform pay?
Also, whats the situation on receiving notification back after a payment is made? Is it fairly quick or does that depend on the provider more?
And finally - given the Drupal way, are there any plans to make a CCK payment field addon mod? On the node edit page you could put in a price and whether recurring or not, and on the node view page this could turn into an order button. For me this would be a superb feature and would make theming a lot more do-able - which is something im not fond about with Ubercart.
Oh and another thing - this could then integrate with Flag which could make a very nice shopping basket - probably not really the intention of this module but it would make a very robust and modular ecommerce system for sure - using bits of drupal many have running anyway...
By the way Im brain storming! It's not a feature request for all of the above :-) - it looks it's going in the right direction and thanks for all your hard work...I think this little set of modules will be a great alternative to a weighty ubercart setup for smaller operations - I'll be keeping an eye on it!
Many thanks, Joe
| Comment | File | Size | Author |
|---|---|---|---|
| #10 | pay_rules-7.x.tar_.gz | 832 bytes | mwm |
| #10 | pay_rules-6.x.tar_.gz | 848 bytes | mwm |
Comments
Comment #1
jerdavisThanks for the brain dump Joe!
I think it makes sense to break some of these things out into feature requests of their own so we can address them more holistically and they're more easily findable by other folks looking for the same types of stuff. Would you mind doing that, creating a unique issue in the appropriate queue for each?
To hit on your first question, there isn't integration with Rules at the moment, but there are a lot of events firing off through out the process of handling a payment transaction / activity that could easily be integrated into Rules or core Actions. This isn't really high on our priority list at the moment but we'd certainly take the time to review any patches that anyone might submit or discuss the topic further.
We're always thrilled to get feedback like this, so thanks again!
Jeremiah
Comment #2
joecanti commentedHi Jememiah,
Thanks for the reply - and yes, I'll split these into separate issues...Namely Rules integration, recurring Payments and CCK. I'll keep the Rules one here. It'll be interesting to see if anyone else thinks these deatures would be useful or not!
Many thanks,
Joe
Comment #3
joecanti commentedComment #4
joecanti commentedRules integration...
Hi Jeremiah,
I would love to see a basic 'on payment accepted > do this......' rule or action available.I could see it having quite a few uses, but the one I had in mind was for site subscriptions. For example when a payment is accepted for a monthly subscription, the user would be moved to the 'premium' role for 1 month and a welcome email sent.
This could be used in any situation where something extra needs to happen, beyond having the payment taken - EG thankyou/confirmation emails, digital download delivery, role upgrades, userpoints granted etc.
I realise this isnt high priority, and unfortunately I'm a designer and am rubbish with code (just learning) - so Im putting this out there to see if any one else has an interest or other user cases.
Many thanks, Joe
Comment #5
DrewMathers commentedThis might be possible using the combination of Webform Pay and Webform Rules.
Comment #6
user654 commented.
Comment #7
allie micka@DrewMathers, it seems like it would make more sense to directly attach rules and actions to the activity of making payments, not necessarily through the webform rules route. I don't know, I guess you could argue that either way.
Pay is firing triggers on a variety of events, but I think that Rules doesn't use these. I briefly looked into adding rules support for Pay, and found it to be much more involved than I had hoped it would be. I'm totally in favor of having this support, so perhaps someone with more familiarity with the Rules API can lend a hand? A patch would be most welcome.
Comment #8
DrewMathers commented@joecanti,
The site subscription functionality you mention on #4 can be achieved with:
http://drupal.org/project/lm_paypal
http://drupal.org/project/role_expire
Comment #9
chrislabeard commentedAnymore progress on rules integration?
Comment #10
mwm commentedI've implemented Rules support for both D6 and D7. It supports an event when a payment transaction has completed, which I use for granting roles.
To use it, just put the pay_rules directory under your pay/modules/ directory, and then enable the pay_rules module.