Need help to do an upgrade from 1.5.0 to 1.5.5

CaroleAs:

To summarize, i did a clean install on a domain called CHALLENGEMEHQ.COM
This took me a while to test/install the mods i needed to use and format the look i wanted.
That part is ok.

Now, i am testing the upgrade of a "LIVE" site. To do that, i am using the cloned version of my live site that was called STORETEST. That is the version i always used, in the past, to test a new mod, etc. It was cloned about 2 years ago, so obviously the database is "outdated", but it still works AS a live site, with the same version as my LIVE site. So this is where i am testing the actual "live upgrade".

The initial testing site had:
DB_DATABASE = creat419_zencart589
DB_PREFIX = zen_

The live site has
DB_DATABASE = creat419_zencart
DB_PREFIX = zen_

The cloned site has
DB_DATABASE = creat419_zencartclone
DB_PREFIX = zen_

Is that correct?

Could be correct provided that _zencartclone came from _zencart... If it came from _zencart589, then well no update to be performed.. Haven't also described the "look" of the cloned site... Is there something expected there from the database (different product?) than was in the testing site?

CaroleAs:

I could copy them all, but they all have a PASSED mention.

So how do i get this GZip enabled?

There's a number of ways identified in internet searches. Its not required for operation, it just offers faster operation, I realize its not an answer, but I may suggest that for that one to discuss with your host to be able to use the method they consider the best to support their system. I saw htaccess methods primarily, but possibly some other ways.

mc12345678:

Could be correct provided that _zencartclone came from _zencart... If it came from _zencart589, then well no update to be performed..

Not sure what you mean by this statement. Each database AND install is separate. I saved the configure.php file for the _zencartclone to use with that store/install. I didn't "mix" database and store. That is the first thing i checked when i got the error because the mention of a "live site"

mc12345678:

Haven't also described the "look" of the cloned site... Is there something expected there from the database (different product?) than was in the testing site?
The cloned site is exactly like the LIVE site (http://creationcassel.com/store). Same front end, same mods, same images, same everything, so although the database is a different one, it is identical in content to what it was 2 years ago, when it was cloned. The test site was a clean install but i had exported the database from the live site so the "content" was the same as the live site. Now, i don't need that database since the cloned site had its own, that was similar enough to the live site. Is that was you were asking?

mc12345678:

There's a number of ways identified in internet searches. Its not required for operation, it just offers faster operation, I realize its not an answer, but I may suggest that for that one to discuss with your host to be able to use the method they consider the best to support their system. I saw htaccess methods primarily, but possibly some other ways.

If that is "not required for operation", i can skip it for now, but i am back to the question about the mention about the database, where it says " Proceeding with Install will wipe out the current database contents! Are you sure you want to install?" Will it erase it all? If so, how would i get all that info again? By re-importing the db again? That is the "next step" that is scaring me because i don't understand what will/can happen. I tried searching for this message but unsuccessfully.

One thing that i am still not understanding is this. When i tested on the blank installation that was installed through Softoculous, i had to upgrade it (from 1.5.5 to 1.5.5e). I HAD a database, that was a cloned DB from my live site. When i ran the zc_install, it never mentioned anything about the DB being from a live site or anything about the DB. It only gave me the option to upgrade. I was using the _zencart589 DB, which was full of data (it was not empty) and it went fine.

Now, i am ALSO trying to upgrade with the zc_install (same one) although it is from 1.5.0 to 1.5.5e. I ALSO have a DB with data in it. Not all the same data as the live site, and the exact same type of data as used in the TEST as it is also cloned from the actual live site. Why is it THIS TIME, throwing a fit (so to speak)?

What makes this second one look like from a live site and not the first one?

After checking and rechecking the configure.php file for anything missing (a comma, a quotation, a typo, anything), nothing seems to be missing or wrong (from MY understanding). I tried to run the zc_install again, and since i am getting the exact same error, i checked the log file. Strangely, the errors are not the same!

Initially, i was getting this:

Aug 31 2017 19:16 -- checkIniGet
FAILED
(
    [inigetName] => output_buffering
    [expectedValue] => 1
)

and now, i am getting these:

Aug 31 2017 23:36 -- checkPhpVersion
FAILED
(
    [version] => 5.5.0
    [versionTest] => ge
)

Aug 31 2017 23:36 -- checkHtaccessSupport
FAILED

And the mention about checkIniGet is not even in the log (no PASSED or FAILED)

CaroleAs:

One thing that i am still not understanding is this. When i tested on the blank installation that was installed through Softoculous, i had to upgrade it (from 1.5.5 to 1.5.5e). I HAD a database, that was a cloned DB from my live site. When i ran the zc_install, it never mentioned anything about the DB being from a live site or anything about the DB. It only gave me the option to upgrade. I was using the _zencart589 DB, which was full of data (it was not empty) and it went fine.

Now, i am ALSO trying to upgrade with the zc_install (same one) although it is from 1.5.0 to 1.5.5e. I ALSO have a DB with data in it. Not all the same data as the live site, and the exact same type of data as used in the TEST as it is also cloned from the actual live site. Why is it THIS TIME, throwing a fit (so to speak)?

What makes this second one look like from a live site and not the first one?

Is this still the same site that recently had a redirect to your live site?
There could be also a setting in that database that is picked up and possibly causing the install to attempt to access the actual live database?
Possible that in the process of making that site live that portions of the following link were not followed? (See "step" 6): https://www.zen-cart.com/content.php?142-i-want-to-move-my-zen-cart-installation-to-another-host-or-a-different-server

CaroleAs:

After checking and rechecking the configure.php file for anything missing (a comma, a quotation, a typo, anything), nothing seems to be missing or wrong (from MY understanding). I tried to run the zc_install again, and since i am getting the exact same error, i checked the log file. Strangely, the errors are not the same!

Initially, i was getting this:

Aug 31 2017 19:16 -- checkIniGet
FAILED
(
[inigetName] => output_buffering
[expectedValue] => 1
)

> 
> and now, i am getting these:
> ```
Aug 31 2017 23:36 -- checkPhpVersion
FAILED
(
    [version] => 5.5.0
    [versionTest] => ge
)

Aug 31 2017 23:36 -- checkHtaccessSupport
FAILED

And the mention about checkIniGet is not even in the log (no PASSED or FAILED)

The version being upgraded, if followed the discussion correctly, the site also is ZC 1.5.0 to be upgraded to 1.5.5 and yet the above PHP version check identifies that the version is 5.5.0... That is outside the scope of operation for ZC 1.5.0; however, not for ZC 1.5.5... So really confused about the status of your files... If you goto the zc_install/includes/version.php file, what is identified for: PROJECT_VERSION_MINOR?

mc12345678:

The version being upgraded, if followed the discussion correctly, the site also is ZC 1.5.0 to be upgraded to 1.5.5 and yet the above PHP version check identifies that the version is 5.5.0... That is outside the scope of operation for ZC 1.5.0; however, not for ZC 1.5.5... So really confused about the status of your files... If you goto the zc_install/includes/version.php file, what is identified for: PROJECT_VERSION_MINOR?

define('PROJECT_VERSION_MINOR', '5.5e');

However, it also says this:
define('EXPECTED_DATABASE_VERSION_MAJOR', '1');
define('EXPECTED_DATABASE_VERSION_MINOR', '5.5');

Does it mean that it is expecting to work with 1.5.5 from the get go instead of the 1.5.0 that i have which is confusing it?

Is this still the same site that recently had a redirect to your live site?
There could be also a setting in that database that is picked up and possibly causing the install to attempt to access the actual live database?
Possible that in the process of making that site live that portions of the following link were not followed? (See "step" 6): https://www.zen-cart.com/content.php...fferent-server
Yes it is. And yes it is 1.5.0. and yes, that "initial" cloned DB was created while the store was on another server too (which is why, in the very beginning, it didn't even have the correct DB name and such). Going to follow that link.

On the very first step to use that tool, it says "* 1. Make sure the DIR_FS_SQL_CACHE setting is correct in your /includes/configure.php file." One thing i had noticed as a difference between the configure.php file from my "storetest" and my "challengemehq" (aside from the URL and DB info that WAS edited) was that there was no information for that cache line. Currently, it reads like this:

/**
 * Advanced use only:
 * The following are OPTIONAL, and should NOT be set unless you intend to change their normal use. Most sites will leave these untouched.
 * To use them, uncomment AND add a proper defined value to them.
 */
// define('DIR_FS_SQL_CACHE' ...
// define('DIR_FS_DOWNLOAD' ...
// define('DIR_FS_LOGS' ...

While the existing "storetest" file (the copy i saved aside from it) reads this:

  // The next 2 "defines" are for SQL cache support.
  // For SQL_CACHE_METHOD, you can select from:  none, database, or file
  // If you choose "file", then you need to set the DIR_FS_SQL_CACHE to a directory where your apache 
  // or webserver user has write privileges (chmod 666 or 777). We recommend using the "cache" folder inside the Zen Cart folder
  // ie: /path/to/your/webspace/public_html/zen/cache   -- leave no trailing slash  
  define('SQL_CACHE_METHOD', 'database'); 
  define('DIR_FS_SQL_CACHE', '/home/creat419/public_html/creationcassel.com/storetest/cache');

So, when the instructions to use the Fix cahe key says to make sure the setting is correct, should i add those lines "back"? It is obviously NOT correct NOW in the active configure.php file since it is NOT THERE.

CaroleAs:

define('PROJECT_VERSION_MINOR', '5.5e');

However, it also says this:
define('EXPECTED_DATABASE_VERSION_MAJOR', '1');
define('EXPECTED_DATABASE_VERSION_MINOR', '5.5');

Does it mean that it is expecting to work with 1.5.5 from the get go instead of the 1.5.0 that i have which is confusing it?

Yes it is. And yes it is 1.5.0. and yes, that "initial" cloned DB was created while the store was on another server too (which is why, in the very beginning, it didn't even have the correct DB name and such). Going to follow that link.
The zc_install process needs to know to what version(s) to upgrade. It is in this file that the information is stored. As DrByte I believe indicated earlier in this thread, once ZC 1.5.5 or any of its sub-versions are installed, there is no need to run zc_install on that upgraded site, that is why the database is identified as 1.5.5, but the files would be considered in your case 5.5e for the minor version. I wanted to see what was in this file, because looking at the zc_install process there doesn't appear to be a reason for an error regarding php at 5.6 to occur, but it would occur on an earlier version of ZC such as ZC 1.5.0 or 1.5.1 when the php version "accepted" was a maximum of 5.3.x... so the results that are being obtained are unusual and seem unexplained unless there is something "redirecting" to somewhere else.

With all instruction followed and site operation occurring at the two other locations both on store front and admin, it doesn't seem that there should exist a zc_install folder in any of the other locations.

Are you sure still that the database hasn't gotten upgraded already in one of these many runs of the zc_install on the current "test" upgrade?

I mean, right now, really, a file compare between all of the files in this current store to the test store on which you were working the last 2 weeks should be the same other than the two configure.php files (includes/configure.php and YOUR_SECRET_ADMIN/includes/configure.php) and the presence/absence of zc_install (possibly renamed) in the recently built upgraded site. The differences between the two equivalently located configure.php files should be that of likely the server, the DIR_WS_CATALOG, the database settings and the DIR_FS_ defines. Ie. Almost everything that is active (not commented out) in the files.

This comparison is also such that neither fileset has something in it that the other doesn't. Ie. The exact same files in both "folders"... though this current test site with the issue would have zc_install while the other upgraded site would/should not.

Have you tried logging into the admin of this upgraded site to see what the version information/history shows?

If they are exactly the same as expected, then the only other "remnant(s)" that seem as a viable reason for such different results that expected is

CaroleAs:

On the very first step to use that tool, it says "* 1. Make sure the DIR_FS_SQL_CACHE setting is correct in your /includes/configure.php file." One thing i had noticed as a difference between the configure.php file from my "storetest" and my "challengemehq" (aside from the URL and DB info that WAS edited) was that there was no information for that cache line. Currently, it reads like this:

/**

• Advanced use only:
• The following are OPTIONAL, and should NOT be set unless you intend to change their normal use. Most sites will leave these untouched.
• To use them, uncomment AND add a proper defined value to them.
  */
  // define('DIR_FS_SQL_CACHE' ...
  // define('DIR_FS_DOWNLOAD' ...
  // define('DIR_FS_LOGS' ...

> 
> While the existing "storetest" file (the copy i saved aside from it) reads this:
> ```
  // The next 2 "defines" are for SQL cache support.
  // For SQL_CACHE_METHOD, you can select from:  none, database, or file
  // If you choose "file", then you need to set the DIR_FS_SQL_CACHE to a directory where your apache 
  // or webserver user has write privileges (chmod 666 or 777). We recommend using the "cache" folder inside the Zen Cart folder
  // ie: /path/to/your/webspace/public_html/zen/cache   -- leave no trailing slash  
  define('SQL_CACHE_METHOD', 'database'); 
  define('DIR_FS_SQL_CACHE', '/home/creat419/public_html/creationcassel.com/storetest/cache');

So, when the instructions to use the Fix cahe key says to make sure the setting is correct, should i add those lines "back"? It is obviously NOT correct NOW in the active configure.php file since it is NOT THERE.
It IS defined, just not in that file. All of the "standard" defines have been moved to a separate file to minimize the user error issues that had been occurring in previous versions. Your configure.php file has been upgraded/modified to a ZC 1.5.5 version to provide a cleaner set of information that is easier for an end user to maintain especially when referring to the instructions about moving a site from one directory to another or one server to another, etc...

The point of the "exercise" was to validate that the database knows which directory of files to attempt to access (ie this store and not the live store) rather than one of the other stores. This may require going into the database itself and updating the associated constant to support this upgrade. I AM making guesses here, because again there was not all that long ago, but in place for a very long time, a 301 redirect from this directory to the live store.

Have you tried logging into the admin of this upgraded site to see what the version information/history shows?

It says it is 1.5.5e!!!
I mean, i don't know how it happened. Was it just when i ran the zc_install the first time and it asked me to upgrade the DB and that was it? I didn't go through the successive upgrades like i did on the "clean install" that needed an upgrade from 1.5.5 to 1.5.5e, so coming from 1.5.0 i would have expected to see those steps instead of being "stuck" seeing those error message all that time.

And would you know it, the front end is "a new zen install!

OK, so now, i will "reinstall" my sideboxes, and mods and such and see how long it will take me.

CaroleAs:

It says it is 1.5.5e!!!
I mean, i don't know how it happened. Was it just when i ran the zc_install the first time and it asked me to upgrade the DB and that was it? I didn't go through the successive upgrades like i did on the "clean install" that needed an upgrade from 1.5.5 to 1.5.5e, so coming from 1.5.0 i would have expected to see those steps instead of being "stuck" seeing those error message all that time.

And would you know it, the front end is "a new zen install!

OK, so now, i will "reinstall" my sideboxes, and mods and such and see how long it will take me.
New clean install??? As in none of your existing data or the data that is/was in your database?

mc12345678:

New clean install??? As in none of your existing data or the data that is/was in your database?

No no!! a "clean front end". Recognizing the default zencart template, and such. The old data is still there. I can see the customers, orders, etc.
It is like the upgrade was done "without telling me"!

CaroleAs:

No no!! a "clean front end". Recognizing the default zencart template, and such. The old data is still there. I can see the customers, orders, etc.
It is like the upgrade was done "without telling me"!
Ahhh. Okay. I was still getting redirected to your store site when attempting to access storetest. I ended up changing from desktop mode to mobile and could see what you described, though it happened after I posted. :)

You know what that all means though, right?

Time to run the test again!!!

Suggestion being: dump that database (or back it up before doing so), copy over your live database to this one, copy your backed up configure.php files (or contents), upload the zc_install again, do upgrade...

mc12345678:

Suggestion being: dump that database (or back it up before doing so), copy over your live database to this one, copy your backed up configure.php files (or contents), upload the zc_install again, do upgrade...

Will that test an upgrade if the files are still all there?

CaroleAs:

Will that test an upgrade if the files are still all there?
Yes, because remember what I wrote I think the page before. The upgrade performed by zc_install is to update the configure.php files and the database. If you use an old database and an old version of the configure.php files (like you would expect on your live site), then you get to "experience" and learn what is necessary to accomplish this step of the process...

mc12345678:

Yes, because remember what I wrote I think the page before. The upgrade performed by zc_install is to update the configure.php files and the database. If you use an old database and an old version of the configure.php files (like you would expect on your live site), then you get to "experience" and learn what is necessary to accomplish this step of the process...

I didn't want to mess up anything and i was not 100% sure how to clone the live site database into this storetest one, so i called my host. Not only he didn't SHOW me how to do it, he created a new db called zencartclone2 instead of cloning into the zencartclone one that i had.

In light of that, do i only have to change the db info in the configure.php files or is there somewhere else? (i know this will not be a step in the live site upgrade, at least!) And when the database is "reverted" to the un-upgraded version, will that show on the top right of the admin side? I just want to make sure i will proceed with an "upgrade" on an "upgradable" db.