Problem with accents on new server

Thursday 25 January 2007 12:49:31 am

Probably a problem with the charset configuration. Check the charset of the db tables and your eZ publish config on the old server and the new one. They should match.

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

Thursday 25 January 2007 1:13:54 am

DROP TABLE IF EXISTS `ezapprove_items`;
CREATE TABLE `ezapprove_items` (
  `collaboration_id` int(11) NOT NULL default '0',
  `id` int(11) NOT NULL auto_increment,
  `workflow_process_id` int(11) NOT NULL default '0',
  PRIMARY KEY  (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8 AUTO_INCREMENT=1 ;

It means that my tables are exported in utf8 ?

eZ Publish Freelance
web : http://www.webaxis.fr

Thursday 25 January 2007 4:52:37 am

I've add a similar problem with 4.0 to 4.1

With a lot of pain and iconv, I could come back to something ok.

Look at the utf8 discussions, there was a code published on the forums to ease the conversion between charsets (I think it was written by Kristof).

X+

http://www.sydesy.com

Thursday 03 January 2008 2:23:11 pm

Hello

How do you "recreate" the database. I am having simmilar problems with accented words, the text gets truncated each time it reaches an accented word.

My site was built from zero with uft8 configuration and once online it just wont display the texts as it should....

Please tell me what to do!

Diseño Web Cuba
Web Design Cuba
www.elfosdesign.com

Thursday 03 January 2008 4:07:37 pm

The encoding problems are not only database related. When you move a database, you are most likely to dump into a text file, whose encoding can get damaged easily. It's best if you control that at all stages with a good text editor (under no condition MS Notepad...). Also, manage your data using proper encoding (phpmyadmin for example, for data manipulation). Things were very nasty before and after MySQL 4.1, where UTF-8 support was introduced. But many people still forget to check the previous encoding when changing or upgrading server. Actually, I've experienced several administrators who weren't very interested in differences between 4.0/4.1/5.0, and carefree upgraded their servers, thus destroying entire databases... ;) On one occasion I've also installed eZ at a server where 'SET NAMES utf8' statement was automatically called for all MySQL/PHP connections, which meant double declaration (or something like that...). Even though data was properly imported, multiple characters seemed damaged ;)

--
Company: mediaSELF Sp. z o.o., http://www.mediaself.pl
eZ references: http://ez.no/partners/worldwide_partners/mediaself
eZ certified developer: http://ez.no/certification/verify/272585
eZ blog: http://ez.ryba.eu