ExpressionEngine CMS
Open, Free, Amazing

Thread

This is an archived forum and the content is probably no longer relevant, but is provided here for posterity.

The active forums are here.

Problems with "charset=" being rewritten

December 01, 2010 8:23am

Subscribe [2]
  • #1 / Dec 01, 2010 8:23am

    John Ryan

    51 posts

    Whenever I save my header template, the following markup:

    <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />

    ...gets changed to…

    <meta http-equiv="Content-Type" content="text/html; (anti-spam-charset=)utf8" />

    Is this EE doing this? Or does the problem lie elsewhere?

    It’s keeps screwing up the characters on a site whenever I update the header template, and the only way to fix it is to change it directly in the database.

  • #2 / Dec 01, 2010 4:42pm

    Ingmar

    29245 posts

    Is that literally “(anti-spam-charset=)”? What version and build of EE are you using? This is the first time I’ve seen anything like this.

  • #3 / Dec 02, 2010 5:40am

    John Ryan

    51 posts

    Yes, it’s exactly that, brackets and all.

    It’s ExpressionEngine 1.6.7 - Build:  20090211

    With the following extensions:
    - Category Checkboxes (v.1.1.5)
    - Structure Extension (v.1.1)
    - Clone Entries (v.1.1)
    - LG Better Meta (v.1.9.1)
    - LG Social Bookmarks (v.2.0.2)
    - Textile Editor Helper (TEH) (v.1.1.0)
    - jQuery for the Control Panel (v.1.1.1)

    I’m going to try disabling extensions and trying another few browsers to see if the problem lies elsewhere.

  • #4 / Dec 02, 2010 5:45am

    John Ryan

    51 posts

    I’ve just tried saving the template with and without extensions enabled, and in both Safari and Firefox and it’s still replacing the “charset=” in the same way?

    I guess that only leaves EE or some server setting?

  • #5 / Dec 02, 2010 5:08pm

    Ingmar

    29245 posts

    Definitely sounds like a server issue. A quick web search found users of other systems affected, too (WP, e.g.) although it doesn’t seem to be too common. Ask your host about it, please.

  • #6 / Dec 03, 2010 6:10am

    John Ryan

    51 posts

    Ok, will do.

  • #7 / Dec 03, 2010 9:47am

    Ingmar

    29245 posts

    Very good. Keep us in the loop, please.

  • #8 / Dec 07, 2010 6:49am

    John Ryan

    51 posts

    It turns out this was an issue with the hosting setup. The hosting company explained they had a security library that parses all form data sent to PHP and changes the data if there is something suspicious. They’ve added the paths to EE’s php files to the list of exceptions and everything works fine now.

    Hopefully this will help anyone who comes across a similar problem. It had me stumped for quite a while!

  • #9 / Dec 07, 2010 4:08pm

    Ingmar

    29245 posts

    Thanks for sharing your solution with us. Please post again as needed.

.(JavaScript must be enabled to view this email address)

ExpressionEngine News!

#eecms, #events, #releases