Purchase Orders 1.4.1

[mwdesigns]

I am using Contribution Purchase Orders 1.4.1.

I have installed osCommerce 2.2 Milestone 2

 

I have successfully installed and tested the following modules & contributions:

contrib_CustomerDiscount_1.1

CVV1.24

FAQ_SYSTEM_2_1a

pictures_zoom_v1.2

RandomNewProducts1.1

 

I am now installing "purchaseorders_1_4_1"

 

The problem I am having is, everything works 100% but I get NO PO Number on the admin email. When I go into the order via admin, the order number is displayed, just not in the email.

 

We run a busy office, but only I have access to the admin password and username, and we want to keep it that way.

 

I have searched the forums, but am blind to finding it. Any help would be appreciated.

 

Cheers

Martin

www.tool-direct.com

[OceanRanch]

This contribution should do you nicely.

 

http://www.oscommerce.com/community/contributions,2947

 

HTH

Tom

[mwdesigns]

This contribution should do you nicely.

 

http://www.oscommerce.com/community/contributions,2947

 

HTH

Tom

<{POST_SNAPBACK}>

 

Thanx Tom,

The problem is not when the customer replies to the email.

The hassle is the order email to admin the site generates isn't pulling the PO number from the DB and passing it onto my admin email.

Cheers

Martin

[OceanRanch]

The contribution actually changes the subject line of the email sent from the site when an order is generated. Asumming you have included yourself via the admin->my store->send extra email facility you will get the email.

 

************ from the contrib summary

We're also going to change the email subject for the initial email that gets sent to the customer when they place an order. We'll change it from:

Order Status

to:

The Great Space Coaster Store Order 1234 has been received.

**************

 

HTH

Tom

[OceanRanch]

Oops, I see the problem. Your talking about a new field in the PO contribution not the order number.

 

Oh well sorry bout that........

 

It shouldn't be to difficult for someone familar with the contrib to replace the order_id number with the PO number.

 

I'll go away now.....

 

:-( Tom

[mwdesigns]

Oops, I see the problem. Your talking about a new field in the PO contribution not the order number.

 

Oh well sorry bout that........

 

It shouldn't be to difficult for someone familar with the contrib to replace the order_id number with the PO number.

 

I'll go away now.....

 

:-( Tom

<{POST_SNAPBACK}>

 

Thanx for trying to help anyways Tom.

[eCentricNick]

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.