Fixed Xhtml Errors Cause Even More Numerous Errors

  • Resolved allthingscfnm

    (@allthingscfnm)


    16 years, 10 months ago

    Hey all…
    I’m having problems where a good number of people complain about not being able to reach the site via IE (even though I can in both IE, Opera, and FF) – so I validated it using w3.org. I get these 4 errors you can see yourself here

    So… when I’ve tried replacing the ” /> with “> as what I assume I need to do given the W3.org validation report, I end up with 260-something errors of varied kinds. I’ve been chasing my tail all day with this. What the heck can I do? Thanks ahead of time!

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

  • Your DOCTYPE tag does not need to be terminated. The fact that it is is really confusing the validator. Please try it like this:
    <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "https://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

    After this is done, you will be able to see the other errors in your html. You’ll need to work through these one at a time.

    BTW: a NSFW warning would have been nice as I am at work and went directly to your page and saw all the nastiness ??

    Thread Starter allthingscfnm

    (@allthingscfnm)

    OOPS! Sorry about that, I’d accidentally edited that out actually… I’ll do it again and then come back with another report of the hundreds of errors on my NSFW blog.

    Sorry again for that!

    Thread Starter allthingscfnm

    (@allthingscfnm)

    Okay check out the 298 errors I get now on my NSFW blog’s validation report by clicking here – I REALLY don’t understand how all this was NOT happening when I was running WP 2.0 with this same theme. EVERYTHING worked just fine then.

    Thread Starter allthingscfnm

    (@allthingscfnm)

    By the way, I’m on a VERY steep learning curve on these things… so please be kind!

    A few suggestions:

    • Remove all whitespace that exists before you DOCTYPE tag.
    • remove the /> from both you <html> and <head> elements. This is causing many errors.
    • Terminate all <br /> tags like this: <br />
    • Terminate all <img> tags like the <br />
    • Add alt attributes to all of your images.
    • Turn all instances of “&” in your dynamic link urls to: &amp;. This url on line 944 is a good example: …/cgi-bin/clicks.cgi?CA=906466-0000&PA=1166639"
    Thread Starter allthingscfnm

    (@allthingscfnm)

    1 ST OFF – Thankyou for your help!
    O.K., these all sound very simple, such as the first one and the last two. I actually had already started tackling that huge task. My blog has TONS of images and links, so that’s a HUGE deal by itself.

    Now the removal of /> from <html> and <head> elements: do I remove those from the header and footer .php’s within my dashboard’s theme editor?

    With the
    tags, you’re saying I need to add ANOTHER
    tag after it so that the line ends as

    ? Otherwise I’m lost on that as it looks like you’ve just repeated
    w/out any change in your suggested fix.

    Lastly, with the <img> tags, I have to end each line of code with a
    ? Very odd, as I’ve seen so many other source codes that don’t have it, but o.k. – you’re most obviously far more experienced than I!

    Thanks again, I REALLY need to get this resolved!

    Thread Starter allthingscfnm

    (@allthingscfnm)

    oops, it read the code …
    With the <br /> tags, you’re saying I need to add ANOTHER
    tag after it so that the line ends as <br /><br />? Otherwise I’m lost on that as it looks like you’ve just repeated the <br /> w/out any change in your suggested fix.

    Now the removal of /> from <html> and <head> elements: do I remove those from the header and footer .php’s within my dashboard’s theme editor?

    Yes

    With the
    tags, you’re saying I need to add ANOTHER
    tag after it so that the line ends as <br /><br />

    Ummm… Thats not what I meant to say. I believe that the forum added the slash for me. You only need one like this: <br />. I’m gonna test the forum’s filtering right here:
    no slash: <br />
    with slash: <br />

    Lastly, with the <img> tags, I have to end each line of code with a

    For successful validation, an <img> tag should have at least the following attributes with a terminating slash:

    <img src="" alt="" />

    Thread Starter allthingscfnm

    (@allthingscfnm)

    O.K. papa bear, you’ve successfully helped me bring 300 errors to 180. It was down to 177, but went up AFTER fixing a few things.

    I’m happier, but still REALLY puzzled by the need for removal of /> from the <head> and <html> elements you’ve mentioned. Mostly because I only found three in the header and cannot find any at all in the footer.

    I’m very much stalled as far as know ing what to do next, especially w/the meta codes and the “# Error Line 126, Column 65: document type does not allow element “a” here; missing one of “object”, “span”, “bdo”, “applet”, “iframe”, “tt”, “i”, “b”, “u”, “s”, “strike”, “big”, “small”, “font”, “em”, “strong”, “dfn”, “code”, “q”, “samp”, “kbd”, “var”, “cite”, “abbr”, “acronym”, “sub”, “sup”, “label”, “ins”, “del” start-tag .” errors…

    Thanks again in advance for your help!

    “META” should be lowercase like: “meta”
    This is the only error that I can see in the head of your document. All of your html tag names should be lowercase. This will probably knockout a large number of errors.

    Thread Starter allthingscfnm

    (@allthingscfnm)

    “META” should be lowercase like: “meta”
    This is the only error that I can see in the head of your document. All of your html tag names should be lowercase. This will probably knockout a large number of errors.

    Actually, your fix suggestion worked, but it only knocked out about ten errors, but hey, I’m not complaining! I’m still making progress…

    However, I’m REALLY still puzzled over `Hey man…
    Can you help me with something? Seriously, I CANNOT figure out why this following code (and others just like it) is giving errors in the site validator I’ve been using:

    <img src=”https://allthingscfnm.net/banners/NEWworkmycock-button.gif&#8221; alt=”work my cock cfnm” />

    This is the error it’s giving me for that line:

    Line 133, Column 51: document type does not allow element “a” here; missing one of “object”, “span”, “bdo”, “applet”, “iframe”, “tt”, “i”, “b”, “u”, “s”, “strike”, “big”, “small”, “font”, “em”, “strong”, “dfn”, “code”, “q”, “samp”, “kbd”, “var”, “cite”, “abbr”, “acronym”, “sub”, “sup”, “label”, “ins”, “del” start-tag .

    …//ww2.workmycock.com/track/ODc6Mjoy/”><img src=”https://allthingscfnm.net/bann

    ?

    The mentioned element is not allowed to appear in the context in which you’ve placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you’ve forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as “<p>” or “<table>”) inside an inline element (such as ““, “<span>”, or “<font>”).`

    What in god’s name does that mean? It’s driving me crazy man, how there’s sooo many errors on this site that seem to work everywhere else. If I can decypher this code’s problems w/some newfound understanding and fix it, I can knock off a TON of errors!

    Thanks again!

    Thread Starter allthingscfnm

    (@allthingscfnm)

    I’ve got myself down to 97 errors, by changing my left sidebar into a text widget and creating a linklist there. However, now in IE, the right sidebar is pushing up into the header, moving EVERYTHING around.

    I’m also now getting errors telling me that the linklist commands that have worked fine before are erred as well. I’m feeling overwhelmed by this. Any more suggestions anyone?

    Thanks again, man… seriously…

    Somehow, you have entered a second <head> tag now.
    I would suggest that you consult the WordPress Pro Mailing List for further help, as debugging html can be done by someone knowledgeable in under an hour. If we carry on like this, it could take forever.

    Thread Starter allthingscfnm

    (@allthingscfnm)

    I beat ya to it mr. fields… but thanks heaps for helping as much as you did because it forced me to learn alot. thanks!

Viewing 14 replies - 1 through 14 (of 14 total)
  • The topic ‘Fixed Xhtml Errors Cause Even More Numerous Errors’ is closed to new replies.