According to the module's status, it is looking for a new maintainer, from the commit log there have been no code commits since 2009. Despite this, apart from a custom module this module appears to be the only way to add the purchase order payment method.

There are now two ports of this module to Drupal 7:

Initial port of 6.x-1.0 (by me) and latest port of 6.x-2.x (by seanr and pgrujic): http://drupal.org/node/1280502
A much better port of 6.x-1.0 (by kmhanser): http://drupal.org/node/1526056

To make things even more interesting there is a new module, Ubercart Custom Payment: http://drupal.org/project/uc_custom_payment. From the project page, it looks like this module will be able to replace version 1 of UC Purchase Order (as well as a number of other small payment modules). At present this module is very new, but once it stabilises there might be a case to merge this module UC Purchase Order into Ubercart Custom Pages.

As most of my store's customers pay by purchase order I need this functionality. If no one else would like to take on maintenance of this project I would be willing to. However I am a relative newcomer to the Drupal community and most of my contributions to the D7 port have been in testing.

This issue is to discuss the future of this module. Do we keep the project as-is or merge with Ubercart Custom Payment?

Comments

end user’s picture

Well the future is in D7/UC and iIn a year or so when D8 comes out D6/UC support will cease. Seeing as Wondex is the dev for the other module and has done quite a bit for UC I'd say to heads are better than one.

demma10’s picture

Apologies for not making myself clear in the original post. What I was trying to say was, do we resurrect this project with a new maintainer and D7 release, or do we migrate to one or more actively maintained modules with equivalent functionality.

@end user I agree with you about moving to UC Custom Payment (in fact I'm in the middle of testing that module). There are only two issues I can see:

  1. The 6.x.2.x branch of this module has code for a purchase order checkout pane independent of the payment method. While implementing this would be outside of the scope of UC Custom Payment a combination of the Webform and UC Webform Checkout Pane modules can implement this.
  2. What to do with the existing D6 data? I have a large collection of orders with purchase order data which must be preserved during the upgrade to D7. At present there are no import or conversion functions in either UC Custom Payment or Webform to import data from another database table.

It should be possible to write payment method conversion/migration code for UC Custom Payment, but I have no idea how to import the checkout pane information into a webform.

kmhanser’s picture

I'm also willing to maintain the 7.x-1.x branch/port of this module.

I haven't looked @ the custom payment module at all so I don't know what the options are there. Sounds like that might be the future, but "waiting 'til D8 comes out" isn't really an option for a lot of people. That was the case here, we had a customer that needed this functionality, and so the port was created to fill that need.

Now that the customer's need is filled, my time that I can put onto this particular project may be less, unless the customer wants additional changes. (besides bug fixes -- I'll get those fixed as soon as I can when/if the bugs are found).

-kevin
Energy Web Design
http://energywebdevelopment.com

demma10’s picture

@kmhanser, if you want to taken on maintenance of this project then you have my support. Since you've done the bulk of the D7 conversion work I think you should take over as project maintainer.

Like you waiting until D8 is not an option for my organisation. Until there is an upgrade path to uc_custom_payment than a D7 version of this module will need to exist.

wodenx’s picture

I haven't had a chance to look at this module in detail - what is needed to migrate to uc_custom_payment? I'd guess pulling the PO numbers from existing orders and attaching them to a new uc_custom_payment method as a field would cover most of it. I'd certainly be interested in seeing that done if anyone wanted to take it on -- will even do it myself if I can find time, but want input from people who actually use the module before undertaking it.

fashionary’s picture

Subscribe

demma10’s picture

For anyone who needs to move to UC Custom Payment right now I've created a migration module to migrate the UC Purchase Order data to a UC Custom Payment method. The sandbox for this module is located here:

https://drupal.org/sandbox/Demma10/1716466

Currently the module only migrates data from version one of UC Purchase Order and does not delete the old database tables. Also I've only run this on my test site, use at your own risk.

Any feedback and suggestions for improvement would be greatly appreciated. I'd like to do a bit more work on this module (and more testing) before applying for full project status.

jennypanighetti’s picture

What's the status, here? What's the plan?

Does anybody have a *complete* 7.0 alpha or beta module? Elsewhere there are zips, there's a new thread with migration... I'm starting a NEW site, so I don't need migration... I need the status...

demma10’s picture

Unfortunately, at this stage there is no complete D7 module, not even an alpha. Given the project status I don't think we'll see a new release until a new maintainer takes over.

If all you need is version 6.1 functionality I'd recommend going with UC Custom Payment for a new site. It can handle all of the functionality of UC Purchase Order and is more active than this project. I'm currently using it on my site and have had no issues with it.

If you would like a (mostly complete) D7 version I can create a zip file of the 6.x-1.x code with all the current patches applied. It will work but it won't be part of Drupal's update tracking.

jennypanighetti’s picture

Thanks, Demma. I'll take a look at Custom Payment and let you know if that works for my client. I'm also perfectly happy installing a module that's not in the system (your zip file), so if I run into problems with CP, I'll ask for the zip. Thank you!

kmhanser’s picture

I will take a look at the current sandbox code in the next few days and try to get a snapshot .tar.gz rolled out. I didn't realize there wasn't one w/the patches applied until I saw your post. I probably won't get a chance to check it out until the weekend though, so if you need it quicker you may want to grab a copy of the code from the git sandbox repo: http://drupal.org/sandbox/bradjmsu/1539674

I believe the code in the sandbox repo is the same code that's being used on a customer site I had worked on (which is still using is as far as I know), so it should be functional. I'm not positive though since I haven't worked on this in a while.

Let me know if you run into any issues! I'll try to get an updated .tar.gz posted in the next couple days.

thx

-k

kmhanser’s picture

StatusFileSize
new15.82 KB

I have attached a SVN snapshot of the code that I was last using on the site that I created this for. I compared it to the code that the site is still running and it seems to match.

I haven't had a chance yet to see if the git repo contains the same code, my git client was acting up on me and I don't feel like messing with it tonite :) I also need to verify if my code contains all of Demma10's patches. I think it does, but there may be one at the end that didn't get implemented(?).

As far as I know, this is a working version of the module. please let me know if you encounter any issues.

thx

-k

demma10’s picture

Thanks kmhanser

The code in the previous comment is missing the patch from comment 20. All this patch does is fix some of the token handling code, it doesn't affect the purchase order number handling. The code should function without the patch but it may produce some errors about invalid tokens.

I have an archive of the git sandbox code with the patch applied. If you'd like I can upload it to this thread.

DanZ’s picture

My company is migrating to Ubercart and needs this module for D7/U3.

The proper solution here is to get a new maintainer or co-maintainer and put the development code here. See http://drupal.org/node/251466 for instructions on getting a new project maintainer.

If there is no maintainer in a month or two, I'll put my name in the hat. I will only be able to maintain the Drupal 7 version, so I won't be able to maintain it alone. If the D6 version is to be maintained, it will require a co-maintainer.

...and yes, the custom payments module looks promising. Supporting that for D7 may be a better idea.

In the meantime, Drupal.org recommends against uploading module archives (tarballs), since they are permanent. Upload to a sandbox project and provide links to that, instead.

demma10’s picture

@DanZ

There already is a sandbox project for a D7 port of this module. The link is in comment #11 of this issue, but here it is again: http://drupal.org/sandbox/bradjmsu/1539674. You're right in that the sandbox should've been suggested as a first point of call.

The big reason we haven't applied for a change in maintainership is because there hasn't been agreement on whether or not to merge with UC Custom Payment. I moved to UC Custom Payment as it was a better fit for my store (numerous simple payment methods which do not require payment at checkout). I'm not sure if kmhanser is still using UC Purchase Order.

Owing to the interest this thread has received lately maybe it's best someone take over maintenance of this project, even if it is just to allow a release before any merger.

kmhanser’s picture

I'm pretty sure the site I did the port for is still using UC Purchase Order. I don't actually work for the company anymore that I was when I was working on the port, so I haven't really had much more involvement with that site for a number of months. I don't think they've made any major changes though since so I would assume they're still using it.

If someone else would like to take over the maintenance of the D7 port of the module, I would be agreeable to that. If not I can continue to maintain it in my spare time, but that's somewhat limited as I have other job duties to attend to as well as time I'd like to spend with my family :)

As Demma10 mentioned, it just kind of entered limbo because there wasn't a clear direction for the module or functionality that the module provides. I wrote this originally because it was something we needed for a client site, and that need was fulfilled by the port that I created. Where it goes from here ...?

DanZ’s picture

If the Custom Payments module really is the way to go, then this module should have a note on its front page that it's deprecated and a pointer to the other module. Even that note requires a maintainer.

kirkofalltrades’s picture

Still confused as to what is the best module to use for PO functionality in Drupal 7 with Ubercart 3.x. Custom Payments is in dev and appears to have several issues at this point. I'm not totally confident using kmhanser's module if it's not being maintained, but that's where I'm leaning at the moment. Can anyone steer me in the right direction? I only need PO functionality, but desire the ability to restrict PO as a payment option to customers that have a particular role.

Thanks!
Kirk

avpaderno’s picture

Status: Active » Closed (outdated)

I am closing this issue, as it has been created for a release that is now not supported.