Need help to do an upgrade from 1.5.0 to 1.5.5

mc12345678:

The community is helpful to those that help themselves and when able others. You're doing a fine job and thank you for answering that question with the detail provided.
Thanks.

mc12345678:

Two things I see right now and it is something you will need to come to understand to successfully update your live store when the time comes.

1. Where did the third database prefix come from? (ie. Expect that one set of tables came from the auto-installer, one definitely came from your live site, but there is a third. Does the database in you site have 2 sets of tables (2 prefixed groups) or just one?)

If two, again back to drbyte's previous comment: look at the includes/configure.php file of your live site for DB_PREFIX. That value is what should be in your upgrade site in the same file. (don't change it without further discussion is a recommendation at this point)
I can only guess that this other prefix came from the installer. At no point in the process was i asked to name a DB (i was expecting that). I was only asked to give a username and password for the admin login. That was all.

To answer your question, yes, i see two sets of tables: one starting with zen_ prefix (just like the one on the live site) and one with zenng_ prefix, which i can only guess came from that installer.

mc12345678:

The other issue is that the three other upgrade steps did not get performed. Namely 1.5.0 to 1.5.1, 1.5.1 to 1.5.2 and 1.5.2 to 1.5.3.

So question is when doing the database upgrade today, we're those three checkboxes marked (automatically) or were they manually unchecked, etc... ie. why were they omitted in the process. Part of the answer to that may lie in a question previously asked about what plugins had been installed in the "old" database.
When i ran the zc_install, this morning, i remember only TWO boxes, one was 1.5.3 > 1.5.4 and 1.5.4 > 1.5.5
There were no other boxes. Since i knew i had 1.5.0, i obviously was expecting other options.

mc12345678:

Minor "background". The installer spot checks some database characteristics to identify the "need" of each upgrade step. If the sought data is found then none of the other changes are made. Therefore a plugin may have updated something in the database to cause the installer to skip an upgrade step.
Any way to know? Or any point in finding out? Or maybe the better question: what to do about it?

I am all ears!

dbltoe:

There's probably no need to wipe the slate and start over but you may need to read posts 10 and 11 at https://www.zen-cart.com/showthread.php?219730-Zen-Cart-v1-5-5e-released!&p=1326914#post1326914.

It just might be that one of those changes (since it involves database function) might fix your problem.
I am wondering if it is something i should do now or something i should have done then.
But again, right now i am seeing double with that double set of tables!

Still both issues to discuss:

1. "Seeing" the two sets of tables, which database? Old aka live? Or new/temp database or both?

2. So, yeah, could go figure out exactly why, but as you did with the questions, let's jump to the end of what to do about it...

My first off-the-cuff thought was to just implement all of the changes that those three would have right now. But... then I realized, duh... these should be done in sequence not randomly...

So... two things to do to approach this smartly now and will make your goal easier to reach. Ask your host to import the database again or as dbltoe suggested work through your cpanel or other tools to do it yourself. Then you will want to apply the missing patches through the phpmyadmin one version at a time for the three missing steps.

Then run zc_install to upgrade from 1.5.3 to 1.5.5e latest version.

Note: because you have a database prefix in use from your old store, you have two options. Either update/modify the three missing step "files" to include the prefix, or you get the prefix removed from the upload/backup. Whatever is done, remember that this all needs to be duplicated again, so you'll want to do one at-a-time. I guess, a third option would be to force the installer to go ahead and execute the three steps anyways... that's likely the easiest route and easily reproduced.... I know there are some that have recently done that. I need to look into the installer again to offer the necessary advise. In the mean time maybe that database transfer can be worked on.

1. "Seeing" the two sets of tables, which database? Old aka live? Or new/temp database or both?
   The one with the zen_ prefix seems identical to the one from the live store. I guess that is the one they imported from the export i made from the live site. Currently, on the test site, i see what i would see in the live store (products, categories, descriptions, etc.). Maybe the zenng_ database was the one created with the auto-install, but then, when i asked my host to import the zen_ database, shouldn't have that replaced the zenng_ one? Should i just remove one? if so, which one? Or remove both and re-import the zen_ one?

Ask your host to import the database again or as dbltoe suggested work through your cpanel or other tools to do it yourself.
Not sure i can rely on my host ;)
I had contacted them this morning for something else and asked if there was a way to have access to import a larger file, considering that i will need that (i think) when i finally do the live store, so they sent me to this page, which should allow that (not to figure out how easy that is, one step at the time).

So, step 1 - i'll go do that

Then you will want to apply the missing patches through the phpmyadmin one version at a time for the three missing steps.
Unfortunately, i don't know what you mean by "applying the missing patches"

Then run zc_install to upgrade from 1.5.3 to 1.5.5e latest version.
Just like i did this morning i guess?

Darn, i can't edit my post for clarification:

I see one DATABASE, called creat419_zenc598. Inside that ONE database, i see two sets of tables. The one with the zen_ prefix seems identical to the one from the live store. I guess that is the one [set of tables/database] they imported from the export i made from the live site. Currently, on the test site (front and backend), i see what i would see in the live store (products, categories, descriptions, etc.). Maybe the zenng_ set of tables were the ones created with the auto-install, but then, when i asked my host to import the zen_ database, shouldn't have that replaced the zenng_ tables? Should i just remove one set of tables? if so, which one? Or remove both and re-import the zen_ one?

CaroleAs:

Darn, i can't edit my post for clarification:

I see one DATABASE, called creat419_zenc598. Inside that ONE database, i see two sets of tables. The one with the zen_ prefix seems identical to the one from the live store. I guess that is the one [set of tables/database] they imported from the export i made from the live site. Currently, on the test site (front and backend), i see what i would see in the live store (products, categories, descriptions, etc.). Maybe the zenng_ set of tables were the ones created with the auto-install, but then, when i asked my host to import the zen_ database, shouldn't have that replaced the zenng_ tables? Should i just remove one set of tables? if so, which one? Or remove both and re-import the zen_ one?

Will be responding to both messages, but one at-a-time.

So, the zenng_ prefix set sounds like it did likely come from the auto-install. The import of the tables from one database to another do not remove the tables that otherwise exist and depending on the method of transfer and/or imported, may or may not replace existing tables of the same name.

So. Should you remove the new install tables? Eh... not too important right now, but keep it on your list of things to do later. For now it serves as a possible "mostly" correct install to which you could always revisit.

Now, the part of "importing" the tables again. If you follow the instructions available in the FAQ, then the import of the old/live tables will replace the tables of the same name. So you don't have to do anything additional to them. (ie. One less step).

Important part is working through the existing suggestion of copying over the old database to the new database again (and maintaining a copy of the live site just in case)

CaroleAs:

Not sure i can rely on my host ;)
I had contacted them this morning for something else and asked if there was a way to have access to import a larger file, considering that i will need that (i think) when i finally do the live store, so they sent me to this page, which should allow that (not to figure out how easy that is, one step at the time).

So, step 1 - i'll go do that

Unfortunately, i don't know what you mean by "applying the missing patches"

Just like i did this morning i guess?
That's ok about not knowing how to complete what I described, I kind of didn't want to overload with things in one single post. :)

That said, I still think it would be faster, easier, more productive to force the installer to try to run them instead of possibly making any number of mistakes in trying to alter the upgrade scripts. Also, the installer makes logs that can be reviewed for any modifications to the script that may be necessary as a result of forcing the execution. Plus it would allow you to concentrate on more important things. :)

Just contacted my host because their explanation of how to import a larger database was more scary then anything. And this time, the tech (more knowledgable than the previous ones), cloned my live site DB into the new install after deleting the new one completely (instead of an import). So now, i have only ONE set of tables, with the same prefix as my live site. Everything is the same (even the login).

So now, i am back to the initial db import that is complete.

In the version history now, i see this:
Zen Cart 1.5.5e
Database Patch Level: 1.5.0
v1.5.0 [2012-02-23 07:42:30] (Version Update 1.3.9->1.5.0)
v1.3.9h [2011-01-27 15:29:47] (Version Update 1.3.8->1.3.9h)
v1.3.8 [2009-02-13 04:51:56] (Fresh Installation)
v1.3.8 [2009-02-13 04:51:56] (Fresh Installation)

From what i understood, i did:

• copy the zc_install folder
• ran the zc_install in my browser
• chose update
• this time it gave me 5 upgrades, i kept them all checked
• now the version history shows as:
  Zen Cart 1.5.5e
  Database Patch Level: 1.5.5
  v1.5.5e [2017-08-24 16:04:10] (Version Update 1.5.4->1.5.5e)
  v1.5.4 [2017-08-24 16:04:09] (Version Update 1.5.3->1.5.4)
  v1.5.3 [2017-08-24 16:04:09] (Version Update 1.5.2->1.5.3)
  v1.5.2 [2017-08-24 16:04:09] (Version Update 1.5.1->1.5.2)
  v1.5.1 [2017-08-24 16:04:08] (Version Update 1.5.0->1.5.1)
  v1.5.0 [2012-02-23 07:42:30] (Version Update 1.3.9->1.5.0)
  v1.3.9h [2011-01-27 15:29:47] (Version Update 1.3.8->1.3.9h)
  v1.3.8 [2009-02-13 04:51:56] (Fresh Installation)
  v1.3.8 [2009-02-13 04:51:56] (Fresh Installation)

Yay!!!

And the warning is GONE.
Now, i have a red warning that the site is showing in maintenance to the public. Is that normal? If so, i am all set to go (for now).

If i am good to go, i have another more general question that will pertain to all my mods afterward.

In many cases, there are instructions to change the MY_TEMPLATE name to the actual template i am using. In the test site, I am not using anything other than the default, so in that case, what is the name i should use to replace MY_TEMPLATE? Is it "classic" (which seems to show everywhere) or "template_default" or all of the above?

One minor reason i wanted this upgrade was for an opportunity to have a responsibe theme (to please Google). But, i don't like those new themes. My audience is quite used to the old looks and the new ones are way too different. So I might just tweak the default theme (there is still a lot of customization that can be done!)

Yup.

Initiate an upgrade and the system "locks" down to prevent changes to the database during the upgrade.

The normal suggestion though would be to place it in maintenance mode first then start the upgrade. This way the files and changes made to them will not affect the database in any way. Once you have this process down including all of the things you are going to do to make it all look and act like you want, you will want to be able to rapidly repeat for the actual upgrade. By repeat I pretty much am referring to what changes need to occur to the database. The files in general will be as modified to get the test site you want.

Hope that makes sense, if not please try to explain what you understood and ask about what you didn't. :)

Hope that makes sense, if not please try to explain what you understood and ask about what you didn't. :)
I think I understand but I'll have to come back to it when the time comes. Right now, I am doing a "dry run". Figuring out what I have to do, what mods I will need (some change, some might no longer be compatible, some might replace older ones, etc.), how to install them (better test than sorry), and take notes of everything I need to do, steps, files, etc. so that it will be faster when the time comes for the real deal. :)

CaroleAs:

If i am good to go, i have another more general question that will pertain to all my mods afterward.

In many cases, there are instructions to change the MY_TEMPLATE name to the actual template i am using. In the test site, I am not using anything other than the default, so in that case, what is the name i should use to replace MY_TEMPLATE? Is it "classic" (which seems to show everywhere) or "template_default" or all of the above?

One minor reason i wanted this upgrade was for an opportunity to have a responsibe theme (to please Google). But, i don't like those new themes. My audience is quite used to the old looks and the new ones are way too different. So I might just tweak the default theme (there is still a lot of customization that can be done!)
Save yourself trouble and plan now.

Having an existing functional, untouched template offers a comparison point to which to return if needed. Ideally you copy (clone) the template of choice and from there make changes to it. There's a FAQ also on the template override system as well as a "plugin" (document containing information about the override system that does not get installed to your store).

There are cases of installing things to the template_default directory, but generally speaking if the file already exists as part of the original fileset AND the file exists in a location where it can be overridden, it is or can be a better idea to place it in the template override folder. There's a lot of discussion of this throughout the forum, and some more so that ZC 1.6.0 is firming up and it looks like a ZC 1.5.6 is just around the corner. With all of the changes in php (unrelated to the designers/maintainers of ZC) plugins are being updated to remain functional and so "everyone" is trying to put their best foot forward in keeping the functionality.

and it looks like a ZC 1.5.6 is just around the corner.
Oh no!!! ;)

OK so following your suggestion, i should find a template now, tweak it now so i can also use it later. Ok, makes sense.
Now, i see in my files that i downloaded trublu template a long time ago and i remember changing the name to cc in my installation (not sure why, maybe following some instructions at one point??) I see it is still available on the site but nothing recent. How do i know if it will be responsive? Unless it is just a matter of zencart 1.5.5 having to be responsive and the theme will just follow?

You can use lat9's Clone a Template to clone the responsive_classic template. None of the others are responsive so, you'd be adding another large layer of work if you didn't. I'd suggest cloning BEFORE making changes

Once you clone the responsive, you may want to look at our Color Change Mod. It makes color selection far easier when tweaking the site.

You can use lat9's Clone a Template to clone the responsive_classic template. None of the others are responsive so, you'd be adding another large layer of work if you didn't. I'd suggest cloning BEFORE making changes
So, the "responsive_classic" template is installed by default, and by cloning it, I would be creating my "own" version, correct?

yep
:yes:

Then, I must be missing something.
I downloaded the plugin (thanks lat9).
Checked the instructions and there is only a list of files to copy. Nothing else.
Where do I indicate what template I want to clone? Am I supposed to run something?

CaroleAs:

I think I understand but I'll have to come back to it when the time comes. Right now, I am doing a "dry run". Figuring out what I have to do, what mods I will need (some change, some might no longer be compatible, some might replace older ones, etc.), how to install them (better test than sorry), and take notes of everything I need to do, steps, files, etc. so that it will be faster when the time comes for the real deal. :)

Ultimately when it comes time for the real deal, the transition should/could be smooth. Plugins that have an auto-installer hopefully will automatically run and upgrade the database to contain what is needed to maintain operation of the plugin, those that have sql commands to be run could be combined into a single "file". If you have adjusted admin configuration settings to something specific you could add those changes to your file or just re-perform the change(s). But the files... they should be as desired/needed so that all you have to do is repeat database/admin changes. This is not exactly the time to modify say product descriptions other than to "learn" what is needed to be done to the live site. Goal right now in my opinion (everyone has one) is to establish the site as functional to the extent needed to maintain operation. With regards to your template and a possible change in look, let your customers know what good/big things you're up to. They may appreciate the change, at least when it comes they will know about it and won't be surprised. Unannounced change can raise questions about why or cause to question what else is going on that hasn't been discussed and how it might impact them, etc...

CaroleAs:

Oh no!!! ;)

OK so following your suggestion, i should find a template now, tweak it now so i can also use it later. Ok, makes sense.
Now, i see in my files that i downloaded trublu template a long time ago and i remember changing the name to cc in my installation (not sure why, maybe following some instructions at one point??) I see it is still available on the site but nothing recent. How do i know if it will be responsive? Unless it is just a matter of zencart 1.5.5 having to be responsive and the theme will just follow?

Again, everyone has an opinion. Mine is that yes if you are going to install plugins that also interface with a template that at minimum you create a separate directory into which the template will be merged/installed, it could be named cc, YOUR_TEMPLATE, whatever you want, it's just that at least for now a plugin's modification is likely best to be in some template override folder.

A template generally affects what visitors see and not the overall operation of the store. Yes ZC 1.5.5 comes with a responsive template, but it also comes with one that is not. It is possible to take a non-responsive template and make it responsive with the responsive template plugin that is in the plugins section. Its possible to take one of the existing responsive templates and work it to be fully functional with ZC 1.5.5, its possible to take an old template and manipulate it to be compatible and then to use the responsive plugin to make it responsive, etc... Every one of these comes with its own lesson to be learned and modifications to be made. Ideally you would be able to see a sample of the template(s) and then select from there of which one(s) you might want to tackle... If the template is from this forum, there is likely to be a thread about it. Suggest going to the end of such thread and working backwards to when the last update was provided to get an idea of what issues exist and how they were overcome and what changes were made from the previous version to get it where it is. Kind of goes with any plugin. Instructions, readmes, docs, _docs etc.. should exist to help describe how to use and/or install the plugin. Suggest reading through those first and then after that doesn't seem to sink in, approaching the forum, reviewing for similar question and when not found, then asking preferably with explanation of what has been done to try to understand and then what is not understood.

I already have some questions for "when the time comes", but there is no point in asking yet, as the information will just get buried.

My plan, for now, was just to get all the functionalities I need to work, and they look to be what I can live with to start. After that, if I need tweaking, I'll have a test platform for it so i can go slowly as time will be available. Right now, i am off work for a couple of weeks so that was my main focus.

For trying other templates, it seems hard as half of those in the repository don't have a demo or preview so it is hard to know what they look like and if they will fit my existing previews and such, which is why, if i can get a site that is similar enough to what i have, I'll be happy.

Now, trying to figure out that Clone a template thing.