HELP - cache does not exist

[midiwhale]

The default stylesheet on my local backup says

// +----------------------------------------------------------------------+
// $Id: stylesheet.css 1223 2005-04-22 03:46:20Z ajeh $

The default stylesheet on the broken web shop says
(waiting an hour to download it all now.....)

One oddity, is on my local backup I have no index.php in the cache folder.
On the broken web version I have an index.php in the cache folder.
Is that normal and from what version ?

cache index.php
// $Id: index.php 1322 2005-05-06 23:22:28Z drbyte $
//

// send to domain root
session_write_close();
header('Location: ' . 'http://' . $_SERVER['HTTP_HOST']);
exit();
?>

[midiwhale]

Project version - Cool Tip ;-)

Project version says 2.5 for main and db
Project history says 2.4

I can't remember if I did do an upgrade or not.

So doesn't look like a forced (or attempted?) 3.6 upgrade then ..... ?

[DrByte]

None of the upgrade tools do anything to the db_cache table.
If your db_cache table is missing, you can recreate it by finding the "CREATE TABLE db_cache ..." section of the mysql_zencart.sql file in the zc_install folder.

[midiwhale]

Thanks DrByte !!

I had a db_cache entry in the database. Just not the entry in the php file, lynda mentioned.


I've found the includes config had changed for the SSL path entry.

Also counters had changed from the backup.

I'm now getting;

1146 Table 'microban_zc1.meta_tags_categories_description' doesn't exist
in:
[select * from meta_tags_categories_description mcd where mcd.categories_id = '0' and mcd.language_id = '1']

and indeed this isn't in the current database (v2.5)

Seems it's a half way upgrade ? - not sure how, who or to what.


Assuming this is a 2.5 version, is it safe for me to do a 3.6 upgrade and do the table upgrades ? bearing in mind I can't log-in as admin, or visit the front page yet ?

WDYT ??

I could do a complete backup to live restore, but AYK it takes ages and there's not guarantee it will work anyway even then.

WDYT is my safest course of action?

I have backed up the mysql file (including config table, which is the bit that worries me) and the broken shop in a spare folder.

Sorry I can't think clearly at the moment. I just wasn't expecting this right now......

Thanks for your help guys !

[kuroi]

The hypothesis that I am working with is that your database and code are out of sync. But before giving advice, it would be helpful to be able to confirm this, hence the request for the date on the stylesheet and for info about the database prefixes. This would still be helpful if you have it.

Longer term, the safest course of action will be to upgrade to the latest version (1.3.7) of Zen Cart - after all that's the one with the most security fixes in. But that's a pretty big undertaking as you would be crossing from 1.2.x to 1.3.x and there were some significant structural changes in Zen Cart with this transition. So some idea of what changes you had made to your Zen Cart and how extensive they were (stylesheet, template files, module file, language files, extra functions, etc.) would help in giving advice.

And as always ... a live link to the broken site can be invaluable.

[midiwhale]

Thanks kuroi. I was still waiting for my ftp program to stop doing stuff so I could check.

The actual install and scripts had no prefix.
mysite_zc1

The admin script is now asking for
mysite_zc1.zen_

My backup stylesheet says
// $Id: stylesheet.css 1223 2005-04-22 03:46:20Z ajeh $

The live web version says
* @version $Id: stylesheet.css 4813 2006-10-23 02:13:53Z drbyte $

I have created my own stylesheet, but it is in its own folder. I've made no scriptng changes, third party mods, or any other addons or extras.

I added the meta_tags_categories_description using phpmyadmin and my storefront now loads but says;

Your database appears to need patching to a higher level. See Admin->Tools->Server Information to review patch levels.

Unfortunately my oriignal blahdmin folder says ILLEGAL ACCESS
and the factory default ADMIN folder says

1146 Table 'mysite_zc1.zen_project_version' doesn't exist
in:
[select * from zen_project_version WHERE project_version_key = 'Zen-Cart Database' ]
If you were entering information, press the BACK button in your browser and re-check the information you had entered to be sure you left no blank fields.

Adding the ZEN prefix which isn't/never was used.


I'm inclined to restore my admin (actually blahadmin to admin folder, as this seems to have changed the most. WDYT ??

What I'm going to ask next of course ;-) is
if I go from 2.5 to 3.6, will it upgrade the databases for me, or do I need to install each step manually ?
If I assume this is somehow a bad upgrade from 2.4 to 2.5, that should be safe yes ?

What is the default admin login, or how do I reset the admin password, cos you know that's bound to go the way of the pear ;-)

Many thanks for your help!

[kuroi]

Let's dissect this ...

I don't think you have a botched upgrade from 2.4 to 2.5. Your database version is 2.5 and the history shows that it was previously 2.4 suggesting one upgrade, probably some time ago. No problem there unless you know differently.

The data from your stylesheet confirms that your code is for version 1.3.6, and from your config files that they have come from the default version release package where the database prefix is zen_. This won't sound like ground-breaking stuff, as we're really just confirming what had been expected all along.

I am curious though as to why you introduced the idea of a forced upgrade to 1.3.6 (as opposed to 1.3.7), since that does look precisely as though that's what has been attempted here. Have you discussed this with your webhost?

Where to go from here. It is relatively easy to upgrade the database to 1.3.6, and in your position that's what I'd do. However, although your data will be fine, you would have to put more effort into rebuilding you template. This couyld range from straightforward if you were basically using classic with minor cosmetic changes and no add-ins, through to huge, enormous and mind-blowing if you had significantly changed from the default.