strange XHTML errors

  • clayfx

    (@clayfx)


    20 years, 8 months ago

    My theme is valid transitionnal when I valid it by direct input, on the W3C site.

    But when I try to validate it directly by URL, here is the result:

    Contradictory Parse Modes Detected!

    The MIME Media Type () indicated parse mode should be SGML, but the DOCTYPE Declaration indicates XML mode. Using SGML mode based on the Content-Type header.
    Namespace Found in non-XML Document

    Namespace "" found, but document type is not XML!

    This page is not Valid XHTML 1.0 Transitional!

    Below are the results of attempting to parse this document with an SGML parser.

    1. Error Line 7 column 69: character data is not allowed here.

    ...ntent-Type" content="text/html; charset=utf-8" />

    2. Error Line 25 column 88: character data is not allowed here.

    ...'http://krylenko.net/live/2005/09/' />

    Then I tried my theme on another personnal test blogs, and it was valid, but without the content (no posts, no plugins…)!

    http://krylenko.net/live

    I’ve search the web but there wasn’t really nothing about that.

    Thanks.

Viewing 4 replies - 1 through 4 (of 4 total)
  • Lorelle

    (@lorelle)

    20 years, 8 months ago

    I’m not sure but for the first error, set the utf to UTF and move the <title>Live</title> to below your Content-Type reference since the title is above it and it should be below it.

    As for the second error, I haven’t got a clue, but it might fix itself with the rest is fixed. Never know.

    If that doesn’t help, let us know.

    Cyndy Otty

    (@ceo)

    20 years, 8 months ago

    Uhm…I’ve always had it as ‘utf-8’ and had the title above and my code validates at 1.1 – though I can’t see what’s causing the errors in clayfx’s code quite honestly, I don’t think that’s it because doesn’t the title go before meta stuff?

    Beel

    (@beel)

    20 years, 8 months ago

    Probably a server setting issue. I noticed the Server and Content-Type (text/html) is not defined. For validation the placement of the meta tag for content type should not matter (though it should go before the title).

    You might try setting the values in htaccess

    Thread Starter clayfx

    (@clayfx)

    20 years, 8 months ago

    It seems that WP defines a Content-type by the way of wp-blog-header.php, which is different from the one which is written on the header.php file. Then here, as Beel, said, the first one was not defined, so it created a confusion.

    Also, in wp-blog-header.php, line 118, I’ve deleted:
    @header('Content-type: ' . get_option('html_type') . '; charset=' . get_option('blog_charset'));

    Then my blog becomes valid XHTML, as it takes in consideration the content-type defined in header.php.

    My solution is quite dirty, I’ve still not understood where the informations deleted were, to be able to modify them in a clean way.

    (excuse my english and the explications not very clear)

    Thanks for Beel, ceo, Lorelle.

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘strange XHTML errors’ is closed to new replies.