Can't install 4.0.0: UTF8 vs. iso-8859-1 sample DB problem

Author Message

Edward Bradburn

Tuesday 15 January 2008 5:26:15 am

I wanted to test the new 4.0.

I have set up XAMPP and have a MySQL instance running there OK. I then ran the web install wizard.

I am now on the last stage of the install wizard and I have this error:

Warning

The database [cdcol] cannot be used, the setup wizard wants to create the site in [utf-8] but
the database has been created using character set [iso-8859-1]. You will have to choose a
database having support for [utf-8] or modify [cdcol] .

I assume the sample databases are in the wrong format or something?

Otherwise I have chosen a fairly normal install: MySQL Improved, Plain Site, and so forth.

Anyone have any idea if I have done something wrong -- or how this can be worked-around or fixed?

Cheers,

Ed

Kristof Coomans

Tuesday 15 January 2008 7:25:25 am

Hi Edward, welcome to the eZ Community!

When creating a new database for your eZ Publish installation, then specify "CHARACTER SET utf8" behind the CREATE DATABASE sql, as outlined in the documentation: http://ez.no/doc/ez_publish/technical_manual/4_0/installation/normal_installation/installing_ez_publish_on_windows or http://ez.no/doc/ez_publish/technical_manual/4_0/installation/normal_installation/installing_ez_publish_on_a_linux_unix_based_system.
Does it work now?

independent eZ Publish developer and service provider | http://blog.coomanskristof.be | http://ezpedia.org

Edward Bradburn

Tuesday 15 January 2008 7:41:05 am

Hi Kristof,

<b>Update</b>

Ah, OK - I understand it now!

The last step merely offers me all the MySQL DBs on my system! It would - given the root access!

I have now added a database user restricted to one DB and now I only get one DB offered on the last page.

OK - so no bug in the installer, but maybe the docs should be updated to make this fact more obvious? Plenty of people will simply opt for "root" when asked, and then will choose databases that are already in use on their system!

What do you think?

<b>end of update</b>

Thanks for the rapid reply.

I'm not sure what you mean by "creating a new database". I have simply entered the database (root account) access details on the page in the wizard - at no point have I been asked to create a database.

On the last page of the wizard the wizard asks me to choose a sample database for the ezpublish site. It seems to be *these* databases that are not in UTF8 - or I am mistaken somewhere?

I would have no problem creating a database, since I am a fairly experienced MySQL admin - but the wizard seems to want to create (or import) the databases itself. And I of course have no idea where these databases actually are!

For reference, the databases are called: "cdcol", "phpmyadmin", "test" and "webauth".

The MySQL I am running, 5.0.51, has full UTF8 support as far as I can see.

Hope this helps you resolve my query!

Many thanks,

Ed Bradburn

George H

Thursday 17 January 2008 3:56:11 pm

Click the database name and set "Collation" to UTF8-bin. : It Worked for Me

Richard Lundberg

Friday 20 August 2010 7:35:00 am

Hi, I have exactly the same problem on an 4.3 installation. I am running php 5.3 and mysql 5.1.

I have done many previous installations without problem. This is a new server because I wanted to run 5.3, but I can't complete the install because of this error.

I have checked php-myadmin and the relevant settings are listed:

MySQL connection collation: utf8_bin

MySQL charset: UTF-8 Unicode (utf8)

so I do not know why it is saying the database is created using iso-8859-1

Any help appreciated

www.peakm3.com

Doug Brethower

Friday 20 August 2010 1:55:14 pm

Have you tried specifying collation when creating the new database?

Something like:

CREATE DATABASE `ez430` DEFAULT CHARACTER SET utf8 COLLATE utf8_general_ci;

Doug Brethower
Apple Certified Technical Consultant, Southwest, MO USA
http://share.ez.no/directory/companies/lakedata.net

Powered by eZ Publish™ CMS Open Source Web Content Management. Copyright © 1999-2014 eZ Systems AS (except where otherwise noted). All rights reserved.