Upgrading Database from 1.5.1 to 1.5.3

I have just completed upgrading from 1.5.1 to 1.5.3. After the upgrade I got a message saying I need to upgrade the database:

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

Using zc_install.php I get an error message:

/admin/includes/configure.php does not exist

For security reasons, I changed the name of the admin folder to another name, e.g.. jjoeadmin

For the installer to work do I have to upload the admin folder within the 1.5.3 installer (which will mean there are two admin folders, admin and jjoeadmin)?

What is the proper way to do this?

Thanks!

To use the installer, rename your secret admin directory to /admin and then run the installer ... when done, rename /admin back to your secret admin name ...

Thank you Linda. That error message disappeared but after I press the Update button all I get is a white screen, no progress bar or anything. If I reload the page, the installer starts from the beginning. Tried with both Firefox and Safari.

I wonder what I should try...

So the /admin is /admin and the /zc_install is /zc_install on the server?

Yes, I changed the name of my admin folder to admin and zc_install is within the same directory that admin is, that is, within the folder that holds all the zen cart files.

If you go to /logs and do a refresh in your FTP program, do you see any new debug logs?

I just tried to upgrade the database from 1.5.1 to 1.5.2, and as soon as I enter my zen cart admin username and password, I get a 500 error. the upgrade doesn't happen. any ideas??

I checked the logs and as one of them was saying configure.php was not writable, I used both my FTP program and my hosting company's file manager to change permissions to both 666 then 777 but the writable message disappears but if I reload that page, it sometime appears.

I also noticed this message:

Previous Zen Cart® Installation Found
Database appears to be Zen Cart® v1.5.3

in the Prerequisites step of the installer.

have attached the relevant logs.

Attachment #14592

error log: client denied by server configuration ....blah/blah/includes/filenames.php

I read somewhere else in this forum it says a problem with the configure.php file. not sure what the "problem" is, since they didn't say what they did to fix it.

I have confirmed that store/includes/configure.php is writable.

In the zcInstallDEBUG log file I am seeing the message below. I'm not sure how to handle it.

Thanks in advance!

[12-Oct-2014 17:19:25 America/Chicago] PHP Warning: require_once(/home/globalpe/public_html/store.globalpeace.jp/../includes/classes/vendors/password_compat-master/lib/password.php) [<a href='function.require-once'>function.require-once</a>]: failed to open stream: No such file or directory in /home/globalpe/public_html/store.globalpeace.jp/includes/classes/class.zcPassword.php on line 52
[12-Oct-2014 17:19:25 America/Chicago] PHP Fatal error: require_once() [<a href='function.require'>function.require</a>]: Failed opening required '/home/globalpe/public_html/store.globalpeace.jp/../includes/classes/vendors/password_compat-master/lib/password.php' (include_path='.:/usr/lib/php:/usr/local/lib/php') in /home/globalpe/public_html/store.globalpeace.jp/includes/classes/class.zcPassword.php on line 52

Peace Freak:

I have confirmed that store/includes/configure.php is writable.

In the zcInstallDEBUG log file I am seeing the message below. I'm not sure how to handle it.

Thanks in advance!

[12-Oct-2014 17:19:25 America/Chicago] PHP Warning: require_once(/home/globalpe/public_html/store.globalpeace.jp/../includes/classes/vendors/password_compat-master/lib/password.php) [<a href='function.require-once'>function.require-once</a>]: failed to open stream: No such file or directory in /home/globalpe/public_html/store.globalpeace.jp/includes/classes/class.zcPassword.php on line 52
[12-Oct-2014 17:19:25 America/Chicago] PHP Fatal error: require_once() [<a href='function.require'>function.require</a>]: Failed opening required '/home/globalpe/public_html/store.globalpeace.jp/../includes/classes/vendors/password_compat-master/lib/password.php' (include_path='.:/usr/lib/php:/usr/local/lib/php') in /home/globalpe/public_html/store.globalpeace.jp/includes/classes/class.zcPassword.php on line 52

The only reason for includes/configure.php to become writeable is if it is to be modified as part of the installation. If only upgrading the database, then it does not need to be writeable. The error contained above has been indicated as appearing if the database upgrade is being performed on a database that has already been upgraded.

In one of the recent threads reporting asimilar issue it was reported that if the contents of the old database are uploaded into the new database (after either the tables are dropped or before the sql that adds each table that table is dropped) then zc_install is performed on the database to upgrde it, the problem did not appear. The zc_install should be the one obtained from the latest version of zc 1.5.3 obtained from http://www.zen-cart.com/getit

That was how one individual resolved the equivalent issue. Note though that recently the generation of passwords has been identified as PHP version dependent, though I haven't figured out how that affects the password that is provided in the FAQ for cases where the password has been forgotten and the PHP version moves up past those bounds.

Sort of a cross post, but similar issue identified in: http://www.zen-cart.com/showthread.php?214618-Database-upgrade-from-1-5-1-to-1-5-3&p=1260997#post1260997

And regarding versions with passwords there is this: http://www.zen-cart.com/showthread.php?214858-Local-upgrade-to-1-5-3-Upload-to-test-site-Can-t-login&goto=newpost

Thanks everyone, especially for the links which were good reading but with no definite answers.

I downloaded the latest "hotfix1" version and used that version of zc_install but still no change.

I'm not really sure what steps I should take. I've had my share of database problems in the past and at one point had to spend weeks rebuilding my site.

I wonder if I should delete the database and then try reinstalling it. Or perhaps Dr. Byte is working on a fix and I should wait a bit.

Would appreciate further thoughts on what I might do...

See the password fix at http://www.zen-cart.com/showthread.php?213868-Known-Bugs-%28and-fixes%29-with-v1-5-3

Been very busy for the last few weeks. Have not been able to get things to fly.

I have a backup of the pre-upgrade data. Rather than deal with the upgrade, could I move the current files to another directory and put the original data back? I guess if the database has not been changed this would be possible???

Is this a viable (temporary) solution? (The store has not been operational for more than three weeks!).

Thanks...

Peace Freak:

Been very busy for the last few weeks. Have not been able to get things to fly.

I have a backup of the pre-upgrade data. Rather than deal with the upgrade, could I move the current files to another directory and put the original data back? I guess if the database has not been changed this would be possible???

Is this a viable (temporary) solution? (The store has not been operational for more than three weeks!).

Thanks...

Nope which is why you'll NEVER see it recommended/suggested..

DivaVocals:

Nope which is why you'll NEVER see it recommended/suggested..

I understood the question to be is it possible to restore everything, but before restoring it set everything aside to work on later.

mc12345678:

I understood the question to be is it possible to restore everything, but before restoring it set everything aside to work on later.

Since the OP didn't say that explicitly.. I understood the question to mean to leave the 1.5.3 files in place and restore the pre 1.5.3 DB.. The answer to that is NO, and that's why it will never be suggested/recommended..

What the OP needs to do to get their LIVE store back up is to restore the ENTIRE pre-1.5.3 store (files and DB)

Then going forward the OP needs to follow the recommended upgrade path which includes creating a dev/test site to do the upgrade work first before applying those changes to the live site.. (which will mitigate the live site being taken down from an upgrade..)