PDA

View Full Version : Cart issues when moneyorder.php used



Asgoroth
10-06-2007, 08:45 AM
Our store has been up and running for some time now. We recently discovered that when a customer uses the check/moneyorder option (moneyorder.php) any items past the first one are dropped. The price is still correct for all items purchased. I have checked in the database and have confirmed that only the first item is being saved.

I opened moneyorder.php and was not able to see anything in the modual that would have anything to do with this issue.

I have done searches here and at oscommerce without any luck. I am looking through checkout files, but so far no luck.

Asgoroth
10-06-2007, 06:19 PM
checkout_process.php
checkout_success.php
moneyorder.php

I have been looking at these files as the trouble for my issue. As the PayPal modual seems to work fine, I am looking more at moneyorder.php as the trouble. Still not finding the issue though. There is very little in the moneyorder.php file.

michael_s
10-06-2007, 09:06 PM
Could it be this:
185: multiple items in an order result in only 1 product in the order details/email - Bug Tracker - open source Commerce Maximized :: osCMax (http://bugtrack.oscmax.com/view.php?id=185)

What version of osCMax? Have you updated to RC3.0.1?

Asgoroth
10-07-2007, 05:59 AM
Could it be this:
185: multiple items in an order result in only 1 product in the order details/email - Bug Tracker - open source Commerce Maximized :: osCMax (http://bugtrack.oscmax.com/view.php?id=185)

What version of osCMax? Have you updated to RC3.0.1?


That was in fact the issue. I had searched but apparently had not used the right words. I have not upgraded to RC3.0.1 I have a number of modifications on the code and time is sometimes not my friend.

Thank you.

michael_s
10-07-2007, 09:02 AM
If you are running RC3, the upgrade to 3.0.1 is trivial and quite easy. See the changelog for details:
http://www.oscmax.com/projects/release/oscmax_power_e_commerce_software_2_0_0_rc3_0_1

It is always a good idea to check the change log for each update, as it notes this bug and links to it directly.