WordPress.org

Forums

[Plugin: Sociable for WordPress 3.0] shortcode causes validation errors (2 posts)

  1. rtivel
    Member
    Posted 4 years ago #

    Using the shortcode, [sociable tagline='Share it:'], in my posts is causing 3 validation errors at w3c:

    # Error Line 206, Column 841: end tag for element "p" which is not open

    …isus. Curabitur tempus ligula ut dui volutpat quis elementum orci faucibus.</p>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.
    # Error Line 211, Column 320: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag

    …ntum consectetur.<div class='sociable'><div></div><div><span class='sociable-t…

    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>").
    # Error Line 213, Column 14: end tag for "p" omitted, but OMITTAG NO was specified

    </div>

    Any ideas about how to fix this?

  2. rtivel
    Member
    Posted 4 years ago #

    This problem seems to be fixed. In the writing settings for wordpress I checked the "WordPress should correct invalidly nested XHTML automatically" box and the blog passed "in the green" at w3c. Just to prove that checking the box fixed the problem, I unchecked it and put the blog through the validator again--and it still passed. So, although the problem is fixed, I'm not sure exactly how.

Topic Closed

This topic has been closed to new replies.

About this Topic