Fix My osCommerce: the next contribution overwrote a file the

When the request is fix my oscommerce, we look at the live site first. The check we expect to matter is: the next contribution overwrote a file the last developer had edited.

A specific fault, not a slogan

• The next contribution overwrote a file the last developer had edited
• Search goes empty after a product import
• The customer reaches the confirmation page and the order never appears in the admin
• A USPS or rate module is still written for an old API

What gets checked

osCommerce stores from that era are still taking orders. The failure is usually a contribution, a payment module, or a PHP version the cart was never updated for. The fix is in the files and the order tables, not a new slogan on the home page.

• Which files differ from a clean cart of the same vintage
• The PHP version the host is really running
• Whether the admin and the catalog are using the same database
• configure.php paths and the SSL flag

What you can send first

One fault often exposes a second one, usually an update that was skipped. We will tell you about that second item before we fold it into the bill.

A repair has a symptom. We reproduce it, change the cause, and try the same steps that failed. If we cannot reproduce it, we say that instead of editing at random.

If you are outside Toronto, the call is the same. We say what we found and what the work is before we change the site.

Call 905-426-1784. We look at the site and tell you what the work is before it starts. The service page for this is osCommerce help.