We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 37437
    • 147 Posts
    I just ran a W3C markup validation on a Revolution 2.0.8 site I developed and although the site passed validation, I did receive the following ’warning’ about character encoding:

    Warning Character Encoding mismatch!
    
    The character encoding specified in the HTTP header (utf-8) is different from the value in the <meta> element (iso-8859-1). I will use the value from the HTTP header (utf-8) for this validation


    Any tips on how to correct this issue?

      • 28042 ☆ A M B ☆
      • 24,524 Posts
      You’ve specified a different encoding in your template’s head than what you have set for MODx in the Configuration. MODx sends the page headings according to its configuration settings, while the page’s HTML will be whatever you put in the template. That’s why I always use [(modx_charset)] or its Revo equivalent in my templates.
        Studying MODX in the desert - http://sottwell.com
        Tips and Tricks from the MODX Forums and Slack Channels - http://modxcookbook.com
        Join the Slack Community - http://modx.org
        • 37437
        • 147 Posts
        Susan. Has anyone ever told you that you ROCK? Thanks very much for bringing clarity to the issue. And just for the record, the Revolution syntax is: [[++modx_charset]].

        Here is the tag being used in context:
        <meta http-equiv="Content-Type" content="text/html; charset=[[++modx_charset]]" />
          • 1343 ☆ A M B ☆
          • 2,213 Posts
          Another solution to the problem is to use metax, which handles just about every thing you would want in your header from base, charset, meta, and even rss feeds smiley

            Patrick | Server Wrangler
            About Me: Website | Tweets |  MODX Hosting