Printable View
--- I find nothing to fix or even explain this error. There is little help when clicking to Tools->Server.Code:Your database appears to need patching to a higher level. See Tools->Server Information to review patch levels.
Can someone explain in plain English how to fix this? I have halted all uprades on client ZEN carts until this issue is resolved.
:(
It simply means that the database-version and the Zen Cart PHP files version are mismatched.
So, either you've upgraded the database and not all the PHP files, or you've upgraded the PHP files and not the database.
https://www.zen-cart.com/tutorials/index.php?article=98
I upgraded an older version to 1.3.9h and per instructions did an install with a new database. Then per instructions I did a backup from the old database in order to restore all the products, customers etc.
All the content and the original template are now working and accepting orders but I cannot get rid of that error across the top of every page.
:blush:
Perhaps someone should edit the title for the upgrade.
It says "3 EASY STEPS TO UPGRADE ZEN CART™"
Suggested title. "3 NOT SO EASY STEPS TO UPGRADE ZEN CART™"
:laugh:
Not nice to gouge the hand that feeds your site for FREE...Quote:
Originally Posted by stuffdone
Quote:
what version did you upgrade from please..
????? What does this mean :blush:Quote:
Originally Posted by haredo
1.3.8 to 1.3.9h
You have to run the database upgrade with zc_install only...
I don't understand this?Quote:
Originally Posted by haredo
I used zc_install into a new directory leaving original site untouched. New database.
I then backed up from the old DB to retain products per the instructions? Wrote down all the info for shipping and payment modules as directed.
I am trying to find out how to fix the error message and not lose all the products and customers.
You must RE-RUN zc_install on this new install and select "Upgrade DB Only"Quote:
I used zc_install into a new directory leaving original site untouched. New database.
I am trying to find out how to fix the error message and not lose all the products and customers.
So if your new directory is xxxxdomain/newdirectory - Then you need to insure that the directory and files for zc_install exist and enter
xxxxdomain/newdirectory/zc_install
I get this on screen:
1253 COLLATION 'latin1_general_ci' is not valid for CHARACTER SET 'utf8'
in:
[CREATE TABLE counter_history_clean as SELECT * FROM counter_history WHERE 1 GROUP BY startdate COLLATE latin1_general_ci;]
Please read this thread:
If this is a mandatory change why was it not an option and a warning in the upgrade install giving the choice to make such a change in the first place?Quote:
Originally Posted by haredo
I have a bunch of zen's to upgrade and this is not turning out to be an "Easy Three Step Process"
Is there another upgrade release on the horizon that will address these issues
It is not, unless somewhere along the way, you or someone has change the DB collation from the default as it appears in your caseQuote:
If this is a mandatory change why was it not an option and a warning in the upgrade install giving the choice to make such a change in the first place?
Quote:
Originally Posted by kobra
Is this something my customer could have done via the Zen control panel? I never made any DB changes myself.
I understand the differences between the character sets but have never seen an option at install or other times to select something other than the actual language. If this is something to look for before the upgrade where does one make sure the old matches with the new before an upgrade? Could this check not be part of the upgrade if there are enough people running into the same wall, presenting a fix at the time?
Default is atin1_general_ci
One must do something to alter this
It is not an admin switch
Might be your host configuretion
Quote:
Originally Posted by kobra
Host configuration? Can you be more specific so I can find what may have caused this before attempting repair and application to a number of other Zen carts on my server?
For the server/host in questionQuote:
Host configuration? Can you be more specific so I can find what may have caused this before attempting repair and application to a number of other Zen carts on my server?
Do a test install and check the DB collation
If not latin1_general_ci then they have something set
How is this "They" you keep referring to. Who has what set?Quote:
Originally Posted by kobra
I am the host. My server. Not sure what you want me to check.
This is the test install and the DB check is why I have the error.
You state this
But you did this replacing the default tables with those from the backupQuote:
This is the test install and the DB check is why I have the error.
What I am stating is look at the default collation of a fresh inatallQuote:
I then backed up from the old DB to retain products
Did you install and configure the LAMP stack yourself'?Quote:
I am the host. My server.
If not, you are only the host in name only
Check the my.cnf configuration for the server
How did this enter the conversation about character set? Did I miss a post?Quote:
Originally Posted by kobra
Quote:
Originally Posted by stuffdone
Quote:
Originally Posted by stuffdone
It is where I stated that it might be the host/server configurationQuote:
Originally Posted by kobra
Where when setup there are thousands of variables that can be set
So if you did not do this, then I guess that is the reason you are perplexed
Did you do a test install and look at the "DEFAULT" DB collation before importing any existing DB backup??
Quote:
Originally Posted by kobra
No...there was no instruction I saw to do that in the three step upgrade process or how to do that.
I did not reference any instructionQuote:
No...there was no instruction I saw to do that in the three step upgrade process or how to do that.
Just install ZenCart with a new DB as a test and view through phpmyadmin what the collation is if you want to know is the server config is overuling the default collation
Quote:
Originally Posted by kobra
The new installation went fine...everything worked at that point. The error occurred when restoring to place all the products back in place. We seem to be talking in a circle without a solution to the problem. I think the error confirmed there is a discrepancy but knowing that is not a solution.
Update requires restoring the products and customers etc. from the old database and this seems to be the source of the problem. I did NOT see any option on new install or upgrade to resolve that conflict while updating or restoring from the old.
I don't need to confirm again what is known. I need to know how to fix it while not losing all the products and settings from the prior version.
The other thing that since crossed my mind was to ignore the upgrade instructions and instead, use EasyPopulate to export from the old and import to the new and avoid this instruction to restore from the old version database.
Thoughts?
EP will not get the customer stuff imported
Again, if a stock install is latin1_general_ci
And the DB to be imported is something else then it was changed
You were already provided the solution earlier by haredoQuote:
I think the error confirmed there is a discrepancy but knowing that is not a solution.
http://www.zen-cart.com/forum/showthread.php?t=168872
I am still trying to determine how it was changed? I have a lot of these to upgrade and knowing that in advance might help me see in advance if the others were changed. Perhaps change it back from the CP and do a fresh backup to use with utf8 set in place.Quote:
Originally Posted by kobra
Is this a function in the Zen control panel that could do this? That is the ONLY place any of the users would have available to them to make such a change. I never made any such changes myself so if it was changed the customer has to have done it.
Just fixing this one then running into the same problem for others is not what I am trying to do if I can avoid this error on the rest.
:smile:
OK, maybe Kobra is not getting through...so let me try....
What I haven't seen you answer is the question about what the collation is when you install a stock 1.3.9h by installing it and going and looking in phpmyadmin to see what it says. If it is anything other than latin1_general_ci then the server is set up to create the databases in another collation method. That would be why the older sites are a different collation method from what the zc_installer expects and you get the error when upgrading the databases.
Stating that you are the host doesn't help much if you don't know what your doing when it comes to server administration and being able to test something as simple as what collation method your server creates databases in by default....
Sorry for being blunt but this thread keeps going over the same ground because you are sure somebody must have changed the collation, so apparently have not checked the default......so hopefully I have clarified what Kobra was trying to get you to do....
I just moved to a brand new server with cPanel and had always used Plesk in the past so I am still wandering in the woods when it comes to fining everything in my CP.Quote:
Originally Posted by barco57
I know from looking at the DB for this particular install it shows utf8 until the very bottom line (summary) where is shows swedish?
I am going to ask my SysAdmin for his input into this. I need to know how to determine what problems I may have upgrading ALL of the zen installs, not just this first test case.
Is that a clean install or one of the ones you have to upgrade?
That would have been important information you could have provided earlierQuote:
I just moved to a brand new server with cPanel and had always used Plesk in the past
A default CP config will accept the script DB collation
If these ZenCarts were on plesk there is no telling if it was configured to force UTF8 or not
Unless you still have access to it - - if so, then get off the dime and do a test install there and CHECK the collation
If not - - Get off the dime and check the DB's that you intend upgrading BEFORE you upgrade
You can create "2" installers
One default
One where you edit it for UTF8
ie: thange the DB_CHARSET in /zc_install/includes/installer_params.php to 'utf8' before using zc_install.
Now you can do either
I have that problem too now, only just upgraded from 138a to 139h.
Got the charset error message during upgrade:-
---------
1253 COLLATION 'utf8_general_ci' is not valid for CHARACTER SET 'latin1'
in:
[CREATE TABLE counter_history_clean as SELECT * FROM counter_history WHERE 1 GROUP BY startdate COLLATE utf8_general_ci;]
---------
Although I had set the installer_params.php to accept 'utf8' and "ignore_db_charset" to "TRUE" in the hope these would by-pass the error messages or force the issue.
My database host is set for utf8 on all tables.
Now entering the Admin section and receiving the message to patch the databases to a higher level.
I've already gone through the "3 Easy Steps" - creating a new DB, exporting the contents of the old DB, importing the contents into the new DB moving the entire site folder to a new location, as a test run, altering all configure files and others to reflect the new location, the new db, etc., etc. So my end appears to be fully-functing, but the interaction with the db isn't working and needs a corrective fix.
What and where it is?
I've followed a few threads over the last 18 hours and found no clear, effective answer to the question of correcting the CHARSET and DB issue.
Current database patch level on the cart's admin section reads 1.3.8
I've also tried running zc_install a couple of times to upgrade the database, and back to the [1253 COLLATION 'utf8_general_ci'...] ERROR message.
If the cart is defaulting to 'latin1' and still offers the option to override to 'utf8' then how do we resolve this conflict?
1. Alter source code?
2. Change all the database, creating new ones in 'latin1' format?
The current DB settings include:-
1 . MySQL charset: UTF-8 Unicode (utf8)
2 . MySQL connection collation: utf8_unicode_ci
From an amateur's point of view this is not something I want to be meddling with unless there is no alternative and there are clear instructions, guidelines and safety hats provided.
:wacko:
As latin1_general_ci is the default and yours is utf8 - - it was altered by somethingQuote:
Originally Posted by worldmaker
To continue using the utf8 DB I reiterate - -
Do the following before running the zc_install to upgrade the DB
change the DB_CHARSET in /zc_install/includes/installer_params.php to 'utf8' before using zc_install.
You didn't read my post - I had already made that change in advance of running the upgrade.Quote:
Originally Posted by kobra
Then received the Error message: "1253 COLLATION 'utf8_general_ci' ..."
Then the internal, Admin, message regarding the need to patch the database.
I am now seeking clarification and answers to resolve the latter issue - how to resolve the patch issue given that my databases are in utf8 format.
:clap:
I appear to have solved the problem, thus:-
1 . Using my test database I dropped all the tables, and cleared it for a fresh start on solving this issue.
2 . I copied then edited the copy of the .sql file from the master store database - the export file. Edited using simple text editor, not word processor. And saved back in simple text format as a .sql file.
3 . In this editing I replaced any references made to any character set other than "latin1_general_ci".
4 . Saved this edited sql file under new name.
5 . Used this new, edited .sql file as the import source for the new database.
6 . During the import I carefully selected the "latin1" character set for the process (at least I think that's what that button meant!), because the service provider defaults to "utf8".
7 . Returned to zc_install/includes/installer_params.php and edited out the "utf8" and restored the "latin1".
8 . Returned through browser to begin installation again.
9 . After a little hiccup or two (had to make configure.php file writable), and carefully going through the steps to upgrade - everything went smoothly.
Conclusion
So far, so good.
Back into the Admin section.
No RED WARNING MESSAGES.
No other alerts that I can see on a preliminary glance.
Will now have to check that all the products, etc., etc., are back in place, to reinstall the payment and shipping modules, add others and see what happens.
I'm sure if something goes wrong you'll be hearing from me again, but on this issue - SOLVED IT!
:smartalec:
If your store's products, categories, customers, ez-pages, etc, use ANY non-english-characters, then DO NOT DO THAT, else you'll find all your database content will contain odd annoying symbols where those characters were originally found.Quote:
Originally Posted by worldmaker
If your database contains strictly english-only characters and no extended-character symbols, (ie: not even TM or (c) symbols), then the raw data-hacking approach you described may work if executed perfectly.
USE WITH EXTREME CAUTION!!!!
Thanks for the addition Doc.
It did cross my mind briefly, to warn everyone but it's been a long couple of days and things are getting blurry around here (it's now past midnight) and I have to assume a little common sense out there, don't I, please?
I'm sure to find a problem later, especially with extended characters, but for now, this worked on my test site.
:unsure:
Since I am not a programmer I have decided to not upgrade in the hopes that a future release will contain a more developed upgrade path that includes a solution to this.
I still don't understand why there is this discrepancy since I never did anything to change from UTF8 prior to the upgrades..what ever it is before the upgrades was the default from the original Zen installation. I always use the defaults for everything other than the obvious site-specifics like the DB info and admin information.
Someone kept insisting I changed something related to the UTF8 but I would not know how nor would I have a reason to do so. If there is a method to change that in the prior version then the upgrade instructions need to warn users and add a 4th step to go to the CP and make sure the utf8 is changed prior to trying the upgrade. :mellow:
SUGGESTION
Can someone who understands all of this write a new Upgrade instruction to include this issue and how to avoid it from the start?
It does not appear to be either isolated or rare that others are finding the same errors when trying to upgrade. It seems more logical to prevent others from wading through dozens of posts to just include the necessary steps as part of the documentation to do the upgrade.
If I understood this myself I'd try to post it but I am confused which may have to do with my advancing years and desire for a nap :laugh:
You might BUT it may be a mysql default set by your host to only use utf8Quote:
Originally Posted by stuffdone
Something then to open with your host
Yes, so many comments on this subject floating around, but our hard-working programmers, all volunteers, can't be everywhere at once. It has crossed my mind to write something but the best I could do was the previous note offering one solution and how to do it, I haven't the time for more (struggling with other problems and relearning everything).Quote:
Originally Posted by stuffdone
However, I did upload my new cart with the edited (export).sql file as I noted above, only this time I tested editing the (export).sql (that's the file exported from the working source database) for "utf8" instead of "latin1" and switched the "zc_install/includes/installer_params.php" to favour "utf8" and had no trouble upgrading at all. This makes my db ready for the next major upgrade when the cart shifts to the new improved model.
Most of it can be done in a plain text editor, if you're language pack is not radically off the mainstream.
As DrByte recommends, this ought to be done with GREAT CARE, and I suggest creating a new separate test database and site first before running a full upgrade to your new cart. And editing a copy of your .sql files not the original export.
:lookaroun
You could try editing /zc_install/includes/functions/general.php on line 150, changing this:to this:Code:$collateSuffix = ' COLLATE ' . DB_CHARSET . '_general_ci';
... and see if that gets around the odd collation error message you were seeing on the CREATE TABLE step.Code:$collateSuffix = (strtoupper($param[3]) == 'AS' || (isset($param[6]) && strtoupper($param[6]) == 'AS')) ? '' : ' COLLATE ' . DB_CHARSET . '_general_ci';
I will give this all a good read and a test once I get some projects out of my hair ( opps...no hair ).
I want all the good programmers involved to know how much I do appreciate their work and how much I like Zen cart. I am just currently frustrated by an upgrade ! :smile:
I have done all the updates as above (in earlier posts) but I am still getting the...
NOTICE: The website is currently Down For Maintenance to the public
Warning Your database appears to need patching to a higher level. See Admin->Tools->Server Information to review patch levels.
Messages and cannot turn them off.
I upgraded from 1.38 to 1.39h
Here is my PATCH Level message...
Zen Cart 1.3.9h
Patch: 1::
Database Patch Level: 1.3.9h
Which means I am patched, yes?
And yet I am getting the ...
Your database appears to need patching to a higher level. See Admin->Tools->Server Information to review patch levels.
On the home page still.
Addendum - Interestingly, my BACK END Admin in my ZEN CART says everything is normal and everything is up to date.
Yet Homepage says: Down for maintenance - Update Database.
Is this simply a message I can switch off somewhere?
admin panel/ configuration/ website maintenance/ Down for Maintenance: ON/OFF
Nope -- set as FALSE.Quote:
Originally Posted by haredo
Backend reports all normal, all patched and on-line.
Cleared browser cache a couple of times as well.
Will happily give you an admin account to poke around.
Thanks!
Note attached image...
I sent you a PM,
After doing the database-upgrade via zc_install, you need to go into your admin area and remove-and-reinstall all your payment and shipping modules. This is documented in the upgrade instructions in the /docs/ folder of the Zen Cart files. After you've done that, you can turn off the down-for-maintenance by going to Admin->Configuration->Website Maintenance and setting Down For Maintenance to False.
Yes - did that too. :-)Quote:
Originally Posted by haredo
I love a good Zen Cart challenge.
Look like you have not upgraded the files properly..
When I go to tools/ template selection and switch back to classic contemporary green I get the same page... NOT GOOD
You need to retrace your paths on the upgrade process.. Sorry
Quote:
Originally Posted by colin99
Looks like your /admin/includes/configure.php is pointing to a different set of database credentials than your /includes/configure.php is.Quote:
Originally Posted by colin99
They need to have the SAME settings for all the DB_xxxxxx parameters, else they're showing you completely different data.
And, remember, if the configure.php file is read-only, you won't be able to upload/edit it without making it writable first.
Ah! I have a DEV DB running at the same time.Quote:
Originally Posted by DrByte
Eep!
My bad - all well now.
Good work ZEN Folk
I have been ZENNING so long now I should try and help out a bit too.
I have tried another upgrade following step by step and have given up. Changing to Virtuemart. ( Sept 2011 )
ZEN developers really need to work on making upgrades easier or write better documentation.
Sorry...while I do appreciate the work put into the actual product and used to love it, when my site using the old version keeps getting hacked due to security holes and I spend hours trying "three easy steps" and still cannot get an upgrade to take it is time to cut my losses ( time and labor and downtime ) and just make a change to something easier to maintain.
I would love to come back to ZEN if/when an auto-update function is developed.
And yes...when I exported my old SQL both that and the new DB are encoded UTF-8 according to phpMyAdmin
:(
[FONT="Georgia"]1253 COLLATION 'latin1_general_ci' is not valid for CHARACTER SET 'utf8'
in:
[CREATE TABLE counter_history_clean as SELECT * FROM counter_history WHERE 1 GROUP BY startdate COLLATE latin1_general_ci;][/FONT]
Sounds like you didn't apply the fix I suggested earlier in this thread. Here's the link: http://www.zen-cart.com/forum/showpo...4&postcount=40
I am hosted on GoDaddy. I had to upgrade to a new server in order to upgrade from 1.3.8a.1 to 1.3.9h. That took a few days and it was all done today.
I had alrady backed up all my databases before starting the process. (I have several carts installed.) OK- one at a time.
I started with one cart today. I uninstalled it... thru Godaddy uninstall....but I SAVED the database... AND GoDaddy saves my custom files on the uninstall process.
Then I installed the 1.3.9h in the same folder where the old one was. Godaddy creates the new database automatically. Then I changed the two configure files to point to the old database.
Well that was wrong because I was getting the 'Your database appears to need patching to a higher level" message. My site being 1.3.9h and the database 1.3.8
I guess the old database will not work in the new upgrade.
I just changed the configure files back to point to the new database. Rats. I really don't want to individually upload over 1000 items into my cart in the new database, but looks like I am stuck.
If I get into my new SQL acct. and import the databse will that work? ... or will it just override the new tables and ruin it?
No, because the old databse is still an old version....you need to upload the zc_install folder, import the old db, then go to http://yourdomain.com/zc_install, accept the license, next page scroll to bottom and click the upgrade database......
or you can skip the import old db to the new database, and just point the config files at the old db and run the upgrader....
Thank you.
That is what I though... old is old. It can not work in the newer version.
OK.. lets see if I understand you.
First, I have not used the "zencart install" before (since I am on GoDaddy - I just click and they install) so excuse me for being lost in this area.
So you say to import the db first. Where do I import it to?
Am I to import it into my current SQL (godaddy has my SQL on a different server) - or upload it somewhere in within the cart files?- or zc_install >sql file? Run the upgrader there & then put the file in my sql on the other server? Will it run the upgrader to my SQL file on the other server directly?
What does the upgrader actually do to the files?
If I get it in my head correctly first I can work with it easier.
I sure would like an easy way to import my products and customers info. This sounds easy.