Jump to content



kymation

Member Since 10 Sep 2003
OFFLINE Last Active Today, 02:01
*****

Posts I've Made

In Topic: Blank checkout_shipping.php page after adding MVS

27 March 2017 - 18:16

The critical error is that last one: you are missing a file. Apparently includes/classes/xmldocument.php was left out of that version of MVS. You can get a copy from the Version 1.2.3 package.

 

I suggest checking the filename list in the MVS instructions, in case you are missing more than one file.

 

Regards

Jim


In Topic: Blank checkout_shipping.php page after adding MVS

27 March 2017 - 17:07

Ask your host where your PHP error log is located. They may need to turn on error logging, or tell you how to do it.

 

Did you replace the checkout_shipping.php with the one from the MVS package or did you apply the patches to your file? The version supplied in the MVS package is for an older version of osCommerce, so you would need to patch the file instead of replace it.

 

For now, just replace that file with your backup copy.

 

Regards

Jim


In Topic: Also Purchased query performance problem

27 March 2017 - 01:38

@douglaswalker  That SQL scans the entire orders table looking for dates that fit in the required range. Without actually testing it, I would say that it is very likely to be slower than the stock code.

 

Regards

Jim


In Topic: Also Purchased query performance problem

27 March 2017 - 00:17

If this is still a 2.2 version database, you are probably missing an index or three. I would compare the database schema for your database to the latest 2.3.4 and add in any missing indexes. It would probably help.

 

Cache is a horrible solution to anything. It should only be used as a temporary fix to keep the store running while you fix the problem. If you do use it, remember that you need to flush the cache every time you make a change or your change will be invisible until some random future time.

 

Regards

Jim


In Topic: Also Purchased query performance problem

26 March 2017 - 20:41

The major problem here is that 130k orders_products table, combined with the 36k orders table. The tables are already indexed, so that's not a solution.

 

The easiest way to solve this is to purge your older orders. If you've been accumulating them for many years, clearing out all but the last year or two will help a lot. You shouldn't need to keep old orders online. Of course you should back up your database first, in case you need some of that old data.

 

The only other solution I can think of would be to rewrite the code to run the query manually in the Admin and store the results in a new database table. The catalog side query would then pull the results from this new table, which would be a great deal faster. The downside is that you need to manually run the query periodically to refresh the new table. That and the new code that would have to be written to do this of course.

 

I would love to see a better solution to this. Anybody?

 

Regards

Jim