Closed (fixed)
Project:
Pay
Version:
6.x-1.1
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
15 Dec 2010 at 08:21 UTC
Updated:
20 Nov 2011 at 20:20 UTC
Jump to comment: Most recent file
Are you planing to port this module for Drupal 7 sometime soon?
| Comment | File | Size | Author |
|---|---|---|---|
| #28 | d7_formatting-998736-28.patch | 88.85 KB | nicolash |
| #28 | d7_functionality-998736-28.patch | 71.45 KB | nicolash |
| #25 | 998736.patch | 139.25 KB | stella |
| #24 | pay.tgz | 64.76 KB | stella |
| #22 | pay.tgz | 88.99 KB | stella |
Comments
Comment #1
Dave Cohen commentedI'm also interested in payment options for Drupal 7. If there is any plan for Pay, please let us know.
Comment #2
mmartinov commentedI'm interested in contributing (with patches and testing) to the porting to D7 effort.
Comment #3
jerdavisHi All,
Porting Pay to Drupal 7 is very high on our list of priorities right now and are working to get the time to do this slotted into our schedule. We've started upgrading some of the periphery modules such as Postal.
Porting the Payment API to D7 should be relatively pain free, if anyone wants to take a crack at it and post a patch we certainly wouldn't turn them down, otherwise if you'd like to support the effort in other ways that's also appreciated! Either way we'll keep folks apprised!
Comment #4
entrigan commented+1
Comment #5
lloydpearsoniv commented+1
Comment #6
brianV commented@jerdavis: any update?
Comment #7
allie mickaHey folks,
We're working a lot on Pay right now, rolling new features and big bux fixes out every day. This is our current priority. After all of this shakes out, we'll be thinking about an upgrade.
Thanks!
Comment #8
brianV commented@Allie:
I noticed the development! What do you project as a timeline for upcoming development?
We are looking at using Pay in an upcoming D7 project, so a port is of great interest to us, and we may be able to assist with it. What do you see as the challenges in doing a port?
Comment #9
sirspacey commentedAny one interested in getting this done by the end of next week for a bounty?
Comment #10
sadist commentedUp!
Comment #11
dboulet commentedI might take a crack at it this week. Really need a D7 version very soon...
Comment #12
c4rl commentedSubscrizzle
Comment #13
EvanDonovan commentedSubscribing.
Comment #14
kevinquillen commentedSubscribing. Would possibly also donate funding to move this along. Pay + Webform Pay = very good solution for many payment based applications.
Comment #15
dboulet commentedRan out of time last week and decided to use lm_paypal instead. I will probably need this for another project though so I might try porting it in the near future.
Comment #16
allie mickaHey everyone,
This is definitely on our radar. Because this work is currently not funded by anyone, we're scheduling this around our client work schedule. (we all gotta eat, right?) If this project were to become funded by someone, we could provide more definitive information on when a D7 version might be available and I'll update here.
It's likely that the upgrade will be somewhat invasive from an API standpoint, since I would like to get the class and method naming conventions more in line with D7's coding standards. IT would also be nice if payment forms were entities. This will mean coordination with other backend and form providing modules. Beyond that, I don't expect that I'll make many changes.
Comment #17
stella commentedsubscribe
Comment #18
kevinquillen commentedHow about a quick port of the D6 version to get it working in D7 (so other modules like Webform Pay can move up to D7), then a 2.x branch for the entity conversions of Pay? What would the timeline of the first one be?
Comment #19
dboulet commentedHere’s the work that I’ve done so far. Ran the code through Coder Upgrade and started cleaning it up. Still tons of work to do and don’t think that I’ll have any more time to put towards this for a while...
Comment #20
laura s commented@allie, I tried contacting you a couple of weeks ago re a bounty for this. Any interest? Alternatively we could put a dev on this.
Comment #21
dboulet commentedHi Allie, should I bother expanding on the work I posted in #19, or do you have someone working on a rewrite of the module?
Comment #22
stella commentedI was going to rewrite it with some of the ideas Allie had, but in the end the client didn't have enough budget for that :( So I ended up fixing up the d7 port some more. This one gets rid of a lot more errors but is probably not finished - there are some todos left in the code btw, especially in areas where I wasn't clear.
The next step for me is to port the pay_realex payment gateway module and start testing some actual transactions rather than just the UI.
I'll be actively working on this over the next couple of days.
Comment #23
jerdavis@stella can you post a patch for the work you've done? DId you do any refactoring or just a straight d7 port?
Comment #24
stella commentedUpdated version, working quite well for me with my D7 ports of 'pay_realex' payment gateway and 'webform_pay' (see relevant issue queues if interested).
This takes the coder_upgrade output and fixes all the problems it finds. It's too tricky at this stage for me to create a patch file, sorry. There's still a few todos in the code, but got rid of most of them, but that's probably a place to start if you want to clean it up some more.
Comment #25
stella commentedActually I had the 6.x-1.1 version in a different git repository, so was able to overwrite that and generate a patch file that way. I'm not sure how useful it is as coder_upgrade changes the coding style throughout and so there are way more changes than a straight port warrants but there's not much I can do about that.
Comment #26
brant commentedsubscribe
Comment #27
nicolash commentedsubscribe
Comment #28
nicolash commentedStella's version worked for me, although I probably didn't touch on many parts of the functionality. I used it with a Authorize.Net dev account and a D7 port for that (#1281366: Authorize.Net D7 port) as well as the webform pay D7 port to provide the form (#1239466: Drupal 7 Port?).
I've separated the formatting coder upgrade changes in a patch, then the functionality Stella provided with a few additions. One thing I had to change was a function call in the actions/trigger integration - it would be great if someone who uses this to confirm it's still working for them.
So apply d7_formatting-998736-28.patch first, then d7_formatting-998736-28.patch.
Comment #29
codesmithSubscribe - I have some comments coming soon...
Comment #31
quicksketchI've branched Webform Pay for 7.x-1.x over in #1239466: Drupal 7 Port?. Sorry I deleted comment #30 above this one, as I accidentally posted #1239466-8: Drupal 7 Port? in this queue instead of the Webform Pay one.
Comment #32
rogical commented+1
Comment #33
allie mickaI have committed the patches from NicholasH and Stella, and I have opened up a Drupal 7 branch.
I'm marking this issue as 'fixed'. Please file new tickets with specific bug or feature requests on Drupal 7.
Big thanks on those patches, by the way!