query_factory.php on line 46 errors when upgrade from 150 to 151

twi:

Thanks for shedding more light on the situation. I am actually really fed up with my current host. Most of the responses seems nothing but patronization instead of really looking and checking for a solution. I am not surprise on the incident you are telling us here. ** It's just confirmed my suspicion that they (some hosts) just give you an answer for the sake of giving an answer. **:(

These guys did more than that.. They took advantage of the fact that my client was not tech savvy.. Some of the things they told her were flat out NOT TRUE.. Some of the things they told her were pretty close to telling her nonsense like she "needed to take a look at her Flux Capacitor and tune it to match the rising aura of her server's capacity". :laugh: Now this is of course an exaggeration, but some of the nonsense they told her was almost at this level of ridiculous..

Having a similar issue here. to my knowledge no datadiggers stuff is installed. upgrading from 1.3.8 to 1.5.3.
admin works fine.
catalog is blank page.
error in log is this: PHP Fatal error: Cannot redeclare class QueryCache in xxxx/includes/classes/query_cache.php on line 16
would like to figure out how to figure this out without having to do a fresh 1.5 install since unless there is a way to import the 1.3.x database into a 1.5.x install thats not going to work since this is a production database with lots of products.

thomaswhiteeagle:

Having a similar issue here. to my knowledge no datadiggers stuff is installed. upgrading from 1.3.8 to 1.5.3.
admin works fine.
catalog is blank page.
error in log is this: PHP Fatal error: Cannot redeclare class QueryCache in xxxx/includes/classes/query_cache.php on line 16
would like to figure out how to figure this out without having to do a fresh 1.5 install since unless there is a way to import the 1.3.x database into a 1.5.x install thats not going to work since this is a production database with lots of products.
Try installing myDEBUG Backtrace (http://www.zen-cart.com/downloads.php?do=file&id=1879). It will give you information about the call-chain that caused the error. It sounds like you might have merged two files going from 1.3.8 to 1.5.3 and left the original file with a .php extension in a folder where all .php files get loaded (like the /includes/auto_loaders and /includes/modules/pages/xxxx directories).

Thanks, Installed it but error code is unfortunately unchanged:

PHP Fatal error: Cannot redeclare class QueryCache in /includes/classes/query_cache.php on line 16

no other info than that.

Right, I forgot that the backtrace fails on PHP Fatal errors:(

Try using your admin's Tools->Developers Tool Kit to search for occurrences of query_cache.php in all Catalog PHP files. My bet is still on an old copy of a file that still has a .php file extension.

thomaswhiteeagle:

would like to figure out how to figure this out without having to do a fresh 1.5 install since unless there is a way to import the 1.3.x database into a 1.5.x install thats not going to work since this is a production database with lots of products.

If I understand correctly, associated with the above, you are concerned that if you try to install a fresh copy of zc 1.5.3 that you won't be able to then maintain your existing data from your 1.3.8 ZC install because you think there is no way to upgrade that database to 1.5.3?

If that is the case I advise that you re-review the upgrade instructions and note that part of the upgrade process is to specifically upgrade the database. While I hvent upgraded a 1.3.8 to 1.5.3 yet, two weeks ago I upgraded one to 1.5.1 (and then 1.5.3 was released just at the conclusion of the upgrade). We agreed that at the moment to wait to upgrade to the next step to see what issues would be identified with things like plugins.

Another thing of note, this production server sounds like is now disabled from selling items. This could have been prevented if the site was assembled also in accordance with the guidelines of upgrading/updating by doing the work outside of the production site location. This way, what is working can continue to work, while updates are made to the software.

thomaswhiteeagle:

Having a similar issue here. to my knowledge no datadiggers stuff is installed. upgrading from 1.3.8 to 1.5.3.
admin works fine.
catalog is blank page.
error in log is this: PHP Fatal error: Cannot redeclare class QueryCache in xxxx/includes/classes/query_cache.php on line 16
would like to figure out how to figure this out without having to do a fresh 1.5 install since unless there is a way to import the 1.3.x database into a 1.5.x install thats not going to work since this is a production database with lots of products.

Simple: compare all your server's files against original ZC files, and get rid of what doesn't belong.

Seems as though you copied new files to your server without removing old files from old plugins you'd installed.

tool kit shows this:

includes/auto_loaders/config.query_cache.php

Line #14 : 'loadFile'=>'query_cache.php');
/includes/auto_loaders/config.core.php

Line #74 : 'loadFile'=>'query_cache.php');

/includes/auto_loaders/config.query_cache.php

Line #14 : 'loadFile'=>'query_cache.php');

If I understand correctly, associated with the above, you are concerned that if you try to install a fresh copy of zc 1.5.3 that you won't be able to then maintain your existing data from your 1.3.8 ZC install because you think there is no way to upgrade that database to 1.5.3?
no I was trying to figure out a way around this problem with least effort. important thing is to get the products into the new 1.5 database install so was wondering if there was a way to simply transfer the product and attributes tables in. I'm familiar with the upgrade instructions as it stands upgrading the entire system from 1.3.8 to 1.5.

Another thing of note, this production server sounds like is now disabled from selling items. This could have been prevented if the site was assembled also in accordance with the guidelines of upgrading/updating by doing the work outside of the production site location. This way, what is working can continue to work, while updates are made to the software.
Not sure how you get the production server being disabled, that is not the case. That would be bad since this site does a lot of business and is supporting many families. The work IS being done outside of the production site location so we could make sure it would work.

thomaswhiteeagle:

tool kit shows this:

includes/auto_loaders/config.query_cache.php

Line #14 : 'loadFile'=>'query_cache.php');
/includes/auto_loaders/config.core.php

Line #74 : 'loadFile'=>'query_cache.php');

/includes/auto_loaders/config.query_cache.php

Line #14 : 'loadFile'=>'query_cache.php');

You should NOT have those two config.query_cache.php files in v1.5.3
In v1.5.3 the only result you should have seen is for config.core.php.