Need help to do an upgrade from 1.5.0 to 1.5.5

mc12345678:

Actually from "our" perspective (viewers of this forum thread) the information provided from that message does not suggest anything directly obvious other than that there is some error in the installation. The details that are provided towards the bottom of that message are what give the clues needed to the reader.

Of course you're familiar with your own sites history so you can fill in the blanks, but providing just the top of that message does not give a lot of detail to the inquiring minds. :)

Oh, i only copied the top of the page simply to indicate that it was not blank. Here is the top half (the bottom half is about how to install):

Hello. Thank you for loading Zen Cart®.

You are seeing this page for one or more reasons:

This is your first time using Zen Cart® and you haven't yet completed the normal Installation procedure.
If this is the case for you, you will need to upload the "zc_install" folder using your FTP program, and then run zc_install/index.php via your browser (or reload this page to see a link to it).

Your /includes/configure.php and/or /admin/includes/configure.php file contains invalid path information and/or invalid database-connection information.
If you recently edited your configure.php files for any reason, or maybe moved your site to a different folder or different server, then you'll need to review and update all your settings to the correct values for your server.
See the Online FAQ and Tutorials area on the Zen Cart® website for assistance.
Additional Details: includes/configure.php file contents invalid. ie: DIR_FS_CATALOG not valid or not set

After this, i also realized that the directory was also wrong. By correcting that, i then get a "Maintenance" image showing up instead.

As to database access, well if the database actually did survive the/a move, you could always establish/re-establish credentials for that particular database. Be careful though, because you may have assigned the same user to have access say as your live site, and if you go and modify the password to work on your test site it may prevent access to your live site (unknowingly), so check the facts and/or create a new user with credentials, etc... keep your live site chugging as much as you can.

This is what i don't know how to do. I contacted my host and they will "try" to recover the PW, but they say that since it is not a server issue (even if it is called DB_SERVER_PASSWORD), they don't usually do that.

I know that the user is different between the two database ( just checked through mySQL). I have no clue how to establish/re-establish credentials for it. I am still searching.

Good news: my host managed to get the password "reactivated". So i am now able to access it, front and back. I put it in maintenance mode for now.

So now i am at the next step of testing on "a live existing site" and my questions are about sequence:

I have printed all the instructions from DrBytes (and lat9).
I want to treat this clone site as a live upgrade so i will be working with "existing files" and existing mods that i don't need (or will need upgrade) so i am unsure about those:

1- when i run the zc_install, will it keep all the images files and download files, and customers/orders info? I assume yes, but need confirmation. If not, what files/folders are "at risk"? Obviously, i'll make a copy of EVERYTHING, in case.

2- how do i deal with outdated or non-longer-needed mods files? Will they need to be deleted manually one by one? or will the installation of the newer versions overwrite the old files?

CaroleAs:

Good news: my host managed to get the password "reactivated". So i am now able to access it, front and back. I put it in maintenance mode for now.

So now i am at the next step of testing on "a live existing site" and my questions are about sequence:

I have printed all the instructions from DrBytes (and lat9).
I want to treat this clone site as a live upgrade so i will be working with "existing files" and existing mods that i don't need (or will need upgrade) so i am unsure about those:

1- when i run the zc_install, will it keep all the images files and download files, and customers/orders info? I assume yes, but need confirmation. If not, what files/folders are "at risk"? Obviously, i'll make a copy of EVERYTHING, in case.

2- how do i deal with outdated or non-longer-needed mods files? Will they need to be deleted manually one by one? or will the installation of the newer versions overwrite the old files?

For the database, the zc_install process (when selecting the operation/action to perform an upgrade) will take all of the existing ZC core data and make the modifications necessary to allow the ZC portions of the database to work with the ZC software version associated with the zc_install.... Therefore, it doesn't delete records, it doesn't specifically prevent things from working provided the software that is associated matches the version to which it is all upgraded... But... It is a database. A backup should be made just before running the zc_install, and to save some time, a backup of the database just after running it... This way, you can restore back to the latest operational data point rather than starting from scratch.

Now... Item 2... I say you're thinking too hard... You have a complete fileset that works with an upgraded database correct?

What changes to the database did you have to make to get that to work?

Take a backup of your database, point your functional files to the database, perform all of the database actions to upgrade the database and then do what is necessary to make the plugins operational... Done...

Ok, so the "what about the old files" thing. Here's a possibility I was glad to come across. Site to be upgraded had a lot of other things associated with it in the root folder. Was able to create a public_html2/ folder that contained all of the other things and the upgraded site. I went ahead and modified the includes/configure.php file and the admin/includes/configure.php file to reflect the site would be located in the public_html folder. I put the site in maintenance mode, renamed the public_html folder as public_html3, then renamed the public_html2 to public_html did the database upgrade, pushed the applicable mysql queries that were needed by various plugins or allowed the auto-installer(s) address it, then navigated the site, took it out of maintenance mode and was done and requested the owner to review the site not only from the ZC portion but the remainder of their operations....

This is why/how the upgrade on the live site should be quick with the most time needed to maybe run through a purchase to validate operation.

Thanks. I will have to re-re-read this slowly, several times! A lot of information for this brain to digest :)

My question about "older plugins" is because some of those i have installed are not compatible with 1.5.5

What changes to the database did you have to make to get that to work?
Maybe i am not understanding correctly but what worked on my test site (not the cloned one) was from a fresh install so no "legacy" plugins. Now, on the CLONED site, i will have those older plugins, just like on the live site, so it is a situation i didn't experience YET, but will. Yes, maybe i am asking question ahead of time, but i don't want to step where i'll mess something (done that enough already).

Take a backup of your database, point your functional files to the database, perform all of the database actions to upgrade the database and then do what is necessary to make the plugins operational... Done...
Something does not click in my head here. I have no clue what you are referring to when saying "point your functional files to the database". And no idea about "upgrading the database". As far as i know, i didn't do anything TO the database but i didn't have operational plugins as i just installed them on that clean install.

CaroleAs:

Thanks. I will have to re-re-read this slowly, several times! A lot of information for this brain to digest :)

My question about "older plugins" is because some of those i have installed are not compatible with 1.5.5

Maybe i am not understanding correctly but what worked on my test site (not the cloned one) was from a fresh install so no "legacy" plugins. Now, on the CLONED site, i will have those older plugins, just like on the live site, so it is a situation i didn't experience YET, but will. Yes, maybe i am asking question ahead of time, but i don't want to step where i'll mess something (done that enough already).

Something does not click in my head here. I have no clue what you are referring to when saying "point your functional files to the database". And no idea about "upgrading the database". As far as i know, i didn't do anything TO the database but i didn't have operational plugins as i just installed them on that clean install.

Yes, you installed them.... If you compared the files that were needed to install them to the files on your server, are all such files still present or did one or the other (typically in the admin) disappear? Did you have to add anything into tools->install SQL patches? Did you have to access phpmyadmin and apply any sql commands? These type things would indicate or suggest a database change.

When you did the zc_install process after getting the database in place by your host, that is when you upgraded the database. If your temporary ZC 1.5.5(e) site is fully functional, then all of the files there work and do what you want. If there is excess "waste" then trim the fat.

The "cloned" site (old site) is basically code to allow accessing the database... You want to update the database and use new files... The old files at that point are unnecessary and basically irrelevant, technically they could be deleted, but if deleted and something goes wrong, then they have to be recovered... Renaming/moving can be so much easier, faster, and a bit more reliable.

What about modifying settings in the admin? did you change anything in the configuration menu dropdown? How about the layout boxes? Any of these modifications touch the database and are database changes.

Doing the CLONE upgrade today.

As i start the upgrade with zc_install, i get this message:

Your configure.php file is an old version and requires updating before we can continue.How do i update it?

For maximum security and compatibility you should be using PHP 5.5 or newer. This installer can proceed, but this is just letting you know that your site will not be PCI Compliant when running out-of-date software.
Something i need to do or ask my host or something else?

Problems with .htaccess support (it is not properly denying access to files that ought to be restricted). [NOTE: If using Nginx, a set of nginx conf files is supplied at the END of zc_install to enable easy rectifying of this situation.]
One htaccess is completely blank (it seemed to have just been added today, although i didn't start the install yet). The other htaccess file on the storetest is the one i had to change to _.htaccess as it included all that code that redirected.

Gzip Extension in PHP is not enabled
What do i need to do and where?

CaroleAs:

Doing the CLONE upgrade today.

As i start the upgrade with zc_install, i get this message:

How do i update it?

Something i need to do or ask my host or something else?

One htaccess is completely blank (it seemed to have just been added today, although i didn't start the install yet). The other htaccess file on the storetest is the one i had to change to _.htaccess as it included all that code that redirected.

What do i need to do and where?
If not mistaken, when presented with a message during the zc_install process, supposedly clicking on the item will provide more information. The configure.php file update/upgrade: just telling you that it's going to change as I recall (I don't tend to worry unless I am prevented from moving forwards.) php version, should be editable in your cPanel if you have one, otherwise yes some sort of contact whether person to person or review of their instructions for their service.

I thought I mentioned it, maybe just thought it, but you may want to restore that htaccess file to begin with a period (still rename it). Typically period starting files remain hidden. An underscore at the beginning removes it from the hidden "group". A blank htaccess is not necessarily a problem. Unexpected file(s), yes that is a concern worth following up on.

Gzip extension: again I think clicking on it, but by now you've likely also progressed or tried to. As to folders not present? Umm. Sure that you have the right version of ZC present? The files should be there as basically provided, though I will leave out the docs folder and a few other things that are to be deleted after installation to just save some time.

Thanks.

If not mistaken, when presented with a message during the zc_install process, supposedly clicking on the item will provide more information.
Yes, that is what it says on that page, yet clicking on any of those message does not do anything. Maybe i'll check with a different browser (i am using Chrome)?

The configure.php file update/upgrade: just telling you that it's going to change as I recall (I don't tend to worry unless I am prevented from moving forwards.) php version, should be editable in your cPanel if you have one, otherwise yes some sort of contact whether person to person or review of their instructions for their service.
Since it says "Your configure.php file is an old version and requires updating before we can continue." i assumed i was stuck here.

I thought I mentioned it, maybe just thought it, but you may want to restore that htaccess file to begin with a period (still rename it).
Since that one .htaccess file i have includes code that redirects, putting that file back might block my access again, wouldn't it?
It has this:

Options +FollowSymlinks
RewriteEngine on
RewriteCond %{REMOTE_HOST} !^142\.167\.20\.37

RewriteRule (.*)$ http://www.creationcassel.com/store [R=301,L]

Should i just edit this one? Or leave a totally blank one? But when the message says "Problems with .htaccess support (it is not properly denying access to files that ought to be restricted).", i assumed it needed something to properly deny access to files

Gzip extension: again I think clicking on it, but by now you've likely also progressed or tried to.
Yup and nothing happens so i have no clue how to fix it.

Now, i had instructions from lat9, that says "Copy the Zen Cart instalation directory (/zc_install) to the root directory of your live site (/zc_install)". I understood to place ONLY that directory and NOT all the other folders (assuming they were already existing in the "live" site). So, now i see that the "live" site didn't have those folders, so i'll copy them.

CaroleAs:

Thanks.

Yes, that is what it says on that page, yet clicking on any of those message does not do anything. Maybe i'll check with a different browser (i am using Chrome)?

Since it says "Your configure.php file is an old version and requires updating before we can continue." i assumed i was stuck here.

Since that one .htaccess file i have includes code that redirects, putting that file back might block my access again, wouldn't it?
It has this:

Options +FollowSymlinks
RewriteEngine on
RewriteCond %{REMOTE_HOST} !^142.167.20.37

RewriteRule (.*)$ http://www.creationcassel.com/store [R=301,L]

> Should i just edit this one? Or leave a totally blank one? But when the message says "Problems with .htaccess support (it is not properly denying access to files that ought to be restricted).", i assumed it needed something to **properly deny access to files**
> 
> 
> Yup and nothing happens so i have no clue how to fix it.
I didn't say restore the filename, I said make it start with a period... 

._.htaccess would be fine.

Gzip isn't required. It's a notification.
The message about the nginx aspect is addressed as saying to do something later (not required to do anything now).
The update/upgrade of the includes/configure.php in my experience automatically happens as part of the process.

Tell me, are you using the ZC 1.5.5 zc_install on your old store files? Or is the only remnant of the old store the includes/configure.php and admin/includes/configure.php files?

Can you make a screen shot of where you're at and what your seeing obscuring anything that is sensitive?

php version, should be editable in your cPanel if you have one,
Yes i have one, but any direction where i would edit that?

Tell me, are you using the ZC 1.5.5 zc_install on your old store files? Or is the only remnant of the old store the includes/configure.php and admin/includes/configure.php files?
Yes, i am using the "storetest" and following all lat9's instructions.

Can you make a screen shot of where you're at and what your seeing obscuring anything that is sensitive?

At the bottom, was "Update the config file".
Thinking it would point me to what i needed to update, but i guess it is updating it (or trying to).
Now, i get a green "warning" saying this:

"An existing configure.php file was found. However your database seems to be current. This suggests you are on a live site. Proceeding with Install will wipe out the current database contents! Are you sure you want to install?"

So yes, it is a "live" site (just a cloned version). Is that the normal step? I thought it was supposed to use the current database???

Now the options are **Clean install **or Refresh

CaroleAs:

At the bottom, was "Update the config file".
Thinking it would point me to what i needed to update, but i guess it is updating it (or trying to).
Now, i get a green "warning" saying this:

"An existing configure.php file was found. However your database seems to be current. This suggests you are on a live site. Proceeding with Install will wipe out the current database contents! Are you sure you want to install?"

So yes, it is a "live" site (just a cloned version). Is that the normal step? I thought it was supposed to use the current database???

Now the options are **Clean install **or Refresh
This all depends on to what database the includes/configure.php was/is pointing. If the database has previously been updated (can find info in the version table), then the referenced database has already been upgraded and the only "alternative" is to start anew (wipe out).

While the installer does/will rewrite the configure.php files as necessary, it basically only touches the database. So when say "clone" it needs to be that of an "old" database and a new fileset.

What's the DB_DATABASE and DB_PREFIX from each site?

For this temporary "staging"/testing setup, I recommend:

live site:
DB_DATABASE = whatever the database name is on the live site
DB_PREFIX = whatever

test/staging site:
DB_DATABASE = something DIFFERENT than what the live site has; you do NOT want to actually use the "real" live site's database here, or you'll mess up your real data.
DB_PREFIX = same as the live site, so that the data you import into the temporary database will have the same table-names. (Prefixes were originally used to allow multiple different stores in the same database, and so the prefix denotes "which" set of data to use. The key: always use the same DB_PREFIX everywhere.)

When zc_install gives you the warning you quoted, it means it's finding tables that have the correct "new" structure that doesn't require updating. This usually means you've set DB_DATABASE to incorrectly use the "live" db instead of the temporary/test db. Or it means you're using a different prefix, which means you've got an extra set of tables, with different prefixes, in your db.

Or you're running it on a site that's already been upgraded. If this is intentional, then, well, you already know you're doing that.

CaroleAs:

Yes, i am using the "storetest" and following all lat9's instructions.

Still not sure which "instructions" are being followed as don't really see any such in this thread after scrolling through the previous 13 pages. I do see, and have fallen "victim" to the "multiple" admin directories issue above. I didn't "see" the message and couldn't continue on. Once I selected the desired admin, it was all ok, but I also had two of the same version of admin (one the ZC standard admin directory the other MY_SECRET_ADMIN). So curious if you were in the same boat, but unsure based on the information provided. I have seen that she does upgrades possibly differently. I like to prevent excess files from getting involved and causing odd behavior when I just had a fully functional site in the test environment with all the needed fixin's.

DrByte:

What's the DB_DATABASE and DB_PREFIX from each site?

For this temporary "staging"/testing setup, I recommend:

live site:
DB_DATABASE = whatever the database name is on the live site
DB_PREFIX = whatever

test/staging site:
DB_DATABASE = something DIFFERENT than what the live site has; you do NOT want to actually use the "real" live site's database here, or you'll mess up your real data.
DB_PREFIX = same as the live site, so that the data you import into the temporary database will have the same table-names. (Prefixes were originally used to allow multiple different stores in the same database, and so the prefix denotes "which" set of data to use. The key: always use the same DB_PREFIX everywhere.)

When zc_install gives you the warning you quoted, it means it's finding tables that have the correct "new" structure that doesn't require updating. This usually means you've set DB_DATABASE to incorrectly use the "live" db instead of the temporary/test db. Or it means you're using a different prefix, which means you've got an extra set of tables, with different prefixes, in your db.

Or you're running it on a site that's already been upgraded. If this is intentional, then, well, you already know you're doing that.

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?

mc12345678:

Still not sure which "instructions" are being followed as don't really see any such in this thread after scrolling through the previous 13 pages. I do see, and have fallen "victim" to the "multiple" admin directories issue above. I didn't "see" the message and couldn't continue on. Once I selected the desired admin, it was all ok, but I also had two of the same version of admin (one the ZC standard admin directory the other MY_SECRET_ADMIN). So curious if you were in the same boat, but unsure based on the information provided. I have seen that she does upgrades possibly differently. I like to prevent excess files from getting involved and causing odd behavior when I just had a fully functional site in the test environment with all the needed fixin's.

Yes, i do have two admin directory. But that was intentional and the one indicated is the correct one. That part is understood.
Now, it is the database that is freaking me out. Their mention of "wiping it clean" is obviously not what i want!

More searching and i realized that those installation attempts generated log files.

I just generated one log and here is where it mentions a failure (everything else passed):

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

I don't know how to interpret this. Can you?

CaroleAs:

More searching and i realized that those installation attempts generated log files.

I just generated one log and here is where it mentions a failure (everything else passed):

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

> 
> I don't know how to interpret this. Can you?

Its kind of back to what was previously identified: GZip disabled. I'm a little surprised that that is all that was logged at all, though I guess reading between the lines, there were other entries in the log and it was just this one that failed...

mc12345678:

Its kind of back to what was previously identified: GZip disabled. I'm a little surprised that that is all that was logged at all, though I guess reading between the lines, there were other entries in the log and it was just this one that failed...

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

So how do i get this GZip enabled?