We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 11694
    • 13 Posts
    Since there is a quite big issue with utf-8 encoding we should talk...
    I used the version 0.9.6.3-RC2
    And i’ve realised that in the backend neather chanks, paramters of template variables, or snippets are saved correctly interms of utf-8 (if i right in greek iget back huh??)
    Sofar i hacked the core as such:
    in the file save_tmplvars.processor.php i’ve changed:
    mysql_query($sql);
    to
    $modx->dbQuery($sql);
    and it worked fine for tv varibles sofar
    Now i’m in the process on hacking the rest in order to store correctly chanks and snippets

    So does anybody nows if i’m dooing the right thing??
    Is there another version that works better?



      • 6726
      • 7,075 Posts
      There has been a lot of discussion about encoding. There is no need for a hack or fix. The one most people refer to in the forums forces the use of SET NAMES.

      You should check this discussion for a better understanding why modx defaults to SET CHARACTER SET, and how to switch to SET NAMES when your environment requires it (when run in advanced mode, the installer will let you choose).

      I am 95% sure your problem comes from your settings, re-running the installer in advanced mode should help you figure out where the mismatch is.
        .: COO - Commerce Guys - Community Driven Innovation :.


        MODx est l'outil id
        • 22303 MODX Staff
        • 10,725 Posts
        This is actually related to http://svn.modxcms.com/jira/browse/MODX-489 I believe which was fixed post RC2.
          • 11694
          • 13 Posts
          Guys thanks a lot for your help now everything works fine (as far as i’ve tested).
          The problem was that when i’ve installed the platform i had to set "Names" to utf-8 instead of "Character Set". I thought that it was all the same.