It can be a real PITA when it comes to UTF-8. I've noticed, for
example, that PHPMyAdmin fails to include a line, 'SET NAMES utf-8' in
the dumps it produces, which can mean that MySQL will b0rk the text
when it's read in.
On Wed, Aug 26, 2009 at 6:18 AM, danfreak<freakclimbing@gmail.com> wrote:
>
>
> Cheers guys,
>
> well my problem is mainly related to the DB entries.
>
> I'm deploying my application to the production server with capistrano,
> pulling the application from a github (git) repository.
>
> --------------------------------
> I have teh following DB config:
> --------------------------------
> var $default = array(
> 'driver' => 'mysql',
> 'persistent' => true,
> 'host' => 'localhost',
> 'login' => 'root',
> 'password' => 'psw',
> 'database' => 'test-db',
> 'encoding' => 'utf8'
> );
> --------------------------------
> In my config/core.php I have:
> --------------------------------
> Configure::write('App.encoding', 'UTF-8');
>
>
> --------------------------------
> My HTML header is:
> --------------------------------
> <?php echo $html->charset('utf-8');?>
>
> The only difference I noticed between the dev and production servers
> is with regard to case handling: dev server is case insensitive, while
> the prod server is case sensitive.
>
> Dan
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "CakePHP" group.
To post to this group, send email to cake-php@googlegroups.com
To unsubscribe from this group, send email to cake-php+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/cake-php?hl=en
-~----------~----~----~----~------~----~------~--~---
No comments:
Post a Comment