Forums

[resolved] XHTML Errors (Nucleus Converted Site) (8 posts)

  1. calvertgames
    Member
    Posted 3 years ago #

    When I run my site (www.calvertgames.com) through XHTML validation, I get the following types of errors:

    # Error Line 72 column 20: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag.

    <p class="MsoNormal">

    Is this the fault of the CSS? Any suggestions on correcting? I just converted 600+ posts from a nucleus site, but the items giving me immediate concern are new entries.

    Thanks for the help/advice.

  2. petit
    Member
    Posted 3 years ago #

    The markup on lines that the W3C Markup Validation Service complains about looks like this:

    #<div class="entry">
    # <p class="MsoNormal">
    # <p class="MsoNormal">
    # <p class="MsoNormal">
    # <p class="MsoNormal">

    That is, the paragraph element are not closed.
    What you do to get this kind of markup, I don't know, but unclosed elements ( or tags ) are not allowed in HTML, much less XHTML Transitional.

    To see what lines the line numbers refers to in the validation service, just rerun the validation with the check box "Show source" ticked. After the list of complaints, the source with line numbers is presented.

    Good hunt!

  3. spencerp
    Member
    Posted 3 years ago #

    That looks to me, like they were maybe using MS WORD, copied/pasted from MS WORD.. right into their Blog's Write Post window..? Before doing that, use NotePad2 or something similiar...

    http://www.flos-freeware.ch/notepad2.html

    Also, close off your <p>'s with the right amount of </p>'s

    spencerp

  4. spencerp
    Member
    Posted 3 years ago #

    I mean, it's ok to use MS WORD for spell checking and so forth, just make sure to copy/paste from MS WORD to something like NotePad2 FIRST, before pasting it into the Write Post window..

    Also, if you're doing that.. you might want to turn off the Rich Text Editor too.
    http://www.vindictivebastard.net/images2/turnoff-rte.gif

    spencerp

  5. calvertgames
    Member
    Posted 3 years ago #

    petit/spencerp,

    Thanks for the prompt responses. With Nucleus I always put together my posts in Word (Lord knows I cannot spell) and then copy/paste into the Nucleus editor.

    That was the problem here. I took the post out of the editor, placed the content in UltraEdit and then moved back to the WP editor. Thanks look much better now.

    I am not going to go back and edit 600+ posts, but at least I know what to do going forward.

    Thanks again for the help!

  6. Chris_K
    Administrator
    Posted 3 years ago #

    Yeah, the trick is with the WYSIWYG editor in WP 2.0.x, you get all of Word's "html" along with your text.

    Some options for going forward

    1) As noted, paste from Word to a text editor then to WP.

    2) Look at this nifty little utility called PureText (http://www.stevemiller.net/puretext/)

    3) Turn off the Wysiwyg thing (Users -> Your profile. Uncheck box on bottom of the page and save)
    http://www.vindictivebastard.net/images2/turnoff-rte.gif

    4) Check out this plugin: http://www.ndsinternet.com/blog/archives/2006/08/wordpress-plain-text-paste-plugin it may be just the ticket, but I've not tried it.

    5) Download and install Windows Live Writer (beta) which is almost like Word and probably the slickest little windows blogging client so far.

  7. spencerp
    Member
    Posted 3 years ago #

    No problem. =)

    spencerp

  8. petit
    Member
    Posted 3 years ago #

    You may use Word as an editor for blog posts, but I'd say, don't. It's bound to create headaches if you are not careful. The HTML produced has a lot of CSS classes used only by Word.
    Better look up a good spellchecker for your browser, like SpellBound for FireFox. It is also part of the Google Toolbar.

    Then you can spell check right there in the "write post" form. You must turn off the WYSIWYG editor in WordPress to use it.

Topic Closed

This topic has been closed to new replies.

About this Topic