WordPress.org

Ready to get started?Download WordPress

Forums

Validating XML (10 posts)

  1. gretchen
    Member
    Posted 9 years ago #

    I'm in the process of validating all my HTML, CSS, etc. Using the W3C validators, I have acheived valid HTML. And, when I plug the CSS right into their form, the CSS comes back valid.

    However, when I just try to enter my site's URL into the CSS validator, I get the following message:

    Please, validate your XML document first!

    Line 219

    Column 54

    Element type "null" must be followed by either attribute specifications, ">" or "/>".

    I have checked the source code, and it appears that something in WordPress is generating javascript at the beginning and ending of my code (I am not generating the javascript through my template; in other words, that particular code is not in my template; it's being generated some other way). (View my source code--www.muppetous.com--to see what I mean.)

    So, how can I either (a) eliminate this javascript permanently or (b) fix the issue with the "null" element so that my XML gets validated?

    Thanks.

    Edit: I am also working on a design for someone else who uses Blogger (leftintheshade.blogspot.com), and I'm running into the same error message when trying to validate her site, so maybe the problem is not WordPress. What, then, is causing the javascript to be generated on these pages? Heeeeelp!

  2. Mark (podz)
    Support Maven
    Posted 9 years ago #

    Can you give us a link to the validation url ?

  3. gretchen
    Member
    Posted 9 years ago #

    Oops, sorry! Here's the CSS validator: http://jigsaw.w3.org/css-validator/

    (If you need to take a look at the HTML validator for any reason, you can click on the link at the top of the screen for validating HTML.)

    Thanks!

  4. Mark (podz)
    Support Maven
    Posted 9 years ago #

    Your css does validate - I pasted it into the validator.

    The error is curious - does the CSS validator count the same lines as the xhtml validator ?

  5. Beel
    Member
    Posted 9 years ago #

    I suspect this is your "error" on that line, though not technically an error, it probably causes the "burp" you experience:
    <a href="">

  6. gretchen
    Member
    Posted 9 years ago #

    I've filled in those missing links in the a href=" ", but I'm still getting the error message (for both sites: http://www.muppetous.com and leftintheshade.blogspot.com) when I enter the URLs in the CSS validator.

    The error for http://www.muppetous.com is on line 219, column 54, and the error for leftintheshade.blogspot.com is on line 391, column 293. (Both errors read the same; see initial post above for the exact wording.)

    Any other ideas?

  7. gretchen
    Member
    Posted 9 years ago #

    Ah, podz, I almost missed your comment. I did the same thing, pasted the CSS into the validator, and then it worked fine. Same with the HTML. But when I enter the site's URL into the CSS validator INSTEAD of pasting the CSS directly in, I get that error message about invalid XML and the "null" character. (If you view the source code of the page, way down at the bottom there's some javascript, which I didn't generate, that has the "null" element in it. This is the part I'm confused by.)

    I haven't quite figured out how the line-counting works. I would think the two different validators would count the same way, but I'm not sure about that.

    Argh!

  8. gretchen
    Member
    Posted 9 years ago #

    I've been doing some web research and reading some forums, and I'm wondering if there's someone out there who does NOT have Norton pop-up blocker who would trying validating my CSS by entering my URL (www.muppetous.com) into the CSS validator (http://jigsaw.w3.org/css-validator/) for me and tell me if you get an error message or not. Any takers?

  9. Beel
    Member
    Posted 9 years ago #

    I don't use Norton pop-up blocker but I did discover your problem in both sites. You have: src="blah-blah"alt="... there should be a space between the double quote and the "a" in alt.

  10. gretchen
    Member
    Posted 9 years ago #

    Thanks, Beel. I corrected this problem in both sites. I'm no longer getting the same error message (can anyone explain why I would've gotten the mesage that I did [see first post above] when the only problem was a missing space? Just curious.), although it's pointing out a new error caused by the navbar generated Blogger, which I can do nothing about. Oh, well, I'm as validated as I can get, I guess. Thanks again!

Topic Closed

This topic has been closed to new replies.

About this Topic

Tags

No tags yet.