Validation Errrors

  • Jackinbox

    (@jackinbox)


    10 years, 6 months ago

    Hello,

    Just noticed some new(er) validation errors, including pages that are not displaying the plugin. Maybe just a simple unencoded ampersand… I didn’t fiddle with the plugin code. Have a look, thanks:

    706. if(document.getElementsByClassName && document.getElementsByTagName) {

    707. var pinit_class_tags = document.getElementsByClassName(“really_simple_share_pinterest”);

    708. for(i=0; i < pinit_class_tags.length; i++) {

    Warning Line 706, Column 40: character “&” is the first character of a delimiter but occurred as data

    if(document.getElementsByClassName && document.getElementsByTagName) {

    ✉

    This message may appear in several cases:

    You tried to include the “<” character in your page: you should escape it as “<“
    You used an unescaped ampersand “&”: this may be valid in some contexts, but it is recommended to use “&”, which is always safe.
    Another possibility is that you forgot to close quotes in a previous tag.

    Warning Line 706, Column 41: character “&” is the first character of a delimiter but occurred as data

    if(document.getElementsByClassName && document.getElementsByTagName) {

    ✉

    This message may appear in several cases:

    You tried to include the “<” character in your page: you should escape it as “<“
    You used an unescaped ampersand “&”: this may be valid in some contexts, but it is recommended to use “&”, which is always safe.
    Another possibility is that you forgot to close quotes in a previous tag.

    Warning Line 708, Column 17: character “<” is the first character of a delimiter but occurred as data

    for(i=0; i < pinit_class_tags.length; i++) {

    ✉

    This message may appear in several cases:

    You tried to include the “<” character in your page: you should escape it as “<“
    You used an unescaped ampersand “&”: this may be valid in some contexts, but it is recommended to use “&”, which is always safe.
    Another possibility is that you forgot to close quotes in a previous tag.

    http://wordpress.org/plugins/really-simple-facebook-twitter-share-buttons/

Viewing 3 replies - 1 through 3 (of 3 total)
  • whiletrue

    (@whiletrue)

    10 years, 6 months ago

    Hi Jackinbox,
    I just fixed it, wrapping the JS code in a CDATA block as requested by XHTML). The new 2.14.1 plugin release should be out in minutes. Thanks a lot for your support!

    Thread Starter Jackinbox

    (@jackinbox)

    10 years, 6 months ago

    Your support on this FREE plugin is much appreciated & one reason why I use it! I’ll update later tonight. Thank you sir!

    Have a look:

    http://wordpress.org/support/topic/linksharereally/page/2?replies=34

    http://wordpress.org/support/topic/good-alternatives-because-linkalpha-have-ruined-this?replies=5

    Thread Starter Jackinbox

    (@jackinbox)

    10 years, 6 months ago

    Hello,

    You sure you got them all? Still getting some extra validation errors. I didn’t look too deeply, obviously, figured you’d need to know anyway! 🙂 See below, & there are many more errors pertaining to the same. I also get a lot of errors pertaining to Strict doc type, but not much we can do there considering my theme. Thanks.

    Warning Line 140, Column 892: cannot generate system identifier for general entity “media”

    ✉

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in “Ampersands in URLs”.

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as “&” (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and æ are different characters.

    If this error appears in some markup generated by PHP’s session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Validation Errrors’ is closed to new replies.