Errors found while checking this document as XHTML 1.0 Strict!

Result: 545 Errors, 794 warning(s)
:
Modified:Fri, 06 Jan 2017 15:27:35 GMT
Server:GSE
Size:44379
Content-Type:text/html
: utf-8
: XHTML 1.0 Strict
Root Element: html
Root Namespace: http://www.w3.org/1999/xhtml
Options

Help on the options is available.

↑ Top

Validation Output: 545 Errors

  1. Error Line 13, Column 54: there is no attribute "property"
    <meta content='http://isteve.blogspot.com/' property='og:url'/>

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  2. Error Line 60, Column 6: invalid comment declaration: found delimiter "-" outside comment but inside comment declaration
    /* ---( page defaults )--- */

  3. Info Line 21, Column 41: comment declaration started here
    <style id='page-skin-1' type='text/css'><!--
  4. Error Line 300, Column 1: delimiter "/" invalid: only S separators and TAGC allowed here
    /noscript

  5. Error Line 300, Column 1: end tag for element "a" which is not open
    /noscript

    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.

  6. Warning Line 367, Column 142: character "<" is the first character of a delimiter but occurred as data
    …case 1:return b+"?m=1";case 2:return 0<=c[1].search("(^|&)m=")?null:b+"&m=1";d…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  7. Warning Line 367, Column 160: character "&" is the first character of a delimiter but occurred as data
    …m=1";case 2:return 0<=c[1].search("(^|&)m=")?null:b+"&m=1";default:return null…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  8. Warning Line 367, Column 176: cannot generate system identifier for general entity "m"
    …rn 0<=c[1].search("(^|&)m=")?null:b+"&m=1";default:return null}}var d=navigato…

    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 "&amp;" (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 &aelig; 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.

  9. Error Line 367, Column 176: general entity "m" not defined and no default entity
    …rn 0<=c[1].search("(^|&)m=")?null:b+"&m=1";default:return null}}var d=navigato…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  10. Warning Line 367, Column 177: reference not terminated by REFC delimiter
    …n 0<=c[1].search("(^|&)m=")?null:b+"&m=1";default:return null}}var d=navigator…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  11. Error Line 367, Column 177: reference to entity "m" for which no system identifier could be generated
    …n 0<=c[1].search("(^|&)m=")?null:b+"&m=1";default:return null}}var d=navigator…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  12. Info Line 367, Column 175: entity was defined here
    …urn 0<=c[1].search("(^|&)m=")?null:b+"&m=1";default:return null}}var d=navigat…
  13. Warning Line 367, Column 254: character "&" is the first character of a delimiter but occurred as data
    …r.userAgent;if(-1!=d.indexOf("Mobile")&&-1!=d.indexOf("WebKit")&&-1==d.indexOf…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  14. Warning Line 367, Column 255: character "&" is the first character of a delimiter but occurred as data
    ….userAgent;if(-1!=d.indexOf("Mobile")&&-1!=d.indexOf("WebKit")&&-1==d.indexOf(…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  15. Warning Line 367, Column 279: character "&" is the first character of a delimiter but occurred as data
    …xOf("Mobile")&&-1!=d.indexOf("WebKit")&&-1==d.indexOf("iPad")||-1!=d.indexOf("…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  16. Warning Line 367, Column 280: character "&" is the first character of a delimiter but occurred as data
    …Of("Mobile")&&-1!=d.indexOf("WebKit")&&-1==d.indexOf("iPad")||-1!=d.indexOf("O…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  17. Warning Line 367, Column 371: character "&" is the first character of a delimiter but occurred as data
    …ra Mini")||-1!=d.indexOf("IEMobile")){var e=a();e&&window.location.replace(e)};

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  18. Warning Line 367, Column 373: cannot generate system identifier for general entity "window.location.replace"
    …ra Mini")||-1!=d.indexOf("IEMobile")){var e=a();e&&window.location.replace(e)};

    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 "&amp;" (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 &aelig; 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.

  19. Error Line 367, Column 373: general entity "window.location.replace" not defined and no default entity
    …ra Mini")||-1!=d.indexOf("IEMobile")){var e=a();e&&window.location.replace(e)};

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  20. Warning Line 367, Column 396: reference not terminated by REFC delimiter
    …ra Mini")||-1!=d.indexOf("IEMobile")){var e=a();e&&window.location.replace(e)};

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  21. Error Line 367, Column 396: reference to entity "window.location.replace" for which no system identifier could be generated
    …ra Mini")||-1!=d.indexOf("IEMobile")){var e=a();e&&window.location.replace(e)};

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  22. Info Line 367, Column 372: entity was defined here
    …ra Mini")||-1!=d.indexOf("IEMobile")){var e=a();e&&window.location.replace(e)};
  23. Error Line 370, Column 81: there is no attribute "data-version"
    …iv class='widget Navbar' data-version='1' id='Navbar1'><script type="text/java…

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  24. Warning Line 384, Column 26: character "&" is the first character of a delimiter but occurred as data
            if (gapi.iframes && gapi.iframes.getContext) {

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  25. Warning Line 384, Column 27: character "&" is the first character of a delimiter but occurred as data
            if (gapi.iframes && gapi.iframes.getContext) {

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  26. Error Line 446, Column 12: there is no attribute "align"
    <div align="left">

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  27. Warning Line 532, Column 80: cannot generate system identifier for general entity "postID"
    ….blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>1…

    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 "&amp;" (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 &aelig; 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.

  28. Error Line 532, Column 80: general entity "postID" not defined and no default entity
    ….blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>1…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  29. Warning Line 532, Column 86: reference not terminated by REFC delimiter
    ….blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>17

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  30. Warning Line 532, Column 86: reference to external entity in attribute value
    ….blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>17

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  31. Error Line 532, Column 86: reference to entity "postID" for which no system identifier could be generated
    ….blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>17

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  32. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  33. Warning Line 537, Column 68: reference not terminated by REFC delimiter
    …com/email-post.g?blogID=9430835&postID=6945236942316918823' title='Email Post'…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  34. Warning Line 537, Column 68: reference to external entity in attribute value
    …com/email-post.g?blogID=9430835&postID=6945236942316918823' title='Email Post'…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  35. Error Line 537, Column 68: reference to entity "postID" for which no system identifier could be generated
    …com/email-post.g?blogID=9430835&postID=6945236942316918823' title='Email Post'…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  36. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  37. Warning Line 542, Column 67: reference not terminated by REFC delimiter
    ….com/post-edit.g?blogID=9430835&postID=6945236942316918823&from=pencil' title=…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  38. Warning Line 542, Column 67: reference to external entity in attribute value
    ….com/post-edit.g?blogID=9430835&postID=6945236942316918823&from=pencil' title=…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  39. Error Line 542, Column 67: reference to entity "postID" for which no system identifier could be generated
    ….com/post-edit.g?blogID=9430835&postID=6945236942316918823&from=pencil' title=…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  40. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  41. Warning Line 542, Column 88: cannot generate system identifier for general entity "from"
    …dit.g?blogID=9430835&postID=6945236942316918823&from=pencil' title='Edit Post'>

    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 "&amp;" (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 &aelig; 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.

  42. Error Line 542, Column 88: general entity "from" not defined and no default entity
    …dit.g?blogID=9430835&postID=6945236942316918823&from=pencil' title='Edit Post'>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  43. Warning Line 542, Column 92: reference not terminated by REFC delimiter
    …dit.g?blogID=9430835&postID=6945236942316918823&from=pencil' title='Edit Post'>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  44. Warning Line 542, Column 92: reference to external entity in attribute value
    …dit.g?blogID=9430835&postID=6945236942316918823&from=pencil' title='Edit Post'>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  45. Error Line 542, Column 92: reference to entity "from" for which no system identifier could be generated
    …dit.g?blogID=9430835&postID=6945236942316918823&from=pencil' title='Edit Post'>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  46. Info Line 542, Column 87: entity was defined here
    …dit.g?blogID=9430835&postID=6945236942316918823&from=pencil' title='Edit Post'>
  47. Warning Line 555, Column 116: reference not terminated by REFC delimiter
    …com/share-post.g?blogID=9430835&postID=6945236942316918823&target=email' targe…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  48. Warning Line 555, Column 116: reference to external entity in attribute value
    …com/share-post.g?blogID=9430835&postID=6945236942316918823&target=email' targe…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  49. Error Line 555, Column 116: reference to entity "postID" for which no system identifier could be generated
    …com/share-post.g?blogID=9430835&postID=6945236942316918823&target=email' targe…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  50. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  51. Warning Line 555, Column 137: cannot generate system identifier for general entity "target"
    …ID=9430835&postID=6945236942316918823&target=email' target='_blank' title='Ema…

    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 "&amp;" (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 &aelig; 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.

  52. Error Line 555, Column 137: general entity "target" not defined and no default entity
    …ID=9430835&postID=6945236942316918823&target=email' target='_blank' title='Ema…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  53. Warning Line 555, Column 143: reference not terminated by REFC delimiter
    …0835&postID=6945236942316918823&target=email' target='_blank' title='Email Thi…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  54. Warning Line 555, Column 143: reference to external entity in attribute value
    …0835&postID=6945236942316918823&target=email' target='_blank' title='Email Thi…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  55. Error Line 555, Column 143: reference to entity "target" for which no system identifier could be generated
    …0835&postID=6945236942316918823&target=email' target='_blank' title='Email Thi…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  56. Info Line 555, Column 136: entity was defined here
    …gID=9430835&postID=6945236942316918823&target=email' target='_blank' title='Em…
  57. Error Line 555, Column 158: there is no attribute "target"
    …5236942316918823&target=email' target='_blank' title='Email This'><span class=…

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  58. Warning Line 555, Column 358: reference not terminated by REFC delimiter
    …com/share-post.g?blogID=9430835&postID=6945236942316918823&target=blog' onclic…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  59. Warning Line 555, Column 358: reference to external entity in attribute value
    …com/share-post.g?blogID=9430835&postID=6945236942316918823&target=blog' onclic…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  60. Error Line 555, Column 358: reference to entity "postID" for which no system identifier could be generated
    …com/share-post.g?blogID=9430835&postID=6945236942316918823&target=blog' onclic…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  61. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  62. Warning Line 555, Column 385: reference not terminated by REFC delimiter
    …0835&postID=6945236942316918823&target=blog' onclick='window.open(this.href, "…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  63. Warning Line 555, Column 385: reference to external entity in attribute value
    …0835&postID=6945236942316918823&target=blog' onclick='window.open(this.href, "…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  64. Error Line 555, Column 385: reference to entity "target" for which no system identifier could be generated
    …0835&postID=6945236942316918823&target=blog' onclick='window.open(this.href, "…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  65. Info Line 555, Column 136: entity was defined here
    …gID=9430835&postID=6945236942316918823&target=email' target='_blank' title='Em…
  66. Warning Line 555, Column 682: reference not terminated by REFC delimiter
    …com/share-post.g?blogID=9430835&postID=6945236942316918823&target=twitter' tar…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  67. Warning Line 555, Column 682: reference to external entity in attribute value
    …com/share-post.g?blogID=9430835&postID=6945236942316918823&target=twitter' tar…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  68. Error Line 555, Column 682: reference to entity "postID" for which no system identifier could be generated
    …com/share-post.g?blogID=9430835&postID=6945236942316918823&target=twitter' tar…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  69. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  70. Warning Line 555, Column 709: reference not terminated by REFC delimiter
    …0835&postID=6945236942316918823&target=twitter' target='_blank' title='Share t…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  71. Warning Line 555, Column 709: reference to external entity in attribute value
    …0835&postID=6945236942316918823&target=twitter' target='_blank' title='Share t…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  72. Error Line 555, Column 709: reference to entity "target" for which no system identifier could be generated
    …0835&postID=6945236942316918823&target=twitter' target='_blank' title='Share t…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  73. Info Line 555, Column 136: entity was defined here
    …gID=9430835&postID=6945236942316918823&target=email' target='_blank' title='Em…
  74. Warning Line 555, Column 942: reference not terminated by REFC delimiter
    …com/share-post.g?blogID=9430835&postID=6945236942316918823&target=facebook' on…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  75. Warning Line 555, Column 942: reference to external entity in attribute value
    …com/share-post.g?blogID=9430835&postID=6945236942316918823&target=facebook' on…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  76. Error Line 555, Column 942: reference to entity "postID" for which no system identifier could be generated
    …com/share-post.g?blogID=9430835&postID=6945236942316918823&target=facebook' on…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  77. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  78. Warning Line 555, Column 969: reference not terminated by REFC delimiter
    …0835&postID=6945236942316918823&target=facebook' onclick='window.open(this.hre…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  79. Warning Line 555, Column 969: reference to external entity in attribute value
    …0835&postID=6945236942316918823&target=facebook' onclick='window.open(this.hre…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  80. Error Line 555, Column 969: reference to entity "target" for which no system identifier could be generated
    …0835&postID=6945236942316918823&target=facebook' onclick='window.open(this.hre…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  81. Info Line 555, Column 136: entity was defined here
    …gID=9430835&postID=6945236942316918823&target=email' target='_blank' title='Em…
  82. Warning Line 555, Column 1288: reference not terminated by REFC delimiter
    …com/share-post.g?blogID=9430835&postID=6945236942316918823&target=pinterest' t…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  83. Warning Line 555, Column 1288: reference to external entity in attribute value
    …com/share-post.g?blogID=9430835&postID=6945236942316918823&target=pinterest' t…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  84. Error Line 555, Column 1288: reference to entity "postID" for which no system identifier could be generated
    …com/share-post.g?blogID=9430835&postID=6945236942316918823&target=pinterest' t…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  85. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  86. Warning Line 555, Column 1315: reference not terminated by REFC delimiter
    …0835&postID=6945236942316918823&target=pinterest' target='_blank' title='Share…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  87. Warning Line 555, Column 1315: reference to external entity in attribute value
    …0835&postID=6945236942316918823&target=pinterest' target='_blank' title='Share…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  88. Error Line 555, Column 1315: reference to entity "target" for which no system identifier could be generated
    …0835&postID=6945236942316918823&target=pinterest' target='_blank' title='Share…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  89. Info Line 555, Column 136: entity was defined here
    …gID=9430835&postID=6945236942316918823&target=email' target='_blank' title='Em…
  90. Error Line 555, Column 1513: there is no attribute "source"
    …us-share-container'><g:plusone source='blogger:blog:plusone' href='http://iste…

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  91. Error Line 555, Column 1541: there is no attribute "href"
    …ne source='blogger:blog:plusone' href='http://isteve.blogspot.com/2014/06/late…

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  92. Error Line 555, Column 1622: there is no attribute "size"
    …isteve-posts-at-unz-review.html' size='medium' width='300' annotation='inline'…

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  93. Error Line 555, Column 1637: there is no attribute "width"
    …posts-at-unz-review.html' size='medium' width='300' annotation='inline'/></div>

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  94. Error Line 555, Column 1654: there is no attribute "annotation"
    …posts-at-unz-review.html' size='medium' width='300' annotation='inline'/></div>

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  95. Error Line 555, Column 1663: element "g:plusone" undefined
    …posts-at-unz-review.html' size='medium' width='300' annotation='inline'/></div>

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  96. Warning Line 606, Column 86: reference not terminated by REFC delimiter
    ….blogger.com/comment.g?blogID=9430835&postID=1712813300946583454' onclick=''>19

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  97. Warning Line 606, Column 86: reference to external entity in attribute value
    ….blogger.com/comment.g?blogID=9430835&postID=1712813300946583454' onclick=''>19

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  98. Error Line 606, Column 86: reference to entity "postID" for which no system identifier could be generated
    ….blogger.com/comment.g?blogID=9430835&postID=1712813300946583454' onclick=''>19

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  99. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  100. Warning Line 611, Column 68: reference not terminated by REFC delimiter
    …com/email-post.g?blogID=9430835&postID=1712813300946583454' title='Email Post'…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  101. Warning Line 611, Column 68: reference to external entity in attribute value
    …com/email-post.g?blogID=9430835&postID=1712813300946583454' title='Email Post'…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  102. Error Line 611, Column 68: reference to entity "postID" for which no system identifier could be generated
    …com/email-post.g?blogID=9430835&postID=1712813300946583454' title='Email Post'…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  103. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  104. Warning Line 616, Column 67: reference not terminated by REFC delimiter
    ….com/post-edit.g?blogID=9430835&postID=1712813300946583454&from=pencil' title=…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  105. Warning Line 616, Column 67: reference to external entity in attribute value
    ….com/post-edit.g?blogID=9430835&postID=1712813300946583454&from=pencil' title=…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  106. Error Line 616, Column 67: reference to entity "postID" for which no system identifier could be generated
    ….com/post-edit.g?blogID=9430835&postID=1712813300946583454&from=pencil' title=…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  107. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  108. Warning Line 616, Column 92: reference not terminated by REFC delimiter
    …dit.g?blogID=9430835&postID=1712813300946583454&from=pencil' title='Edit Post'>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  109. Warning Line 616, Column 92: reference to external entity in attribute value
    …dit.g?blogID=9430835&postID=1712813300946583454&from=pencil' title='Edit Post'>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  110. Error Line 616, Column 92: reference to entity "from" for which no system identifier could be generated
    …dit.g?blogID=9430835&postID=1712813300946583454&from=pencil' title='Edit Post'>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  111. Info Line 542, Column 87: entity was defined here
    …dit.g?blogID=9430835&postID=6945236942316918823&from=pencil' title='Edit Post'>
  112. Warning Line 629, Column 116: reference not terminated by REFC delimiter
    …com/share-post.g?blogID=9430835&postID=1712813300946583454&target=email' targe…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  113. Warning Line 629, Column 116: reference to external entity in attribute value
    …com/share-post.g?blogID=9430835&postID=1712813300946583454&target=email' targe…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  114. Error Line 629, Column 116: reference to entity "postID" for which no system identifier could be generated
    …com/share-post.g?blogID=9430835&postID=1712813300946583454&target=email' targe…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  115. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  116. Warning Line 629, Column 143: reference not terminated by REFC delimiter
    …0835&postID=1712813300946583454&target=email' target='_blank' title='Email Thi…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  117. Warning Line 629, Column 143: reference to external entity in attribute value
    …0835&postID=1712813300946583454&target=email' target='_blank' title='Email Thi…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  118. Error Line 629, Column 143: reference to entity "target" for which no system identifier could be generated
    …0835&postID=1712813300946583454&target=email' target='_blank' title='Email Thi…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  119. Info Line 555, Column 136: entity was defined here
    …gID=9430835&postID=6945236942316918823&target=email' target='_blank' title='Em…
  120. Warning Line 629, Column 358: reference not terminated by REFC delimiter
    …com/share-post.g?blogID=9430835&postID=1712813300946583454&target=blog' onclic…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  121. Warning Line 629, Column 358: reference to external entity in attribute value
    …com/share-post.g?blogID=9430835&postID=1712813300946583454&target=blog' onclic…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  122. Error Line 629, Column 358: reference to entity "postID" for which no system identifier could be generated
    …com/share-post.g?blogID=9430835&postID=1712813300946583454&target=blog' onclic…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  123. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  124. Warning Line 629, Column 385: reference not terminated by REFC delimiter
    …0835&postID=1712813300946583454&target=blog' onclick='window.open(this.href, "…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  125. Warning Line 629, Column 385: reference to external entity in attribute value
    …0835&postID=1712813300946583454&target=blog' onclick='window.open(this.href, "…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  126. Error Line 629, Column 385: reference to entity "target" for which no system identifier could be generated
    …0835&postID=1712813300946583454&target=blog' onclick='window.open(this.href, "…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  127. Info Line 555, Column 136: entity was defined here
    …gID=9430835&postID=6945236942316918823&target=email' target='_blank' title='Em…
  128. Warning Line 629, Column 682: reference not terminated by REFC delimiter
    …com/share-post.g?blogID=9430835&postID=1712813300946583454&target=twitter' tar…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  129. Warning Line 629, Column 682: reference to external entity in attribute value
    …com/share-post.g?blogID=9430835&postID=1712813300946583454&target=twitter' tar…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  130. Error Line 629, Column 682: reference to entity "postID" for which no system identifier could be generated
    …com/share-post.g?blogID=9430835&postID=1712813300946583454&target=twitter' tar…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  131. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  132. Warning Line 629, Column 709: reference not terminated by REFC delimiter
    …0835&postID=1712813300946583454&target=twitter' target='_blank' title='Share t…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  133. Warning Line 629, Column 709: reference to external entity in attribute value
    …0835&postID=1712813300946583454&target=twitter' target='_blank' title='Share t…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  134. Error Line 629, Column 709: reference to entity "target" for which no system identifier could be generated
    …0835&postID=1712813300946583454&target=twitter' target='_blank' title='Share t…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  135. Info Line 555, Column 136: entity was defined here
    …gID=9430835&postID=6945236942316918823&target=email' target='_blank' title='Em…
  136. Warning Line 629, Column 942: reference not terminated by REFC delimiter
    …com/share-post.g?blogID=9430835&postID=1712813300946583454&target=facebook' on…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  137. Warning Line 629, Column 942: reference to external entity in attribute value
    …com/share-post.g?blogID=9430835&postID=1712813300946583454&target=facebook' on…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  138. Error Line 629, Column 942: reference to entity "postID" for which no system identifier could be generated
    …com/share-post.g?blogID=9430835&postID=1712813300946583454&target=facebook' on…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  139. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  140. Warning Line 629, Column 969: reference not terminated by REFC delimiter
    …0835&postID=1712813300946583454&target=facebook' onclick='window.open(this.hre…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  141. Warning Line 629, Column 969: reference to external entity in attribute value
    …0835&postID=1712813300946583454&target=facebook' onclick='window.open(this.hre…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  142. Error Line 629, Column 969: reference to entity "target" for which no system identifier could be generated
    …0835&postID=1712813300946583454&target=facebook' onclick='window.open(this.hre…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  143. Info Line 555, Column 136: entity was defined here
    …gID=9430835&postID=6945236942316918823&target=email' target='_blank' title='Em…
  144. Warning Line 629, Column 1288: reference not terminated by REFC delimiter
    …com/share-post.g?blogID=9430835&postID=1712813300946583454&target=pinterest' t…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  145. Warning Line 629, Column 1288: reference to external entity in attribute value
    …com/share-post.g?blogID=9430835&postID=1712813300946583454&target=pinterest' t…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  146. Error Line 629, Column 1288: reference to entity "postID" for which no system identifier could be generated
    …com/share-post.g?blogID=9430835&postID=1712813300946583454&target=pinterest' t…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  147. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  148. Warning Line 629, Column 1315: reference not terminated by REFC delimiter
    …0835&postID=1712813300946583454&target=pinterest' target='_blank' title='Share…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  149. Warning Line 629, Column 1315: reference to external entity in attribute value
    …0835&postID=1712813300946583454&target=pinterest' target='_blank' title='Share…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  150. Error Line 629, Column 1315: reference to entity "target" for which no system identifier could be generated
    …0835&postID=1712813300946583454&target=pinterest' target='_blank' title='Share…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  151. Info Line 555, Column 136: entity was defined here
    …gID=9430835&postID=6945236942316918823&target=email' target='_blank' title='Em…
  152. Error Line 629, Column 1655: element "g:plusone" undefined
    …gging-at-unz-review.html' size='medium' width='300' annotation='inline'/></div>

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  153. Error Line 652, Column 14: there is no attribute "align"
    <table align="center" cellpadding="0" cellspacing="0" class="tr-caption-contain…

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  154. Error Line 653, Column 176: there is no attribute "imageanchor"
    …-2nd-Linksland.com-1.jpg" imageanchor="1" style="margin-left: auto; margin-rig…

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  155. Error Line 653, Column 239: there is no attribute "border"
    …uto; margin-right: auto;"><img border="0" src="http://theaposition.com/jeffwal…

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  156. Error Line 653, Column 392: required attribute "alt" not specified
    …s-Old-Course-2nd-Linksland.com-1.jpg" height="245" width="400" /></a></td></tr>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  157. Warning Line 673, Column 86: reference not terminated by REFC delimiter
    …ww.blogger.com/comment.g?blogID=9430835&postID=101453778386923953' onclick=''>9

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  158. Warning Line 673, Column 86: reference to external entity in attribute value
    …ww.blogger.com/comment.g?blogID=9430835&postID=101453778386923953' onclick=''>9

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  159. Error Line 673, Column 86: reference to entity "postID" for which no system identifier could be generated
    …ww.blogger.com/comment.g?blogID=9430835&postID=101453778386923953' onclick=''>9

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  160. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  161. Warning Line 678, Column 68: reference not terminated by REFC delimiter
    ….com/email-post.g?blogID=9430835&postID=101453778386923953' title='Email Post'>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  162. Warning Line 678, Column 68: reference to external entity in attribute value
    ….com/email-post.g?blogID=9430835&postID=101453778386923953' title='Email Post'>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  163. Error Line 678, Column 68: reference to entity "postID" for which no system identifier could be generated
    ….com/email-post.g?blogID=9430835&postID=101453778386923953' title='Email Post'>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  164. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  165. Warning Line 683, Column 67: reference not terminated by REFC delimiter
    ….com/post-edit.g?blogID=9430835&postID=101453778386923953&from=pencil' title='…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  166. Warning Line 683, Column 67: reference to external entity in attribute value
    ….com/post-edit.g?blogID=9430835&postID=101453778386923953&from=pencil' title='…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  167. Error Line 683, Column 67: reference to entity "postID" for which no system identifier could be generated
    ….com/post-edit.g?blogID=9430835&postID=101453778386923953&from=pencil' title='…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  168. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  169. Warning Line 683, Column 91: reference not terminated by REFC delimiter
    …edit.g?blogID=9430835&postID=101453778386923953&from=pencil' title='Edit Post'>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  170. Warning Line 683, Column 91: reference to external entity in attribute value
    …edit.g?blogID=9430835&postID=101453778386923953&from=pencil' title='Edit Post'>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  171. Error Line 683, Column 91: reference to entity "from" for which no system identifier could be generated
    …edit.g?blogID=9430835&postID=101453778386923953&from=pencil' title='Edit Post'>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  172. Info Line 542, Column 87: entity was defined here
    …dit.g?blogID=9430835&postID=6945236942316918823&from=pencil' title='Edit Post'>
  173. Warning Line 696, Column 116: reference not terminated by REFC delimiter
    …com/share-post.g?blogID=9430835&postID=101453778386923953&target=email' target…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  174. Warning Line 696, Column 116: reference to external entity in attribute value
    …com/share-post.g?blogID=9430835&postID=101453778386923953&target=email' target…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  175. Error Line 696, Column 116: reference to entity "postID" for which no system identifier could be generated
    …com/share-post.g?blogID=9430835&postID=101453778386923953&target=email' target…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  176. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  177. Warning Line 696, Column 142: reference not terminated by REFC delimiter
    …30835&postID=101453778386923953&target=email' target='_blank' title='Email Thi…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  178. Warning Line 696, Column 142: reference to external entity in attribute value
    …30835&postID=101453778386923953&target=email' target='_blank' title='Email Thi…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  179. Error Line 696, Column 142: reference to entity "target" for which no system identifier could be generated
    …30835&postID=101453778386923953&target=email' target='_blank' title='Email Thi…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  180. Info Line 555, Column 136: entity was defined here
    …gID=9430835&postID=6945236942316918823&target=email' target='_blank' title='Em…
  181. Warning Line 696, Column 357: reference not terminated by REFC delimiter
    …com/share-post.g?blogID=9430835&postID=101453778386923953&target=blog' onclick…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  182. Warning Line 696, Column 357: reference to external entity in attribute value
    …com/share-post.g?blogID=9430835&postID=101453778386923953&target=blog' onclick…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  183. Error Line 696, Column 357: reference to entity "postID" for which no system identifier could be generated
    …com/share-post.g?blogID=9430835&postID=101453778386923953&target=blog' onclick…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  184. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  185. Warning Line 696, Column 383: reference not terminated by REFC delimiter
    …30835&postID=101453778386923953&target=blog' onclick='window.open(this.href, "…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  186. Warning Line 696, Column 383: reference to external entity in attribute value
    …30835&postID=101453778386923953&target=blog' onclick='window.open(this.href, "…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  187. Error Line 696, Column 383: reference to entity "target" for which no system identifier could be generated
    …30835&postID=101453778386923953&target=blog' onclick='window.open(this.href, "…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  188. Info Line 555, Column 136: entity was defined here
    …gID=9430835&postID=6945236942316918823&target=email' target='_blank' title='Em…
  189. Warning Line 696, Column 680: reference not terminated by REFC delimiter
    …com/share-post.g?blogID=9430835&postID=101453778386923953&target=twitter' targ…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  190. Warning Line 696, Column 680: reference to external entity in attribute value
    …com/share-post.g?blogID=9430835&postID=101453778386923953&target=twitter' targ…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  191. Error Line 696, Column 680: reference to entity "postID" for which no system identifier could be generated
    …com/share-post.g?blogID=9430835&postID=101453778386923953&target=twitter' targ…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  192. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  193. Warning Line 696, Column 706: reference not terminated by REFC delimiter
    …30835&postID=101453778386923953&target=twitter' target='_blank' title='Share t…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  194. Warning Line 696, Column 706: reference to external entity in attribute value
    …30835&postID=101453778386923953&target=twitter' target='_blank' title='Share t…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  195. Error Line 696, Column 706: reference to entity "target" for which no system identifier could be generated
    …30835&postID=101453778386923953&target=twitter' target='_blank' title='Share t…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  196. Info Line 555, Column 136: entity was defined here
    …gID=9430835&postID=6945236942316918823&target=email' target='_blank' title='Em…
  197. Warning Line 696, Column 939: reference not terminated by REFC delimiter
    …com/share-post.g?blogID=9430835&postID=101453778386923953&target=facebook' onc…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  198. Warning Line 696, Column 939: reference to external entity in attribute value
    …com/share-post.g?blogID=9430835&postID=101453778386923953&target=facebook' onc…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  199. Error Line 696, Column 939: reference to entity "postID" for which no system identifier could be generated
    …com/share-post.g?blogID=9430835&postID=101453778386923953&target=facebook' onc…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  200. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  201. Warning Line 696, Column 965: reference not terminated by REFC delimiter
    …30835&postID=101453778386923953&target=facebook' onclick='window.open(this.hre…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  202. Warning Line 696, Column 965: reference to external entity in attribute value
    …30835&postID=101453778386923953&target=facebook' onclick='window.open(this.hre…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  203. Error Line 696, Column 965: reference to entity "target" for which no system identifier could be generated
    …30835&postID=101453778386923953&target=facebook' onclick='window.open(this.hre…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  204. Info Line 555, Column 136: entity was defined here
    …gID=9430835&postID=6945236942316918823&target=email' target='_blank' title='Em…
  205. Warning Line 696, Column 1284: reference not terminated by REFC delimiter
    …com/share-post.g?blogID=9430835&postID=101453778386923953&target=pinterest' ta…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  206. Warning Line 696, Column 1284: reference to external entity in attribute value
    …com/share-post.g?blogID=9430835&postID=101453778386923953&target=pinterest' ta…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  207. Error Line 696, Column 1284: reference to entity "postID" for which no system identifier could be generated
    …com/share-post.g?blogID=9430835&postID=101453778386923953&target=pinterest' ta…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  208. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  209. Warning Line 696, Column 1310: reference not terminated by REFC delimiter
    …30835&postID=101453778386923953&target=pinterest' target='_blank' title='Share…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  210. Warning Line 696, Column 1310: reference to external entity in attribute value
    …30835&postID=101453778386923953&target=pinterest' target='_blank' title='Share…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  211. Error Line 696, Column 1310: reference to entity "target" for which no system identifier could be generated
    …30835&postID=101453778386923953&target=pinterest' target='_blank' title='Share…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  212. Info Line 555, Column 136: entity was defined here
    …gID=9430835&postID=6945236942316918823&target=email' target='_blank' title='Em…
  213. Error Line 696, Column 1658: element "g:plusone" undefined
    …nk-between-golf-and.html' size='medium' width='300' annotation='inline'/></div>

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  214. Warning Line 727, Column 86: reference not terminated by REFC delimiter
    …w.blogger.com/comment.g?blogID=9430835&postID=2991244579628063153' onclick=''>3

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  215. Warning Line 727, Column 86: reference to external entity in attribute value
    …w.blogger.com/comment.g?blogID=9430835&postID=2991244579628063153' onclick=''>3

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  216. Error Line 727, Column 86: reference to entity "postID" for which no system identifier could be generated
    …w.blogger.com/comment.g?blogID=9430835&postID=2991244579628063153' onclick=''>3

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  217. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  218. Warning Line 732, Column 68: reference not terminated by REFC delimiter
    …com/email-post.g?blogID=9430835&postID=2991244579628063153' title='Email Post'…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  219. Warning Line 732, Column 68: reference to external entity in attribute value
    …com/email-post.g?blogID=9430835&postID=2991244579628063153' title='Email Post'…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  220. Error Line 732, Column 68: reference to entity "postID" for which no system identifier could be generated
    …com/email-post.g?blogID=9430835&postID=2991244579628063153' title='Email Post'…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  221. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  222. Warning Line 737, Column 67: reference not terminated by REFC delimiter
    ….com/post-edit.g?blogID=9430835&postID=2991244579628063153&from=pencil' title=…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  223. Warning Line 737, Column 67: reference to external entity in attribute value
    ….com/post-edit.g?blogID=9430835&postID=2991244579628063153&from=pencil' title=…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  224. Error Line 737, Column 67: reference to entity "postID" for which no system identifier could be generated
    ….com/post-edit.g?blogID=9430835&postID=2991244579628063153&from=pencil' title=…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  225. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  226. Warning Line 737, Column 92: reference not terminated by REFC delimiter
    …dit.g?blogID=9430835&postID=2991244579628063153&from=pencil' title='Edit Post'>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  227. Warning Line 737, Column 92: reference to external entity in attribute value
    …dit.g?blogID=9430835&postID=2991244579628063153&from=pencil' title='Edit Post'>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  228. Error Line 737, Column 92: reference to entity "from" for which no system identifier could be generated
    …dit.g?blogID=9430835&postID=2991244579628063153&from=pencil' title='Edit Post'>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  229. Info Line 542, Column 87: entity was defined here
    …dit.g?blogID=9430835&postID=6945236942316918823&from=pencil' title='Edit Post'>
  230. Warning Line 750, Column 116: reference not terminated by REFC delimiter
    …com/share-post.g?blogID=9430835&postID=2991244579628063153&target=email' targe…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  231. Warning Line 750, Column 116: reference to external entity in attribute value
    …com/share-post.g?blogID=9430835&postID=2991244579628063153&target=email' targe…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  232. Error Line 750, Column 116: reference to entity "postID" for which no system identifier could be generated
    …com/share-post.g?blogID=9430835&postID=2991244579628063153&target=email' targe…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  233. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  234. Warning Line 750, Column 143: reference not terminated by REFC delimiter
    …0835&postID=2991244579628063153&target=email' target='_blank' title='Email Thi…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  235. Warning Line 750, Column 143: reference to external entity in attribute value
    …0835&postID=2991244579628063153&target=email' target='_blank' title='Email Thi…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  236. Error Line 750, Column 143: reference to entity "target" for which no system identifier could be generated
    …0835&postID=2991244579628063153&target=email' target='_blank' title='Email Thi…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  237. Info Line 555, Column 136: entity was defined here
    …gID=9430835&postID=6945236942316918823&target=email' target='_blank' title='Em…
  238. Warning Line 750, Column 358: reference not terminated by REFC delimiter
    …com/share-post.g?blogID=9430835&postID=2991244579628063153&target=blog' onclic…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  239. Warning Line 750, Column 358: reference to external entity in attribute value
    …com/share-post.g?blogID=9430835&postID=2991244579628063153&target=blog' onclic…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  240. Error Line 750, Column 358: reference to entity "postID" for which no system identifier could be generated
    …com/share-post.g?blogID=9430835&postID=2991244579628063153&target=blog' onclic…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  241. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  242. Warning Line 750, Column 385: reference not terminated by REFC delimiter
    …0835&postID=2991244579628063153&target=blog' onclick='window.open(this.href, "…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  243. Warning Line 750, Column 385: reference to external entity in attribute value
    …0835&postID=2991244579628063153&target=blog' onclick='window.open(this.href, "…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  244. Error Line 750, Column 385: reference to entity "target" for which no system identifier could be generated
    …0835&postID=2991244579628063153&target=blog' onclick='window.open(this.href, "…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  245. Info Line 555, Column 136: entity was defined here
    …gID=9430835&postID=6945236942316918823&target=email' target='_blank' title='Em…
  246. Warning Line 750, Column 682: reference not terminated by REFC delimiter
    …com/share-post.g?blogID=9430835&postID=2991244579628063153&target=twitter' tar…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  247. Warning Line 750, Column 682: reference to external entity in attribute value
    …com/share-post.g?blogID=9430835&postID=2991244579628063153&target=twitter' tar…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  248. Error Line 750, Column 682: reference to entity "postID" for which no system identifier could be generated
    …com/share-post.g?blogID=9430835&postID=2991244579628063153&target=twitter' tar…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  249. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  250. Warning Line 750, Column 709: reference not terminated by REFC delimiter
    …0835&postID=2991244579628063153&target=twitter' target='_blank' title='Share t…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  251. Warning Line 750, Column 709: reference to external entity in attribute value
    …0835&postID=2991244579628063153&target=twitter' target='_blank' title='Share t…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  252. Error Line 750, Column 709: reference to entity "target" for which no system identifier could be generated
    …0835&postID=2991244579628063153&target=twitter' target='_blank' title='Share t…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  253. Info Line 555, Column 136: entity was defined here
    …gID=9430835&postID=6945236942316918823&target=email' target='_blank' title='Em…
  254. Warning Line 750, Column 942: reference not terminated by REFC delimiter
    …com/share-post.g?blogID=9430835&postID=2991244579628063153&target=facebook' on…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  255. Warning Line 750, Column 942: reference to external entity in attribute value
    …com/share-post.g?blogID=9430835&postID=2991244579628063153&target=facebook' on…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  256. Error Line 750, Column 942: reference to entity "postID" for which no system identifier could be generated
    …com/share-post.g?blogID=9430835&postID=2991244579628063153&target=facebook' on…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  257. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  258. Warning Line 750, Column 969: reference not terminated by REFC delimiter
    …0835&postID=2991244579628063153&target=facebook' onclick='window.open(this.hre…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  259. Warning Line 750, Column 969: reference to external entity in attribute value
    …0835&postID=2991244579628063153&target=facebook' onclick='window.open(this.hre…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  260. Error Line 750, Column 969: reference to entity "target" for which no system identifier could be generated
    …0835&postID=2991244579628063153&target=facebook' onclick='window.open(this.hre…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  261. Info Line 555, Column 136: entity was defined here
    …gID=9430835&postID=6945236942316918823&target=email' target='_blank' title='Em…
  262. Warning Line 750, Column 1288: reference not terminated by REFC delimiter
    …com/share-post.g?blogID=9430835&postID=2991244579628063153&target=pinterest' t…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  263. Warning Line 750, Column 1288: reference to external entity in attribute value
    …com/share-post.g?blogID=9430835&postID=2991244579628063153&target=pinterest' t…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  264. Error Line 750, Column 1288: reference to entity "postID" for which no system identifier could be generated
    …com/share-post.g?blogID=9430835&postID=2991244579628063153&target=pinterest' t…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  265. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  266. Warning Line 750, Column 1315: reference not terminated by REFC delimiter
    …0835&postID=2991244579628063153&target=pinterest' target='_blank' title='Share…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  267. Warning Line 750, Column 1315: reference to external entity in attribute value
    …0835&postID=2991244579628063153&target=pinterest' target='_blank' title='Share…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  268. Error Line 750, Column 1315: reference to entity "target" for which no system identifier could be generated
    …0835&postID=2991244579628063153&target=pinterest' target='_blank' title='Share…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  269. Info Line 555, Column 136: entity was defined here
    …gID=9430835&postID=6945236942316918823&target=email' target='_blank' title='Em…
  270. Error Line 750, Column 1662: element "g:plusone" undefined
    …ys-permanent-record.html' size='medium' width='300' annotation='inline'/></div>

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  271. Warning Line 779, Column 86: reference not terminated by REFC delimiter
    …w.blogger.com/comment.g?blogID=9430835&postID=9139489789318791262' onclick=''>2

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  272. Warning Line 779, Column 86: reference to external entity in attribute value
    …w.blogger.com/comment.g?blogID=9430835&postID=9139489789318791262' onclick=''>2

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  273. Error Line 779, Column 86: reference to entity "postID" for which no system identifier could be generated
    …w.blogger.com/comment.g?blogID=9430835&postID=9139489789318791262' onclick=''>2

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  274. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  275. Warning Line 784, Column 68: reference not terminated by REFC delimiter
    …com/email-post.g?blogID=9430835&postID=9139489789318791262' title='Email Post'…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  276. Warning Line 784, Column 68: reference to external entity in attribute value
    …com/email-post.g?blogID=9430835&postID=9139489789318791262' title='Email Post'…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  277. Error Line 784, Column 68: reference to entity "postID" for which no system identifier could be generated
    …com/email-post.g?blogID=9430835&postID=9139489789318791262' title='Email Post'…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  278. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  279. Warning Line 789, Column 67: reference not terminated by REFC delimiter
    ….com/post-edit.g?blogID=9430835&postID=9139489789318791262&from=pencil' title=…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  280. Warning Line 789, Column 67: reference to external entity in attribute value
    ….com/post-edit.g?blogID=9430835&postID=9139489789318791262&from=pencil' title=…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  281. Error Line 789, Column 67: reference to entity "postID" for which no system identifier could be generated
    ….com/post-edit.g?blogID=9430835&postID=9139489789318791262&from=pencil' title=…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  282. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  283. Warning Line 789, Column 92: reference not terminated by REFC delimiter
    …dit.g?blogID=9430835&postID=9139489789318791262&from=pencil' title='Edit Post'>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  284. Warning Line 789, Column 92: reference to external entity in attribute value
    …dit.g?blogID=9430835&postID=9139489789318791262&from=pencil' title='Edit Post'>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  285. Error Line 789, Column 92: reference to entity "from" for which no system identifier could be generated
    …dit.g?blogID=9430835&postID=9139489789318791262&from=pencil' title='Edit Post'>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  286. Info Line 542, Column 87: entity was defined here
    …dit.g?blogID=9430835&postID=6945236942316918823&from=pencil' title='Edit Post'>
  287. Warning Line 802, Column 116: reference not terminated by REFC delimiter
    …com/share-post.g?blogID=9430835&postID=9139489789318791262&target=email' targe…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  288. Warning Line 802, Column 116: reference to external entity in attribute value
    …com/share-post.g?blogID=9430835&postID=9139489789318791262&target=email' targe…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  289. Error Line 802, Column 116: reference to entity "postID" for which no system identifier could be generated
    …com/share-post.g?blogID=9430835&postID=9139489789318791262&target=email' targe…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  290. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  291. Warning Line 802, Column 143: reference not terminated by REFC delimiter
    …0835&postID=9139489789318791262&target=email' target='_blank' title='Email Thi…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  292. Warning Line 802, Column 143: reference to external entity in attribute value
    …0835&postID=9139489789318791262&target=email' target='_blank' title='Email Thi…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  293. Error Line 802, Column 143: reference to entity "target" for which no system identifier could be generated
    …0835&postID=9139489789318791262&target=email' target='_blank' title='Email Thi…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  294. Info Line 555, Column 136: entity was defined here
    …gID=9430835&postID=6945236942316918823&target=email' target='_blank' title='Em…
  295. Warning Line 802, Column 358: reference not terminated by REFC delimiter
    …com/share-post.g?blogID=9430835&postID=9139489789318791262&target=blog' onclic…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  296. Warning Line 802, Column 358: reference to external entity in attribute value
    …com/share-post.g?blogID=9430835&postID=9139489789318791262&target=blog' onclic…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  297. Error Line 802, Column 358: reference to entity "postID" for which no system identifier could be generated
    …com/share-post.g?blogID=9430835&postID=9139489789318791262&target=blog' onclic…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  298. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  299. Warning Line 802, Column 385: reference not terminated by REFC delimiter
    …0835&postID=9139489789318791262&target=blog' onclick='window.open(this.href, "…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  300. Warning Line 802, Column 385: reference to external entity in attribute value
    …0835&postID=9139489789318791262&target=blog' onclick='window.open(this.href, "…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  301. Error Line 802, Column 385: reference to entity "target" for which no system identifier could be generated
    …0835&postID=9139489789318791262&target=blog' onclick='window.open(this.href, "…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  302. Info Line 555, Column 136: entity was defined here
    …gID=9430835&postID=6945236942316918823&target=email' target='_blank' title='Em…
  303. Warning Line 802, Column 682: reference not terminated by REFC delimiter
    …com/share-post.g?blogID=9430835&postID=9139489789318791262&target=twitter' tar…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  304. Warning Line 802, Column 682: reference to external entity in attribute value
    …com/share-post.g?blogID=9430835&postID=9139489789318791262&target=twitter' tar…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  305. Error Line 802, Column 682: reference to entity "postID" for which no system identifier could be generated
    …com/share-post.g?blogID=9430835&postID=9139489789318791262&target=twitter' tar…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  306. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  307. Warning Line 802, Column 709: reference not terminated by REFC delimiter
    …0835&postID=9139489789318791262&target=twitter' target='_blank' title='Share t…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  308. Warning Line 802, Column 709: reference to external entity in attribute value
    …0835&postID=9139489789318791262&target=twitter' target='_blank' title='Share t…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  309. Error Line 802, Column 709: reference to entity "target" for which no system identifier could be generated
    …0835&postID=9139489789318791262&target=twitter' target='_blank' title='Share t…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  310. Info Line 555, Column 136: entity was defined here
    …gID=9430835&postID=6945236942316918823&target=email' target='_blank' title='Em…
  311. Warning Line 802, Column 942: reference not terminated by REFC delimiter
    …com/share-post.g?blogID=9430835&postID=9139489789318791262&target=facebook' on…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  312. Warning Line 802, Column 942: reference to external entity in attribute value
    …com/share-post.g?blogID=9430835&postID=9139489789318791262&target=facebook' on…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  313. Error Line 802, Column 942: reference to entity "postID" for which no system identifier could be generated
    …com/share-post.g?blogID=9430835&postID=9139489789318791262&target=facebook' on…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  314. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  315. Warning Line 802, Column 969: reference not terminated by REFC delimiter
    …0835&postID=9139489789318791262&target=facebook' onclick='window.open(this.hre…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  316. Warning Line 802, Column 969: reference to external entity in attribute value
    …0835&postID=9139489789318791262&target=facebook' onclick='window.open(this.hre…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  317. Error Line 802, Column 969: reference to entity "target" for which no system identifier could be generated
    …0835&postID=9139489789318791262&target=facebook' onclick='window.open(this.hre…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  318. Info Line 555, Column 136: entity was defined here
    …gID=9430835&postID=6945236942316918823&target=email' target='_blank' title='Em…
  319. Warning Line 802, Column 1288: reference not terminated by REFC delimiter
    …com/share-post.g?blogID=9430835&postID=9139489789318791262&target=pinterest' t…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  320. Warning Line 802, Column 1288: reference to external entity in attribute value
    …com/share-post.g?blogID=9430835&postID=9139489789318791262&target=pinterest' t…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  321. Error Line 802, Column 1288: reference to entity "postID" for which no system identifier could be generated
    …com/share-post.g?blogID=9430835&postID=9139489789318791262&target=pinterest' t…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  322. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  323. Warning Line 802, Column 1315: reference not terminated by REFC delimiter
    …0835&postID=9139489789318791262&target=pinterest' target='_blank' title='Share…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  324. Warning Line 802, Column 1315: reference to external entity in attribute value
    …0835&postID=9139489789318791262&target=pinterest' target='_blank' title='Share…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  325. Error Line 802, Column 1315: reference to entity "target" for which no system identifier could be generated
    …0835&postID=9139489789318791262&target=pinterest' target='_blank' title='Share…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  326. Info Line 555, Column 136: entity was defined here
    …gID=9430835&postID=6945236942316918823&target=email' target='_blank' title='Em…
  327. Error Line 802, Column 1669: element "g:plusone" undefined
    …nounced-as-low-brow.html' size='medium' width='300' annotation='inline'/></div>

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  328. Error Line 824, Column 165: document type does not allow element "a" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …-and-significant-flows-of-prosperity/">Biden: Amnesty Skepticism Is the Enlarg…

    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 "<a>", "<span>", or "<font>").

  329. Error Line 827, Column 191: required attribute "alt" not specified
    …g border="0" src="http://www.ingramcs.com/TDN/NewFiles/Flomax.jpg" /></a></div>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  330. Warning Line 843, Column 86: reference not terminated by REFC delimiter
    …w.blogger.com/comment.g?blogID=9430835&postID=4587202874538069951' onclick=''>0

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  331. Warning Line 843, Column 86: reference to external entity in attribute value
    …w.blogger.com/comment.g?blogID=9430835&postID=4587202874538069951' onclick=''>0

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  332. Error Line 843, Column 86: reference to entity "postID" for which no system identifier could be generated
    …w.blogger.com/comment.g?blogID=9430835&postID=4587202874538069951' onclick=''>0

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  333. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  334. Warning Line 848, Column 68: reference not terminated by REFC delimiter
    …com/email-post.g?blogID=9430835&postID=4587202874538069951' title='Email Post'…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  335. Warning Line 848, Column 68: reference to external entity in attribute value
    …com/email-post.g?blogID=9430835&postID=4587202874538069951' title='Email Post'…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  336. Error Line 848, Column 68: reference to entity "postID" for which no system identifier could be generated
    …com/email-post.g?blogID=9430835&postID=4587202874538069951' title='Email Post'…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  337. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  338. Warning Line 853, Column 67: reference not terminated by REFC delimiter
    ….com/post-edit.g?blogID=9430835&postID=4587202874538069951&from=pencil' title=…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  339. Warning Line 853, Column 67: reference to external entity in attribute value
    ….com/post-edit.g?blogID=9430835&postID=4587202874538069951&from=pencil' title=…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  340. Error Line 853, Column 67: reference to entity "postID" for which no system identifier could be generated
    ….com/post-edit.g?blogID=9430835&postID=4587202874538069951&from=pencil' title=…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  341. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  342. Warning Line 853, Column 92: reference not terminated by REFC delimiter
    …dit.g?blogID=9430835&postID=4587202874538069951&from=pencil' title='Edit Post'>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  343. Warning Line 853, Column 92: reference to external entity in attribute value
    …dit.g?blogID=9430835&postID=4587202874538069951&from=pencil' title='Edit Post'>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  344. Error Line 853, Column 92: reference to entity "from" for which no system identifier could be generated
    …dit.g?blogID=9430835&postID=4587202874538069951&from=pencil' title='Edit Post'>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  345. Info Line 542, Column 87: entity was defined here
    …dit.g?blogID=9430835&postID=6945236942316918823&from=pencil' title='Edit Post'>
  346. Warning Line 866, Column 116: reference not terminated by REFC delimiter
    …com/share-post.g?blogID=9430835&postID=4587202874538069951&target=email' targe…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  347. Warning Line 866, Column 116: reference to external entity in attribute value
    …com/share-post.g?blogID=9430835&postID=4587202874538069951&target=email' targe…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  348. Error Line 866, Column 116: reference to entity "postID" for which no system identifier could be generated
    …com/share-post.g?blogID=9430835&postID=4587202874538069951&target=email' targe…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  349. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  350. Warning Line 866, Column 143: reference not terminated by REFC delimiter
    …0835&postID=4587202874538069951&target=email' target='_blank' title='Email Thi…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  351. Warning Line 866, Column 143: reference to external entity in attribute value
    …0835&postID=4587202874538069951&target=email' target='_blank' title='Email Thi…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  352. Error Line 866, Column 143: reference to entity "target" for which no system identifier could be generated
    …0835&postID=4587202874538069951&target=email' target='_blank' title='Email Thi…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  353. Info Line 555, Column 136: entity was defined here
    …gID=9430835&postID=6945236942316918823&target=email' target='_blank' title='Em…
  354. Warning Line 866, Column 358: reference not terminated by REFC delimiter
    …com/share-post.g?blogID=9430835&postID=4587202874538069951&target=blog' onclic…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  355. Warning Line 866, Column 358: reference to external entity in attribute value
    …com/share-post.g?blogID=9430835&postID=4587202874538069951&target=blog' onclic…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  356. Error Line 866, Column 358: reference to entity "postID" for which no system identifier could be generated
    …com/share-post.g?blogID=9430835&postID=4587202874538069951&target=blog' onclic…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  357. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  358. Warning Line 866, Column 385: reference not terminated by REFC delimiter
    …0835&postID=4587202874538069951&target=blog' onclick='window.open(this.href, "…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  359. Warning Line 866, Column 385: reference to external entity in attribute value
    …0835&postID=4587202874538069951&target=blog' onclick='window.open(this.href, "…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  360. Error Line 866, Column 385: reference to entity "target" for which no system identifier could be generated
    …0835&postID=4587202874538069951&target=blog' onclick='window.open(this.href, "…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  361. Info Line 555, Column 136: entity was defined here
    …gID=9430835&postID=6945236942316918823&target=email' target='_blank' title='Em…
  362. Warning Line 866, Column 682: reference not terminated by REFC delimiter
    …com/share-post.g?blogID=9430835&postID=4587202874538069951&target=twitter' tar…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  363. Warning Line 866, Column 682: reference to external entity in attribute value
    …com/share-post.g?blogID=9430835&postID=4587202874538069951&target=twitter' tar…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  364. Error Line 866, Column 682: reference to entity "postID" for which no system identifier could be generated
    …com/share-post.g?blogID=9430835&postID=4587202874538069951&target=twitter' tar…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  365. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  366. Warning Line 866, Column 709: reference not terminated by REFC delimiter
    …0835&postID=4587202874538069951&target=twitter' target='_blank' title='Share t…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  367. Warning Line 866, Column 709: reference to external entity in attribute value
    …0835&postID=4587202874538069951&target=twitter' target='_blank' title='Share t…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  368. Error Line 866, Column 709: reference to entity "target" for which no system identifier could be generated
    …0835&postID=4587202874538069951&target=twitter' target='_blank' title='Share t…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  369. Info Line 555, Column 136: entity was defined here
    …gID=9430835&postID=6945236942316918823&target=email' target='_blank' title='Em…
  370. Warning Line 866, Column 942: reference not terminated by REFC delimiter
    …com/share-post.g?blogID=9430835&postID=4587202874538069951&target=facebook' on…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  371. Warning Line 866, Column 942: reference to external entity in attribute value
    …com/share-post.g?blogID=9430835&postID=4587202874538069951&target=facebook' on…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  372. Error Line 866, Column 942: reference to entity "postID" for which no system identifier could be generated
    …com/share-post.g?blogID=9430835&postID=4587202874538069951&target=facebook' on…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  373. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  374. Warning Line 866, Column 969: reference not terminated by REFC delimiter
    …0835&postID=4587202874538069951&target=facebook' onclick='window.open(this.hre…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  375. Warning Line 866, Column 969: reference to external entity in attribute value
    …0835&postID=4587202874538069951&target=facebook' onclick='window.open(this.hre…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  376. Error Line 866, Column 969: reference to entity "target" for which no system identifier could be generated
    …0835&postID=4587202874538069951&target=facebook' onclick='window.open(this.hre…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  377. Info Line 555, Column 136: entity was defined here
    …gID=9430835&postID=6945236942316918823&target=email' target='_blank' title='Em…
  378. Warning Line 866, Column 1288: reference not terminated by REFC delimiter
    …com/share-post.g?blogID=9430835&postID=4587202874538069951&target=pinterest' t…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  379. Warning Line 866, Column 1288: reference to external entity in attribute value
    …com/share-post.g?blogID=9430835&postID=4587202874538069951&target=pinterest' t…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  380. Error Line 866, Column 1288: reference to entity "postID" for which no system identifier could be generated
    …com/share-post.g?blogID=9430835&postID=4587202874538069951&target=pinterest' t…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  381. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  382. Warning Line 866, Column 1315: reference not terminated by REFC delimiter
    …0835&postID=4587202874538069951&target=pinterest' target='_blank' title='Share…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  383. Warning Line 866, Column 1315: reference to external entity in attribute value
    …0835&postID=4587202874538069951&target=pinterest' target='_blank' title='Share…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  384. Error Line 866, Column 1315: reference to entity "target" for which no system identifier could be generated
    …0835&postID=4587202874538069951&target=pinterest' target='_blank' title='Share…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  385. Info Line 555, Column 136: entity was defined here
    …gID=9430835&postID=6945236942316918823&target=email' target='_blank' title='Em…
  386. Error Line 866, Column 1667: element "g:plusone" undefined
    …ress-pass-urination.html' size='medium' width='300' annotation='inline'/></div>

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  387. Warning Line 906, Column 86: reference not terminated by REFC delimiter
    ….blogger.com/comment.g?blogID=9430835&postID=3783166303458108287' onclick=''>11

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  388. Warning Line 906, Column 86: reference to external entity in attribute value
    ….blogger.com/comment.g?blogID=9430835&postID=3783166303458108287' onclick=''>11

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  389. Error Line 906, Column 86: reference to entity "postID" for which no system identifier could be generated
    ….blogger.com/comment.g?blogID=9430835&postID=3783166303458108287' onclick=''>11

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  390. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  391. Warning Line 911, Column 68: reference not terminated by REFC delimiter
    …com/email-post.g?blogID=9430835&postID=3783166303458108287' title='Email Post'…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  392. Warning Line 911, Column 68: reference to external entity in attribute value
    …com/email-post.g?blogID=9430835&postID=3783166303458108287' title='Email Post'…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  393. Error Line 911, Column 68: reference to entity "postID" for which no system identifier could be generated
    …com/email-post.g?blogID=9430835&postID=3783166303458108287' title='Email Post'…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  394. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  395. Warning Line 916, Column 67: reference not terminated by REFC delimiter
    ….com/post-edit.g?blogID=9430835&postID=3783166303458108287&from=pencil' title=…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  396. Warning Line 916, Column 67: reference to external entity in attribute value
    ….com/post-edit.g?blogID=9430835&postID=3783166303458108287&from=pencil' title=…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  397. Error Line 916, Column 67: reference to entity "postID" for which no system identifier could be generated
    ….com/post-edit.g?blogID=9430835&postID=3783166303458108287&from=pencil' title=…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  398. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  399. Warning Line 916, Column 92: reference not terminated by REFC delimiter
    …dit.g?blogID=9430835&postID=3783166303458108287&from=pencil' title='Edit Post'>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  400. Warning Line 916, Column 92: reference to external entity in attribute value
    …dit.g?blogID=9430835&postID=3783166303458108287&from=pencil' title='Edit Post'>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  401. Error Line 916, Column 92: reference to entity "from" for which no system identifier could be generated
    …dit.g?blogID=9430835&postID=3783166303458108287&from=pencil' title='Edit Post'>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  402. Info Line 542, Column 87: entity was defined here
    …dit.g?blogID=9430835&postID=6945236942316918823&from=pencil' title='Edit Post'>
  403. Warning Line 929, Column 116: reference not terminated by REFC delimiter
    …com/share-post.g?blogID=9430835&postID=3783166303458108287&target=email' targe…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  404. Warning Line 929, Column 116: reference to external entity in attribute value
    …com/share-post.g?blogID=9430835&postID=3783166303458108287&target=email' targe…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  405. Error Line 929, Column 116: reference to entity "postID" for which no system identifier could be generated
    …com/share-post.g?blogID=9430835&postID=3783166303458108287&target=email' targe…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  406. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  407. Warning Line 929, Column 143: reference not terminated by REFC delimiter
    …0835&postID=3783166303458108287&target=email' target='_blank' title='Email Thi…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  408. Warning Line 929, Column 143: reference to external entity in attribute value
    …0835&postID=3783166303458108287&target=email' target='_blank' title='Email Thi…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  409. Error Line 929, Column 143: reference to entity "target" for which no system identifier could be generated
    …0835&postID=3783166303458108287&target=email' target='_blank' title='Email Thi…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  410. Info Line 555, Column 136: entity was defined here
    …gID=9430835&postID=6945236942316918823&target=email' target='_blank' title='Em…
  411. Warning Line 929, Column 358: reference not terminated by REFC delimiter
    …com/share-post.g?blogID=9430835&postID=3783166303458108287&target=blog' onclic…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  412. Warning Line 929, Column 358: reference to external entity in attribute value
    …com/share-post.g?blogID=9430835&postID=3783166303458108287&target=blog' onclic…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  413. Error Line 929, Column 358: reference to entity "postID" for which no system identifier could be generated
    …com/share-post.g?blogID=9430835&postID=3783166303458108287&target=blog' onclic…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  414. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  415. Warning Line 929, Column 385: reference not terminated by REFC delimiter
    …0835&postID=3783166303458108287&target=blog' onclick='window.open(this.href, "…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  416. Warning Line 929, Column 385: reference to external entity in attribute value
    …0835&postID=3783166303458108287&target=blog' onclick='window.open(this.href, "…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  417. Error Line 929, Column 385: reference to entity "target" for which no system identifier could be generated
    …0835&postID=3783166303458108287&target=blog' onclick='window.open(this.href, "…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  418. Info Line 555, Column 136: entity was defined here
    …gID=9430835&postID=6945236942316918823&target=email' target='_blank' title='Em…
  419. Warning Line 929, Column 682: reference not terminated by REFC delimiter
    …com/share-post.g?blogID=9430835&postID=3783166303458108287&target=twitter' tar…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  420. Warning Line 929, Column 682: reference to external entity in attribute value
    …com/share-post.g?blogID=9430835&postID=3783166303458108287&target=twitter' tar…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  421. Error Line 929, Column 682: reference to entity "postID" for which no system identifier could be generated
    …com/share-post.g?blogID=9430835&postID=3783166303458108287&target=twitter' tar…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  422. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  423. Warning Line 929, Column 709: reference not terminated by REFC delimiter
    …0835&postID=3783166303458108287&target=twitter' target='_blank' title='Share t…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  424. Warning Line 929, Column 709: reference to external entity in attribute value
    …0835&postID=3783166303458108287&target=twitter' target='_blank' title='Share t…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  425. Error Line 929, Column 709: reference to entity "target" for which no system identifier could be generated
    …0835&postID=3783166303458108287&target=twitter' target='_blank' title='Share t…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  426. Info Line 555, Column 136: entity was defined here
    …gID=9430835&postID=6945236942316918823&target=email' target='_blank' title='Em…
  427. Warning Line 929, Column 942: reference not terminated by REFC delimiter
    …com/share-post.g?blogID=9430835&postID=3783166303458108287&target=facebook' on…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  428. Warning Line 929, Column 942: reference to external entity in attribute value
    …com/share-post.g?blogID=9430835&postID=3783166303458108287&target=facebook' on…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  429. Error Line 929, Column 942: reference to entity "postID" for which no system identifier could be generated
    …com/share-post.g?blogID=9430835&postID=3783166303458108287&target=facebook' on…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  430. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  431. Warning Line 929, Column 969: reference not terminated by REFC delimiter
    …0835&postID=3783166303458108287&target=facebook' onclick='window.open(this.hre…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  432. Warning Line 929, Column 969: reference to external entity in attribute value
    …0835&postID=3783166303458108287&target=facebook' onclick='window.open(this.hre…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  433. Error Line 929, Column 969: reference to entity "target" for which no system identifier could be generated
    …0835&postID=3783166303458108287&target=facebook' onclick='window.open(this.hre…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  434. Info Line 555, Column 136: entity was defined here
    …gID=9430835&postID=6945236942316918823&target=email' target='_blank' title='Em…
  435. Warning Line 929, Column 1288: reference not terminated by REFC delimiter
    …com/share-post.g?blogID=9430835&postID=3783166303458108287&target=pinterest' t…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  436. Warning Line 929, Column 1288: reference to external entity in attribute value
    …com/share-post.g?blogID=9430835&postID=3783166303458108287&target=pinterest' t…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  437. Error Line 929, Column 1288: reference to entity "postID" for which no system identifier could be generated
    …com/share-post.g?blogID=9430835&postID=3783166303458108287&target=pinterest' t…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  438. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  439. Warning Line 929, Column 1315: reference not terminated by REFC delimiter
    …0835&postID=3783166303458108287&target=pinterest' target='_blank' title='Share…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  440. Warning Line 929, Column 1315: reference to external entity in attribute value
    …0835&postID=3783166303458108287&target=pinterest' target='_blank' title='Share…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  441. Error Line 929, Column 1315: reference to entity "target" for which no system identifier could be generated
    …0835&postID=3783166303458108287&target=pinterest' target='_blank' title='Share…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  442. Info Line 555, Column 136: entity was defined here
    …gID=9430835&postID=6945236942316918823&target=email' target='_blank' title='Em…
  443. Error Line 929, Column 1647: element "g:plusone" undefined
    …6/eric-cantor-loses.html' size='medium' width='300' annotation='inline'/></div>

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  444. Warning Line 962, Column 86: reference not terminated by REFC delimiter
    …er.com/comment.g?blogID=9430835&postID=7071899043929548779' onclick=''>1 comme…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  445. Warning Line 962, Column 86: reference to external entity in attribute value
    …er.com/comment.g?blogID=9430835&postID=7071899043929548779' onclick=''>1 comme…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  446. Error Line 962, Column 86: reference to entity "postID" for which no system identifier could be generated
    …er.com/comment.g?blogID=9430835&postID=7071899043929548779' onclick=''>1 comme…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  447. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  448. Warning Line 966, Column 68: reference not terminated by REFC delimiter
    …com/email-post.g?blogID=9430835&postID=7071899043929548779' title='Email Post'…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  449. Warning Line 966, Column 68: reference to external entity in attribute value
    …com/email-post.g?blogID=9430835&postID=7071899043929548779' title='Email Post'…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  450. Error Line 966, Column 68: reference to entity "postID" for which no system identifier could be generated
    …com/email-post.g?blogID=9430835&postID=7071899043929548779' title='Email Post'…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  451. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  452. Warning Line 971, Column 67: reference not terminated by REFC delimiter
    ….com/post-edit.g?blogID=9430835&postID=7071899043929548779&from=pencil' title=…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  453. Warning Line 971, Column 67: reference to external entity in attribute value
    ….com/post-edit.g?blogID=9430835&postID=7071899043929548779&from=pencil' title=…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  454. Error Line 971, Column 67: reference to entity "postID" for which no system identifier could be generated
    ….com/post-edit.g?blogID=9430835&postID=7071899043929548779&from=pencil' title=…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  455. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  456. Warning Line 971, Column 92: reference not terminated by REFC delimiter
    …dit.g?blogID=9430835&postID=7071899043929548779&from=pencil' title='Edit Post'>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  457. Warning Line 971, Column 92: reference to external entity in attribute value
    …dit.g?blogID=9430835&postID=7071899043929548779&from=pencil' title='Edit Post'>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  458. Error Line 971, Column 92: reference to entity "from" for which no system identifier could be generated
    …dit.g?blogID=9430835&postID=7071899043929548779&from=pencil' title='Edit Post'>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  459. Info Line 542, Column 87: entity was defined here
    …dit.g?blogID=9430835&postID=6945236942316918823&from=pencil' title='Edit Post'>
  460. Warning Line 984, Column 116: reference not terminated by REFC delimiter
    …com/share-post.g?blogID=9430835&postID=7071899043929548779&target=email' targe…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  461. Warning Line 984, Column 116: reference to external entity in attribute value
    …com/share-post.g?blogID=9430835&postID=7071899043929548779&target=email' targe…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  462. Error Line 984, Column 116: reference to entity "postID" for which no system identifier could be generated
    …com/share-post.g?blogID=9430835&postID=7071899043929548779&target=email' targe…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  463. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  464. Warning Line 984, Column 143: reference not terminated by REFC delimiter
    …0835&postID=7071899043929548779&target=email' target='_blank' title='Email Thi…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  465. Warning Line 984, Column 143: reference to external entity in attribute value
    …0835&postID=7071899043929548779&target=email' target='_blank' title='Email Thi…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  466. Error Line 984, Column 143: reference to entity "target" for which no system identifier could be generated
    …0835&postID=7071899043929548779&target=email' target='_blank' title='Email Thi…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  467. Info Line 555, Column 136: entity was defined here
    …gID=9430835&postID=6945236942316918823&target=email' target='_blank' title='Em…
  468. Warning Line 984, Column 358: reference not terminated by REFC delimiter
    …com/share-post.g?blogID=9430835&postID=7071899043929548779&target=blog' onclic…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  469. Warning Line 984, Column 358: reference to external entity in attribute value
    …com/share-post.g?blogID=9430835&postID=7071899043929548779&target=blog' onclic…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  470. Error Line 984, Column 358: reference to entity "postID" for which no system identifier could be generated
    …com/share-post.g?blogID=9430835&postID=7071899043929548779&target=blog' onclic…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  471. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  472. Warning Line 984, Column 385: reference not terminated by REFC delimiter
    …0835&postID=7071899043929548779&target=blog' onclick='window.open(this.href, "…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  473. Warning Line 984, Column 385: reference to external entity in attribute value
    …0835&postID=7071899043929548779&target=blog' onclick='window.open(this.href, "…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  474. Error Line 984, Column 385: reference to entity "target" for which no system identifier could be generated
    …0835&postID=7071899043929548779&target=blog' onclick='window.open(this.href, "…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  475. Info Line 555, Column 136: entity was defined here
    …gID=9430835&postID=6945236942316918823&target=email' target='_blank' title='Em…
  476. Warning Line 984, Column 682: reference not terminated by REFC delimiter
    …com/share-post.g?blogID=9430835&postID=7071899043929548779&target=twitter' tar…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  477. Warning Line 984, Column 682: reference to external entity in attribute value
    …com/share-post.g?blogID=9430835&postID=7071899043929548779&target=twitter' tar…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  478. Error Line 984, Column 682: reference to entity "postID" for which no system identifier could be generated
    …com/share-post.g?blogID=9430835&postID=7071899043929548779&target=twitter' tar…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  479. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  480. Warning Line 984, Column 709: reference not terminated by REFC delimiter
    …0835&postID=7071899043929548779&target=twitter' target='_blank' title='Share t…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  481. Warning Line 984, Column 709: reference to external entity in attribute value
    …0835&postID=7071899043929548779&target=twitter' target='_blank' title='Share t…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  482. Error Line 984, Column 709: reference to entity "target" for which no system identifier could be generated
    …0835&postID=7071899043929548779&target=twitter' target='_blank' title='Share t…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  483. Info Line 555, Column 136: entity was defined here
    …gID=9430835&postID=6945236942316918823&target=email' target='_blank' title='Em…
  484. Warning Line 984, Column 942: reference not terminated by REFC delimiter
    …com/share-post.g?blogID=9430835&postID=7071899043929548779&target=facebook' on…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  485. Warning Line 984, Column 942: reference to external entity in attribute value
    …com/share-post.g?blogID=9430835&postID=7071899043929548779&target=facebook' on…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  486. Error Line 984, Column 942: reference to entity "postID" for which no system identifier could be generated
    …com/share-post.g?blogID=9430835&postID=7071899043929548779&target=facebook' on…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  487. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  488. Warning Line 984, Column 969: reference not terminated by REFC delimiter
    …0835&postID=7071899043929548779&target=facebook' onclick='window.open(this.hre…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  489. Warning Line 984, Column 969: reference to external entity in attribute value
    …0835&postID=7071899043929548779&target=facebook' onclick='window.open(this.hre…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  490. Error Line 984, Column 969: reference to entity "target" for which no system identifier could be generated
    …0835&postID=7071899043929548779&target=facebook' onclick='window.open(this.hre…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  491. Info Line 555, Column 136: entity was defined here
    …gID=9430835&postID=6945236942316918823&target=email' target='_blank' title='Em…
  492. Warning Line 984, Column 1288: reference not terminated by REFC delimiter
    …com/share-post.g?blogID=9430835&postID=7071899043929548779&target=pinterest' t…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  493. Warning Line 984, Column 1288: reference to external entity in attribute value
    …com/share-post.g?blogID=9430835&postID=7071899043929548779&target=pinterest' t…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  494. Error Line 984, Column 1288: reference to entity "postID" for which no system identifier could be generated
    …com/share-post.g?blogID=9430835&postID=7071899043929548779&target=pinterest' t…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  495. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  496. Warning Line 984, Column 1315: reference not terminated by REFC delimiter
    …0835&postID=7071899043929548779&target=pinterest' target='_blank' title='Share…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  497. Warning Line 984, Column 1315: reference to external entity in attribute value
    …0835&postID=7071899043929548779&target=pinterest' target='_blank' title='Share…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  498. Error Line 984, Column 1315: reference to entity "target" for which no system identifier could be generated
    …0835&postID=7071899043929548779&target=pinterest' target='_blank' title='Share…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  499. Info Line 555, Column 136: entity was defined here
    …gID=9430835&postID=6945236942316918823&target=email' target='_blank' title='Em…
  500. Error Line 984, Column 1665: element "g:plusone" undefined
    …ke-family-formation.html' size='medium' width='300' annotation='inline'/></div>

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  501. Warning Line 1014, Column 86: reference not terminated by REFC delimiter
    …ww.blogger.com/comment.g?blogID=9430835&postID=977488074256261437' onclick=''>3

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  502. Warning Line 1014, Column 86: reference to external entity in attribute value
    …ww.blogger.com/comment.g?blogID=9430835&postID=977488074256261437' onclick=''>3

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  503. Error Line 1014, Column 86: reference to entity "postID" for which no system identifier could be generated
    …ww.blogger.com/comment.g?blogID=9430835&postID=977488074256261437' onclick=''>3

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  504. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  505. Warning Line 1019, Column 68: reference not terminated by REFC delimiter
    ….com/email-post.g?blogID=9430835&postID=977488074256261437' title='Email Post'>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  506. Warning Line 1019, Column 68: reference to external entity in attribute value
    ….com/email-post.g?blogID=9430835&postID=977488074256261437' title='Email Post'>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  507. Error Line 1019, Column 68: reference to entity "postID" for which no system identifier could be generated
    ….com/email-post.g?blogID=9430835&postID=977488074256261437' title='Email Post'>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  508. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  509. Warning Line 1024, Column 67: reference not terminated by REFC delimiter
    ….com/post-edit.g?blogID=9430835&postID=977488074256261437&from=pencil' title='…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  510. Warning Line 1024, Column 67: reference to external entity in attribute value
    ….com/post-edit.g?blogID=9430835&postID=977488074256261437&from=pencil' title='…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  511. Error Line 1024, Column 67: reference to entity "postID" for which no system identifier could be generated
    ….com/post-edit.g?blogID=9430835&postID=977488074256261437&from=pencil' title='…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  512. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  513. Warning Line 1024, Column 91: reference not terminated by REFC delimiter
    …edit.g?blogID=9430835&postID=977488074256261437&from=pencil' title='Edit Post'>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  514. Warning Line 1024, Column 91: reference to external entity in attribute value
    …edit.g?blogID=9430835&postID=977488074256261437&from=pencil' title='Edit Post'>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  515. Error Line 1024, Column 91: reference to entity "from" for which no system identifier could be generated
    …edit.g?blogID=9430835&postID=977488074256261437&from=pencil' title='Edit Post'>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  516. Info Line 542, Column 87: entity was defined here
    …dit.g?blogID=9430835&postID=6945236942316918823&from=pencil' title='Edit Post'>
  517. Warning Line 1037, Column 116: reference not terminated by REFC delimiter
    …com/share-post.g?blogID=9430835&postID=977488074256261437&target=email' target…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  518. Warning Line 1037, Column 116: reference to external entity in attribute value
    …com/share-post.g?blogID=9430835&postID=977488074256261437&target=email' target…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  519. Error Line 1037, Column 116: reference to entity "postID" for which no system identifier could be generated
    …com/share-post.g?blogID=9430835&postID=977488074256261437&target=email' target…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  520. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  521. Warning Line 1037, Column 142: reference not terminated by REFC delimiter
    …30835&postID=977488074256261437&target=email' target='_blank' title='Email Thi…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  522. Warning Line 1037, Column 142: reference to external entity in attribute value
    …30835&postID=977488074256261437&target=email' target='_blank' title='Email Thi…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  523. Error Line 1037, Column 142: reference to entity "target" for which no system identifier could be generated
    …30835&postID=977488074256261437&target=email' target='_blank' title='Email Thi…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  524. Info Line 555, Column 136: entity was defined here
    …gID=9430835&postID=6945236942316918823&target=email' target='_blank' title='Em…
  525. Warning Line 1037, Column 357: reference not terminated by REFC delimiter
    …com/share-post.g?blogID=9430835&postID=977488074256261437&target=blog' onclick…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  526. Warning Line 1037, Column 357: reference to external entity in attribute value
    …com/share-post.g?blogID=9430835&postID=977488074256261437&target=blog' onclick…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  527. Error Line 1037, Column 357: reference to entity "postID" for which no system identifier could be generated
    …com/share-post.g?blogID=9430835&postID=977488074256261437&target=blog' onclick…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  528. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  529. Warning Line 1037, Column 383: reference not terminated by REFC delimiter
    …30835&postID=977488074256261437&target=blog' onclick='window.open(this.href, "…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  530. Warning Line 1037, Column 383: reference to external entity in attribute value
    …30835&postID=977488074256261437&target=blog' onclick='window.open(this.href, "…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  531. Error Line 1037, Column 383: reference to entity "target" for which no system identifier could be generated
    …30835&postID=977488074256261437&target=blog' onclick='window.open(this.href, "…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  532. Info Line 555, Column 136: entity was defined here
    …gID=9430835&postID=6945236942316918823&target=email' target='_blank' title='Em…
  533. Warning Line 1037, Column 680: reference not terminated by REFC delimiter
    …com/share-post.g?blogID=9430835&postID=977488074256261437&target=twitter' targ…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  534. Warning Line 1037, Column 680: reference to external entity in attribute value
    …com/share-post.g?blogID=9430835&postID=977488074256261437&target=twitter' targ…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  535. Error Line 1037, Column 680: reference to entity "postID" for which no system identifier could be generated
    …com/share-post.g?blogID=9430835&postID=977488074256261437&target=twitter' targ…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  536. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  537. Warning Line 1037, Column 706: reference not terminated by REFC delimiter
    …30835&postID=977488074256261437&target=twitter' target='_blank' title='Share t…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  538. Warning Line 1037, Column 706: reference to external entity in attribute value
    …30835&postID=977488074256261437&target=twitter' target='_blank' title='Share t…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  539. Error Line 1037, Column 706: reference to entity "target" for which no system identifier could be generated
    …30835&postID=977488074256261437&target=twitter' target='_blank' title='Share t…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  540. Info Line 555, Column 136: entity was defined here
    …gID=9430835&postID=6945236942316918823&target=email' target='_blank' title='Em…
  541. Warning Line 1037, Column 939: reference not terminated by REFC delimiter
    …com/share-post.g?blogID=9430835&postID=977488074256261437&target=facebook' onc…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  542. Warning Line 1037, Column 939: reference to external entity in attribute value
    …com/share-post.g?blogID=9430835&postID=977488074256261437&target=facebook' onc…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  543. Error Line 1037, Column 939: reference to entity "postID" for which no system identifier could be generated
    …com/share-post.g?blogID=9430835&postID=977488074256261437&target=facebook' onc…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  544. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  545. Warning Line 1037, Column 965: reference not terminated by REFC delimiter
    …30835&postID=977488074256261437&target=facebook' onclick='window.open(this.hre…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  546. Warning Line 1037, Column 965: reference to external entity in attribute value
    …30835&postID=977488074256261437&target=facebook' onclick='window.open(this.hre…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  547. Error Line 1037, Column 965: reference to entity "target" for which no system identifier could be generated
    …30835&postID=977488074256261437&target=facebook' onclick='window.open(this.hre…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  548. Info Line 555, Column 136: entity was defined here
    …gID=9430835&postID=6945236942316918823&target=email' target='_blank' title='Em…
  549. Warning Line 1037, Column 1284: reference not terminated by REFC delimiter
    …com/share-post.g?blogID=9430835&postID=977488074256261437&target=pinterest' ta…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  550. Warning Line 1037, Column 1284: reference to external entity in attribute value
    …com/share-post.g?blogID=9430835&postID=977488074256261437&target=pinterest' ta…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  551. Error Line 1037, Column 1284: reference to entity "postID" for which no system identifier could be generated
    …com/share-post.g?blogID=9430835&postID=977488074256261437&target=pinterest' ta…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  552. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  553. Warning Line 1037, Column 1310: reference not terminated by REFC delimiter
    …30835&postID=977488074256261437&target=pinterest' target='_blank' title='Share…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  554. Warning Line 1037, Column 1310: reference to external entity in attribute value
    …30835&postID=977488074256261437&target=pinterest' target='_blank' title='Share…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  555. Error Line 1037, Column 1310: reference to entity "target" for which no system identifier could be generated
    …30835&postID=977488074256261437&target=pinterest' target='_blank' title='Share…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  556. Info Line 555, Column 136: entity was defined here
    …gID=9430835&postID=6945236942316918823&target=email' target='_blank' title='Em…
  557. Error Line 1037, Column 1665: element "g:plusone" undefined
    …-same-mistake-twice.html' size='medium' width='300' annotation='inline'/></div>

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  558. Warning Line 1076, Column 86: reference not terminated by REFC delimiter
    …w.blogger.com/comment.g?blogID=9430835&postID=9060260648925518667' onclick=''>5

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  559. Warning Line 1076, Column 86: reference to external entity in attribute value
    …w.blogger.com/comment.g?blogID=9430835&postID=9060260648925518667' onclick=''>5

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  560. Error Line 1076, Column 86: reference to entity "postID" for which no system identifier could be generated
    …w.blogger.com/comment.g?blogID=9430835&postID=9060260648925518667' onclick=''>5

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  561. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  562. Warning Line 1081, Column 68: reference not terminated by REFC delimiter
    …com/email-post.g?blogID=9430835&postID=9060260648925518667' title='Email Post'…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  563. Warning Line 1081, Column 68: reference to external entity in attribute value
    …com/email-post.g?blogID=9430835&postID=9060260648925518667' title='Email Post'…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  564. Error Line 1081, Column 68: reference to entity "postID" for which no system identifier could be generated
    …com/email-post.g?blogID=9430835&postID=9060260648925518667' title='Email Post'…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  565. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  566. Warning Line 1086, Column 67: reference not terminated by REFC delimiter
    ….com/post-edit.g?blogID=9430835&postID=9060260648925518667&from=pencil' title=…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  567. Warning Line 1086, Column 67: reference to external entity in attribute value
    ….com/post-edit.g?blogID=9430835&postID=9060260648925518667&from=pencil' title=…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  568. Error Line 1086, Column 67: reference to entity "postID" for which no system identifier could be generated
    ….com/post-edit.g?blogID=9430835&postID=9060260648925518667&from=pencil' title=…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  569. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  570. Warning Line 1086, Column 92: reference not terminated by REFC delimiter
    …dit.g?blogID=9430835&postID=9060260648925518667&from=pencil' title='Edit Post'>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  571. Warning Line 1086, Column 92: reference to external entity in attribute value
    …dit.g?blogID=9430835&postID=9060260648925518667&from=pencil' title='Edit Post'>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  572. Error Line 1086, Column 92: reference to entity "from" for which no system identifier could be generated
    …dit.g?blogID=9430835&postID=9060260648925518667&from=pencil' title='Edit Post'>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  573. Info Line 542, Column 87: entity was defined here
    …dit.g?blogID=9430835&postID=6945236942316918823&from=pencil' title='Edit Post'>
  574. Warning Line 1099, Column 116: reference not terminated by REFC delimiter
    …com/share-post.g?blogID=9430835&postID=9060260648925518667&target=email' targe…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  575. Warning Line 1099, Column 116: reference to external entity in attribute value
    …com/share-post.g?blogID=9430835&postID=9060260648925518667&target=email' targe…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  576. Error Line 1099, Column 116: reference to entity "postID" for which no system identifier could be generated
    …com/share-post.g?blogID=9430835&postID=9060260648925518667&target=email' targe…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  577. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  578. Warning Line 1099, Column 143: reference not terminated by REFC delimiter
    …0835&postID=9060260648925518667&target=email' target='_blank' title='Email Thi…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  579. Warning Line 1099, Column 143: reference to external entity in attribute value
    …0835&postID=9060260648925518667&target=email' target='_blank' title='Email Thi…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  580. Error Line 1099, Column 143: reference to entity "target" for which no system identifier could be generated
    …0835&postID=9060260648925518667&target=email' target='_blank' title='Email Thi…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  581. Info Line 555, Column 136: entity was defined here
    …gID=9430835&postID=6945236942316918823&target=email' target='_blank' title='Em…
  582. Warning Line 1099, Column 358: reference not terminated by REFC delimiter
    …com/share-post.g?blogID=9430835&postID=9060260648925518667&target=blog' onclic…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  583. Warning Line 1099, Column 358: reference to external entity in attribute value
    …com/share-post.g?blogID=9430835&postID=9060260648925518667&target=blog' onclic…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  584. Error Line 1099, Column 358: reference to entity "postID" for which no system identifier could be generated
    …com/share-post.g?blogID=9430835&postID=9060260648925518667&target=blog' onclic…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  585. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  586. Warning Line 1099, Column 385: reference not terminated by REFC delimiter
    …0835&postID=9060260648925518667&target=blog' onclick='window.open(this.href, "…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  587. Warning Line 1099, Column 385: reference to external entity in attribute value
    …0835&postID=9060260648925518667&target=blog' onclick='window.open(this.href, "…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  588. Error Line 1099, Column 385: reference to entity "target" for which no system identifier could be generated
    …0835&postID=9060260648925518667&target=blog' onclick='window.open(this.href, "…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  589. Info Line 555, Column 136: entity was defined here
    …gID=9430835&postID=6945236942316918823&target=email' target='_blank' title='Em…
  590. Warning Line 1099, Column 682: reference not terminated by REFC delimiter
    …com/share-post.g?blogID=9430835&postID=9060260648925518667&target=twitter' tar…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  591. Warning Line 1099, Column 682: reference to external entity in attribute value
    …com/share-post.g?blogID=9430835&postID=9060260648925518667&target=twitter' tar…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  592. Error Line 1099, Column 682: reference to entity "postID" for which no system identifier could be generated
    …com/share-post.g?blogID=9430835&postID=9060260648925518667&target=twitter' tar…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  593. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  594. Warning Line 1099, Column 709: reference not terminated by REFC delimiter
    …0835&postID=9060260648925518667&target=twitter' target='_blank' title='Share t…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  595. Warning Line 1099, Column 709: reference to external entity in attribute value
    …0835&postID=9060260648925518667&target=twitter' target='_blank' title='Share t…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  596. Error Line 1099, Column 709: reference to entity "target" for which no system identifier could be generated
    …0835&postID=9060260648925518667&target=twitter' target='_blank' title='Share t…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  597. Info Line 555, Column 136: entity was defined here
    …gID=9430835&postID=6945236942316918823&target=email' target='_blank' title='Em…
  598. Warning Line 1099, Column 942: reference not terminated by REFC delimiter
    …com/share-post.g?blogID=9430835&postID=9060260648925518667&target=facebook' on…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  599. Warning Line 1099, Column 942: reference to external entity in attribute value
    …com/share-post.g?blogID=9430835&postID=9060260648925518667&target=facebook' on…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  600. Error Line 1099, Column 942: reference to entity "postID" for which no system identifier could be generated
    …com/share-post.g?blogID=9430835&postID=9060260648925518667&target=facebook' on…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  601. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  602. Warning Line 1099, Column 969: reference not terminated by REFC delimiter
    …0835&postID=9060260648925518667&target=facebook' onclick='window.open(this.hre…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  603. Warning Line 1099, Column 969: reference to external entity in attribute value
    …0835&postID=9060260648925518667&target=facebook' onclick='window.open(this.hre…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  604. Error Line 1099, Column 969: reference to entity "target" for which no system identifier could be generated
    …0835&postID=9060260648925518667&target=facebook' onclick='window.open(this.hre…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  605. Info Line 555, Column 136: entity was defined here
    …gID=9430835&postID=6945236942316918823&target=email' target='_blank' title='Em…
  606. Warning Line 1099, Column 1288: reference not terminated by REFC delimiter
    …com/share-post.g?blogID=9430835&postID=9060260648925518667&target=pinterest' t…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  607. Warning Line 1099, Column 1288: reference to external entity in attribute value
    …com/share-post.g?blogID=9430835&postID=9060260648925518667&target=pinterest' t…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  608. Error Line 1099, Column 1288: reference to entity "postID" for which no system identifier could be generated
    …com/share-post.g?blogID=9430835&postID=9060260648925518667&target=pinterest' t…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  609. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  610. Warning Line 1099, Column 1315: reference not terminated by REFC delimiter
    …0835&postID=9060260648925518667&target=pinterest' target='_blank' title='Share…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  611. Warning Line 1099, Column 1315: reference to external entity in attribute value
    …0835&postID=9060260648925518667&target=pinterest' target='_blank' title='Share…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  612. Error Line 1099, Column 1315: reference to entity "target" for which no system identifier could be generated
    …0835&postID=9060260648925518667&target=pinterest' target='_blank' title='Share…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  613. Info Line 555, Column 136: entity was defined here
    …gID=9430835&postID=6945236942316918823&target=email' target='_blank' title='Em…
  614. Error Line 1099, Column 1649: element "g:plusone" undefined
    …kon-tiki-vindicated.html' size='medium' width='300' annotation='inline'/></div>

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  615. Warning Line 1134, Column 86: reference not terminated by REFC delimiter
    …er.com/comment.g?blogID=9430835&postID=5736346114523015579' onclick=''>1 comme…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  616. Warning Line 1134, Column 86: reference to external entity in attribute value
    …er.com/comment.g?blogID=9430835&postID=5736346114523015579' onclick=''>1 comme…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  617. Error Line 1134, Column 86: reference to entity "postID" for which no system identifier could be generated
    …er.com/comment.g?blogID=9430835&postID=5736346114523015579' onclick=''>1 comme…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  618. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  619. Warning Line 1138, Column 68: reference not terminated by REFC delimiter
    …com/email-post.g?blogID=9430835&postID=5736346114523015579' title='Email Post'…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  620. Warning Line 1138, Column 68: reference to external entity in attribute value
    …com/email-post.g?blogID=9430835&postID=5736346114523015579' title='Email Post'…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  621. Error Line 1138, Column 68: reference to entity "postID" for which no system identifier could be generated
    …com/email-post.g?blogID=9430835&postID=5736346114523015579' title='Email Post'…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  622. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  623. Warning Line 1143, Column 67: reference not terminated by REFC delimiter
    ….com/post-edit.g?blogID=9430835&postID=5736346114523015579&from=pencil' title=…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  624. Warning Line 1143, Column 67: reference to external entity in attribute value
    ….com/post-edit.g?blogID=9430835&postID=5736346114523015579&from=pencil' title=…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  625. Error Line 1143, Column 67: reference to entity "postID" for which no system identifier could be generated
    ….com/post-edit.g?blogID=9430835&postID=5736346114523015579&from=pencil' title=…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  626. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  627. Warning Line 1143, Column 92: reference not terminated by REFC delimiter
    …dit.g?blogID=9430835&postID=5736346114523015579&from=pencil' title='Edit Post'>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  628. Warning Line 1143, Column 92: reference to external entity in attribute value
    …dit.g?blogID=9430835&postID=5736346114523015579&from=pencil' title='Edit Post'>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  629. Error Line 1143, Column 92: reference to entity "from" for which no system identifier could be generated
    …dit.g?blogID=9430835&postID=5736346114523015579&from=pencil' title='Edit Post'>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  630. Info Line 542, Column 87: entity was defined here
    …dit.g?blogID=9430835&postID=6945236942316918823&from=pencil' title='Edit Post'>
  631. Warning Line 1156, Column 116: reference not terminated by REFC delimiter
    …com/share-post.g?blogID=9430835&postID=5736346114523015579&target=email' targe…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  632. Warning Line 1156, Column 116: reference to external entity in attribute value
    …com/share-post.g?blogID=9430835&postID=5736346114523015579&target=email' targe…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  633. Error Line 1156, Column 116: reference to entity "postID" for which no system identifier could be generated
    …com/share-post.g?blogID=9430835&postID=5736346114523015579&target=email' targe…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  634. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  635. Warning Line 1156, Column 143: reference not terminated by REFC delimiter
    …0835&postID=5736346114523015579&target=email' target='_blank' title='Email Thi…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  636. Warning Line 1156, Column 143: reference to external entity in attribute value
    …0835&postID=5736346114523015579&target=email' target='_blank' title='Email Thi…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  637. Error Line 1156, Column 143: reference to entity "target" for which no system identifier could be generated
    …0835&postID=5736346114523015579&target=email' target='_blank' title='Email Thi…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  638. Info Line 555, Column 136: entity was defined here
    …gID=9430835&postID=6945236942316918823&target=email' target='_blank' title='Em…
  639. Warning Line 1156, Column 358: reference not terminated by REFC delimiter
    …com/share-post.g?blogID=9430835&postID=5736346114523015579&target=blog' onclic…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  640. Warning Line 1156, Column 358: reference to external entity in attribute value
    …com/share-post.g?blogID=9430835&postID=5736346114523015579&target=blog' onclic…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  641. Error Line 1156, Column 358: reference to entity "postID" for which no system identifier could be generated
    …com/share-post.g?blogID=9430835&postID=5736346114523015579&target=blog' onclic…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  642. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  643. Warning Line 1156, Column 385: reference not terminated by REFC delimiter
    …0835&postID=5736346114523015579&target=blog' onclick='window.open(this.href, "…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  644. Warning Line 1156, Column 385: reference to external entity in attribute value
    …0835&postID=5736346114523015579&target=blog' onclick='window.open(this.href, "…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  645. Error Line 1156, Column 385: reference to entity "target" for which no system identifier could be generated
    …0835&postID=5736346114523015579&target=blog' onclick='window.open(this.href, "…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  646. Info Line 555, Column 136: entity was defined here
    …gID=9430835&postID=6945236942316918823&target=email' target='_blank' title='Em…
  647. Warning Line 1156, Column 682: reference not terminated by REFC delimiter
    …com/share-post.g?blogID=9430835&postID=5736346114523015579&target=twitter' tar…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  648. Warning Line 1156, Column 682: reference to external entity in attribute value
    …com/share-post.g?blogID=9430835&postID=5736346114523015579&target=twitter' tar…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  649. Error Line 1156, Column 682: reference to entity "postID" for which no system identifier could be generated
    …com/share-post.g?blogID=9430835&postID=5736346114523015579&target=twitter' tar…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  650. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  651. Warning Line 1156, Column 709: reference not terminated by REFC delimiter
    …0835&postID=5736346114523015579&target=twitter' target='_blank' title='Share t…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  652. Warning Line 1156, Column 709: reference to external entity in attribute value
    …0835&postID=5736346114523015579&target=twitter' target='_blank' title='Share t…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  653. Error Line 1156, Column 709: reference to entity "target" for which no system identifier could be generated
    …0835&postID=5736346114523015579&target=twitter' target='_blank' title='Share t…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  654. Info Line 555, Column 136: entity was defined here
    …gID=9430835&postID=6945236942316918823&target=email' target='_blank' title='Em…
  655. Warning Line 1156, Column 942: reference not terminated by REFC delimiter
    …com/share-post.g?blogID=9430835&postID=5736346114523015579&target=facebook' on…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  656. Warning Line 1156, Column 942: reference to external entity in attribute value
    …com/share-post.g?blogID=9430835&postID=5736346114523015579&target=facebook' on…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  657. Error Line 1156, Column 942: reference to entity "postID" for which no system identifier could be generated
    …com/share-post.g?blogID=9430835&postID=5736346114523015579&target=facebook' on…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  658. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  659. Warning Line 1156, Column 969: reference not terminated by REFC delimiter
    …0835&postID=5736346114523015579&target=facebook' onclick='window.open(this.hre…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  660. Warning Line 1156, Column 969: reference to external entity in attribute value
    …0835&postID=5736346114523015579&target=facebook' onclick='window.open(this.hre…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  661. Error Line 1156, Column 969: reference to entity "target" for which no system identifier could be generated
    …0835&postID=5736346114523015579&target=facebook' onclick='window.open(this.hre…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  662. Info Line 555, Column 136: entity was defined here
    …gID=9430835&postID=6945236942316918823&target=email' target='_blank' title='Em…
  663. Warning Line 1156, Column 1288: reference not terminated by REFC delimiter
    …com/share-post.g?blogID=9430835&postID=5736346114523015579&target=pinterest' t…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  664. Warning Line 1156, Column 1288: reference to external entity in attribute value
    …com/share-post.g?blogID=9430835&postID=5736346114523015579&target=pinterest' t…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  665. Error Line 1156, Column 1288: reference to entity "postID" for which no system identifier could be generated
    …com/share-post.g?blogID=9430835&postID=5736346114523015579&target=pinterest' t…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  666. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  667. Warning Line 1156, Column 1315: reference not terminated by REFC delimiter
    …0835&postID=5736346114523015579&target=pinterest' target='_blank' title='Share…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  668. Warning Line 1156, Column 1315: reference to external entity in attribute value
    …0835&postID=5736346114523015579&target=pinterest' target='_blank' title='Share…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  669. Error Line 1156, Column 1315: reference to entity "target" for which no system identifier could be generated
    …0835&postID=5736346114523015579&target=pinterest' target='_blank' title='Share…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  670. Info Line 555, Column 136: entity was defined here
    …gID=9430835&postID=6945236942316918823&target=email' target='_blank' title='Em…
  671. Error Line 1156, Column 1663: element "g:plusone" undefined
    …should-i-stop-being.html' size='medium' width='300' annotation='inline'/></div>

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  672. Warning Line 1189, Column 86: reference not terminated by REFC delimiter
    …w.blogger.com/comment.g?blogID=9430835&postID=8885448726366862238' onclick=''>0

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  673. Warning Line 1189, Column 86: reference to external entity in attribute value
    …w.blogger.com/comment.g?blogID=9430835&postID=8885448726366862238' onclick=''>0

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  674. Error Line 1189, Column 86: reference to entity "postID" for which no system identifier could be generated
    …w.blogger.com/comment.g?blogID=9430835&postID=8885448726366862238' onclick=''>0

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  675. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  676. Warning Line 1194, Column 68: reference not terminated by REFC delimiter
    …com/email-post.g?blogID=9430835&postID=8885448726366862238' title='Email Post'…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  677. Warning Line 1194, Column 68: reference to external entity in attribute value
    …com/email-post.g?blogID=9430835&postID=8885448726366862238' title='Email Post'…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  678. Error Line 1194, Column 68: reference to entity "postID" for which no system identifier could be generated
    …com/email-post.g?blogID=9430835&postID=8885448726366862238' title='Email Post'…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  679. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  680. Warning Line 1199, Column 67: reference not terminated by REFC delimiter
    ….com/post-edit.g?blogID=9430835&postID=8885448726366862238&from=pencil' title=…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  681. Warning Line 1199, Column 67: reference to external entity in attribute value
    ….com/post-edit.g?blogID=9430835&postID=8885448726366862238&from=pencil' title=…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  682. Error Line 1199, Column 67: reference to entity "postID" for which no system identifier could be generated
    ….com/post-edit.g?blogID=9430835&postID=8885448726366862238&from=pencil' title=…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  683. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  684. Warning Line 1199, Column 92: reference not terminated by REFC delimiter
    …dit.g?blogID=9430835&postID=8885448726366862238&from=pencil' title='Edit Post'>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  685. Warning Line 1199, Column 92: reference to external entity in attribute value
    …dit.g?blogID=9430835&postID=8885448726366862238&from=pencil' title='Edit Post'>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  686. Error Line 1199, Column 92: reference to entity "from" for which no system identifier could be generated
    …dit.g?blogID=9430835&postID=8885448726366862238&from=pencil' title='Edit Post'>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  687. Info Line 542, Column 87: entity was defined here
    …dit.g?blogID=9430835&postID=6945236942316918823&from=pencil' title='Edit Post'>
  688. Warning Line 1212, Column 116: reference not terminated by REFC delimiter
    …com/share-post.g?blogID=9430835&postID=8885448726366862238&target=email' targe…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  689. Warning Line 1212, Column 116: reference to external entity in attribute value
    …com/share-post.g?blogID=9430835&postID=8885448726366862238&target=email' targe…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  690. Error Line 1212, Column 116: reference to entity "postID" for which no system identifier could be generated
    …com/share-post.g?blogID=9430835&postID=8885448726366862238&target=email' targe…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  691. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  692. Warning Line 1212, Column 143: reference not terminated by REFC delimiter
    …0835&postID=8885448726366862238&target=email' target='_blank' title='Email Thi…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  693. Warning Line 1212, Column 143: reference to external entity in attribute value
    …0835&postID=8885448726366862238&target=email' target='_blank' title='Email Thi…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  694. Error Line 1212, Column 143: reference to entity "target" for which no system identifier could be generated
    …0835&postID=8885448726366862238&target=email' target='_blank' title='Email Thi…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  695. Info Line 555, Column 136: entity was defined here
    …gID=9430835&postID=6945236942316918823&target=email' target='_blank' title='Em…
  696. Warning Line 1212, Column 358: reference not terminated by REFC delimiter
    …com/share-post.g?blogID=9430835&postID=8885448726366862238&target=blog' onclic…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  697. Warning Line 1212, Column 358: reference to external entity in attribute value
    …com/share-post.g?blogID=9430835&postID=8885448726366862238&target=blog' onclic…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  698. Error Line 1212, Column 358: reference to entity "postID" for which no system identifier could be generated
    …com/share-post.g?blogID=9430835&postID=8885448726366862238&target=blog' onclic…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  699. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  700. Warning Line 1212, Column 385: reference not terminated by REFC delimiter
    …0835&postID=8885448726366862238&target=blog' onclick='window.open(this.href, "…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  701. Warning Line 1212, Column 385: reference to external entity in attribute value
    …0835&postID=8885448726366862238&target=blog' onclick='window.open(this.href, "…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  702. Error Line 1212, Column 385: reference to entity "target" for which no system identifier could be generated
    …0835&postID=8885448726366862238&target=blog' onclick='window.open(this.href, "…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  703. Info Line 555, Column 136: entity was defined here
    …gID=9430835&postID=6945236942316918823&target=email' target='_blank' title='Em…
  704. Warning Line 1212, Column 682: reference not terminated by REFC delimiter
    …com/share-post.g?blogID=9430835&postID=8885448726366862238&target=twitter' tar…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  705. Warning Line 1212, Column 682: reference to external entity in attribute value
    …com/share-post.g?blogID=9430835&postID=8885448726366862238&target=twitter' tar…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  706. Error Line 1212, Column 682: reference to entity "postID" for which no system identifier could be generated
    …com/share-post.g?blogID=9430835&postID=8885448726366862238&target=twitter' tar…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  707. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  708. Warning Line 1212, Column 709: reference not terminated by REFC delimiter
    …0835&postID=8885448726366862238&target=twitter' target='_blank' title='Share t…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  709. Warning Line 1212, Column 709: reference to external entity in attribute value
    …0835&postID=8885448726366862238&target=twitter' target='_blank' title='Share t…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  710. Error Line 1212, Column 709: reference to entity "target" for which no system identifier could be generated
    …0835&postID=8885448726366862238&target=twitter' target='_blank' title='Share t…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  711. Info Line 555, Column 136: entity was defined here
    …gID=9430835&postID=6945236942316918823&target=email' target='_blank' title='Em…
  712. Warning Line 1212, Column 942: reference not terminated by REFC delimiter
    …com/share-post.g?blogID=9430835&postID=8885448726366862238&target=facebook' on…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  713. Warning Line 1212, Column 942: reference to external entity in attribute value
    …com/share-post.g?blogID=9430835&postID=8885448726366862238&target=facebook' on…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  714. Error Line 1212, Column 942: reference to entity "postID" for which no system identifier could be generated
    …com/share-post.g?blogID=9430835&postID=8885448726366862238&target=facebook' on…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  715. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  716. Warning Line 1212, Column 969: reference not terminated by REFC delimiter
    …0835&postID=8885448726366862238&target=facebook' onclick='window.open(this.hre…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  717. Warning Line 1212, Column 969: reference to external entity in attribute value
    …0835&postID=8885448726366862238&target=facebook' onclick='window.open(this.hre…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  718. Error Line 1212, Column 969: reference to entity "target" for which no system identifier could be generated
    …0835&postID=8885448726366862238&target=facebook' onclick='window.open(this.hre…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  719. Info Line 555, Column 136: entity was defined here
    …gID=9430835&postID=6945236942316918823&target=email' target='_blank' title='Em…
  720. Warning Line 1212, Column 1288: reference not terminated by REFC delimiter
    …com/share-post.g?blogID=9430835&postID=8885448726366862238&target=pinterest' t…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  721. Warning Line 1212, Column 1288: reference to external entity in attribute value
    …com/share-post.g?blogID=9430835&postID=8885448726366862238&target=pinterest' t…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  722. Error Line 1212, Column 1288: reference to entity "postID" for which no system identifier could be generated
    …com/share-post.g?blogID=9430835&postID=8885448726366862238&target=pinterest' t…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  723. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  724. Warning Line 1212, Column 1315: reference not terminated by REFC delimiter
    …0835&postID=8885448726366862238&target=pinterest' target='_blank' title='Share…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  725. Warning Line 1212, Column 1315: reference to external entity in attribute value
    …0835&postID=8885448726366862238&target=pinterest' target='_blank' title='Share…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  726. Error Line 1212, Column 1315: reference to entity "target" for which no system identifier could be generated
    …0835&postID=8885448726366862238&target=pinterest' target='_blank' title='Share…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  727. Info Line 555, Column 136: entity was defined here
    …gID=9430835&postID=6945236942316918823&target=email' target='_blank' title='Em…
  728. Error Line 1212, Column 1668: element "g:plusone" undefined
    …ver-at-unzcomisteve.html' size='medium' width='300' annotation='inline'/></div>

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  729. Warning Line 1251, Column 86: reference not terminated by REFC delimiter
    …w.blogger.com/comment.g?blogID=9430835&postID=7079506991046321150' onclick=''>2

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  730. Warning Line 1251, Column 86: reference to external entity in attribute value
    …w.blogger.com/comment.g?blogID=9430835&postID=7079506991046321150' onclick=''>2

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  731. Error Line 1251, Column 86: reference to entity "postID" for which no system identifier could be generated
    …w.blogger.com/comment.g?blogID=9430835&postID=7079506991046321150' onclick=''>2

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  732. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  733. Warning Line 1256, Column 68: reference not terminated by REFC delimiter
    …com/email-post.g?blogID=9430835&postID=7079506991046321150' title='Email Post'…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  734. Warning Line 1256, Column 68: reference to external entity in attribute value
    …com/email-post.g?blogID=9430835&postID=7079506991046321150' title='Email Post'…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  735. Error Line 1256, Column 68: reference to entity "postID" for which no system identifier could be generated
    …com/email-post.g?blogID=9430835&postID=7079506991046321150' title='Email Post'…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  736. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  737. Warning Line 1261, Column 67: reference not terminated by REFC delimiter
    ….com/post-edit.g?blogID=9430835&postID=7079506991046321150&from=pencil' title=…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  738. Warning Line 1261, Column 67: reference to external entity in attribute value
    ….com/post-edit.g?blogID=9430835&postID=7079506991046321150&from=pencil' title=…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  739. Error Line 1261, Column 67: reference to entity "postID" for which no system identifier could be generated
    ….com/post-edit.g?blogID=9430835&postID=7079506991046321150&from=pencil' title=…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  740. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  741. Warning Line 1261, Column 92: reference not terminated by REFC delimiter
    …dit.g?blogID=9430835&postID=7079506991046321150&from=pencil' title='Edit Post'>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  742. Warning Line 1261, Column 92: reference to external entity in attribute value
    …dit.g?blogID=9430835&postID=7079506991046321150&from=pencil' title='Edit Post'>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  743. Error Line 1261, Column 92: reference to entity "from" for which no system identifier could be generated
    …dit.g?blogID=9430835&postID=7079506991046321150&from=pencil' title='Edit Post'>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  744. Info Line 542, Column 87: entity was defined here
    …dit.g?blogID=9430835&postID=6945236942316918823&from=pencil' title='Edit Post'>
  745. Warning Line 1274, Column 116: reference not terminated by REFC delimiter
    …com/share-post.g?blogID=9430835&postID=7079506991046321150&target=email' targe…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  746. Warning Line 1274, Column 116: reference to external entity in attribute value
    …com/share-post.g?blogID=9430835&postID=7079506991046321150&target=email' targe…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  747. Error Line 1274, Column 116: reference to entity "postID" for which no system identifier could be generated
    …com/share-post.g?blogID=9430835&postID=7079506991046321150&target=email' targe…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  748. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  749. Warning Line 1274, Column 143: reference not terminated by REFC delimiter
    …0835&postID=7079506991046321150&target=email' target='_blank' title='Email Thi…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  750. Warning Line 1274, Column 143: reference to external entity in attribute value
    …0835&postID=7079506991046321150&target=email' target='_blank' title='Email Thi…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  751. Error Line 1274, Column 143: reference to entity "target" for which no system identifier could be generated
    …0835&postID=7079506991046321150&target=email' target='_blank' title='Email Thi…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  752. Info Line 555, Column 136: entity was defined here
    …gID=9430835&postID=6945236942316918823&target=email' target='_blank' title='Em…
  753. Warning Line 1274, Column 358: reference not terminated by REFC delimiter
    …com/share-post.g?blogID=9430835&postID=7079506991046321150&target=blog' onclic…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  754. Warning Line 1274, Column 358: reference to external entity in attribute value
    …com/share-post.g?blogID=9430835&postID=7079506991046321150&target=blog' onclic…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  755. Error Line 1274, Column 358: reference to entity "postID" for which no system identifier could be generated
    …com/share-post.g?blogID=9430835&postID=7079506991046321150&target=blog' onclic…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  756. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  757. Warning Line 1274, Column 385: reference not terminated by REFC delimiter
    …0835&postID=7079506991046321150&target=blog' onclick='window.open(this.href, "…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  758. Warning Line 1274, Column 385: reference to external entity in attribute value
    …0835&postID=7079506991046321150&target=blog' onclick='window.open(this.href, "…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  759. Error Line 1274, Column 385: reference to entity "target" for which no system identifier could be generated
    …0835&postID=7079506991046321150&target=blog' onclick='window.open(this.href, "…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  760. Info Line 555, Column 136: entity was defined here
    …gID=9430835&postID=6945236942316918823&target=email' target='_blank' title='Em…
  761. Warning Line 1274, Column 682: reference not terminated by REFC delimiter
    …com/share-post.g?blogID=9430835&postID=7079506991046321150&target=twitter' tar…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  762. Warning Line 1274, Column 682: reference to external entity in attribute value
    …com/share-post.g?blogID=9430835&postID=7079506991046321150&target=twitter' tar…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  763. Error Line 1274, Column 682: reference to entity "postID" for which no system identifier could be generated
    …com/share-post.g?blogID=9430835&postID=7079506991046321150&target=twitter' tar…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  764. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  765. Warning Line 1274, Column 709: reference not terminated by REFC delimiter
    …0835&postID=7079506991046321150&target=twitter' target='_blank' title='Share t…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  766. Warning Line 1274, Column 709: reference to external entity in attribute value
    …0835&postID=7079506991046321150&target=twitter' target='_blank' title='Share t…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  767. Error Line 1274, Column 709: reference to entity "target" for which no system identifier could be generated
    …0835&postID=7079506991046321150&target=twitter' target='_blank' title='Share t…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  768. Info Line 555, Column 136: entity was defined here
    …gID=9430835&postID=6945236942316918823&target=email' target='_blank' title='Em…
  769. Warning Line 1274, Column 942: reference not terminated by REFC delimiter
    …com/share-post.g?blogID=9430835&postID=7079506991046321150&target=facebook' on…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  770. Warning Line 1274, Column 942: reference to external entity in attribute value
    …com/share-post.g?blogID=9430835&postID=7079506991046321150&target=facebook' on…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  771. Error Line 1274, Column 942: reference to entity "postID" for which no system identifier could be generated
    …com/share-post.g?blogID=9430835&postID=7079506991046321150&target=facebook' on…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  772. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  773. Warning Line 1274, Column 969: reference not terminated by REFC delimiter
    …0835&postID=7079506991046321150&target=facebook' onclick='window.open(this.hre…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  774. Warning Line 1274, Column 969: reference to external entity in attribute value
    …0835&postID=7079506991046321150&target=facebook' onclick='window.open(this.hre…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  775. Error Line 1274, Column 969: reference to entity "target" for which no system identifier could be generated
    …0835&postID=7079506991046321150&target=facebook' onclick='window.open(this.hre…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  776. Info Line 555, Column 136: entity was defined here
    …gID=9430835&postID=6945236942316918823&target=email' target='_blank' title='Em…
  777. Warning Line 1274, Column 1288: reference not terminated by REFC delimiter
    …com/share-post.g?blogID=9430835&postID=7079506991046321150&target=pinterest' t…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  778. Warning Line 1274, Column 1288: reference to external entity in attribute value
    …com/share-post.g?blogID=9430835&postID=7079506991046321150&target=pinterest' t…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  779. Error Line 1274, Column 1288: reference to entity "postID" for which no system identifier could be generated
    …com/share-post.g?blogID=9430835&postID=7079506991046321150&target=pinterest' t…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  780. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  781. Warning Line 1274, Column 1315: reference not terminated by REFC delimiter
    …0835&postID=7079506991046321150&target=pinterest' target='_blank' title='Share…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  782. Warning Line 1274, Column 1315: reference to external entity in attribute value
    …0835&postID=7079506991046321150&target=pinterest' target='_blank' title='Share…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  783. Error Line 1274, Column 1315: reference to entity "target" for which no system identifier could be generated
    …0835&postID=7079506991046321150&target=pinterest' target='_blank' title='Share…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  784. Info Line 555, Column 136: entity was defined here
    …gID=9430835&postID=6945236942316918823&target=email' target='_blank' title='Em…
  785. Error Line 1274, Column 1650: element "g:plusone" undefined
    …irst-world-problems.html' size='medium' width='300' annotation='inline'/></div>

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  786. Warning Line 1303, Column 86: reference not terminated by REFC delimiter
    …w.blogger.com/comment.g?blogID=9430835&postID=7870858138012780177' onclick=''>3

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  787. Warning Line 1303, Column 86: reference to external entity in attribute value
    …w.blogger.com/comment.g?blogID=9430835&postID=7870858138012780177' onclick=''>3

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  788. Error Line 1303, Column 86: reference to entity "postID" for which no system identifier could be generated
    …w.blogger.com/comment.g?blogID=9430835&postID=7870858138012780177' onclick=''>3

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  789. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  790. Warning Line 1308, Column 68: reference not terminated by REFC delimiter
    …com/email-post.g?blogID=9430835&postID=7870858138012780177' title='Email Post'…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  791. Warning Line 1308, Column 68: reference to external entity in attribute value
    …com/email-post.g?blogID=9430835&postID=7870858138012780177' title='Email Post'…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  792. Error Line 1308, Column 68: reference to entity "postID" for which no system identifier could be generated
    …com/email-post.g?blogID=9430835&postID=7870858138012780177' title='Email Post'…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  793. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  794. Warning Line 1313, Column 67: reference not terminated by REFC delimiter
    ….com/post-edit.g?blogID=9430835&postID=7870858138012780177&from=pencil' title=…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  795. Warning Line 1313, Column 67: reference to external entity in attribute value
    ….com/post-edit.g?blogID=9430835&postID=7870858138012780177&from=pencil' title=…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  796. Error Line 1313, Column 67: reference to entity "postID" for which no system identifier could be generated
    ….com/post-edit.g?blogID=9430835&postID=7870858138012780177&from=pencil' title=…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  797. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  798. Warning Line 1313, Column 92: reference not terminated by REFC delimiter
    …dit.g?blogID=9430835&postID=7870858138012780177&from=pencil' title='Edit Post'>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  799. Warning Line 1313, Column 92: reference to external entity in attribute value
    …dit.g?blogID=9430835&postID=7870858138012780177&from=pencil' title='Edit Post'>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  800. Error Line 1313, Column 92: reference to entity "from" for which no system identifier could be generated
    …dit.g?blogID=9430835&postID=7870858138012780177&from=pencil' title='Edit Post'>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  801. Info Line 542, Column 87: entity was defined here
    …dit.g?blogID=9430835&postID=6945236942316918823&from=pencil' title='Edit Post'>
  802. Warning Line 1326, Column 116: reference not terminated by REFC delimiter
    …com/share-post.g?blogID=9430835&postID=7870858138012780177&target=email' targe…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  803. Warning Line 1326, Column 116: reference to external entity in attribute value
    …com/share-post.g?blogID=9430835&postID=7870858138012780177&target=email' targe…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  804. Error Line 1326, Column 116: reference to entity "postID" for which no system identifier could be generated
    …com/share-post.g?blogID=9430835&postID=7870858138012780177&target=email' targe…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  805. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  806. Warning Line 1326, Column 143: reference not terminated by REFC delimiter
    …0835&postID=7870858138012780177&target=email' target='_blank' title='Email Thi…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  807. Warning Line 1326, Column 143: reference to external entity in attribute value
    …0835&postID=7870858138012780177&target=email' target='_blank' title='Email Thi…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  808. Error Line 1326, Column 143: reference to entity "target" for which no system identifier could be generated
    …0835&postID=7870858138012780177&target=email' target='_blank' title='Email Thi…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  809. Info Line 555, Column 136: entity was defined here
    …gID=9430835&postID=6945236942316918823&target=email' target='_blank' title='Em…
  810. Warning Line 1326, Column 358: reference not terminated by REFC delimiter
    …com/share-post.g?blogID=9430835&postID=7870858138012780177&target=blog' onclic…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  811. Warning Line 1326, Column 358: reference to external entity in attribute value
    …com/share-post.g?blogID=9430835&postID=7870858138012780177&target=blog' onclic…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  812. Error Line 1326, Column 358: reference to entity "postID" for which no system identifier could be generated
    …com/share-post.g?blogID=9430835&postID=7870858138012780177&target=blog' onclic…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  813. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  814. Warning Line 1326, Column 385: reference not terminated by REFC delimiter
    …0835&postID=7870858138012780177&target=blog' onclick='window.open(this.href, "…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  815. Warning Line 1326, Column 385: reference to external entity in attribute value
    …0835&postID=7870858138012780177&target=blog' onclick='window.open(this.href, "…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  816. Error Line 1326, Column 385: reference to entity "target" for which no system identifier could be generated
    …0835&postID=7870858138012780177&target=blog' onclick='window.open(this.href, "…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  817. Info Line 555, Column 136: entity was defined here
    …gID=9430835&postID=6945236942316918823&target=email' target='_blank' title='Em…
  818. Warning Line 1326, Column 682: reference not terminated by REFC delimiter
    …com/share-post.g?blogID=9430835&postID=7870858138012780177&target=twitter' tar…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  819. Warning Line 1326, Column 682: reference to external entity in attribute value
    …com/share-post.g?blogID=9430835&postID=7870858138012780177&target=twitter' tar…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  820. Error Line 1326, Column 682: reference to entity "postID" for which no system identifier could be generated
    …com/share-post.g?blogID=9430835&postID=7870858138012780177&target=twitter' tar…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  821. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  822. Warning Line 1326, Column 709: reference not terminated by REFC delimiter
    …0835&postID=7870858138012780177&target=twitter' target='_blank' title='Share t…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  823. Warning Line 1326, Column 709: reference to external entity in attribute value
    …0835&postID=7870858138012780177&target=twitter' target='_blank' title='Share t…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  824. Error Line 1326, Column 709: reference to entity "target" for which no system identifier could be generated
    …0835&postID=7870858138012780177&target=twitter' target='_blank' title='Share t…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  825. Info Line 555, Column 136: entity was defined here
    …gID=9430835&postID=6945236942316918823&target=email' target='_blank' title='Em…
  826. Warning Line 1326, Column 942: reference not terminated by REFC delimiter
    …com/share-post.g?blogID=9430835&postID=7870858138012780177&target=facebook' on…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  827. Warning Line 1326, Column 942: reference to external entity in attribute value
    …com/share-post.g?blogID=9430835&postID=7870858138012780177&target=facebook' on…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  828. Error Line 1326, Column 942: reference to entity "postID" for which no system identifier could be generated
    …com/share-post.g?blogID=9430835&postID=7870858138012780177&target=facebook' on…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  829. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  830. Warning Line 1326, Column 969: reference not terminated by REFC delimiter
    …0835&postID=7870858138012780177&target=facebook' onclick='window.open(this.hre…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  831. Warning Line 1326, Column 969: reference to external entity in attribute value
    …0835&postID=7870858138012780177&target=facebook' onclick='window.open(this.hre…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  832. Error Line 1326, Column 969: reference to entity "target" for which no system identifier could be generated
    …0835&postID=7870858138012780177&target=facebook' onclick='window.open(this.hre…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  833. Info Line 555, Column 136: entity was defined here
    …gID=9430835&postID=6945236942316918823&target=email' target='_blank' title='Em…
  834. Warning Line 1326, Column 1288: reference not terminated by REFC delimiter
    …com/share-post.g?blogID=9430835&postID=7870858138012780177&target=pinterest' t…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  835. Warning Line 1326, Column 1288: reference to external entity in attribute value
    …com/share-post.g?blogID=9430835&postID=7870858138012780177&target=pinterest' t…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  836. Error Line 1326, Column 1288: reference to entity "postID" for which no system identifier could be generated
    …com/share-post.g?blogID=9430835&postID=7870858138012780177&target=pinterest' t…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  837. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  838. Warning Line 1326, Column 1315: reference not terminated by REFC delimiter
    …0835&postID=7870858138012780177&target=pinterest' target='_blank' title='Share…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  839. Warning Line 1326, Column 1315: reference to external entity in attribute value
    …0835&postID=7870858138012780177&target=pinterest' target='_blank' title='Share…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  840. Error Line 1326, Column 1315: reference to entity "target" for which no system identifier could be generated
    …0835&postID=7870858138012780177&target=pinterest' target='_blank' title='Share…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  841. Info Line 555, Column 136: entity was defined here
    …gID=9430835&postID=6945236942316918823&target=email' target='_blank' title='Em…
  842. Error Line 1326, Column 1659: element "g:plusone" undefined
    …able-housing-racket.html' size='medium' width='300' annotation='inline'/></div>

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  843. Warning Line 1356, Column 86: reference not terminated by REFC delimiter
    …w.blogger.com/comment.g?blogID=9430835&postID=7239246200245539264' onclick=''>2

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  844. Warning Line 1356, Column 86: reference to external entity in attribute value
    …w.blogger.com/comment.g?blogID=9430835&postID=7239246200245539264' onclick=''>2

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  845. Error Line 1356, Column 86: reference to entity "postID" for which no system identifier could be generated
    …w.blogger.com/comment.g?blogID=9430835&postID=7239246200245539264' onclick=''>2

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  846. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  847. Warning Line 1361, Column 68: reference not terminated by REFC delimiter
    …com/email-post.g?blogID=9430835&postID=7239246200245539264' title='Email Post'…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  848. Warning Line 1361, Column 68: reference to external entity in attribute value
    …com/email-post.g?blogID=9430835&postID=7239246200245539264' title='Email Post'…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  849. Error Line 1361, Column 68: reference to entity "postID" for which no system identifier could be generated
    …com/email-post.g?blogID=9430835&postID=7239246200245539264' title='Email Post'…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  850. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  851. Warning Line 1366, Column 67: reference not terminated by REFC delimiter
    ….com/post-edit.g?blogID=9430835&postID=7239246200245539264&from=pencil' title=…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  852. Warning Line 1366, Column 67: reference to external entity in attribute value
    ….com/post-edit.g?blogID=9430835&postID=7239246200245539264&from=pencil' title=…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  853. Error Line 1366, Column 67: reference to entity "postID" for which no system identifier could be generated
    ….com/post-edit.g?blogID=9430835&postID=7239246200245539264&from=pencil' title=…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  854. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  855. Warning Line 1366, Column 92: reference not terminated by REFC delimiter
    …dit.g?blogID=9430835&postID=7239246200245539264&from=pencil' title='Edit Post'>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  856. Warning Line 1366, Column 92: reference to external entity in attribute value
    …dit.g?blogID=9430835&postID=7239246200245539264&from=pencil' title='Edit Post'>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  857. Error Line 1366, Column 92: reference to entity "from" for which no system identifier could be generated
    …dit.g?blogID=9430835&postID=7239246200245539264&from=pencil' title='Edit Post'>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  858. Info Line 542, Column 87: entity was defined here
    …dit.g?blogID=9430835&postID=6945236942316918823&from=pencil' title='Edit Post'>
  859. Warning Line 1379, Column 116: reference not terminated by REFC delimiter
    …com/share-post.g?blogID=9430835&postID=7239246200245539264&target=email' targe…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  860. Warning Line 1379, Column 116: reference to external entity in attribute value
    …com/share-post.g?blogID=9430835&postID=7239246200245539264&target=email' targe…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  861. Error Line 1379, Column 116: reference to entity "postID" for which no system identifier could be generated
    …com/share-post.g?blogID=9430835&postID=7239246200245539264&target=email' targe…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  862. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  863. Warning Line 1379, Column 143: reference not terminated by REFC delimiter
    …0835&postID=7239246200245539264&target=email' target='_blank' title='Email Thi…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  864. Warning Line 1379, Column 143: reference to external entity in attribute value
    …0835&postID=7239246200245539264&target=email' target='_blank' title='Email Thi…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  865. Error Line 1379, Column 143: reference to entity "target" for which no system identifier could be generated
    …0835&postID=7239246200245539264&target=email' target='_blank' title='Email Thi…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  866. Info Line 555, Column 136: entity was defined here
    …gID=9430835&postID=6945236942316918823&target=email' target='_blank' title='Em…
  867. Warning Line 1379, Column 358: reference not terminated by REFC delimiter
    …com/share-post.g?blogID=9430835&postID=7239246200245539264&target=blog' onclic…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  868. Warning Line 1379, Column 358: reference to external entity in attribute value
    …com/share-post.g?blogID=9430835&postID=7239246200245539264&target=blog' onclic…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  869. Error Line 1379, Column 358: reference to entity "postID" for which no system identifier could be generated
    …com/share-post.g?blogID=9430835&postID=7239246200245539264&target=blog' onclic…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  870. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  871. Warning Line 1379, Column 385: reference not terminated by REFC delimiter
    …0835&postID=7239246200245539264&target=blog' onclick='window.open(this.href, "…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  872. Warning Line 1379, Column 385: reference to external entity in attribute value
    …0835&postID=7239246200245539264&target=blog' onclick='window.open(this.href, "…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  873. Error Line 1379, Column 385: reference to entity "target" for which no system identifier could be generated
    …0835&postID=7239246200245539264&target=blog' onclick='window.open(this.href, "…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  874. Info Line 555, Column 136: entity was defined here
    …gID=9430835&postID=6945236942316918823&target=email' target='_blank' title='Em…
  875. Warning Line 1379, Column 682: reference not terminated by REFC delimiter
    …com/share-post.g?blogID=9430835&postID=7239246200245539264&target=twitter' tar…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  876. Warning Line 1379, Column 682: reference to external entity in attribute value
    …com/share-post.g?blogID=9430835&postID=7239246200245539264&target=twitter' tar…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  877. Error Line 1379, Column 682: reference to entity "postID" for which no system identifier could be generated
    …com/share-post.g?blogID=9430835&postID=7239246200245539264&target=twitter' tar…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  878. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  879. Warning Line 1379, Column 709: reference not terminated by REFC delimiter
    …0835&postID=7239246200245539264&target=twitter' target='_blank' title='Share t…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  880. Warning Line 1379, Column 709: reference to external entity in attribute value
    …0835&postID=7239246200245539264&target=twitter' target='_blank' title='Share t…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  881. Error Line 1379, Column 709: reference to entity "target" for which no system identifier could be generated
    …0835&postID=7239246200245539264&target=twitter' target='_blank' title='Share t…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  882. Info Line 555, Column 136: entity was defined here
    …gID=9430835&postID=6945236942316918823&target=email' target='_blank' title='Em…
  883. Warning Line 1379, Column 942: reference not terminated by REFC delimiter
    …com/share-post.g?blogID=9430835&postID=7239246200245539264&target=facebook' on…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  884. Warning Line 1379, Column 942: reference to external entity in attribute value
    …com/share-post.g?blogID=9430835&postID=7239246200245539264&target=facebook' on…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  885. Error Line 1379, Column 942: reference to entity "postID" for which no system identifier could be generated
    …com/share-post.g?blogID=9430835&postID=7239246200245539264&target=facebook' on…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  886. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  887. Warning Line 1379, Column 969: reference not terminated by REFC delimiter
    …0835&postID=7239246200245539264&target=facebook' onclick='window.open(this.hre…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  888. Warning Line 1379, Column 969: reference to external entity in attribute value
    …0835&postID=7239246200245539264&target=facebook' onclick='window.open(this.hre…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  889. Error Line 1379, Column 969: reference to entity "target" for which no system identifier could be generated
    …0835&postID=7239246200245539264&target=facebook' onclick='window.open(this.hre…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  890. Info Line 555, Column 136: entity was defined here
    …gID=9430835&postID=6945236942316918823&target=email' target='_blank' title='Em…
  891. Warning Line 1379, Column 1288: reference not terminated by REFC delimiter
    …com/share-post.g?blogID=9430835&postID=7239246200245539264&target=pinterest' t…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  892. Warning Line 1379, Column 1288: reference to external entity in attribute value
    …com/share-post.g?blogID=9430835&postID=7239246200245539264&target=pinterest' t…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  893. Error Line 1379, Column 1288: reference to entity "postID" for which no system identifier could be generated
    …com/share-post.g?blogID=9430835&postID=7239246200245539264&target=pinterest' t…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  894. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  895. Warning Line 1379, Column 1315: reference not terminated by REFC delimiter
    …0835&postID=7239246200245539264&target=pinterest' target='_blank' title='Share…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  896. Warning Line 1379, Column 1315: reference to external entity in attribute value
    …0835&postID=7239246200245539264&target=pinterest' target='_blank' title='Share…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  897. Error Line 1379, Column 1315: reference to entity "target" for which no system identifier could be generated
    …0835&postID=7239246200245539264&target=pinterest' target='_blank' title='Share…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  898. Info Line 555, Column 136: entity was defined here
    …gID=9430835&postID=6945236942316918823&target=email' target='_blank' title='Em…
  899. Error Line 1379, Column 1638: element "g:plusone" undefined
    …om/2014/06/bergdahl.html' size='medium' width='300' annotation='inline'/></div>

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  900. Error Line 1393, Column 232: there is no attribute "data-thumbnail-src"
    …#version=6,0,40,0" data-thumbnail-src="https://ytimg.googleusercontent.com/vi/…

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  901. Warning Line 1393, Column 363: cannot generate system identifier for general entity "source"
    …/youtube.googleapis.com/v/TbWWW32qFvo&source=uds" /><param name="bgcolor" valu…

    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 "&amp;" (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 &aelig; 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.

  902. Error Line 1393, Column 363: general entity "source" not defined and no default entity
    …/youtube.googleapis.com/v/TbWWW32qFvo&source=uds" /><param name="bgcolor" valu…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  903. Warning Line 1393, Column 369: reference not terminated by REFC delimiter
    …be.googleapis.com/v/TbWWW32qFvo&source=uds" /><param name="bgcolor" value="#FF…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  904. Warning Line 1393, Column 369: reference to external entity in attribute value
    …be.googleapis.com/v/TbWWW32qFvo&source=uds" /><param name="bgcolor" value="#FF…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  905. Error Line 1393, Column 369: reference to entity "source" for which no system identifier could be generated
    …be.googleapis.com/v/TbWWW32qFvo&source=uds" /><param name="bgcolor" value="#FF…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  906. Info Line 1393, Column 362: entity was defined here
    …//youtube.googleapis.com/v/TbWWW32qFvo&source=uds" /><param name="bgcolor" val…
  907. Error Line 1393, Column 475: there is no attribute "width"
    …llScreen" value="true" /><embed width="320" height="266"  src="https://youtube…

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  908. Error Line 1393, Column 488: there is no attribute "height"
    …ue="true" /><embed width="320" height="266"  src="https://youtube.googleapis.c…

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  909. Error Line 1393, Column 499: there is no attribute "src"
    …><embed width="320" height="266"  src="https://youtube.googleapis.com/v/TbWWW3…

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  910. Warning Line 1393, Column 551: reference not terminated by REFC delimiter
    …be.googleapis.com/v/TbWWW32qFvo&source=uds" type="application/x-shockwave-flas…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  911. Warning Line 1393, Column 551: reference to external entity in attribute value
    …be.googleapis.com/v/TbWWW32qFvo&source=uds" type="application/x-shockwave-flas…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  912. Error Line 1393, Column 551: reference to entity "source" for which no system identifier could be generated
    …be.googleapis.com/v/TbWWW32qFvo&source=uds" type="application/x-shockwave-flas…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  913. Info Line 1393, Column 362: entity was defined here
    …//youtube.googleapis.com/v/TbWWW32qFvo&source=uds" /><param name="bgcolor" val…
  914. Error Line 1393, Column 562: there is no attribute "type"
    …is.com/v/TbWWW32qFvo&source=uds" type="application/x-shockwave-flash" allowful…

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  915. Error Line 1393, Column 610: there is no attribute "allowfullscreen"
    …="application/x-shockwave-flash" allowfullscreen="true"></embed></object></div>

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  916. Error Line 1393, Column 616: element "embed" undefined
    …="application/x-shockwave-flash" allowfullscreen="true"></embed></object></div>

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  917. Warning Line 1414, Column 86: reference not terminated by REFC delimiter
    ….blogger.com/comment.g?blogID=9430835&postID=4459149777442922155' onclick=''>11

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  918. Warning Line 1414, Column 86: reference to external entity in attribute value
    ….blogger.com/comment.g?blogID=9430835&postID=4459149777442922155' onclick=''>11

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  919. Error Line 1414, Column 86: reference to entity "postID" for which no system identifier could be generated
    ….blogger.com/comment.g?blogID=9430835&postID=4459149777442922155' onclick=''>11

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  920. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  921. Warning Line 1419, Column 68: reference not terminated by REFC delimiter
    …com/email-post.g?blogID=9430835&postID=4459149777442922155' title='Email Post'…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  922. Warning Line 1419, Column 68: reference to external entity in attribute value
    …com/email-post.g?blogID=9430835&postID=4459149777442922155' title='Email Post'…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  923. Error Line 1419, Column 68: reference to entity "postID" for which no system identifier could be generated
    …com/email-post.g?blogID=9430835&postID=4459149777442922155' title='Email Post'…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  924. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  925. Warning Line 1424, Column 67: reference not terminated by REFC delimiter
    ….com/post-edit.g?blogID=9430835&postID=4459149777442922155&from=pencil' title=…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  926. Warning Line 1424, Column 67: reference to external entity in attribute value
    ….com/post-edit.g?blogID=9430835&postID=4459149777442922155&from=pencil' title=…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  927. Error Line 1424, Column 67: reference to entity "postID" for which no system identifier could be generated
    ….com/post-edit.g?blogID=9430835&postID=4459149777442922155&from=pencil' title=…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  928. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  929. Warning Line 1424, Column 92: reference not terminated by REFC delimiter
    …dit.g?blogID=9430835&postID=4459149777442922155&from=pencil' title='Edit Post'>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  930. Warning Line 1424, Column 92: reference to external entity in attribute value
    …dit.g?blogID=9430835&postID=4459149777442922155&from=pencil' title='Edit Post'>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  931. Error Line 1424, Column 92: reference to entity "from" for which no system identifier could be generated
    …dit.g?blogID=9430835&postID=4459149777442922155&from=pencil' title='Edit Post'>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  932. Info Line 542, Column 87: entity was defined here
    …dit.g?blogID=9430835&postID=6945236942316918823&from=pencil' title='Edit Post'>
  933. Warning Line 1437, Column 116: reference not terminated by REFC delimiter
    …com/share-post.g?blogID=9430835&postID=4459149777442922155&target=email' targe…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  934. Warning Line 1437, Column 116: reference to external entity in attribute value
    …com/share-post.g?blogID=9430835&postID=4459149777442922155&target=email' targe…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  935. Error Line 1437, Column 116: reference to entity "postID" for which no system identifier could be generated
    …com/share-post.g?blogID=9430835&postID=4459149777442922155&target=email' targe…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  936. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  937. Warning Line 1437, Column 143: reference not terminated by REFC delimiter
    …0835&postID=4459149777442922155&target=email' target='_blank' title='Email Thi…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  938. Warning Line 1437, Column 143: reference to external entity in attribute value
    …0835&postID=4459149777442922155&target=email' target='_blank' title='Email Thi…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  939. Error Line 1437, Column 143: reference to entity "target" for which no system identifier could be generated
    …0835&postID=4459149777442922155&target=email' target='_blank' title='Email Thi…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  940. Info Line 555, Column 136: entity was defined here
    …gID=9430835&postID=6945236942316918823&target=email' target='_blank' title='Em…
  941. Warning Line 1437, Column 358: reference not terminated by REFC delimiter
    …com/share-post.g?blogID=9430835&postID=4459149777442922155&target=blog' onclic…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  942. Warning Line 1437, Column 358: reference to external entity in attribute value
    …com/share-post.g?blogID=9430835&postID=4459149777442922155&target=blog' onclic…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  943. Error Line 1437, Column 358: reference to entity "postID" for which no system identifier could be generated
    …com/share-post.g?blogID=9430835&postID=4459149777442922155&target=blog' onclic…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  944. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  945. Warning Line 1437, Column 385: reference not terminated by REFC delimiter
    …0835&postID=4459149777442922155&target=blog' onclick='window.open(this.href, "…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  946. Warning Line 1437, Column 385: reference to external entity in attribute value
    …0835&postID=4459149777442922155&target=blog' onclick='window.open(this.href, "…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  947. Error Line 1437, Column 385: reference to entity "target" for which no system identifier could be generated
    …0835&postID=4459149777442922155&target=blog' onclick='window.open(this.href, "…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  948. Info Line 555, Column 136: entity was defined here
    …gID=9430835&postID=6945236942316918823&target=email' target='_blank' title='Em…
  949. Warning Line 1437, Column 682: reference not terminated by REFC delimiter
    …com/share-post.g?blogID=9430835&postID=4459149777442922155&target=twitter' tar…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  950. Warning Line 1437, Column 682: reference to external entity in attribute value
    …com/share-post.g?blogID=9430835&postID=4459149777442922155&target=twitter' tar…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  951. Error Line 1437, Column 682: reference to entity "postID" for which no system identifier could be generated
    …com/share-post.g?blogID=9430835&postID=4459149777442922155&target=twitter' tar…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  952. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  953. Warning Line 1437, Column 709: reference not terminated by REFC delimiter
    …0835&postID=4459149777442922155&target=twitter' target='_blank' title='Share t…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  954. Warning Line 1437, Column 709: reference to external entity in attribute value
    …0835&postID=4459149777442922155&target=twitter' target='_blank' title='Share t…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  955. Error Line 1437, Column 709: reference to entity "target" for which no system identifier could be generated
    …0835&postID=4459149777442922155&target=twitter' target='_blank' title='Share t…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  956. Info Line 555, Column 136: entity was defined here
    …gID=9430835&postID=6945236942316918823&target=email' target='_blank' title='Em…
  957. Warning Line 1437, Column 942: reference not terminated by REFC delimiter
    …com/share-post.g?blogID=9430835&postID=4459149777442922155&target=facebook' on…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  958. Warning Line 1437, Column 942: reference to external entity in attribute value
    …com/share-post.g?blogID=9430835&postID=4459149777442922155&target=facebook' on…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  959. Error Line 1437, Column 942: reference to entity "postID" for which no system identifier could be generated
    …com/share-post.g?blogID=9430835&postID=4459149777442922155&target=facebook' on…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  960. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  961. Warning Line 1437, Column 969: reference not terminated by REFC delimiter
    …0835&postID=4459149777442922155&target=facebook' onclick='window.open(this.hre…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  962. Warning Line 1437, Column 969: reference to external entity in attribute value
    …0835&postID=4459149777442922155&target=facebook' onclick='window.open(this.hre…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  963. Error Line 1437, Column 969: reference to entity "target" for which no system identifier could be generated
    …0835&postID=4459149777442922155&target=facebook' onclick='window.open(this.hre…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  964. Info Line 555, Column 136: entity was defined here
    …gID=9430835&postID=6945236942316918823&target=email' target='_blank' title='Em…
  965. Warning Line 1437, Column 1288: reference not terminated by REFC delimiter
    …com/share-post.g?blogID=9430835&postID=4459149777442922155&target=pinterest' t…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  966. Warning Line 1437, Column 1288: reference to external entity in attribute value
    …com/share-post.g?blogID=9430835&postID=4459149777442922155&target=pinterest' t…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  967. Error Line 1437, Column 1288: reference to entity "postID" for which no system identifier could be generated
    …com/share-post.g?blogID=9430835&postID=4459149777442922155&target=pinterest' t…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  968. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  969. Warning Line 1437, Column 1315: reference not terminated by REFC delimiter
    …0835&postID=4459149777442922155&target=pinterest' target='_blank' title='Share…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  970. Warning Line 1437, Column 1315: reference to external entity in attribute value
    …0835&postID=4459149777442922155&target=pinterest' target='_blank' title='Share…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  971. Error Line 1437, Column 1315: reference to entity "target" for which no system identifier could be generated
    …0835&postID=4459149777442922155&target=pinterest' target='_blank' title='Share…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  972. Info Line 555, Column 136: entity was defined here
    …gID=9430835&postID=6945236942316918823&target=email' target='_blank' title='Em…
  973. Error Line 1437, Column 1665: element "g:plusone" undefined
    …s-shows-celebs-race.html' size='medium' width='300' annotation='inline'/></div>

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  974. Warning Line 1468, Column 86: reference not terminated by REFC delimiter
    …w.blogger.com/comment.g?blogID=9430835&postID=8667000908994685280' onclick=''>2

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  975. Warning Line 1468, Column 86: reference to external entity in attribute value
    …w.blogger.com/comment.g?blogID=9430835&postID=8667000908994685280' onclick=''>2

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  976. Error Line 1468, Column 86: reference to entity "postID" for which no system identifier could be generated
    …w.blogger.com/comment.g?blogID=9430835&postID=8667000908994685280' onclick=''>2

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  977. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  978. Warning Line 1473, Column 68: reference not terminated by REFC delimiter
    …com/email-post.g?blogID=9430835&postID=8667000908994685280' title='Email Post'…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  979. Warning Line 1473, Column 68: reference to external entity in attribute value
    …com/email-post.g?blogID=9430835&postID=8667000908994685280' title='Email Post'…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  980. Error Line 1473, Column 68: reference to entity "postID" for which no system identifier could be generated
    …com/email-post.g?blogID=9430835&postID=8667000908994685280' title='Email Post'…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  981. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  982. Warning Line 1478, Column 67: reference not terminated by REFC delimiter
    ….com/post-edit.g?blogID=9430835&postID=8667000908994685280&from=pencil' title=…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  983. Warning Line 1478, Column 67: reference to external entity in attribute value
    ….com/post-edit.g?blogID=9430835&postID=8667000908994685280&from=pencil' title=…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  984. Error Line 1478, Column 67: reference to entity "postID" for which no system identifier could be generated
    ….com/post-edit.g?blogID=9430835&postID=8667000908994685280&from=pencil' title=…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  985. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  986. Warning Line 1478, Column 92: reference not terminated by REFC delimiter
    …dit.g?blogID=9430835&postID=8667000908994685280&from=pencil' title='Edit Post'>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  987. Warning Line 1478, Column 92: reference to external entity in attribute value
    …dit.g?blogID=9430835&postID=8667000908994685280&from=pencil' title='Edit Post'>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  988. Error Line 1478, Column 92: reference to entity "from" for which no system identifier could be generated
    …dit.g?blogID=9430835&postID=8667000908994685280&from=pencil' title='Edit Post'>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  989. Info Line 542, Column 87: entity was defined here
    …dit.g?blogID=9430835&postID=6945236942316918823&from=pencil' title='Edit Post'>
  990. Warning Line 1491, Column 116: reference not terminated by REFC delimiter
    …com/share-post.g?blogID=9430835&postID=8667000908994685280&target=email' targe…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  991. Warning Line 1491, Column 116: reference to external entity in attribute value
    …com/share-post.g?blogID=9430835&postID=8667000908994685280&target=email' targe…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  992. Error Line 1491, Column 116: reference to entity "postID" for which no system identifier could be generated
    …com/share-post.g?blogID=9430835&postID=8667000908994685280&target=email' targe…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  993. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  994. Warning Line 1491, Column 143: reference not terminated by REFC delimiter
    …0835&postID=8667000908994685280&target=email' target='_blank' title='Email Thi…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  995. Warning Line 1491, Column 143: reference to external entity in attribute value
    …0835&postID=8667000908994685280&target=email' target='_blank' title='Email Thi…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  996. Error Line 1491, Column 143: reference to entity "target" for which no system identifier could be generated
    …0835&postID=8667000908994685280&target=email' target='_blank' title='Email Thi…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  997. Info Line 555, Column 136: entity was defined here
    …gID=9430835&postID=6945236942316918823&target=email' target='_blank' title='Em…
  998. Warning Line 1491, Column 358: reference not terminated by REFC delimiter
    …com/share-post.g?blogID=9430835&postID=8667000908994685280&target=blog' onclic…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  999. Warning Line 1491, Column 358: reference to external entity in attribute value
    …com/share-post.g?blogID=9430835&postID=8667000908994685280&target=blog' onclic…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1000. Error Line 1491, Column 358: reference to entity "postID" for which no system identifier could be generated
    …com/share-post.g?blogID=9430835&postID=8667000908994685280&target=blog' onclic…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1001. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  1002. Warning Line 1491, Column 385: reference not terminated by REFC delimiter
    …0835&postID=8667000908994685280&target=blog' onclick='window.open(this.href, "…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1003. Warning Line 1491, Column 385: reference to external entity in attribute value
    …0835&postID=8667000908994685280&target=blog' onclick='window.open(this.href, "…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1004. Error Line 1491, Column 385: reference to entity "target" for which no system identifier could be generated
    …0835&postID=8667000908994685280&target=blog' onclick='window.open(this.href, "…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1005. Info Line 555, Column 136: entity was defined here
    …gID=9430835&postID=6945236942316918823&target=email' target='_blank' title='Em…
  1006. Warning Line 1491, Column 682: reference not terminated by REFC delimiter
    …com/share-post.g?blogID=9430835&postID=8667000908994685280&target=twitter' tar…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1007. Warning Line 1491, Column 682: reference to external entity in attribute value
    …com/share-post.g?blogID=9430835&postID=8667000908994685280&target=twitter' tar…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1008. Error Line 1491, Column 682: reference to entity "postID" for which no system identifier could be generated
    …com/share-post.g?blogID=9430835&postID=8667000908994685280&target=twitter' tar…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1009. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  1010. Warning Line 1491, Column 709: reference not terminated by REFC delimiter
    …0835&postID=8667000908994685280&target=twitter' target='_blank' title='Share t…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1011. Warning Line 1491, Column 709: reference to external entity in attribute value
    …0835&postID=8667000908994685280&target=twitter' target='_blank' title='Share t…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1012. Error Line 1491, Column 709: reference to entity "target" for which no system identifier could be generated
    …0835&postID=8667000908994685280&target=twitter' target='_blank' title='Share t…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1013. Info Line 555, Column 136: entity was defined here
    …gID=9430835&postID=6945236942316918823&target=email' target='_blank' title='Em…
  1014. Warning Line 1491, Column 942: reference not terminated by REFC delimiter
    …com/share-post.g?blogID=9430835&postID=8667000908994685280&target=facebook' on…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1015. Warning Line 1491, Column 942: reference to external entity in attribute value
    …com/share-post.g?blogID=9430835&postID=8667000908994685280&target=facebook' on…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1016. Error Line 1491, Column 942: reference to entity "postID" for which no system identifier could be generated
    …com/share-post.g?blogID=9430835&postID=8667000908994685280&target=facebook' on…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1017. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  1018. Warning Line 1491, Column 969: reference not terminated by REFC delimiter
    …0835&postID=8667000908994685280&target=facebook' onclick='window.open(this.hre…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1019. Warning Line 1491, Column 969: reference to external entity in attribute value
    …0835&postID=8667000908994685280&target=facebook' onclick='window.open(this.hre…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1020. Error Line 1491, Column 969: reference to entity "target" for which no system identifier could be generated
    …0835&postID=8667000908994685280&target=facebook' onclick='window.open(this.hre…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1021. Info Line 555, Column 136: entity was defined here
    …gID=9430835&postID=6945236942316918823&target=email' target='_blank' title='Em…
  1022. Warning Line 1491, Column 1288: reference not terminated by REFC delimiter
    …com/share-post.g?blogID=9430835&postID=8667000908994685280&target=pinterest' t…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1023. Warning Line 1491, Column 1288: reference to external entity in attribute value
    …com/share-post.g?blogID=9430835&postID=8667000908994685280&target=pinterest' t…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1024. Error Line 1491, Column 1288: reference to entity "postID" for which no system identifier could be generated
    …com/share-post.g?blogID=9430835&postID=8667000908994685280&target=pinterest' t…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1025. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  1026. Warning Line 1491, Column 1315: reference not terminated by REFC delimiter
    …0835&postID=8667000908994685280&target=pinterest' target='_blank' title='Share…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1027. Warning Line 1491, Column 1315: reference to external entity in attribute value
    …0835&postID=8667000908994685280&target=pinterest' target='_blank' title='Share…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1028. Error Line 1491, Column 1315: reference to entity "target" for which no system identifier could be generated
    …0835&postID=8667000908994685280&target=pinterest' target='_blank' title='Share…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1029. Info Line 555, Column 136: entity was defined here
    …gID=9430835&postID=6945236942316918823&target=email' target='_blank' title='Em…
  1030. Error Line 1491, Column 1658: element "g:plusone" undefined
    …es-edge-of-tomorrow.html' size='medium' width='300' annotation='inline'/></div>

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  1031. Error Line 1509, Column 69: document type does not allow element "a" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …teve/world-war-t-v-world-war-piketty/">http://www.unz.com/isteve/world-war-t-v…

    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 "<a>", "<span>", or "<font>").

  1032. Warning Line 1523, Column 86: reference not terminated by REFC delimiter
    …w.blogger.com/comment.g?blogID=9430835&postID=7525623255117610383' onclick=''>0

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1033. Warning Line 1523, Column 86: reference to external entity in attribute value
    …w.blogger.com/comment.g?blogID=9430835&postID=7525623255117610383' onclick=''>0

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1034. Error Line 1523, Column 86: reference to entity "postID" for which no system identifier could be generated
    …w.blogger.com/comment.g?blogID=9430835&postID=7525623255117610383' onclick=''>0

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1035. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  1036. Warning Line 1528, Column 68: reference not terminated by REFC delimiter
    …com/email-post.g?blogID=9430835&postID=7525623255117610383' title='Email Post'…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1037. Warning Line 1528, Column 68: reference to external entity in attribute value
    …com/email-post.g?blogID=9430835&postID=7525623255117610383' title='Email Post'…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1038. Error Line 1528, Column 68: reference to entity "postID" for which no system identifier could be generated
    …com/email-post.g?blogID=9430835&postID=7525623255117610383' title='Email Post'…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1039. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  1040. Warning Line 1533, Column 67: reference not terminated by REFC delimiter
    ….com/post-edit.g?blogID=9430835&postID=7525623255117610383&from=pencil' title=…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1041. Warning Line 1533, Column 67: reference to external entity in attribute value
    ….com/post-edit.g?blogID=9430835&postID=7525623255117610383&from=pencil' title=…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1042. Error Line 1533, Column 67: reference to entity "postID" for which no system identifier could be generated
    ….com/post-edit.g?blogID=9430835&postID=7525623255117610383&from=pencil' title=…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1043. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  1044. Warning Line 1533, Column 92: reference not terminated by REFC delimiter
    …dit.g?blogID=9430835&postID=7525623255117610383&from=pencil' title='Edit Post'>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1045. Warning Line 1533, Column 92: reference to external entity in attribute value
    …dit.g?blogID=9430835&postID=7525623255117610383&from=pencil' title='Edit Post'>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1046. Error Line 1533, Column 92: reference to entity "from" for which no system identifier could be generated
    …dit.g?blogID=9430835&postID=7525623255117610383&from=pencil' title='Edit Post'>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1047. Info Line 542, Column 87: entity was defined here
    …dit.g?blogID=9430835&postID=6945236942316918823&from=pencil' title='Edit Post'>
  1048. Warning Line 1546, Column 116: reference not terminated by REFC delimiter
    …com/share-post.g?blogID=9430835&postID=7525623255117610383&target=email' targe…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1049. Warning Line 1546, Column 116: reference to external entity in attribute value
    …com/share-post.g?blogID=9430835&postID=7525623255117610383&target=email' targe…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1050. Error Line 1546, Column 116: reference to entity "postID" for which no system identifier could be generated
    …com/share-post.g?blogID=9430835&postID=7525623255117610383&target=email' targe…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1051. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  1052. Warning Line 1546, Column 143: reference not terminated by REFC delimiter
    …0835&postID=7525623255117610383&target=email' target='_blank' title='Email Thi…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1053. Warning Line 1546, Column 143: reference to external entity in attribute value
    …0835&postID=7525623255117610383&target=email' target='_blank' title='Email Thi…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1054. Error Line 1546, Column 143: reference to entity "target" for which no system identifier could be generated
    …0835&postID=7525623255117610383&target=email' target='_blank' title='Email Thi…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1055. Info Line 555, Column 136: entity was defined here
    …gID=9430835&postID=6945236942316918823&target=email' target='_blank' title='Em…
  1056. Warning Line 1546, Column 358: reference not terminated by REFC delimiter
    …com/share-post.g?blogID=9430835&postID=7525623255117610383&target=blog' onclic…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1057. Warning Line 1546, Column 358: reference to external entity in attribute value
    …com/share-post.g?blogID=9430835&postID=7525623255117610383&target=blog' onclic…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1058. Error Line 1546, Column 358: reference to entity "postID" for which no system identifier could be generated
    …com/share-post.g?blogID=9430835&postID=7525623255117610383&target=blog' onclic…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1059. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  1060. Warning Line 1546, Column 385: reference not terminated by REFC delimiter
    …0835&postID=7525623255117610383&target=blog' onclick='window.open(this.href, "…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1061. Warning Line 1546, Column 385: reference to external entity in attribute value
    …0835&postID=7525623255117610383&target=blog' onclick='window.open(this.href, "…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1062. Error Line 1546, Column 385: reference to entity "target" for which no system identifier could be generated
    …0835&postID=7525623255117610383&target=blog' onclick='window.open(this.href, "…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1063. Info Line 555, Column 136: entity was defined here
    …gID=9430835&postID=6945236942316918823&target=email' target='_blank' title='Em…
  1064. Warning Line 1546, Column 682: reference not terminated by REFC delimiter
    …com/share-post.g?blogID=9430835&postID=7525623255117610383&target=twitter' tar…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1065. Warning Line 1546, Column 682: reference to external entity in attribute value
    …com/share-post.g?blogID=9430835&postID=7525623255117610383&target=twitter' tar…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1066. Error Line 1546, Column 682: reference to entity "postID" for which no system identifier could be generated
    …com/share-post.g?blogID=9430835&postID=7525623255117610383&target=twitter' tar…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1067. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  1068. Warning Line 1546, Column 709: reference not terminated by REFC delimiter
    …0835&postID=7525623255117610383&target=twitter' target='_blank' title='Share t…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1069. Warning Line 1546, Column 709: reference to external entity in attribute value
    …0835&postID=7525623255117610383&target=twitter' target='_blank' title='Share t…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1070. Error Line 1546, Column 709: reference to entity "target" for which no system identifier could be generated
    …0835&postID=7525623255117610383&target=twitter' target='_blank' title='Share t…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1071. Info Line 555, Column 136: entity was defined here
    …gID=9430835&postID=6945236942316918823&target=email' target='_blank' title='Em…
  1072. Warning Line 1546, Column 942: reference not terminated by REFC delimiter
    …com/share-post.g?blogID=9430835&postID=7525623255117610383&target=facebook' on…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1073. Warning Line 1546, Column 942: reference to external entity in attribute value
    …com/share-post.g?blogID=9430835&postID=7525623255117610383&target=facebook' on…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1074. Error Line 1546, Column 942: reference to entity "postID" for which no system identifier could be generated
    …com/share-post.g?blogID=9430835&postID=7525623255117610383&target=facebook' on…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1075. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  1076. Warning Line 1546, Column 969: reference not terminated by REFC delimiter
    …0835&postID=7525623255117610383&target=facebook' onclick='window.open(this.hre…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1077. Warning Line 1546, Column 969: reference to external entity in attribute value
    …0835&postID=7525623255117610383&target=facebook' onclick='window.open(this.hre…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1078. Error Line 1546, Column 969: reference to entity "target" for which no system identifier could be generated
    …0835&postID=7525623255117610383&target=facebook' onclick='window.open(this.hre…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1079. Info Line 555, Column 136: entity was defined here
    …gID=9430835&postID=6945236942316918823&target=email' target='_blank' title='Em…
  1080. Warning Line 1546, Column 1288: reference not terminated by REFC delimiter
    …com/share-post.g?blogID=9430835&postID=7525623255117610383&target=pinterest' t…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1081. Warning Line 1546, Column 1288: reference to external entity in attribute value
    …com/share-post.g?blogID=9430835&postID=7525623255117610383&target=pinterest' t…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1082. Error Line 1546, Column 1288: reference to entity "postID" for which no system identifier could be generated
    …com/share-post.g?blogID=9430835&postID=7525623255117610383&target=pinterest' t…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1083. Info Line 532, Column 79: entity was defined here
    …w.blogger.com/comment.g?blogID=9430835&postID=6945236942316918823' onclick=''>…
  1084. Warning Line 1546, Column 1315: reference not terminated by REFC delimiter
    …0835&postID=7525623255117610383&target=pinterest' target='_blank' title='Share…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1085. Warning Line 1546, Column 1315: reference to external entity in attribute value
    …0835&postID=7525623255117610383&target=pinterest' target='_blank' title='Share…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1086. Error Line 1546, Column 1315: reference to entity "target" for which no system identifier could be generated
    …0835&postID=7525623255117610383&target=pinterest' target='_blank' title='Share…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1087. Info Line 555, Column 136: entity was defined here
    …gID=9430835&postID=6945236942316918823&target=email' target='_blank' title='Em…
  1088. Error Line 1546, Column 1664: element "g:plusone" undefined
    …male-ceo-in-america.html' size='medium' width='300' annotation='inline'/></div>

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  1089. Error Line 1575, Column 286: there is no attribute "face"
    …upport my work:</span></div><div face="Georgia, serif" size="3" style="font-st…

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  1090. Error Line 1575, Column 308: there is no attribute "size"
    …</div><div face="Georgia, serif" size="3" style="font-style: normal; font-weig…

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  1091. Error Line 1575, Column 2885: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …ont-family:Arial;font-size:100%;"><div></div></span><p   style="font-family: G…

    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 "<a>", "<span>", or "<font>").

  1092. Warning Line 1580, Column 71: cannot generate system identifier for general entity "widgetType"
    ….blogger.com/rearrange?blogID=9430835&widgetType=Text&widgetId=Text2&action=ed…

    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 "&amp;" (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 &aelig; 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.

  1093. Error Line 1580, Column 71: general entity "widgetType" not defined and no default entity
    ….blogger.com/rearrange?blogID=9430835&widgetType=Text&widgetId=Text2&action=ed…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1094. Warning Line 1580, Column 81: reference not terminated by REFC delimiter
    …om/rearrange?blogID=9430835&widgetType=Text&widgetId=Text2&action=editWidget&s…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1095. Warning Line 1580, Column 81: reference to external entity in attribute value
    …om/rearrange?blogID=9430835&widgetType=Text&widgetId=Text2&action=editWidget&s…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1096. Error Line 1580, Column 81: reference to entity "widgetType" for which no system identifier could be generated
    …om/rearrange?blogID=9430835&widgetType=Text&widgetId=Text2&action=editWidget&s…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1097. Info Line 1580, Column 70: entity was defined here
    …w.blogger.com/rearrange?blogID=9430835&widgetType=Text&widgetId=Text2&action=e…
  1098. Warning Line 1580, Column 87: cannot generate system identifier for general entity "widgetId"
    …rrange?blogID=9430835&widgetType=Text&widgetId=Text2&action=editWidget&section…

    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 "&amp;" (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 &aelig; 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.

  1099. Error Line 1580, Column 87: general entity "widgetId" not defined and no default entity
    …rrange?blogID=9430835&widgetType=Text&widgetId=Text2&action=editWidget&section…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1100. Warning Line 1580, Column 95: reference not terminated by REFC delimiter
    …logID=9430835&widgetType=Text&widgetId=Text2&action=editWidget&sectionId=sideb…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1101. Warning Line 1580, Column 95: reference to external entity in attribute value
    …logID=9430835&widgetType=Text&widgetId=Text2&action=editWidget&sectionId=sideb…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1102. Error Line 1580, Column 95: reference to entity "widgetId" for which no system identifier could be generated
    …logID=9430835&widgetType=Text&widgetId=Text2&action=editWidget&sectionId=sideb…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1103. Info Line 1580, Column 86: entity was defined here
    …arrange?blogID=9430835&widgetType=Text&widgetId=Text2&action=editWidget&sectio…
  1104. Warning Line 1580, Column 102: cannot generate system identifier for general entity "action"
    …430835&widgetType=Text&widgetId=Text2&action=editWidget&sectionId=sidebar' onc…

    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 "&amp;" (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 &aelig; 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.

  1105. Error Line 1580, Column 102: general entity "action" not defined and no default entity
    …430835&widgetType=Text&widgetId=Text2&action=editWidget&sectionId=sidebar' onc…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1106. Warning Line 1580, Column 108: reference not terminated by REFC delimiter
    …&widgetType=Text&widgetId=Text2&action=editWidget&sectionId=sidebar' onclick='…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1107. Warning Line 1580, Column 108: reference to external entity in attribute value
    …&widgetType=Text&widgetId=Text2&action=editWidget&sectionId=sidebar' onclick='…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1108. Error Line 1580, Column 108: reference to entity "action" for which no system identifier could be generated
    …&widgetType=Text&widgetId=Text2&action=editWidget&sectionId=sidebar' onclick='…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1109. Info Line 1580, Column 101: entity was defined here
    …9430835&widgetType=Text&widgetId=Text2&action=editWidget&sectionId=sidebar' on…
  1110. Warning Line 1580, Column 120: cannot generate system identifier for general entity "sectionId"
    …Text&widgetId=Text2&action=editWidget&sectionId=sidebar' onclick='return _Widg…

    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 "&amp;" (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 &aelig; 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.

  1111. Error Line 1580, Column 120: general entity "sectionId" not defined and no default entity
    …Text&widgetId=Text2&action=editWidget&sectionId=sidebar' onclick='return _Widg…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1112. Warning Line 1580, Column 129: reference not terminated by REFC delimiter
    …etId=Text2&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1113. Warning Line 1580, Column 129: reference to external entity in attribute value
    …etId=Text2&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1114. Error Line 1580, Column 129: reference to entity "sectionId" for which no system identifier could be generated
    …etId=Text2&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1115. Info Line 1580, Column 119: entity was defined here
    …=Text&widgetId=Text2&action=editWidget&sectionId=sidebar' onclick='return _Wid…
  1116. Error Line 1594, Column 102: required attribute "alt" not specified
    …ropdown-arrow' src='https://img2.blogblog.com/img/widgets/arrow_dropdown.gif'/>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  1117. Error Line 1595, Column 12: there is no attribute "align"
    <img align='absmiddle' alt='' border='0' class='feed-icon' src='https://img1.bl…

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  1118. Error Line 1600, Column 73: required attribute "alt" not specified
    <img src='https://img1.blogblog.com/img/widgets/subscribe-netvibes.png'/>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  1119. Error Line 1603, Column 70: required attribute "alt" not specified
    <img src='https://img1.blogblog.com/img/widgets/subscribe-yahoo.png'/>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  1120. Error Line 1606, Column 94: required attribute "alt" not specified
    …middle' class='feed-icon' src='https://img1.blogblog.com/img/icon_feed12.png'/>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  1121. Error Line 1616, Column 102: required attribute "alt" not specified
    …ropdown-arrow' src='https://img2.blogblog.com/img/widgets/arrow_dropdown.gif'/>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  1122. Error Line 1630, Column 102: required attribute "alt" not specified
    …ropdown-arrow' src='https://img2.blogblog.com/img/widgets/arrow_dropdown.gif'/>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  1123. Error Line 1636, Column 73: required attribute "alt" not specified
    <img src='https://img1.blogblog.com/img/widgets/subscribe-netvibes.png'/>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  1124. Error Line 1639, Column 70: required attribute "alt" not specified
    <img src='https://img1.blogblog.com/img/widgets/subscribe-yahoo.png'/>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  1125. Error Line 1642, Column 94: required attribute "alt" not specified
    …middle' class='feed-icon' src='https://img1.blogblog.com/img/icon_feed12.png'/>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  1126. Error Line 1652, Column 102: required attribute "alt" not specified
    …ropdown-arrow' src='https://img2.blogblog.com/img/widgets/arrow_dropdown.gif'/>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  1127. Warning Line 1668, Column 81: reference not terminated by REFC delimiter
    …om/rearrange?blogID=9430835&widgetType=Subscribe&widgetId=Subscribe4&action=ed…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1128. Warning Line 1668, Column 81: reference to external entity in attribute value
    …om/rearrange?blogID=9430835&widgetType=Subscribe&widgetId=Subscribe4&action=ed…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1129. Error Line 1668, Column 81: reference to entity "widgetType" for which no system identifier could be generated
    …om/rearrange?blogID=9430835&widgetType=Subscribe&widgetId=Subscribe4&action=ed…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1130. Info Line 1580, Column 70: entity was defined here
    …w.blogger.com/rearrange?blogID=9430835&widgetType=Text&widgetId=Text2&action=e…
  1131. Warning Line 1668, Column 100: reference not terminated by REFC delimiter
    …=9430835&widgetType=Subscribe&widgetId=Subscribe4&action=editWidget&sectionId=…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1132. Warning Line 1668, Column 100: reference to external entity in attribute value
    …=9430835&widgetType=Subscribe&widgetId=Subscribe4&action=editWidget&sectionId=…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1133. Error Line 1668, Column 100: reference to entity "widgetId" for which no system identifier could be generated
    …=9430835&widgetType=Subscribe&widgetId=Subscribe4&action=editWidget&sectionId=…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1134. Info Line 1580, Column 86: entity was defined here
    …arrange?blogID=9430835&widgetType=Text&widgetId=Text2&action=editWidget&sectio…
  1135. Warning Line 1668, Column 118: reference not terminated by REFC delimiter
    …e=Subscribe&widgetId=Subscribe4&action=editWidget&sectionId=sidebar' onclick='…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1136. Warning Line 1668, Column 118: reference to external entity in attribute value
    …e=Subscribe&widgetId=Subscribe4&action=editWidget&sectionId=sidebar' onclick='…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1137. Error Line 1668, Column 118: reference to entity "action" for which no system identifier could be generated
    …e=Subscribe&widgetId=Subscribe4&action=editWidget&sectionId=sidebar' onclick='…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1138. Info Line 1580, Column 101: entity was defined here
    …9430835&widgetType=Text&widgetId=Text2&action=editWidget&sectionId=sidebar' on…
  1139. Warning Line 1668, Column 139: reference not terminated by REFC delimiter
    …Subscribe4&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1140. Warning Line 1668, Column 139: reference to external entity in attribute value
    …Subscribe4&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1141. Error Line 1668, Column 139: reference to entity "sectionId" for which no system identifier could be generated
    …Subscribe4&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1142. Info Line 1580, Column 119: entity was defined here
    …=Text&widgetId=Text2&action=editWidget&sectionId=sidebar' onclick='return _Wid…
  1143. Warning Line 1681, Column 81: reference not terminated by REFC delimiter
    …om/rearrange?blogID=9430835&widgetType=Text&widgetId=Text1&action=editWidget&s…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1144. Warning Line 1681, Column 81: reference to external entity in attribute value
    …om/rearrange?blogID=9430835&widgetType=Text&widgetId=Text1&action=editWidget&s…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1145. Error Line 1681, Column 81: reference to entity "widgetType" for which no system identifier could be generated
    …om/rearrange?blogID=9430835&widgetType=Text&widgetId=Text1&action=editWidget&s…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1146. Info Line 1580, Column 70: entity was defined here
    …w.blogger.com/rearrange?blogID=9430835&widgetType=Text&widgetId=Text2&action=e…
  1147. Warning Line 1681, Column 95: reference not terminated by REFC delimiter
    …logID=9430835&widgetType=Text&widgetId=Text1&action=editWidget&sectionId=sideb…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1148. Warning Line 1681, Column 95: reference to external entity in attribute value
    …logID=9430835&widgetType=Text&widgetId=Text1&action=editWidget&sectionId=sideb…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1149. Error Line 1681, Column 95: reference to entity "widgetId" for which no system identifier could be generated
    …logID=9430835&widgetType=Text&widgetId=Text1&action=editWidget&sectionId=sideb…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1150. Info Line 1580, Column 86: entity was defined here
    …arrange?blogID=9430835&widgetType=Text&widgetId=Text2&action=editWidget&sectio…
  1151. Warning Line 1681, Column 108: reference not terminated by REFC delimiter
    …&widgetType=Text&widgetId=Text1&action=editWidget&sectionId=sidebar' onclick='…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1152. Warning Line 1681, Column 108: reference to external entity in attribute value
    …&widgetType=Text&widgetId=Text1&action=editWidget&sectionId=sidebar' onclick='…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1153. Error Line 1681, Column 108: reference to entity "action" for which no system identifier could be generated
    …&widgetType=Text&widgetId=Text1&action=editWidget&sectionId=sidebar' onclick='…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1154. Info Line 1580, Column 101: entity was defined here
    …9430835&widgetType=Text&widgetId=Text2&action=editWidget&sectionId=sidebar' on…
  1155. Warning Line 1681, Column 129: reference not terminated by REFC delimiter
    …etId=Text1&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1156. Warning Line 1681, Column 129: reference to external entity in attribute value
    …etId=Text1&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1157. Error Line 1681, Column 129: reference to entity "sectionId" for which no system identifier could be generated
    …etId=Text1&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1158. Info Line 1580, Column 119: entity was defined here
    …=Text&widgetId=Text2&action=editWidget&sectionId=sidebar' onclick='return _Wid…
  1159. Warning Line 1709, Column 49: cannot generate system identifier for general entity "c2coff"
    …f='http://www.google.com/search?hl=en&c2coff=1&safe=off&client=firefox-a&rls=o…

    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 "&amp;" (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 &aelig; 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.

  1160. Error Line 1709, Column 49: general entity "c2coff" not defined and no default entity
    …f='http://www.google.com/search?hl=en&c2coff=1&safe=off&client=firefox-a&rls=o…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1161. Warning Line 1709, Column 55: reference not terminated by REFC delimiter
    …p://www.google.com/search?hl=en&c2coff=1&safe=off&client=firefox-a&rls=org.moz…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1162. Warning Line 1709, Column 55: reference to external entity in attribute value
    …p://www.google.com/search?hl=en&c2coff=1&safe=off&client=firefox-a&rls=org.moz…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1163. Error Line 1709, Column 55: reference to entity "c2coff" for which no system identifier could be generated
    …p://www.google.com/search?hl=en&c2coff=1&safe=off&client=firefox-a&rls=org.moz…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1164. Info Line 1709, Column 48: entity was defined here
    …ef='http://www.google.com/search?hl=en&c2coff=1&safe=off&client=firefox-a&rls=…
  1165. Warning Line 1709, Column 58: cannot generate system identifier for general entity "safe"
    …/www.google.com/search?hl=en&c2coff=1&safe=off&client=firefox-a&rls=org.mozill…

    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 "&amp;" (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 &aelig; 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.

  1166. Error Line 1709, Column 58: general entity "safe" not defined and no default entity
    …/www.google.com/search?hl=en&c2coff=1&safe=off&client=firefox-a&rls=org.mozill…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1167. Warning Line 1709, Column 62: reference not terminated by REFC delimiter
    ….google.com/search?hl=en&c2coff=1&safe=off&client=firefox-a&rls=org.mozilla:en…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1168. Warning Line 1709, Column 62: reference to external entity in attribute value
    ….google.com/search?hl=en&c2coff=1&safe=off&client=firefox-a&rls=org.mozilla:en…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1169. Error Line 1709, Column 62: reference to entity "safe" for which no system identifier could be generated
    ….google.com/search?hl=en&c2coff=1&safe=off&client=firefox-a&rls=org.mozilla:en…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1170. Info Line 1709, Column 57: entity was defined here
    …//www.google.com/search?hl=en&c2coff=1&safe=off&client=firefox-a&rls=org.mozil…
  1171. Warning Line 1709, Column 67: cannot generate system identifier for general entity "client"
    …le.com/search?hl=en&c2coff=1&safe=off&client=firefox-a&rls=org.mozilla:en-US:o…

    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 "&amp;" (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 &aelig; 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.

  1172. Error Line 1709, Column 67: general entity "client" not defined and no default entity
    …le.com/search?hl=en&c2coff=1&safe=off&client=firefox-a&rls=org.mozilla:en-US:o…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1173. Warning Line 1709, Column 73: reference not terminated by REFC delimiter
    …/search?hl=en&c2coff=1&safe=off&client=firefox-a&rls=org.mozilla:en-US:officia…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1174. Warning Line 1709, Column 73: reference to external entity in attribute value
    …/search?hl=en&c2coff=1&safe=off&client=firefox-a&rls=org.mozilla:en-US:officia…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1175. Error Line 1709, Column 73: reference to entity "client" for which no system identifier could be generated
    …/search?hl=en&c2coff=1&safe=off&client=firefox-a&rls=org.mozilla:en-US:officia…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1176. Info Line 1709, Column 66: entity was defined here
    …gle.com/search?hl=en&c2coff=1&safe=off&client=firefox-a&rls=org.mozilla:en-US:…
  1177. Warning Line 1709, Column 84: cannot generate system identifier for general entity "rls"
    …en&c2coff=1&safe=off&client=firefox-a&rls=org.mozilla:en-US:official&hs=HAJ&q=…

    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 "&amp;" (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 &aelig; 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.

  1178. Error Line 1709, Column 84: general entity "rls" not defined and no default entity
    …en&c2coff=1&safe=off&client=firefox-a&rls=org.mozilla:en-US:official&hs=HAJ&q=…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1179. Warning Line 1709, Column 87: reference not terminated by REFC delimiter
    …c2coff=1&safe=off&client=firefox-a&rls=org.mozilla:en-US:official&hs=HAJ&q=+si…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1180. Warning Line 1709, Column 87: reference to external entity in attribute value
    …c2coff=1&safe=off&client=firefox-a&rls=org.mozilla:en-US:official&hs=HAJ&q=+si…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1181. Error Line 1709, Column 87: reference to entity "rls" for which no system identifier could be generated
    …c2coff=1&safe=off&client=firefox-a&rls=org.mozilla:en-US:official&hs=HAJ&q=+si…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1182. Info Line 1709, Column 83: entity was defined here
    …=en&c2coff=1&safe=off&client=firefox-a&rls=org.mozilla:en-US:official&hs=HAJ&q…
  1183. Warning Line 1709, Column 115: cannot generate system identifier for general entity "hs"
    …efox-a&rls=org.mozilla:en-US:official&hs=HAJ&q=+site:www.amconmag.com+%22steve…

    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 "&amp;" (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 &aelig; 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.

  1184. Error Line 1709, Column 115: general entity "hs" not defined and no default entity
    …efox-a&rls=org.mozilla:en-US:official&hs=HAJ&q=+site:www.amconmag.com+%22steve…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1185. Warning Line 1709, Column 117: reference not terminated by REFC delimiter
    …ox-a&rls=org.mozilla:en-US:official&hs=HAJ&q=+site:www.amconmag.com+%22steve+s…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1186. Warning Line 1709, Column 117: reference to external entity in attribute value
    …ox-a&rls=org.mozilla:en-US:official&hs=HAJ&q=+site:www.amconmag.com+%22steve+s…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1187. Error Line 1709, Column 117: reference to entity "hs" for which no system identifier could be generated
    …ox-a&rls=org.mozilla:en-US:official&hs=HAJ&q=+site:www.amconmag.com+%22steve+s…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1188. Info Line 1709, Column 114: entity was defined here
    …refox-a&rls=org.mozilla:en-US:official&hs=HAJ&q=+site:www.amconmag.com+%22stev…
  1189. Warning Line 1709, Column 122: cannot generate system identifier for general entity "q"
    …rls=org.mozilla:en-US:official&hs=HAJ&q=+site:www.amconmag.com+%22steve+sailer…

    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 "&amp;" (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 &aelig; 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.

  1190. Error Line 1709, Column 122: general entity "q" not defined and no default entity
    …rls=org.mozilla:en-US:official&hs=HAJ&q=+site:www.amconmag.com+%22steve+sailer…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1191. Warning Line 1709, Column 123: reference not terminated by REFC delimiter
    …ls=org.mozilla:en-US:official&hs=HAJ&q=+site:www.amconmag.com+%22steve+sailer%…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1192. Warning Line 1709, Column 123: reference to external entity in attribute value
    …ls=org.mozilla:en-US:official&hs=HAJ&q=+site:www.amconmag.com+%22steve+sailer%…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1193. Error Line 1709, Column 123: reference to entity "q" for which no system identifier could be generated
    …ls=org.mozilla:en-US:official&hs=HAJ&q=+site:www.amconmag.com+%22steve+sailer%…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1194. Info Line 1709, Column 121: entity was defined here
    …&rls=org.mozilla:en-US:official&hs=HAJ&q=+site:www.amconmag.com+%22steve+saile…
  1195. Warning Line 1715, Column 49: character "&" is the first character of a delimiter but occurred as data
    <li><a href='http://www.aldaily.com/'>Arts-Arts & Letters Daily</a></li>

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  1196. Warning Line 1746, Column 62: character "&" is the first character of a delimiter but occurred as data
    <li><a href='http://www.leadandgold.blogspot.com/'>Blog-Lead & Gold</a></li>

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  1197. Warning Line 1843, Column 81: reference not terminated by REFC delimiter
    …om/rearrange?blogID=9430835&widgetType=LinkList&widgetId=LinkList1&action=edit…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1198. Warning Line 1843, Column 81: reference to external entity in attribute value
    …om/rearrange?blogID=9430835&widgetType=LinkList&widgetId=LinkList1&action=edit…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1199. Error Line 1843, Column 81: reference to entity "widgetType" for which no system identifier could be generated
    …om/rearrange?blogID=9430835&widgetType=LinkList&widgetId=LinkList1&action=edit…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1200. Info Line 1580, Column 70: entity was defined here
    …w.blogger.com/rearrange?blogID=9430835&widgetType=Text&widgetId=Text2&action=e…
  1201. Warning Line 1843, Column 99: reference not terminated by REFC delimiter
    …D=9430835&widgetType=LinkList&widgetId=LinkList1&action=editWidget&sectionId=s…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1202. Warning Line 1843, Column 99: reference to external entity in attribute value
    …D=9430835&widgetType=LinkList&widgetId=LinkList1&action=editWidget&sectionId=s…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1203. Error Line 1843, Column 99: reference to entity "widgetId" for which no system identifier could be generated
    …D=9430835&widgetType=LinkList&widgetId=LinkList1&action=editWidget&sectionId=s…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1204. Info Line 1580, Column 86: entity was defined here
    …arrange?blogID=9430835&widgetType=Text&widgetId=Text2&action=editWidget&sectio…
  1205. Warning Line 1843, Column 116: reference not terminated by REFC delimiter
    …ype=LinkList&widgetId=LinkList1&action=editWidget&sectionId=sidebar' onclick='…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1206. Warning Line 1843, Column 116: reference to external entity in attribute value
    …ype=LinkList&widgetId=LinkList1&action=editWidget&sectionId=sidebar' onclick='…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1207. Error Line 1843, Column 116: reference to entity "action" for which no system identifier could be generated
    …ype=LinkList&widgetId=LinkList1&action=editWidget&sectionId=sidebar' onclick='…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1208. Info Line 1580, Column 101: entity was defined here
    …9430835&widgetType=Text&widgetId=Text2&action=editWidget&sectionId=sidebar' on…
  1209. Warning Line 1843, Column 137: reference not terminated by REFC delimiter
    …=LinkList1&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1210. Warning Line 1843, Column 137: reference to external entity in attribute value
    …=LinkList1&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1211. Error Line 1843, Column 137: reference to entity "sectionId" for which no system identifier could be generated
    …=LinkList1&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1212. Info Line 1580, Column 119: entity was defined here
    …=Text&widgetId=Text2&action=editWidget&sectionId=sidebar' onclick='return _Wid…
  1213. Warning Line 1858, Column 81: reference not terminated by REFC delimiter
    …om/rearrange?blogID=9430835&widgetType=Image&widgetId=Image3&action=editWidget…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1214. Warning Line 1858, Column 81: reference to external entity in attribute value
    …om/rearrange?blogID=9430835&widgetType=Image&widgetId=Image3&action=editWidget…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1215. Error Line 1858, Column 81: reference to entity "widgetType" for which no system identifier could be generated
    …om/rearrange?blogID=9430835&widgetType=Image&widgetId=Image3&action=editWidget…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1216. Info Line 1580, Column 70: entity was defined here
    …w.blogger.com/rearrange?blogID=9430835&widgetType=Text&widgetId=Text2&action=e…
  1217. Warning Line 1858, Column 96: reference not terminated by REFC delimiter
    …ogID=9430835&widgetType=Image&widgetId=Image3&action=editWidget&sectionId=side…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1218. Warning Line 1858, Column 96: reference to external entity in attribute value
    …ogID=9430835&widgetType=Image&widgetId=Image3&action=editWidget&sectionId=side…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1219. Error Line 1858, Column 96: reference to entity "widgetId" for which no system identifier could be generated
    …ogID=9430835&widgetType=Image&widgetId=Image3&action=editWidget&sectionId=side…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1220. Info Line 1580, Column 86: entity was defined here
    …arrange?blogID=9430835&widgetType=Text&widgetId=Text2&action=editWidget&sectio…
  1221. Warning Line 1858, Column 110: reference not terminated by REFC delimiter
    …idgetType=Image&widgetId=Image3&action=editWidget&sectionId=sidebar' onclick='…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1222. Warning Line 1858, Column 110: reference to external entity in attribute value
    …idgetType=Image&widgetId=Image3&action=editWidget&sectionId=sidebar' onclick='…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1223. Error Line 1858, Column 110: reference to entity "action" for which no system identifier could be generated
    …idgetType=Image&widgetId=Image3&action=editWidget&sectionId=sidebar' onclick='…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1224. Info Line 1580, Column 101: entity was defined here
    …9430835&widgetType=Text&widgetId=Text2&action=editWidget&sectionId=sidebar' on…
  1225. Warning Line 1858, Column 131: reference not terminated by REFC delimiter
    …tId=Image3&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1226. Warning Line 1858, Column 131: reference to external entity in attribute value
    …tId=Image3&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1227. Error Line 1858, Column 131: reference to entity "sectionId" for which no system identifier could be generated
    …tId=Image3&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1228. Info Line 1580, Column 119: entity was defined here
    …=Text&widgetId=Text2&action=editWidget&sectionId=sidebar' onclick='return _Wid…
  1229. Error Line 1871, Column 23: document type does not allow element "style" here
    <style type='text/css'>

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  1230. Warning Line 1931, Column 81: reference not terminated by REFC delimiter
    …om/rearrange?blogID=9430835&widgetType=CustomSearch&widgetId=CustomSearch1&act…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1231. Warning Line 1931, Column 81: reference to external entity in attribute value
    …om/rearrange?blogID=9430835&widgetType=CustomSearch&widgetId=CustomSearch1&act…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1232. Error Line 1931, Column 81: reference to entity "widgetType" for which no system identifier could be generated
    …om/rearrange?blogID=9430835&widgetType=CustomSearch&widgetId=CustomSearch1&act…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1233. Info Line 1580, Column 70: entity was defined here
    …w.blogger.com/rearrange?blogID=9430835&widgetType=Text&widgetId=Text2&action=e…
  1234. Warning Line 1931, Column 103: reference not terminated by REFC delimiter
    …30835&widgetType=CustomSearch&widgetId=CustomSearch1&action=editWidget&section…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1235. Warning Line 1931, Column 103: reference to external entity in attribute value
    …30835&widgetType=CustomSearch&widgetId=CustomSearch1&action=editWidget&section…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1236. Error Line 1931, Column 103: reference to entity "widgetId" for which no system identifier could be generated
    …30835&widgetType=CustomSearch&widgetId=CustomSearch1&action=editWidget&section…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1237. Info Line 1580, Column 86: entity was defined here
    …arrange?blogID=9430835&widgetType=Text&widgetId=Text2&action=editWidget&sectio…
  1238. Warning Line 1931, Column 124: reference not terminated by REFC delimiter
    …omSearch&widgetId=CustomSearch1&action=editWidget&sectionId=sidebar' onclick='…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1239. Warning Line 1931, Column 124: reference to external entity in attribute value
    …omSearch&widgetId=CustomSearch1&action=editWidget&sectionId=sidebar' onclick='…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1240. Error Line 1931, Column 124: reference to entity "action" for which no system identifier could be generated
    …omSearch&widgetId=CustomSearch1&action=editWidget&sectionId=sidebar' onclick='…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1241. Info Line 1580, Column 101: entity was defined here
    …9430835&widgetType=Text&widgetId=Text2&action=editWidget&sectionId=sidebar' on…
  1242. Warning Line 1931, Column 145: reference not terminated by REFC delimiter
    …tomSearch1&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1243. Warning Line 1931, Column 145: reference to external entity in attribute value
    …tomSearch1&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1244. Error Line 1931, Column 145: reference to entity "sectionId" for which no system identifier could be generated
    …tomSearch1&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1245. Info Line 1580, Column 119: entity was defined here
    …=Text&widgetId=Text2&action=editWidget&sectionId=sidebar' onclick='return _Wid…
  1246. Warning Line 1942, Column 81: reference not terminated by REFC delimiter
    …om/rearrange?blogID=9430835&widgetType=Gadget&widgetId=Gadget2&action=editWidg…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1247. Warning Line 1942, Column 81: reference to external entity in attribute value
    …om/rearrange?blogID=9430835&widgetType=Gadget&widgetId=Gadget2&action=editWidg…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1248. Error Line 1942, Column 81: reference to entity "widgetType" for which no system identifier could be generated
    …om/rearrange?blogID=9430835&widgetType=Gadget&widgetId=Gadget2&action=editWidg…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1249. Info Line 1580, Column 70: entity was defined here
    …w.blogger.com/rearrange?blogID=9430835&widgetType=Text&widgetId=Text2&action=e…
  1250. Warning Line 1942, Column 97: reference not terminated by REFC delimiter
    …gID=9430835&widgetType=Gadget&widgetId=Gadget2&action=editWidget&sectionId=sid…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1251. Warning Line 1942, Column 97: reference to external entity in attribute value
    …gID=9430835&widgetType=Gadget&widgetId=Gadget2&action=editWidget&sectionId=sid…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1252. Error Line 1942, Column 97: reference to entity "widgetId" for which no system identifier could be generated
    …gID=9430835&widgetType=Gadget&widgetId=Gadget2&action=editWidget&sectionId=sid…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1253. Info Line 1580, Column 86: entity was defined here
    …arrange?blogID=9430835&widgetType=Text&widgetId=Text2&action=editWidget&sectio…
  1254. Warning Line 1942, Column 112: reference not terminated by REFC delimiter
    …getType=Gadget&widgetId=Gadget2&action=editWidget&sectionId=sidebar' onclick='…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1255. Warning Line 1942, Column 112: reference to external entity in attribute value
    …getType=Gadget&widgetId=Gadget2&action=editWidget&sectionId=sidebar' onclick='…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1256. Error Line 1942, Column 112: reference to entity "action" for which no system identifier could be generated
    …getType=Gadget&widgetId=Gadget2&action=editWidget&sectionId=sidebar' onclick='…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1257. Info Line 1580, Column 101: entity was defined here
    …9430835&widgetType=Text&widgetId=Text2&action=editWidget&sectionId=sidebar' on…
  1258. Warning Line 1942, Column 133: reference not terminated by REFC delimiter
    …Id=Gadget2&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1259. Warning Line 1942, Column 133: reference to external entity in attribute value
    …Id=Gadget2&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1260. Error Line 1942, Column 133: reference to entity "sectionId" for which no system identifier could be generated
    …Id=Gadget2&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1261. Info Line 1580, Column 119: entity was defined here
    …=Text&widgetId=Text2&action=editWidget&sectionId=sidebar' onclick='return _Wid…
  1262. Error Line 1951, Column 15: there is no attribute "style"
    <script style=text/javascript src="http://helplogger.googlecode.com/svn/trunk/r…

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  1263. Error Line 1951, Column 15: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <script style=text/javascript src="http://helplogger.googlecode.com/svn/trunk/r…

  1264. Error Line 1951, Column 20: NET-enabling start-tag not immediately followed by null end-tag
    <script style=text/javascript src="http://helplogger.googlecode.com/svn/trunk/r…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  1265. Error Line 1951, Column 20: required attribute "type" not specified
    <script style=text/javascript src="http://helplogger.googlecode.com/svn/trunk/r…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  1266. Error Line 1951, Column 114: end tag for element "script" which is not open
    …nk/recent comments widget.js"></script><script style=text/javascript >var a_rc…

    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.

  1267. Error Line 1951, Column 129: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …nts widget.js"></script><script style=text/javascript >var a_rc=25;var m_rc=fa…

  1268. Error Line 1951, Column 134: NET-enabling start-tag not immediately followed by null end-tag
    …idget.js"></script><script style=text/javascript >var a_rc=25;var m_rc=false;v…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  1269. Error Line 1951, Column 134: required attribute "type" not specified
    …idget.js"></script><script style=text/javascript >var a_rc=25;var m_rc=false;v…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  1270. Error Line 1951, Column 208: end tag for element "script" which is not open
    …se;var n_rc=true;var o_rc=400;</script><script src=http://isteve.blogspot.com/…

    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.

  1271. Error Line 1951, Column 221: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …rue;var o_rc=400;</script><script src=http://isteve.blogspot.com/feeds/comment…

  1272. Error Line 1951, Column 227: NET-enabling start-tag not immediately followed by null end-tag
    …r o_rc=400;</script><script src=http://isteve.blogspot.com/feeds/comments/defa…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  1273. Error Line 1951, Column 227: required attribute "type" not specified
    …r o_rc=400;</script><script src=http://isteve.blogspot.com/feeds/comments/defa…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  1274. Warning Line 1951, Column 290: cannot generate system identifier for general entity "callback"
    …s/comments/default?alt=json-in-script&callback=showrecentcomments ></script><s…

    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 "&amp;" (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 &aelig; 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.

  1275. Error Line 1951, Column 290: general entity "callback" not defined and no default entity
    …s/comments/default?alt=json-in-script&callback=showrecentcomments ></script><s…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1276. Warning Line 1951, Column 298: reference not terminated by REFC delimiter
    …ts/default?alt=json-in-script&callback=showrecentcomments ></script><span id=r…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1277. Error Line 1951, Column 298: reference to entity "callback" for which no system identifier could be generated
    …ts/default?alt=json-in-script&callback=showrecentcomments ></script><span id=r…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1278. Info Line 1951, Column 289: entity was defined here
    …ds/comments/default?alt=json-in-script&callback=showrecentcomments ></script><…
  1279. Error Line 1951, Column 327: end tag for element "script" which is not open
    …&callback=showrecentcomments ></script><span id=rcw-cr><a href=http://helplogg…

    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.

  1280. Error Line 1951, Column 337: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …showrecentcomments ></script><span id=rcw-cr><a href=http://helplogger.blogspo…

  1281. Error Line 1951, Column 352: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …nts ></script><span id=rcw-cr><a href=http://helplogger.blogspot.com/2012/03/r…

  1282. Error Line 1951, Column 358: NET-enabling start-tag not immediately followed by null end-tag
    …/script><span id=rcw-cr><a href=http://helplogger.blogspot.com/2012/03/recent-…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  1283. Error Line 1951, Column 456: end tag for element "a" which is not open
    …blogger.html>Recent Comments Widget</a></span><style type=text/css> .rcw-comme…

    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.

  1284. Error Line 1951, Column 476: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …Comments Widget</a></span><style type=text/css> .rcw-comments a {text-transfor…

  1285. Error Line 1951, Column 481: NET-enabling start-tag not immediately followed by null end-tag
    …nts Widget</a></span><style type=text/css> .rcw-comments a {text-transform: ca…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  1286. Error Line 1951, Column 481: document type does not allow element "style" here
    …nts Widget</a></span><style type=text/css> .rcw-comments a {text-transform: ca…

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  1287. Error Line 1951, Column 722: end tag for element "style" which is not open
    …ont-family: Arial,Tahoma;font-size:9px;padding-top:7px;display:block;} </style>

    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.

  1288. Warning Line 1956, Column 81: reference not terminated by REFC delimiter
    …om/rearrange?blogID=9430835&widgetType=HTML&widgetId=HTML4&action=editWidget&s…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1289. Warning Line 1956, Column 81: reference to external entity in attribute value
    …om/rearrange?blogID=9430835&widgetType=HTML&widgetId=HTML4&action=editWidget&s…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1290. Error Line 1956, Column 81: reference to entity "widgetType" for which no system identifier could be generated
    …om/rearrange?blogID=9430835&widgetType=HTML&widgetId=HTML4&action=editWidget&s…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1291. Info Line 1580, Column 70: entity was defined here
    …w.blogger.com/rearrange?blogID=9430835&widgetType=Text&widgetId=Text2&action=e…
  1292. Warning Line 1956, Column 95: reference not terminated by REFC delimiter
    …logID=9430835&widgetType=HTML&widgetId=HTML4&action=editWidget&sectionId=sideb…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1293. Warning Line 1956, Column 95: reference to external entity in attribute value
    …logID=9430835&widgetType=HTML&widgetId=HTML4&action=editWidget&sectionId=sideb…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1294. Error Line 1956, Column 95: reference to entity "widgetId" for which no system identifier could be generated
    …logID=9430835&widgetType=HTML&widgetId=HTML4&action=editWidget&sectionId=sideb…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1295. Info Line 1580, Column 86: entity was defined here
    …arrange?blogID=9430835&widgetType=Text&widgetId=Text2&action=editWidget&sectio…
  1296. Warning Line 1956, Column 108: reference not terminated by REFC delimiter
    …&widgetType=HTML&widgetId=HTML4&action=editWidget&sectionId=sidebar' onclick='…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1297. Warning Line 1956, Column 108: reference to external entity in attribute value
    …&widgetType=HTML&widgetId=HTML4&action=editWidget&sectionId=sidebar' onclick='…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1298. Error Line 1956, Column 108: reference to entity "action" for which no system identifier could be generated
    …&widgetType=HTML&widgetId=HTML4&action=editWidget&sectionId=sidebar' onclick='…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1299. Info Line 1580, Column 101: entity was defined here
    …9430835&widgetType=Text&widgetId=Text2&action=editWidget&sectionId=sidebar' on…
  1300. Warning Line 1956, Column 129: reference not terminated by REFC delimiter
    …etId=HTML4&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1301. Warning Line 1956, Column 129: reference to external entity in attribute value
    …etId=HTML4&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1302. Error Line 1956, Column 129: reference to entity "sectionId" for which no system identifier could be generated
    …etId=HTML4&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1303. Info Line 1580, Column 119: entity was defined here
    …=Text&widgetId=Text2&action=editWidget&sectionId=sidebar' onclick='return _Wid…
  1304. Error Line 1967, Column 57: an attribute specification must start with a name or name token
              document.write('<script type="text/javascript"' +

    An attribute name (and some attribute values) must start with one of a restricted set of characters. This error usually indicates that you have failed to add a closing quotation mark on a previous attribute value (so the attribute value looks like the start of a new attribute) or have used an attribute that is not defined (usually a typo in a common attribute name).

  1305. Error Line 1967, Column 57: document type does not allow element "script" here
              document.write('<script type="text/javascript"' +

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  1306. Error Line 1969, Column 25: delimiter "'" invalid: only S separators and TAGC allowed here
                      '</scr' + 'ipt>');

  1307. Error Line 1969, Column 25: end tag for element "scr" which is not open
                      '</scr' + 'ipt>');

    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.

  1308. Error Line 1972, Column 31: document type does not allow element "script" here
    <script type="text/javascript">

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  1309. Error Line 1994, Column 31: document type does not allow element "script" here
    <script type="text/javascript">

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  1310. Error Line 2011, Column 13: there is no attribute "src"
    <iframe src="//9dl7h78ivl8smpn7vl3d9mo2g1ajbhaj-a-blogger-opensocial.googleuser…

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  1311. Error Line 2011, Column 684: there is no attribute "frameborder"
    …ken=-2724915628511647890" frameborder="0" style="width: 100%; display: block" …

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  1312. Error Line 2011, Column 694: there is no attribute "style"
    …15628511647890" frameborder="0" style="width: 100%; display: block" height="20…

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  1313. Error Line 2011, Column 731: there is no attribute "height"
    …="width: 100%; display: block" height="200" id="sidebar-gadget1" name="sidebar…

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  1314. Error Line 2011, Column 740: there is no attribute "id"
    …100%; display: block" height="200" id="sidebar-gadget1" name="sidebar-gadget1"…

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  1315. Error Line 2011, Column 763: there is no attribute "name"
    …play: block" height="200" id="sidebar-gadget1" name="sidebar-gadget1"></iframe>

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  1316. Error Line 2011, Column 780: element "iframe" undefined
    …play: block" height="200" id="sidebar-gadget1" name="sidebar-gadget1"></iframe>

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  1317. Error Line 2012, Column 31: document type does not allow element "script" here
    <script type="text/javascript">

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  1318. Error Line 2016, Column 6: end tag for "script" omitted, but OMITTAG NO was specified
    </div>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  1319. Info Line 1965, Column 1: start tag was here
    <script type="text/javascript">
  1320. Warning Line 2020, Column 81: reference not terminated by REFC delimiter
    …om/rearrange?blogID=9430835&widgetType=Gadget&widgetId=Gadget1&action=editWidg…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1321. Warning Line 2020, Column 81: reference to external entity in attribute value
    …om/rearrange?blogID=9430835&widgetType=Gadget&widgetId=Gadget1&action=editWidg…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1322. Error Line 2020, Column 81: reference to entity "widgetType" for which no system identifier could be generated
    …om/rearrange?blogID=9430835&widgetType=Gadget&widgetId=Gadget1&action=editWidg…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1323. Info Line 1580, Column 70: entity was defined here
    …w.blogger.com/rearrange?blogID=9430835&widgetType=Text&widgetId=Text2&action=e…
  1324. Warning Line 2020, Column 97: reference not terminated by REFC delimiter
    …gID=9430835&widgetType=Gadget&widgetId=Gadget1&action=editWidget&sectionId=sid…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1325. Warning Line 2020, Column 97: reference to external entity in attribute value
    …gID=9430835&widgetType=Gadget&widgetId=Gadget1&action=editWidget&sectionId=sid…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1326. Error Line 2020, Column 97: reference to entity "widgetId" for which no system identifier could be generated
    …gID=9430835&widgetType=Gadget&widgetId=Gadget1&action=editWidget&sectionId=sid…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1327. Info Line 1580, Column 86: entity was defined here
    …arrange?blogID=9430835&widgetType=Text&widgetId=Text2&action=editWidget&sectio…
  1328. Warning Line 2020, Column 112: reference not terminated by REFC delimiter
    …getType=Gadget&widgetId=Gadget1&action=editWidget&sectionId=sidebar' onclick='…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1329. Warning Line 2020, Column 112: reference to external entity in attribute value
    …getType=Gadget&widgetId=Gadget1&action=editWidget&sectionId=sidebar' onclick='…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1330. Error Line 2020, Column 112: reference to entity "action" for which no system identifier could be generated
    …getType=Gadget&widgetId=Gadget1&action=editWidget&sectionId=sidebar' onclick='…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1331. Info Line 1580, Column 101: entity was defined here
    …9430835&widgetType=Text&widgetId=Text2&action=editWidget&sectionId=sidebar' on…
  1332. Warning Line 2020, Column 133: reference not terminated by REFC delimiter
    …Id=Gadget1&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1333. Warning Line 2020, Column 133: reference to external entity in attribute value
    …Id=Gadget1&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1334. Error Line 2020, Column 133: reference to entity "sectionId" for which no system identifier could be generated
    …Id=Gadget1&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1335. Info Line 1580, Column 119: entity was defined here
    …=Text&widgetId=Text2&action=editWidget&sectionId=sidebar' onclick='return _Wid…
  1336. Warning Line 2036, Column 81: reference not terminated by REFC delimiter
    …om/rearrange?blogID=9430835&widgetType=Image&widgetId=Image2&action=editWidget…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1337. Warning Line 2036, Column 81: reference to external entity in attribute value
    …om/rearrange?blogID=9430835&widgetType=Image&widgetId=Image2&action=editWidget…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1338. Error Line 2036, Column 81: reference to entity "widgetType" for which no system identifier could be generated
    …om/rearrange?blogID=9430835&widgetType=Image&widgetId=Image2&action=editWidget…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1339. Info Line 1580, Column 70: entity was defined here
    …w.blogger.com/rearrange?blogID=9430835&widgetType=Text&widgetId=Text2&action=e…
  1340. Warning Line 2036, Column 96: reference not terminated by REFC delimiter
    …ogID=9430835&widgetType=Image&widgetId=Image2&action=editWidget&sectionId=side…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1341. Warning Line 2036, Column 96: reference to external entity in attribute value
    …ogID=9430835&widgetType=Image&widgetId=Image2&action=editWidget&sectionId=side…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1342. Error Line 2036, Column 96: reference to entity "widgetId" for which no system identifier could be generated
    …ogID=9430835&widgetType=Image&widgetId=Image2&action=editWidget&sectionId=side…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1343. Info Line 1580, Column 86: entity was defined here
    …arrange?blogID=9430835&widgetType=Text&widgetId=Text2&action=editWidget&sectio…
  1344. Warning Line 2036, Column 110: reference not terminated by REFC delimiter
    …idgetType=Image&widgetId=Image2&action=editWidget&sectionId=sidebar' onclick='…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1345. Warning Line 2036, Column 110: reference to external entity in attribute value
    …idgetType=Image&widgetId=Image2&action=editWidget&sectionId=sidebar' onclick='…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1346. Error Line 2036, Column 110: reference to entity "action" for which no system identifier could be generated
    …idgetType=Image&widgetId=Image2&action=editWidget&sectionId=sidebar' onclick='…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1347. Info Line 1580, Column 101: entity was defined here
    …9430835&widgetType=Text&widgetId=Text2&action=editWidget&sectionId=sidebar' on…
  1348. Warning Line 2036, Column 131: reference not terminated by REFC delimiter
    …tId=Image2&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1349. Warning Line 2036, Column 131: reference to external entity in attribute value
    …tId=Image2&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1350. Error Line 2036, Column 131: reference to entity "sectionId" for which no system identifier could be generated
    …tId=Image2&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1351. Info Line 1580, Column 119: entity was defined here
    …=Text&widgetId=Text2&action=editWidget&sectionId=sidebar' onclick='return _Wid…
  1352. Warning Line 2070, Column 81: reference not terminated by REFC delimiter
    …om/rearrange?blogID=9430835&widgetType=LinkList&widgetId=LinkList2&action=edit…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1353. Warning Line 2070, Column 81: reference to external entity in attribute value
    …om/rearrange?blogID=9430835&widgetType=LinkList&widgetId=LinkList2&action=edit…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1354. Error Line 2070, Column 81: reference to entity "widgetType" for which no system identifier could be generated
    …om/rearrange?blogID=9430835&widgetType=LinkList&widgetId=LinkList2&action=edit…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1355. Info Line 1580, Column 70: entity was defined here
    …w.blogger.com/rearrange?blogID=9430835&widgetType=Text&widgetId=Text2&action=e…
  1356. Warning Line 2070, Column 99: reference not terminated by REFC delimiter
    …D=9430835&widgetType=LinkList&widgetId=LinkList2&action=editWidget&sectionId=s…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1357. Warning Line 2070, Column 99: reference to external entity in attribute value
    …D=9430835&widgetType=LinkList&widgetId=LinkList2&action=editWidget&sectionId=s…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1358. Error Line 2070, Column 99: reference to entity "widgetId" for which no system identifier could be generated
    …D=9430835&widgetType=LinkList&widgetId=LinkList2&action=editWidget&sectionId=s…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1359. Info Line 1580, Column 86: entity was defined here
    …arrange?blogID=9430835&widgetType=Text&widgetId=Text2&action=editWidget&sectio…
  1360. Warning Line 2070, Column 116: reference not terminated by REFC delimiter
    …ype=LinkList&widgetId=LinkList2&action=editWidget&sectionId=sidebar' onclick='…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1361. Warning Line 2070, Column 116: reference to external entity in attribute value
    …ype=LinkList&widgetId=LinkList2&action=editWidget&sectionId=sidebar' onclick='…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1362. Error Line 2070, Column 116: reference to entity "action" for which no system identifier could be generated
    …ype=LinkList&widgetId=LinkList2&action=editWidget&sectionId=sidebar' onclick='…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1363. Info Line 1580, Column 101: entity was defined here
    …9430835&widgetType=Text&widgetId=Text2&action=editWidget&sectionId=sidebar' on…
  1364. Warning Line 2070, Column 137: reference not terminated by REFC delimiter
    …=LinkList2&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1365. Warning Line 2070, Column 137: reference to external entity in attribute value
    …=LinkList2&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1366. Error Line 2070, Column 137: reference to entity "sectionId" for which no system identifier could be generated
    …=LinkList2&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1367. Info Line 1580, Column 119: entity was defined here
    …=Text&widgetId=Text2&action=editWidget&sectionId=sidebar' onclick='return _Wid…
  1368. Warning Line 2095, Column 81: reference not terminated by REFC delimiter
    …om/rearrange?blogID=9430835&widgetType=AdSense&widgetId=AdSense3&action=editWi…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1369. Warning Line 2095, Column 81: reference to external entity in attribute value
    …om/rearrange?blogID=9430835&widgetType=AdSense&widgetId=AdSense3&action=editWi…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1370. Error Line 2095, Column 81: reference to entity "widgetType" for which no system identifier could be generated
    …om/rearrange?blogID=9430835&widgetType=AdSense&widgetId=AdSense3&action=editWi…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1371. Info Line 1580, Column 70: entity was defined here
    …w.blogger.com/rearrange?blogID=9430835&widgetType=Text&widgetId=Text2&action=e…
  1372. Warning Line 2095, Column 98: reference not terminated by REFC delimiter
    …ID=9430835&widgetType=AdSense&widgetId=AdSense3&action=editWidget&sectionId=si…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1373. Warning Line 2095, Column 98: reference to external entity in attribute value
    …ID=9430835&widgetType=AdSense&widgetId=AdSense3&action=editWidget&sectionId=si…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1374. Error Line 2095, Column 98: reference to entity "widgetId" for which no system identifier could be generated
    …ID=9430835&widgetType=AdSense&widgetId=AdSense3&action=editWidget&sectionId=si…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1375. Info Line 1580, Column 86: entity was defined here
    …arrange?blogID=9430835&widgetType=Text&widgetId=Text2&action=editWidget&sectio…
  1376. Warning Line 2095, Column 114: reference not terminated by REFC delimiter
    …tType=AdSense&widgetId=AdSense3&action=editWidget&sectionId=sidebar' onclick='…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1377. Warning Line 2095, Column 114: reference to external entity in attribute value
    …tType=AdSense&widgetId=AdSense3&action=editWidget&sectionId=sidebar' onclick='…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1378. Error Line 2095, Column 114: reference to entity "action" for which no system identifier could be generated
    …tType=AdSense&widgetId=AdSense3&action=editWidget&sectionId=sidebar' onclick='…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1379. Info Line 1580, Column 101: entity was defined here
    …9430835&widgetType=Text&widgetId=Text2&action=editWidget&sectionId=sidebar' on…
  1380. Warning Line 2095, Column 135: reference not terminated by REFC delimiter
    …d=AdSense3&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1381. Warning Line 2095, Column 135: reference to external entity in attribute value
    …d=AdSense3&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1382. Error Line 2095, Column 135: reference to entity "sectionId" for which no system identifier could be generated
    …d=AdSense3&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1383. Info Line 1580, Column 119: entity was defined here
    …=Text&widgetId=Text2&action=editWidget&sectionId=sidebar' onclick='return _Wid…
  1384. Error Line 2110, Column 102: required attribute "alt" not specified
    …ropdown-arrow' src='https://img2.blogblog.com/img/widgets/arrow_dropdown.gif'/>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  1385. Error Line 2116, Column 73: required attribute "alt" not specified
    <img src='https://img1.blogblog.com/img/widgets/subscribe-netvibes.png'/>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  1386. Error Line 2119, Column 70: required attribute "alt" not specified
    <img src='https://img1.blogblog.com/img/widgets/subscribe-yahoo.png'/>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  1387. Error Line 2122, Column 94: required attribute "alt" not specified
    …middle' class='feed-icon' src='https://img1.blogblog.com/img/icon_feed12.png'/>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  1388. Error Line 2132, Column 102: required attribute "alt" not specified
    …ropdown-arrow' src='https://img2.blogblog.com/img/widgets/arrow_dropdown.gif'/>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  1389. Error Line 2146, Column 102: required attribute "alt" not specified
    …ropdown-arrow' src='https://img2.blogblog.com/img/widgets/arrow_dropdown.gif'/>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  1390. Error Line 2152, Column 73: required attribute "alt" not specified
    <img src='https://img1.blogblog.com/img/widgets/subscribe-netvibes.png'/>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  1391. Error Line 2155, Column 70: required attribute "alt" not specified
    <img src='https://img1.blogblog.com/img/widgets/subscribe-yahoo.png'/>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  1392. Error Line 2158, Column 94: required attribute "alt" not specified
    …middle' class='feed-icon' src='https://img1.blogblog.com/img/icon_feed12.png'/>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  1393. Error Line 2168, Column 102: required attribute "alt" not specified
    …ropdown-arrow' src='https://img2.blogblog.com/img/widgets/arrow_dropdown.gif'/>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  1394. Warning Line 2184, Column 81: reference not terminated by REFC delimiter
    …om/rearrange?blogID=9430835&widgetType=Subscribe&widgetId=Subscribe3&action=ed…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1395. Warning Line 2184, Column 81: reference to external entity in attribute value
    …om/rearrange?blogID=9430835&widgetType=Subscribe&widgetId=Subscribe3&action=ed…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1396. Error Line 2184, Column 81: reference to entity "widgetType" for which no system identifier could be generated
    …om/rearrange?blogID=9430835&widgetType=Subscribe&widgetId=Subscribe3&action=ed…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1397. Info Line 1580, Column 70: entity was defined here
    …w.blogger.com/rearrange?blogID=9430835&widgetType=Text&widgetId=Text2&action=e…
  1398. Warning Line 2184, Column 100: reference not terminated by REFC delimiter
    …=9430835&widgetType=Subscribe&widgetId=Subscribe3&action=editWidget&sectionId=…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1399. Warning Line 2184, Column 100: reference to external entity in attribute value
    …=9430835&widgetType=Subscribe&widgetId=Subscribe3&action=editWidget&sectionId=…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1400. Error Line 2184, Column 100: reference to entity "widgetId" for which no system identifier could be generated
    …=9430835&widgetType=Subscribe&widgetId=Subscribe3&action=editWidget&sectionId=…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1401. Info Line 1580, Column 86: entity was defined here
    …arrange?blogID=9430835&widgetType=Text&widgetId=Text2&action=editWidget&sectio…
  1402. Warning Line 2184, Column 118: reference not terminated by REFC delimiter
    …e=Subscribe&widgetId=Subscribe3&action=editWidget&sectionId=sidebar' onclick='…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1403. Warning Line 2184, Column 118: reference to external entity in attribute value
    …e=Subscribe&widgetId=Subscribe3&action=editWidget&sectionId=sidebar' onclick='…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1404. Error Line 2184, Column 118: reference to entity "action" for which no system identifier could be generated
    …e=Subscribe&widgetId=Subscribe3&action=editWidget&sectionId=sidebar' onclick='…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1405. Info Line 1580, Column 101: entity was defined here
    …9430835&widgetType=Text&widgetId=Text2&action=editWidget&sectionId=sidebar' on…
  1406. Warning Line 2184, Column 139: reference not terminated by REFC delimiter
    …Subscribe3&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1407. Warning Line 2184, Column 139: reference to external entity in attribute value
    …Subscribe3&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1408. Error Line 2184, Column 139: reference to entity "sectionId" for which no system identifier could be generated
    …Subscribe3&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1409. Info Line 1580, Column 119: entity was defined here
    …=Text&widgetId=Text2&action=editWidget&sectionId=sidebar' onclick='return _Wid…
  1410. Warning Line 2200, Column 81: reference not terminated by REFC delimiter
    …om/rearrange?blogID=9430835&widgetType=Image&widgetId=Image4&action=editWidget…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1411. Warning Line 2200, Column 81: reference to external entity in attribute value
    …om/rearrange?blogID=9430835&widgetType=Image&widgetId=Image4&action=editWidget…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1412. Error Line 2200, Column 81: reference to entity "widgetType" for which no system identifier could be generated
    …om/rearrange?blogID=9430835&widgetType=Image&widgetId=Image4&action=editWidget…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1413. Info Line 1580, Column 70: entity was defined here
    …w.blogger.com/rearrange?blogID=9430835&widgetType=Text&widgetId=Text2&action=e…
  1414. Warning Line 2200, Column 96: reference not terminated by REFC delimiter
    …ogID=9430835&widgetType=Image&widgetId=Image4&action=editWidget&sectionId=side…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1415. Warning Line 2200, Column 96: reference to external entity in attribute value
    …ogID=9430835&widgetType=Image&widgetId=Image4&action=editWidget&sectionId=side…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1416. Error Line 2200, Column 96: reference to entity "widgetId" for which no system identifier could be generated
    …ogID=9430835&widgetType=Image&widgetId=Image4&action=editWidget&sectionId=side…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1417. Info Line 1580, Column 86: entity was defined here
    …arrange?blogID=9430835&widgetType=Text&widgetId=Text2&action=editWidget&sectio…
  1418. Warning Line 2200, Column 110: reference not terminated by REFC delimiter
    …idgetType=Image&widgetId=Image4&action=editWidget&sectionId=sidebar' onclick='…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1419. Warning Line 2200, Column 110: reference to external entity in attribute value
    …idgetType=Image&widgetId=Image4&action=editWidget&sectionId=sidebar' onclick='…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1420. Error Line 2200, Column 110: reference to entity "action" for which no system identifier could be generated
    …idgetType=Image&widgetId=Image4&action=editWidget&sectionId=sidebar' onclick='…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1421. Info Line 1580, Column 101: entity was defined here
    …9430835&widgetType=Text&widgetId=Text2&action=editWidget&sectionId=sidebar' on…
  1422. Warning Line 2200, Column 131: reference not terminated by REFC delimiter
    …tId=Image4&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1423. Warning Line 2200, Column 131: reference to external entity in attribute value
    …tId=Image4&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1424. Error Line 2200, Column 131: reference to entity "sectionId" for which no system identifier could be generated
    …tId=Image4&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1425. Info Line 1580, Column 119: entity was defined here
    …=Text&widgetId=Text2&action=editWidget&sectionId=sidebar' onclick='return _Wid…
  1426. Error Line 2214, Column 102: required attribute "alt" not specified
    …ropdown-arrow' src='https://img2.blogblog.com/img/widgets/arrow_dropdown.gif'/>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  1427. Error Line 2220, Column 73: required attribute "alt" not specified
    <img src='https://img1.blogblog.com/img/widgets/subscribe-netvibes.png'/>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  1428. Error Line 2223, Column 70: required attribute "alt" not specified
    <img src='https://img1.blogblog.com/img/widgets/subscribe-yahoo.png'/>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  1429. Error Line 2226, Column 94: required attribute "alt" not specified
    …middle' class='feed-icon' src='https://img1.blogblog.com/img/icon_feed12.png'/>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  1430. Error Line 2236, Column 102: required attribute "alt" not specified
    …ropdown-arrow' src='https://img2.blogblog.com/img/widgets/arrow_dropdown.gif'/>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  1431. Error Line 2250, Column 102: required attribute "alt" not specified
    …ropdown-arrow' src='https://img2.blogblog.com/img/widgets/arrow_dropdown.gif'/>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  1432. Error Line 2256, Column 73: required attribute "alt" not specified
    <img src='https://img1.blogblog.com/img/widgets/subscribe-netvibes.png'/>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  1433. Error Line 2259, Column 70: required attribute "alt" not specified
    <img src='https://img1.blogblog.com/img/widgets/subscribe-yahoo.png'/>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  1434. Error Line 2262, Column 94: required attribute "alt" not specified
    …middle' class='feed-icon' src='https://img1.blogblog.com/img/icon_feed12.png'/>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  1435. Error Line 2272, Column 102: required attribute "alt" not specified
    …ropdown-arrow' src='https://img2.blogblog.com/img/widgets/arrow_dropdown.gif'/>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  1436. Warning Line 2288, Column 81: reference not terminated by REFC delimiter
    …om/rearrange?blogID=9430835&widgetType=Subscribe&widgetId=Subscribe2&action=ed…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1437. Warning Line 2288, Column 81: reference to external entity in attribute value
    …om/rearrange?blogID=9430835&widgetType=Subscribe&widgetId=Subscribe2&action=ed…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1438. Error Line 2288, Column 81: reference to entity "widgetType" for which no system identifier could be generated
    …om/rearrange?blogID=9430835&widgetType=Subscribe&widgetId=Subscribe2&action=ed…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1439. Info Line 1580, Column 70: entity was defined here
    …w.blogger.com/rearrange?blogID=9430835&widgetType=Text&widgetId=Text2&action=e…
  1440. Warning Line 2288, Column 100: reference not terminated by REFC delimiter
    …=9430835&widgetType=Subscribe&widgetId=Subscribe2&action=editWidget&sectionId=…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1441. Warning Line 2288, Column 100: reference to external entity in attribute value
    …=9430835&widgetType=Subscribe&widgetId=Subscribe2&action=editWidget&sectionId=…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1442. Error Line 2288, Column 100: reference to entity "widgetId" for which no system identifier could be generated
    …=9430835&widgetType=Subscribe&widgetId=Subscribe2&action=editWidget&sectionId=…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1443. Info Line 1580, Column 86: entity was defined here
    …arrange?blogID=9430835&widgetType=Text&widgetId=Text2&action=editWidget&sectio…
  1444. Warning Line 2288, Column 118: reference not terminated by REFC delimiter
    …e=Subscribe&widgetId=Subscribe2&action=editWidget&sectionId=sidebar' onclick='…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1445. Warning Line 2288, Column 118: reference to external entity in attribute value
    …e=Subscribe&widgetId=Subscribe2&action=editWidget&sectionId=sidebar' onclick='…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1446. Error Line 2288, Column 118: reference to entity "action" for which no system identifier could be generated
    …e=Subscribe&widgetId=Subscribe2&action=editWidget&sectionId=sidebar' onclick='…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1447. Info Line 1580, Column 101: entity was defined here
    …9430835&widgetType=Text&widgetId=Text2&action=editWidget&sectionId=sidebar' on…
  1448. Warning Line 2288, Column 139: reference not terminated by REFC delimiter
    …Subscribe2&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1449. Warning Line 2288, Column 139: reference to external entity in attribute value
    …Subscribe2&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1450. Error Line 2288, Column 139: reference to entity "sectionId" for which no system identifier could be generated
    …Subscribe2&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1451. Info Line 1580, Column 119: entity was defined here
    …=Text&widgetId=Text2&action=editWidget&sectionId=sidebar' onclick='return _Wid…
  1452. Warning Line 2306, Column 81: reference not terminated by REFC delimiter
    …om/rearrange?blogID=9430835&widgetType=Image&widgetId=Image5&action=editWidget…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1453. Warning Line 2306, Column 81: reference to external entity in attribute value
    …om/rearrange?blogID=9430835&widgetType=Image&widgetId=Image5&action=editWidget…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1454. Error Line 2306, Column 81: reference to entity "widgetType" for which no system identifier could be generated
    …om/rearrange?blogID=9430835&widgetType=Image&widgetId=Image5&action=editWidget…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1455. Info Line 1580, Column 70: entity was defined here
    …w.blogger.com/rearrange?blogID=9430835&widgetType=Text&widgetId=Text2&action=e…
  1456. Warning Line 2306, Column 96: reference not terminated by REFC delimiter
    …ogID=9430835&widgetType=Image&widgetId=Image5&action=editWidget&sectionId=side…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1457. Warning Line 2306, Column 96: reference to external entity in attribute value
    …ogID=9430835&widgetType=Image&widgetId=Image5&action=editWidget&sectionId=side…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1458. Error Line 2306, Column 96: reference to entity "widgetId" for which no system identifier could be generated
    …ogID=9430835&widgetType=Image&widgetId=Image5&action=editWidget&sectionId=side…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1459. Info Line 1580, Column 86: entity was defined here
    …arrange?blogID=9430835&widgetType=Text&widgetId=Text2&action=editWidget&sectio…
  1460. Warning Line 2306, Column 110: reference not terminated by REFC delimiter
    …idgetType=Image&widgetId=Image5&action=editWidget&sectionId=sidebar' onclick='…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1461. Warning Line 2306, Column 110: reference to external entity in attribute value
    …idgetType=Image&widgetId=Image5&action=editWidget&sectionId=sidebar' onclick='…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1462. Error Line 2306, Column 110: reference to entity "action" for which no system identifier could be generated
    …idgetType=Image&widgetId=Image5&action=editWidget&sectionId=sidebar' onclick='…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1463. Info Line 1580, Column 101: entity was defined here
    …9430835&widgetType=Text&widgetId=Text2&action=editWidget&sectionId=sidebar' on…
  1464. Warning Line 2306, Column 131: reference not terminated by REFC delimiter
    …tId=Image5&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1465. Warning Line 2306, Column 131: reference to external entity in attribute value
    …tId=Image5&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1466. Error Line 2306, Column 131: reference to entity "sectionId" for which no system identifier could be generated
    …tId=Image5&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1467. Info Line 1580, Column 119: entity was defined here
    …=Text&widgetId=Text2&action=editWidget&sectionId=sidebar' onclick='return _Wid…
  1468. Warning Line 10246, Column 81: reference not terminated by REFC delimiter
    …om/rearrange?blogID=9430835&widgetType=BlogArchive&widgetId=BlogArchive1&actio…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1469. Warning Line 10246, Column 81: reference to external entity in attribute value
    …om/rearrange?blogID=9430835&widgetType=BlogArchive&widgetId=BlogArchive1&actio…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1470. Error Line 10246, Column 81: reference to entity "widgetType" for which no system identifier could be generated
    …om/rearrange?blogID=9430835&widgetType=BlogArchive&widgetId=BlogArchive1&actio…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1471. Info Line 1580, Column 70: entity was defined here
    …w.blogger.com/rearrange?blogID=9430835&widgetType=Text&widgetId=Text2&action=e…
  1472. Warning Line 10246, Column 102: reference not terminated by REFC delimiter
    …430835&widgetType=BlogArchive&widgetId=BlogArchive1&action=editWidget&sectionI…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1473. Warning Line 10246, Column 102: reference to external entity in attribute value
    …430835&widgetType=BlogArchive&widgetId=BlogArchive1&action=editWidget&sectionI…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1474. Error Line 10246, Column 102: reference to entity "widgetId" for which no system identifier could be generated
    …430835&widgetType=BlogArchive&widgetId=BlogArchive1&action=editWidget&sectionI…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1475. Info Line 1580, Column 86: entity was defined here
    …arrange?blogID=9430835&widgetType=Text&widgetId=Text2&action=editWidget&sectio…
  1476. Warning Line 10246, Column 122: reference not terminated by REFC delimiter
    …ogArchive&widgetId=BlogArchive1&action=editWidget&sectionId=sidebar' onclick='…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1477. Warning Line 10246, Column 122: reference to external entity in attribute value
    …ogArchive&widgetId=BlogArchive1&action=editWidget&sectionId=sidebar' onclick='…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1478. Error Line 10246, Column 122: reference to entity "action" for which no system identifier could be generated
    …ogArchive&widgetId=BlogArchive1&action=editWidget&sectionId=sidebar' onclick='…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1479. Info Line 1580, Column 101: entity was defined here
    …9430835&widgetType=Text&widgetId=Text2&action=editWidget&sectionId=sidebar' on…
  1480. Warning Line 10246, Column 143: reference not terminated by REFC delimiter
    …ogArchive1&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1481. Warning Line 10246, Column 143: reference to external entity in attribute value
    …ogArchive1&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1482. Error Line 10246, Column 143: reference to entity "sectionId" for which no system identifier could be generated
    …ogArchive1&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1483. Info Line 1580, Column 119: entity was defined here
    …=Text&widgetId=Text2&action=editWidget&sectionId=sidebar' onclick='return _Wid…
  1484. Warning Line 10265, Column 81: reference not terminated by REFC delimiter
    …om/rearrange?blogID=9430835&widgetType=Image&widgetId=Image1&action=editWidget…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1485. Warning Line 10265, Column 81: reference to external entity in attribute value
    …om/rearrange?blogID=9430835&widgetType=Image&widgetId=Image1&action=editWidget…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1486. Error Line 10265, Column 81: reference to entity "widgetType" for which no system identifier could be generated
    …om/rearrange?blogID=9430835&widgetType=Image&widgetId=Image1&action=editWidget…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1487. Info Line 1580, Column 70: entity was defined here
    …w.blogger.com/rearrange?blogID=9430835&widgetType=Text&widgetId=Text2&action=e…
  1488. Warning Line 10265, Column 96: reference not terminated by REFC delimiter
    …ogID=9430835&widgetType=Image&widgetId=Image1&action=editWidget&sectionId=side…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1489. Warning Line 10265, Column 96: reference to external entity in attribute value
    …ogID=9430835&widgetType=Image&widgetId=Image1&action=editWidget&sectionId=side…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1490. Error Line 10265, Column 96: reference to entity "widgetId" for which no system identifier could be generated
    …ogID=9430835&widgetType=Image&widgetId=Image1&action=editWidget&sectionId=side…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1491. Info Line 1580, Column 86: entity was defined here
    …arrange?blogID=9430835&widgetType=Text&widgetId=Text2&action=editWidget&sectio…
  1492. Warning Line 10265, Column 110: reference not terminated by REFC delimiter
    …idgetType=Image&widgetId=Image1&action=editWidget&sectionId=sidebar' onclick='…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1493. Warning Line 10265, Column 110: reference to external entity in attribute value
    …idgetType=Image&widgetId=Image1&action=editWidget&sectionId=sidebar' onclick='…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1494. Error Line 10265, Column 110: reference to entity "action" for which no system identifier could be generated
    …idgetType=Image&widgetId=Image1&action=editWidget&sectionId=sidebar' onclick='…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1495. Info Line 1580, Column 101: entity was defined here
    …9430835&widgetType=Text&widgetId=Text2&action=editWidget&sectionId=sidebar' on…
  1496. Warning Line 10265, Column 131: reference not terminated by REFC delimiter
    …tId=Image1&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1497. Warning Line 10265, Column 131: reference to external entity in attribute value
    …tId=Image1&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1498. Error Line 10265, Column 131: reference to entity "sectionId" for which no system identifier could be generated
    …tId=Image1&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1499. Info Line 1580, Column 119: entity was defined here
    …=Text&widgetId=Text2&action=editWidget&sectionId=sidebar' onclick='return _Wid…
  1500. Warning Line 11739, Column 81: reference not terminated by REFC delimiter
    …om/rearrange?blogID=9430835&widgetType=Label&widgetId=Label1&action=editWidget…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1501. Warning Line 11739, Column 81: reference to external entity in attribute value
    …om/rearrange?blogID=9430835&widgetType=Label&widgetId=Label1&action=editWidget…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1502. Error Line 11739, Column 81: reference to entity "widgetType" for which no system identifier could be generated
    …om/rearrange?blogID=9430835&widgetType=Label&widgetId=Label1&action=editWidget…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1503. Info Line 1580, Column 70: entity was defined here
    …w.blogger.com/rearrange?blogID=9430835&widgetType=Text&widgetId=Text2&action=e…
  1504. Warning Line 11739, Column 96: reference not terminated by REFC delimiter
    …ogID=9430835&widgetType=Label&widgetId=Label1&action=editWidget&sectionId=side…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1505. Warning Line 11739, Column 96: reference to external entity in attribute value
    …ogID=9430835&widgetType=Label&widgetId=Label1&action=editWidget&sectionId=side…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1506. Error Line 11739, Column 96: reference to entity "widgetId" for which no system identifier could be generated
    …ogID=9430835&widgetType=Label&widgetId=Label1&action=editWidget&sectionId=side…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1507. Info Line 1580, Column 86: entity was defined here
    …arrange?blogID=9430835&widgetType=Text&widgetId=Text2&action=editWidget&sectio…
  1508. Warning Line 11739, Column 110: reference not terminated by REFC delimiter
    …idgetType=Label&widgetId=Label1&action=editWidget&sectionId=sidebar' onclick='…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1509. Warning Line 11739, Column 110: reference to external entity in attribute value
    …idgetType=Label&widgetId=Label1&action=editWidget&sectionId=sidebar' onclick='…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1510. Error Line 11739, Column 110: reference to entity "action" for which no system identifier could be generated
    …idgetType=Label&widgetId=Label1&action=editWidget&sectionId=sidebar' onclick='…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1511. Info Line 1580, Column 101: entity was defined here
    …9430835&widgetType=Text&widgetId=Text2&action=editWidget&sectionId=sidebar' on…
  1512. Warning Line 11739, Column 131: reference not terminated by REFC delimiter
    …tId=Label1&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1513. Warning Line 11739, Column 131: reference to external entity in attribute value
    …tId=Label1&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1514. Error Line 11739, Column 131: reference to entity "sectionId" for which no system identifier could be generated
    …tId=Label1&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1515. Info Line 1580, Column 119: entity was defined here
    …=Text&widgetId=Text2&action=editWidget&sectionId=sidebar' onclick='return _Wid…
  1516. Warning Line 11768, Column 81: reference not terminated by REFC delimiter
    …om/rearrange?blogID=9430835&widgetType=AdSense&widgetId=AdSense1&action=editWi…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1517. Warning Line 11768, Column 81: reference to external entity in attribute value
    …om/rearrange?blogID=9430835&widgetType=AdSense&widgetId=AdSense1&action=editWi…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1518. Error Line 11768, Column 81: reference to entity "widgetType" for which no system identifier could be generated
    …om/rearrange?blogID=9430835&widgetType=AdSense&widgetId=AdSense1&action=editWi…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1519. Info Line 1580, Column 70: entity was defined here
    …w.blogger.com/rearrange?blogID=9430835&widgetType=Text&widgetId=Text2&action=e…
  1520. Warning Line 11768, Column 98: reference not terminated by REFC delimiter
    …ID=9430835&widgetType=AdSense&widgetId=AdSense1&action=editWidget&sectionId=si…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1521. Warning Line 11768, Column 98: reference to external entity in attribute value
    …ID=9430835&widgetType=AdSense&widgetId=AdSense1&action=editWidget&sectionId=si…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1522. Error Line 11768, Column 98: reference to entity "widgetId" for which no system identifier could be generated
    …ID=9430835&widgetType=AdSense&widgetId=AdSense1&action=editWidget&sectionId=si…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1523. Info Line 1580, Column 86: entity was defined here
    …arrange?blogID=9430835&widgetType=Text&widgetId=Text2&action=editWidget&sectio…
  1524. Warning Line 11768, Column 114: reference not terminated by REFC delimiter
    …tType=AdSense&widgetId=AdSense1&action=editWidget&sectionId=sidebar' onclick='…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1525. Warning Line 11768, Column 114: reference to external entity in attribute value
    …tType=AdSense&widgetId=AdSense1&action=editWidget&sectionId=sidebar' onclick='…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1526. Error Line 11768, Column 114: reference to entity "action" for which no system identifier could be generated
    …tType=AdSense&widgetId=AdSense1&action=editWidget&sectionId=sidebar' onclick='…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1527. Info Line 1580, Column 101: entity was defined here
    …9430835&widgetType=Text&widgetId=Text2&action=editWidget&sectionId=sidebar' on…
  1528. Warning Line 11768, Column 135: reference not terminated by REFC delimiter
    …d=AdSense1&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1529. Warning Line 11768, Column 135: reference to external entity in attribute value
    …d=AdSense1&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1530. Error Line 11768, Column 135: reference to entity "sectionId" for which no system identifier could be generated
    …d=AdSense1&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1531. Info Line 1580, Column 119: entity was defined here
    …=Text&widgetId=Text2&action=editWidget&sectionId=sidebar' onclick='return _Wid…
  1532. Error Line 11779, Column 249: there is no attribute "target"
    …ow", "scrollbars=yes,width=550,height=520"); return true' target='popupwindow'>

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  1533. Error Line 11783, Column 65: there is no attribute "placeholder"
    …low-by-email-address' name='email' placeholder='Email address...' type='text'/>

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  1534. Error Line 11785, Column 11: there is no attribute "width"
    <td width='64px'>

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  1535. Error Line 11790, Column 64: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    <input name='uri' type='hidden' value='SteveSailersIsteveBlog'/>

    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 "<a>", "<span>", or "<font>").

  1536. Error Line 11791, Column 47: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    <input name='loc' type='hidden' value='en_US'/>

    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 "<a>", "<span>", or "<font>").

  1537. Error Line 11796, Column 19: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div class='clear'></div>

    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 "<a>", "<span>", or "<font>").

  1538. Warning Line 11799, Column 81: reference not terminated by REFC delimiter
    …om/rearrange?blogID=9430835&widgetType=FollowByEmail&widgetId=FollowByEmail1&a…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1539. Warning Line 11799, Column 81: reference to external entity in attribute value
    …om/rearrange?blogID=9430835&widgetType=FollowByEmail&widgetId=FollowByEmail1&a…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1540. Error Line 11799, Column 81: reference to entity "widgetType" for which no system identifier could be generated
    …om/rearrange?blogID=9430835&widgetType=FollowByEmail&widgetId=FollowByEmail1&a…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1541. Info Line 1580, Column 70: entity was defined here
    …w.blogger.com/rearrange?blogID=9430835&widgetType=Text&widgetId=Text2&action=e…
  1542. Warning Line 11799, Column 104: reference not terminated by REFC delimiter
    …0835&widgetType=FollowByEmail&widgetId=FollowByEmail1&action=editWidget&sectio…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1543. Warning Line 11799, Column 104: reference to external entity in attribute value
    …0835&widgetType=FollowByEmail&widgetId=FollowByEmail1&action=editWidget&sectio…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1544. Error Line 11799, Column 104: reference to entity "widgetId" for which no system identifier could be generated
    …0835&widgetType=FollowByEmail&widgetId=FollowByEmail1&action=editWidget&sectio…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1545. Info Line 1580, Column 86: entity was defined here
    …arrange?blogID=9430835&widgetType=Text&widgetId=Text2&action=editWidget&sectio…
  1546. Warning Line 11799, Column 126: reference not terminated by REFC delimiter
    …ByEmail&widgetId=FollowByEmail1&action=editWidget&sectionId=sidebar' onclick='…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1547. Warning Line 11799, Column 126: reference to external entity in attribute value
    …ByEmail&widgetId=FollowByEmail1&action=editWidget&sectionId=sidebar' onclick='…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1548. Error Line 11799, Column 126: reference to entity "action" for which no system identifier could be generated
    …ByEmail&widgetId=FollowByEmail1&action=editWidget&sectionId=sidebar' onclick='…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1549. Info Line 1580, Column 101: entity was defined here
    …9430835&widgetType=Text&widgetId=Text2&action=editWidget&sectionId=sidebar' on…
  1550. Warning Line 11799, Column 147: reference not terminated by REFC delimiter
    …owByEmail1&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1551. Warning Line 11799, Column 147: reference to external entity in attribute value
    …owByEmail1&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1552. Error Line 11799, Column 147: reference to entity "sectionId" for which no system identifier could be generated
    …owByEmail1&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1553. Info Line 1580, Column 119: entity was defined here
    …=Text&widgetId=Text2&action=editWidget&sectionId=sidebar' onclick='return _Wid…
  1554. Error Line 11804, Column 19: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div class='clear'></div>

    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 "<a>", "<span>", or "<font>").

  1555. Error Line 11811, Column 57: an attribute specification must start with a name or name token
              document.write('<script type="text/javascript"' +

    An attribute name (and some attribute values) must start with one of a restricted set of characters. This error usually indicates that you have failed to add a closing quotation mark on a previous attribute value (so the attribute value looks like the start of a new attribute) or have used an attribute that is not defined (usually a typo in a common attribute name).

  1556. Error Line 11811, Column 57: document type does not allow element "script" here
              document.write('<script type="text/javascript"' +

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  1557. Error Line 11813, Column 25: delimiter "'" invalid: only S separators and TAGC allowed here
                      '</scr' + 'ipt>');

  1558. Error Line 11813, Column 25: end tag for element "scr" which is not open
                      '</scr' + 'ipt>');

    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.

  1559. Error Line 11816, Column 31: document type does not allow element "script" here
    <script type="text/javascript">

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  1560. Error Line 11838, Column 31: document type does not allow element "script" here
    <script type="text/javascript">

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  1561. Error Line 11855, Column 752: element "iframe" undefined
    …play: block" height="200" id="sidebar-gadget4" name="sidebar-gadget4"></iframe>

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  1562. Error Line 11856, Column 31: document type does not allow element "script" here
    <script type="text/javascript">

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  1563. Error Line 11860, Column 6: end tag for "script" omitted, but OMITTAG NO was specified
    </div>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  1564. Info Line 11809, Column 1: start tag was here
    <script type="text/javascript">
  1565. Warning Line 11864, Column 81: reference not terminated by REFC delimiter
    …om/rearrange?blogID=9430835&widgetType=Gadget&widgetId=Gadget4&action=editWidg…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1566. Warning Line 11864, Column 81: reference to external entity in attribute value
    …om/rearrange?blogID=9430835&widgetType=Gadget&widgetId=Gadget4&action=editWidg…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1567. Error Line 11864, Column 81: reference to entity "widgetType" for which no system identifier could be generated
    …om/rearrange?blogID=9430835&widgetType=Gadget&widgetId=Gadget4&action=editWidg…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1568. Info Line 1580, Column 70: entity was defined here
    …w.blogger.com/rearrange?blogID=9430835&widgetType=Text&widgetId=Text2&action=e…
  1569. Warning Line 11864, Column 97: reference not terminated by REFC delimiter
    …gID=9430835&widgetType=Gadget&widgetId=Gadget4&action=editWidget&sectionId=sid…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1570. Warning Line 11864, Column 97: reference to external entity in attribute value
    …gID=9430835&widgetType=Gadget&widgetId=Gadget4&action=editWidget&sectionId=sid…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1571. Error Line 11864, Column 97: reference to entity "widgetId" for which no system identifier could be generated
    …gID=9430835&widgetType=Gadget&widgetId=Gadget4&action=editWidget&sectionId=sid…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1572. Info Line 1580, Column 86: entity was defined here
    …arrange?blogID=9430835&widgetType=Text&widgetId=Text2&action=editWidget&sectio…
  1573. Warning Line 11864, Column 112: reference not terminated by REFC delimiter
    …getType=Gadget&widgetId=Gadget4&action=editWidget&sectionId=sidebar' onclick='…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1574. Warning Line 11864, Column 112: reference to external entity in attribute value
    …getType=Gadget&widgetId=Gadget4&action=editWidget&sectionId=sidebar' onclick='…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1575. Error Line 11864, Column 112: reference to entity "action" for which no system identifier could be generated
    …getType=Gadget&widgetId=Gadget4&action=editWidget&sectionId=sidebar' onclick='…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1576. Info Line 1580, Column 101: entity was defined here
    …9430835&widgetType=Text&widgetId=Text2&action=editWidget&sectionId=sidebar' on…
  1577. Warning Line 11864, Column 133: reference not terminated by REFC delimiter
    …Id=Gadget4&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1578. Warning Line 11864, Column 133: reference to external entity in attribute value
    …Id=Gadget4&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1579. Error Line 11864, Column 133: reference to entity "sectionId" for which no system identifier could be generated
    …Id=Gadget4&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1580. Info Line 1580, Column 119: entity was defined here
    …=Text&widgetId=Text2&action=editWidget&sectionId=sidebar' onclick='return _Wid…
  1581. Warning Line 11958, Column 81: reference not terminated by REFC delimiter
    …om/rearrange?blogID=9430835&widgetType=PopularPosts&widgetId=PopularPosts1&act…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1582. Warning Line 11958, Column 81: reference to external entity in attribute value
    …om/rearrange?blogID=9430835&widgetType=PopularPosts&widgetId=PopularPosts1&act…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1583. Error Line 11958, Column 81: reference to entity "widgetType" for which no system identifier could be generated
    …om/rearrange?blogID=9430835&widgetType=PopularPosts&widgetId=PopularPosts1&act…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1584. Info Line 1580, Column 70: entity was defined here
    …w.blogger.com/rearrange?blogID=9430835&widgetType=Text&widgetId=Text2&action=e…
  1585. Warning Line 11958, Column 103: reference not terminated by REFC delimiter
    …30835&widgetType=PopularPosts&widgetId=PopularPosts1&action=editWidget&section…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1586. Warning Line 11958, Column 103: reference to external entity in attribute value
    …30835&widgetType=PopularPosts&widgetId=PopularPosts1&action=editWidget&section…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1587. Error Line 11958, Column 103: reference to entity "widgetId" for which no system identifier could be generated
    …30835&widgetType=PopularPosts&widgetId=PopularPosts1&action=editWidget&section…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1588. Info Line 1580, Column 86: entity was defined here
    …arrange?blogID=9430835&widgetType=Text&widgetId=Text2&action=editWidget&sectio…
  1589. Warning Line 11958, Column 124: reference not terminated by REFC delimiter
    …larPosts&widgetId=PopularPosts1&action=editWidget&sectionId=sidebar' onclick='…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1590. Warning Line 11958, Column 124: reference to external entity in attribute value
    …larPosts&widgetId=PopularPosts1&action=editWidget&sectionId=sidebar' onclick='…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1591. Error Line 11958, Column 124: reference to entity "action" for which no system identifier could be generated
    …larPosts&widgetId=PopularPosts1&action=editWidget&sectionId=sidebar' onclick='…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1592. Info Line 1580, Column 101: entity was defined here
    …9430835&widgetType=Text&widgetId=Text2&action=editWidget&sectionId=sidebar' on…
  1593. Warning Line 11958, Column 145: reference not terminated by REFC delimiter
    …ularPosts1&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1594. Warning Line 11958, Column 145: reference to external entity in attribute value
    …ularPosts1&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1595. Error Line 11958, Column 145: reference to entity "sectionId" for which no system identifier could be generated
    …ularPosts1&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1596. Info Line 1580, Column 119: entity was defined here
    …=Text&widgetId=Text2&action=editWidget&sectionId=sidebar' onclick='return _Wid…
  1597. Warning Line 11973, Column 81: reference not terminated by REFC delimiter
    …om/rearrange?blogID=9430835&widgetType=HTML&widgetId=HTML3&action=editWidget&s…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1598. Warning Line 11973, Column 81: reference to external entity in attribute value
    …om/rearrange?blogID=9430835&widgetType=HTML&widgetId=HTML3&action=editWidget&s…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1599. Error Line 11973, Column 81: reference to entity "widgetType" for which no system identifier could be generated
    …om/rearrange?blogID=9430835&widgetType=HTML&widgetId=HTML3&action=editWidget&s…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1600. Info Line 1580, Column 70: entity was defined here
    …w.blogger.com/rearrange?blogID=9430835&widgetType=Text&widgetId=Text2&action=e…
  1601. Warning Line 11973, Column 95: reference not terminated by REFC delimiter
    …logID=9430835&widgetType=HTML&widgetId=HTML3&action=editWidget&sectionId=sideb…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1602. Warning Line 11973, Column 95: reference to external entity in attribute value
    …logID=9430835&widgetType=HTML&widgetId=HTML3&action=editWidget&sectionId=sideb…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1603. Error Line 11973, Column 95: reference to entity "widgetId" for which no system identifier could be generated
    …logID=9430835&widgetType=HTML&widgetId=HTML3&action=editWidget&sectionId=sideb…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1604. Info Line 1580, Column 86: entity was defined here
    …arrange?blogID=9430835&widgetType=Text&widgetId=Text2&action=editWidget&sectio…
  1605. Warning Line 11973, Column 108: reference not terminated by REFC delimiter
    …&widgetType=HTML&widgetId=HTML3&action=editWidget&sectionId=sidebar' onclick='…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1606. Warning Line 11973, Column 108: reference to external entity in attribute value
    …&widgetType=HTML&widgetId=HTML3&action=editWidget&sectionId=sidebar' onclick='…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1607. Error Line 11973, Column 108: reference to entity "action" for which no system identifier could be generated
    …&widgetType=HTML&widgetId=HTML3&action=editWidget&sectionId=sidebar' onclick='…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1608. Info Line 1580, Column 101: entity was defined here
    …9430835&widgetType=Text&widgetId=Text2&action=editWidget&sectionId=sidebar' on…
  1609. Warning Line 11973, Column 129: reference not terminated by REFC delimiter
    …etId=HTML3&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1610. Warning Line 11973, Column 129: reference to external entity in attribute value
    …etId=HTML3&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1611. Error Line 11973, Column 129: reference to entity "sectionId" for which no system identifier could be generated
    …etId=HTML3&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1612. Info Line 1580, Column 119: entity was defined here
    …=Text&widgetId=Text2&action=editWidget&sectionId=sidebar' onclick='return _Wid…
  1613. Warning Line 11984, Column 98: cannot generate system identifier for general entity "everywhere"
    …ools.flattr.net/blogger/flattrbutton.js?compact=true&everywhere=true'></script>

    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 "&amp;" (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 &aelig; 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.

  1614. Error Line 11984, Column 98: general entity "everywhere" not defined and no default entity
    …ools.flattr.net/blogger/flattrbutton.js?compact=true&everywhere=true'></script>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1615. Warning Line 11984, Column 108: reference not terminated by REFC delimiter
    …ools.flattr.net/blogger/flattrbutton.js?compact=true&everywhere=true'></script>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1616. Warning Line 11984, Column 108: reference to external entity in attribute value
    …ools.flattr.net/blogger/flattrbutton.js?compact=true&everywhere=true'></script>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1617. Error Line 11984, Column 108: reference to entity "everywhere" for which no system identifier could be generated
    …ools.flattr.net/blogger/flattrbutton.js?compact=true&everywhere=true'></script>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1618. Info Line 11984, Column 97: entity was defined here
    …ools.flattr.net/blogger/flattrbutton.js?compact=true&everywhere=true'></script>
  1619. Warning Line 11989, Column 81: reference not terminated by REFC delimiter
    …om/rearrange?blogID=9430835&widgetType=HTML&widgetId=HTML1&action=editWidget&s…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1620. Warning Line 11989, Column 81: reference to external entity in attribute value
    …om/rearrange?blogID=9430835&widgetType=HTML&widgetId=HTML1&action=editWidget&s…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1621. Error Line 11989, Column 81: reference to entity "widgetType" for which no system identifier could be generated
    …om/rearrange?blogID=9430835&widgetType=HTML&widgetId=HTML1&action=editWidget&s…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1622. Info Line 1580, Column 70: entity was defined here
    …w.blogger.com/rearrange?blogID=9430835&widgetType=Text&widgetId=Text2&action=e…
  1623. Warning Line 11989, Column 95: reference not terminated by REFC delimiter
    …logID=9430835&widgetType=HTML&widgetId=HTML1&action=editWidget&sectionId=sideb…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1624. Warning Line 11989, Column 95: reference to external entity in attribute value
    …logID=9430835&widgetType=HTML&widgetId=HTML1&action=editWidget&sectionId=sideb…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1625. Error Line 11989, Column 95: reference to entity "widgetId" for which no system identifier could be generated
    …logID=9430835&widgetType=HTML&widgetId=HTML1&action=editWidget&sectionId=sideb…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1626. Info Line 1580, Column 86: entity was defined here
    …arrange?blogID=9430835&widgetType=Text&widgetId=Text2&action=editWidget&sectio…
  1627. Warning Line 11989, Column 108: reference not terminated by REFC delimiter
    …&widgetType=HTML&widgetId=HTML1&action=editWidget&sectionId=sidebar' onclick='…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1628. Warning Line 11989, Column 108: reference to external entity in attribute value
    …&widgetType=HTML&widgetId=HTML1&action=editWidget&sectionId=sidebar' onclick='…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1629. Error Line 11989, Column 108: reference to entity "action" for which no system identifier could be generated
    …&widgetType=HTML&widgetId=HTML1&action=editWidget&sectionId=sidebar' onclick='…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1630. Info Line 1580, Column 101: entity was defined here
    …9430835&widgetType=Text&widgetId=Text2&action=editWidget&sectionId=sidebar' on…
  1631. Warning Line 11989, Column 129: reference not terminated by REFC delimiter
    …etId=HTML1&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1632. Warning Line 11989, Column 129: reference to external entity in attribute value
    …etId=HTML1&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1633. Error Line 11989, Column 129: reference to entity "sectionId" for which no system identifier could be generated
    …etId=HTML1&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1634. Info Line 1580, Column 119: entity was defined here
    …=Text&widgetId=Text2&action=editWidget&sectionId=sidebar' onclick='return _Wid…
  1635. Error Line 11998, Column 8: required attribute "type" not specified
    <script>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  1636. Error Line 12007, Column 90: required attribute "type" not specified
    …late.google.com/translate_a/element.js?cb=googleTranslateElementInit'></script>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  1637. Warning Line 12011, Column 81: reference not terminated by REFC delimiter
    …om/rearrange?blogID=9430835&widgetType=Translate&widgetId=Translate1&action=ed…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1638. Warning Line 12011, Column 81: reference to external entity in attribute value
    …om/rearrange?blogID=9430835&widgetType=Translate&widgetId=Translate1&action=ed…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1639. Error Line 12011, Column 81: reference to entity "widgetType" for which no system identifier could be generated
    …om/rearrange?blogID=9430835&widgetType=Translate&widgetId=Translate1&action=ed…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1640. Info Line 1580, Column 70: entity was defined here
    …w.blogger.com/rearrange?blogID=9430835&widgetType=Text&widgetId=Text2&action=e…
  1641. Warning Line 12011, Column 100: reference not terminated by REFC delimiter
    …=9430835&widgetType=Translate&widgetId=Translate1&action=editWidget&sectionId=…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1642. Warning Line 12011, Column 100: reference to external entity in attribute value
    …=9430835&widgetType=Translate&widgetId=Translate1&action=editWidget&sectionId=…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1643. Error Line 12011, Column 100: reference to entity "widgetId" for which no system identifier could be generated
    …=9430835&widgetType=Translate&widgetId=Translate1&action=editWidget&sectionId=…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1644. Info Line 1580, Column 86: entity was defined here
    …arrange?blogID=9430835&widgetType=Text&widgetId=Text2&action=editWidget&sectio…
  1645. Warning Line 12011, Column 118: reference not terminated by REFC delimiter
    …e=Translate&widgetId=Translate1&action=editWidget&sectionId=sidebar' onclick='…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1646. Warning Line 12011, Column 118: reference to external entity in attribute value
    …e=Translate&widgetId=Translate1&action=editWidget&sectionId=sidebar' onclick='…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1647. Error Line 12011, Column 118: reference to entity "action" for which no system identifier could be generated
    …e=Translate&widgetId=Translate1&action=editWidget&sectionId=sidebar' onclick='…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1648. Info Line 1580, Column 101: entity was defined here
    …9430835&widgetType=Text&widgetId=Text2&action=editWidget&sectionId=sidebar' on…
  1649. Warning Line 12011, Column 139: reference not terminated by REFC delimiter
    …Translate1&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1650. Warning Line 12011, Column 139: reference to external entity in attribute value
    …Translate1&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1651. Error Line 12011, Column 139: reference to entity "sectionId" for which no system identifier could be generated
    …Translate1&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1652. Info Line 1580, Column 119: entity was defined here
    …=Text&widgetId=Text2&action=editWidget&sectionId=sidebar' onclick='return _Wid…
  1653. Warning Line 12025, Column 81: reference not terminated by REFC delimiter
    …om/rearrange?blogID=9430835&widgetType=Text&widgetId=Text3&action=editWidget&s…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1654. Warning Line 12025, Column 81: reference to external entity in attribute value
    …om/rearrange?blogID=9430835&widgetType=Text&widgetId=Text3&action=editWidget&s…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1655. Error Line 12025, Column 81: reference to entity "widgetType" for which no system identifier could be generated
    …om/rearrange?blogID=9430835&widgetType=Text&widgetId=Text3&action=editWidget&s…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1656. Info Line 1580, Column 70: entity was defined here
    …w.blogger.com/rearrange?blogID=9430835&widgetType=Text&widgetId=Text2&action=e…
  1657. Warning Line 12025, Column 95: reference not terminated by REFC delimiter
    …logID=9430835&widgetType=Text&widgetId=Text3&action=editWidget&sectionId=sideb…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1658. Warning Line 12025, Column 95: reference to external entity in attribute value
    …logID=9430835&widgetType=Text&widgetId=Text3&action=editWidget&sectionId=sideb…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1659. Error Line 12025, Column 95: reference to entity "widgetId" for which no system identifier could be generated
    …logID=9430835&widgetType=Text&widgetId=Text3&action=editWidget&sectionId=sideb…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1660. Info Line 1580, Column 86: entity was defined here
    …arrange?blogID=9430835&widgetType=Text&widgetId=Text2&action=editWidget&sectio…
  1661. Warning Line 12025, Column 108: reference not terminated by REFC delimiter
    …&widgetType=Text&widgetId=Text3&action=editWidget&sectionId=sidebar' onclick='…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1662. Warning Line 12025, Column 108: reference to external entity in attribute value
    …&widgetType=Text&widgetId=Text3&action=editWidget&sectionId=sidebar' onclick='…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1663. Error Line 12025, Column 108: reference to entity "action" for which no system identifier could be generated
    …&widgetType=Text&widgetId=Text3&action=editWidget&sectionId=sidebar' onclick='…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1664. Info Line 1580, Column 101: entity was defined here
    …9430835&widgetType=Text&widgetId=Text2&action=editWidget&sectionId=sidebar' on…
  1665. Warning Line 12025, Column 129: reference not terminated by REFC delimiter
    …etId=Text3&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1666. Warning Line 12025, Column 129: reference to external entity in attribute value
    …etId=Text3&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1667. Error Line 12025, Column 129: reference to entity "sectionId" for which no system identifier could be generated
    …etId=Text3&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1668. Info Line 1580, Column 119: entity was defined here
    …=Text&widgetId=Text2&action=editWidget&sectionId=sidebar' onclick='return _Wid…
  1669. Warning Line 12040, Column 81: reference not terminated by REFC delimiter
    …om/rearrange?blogID=9430835&widgetType=Stats&widgetId=Stats1&action=editWidget…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1670. Warning Line 12040, Column 81: reference to external entity in attribute value
    …om/rearrange?blogID=9430835&widgetType=Stats&widgetId=Stats1&action=editWidget…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1671. Error Line 12040, Column 81: reference to entity "widgetType" for which no system identifier could be generated
    …om/rearrange?blogID=9430835&widgetType=Stats&widgetId=Stats1&action=editWidget…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1672. Info Line 1580, Column 70: entity was defined here
    …w.blogger.com/rearrange?blogID=9430835&widgetType=Text&widgetId=Text2&action=e…
  1673. Warning Line 12040, Column 96: reference not terminated by REFC delimiter
    …ogID=9430835&widgetType=Stats&widgetId=Stats1&action=editWidget&sectionId=side…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1674. Warning Line 12040, Column 96: reference to external entity in attribute value
    …ogID=9430835&widgetType=Stats&widgetId=Stats1&action=editWidget&sectionId=side…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1675. Error Line 12040, Column 96: reference to entity "widgetId" for which no system identifier could be generated
    …ogID=9430835&widgetType=Stats&widgetId=Stats1&action=editWidget&sectionId=side…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1676. Info Line 1580, Column 86: entity was defined here
    …arrange?blogID=9430835&widgetType=Text&widgetId=Text2&action=editWidget&sectio…
  1677. Warning Line 12040, Column 110: reference not terminated by REFC delimiter
    …idgetType=Stats&widgetId=Stats1&action=editWidget&sectionId=sidebar' onclick='…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1678. Warning Line 12040, Column 110: reference to external entity in attribute value
    …idgetType=Stats&widgetId=Stats1&action=editWidget&sectionId=sidebar' onclick='…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1679. Error Line 12040, Column 110: reference to entity "action" for which no system identifier could be generated
    …idgetType=Stats&widgetId=Stats1&action=editWidget&sectionId=sidebar' onclick='…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1680. Info Line 1580, Column 101: entity was defined here
    …9430835&widgetType=Text&widgetId=Text2&action=editWidget&sectionId=sidebar' on…
  1681. Warning Line 12040, Column 131: reference not terminated by REFC delimiter
    …tId=Stats1&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1682. Warning Line 12040, Column 131: reference to external entity in attribute value
    …tId=Stats1&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1683. Error Line 12040, Column 131: reference to entity "sectionId" for which no system identifier could be generated
    …tId=Stats1&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1684. Info Line 1580, Column 119: entity was defined here
    …=Text&widgetId=Text2&action=editWidget&sectionId=sidebar' onclick='return _Wid…
  1685. Error Line 12063, Column 102: required attribute "alt" not specified
    …ropdown-arrow' src='https://img2.blogblog.com/img/widgets/arrow_dropdown.gif'/>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  1686. Error Line 12069, Column 73: required attribute "alt" not specified
    <img src='https://img1.blogblog.com/img/widgets/subscribe-netvibes.png'/>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  1687. Error Line 12072, Column 70: required attribute "alt" not specified
    <img src='https://img1.blogblog.com/img/widgets/subscribe-yahoo.png'/>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  1688. Error Line 12075, Column 94: required attribute "alt" not specified
    …middle' class='feed-icon' src='https://img1.blogblog.com/img/icon_feed12.png'/>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  1689. Error Line 12085, Column 102: required attribute "alt" not specified
    …ropdown-arrow' src='https://img2.blogblog.com/img/widgets/arrow_dropdown.gif'/>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  1690. Error Line 12099, Column 102: required attribute "alt" not specified
    …ropdown-arrow' src='https://img2.blogblog.com/img/widgets/arrow_dropdown.gif'/>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  1691. Error Line 12105, Column 73: required attribute "alt" not specified
    <img src='https://img1.blogblog.com/img/widgets/subscribe-netvibes.png'/>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  1692. Error Line 12108, Column 70: required attribute "alt" not specified
    <img src='https://img1.blogblog.com/img/widgets/subscribe-yahoo.png'/>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  1693. Error Line 12111, Column 94: required attribute "alt" not specified
    …middle' class='feed-icon' src='https://img1.blogblog.com/img/icon_feed12.png'/>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  1694. Error Line 12121, Column 102: required attribute "alt" not specified
    …ropdown-arrow' src='https://img2.blogblog.com/img/widgets/arrow_dropdown.gif'/>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  1695. Warning Line 12137, Column 81: reference not terminated by REFC delimiter
    …om/rearrange?blogID=9430835&widgetType=Subscribe&widgetId=Subscribe1&action=ed…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1696. Warning Line 12137, Column 81: reference to external entity in attribute value
    …om/rearrange?blogID=9430835&widgetType=Subscribe&widgetId=Subscribe1&action=ed…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1697. Error Line 12137, Column 81: reference to entity "widgetType" for which no system identifier could be generated
    …om/rearrange?blogID=9430835&widgetType=Subscribe&widgetId=Subscribe1&action=ed…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1698. Info Line 1580, Column 70: entity was defined here
    …w.blogger.com/rearrange?blogID=9430835&widgetType=Text&widgetId=Text2&action=e…
  1699. Warning Line 12137, Column 100: reference not terminated by REFC delimiter
    …=9430835&widgetType=Subscribe&widgetId=Subscribe1&action=editWidget&sectionId=…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1700. Warning Line 12137, Column 100: reference to external entity in attribute value
    …=9430835&widgetType=Subscribe&widgetId=Subscribe1&action=editWidget&sectionId=…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1701. Error Line 12137, Column 100: reference to entity "widgetId" for which no system identifier could be generated
    …=9430835&widgetType=Subscribe&widgetId=Subscribe1&action=editWidget&sectionId=…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1702. Info Line 1580, Column 86: entity was defined here
    …arrange?blogID=9430835&widgetType=Text&widgetId=Text2&action=editWidget&sectio…
  1703. Warning Line 12137, Column 118: reference not terminated by REFC delimiter
    …e=Subscribe&widgetId=Subscribe1&action=editWidget&sectionId=footer' onclick='r…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1704. Warning Line 12137, Column 118: reference to external entity in attribute value
    …e=Subscribe&widgetId=Subscribe1&action=editWidget&sectionId=footer' onclick='r…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1705. Error Line 12137, Column 118: reference to entity "action" for which no system identifier could be generated
    …e=Subscribe&widgetId=Subscribe1&action=editWidget&sectionId=footer' onclick='r…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1706. Info Line 1580, Column 101: entity was defined here
    …9430835&widgetType=Text&widgetId=Text2&action=editWidget&sectionId=sidebar' on…
  1707. Warning Line 12137, Column 139: reference not terminated by REFC delimiter
    …Subscribe1&action=editWidget&sectionId=footer' onclick='return _WidgetManager.…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1708. Warning Line 12137, Column 139: reference to external entity in attribute value
    …Subscribe1&action=editWidget&sectionId=footer' onclick='return _WidgetManager.…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1709. Error Line 12137, Column 139: reference to entity "sectionId" for which no system identifier could be generated
    …Subscribe1&action=editWidget&sectionId=footer' onclick='return _WidgetManager.…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1710. Info Line 1580, Column 119: entity was defined here
    …=Text&widgetId=Text2&action=editWidget&sectionId=sidebar' onclick='return _Wid…
  1711. Warning Line 12154, Column 81: reference not terminated by REFC delimiter
    …om/rearrange?blogID=9430835&widgetType=HTML&widgetId=HTML2&action=editWidget&s…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1712. Warning Line 12154, Column 81: reference to external entity in attribute value
    …om/rearrange?blogID=9430835&widgetType=HTML&widgetId=HTML2&action=editWidget&s…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1713. Error Line 12154, Column 81: reference to entity "widgetType" for which no system identifier could be generated
    …om/rearrange?blogID=9430835&widgetType=HTML&widgetId=HTML2&action=editWidget&s…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1714. Info Line 1580, Column 70: entity was defined here
    …w.blogger.com/rearrange?blogID=9430835&widgetType=Text&widgetId=Text2&action=e…
  1715. Warning Line 12154, Column 95: reference not terminated by REFC delimiter
    …logID=9430835&widgetType=HTML&widgetId=HTML2&action=editWidget&sectionId=foote…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1716. Warning Line 12154, Column 95: reference to external entity in attribute value
    …logID=9430835&widgetType=HTML&widgetId=HTML2&action=editWidget&sectionId=foote…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1717. Error Line 12154, Column 95: reference to entity "widgetId" for which no system identifier could be generated
    …logID=9430835&widgetType=HTML&widgetId=HTML2&action=editWidget&sectionId=foote…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1718. Info Line 1580, Column 86: entity was defined here
    …arrange?blogID=9430835&widgetType=Text&widgetId=Text2&action=editWidget&sectio…
  1719. Warning Line 12154, Column 108: reference not terminated by REFC delimiter
    …&widgetType=HTML&widgetId=HTML2&action=editWidget&sectionId=footer' onclick='r…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1720. Warning Line 12154, Column 108: reference to external entity in attribute value
    …&widgetType=HTML&widgetId=HTML2&action=editWidget&sectionId=footer' onclick='r…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1721. Error Line 12154, Column 108: reference to entity "action" for which no system identifier could be generated
    …&widgetType=HTML&widgetId=HTML2&action=editWidget&sectionId=footer' onclick='r…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1722. Info Line 1580, Column 101: entity was defined here
    …9430835&widgetType=Text&widgetId=Text2&action=editWidget&sectionId=sidebar' on…
  1723. Warning Line 12154, Column 129: reference not terminated by REFC delimiter
    …etId=HTML2&action=editWidget&sectionId=footer' onclick='return _WidgetManager.…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  1724. Warning Line 12154, Column 129: reference to external entity in attribute value
    …etId=HTML2&action=editWidget&sectionId=footer' onclick='return _WidgetManager.…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  1725. Error Line 12154, Column 129: reference to entity "sectionId" for which no system identifier could be generated
    …etId=HTML2&action=editWidget&sectionId=footer' onclick='return _WidgetManager.…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  1726. Info Line 1580, Column 119: entity was defined here
    …=Text&widgetId=Text2&action=editWidget&sectionId=sidebar' onclick='return _Wid…

↑ Top