Purchase Orders 1.4.1 with 2.2 MS2

[zachmorris]

I'm attempting to use the contribution Purchase Orders 1.4.1

 

Everything works fine except the display of the PO Number on the admin side.

 

From the php code, it inserts a PO number into the 'orders' table just fine using:

 

'purchase_order_number' => $order->info['purchase_order_number'],

 

I can go into the table using phpmyadmin and see it is inserted correctly.

 

Then using this code:

 

<?php echo $order->info['purchase_order_number']; ?>

 

I think I should be able to show the correct number, but it doesn't show up. Has anyone used this contribution with 2.2 MS2? Any help would be appreciated.

 

Thanks

[Guest]

Sorry to ressurect an old thread but I didn't see an answer to this problem. I have the contrib installed too and having the same problem.

 

The thing I've noticed is that while everything looks like its working going through the order process but it appears to me that the purchase order number never gets inserted into the database. So when as admin you go to look at invoices or orders there is no purchase order number to display.

 

I think the problem is in the checkout_process.php file but I have yet to find what needs to be fixed.

 

Anyone have any ideas?

[eCentricNick]

Sorry to ressurect an old thread but I didn't see an answer to this problem. I have the contrib installed too and having the same problem.

 

The thing I've noticed is that while everything looks like its working going through the order process but it appears to me that the purchase order number never gets inserted into the database. So when as admin you go to look at invoices or orders there is no purchase order number to display.

 

I think the problem is in the checkout_process.php file but I have yet to find what needs to be fixed.

 

Anyone have any ideas?

<{POST_SNAPBACK}>

 

There are a number of issues with the Purchase Order module 1.4.1, when used with osCommerce 2.2ms2.

 

First of all, if you are installing this module on a live site, it is vital that you follow the instructions in reverse order:

 

1) Make the database changes first, otherwise your site will fall over.

2) Then perform the page changes.

3) Then add the new pages and perform the install in the admin payment module control centre.

 

Secondly, you will need some coding experience to be able to do the page changes. Simply cutting and pasting is not enough. You need to be able to recognise constructs such as if-then-else as some of the changes span parts of these blocks. Some also amend array initialisers.

 

Thirdly, the instructions advise to optionally add a default to the database column. This is to allow the site to default to customers not being able to pay by this method until one approves them within the admin panel. Be warned, the default will only affect newcustomers! If you wish to prevent all your existing registered users from being able to pay by purchase order (until you approve them), you will also need to run a subsequent SQL update to set all those customers to false.

 

Fourthly, the module will not work with 2.2ms2 unless you finish writing the code for the po class. The before_process() method has not been coded which results in the PO number entered by the customer being lost between the order confirmation and order success pages.

 

After a lot of rewriting, we have completed a fully working integration of this module for a site we are building for one of our eCommerce clients.

 

If you need further guidance, please email me for details.

[soodanim]

After a lot of rewriting, we have completed a fully working integration of this module for a site we are building for one of our eCommerce clients.

 

<{POST_SNAPBACK}>

 

Will you be sharing the "working" version? in the contributions for those who would like to download and install?

 

Thanks

[eCentricNick]

Will you be sharing the "working" version? in the contributions for those who would like to download and install?

 

Thanks

<{POST_SNAPBACK}>

 

Most of our findings refer not to the module itself, but rather to the poor guidance given with it. I've outlined the need for caution and a proper sequence of installation in my posts already.

 

As much as I would like to post our full working version as a contribution module, contractually those enhancements belong to the client who paid my consultancy to carry them out and integrate osCommerce with their existing systems.

 

I'm happy to share the detailed information on a one-on-one basis with anyone who asks but the client will not allow me, at this stage, to post any code they have paid for.

[Kishy]

I am having the same problems but the actual purchase code is not even being submitted into the database field I have added. I have v2.2 RC1 and would love to use this add on. Has anyone fixed this problem or can point me in the direction to fix it?