Home Foto Jual Paket Dvd Pasang Banner Koleksi Video Bokep meringis di obok-obok 07:51 Febi ML 00:35 Febi Ngangkang 01:09 Febi Dance 2 00:12 Febi Dance 00:29 for u pa 03:00 Farah 4 ...

bokepgratiz.info
  • Domain Name
    bokepgratiz.info
  • Favicon
  • Google Page Rank
    0
  • Alexa Rank
    #24957
  • Page Size
    20.9 KB
  • Ip Address
    174.136.13.119
  • Heading
    H1: 1, H2: 16, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    8 GIF, 16 JPG, 1 PNG

Website Meta Analysis

  • Title
    Bokepgratiz.info | Koleksi Bokep Indonesia
  • Meta Keyword
  • Meta Description
    Home Foto Jual Paket Dvd Pasang Banner Koleksi Video Bokep meringis di obok-obok 07:51 Febi ML 00:35 Febi Ngangkang 01:09 Febi Dance 2 00:12 Febi Dance 00:29 for u pa 03:00 Farah 4 00:57 Farah 3 01:35 Farah 2 00:36 Farah1 00:06 Dengan miera ...

Technical Analysis

  • Webserver
    Apache
  • Ip Address
    174.136.13.119
  • Domain Age
    9 Months, 15 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from bokepgratiz.info.

HTML Analysis

  • server: Apache
  • date: Tue, 10 Sep 2013 14:54:11 GMT
  • content-type: text/html; charset=UTF-8
  • connection: keep-alive
  • vary: Accept-Encoding,Cookie
  • cache-control: max-age=3, must-revalidate
  • wp-super-cache: Served supercache file from PHP
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for bokepgratiz.info

DNS Analysis


DNS servers
manage1.rumahweb.com
manage2.rumahweb.com
manage4.rumahweb.com
manage3.rumahweb.com


DNS Records

Answer records
bokepgratiz.info NS  manage1.rumahweb.com 38400s
bokepgratiz.info A 216.239.34.21 28800s
bokepgratiz.info A 216.239.38.21 28800s
bokepgratiz.info A 216.239.36.21 28800s
bokepgratiz.info NS  manage2.rumahweb.com 38400s
bokepgratiz.info SOA
server: manage1.rumahweb.com
email: dhikodwi@rocketmail.com
serial: 2012120112
refresh: 7200
retry: 7200
expire: 172800
minimum ttl: 38400
7200s
bokepgratiz.info NS  manage4.rumahweb.com 38400s
bokepgratiz.info NS  manage3.rumahweb.com 38400s
bokepgratiz.info A 216.239.32.21 28800s

Authority records

Additional records

IP 174.136.13.119 Analysis

  • Country Code
  • Country Code3
  • Country Name
  • City
  • Continent Code
  • Latitude
  • Longitude
  • No whois ip data for 174.136.13.119

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 9 Errors
  • 388 Warnings
Ratio Text/Html
  • 0.6680195941217635
Message Error
  • Warning Line 9, Column 121: cannot generate system identifier for general entity "zx"
    …on.css?targetBlogID=51421036228529037&zx=bd3af301-29d6-4823-bdfd-e2b4bd01c561"…

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

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

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

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

  • Error Line 9, Column 121: general entity "zx" not defined and no default entity
    …on.css?targetBlogID=51421036228529037&zx=bd3af301-29d6-4823-bdfd-e2b4bd01c561"…

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

  • Warning Line 9, Column 123: reference not terminated by REFC delimiter
    …n.css?targetBlogID=51421036228529037&zx=bd3af301-29d6-4823-bdfd-e2b4bd01c561"/>

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

  • Warning Line 9, Column 123: reference to external entity in attribute value
    …n.css?targetBlogID=51421036228529037&zx=bd3af301-29d6-4823-bdfd-e2b4bd01c561"/>

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

  • Error Line 9, Column 123: reference to entity "zx" for which no system identifier could be generated
    …n.css?targetBlogID=51421036228529037&zx=bd3af301-29d6-4823-bdfd-e2b4bd01c561"/>

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

  • Info Line 9, Column 120: entity was defined here
    …ion.css?targetBlogID=51421036228529037&zx=bd3af301-29d6-4823-bdfd-e2b4bd01c561…
  • Warning Line 12, Column 5: multiple comments in comment declaration
    -----------------------------------------------
  • Warning Line 12, Column 9: multiple comments in comment declaration
    -----------------------------------------------
  • Warning Line 12, Column 13: multiple comments in comment declaration
    -----------------------------------------------
  • Warning Line 12, Column 17: multiple comments in comment declaration
    -----------------------------------------------
  • Warning Line 12, Column 21: multiple comments in comment declaration
    -----------------------------------------------
  • Warning Line 12, Column 25: multiple comments in comment declaration
    -----------------------------------------------
  • Warning Line 12, Column 29: multiple comments in comment declaration
    -----------------------------------------------
  • Warning Line 12, Column 33: multiple comments in comment declaration
    -----------------------------------------------
  • Warning Line 12, Column 37: multiple comments in comment declaration
    -----------------------------------------------
  • Warning Line 12, Column 41: multiple comments in comment declaration
    -----------------------------------------------
  • Warning Line 12, Column 45: multiple comments in comment declaration
    -----------------------------------------------
  • Error Line 12, Column 47: invalid comment declaration: found name character outside comment but inside comment declaration
    -----------------------------------------------
  • Info Line 10, Column 41: comment declaration started here
    <style id='page-skin-1' type='text/css'><!--
  • Error Line 370, Column 7: required attribute "type" not specified
    <style>

    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>.

  • Warning Line 398, Column 78: cannot generate system identifier for general entity "m"
    …vigator,b="userAgent",c="indexOf",f="&m=1",g="(^|&)m=",h="?",i="?m=1";function…

    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.

  • Error Line 398, Column 78: general entity "m" not defined and no default entity
    …vigator,b="userAgent",c="indexOf",f="&m=1",g="(^|&)m=",h="?",i="?m=1";function…

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

  • Warning Line 398, Column 79: reference not terminated by REFC delimiter
    …igator,b="userAgent",c="indexOf",f="&m=1",g="(^|&)m=",h="?",i="?m=1";function …

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

  • Error Line 398, Column 79: reference to entity "m" for which no system identifier could be generated
    …igator,b="userAgent",c="indexOf",f="&m=1",g="(^|&)m=",h="?",i="?m=1";function …

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

  • Info Line 398, Column 77: entity was defined here
    …avigator,b="userAgent",c="indexOf",f="&m=1",g="(^|&)m=",h="?",i="?m=1";functio…
  • Warning Line 398, Column 89: character "&" is the first character of a delimiter but occurred as data
    …userAgent",c="indexOf",f="&m=1",g="(^|&)m=",h="?",i="?m=1";function j(){var 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.
  • Warning Line 398, Column 213: character "<" is the first character of a delimiter but occurred as data
    …gth){case 1:return d+i;case 2:return 0<=e[1].search(g)?null:d+f;default:return…

    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.
  • Warning Line 398, Column 284: character "&" is the first character of a delimiter but occurred as data
    …:return null}}if(-1!=a[b][c]("Mobile")&&-1!=a[b][c]("WebKit")&&-1==a[b][c]("iP…

    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.
  • Warning Line 398, Column 285: character "&" is the first character of a delimiter but occurred as data
    …return null}}if(-1!=a[b][c]("Mobile")&&-1!=a[b][c]("WebKit")&&-1==a[b][c]("iPa…

    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.
  • Warning Line 398, Column 307: character "&" is the first character of a delimiter but occurred as data
    …b][c]("Mobile")&&-1!=a[b][c]("WebKit")&&-1==a[b][c]("iPad")||-1!=a[b][c]("Oper…

    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.
  • Warning Line 398, Column 308: character "&" is the first character of a delimiter but occurred as data
    …][c]("Mobile")&&-1!=a[b][c]("WebKit")&&-1==a[b][c]("iPad")||-1!=a[b][c]("Opera…

    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.
  • Warning Line 398, Column 393: character "&" is the first character of a delimiter but occurred as data
    …pera Mini")||-1!=a[b][c]("IEMobile")){var k=j();k&&window.location.replace(k)};

    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.
  • Warning Line 398, Column 395: cannot generate system identifier for general entity "window.location.replace"
    …pera Mini")||-1!=a[b][c]("IEMobile")){var k=j();k&&window.location.replace(k)};

    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.

  • Error Line 398, Column 395: general entity "window.location.replace" not defined and no default entity
    …pera Mini")||-1!=a[b][c]("IEMobile")){var k=j();k&&window.location.replace(k)};

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

  • Warning Line 398, Column 418: reference not terminated by REFC delimiter
    …pera Mini")||-1!=a[b][c]("IEMobile")){var k=j();k&&window.location.replace(k)};

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

  • Error Line 398, Column 418: reference to entity "window.location.replace" for which no system identifier could be generated
    …pera Mini")||-1!=a[b][c]("IEMobile")){var k=j();k&&window.location.replace(k)};

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

  • Info Line 398, Column 394: entity was defined here
    …pera Mini")||-1!=a[b][c]("IEMobile")){var k=j();k&&window.location.replace(k)};
  • Warning Line 417, Column 30: character "&" is the first character of a delimiter but occurred as data
              if (window.iframes && iframes.open) {

    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.
  • Warning Line 417, Column 31: character "&" is the first character of a delimiter but occurred as data
              if (window.iframes && iframes.open) {

    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.
  • Error Line 460, Column 7: required attribute "type" not specified
    <style>/* Navigasi tabs Sederhana buka-rahasia.blogsot.com Starts */

    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>.

  • Error Line 460, Column 7: document type does not allow element "style" here
    <style>/* Navigasi tabs Sederhana buka-rahasia.blogsot.com Starts */

    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).

  • Error Line 470, Column 44: there is no attribute "target"
    …ef="http://www.foto17xxx.com/" target='_blank' class="burastabs2">Foto Bugil</…

    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.

  • Error Line 478, Column 58: 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
    …nput" name="q" size="39" type="text" /> <input class="buttonsubmit" name="subm…

    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>").

  • Error Line 478, Column 134: 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
    …put class="buttonsubmit" name="submit" type="submit" value="Telusuri" /></form>

    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>").

  • Warning Line 484, Column 81: cannot generate system identifier for general entity "widgetType"
    …om/rearrange?blogID=51421036228529037&widgetType=HTML&widgetId=HTML6&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.

  • Error Line 484, Column 81: general entity "widgetType" not defined and no default entity
    …om/rearrange?blogID=51421036228529037&widgetType=HTML&widgetId=HTML6&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.

  • Warning Line 484, Column 91: reference not terminated by REFC delimiter
    …ge?blogID=51421036228529037&widgetType=HTML&widgetId=HTML6&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.

  • Warning Line 484, Column 91: reference to external entity in attribute value
    …ge?blogID=51421036228529037&widgetType=HTML&widgetId=HTML6&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;'.

  • Error Line 484, Column 91: reference to entity "widgetType" for which no system identifier could be generated
    …ge?blogID=51421036228529037&widgetType=HTML&widgetId=HTML6&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.

  • Info Line 484, Column 80: entity was defined here
    …com/rearrange?blogID=51421036228529037&widgetType=HTML&widgetId=HTML6&action=e…
  • Warning Line 484, Column 97: cannot generate system identifier for general entity "widgetId"
    …gID=51421036228529037&widgetType=HTML&widgetId=HTML6&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.

  • Error Line 484, Column 97: general entity "widgetId" not defined and no default entity
    …gID=51421036228529037&widgetType=HTML&widgetId=HTML6&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.

  • Warning Line 484, Column 105: reference not terminated by REFC delimiter
    …1036228529037&widgetType=HTML&widgetId=HTML6&action=editWidget&sectionId=heade…

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

  • Warning Line 484, Column 105: reference to external entity in attribute value
    …1036228529037&widgetType=HTML&widgetId=HTML6&action=editWidget&sectionId=heade…

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

  • Error Line 484, Column 105: reference to entity "widgetId" for which no system identifier could be generated
    …1036228529037&widgetType=HTML&widgetId=HTML6&action=editWidget&sectionId=heade…

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

  • Info Line 484, Column 96: entity was defined here
    …ogID=51421036228529037&widgetType=HTML&widgetId=HTML6&action=editWidget&sectio…
  • Warning Line 484, Column 112: cannot generate system identifier for general entity "action"
    …529037&widgetType=HTML&widgetId=HTML6&action=editWidget&sectionId=header2' 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.

  • Error Line 484, Column 112: general entity "action" not defined and no default entity
    …529037&widgetType=HTML&widgetId=HTML6&action=editWidget&sectionId=header2' 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.

  • Warning Line 484, Column 118: reference not terminated by REFC delimiter
    …&widgetType=HTML&widgetId=HTML6&action=editWidget&sectionId=header2' 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.

  • Warning Line 484, Column 118: reference to external entity in attribute value
    …&widgetType=HTML&widgetId=HTML6&action=editWidget&sectionId=header2' 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;'.

  • Error Line 484, Column 118: reference to entity "action" for which no system identifier could be generated
    …&widgetType=HTML&widgetId=HTML6&action=editWidget&sectionId=header2' 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.

  • Info Line 484, Column 111: entity was defined here
    …8529037&widgetType=HTML&widgetId=HTML6&action=editWidget&sectionId=header2' on…
  • Warning Line 484, Column 130: cannot generate system identifier for general entity "sectionId"
    …HTML&widgetId=HTML6&action=editWidget&sectionId=header2' 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.

  • Error Line 484, Column 130: general entity "sectionId" not defined and no default entity
    …HTML&widgetId=HTML6&action=editWidget&sectionId=header2' 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.

  • Warning Line 484, Column 139: reference not terminated by REFC delimiter
    …etId=HTML6&action=editWidget&sectionId=header2' 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.

  • Warning Line 484, Column 139: reference to external entity in attribute value
    …etId=HTML6&action=editWidget&sectionId=header2' 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;'.

  • Error Line 484, Column 139: reference to entity "sectionId" for which no system identifier could be generated
    …etId=HTML6&action=editWidget&sectionId=header2' 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.

  • Info Line 484, Column 129: entity was defined here
    …=HTML&widgetId=HTML6&action=editWidget&sectionId=header2' onclick='return _Wid…
  • Error Line 503, Column 138: there is no attribute "border"
    …ikodwi/468x60_zps6ff95971.gif" border="0" alt="CARA CEPAT MEMBESARKAN PENIS"/>…

    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.

  • Error Line 506, Column 16: there is no attribute "border"
    <iframe border=0 frameborder=0 marginheight=0 marginwidth=0 width=476 height=68…

    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.

  • Error Line 506, Column 16: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <iframe border=0 frameborder=0 marginheight=0 marginwidth=0 width=476 height=68…
  • Error Line 506, Column 30: there is no attribute "frameborder"
    <iframe border=0 frameborder=0 marginheight=0 marginwidth=0 width=476 height=68…

    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.

  • Error Line 506, Column 30: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <iframe border=0 frameborder=0 marginheight=0 marginwidth=0 width=476 height=68…
  • Error Line 506, Column 45: there is no attribute "marginheight"
    …e border=0 frameborder=0 marginheight=0 marginwidth=0 width=476 height=68 scro…

    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.

  • Error Line 506, Column 45: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …e border=0 frameborder=0 marginheight=0 marginwidth=0 width=476 height=68 scro…
  • Error Line 506, Column 59: there is no attribute "marginwidth"
    …meborder=0 marginheight=0 marginwidth=0 width=476 height=68 scrolling=no allow…

    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.

  • Error Line 506, Column 59: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …meborder=0 marginheight=0 marginwidth=0 width=476 height=68 scrolling=no allow…
  • Error Line 506, Column 67: there is no attribute "width"
    …=0 marginheight=0 marginwidth=0 width=476 height=68 scrolling=no allowtranspar…

    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.

  • Error Line 506, Column 67: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …=0 marginheight=0 marginwidth=0 width=476 height=68 scrolling=no allowtranspar…
  • Error Line 506, Column 78: there is no attribute "height"
    …ight=0 marginwidth=0 width=476 height=68 scrolling=no allowtransparency=true s…

    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.

  • Error Line 506, Column 78: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ight=0 marginwidth=0 width=476 height=68 scrolling=no allowtransparency=true s…
  • Error Line 506, Column 91: there is no attribute "scrolling"
    …width=0 width=476 height=68 scrolling=no allowtransparency=true src=http://ads…

    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.

  • Error Line 506, Column 91: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …width=0 width=476 height=68 scrolling=no allowtransparency=true src=http://ads…
  • Error Line 506, Column 112: there is no attribute "allowtransparency"
    …ght=68 scrolling=no allowtransparency=true src=http://adserver.juicyads.com/ad…

    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.

  • Error Line 506, Column 112: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ght=68 scrolling=no allowtransparency=true src=http://adserver.juicyads.com/ad…
  • Error Line 506, Column 121: there is no attribute "src"
    …rolling=no allowtransparency=true src=http://adserver.juicyads.com/adshow.php?…

    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.

  • Error Line 506, Column 121: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …rolling=no allowtransparency=true src=http://adserver.juicyads.com/adshow.php?…
  • Error Line 506, Column 127: NET-enabling start-tag not immediately followed by null end-tag
    …g=no allowtransparency=true src=http://adserver.juicyads.com/adshow.php?adzone…

    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).

  • Error Line 506, Column 127: element "iframe" undefined
    …g=no allowtransparency=true src=http://adserver.juicyads.com/adshow.php?adzone…

    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).
  • Error Line 506, Column 183: end tag for element "iframe" which is not open
    …arency=true src=http://adserver.juicyads.com/adshow.php?adzone=188562></iframe>

    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.

  • Warning Line 512, Column 99: cannot generate system identifier for general entity "ver"
    …'http://ads.adxpansion.com/public/js/showads.php?zone_id=42694&ver=1'></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.

  • Error Line 512, Column 99: general entity "ver" not defined and no default entity
    …'http://ads.adxpansion.com/public/js/showads.php?zone_id=42694&ver=1'></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.

  • Warning Line 512, Column 102: reference not terminated by REFC delimiter
    …'http://ads.adxpansion.com/public/js/showads.php?zone_id=42694&ver=1'></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.

  • Warning Line 512, Column 102: reference to external entity in attribute value
    …'http://ads.adxpansion.com/public/js/showads.php?zone_id=42694&ver=1'></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;'.

  • Error Line 512, Column 102: reference to entity "ver" for which no system identifier could be generated
    …'http://ads.adxpansion.com/public/js/showads.php?zone_id=42694&ver=1'></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.

  • Info Line 512, Column 98: entity was defined here
    …'http://ads.adxpansion.com/public/js/showads.php?zone_id=42694&ver=1'></script>
  • Warning Line 522, Column 91: reference not terminated by REFC delimiter
    …ge?blogID=51421036228529037&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.

  • Warning Line 522, Column 91: reference to external entity in attribute value
    …ge?blogID=51421036228529037&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;'.

  • Error Line 522, Column 91: reference to entity "widgetType" for which no system identifier could be generated
    …ge?blogID=51421036228529037&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.

  • Info Line 484, Column 80: entity was defined here
    …com/rearrange?blogID=51421036228529037&widgetType=HTML&widgetId=HTML6&action=e…
  • Warning Line 522, Column 105: reference not terminated by REFC delimiter
    …1036228529037&widgetType=HTML&widgetId=HTML2&action=editWidget&sectionId=main'…

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

  • Warning Line 522, Column 105: reference to external entity in attribute value
    …1036228529037&widgetType=HTML&widgetId=HTML2&action=editWidget&sectionId=main'…

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

  • Error Line 522, Column 105: reference to entity "widgetId" for which no system identifier could be generated
    …1036228529037&widgetType=HTML&widgetId=HTML2&action=editWidget&sectionId=main'…

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

  • Info Line 484, Column 96: entity was defined here
    …ogID=51421036228529037&widgetType=HTML&widgetId=HTML6&action=editWidget&sectio…
  • Warning Line 522, Column 118: reference not terminated by REFC delimiter
    …&widgetType=HTML&widgetId=HTML2&action=editWidget&sectionId=main' onclick='ret…

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

  • Warning Line 522, Column 118: reference to external entity in attribute value
    …&widgetType=HTML&widgetId=HTML2&action=editWidget&sectionId=main' onclick='ret…

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

  • Error Line 522, Column 118: reference to entity "action" for which no system identifier could be generated
    …&widgetType=HTML&widgetId=HTML2&action=editWidget&sectionId=main' onclick='ret…

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

  • Info Line 484, Column 111: entity was defined here
    …8529037&widgetType=HTML&widgetId=HTML6&action=editWidget&sectionId=header2' on…
  • Warning Line 522, Column 139: reference not terminated by REFC delimiter
    …etId=HTML2&action=editWidget&sectionId=main' onclick='return _WidgetManager._P…

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

  • Warning Line 522, Column 139: reference to external entity in attribute value
    …etId=HTML2&action=editWidget&sectionId=main' onclick='return _WidgetManager._P…

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

  • Error Line 522, Column 139: reference to entity "sectionId" for which no system identifier could be generated
    …etId=HTML2&action=editWidget&sectionId=main' onclick='return _WidgetManager._P…

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

  • Info Line 484, Column 129: entity was defined here
    …=HTML&widgetId=HTML6&action=editWidget&sectionId=header2' onclick='return _Wid…
  • Error Line 603, Column 37: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div id='summary5681725945039188343'>

    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>").

  • Error Line 605, Column 298: end tag for "param" omitted, but OMITTAG NO was specified
    …cab#version=6,0,40,0"><param name="movie" value="//www.youtube.com/get_player">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 605, Column 241: start tag was here
    …s/flash/swflash.cab#version=6,0,40,0"><param name="movie" value="//www.youtube…
  • Error Line 606, Column 39: end tag for "param" omitted, but OMITTAG NO was specified
    <param name="bgcolor" value="#FFFFFF">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 606, Column 1: start tag was here
    <param name="bgcolor" value="#FFFFFF">
  • Error Line 607, Column 44: end tag for "param" omitted, but OMITTAG NO was specified
    <param name="allowfullscreen" value="true">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 607, Column 1: start tag was here
    <param name="allowfullscreen" value="true">
  • Error Line 608, Column 586: end tag for "param" omitted, but OMITTAG NO was specified
    …tag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&amp;autoplay=0&amp;ps=blogger">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 608, Column 1: start tag was here
    <param name="flashvars" value="flvurl=http://redirector.googlevideo.com/videopl…
  • Error Line 609, Column 12: there is no attribute "src"
    <embed src="//www.youtube.com/get_player" type="application/x-shockwave-flash"

    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.

  • Error Line 609, Column 48: there is no attribute "type"
    <embed src="//www.youtube.com/get_player" type="application/x-shockwave-flash"

    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.

  • Error Line 610, Column 7: there is no attribute "width"
    width="320" height="266" bgcolor="#FFFFFF"

    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.

  • Error Line 610, Column 20: there is no attribute "height"
    width="320" height="266" bgcolor="#FFFFFF"

    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.

  • Error Line 610, Column 34: there is no attribute "bgcolor"
    width="320" height="266" bgcolor="#FFFFFF"

    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.

  • Error Line 611, Column 11: there is no attribute "flashvars"
    flashvars="flvurl=http://redirector.googlevideo.com/videoplayback?id%3Df781f221…

    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.

  • Warning Line 611, Column 371: cannot generate system identifier for general entity "iurl"
    …5FA5BF22D7FFFDBF017BD1658%26key%3Dck2&iurl=http://video.google.com/ThumbnailSe…

    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.

  • Error Line 611, Column 371: general entity "iurl" not defined and no default entity
    …5FA5BF22D7FFFDBF017BD1658%26key%3Dck2&iurl=http://video.google.com/ThumbnailSe…

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

  • Warning Line 611, Column 375: reference not terminated by REFC delimiter
    …BF22D7FFFDBF017BD1658%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Warning Line 611, Column 375: reference to external entity in attribute value
    …BF22D7FFFDBF017BD1658%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Error Line 611, Column 375: reference to entity "iurl" for which no system identifier could be generated
    …BF22D7FFFDBF017BD1658%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Info Line 611, Column 370: entity was defined here
    …D5FA5BF22D7FFFDBF017BD1658%26key%3Dck2&iurl=http://video.google.com/ThumbnailS…
  • Warning Line 611, Column 531: cannot generate system identifier for general entity "autoplay"
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"

    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.

  • Error Line 611, Column 531: general entity "autoplay" not defined and no default entity
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"

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

  • Warning Line 611, Column 539: reference not terminated by REFC delimiter
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"

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

  • Warning Line 611, Column 539: reference to external entity in attribute value
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"

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

  • Error Line 611, Column 539: reference to entity "autoplay" for which no system identifier could be generated
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"

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

  • Info Line 611, Column 530: entity was defined here
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"
  • Warning Line 611, Column 542: cannot generate system identifier for general entity "ps"
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"

    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.

  • Error Line 611, Column 542: general entity "ps" not defined and no default entity
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"

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

  • Warning Line 611, Column 544: reference not terminated by REFC delimiter
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"

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

  • Warning Line 611, Column 544: reference to external entity in attribute value
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"

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

  • Error Line 611, Column 544: reference to entity "ps" for which no system identifier could be generated
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"

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

  • Info Line 611, Column 541: entity was defined here
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"
  • Error Line 612, Column 17: there is no attribute "allowFullScreen"
    allowFullScreen="true" /></object>

    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.

  • Error Line 612, Column 25: element "embed" undefined
    allowFullScreen="true" /></object>

    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).
  • Error Line 613, Column 395: end tag for "img" omitted, but OMITTAG NO was specified
    …ss="BLOG_mobile_video_class" id="BLOG_mobile_video-f781f22160f9a869"></a></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 ">".

  • Info Line 613, Column 119: start tag was here
    …==/0/0/0/video.3gp" type="video/3gpp"><img width="320" height="266" alt="video…
  • Error Line 692, Column 37: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div id='summary8389073282569265051'>

    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>").

  • Error Line 694, Column 298: end tag for "param" omitted, but OMITTAG NO was specified
    …cab#version=6,0,40,0"><param name="movie" value="//www.youtube.com/get_player">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 694, Column 241: start tag was here
    …s/flash/swflash.cab#version=6,0,40,0"><param name="movie" value="//www.youtube…
  • Error Line 695, Column 39: end tag for "param" omitted, but OMITTAG NO was specified
    <param name="bgcolor" value="#FFFFFF">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 695, Column 1: start tag was here
    <param name="bgcolor" value="#FFFFFF">
  • Error Line 696, Column 44: end tag for "param" omitted, but OMITTAG NO was specified
    <param name="allowfullscreen" value="true">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 696, Column 1: start tag was here
    <param name="allowfullscreen" value="true">
  • Error Line 697, Column 586: end tag for "param" omitted, but OMITTAG NO was specified
    …tag%3Dw160%26sigh%3DMoer-sMF3fiyD_Ihj9LXGw4VdxE&amp;autoplay=0&amp;ps=blogger">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 697, Column 1: start tag was here
    <param name="flashvars" value="flvurl=http://redirector.googlevideo.com/videopl…
  • Warning Line 700, Column 375: reference not terminated by REFC delimiter
    …F72CD0C1803A033CB7696%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Warning Line 700, Column 375: reference to external entity in attribute value
    …F72CD0C1803A033CB7696%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Error Line 700, Column 375: reference to entity "iurl" for which no system identifier could be generated
    …F72CD0C1803A033CB7696%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Info Line 611, Column 370: entity was defined here
    …D5FA5BF22D7FFFDBF017BD1658%26key%3Dck2&iurl=http://video.google.com/ThumbnailS…
  • Warning Line 700, Column 539: reference not terminated by REFC delimiter
    …D5000%26itag%3Dw160%26sigh%3DMoer-sMF3fiyD_Ihj9LXGw4VdxE&autoplay=0&ps=blogger"

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

  • Warning Line 700, Column 539: reference to external entity in attribute value
    …D5000%26itag%3Dw160%26sigh%3DMoer-sMF3fiyD_Ihj9LXGw4VdxE&autoplay=0&ps=blogger"

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

  • Error Line 700, Column 539: reference to entity "autoplay" for which no system identifier could be generated
    …D5000%26itag%3Dw160%26sigh%3DMoer-sMF3fiyD_Ihj9LXGw4VdxE&autoplay=0&ps=blogger"

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

  • Info Line 611, Column 530: entity was defined here
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"
  • Warning Line 700, Column 544: reference not terminated by REFC delimiter
    …D5000%26itag%3Dw160%26sigh%3DMoer-sMF3fiyD_Ihj9LXGw4VdxE&autoplay=0&ps=blogger"

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

  • Warning Line 700, Column 544: reference to external entity in attribute value
    …D5000%26itag%3Dw160%26sigh%3DMoer-sMF3fiyD_Ihj9LXGw4VdxE&autoplay=0&ps=blogger"

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

  • Error Line 700, Column 544: reference to entity "ps" for which no system identifier could be generated
    …D5000%26itag%3Dw160%26sigh%3DMoer-sMF3fiyD_Ihj9LXGw4VdxE&autoplay=0&ps=blogger"

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

  • Info Line 611, Column 541: entity was defined here
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"
  • Error Line 701, Column 25: element "embed" undefined
    allowFullScreen="true" /></object>

    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).
  • Error Line 702, Column 395: end tag for "img" omitted, but OMITTAG NO was specified
    …ss="BLOG_mobile_video_class" id="BLOG_mobile_video-61ec7a1fa3b3f6c9"></a></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 ">".

  • Info Line 702, Column 119: start tag was here
    …==/0/0/0/video.3gp" type="video/3gpp"><img width="320" height="266" alt="video…
  • Error Line 781, Column 37: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div id='summary1919713136886055861'>

    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>").

  • Error Line 783, Column 298: end tag for "param" omitted, but OMITTAG NO was specified
    …cab#version=6,0,40,0"><param name="movie" value="//www.youtube.com/get_player">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 783, Column 241: start tag was here
    …s/flash/swflash.cab#version=6,0,40,0"><param name="movie" value="//www.youtube…
  • Error Line 784, Column 39: end tag for "param" omitted, but OMITTAG NO was specified
    <param name="bgcolor" value="#FFFFFF">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 784, Column 1: start tag was here
    <param name="bgcolor" value="#FFFFFF">
  • Error Line 785, Column 44: end tag for "param" omitted, but OMITTAG NO was specified
    <param name="allowfullscreen" value="true">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 785, Column 1: start tag was here
    <param name="allowfullscreen" value="true">
  • Error Line 786, Column 586: end tag for "param" omitted, but OMITTAG NO was specified
    …tag%3Dw160%26sigh%3DP-D2wnzUyw6NJU-bRJi_xtz2yUc&amp;autoplay=0&amp;ps=blogger">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 786, Column 1: start tag was here
    <param name="flashvars" value="flvurl=http://redirector.googlevideo.com/videopl…
  • Warning Line 789, Column 375: reference not terminated by REFC delimiter
    …FCA03D6D3F18B1B7A5AE2%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Warning Line 789, Column 375: reference to external entity in attribute value
    …FCA03D6D3F18B1B7A5AE2%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Error Line 789, Column 375: reference to entity "iurl" for which no system identifier could be generated
    …FCA03D6D3F18B1B7A5AE2%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Info Line 611, Column 370: entity was defined here
    …D5FA5BF22D7FFFDBF017BD1658%26key%3Dck2&iurl=http://video.google.com/ThumbnailS…
  • Warning Line 789, Column 539: reference not terminated by REFC delimiter
    …D5000%26itag%3Dw160%26sigh%3DP-D2wnzUyw6NJU-bRJi_xtz2yUc&autoplay=0&ps=blogger"

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

  • Warning Line 789, Column 539: reference to external entity in attribute value
    …D5000%26itag%3Dw160%26sigh%3DP-D2wnzUyw6NJU-bRJi_xtz2yUc&autoplay=0&ps=blogger"

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

  • Error Line 789, Column 539: reference to entity "autoplay" for which no system identifier could be generated
    …D5000%26itag%3Dw160%26sigh%3DP-D2wnzUyw6NJU-bRJi_xtz2yUc&autoplay=0&ps=blogger"

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

  • Info Line 611, Column 530: entity was defined here
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"
  • Warning Line 789, Column 544: reference not terminated by REFC delimiter
    …D5000%26itag%3Dw160%26sigh%3DP-D2wnzUyw6NJU-bRJi_xtz2yUc&autoplay=0&ps=blogger"

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

  • Warning Line 789, Column 544: reference to external entity in attribute value
    …D5000%26itag%3Dw160%26sigh%3DP-D2wnzUyw6NJU-bRJi_xtz2yUc&autoplay=0&ps=blogger"

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

  • Error Line 789, Column 544: reference to entity "ps" for which no system identifier could be generated
    …D5000%26itag%3Dw160%26sigh%3DP-D2wnzUyw6NJU-bRJi_xtz2yUc&autoplay=0&ps=blogger"

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

  • Info Line 611, Column 541: entity was defined here
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"
  • Error Line 790, Column 25: element "embed" undefined
    allowFullScreen="true" /></object>

    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).
  • Error Line 791, Column 395: end tag for "img" omitted, but OMITTAG NO was specified
    …ss="BLOG_mobile_video_class" id="BLOG_mobile_video-8fa4a26ad18298e8"></a></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 ">".

  • Info Line 791, Column 119: start tag was here
    …==/0/0/0/video.3gp" type="video/3gpp"><img width="320" height="266" alt="video…
  • Error Line 870, Column 37: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div id='summary1460299007597681799'>

    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>").

  • Error Line 872, Column 298: end tag for "param" omitted, but OMITTAG NO was specified
    …cab#version=6,0,40,0"><param name="movie" value="//www.youtube.com/get_player">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 872, Column 241: start tag was here
    …s/flash/swflash.cab#version=6,0,40,0"><param name="movie" value="//www.youtube…
  • Error Line 873, Column 39: end tag for "param" omitted, but OMITTAG NO was specified
    <param name="bgcolor" value="#FFFFFF">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 873, Column 1: start tag was here
    <param name="bgcolor" value="#FFFFFF">
  • Error Line 874, Column 44: end tag for "param" omitted, but OMITTAG NO was specified
    <param name="allowfullscreen" value="true">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 874, Column 1: start tag was here
    <param name="allowfullscreen" value="true">
  • Error Line 875, Column 586: end tag for "param" omitted, but OMITTAG NO was specified
    …tag%3Dw160%26sigh%3DSm2A8EU_kdmcu2gptph8aFuIV9I&amp;autoplay=0&amp;ps=blogger">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 875, Column 1: start tag was here
    <param name="flashvars" value="flvurl=http://redirector.googlevideo.com/videopl…
  • Warning Line 878, Column 375: reference not terminated by REFC delimiter
    …335516298A632D0B8CE26%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Warning Line 878, Column 375: reference to external entity in attribute value
    …335516298A632D0B8CE26%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Error Line 878, Column 375: reference to entity "iurl" for which no system identifier could be generated
    …335516298A632D0B8CE26%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Info Line 611, Column 370: entity was defined here
    …D5FA5BF22D7FFFDBF017BD1658%26key%3Dck2&iurl=http://video.google.com/ThumbnailS…
  • Warning Line 878, Column 539: reference not terminated by REFC delimiter
    …D5000%26itag%3Dw160%26sigh%3DSm2A8EU_kdmcu2gptph8aFuIV9I&autoplay=0&ps=blogger"

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

  • Warning Line 878, Column 539: reference to external entity in attribute value
    …D5000%26itag%3Dw160%26sigh%3DSm2A8EU_kdmcu2gptph8aFuIV9I&autoplay=0&ps=blogger"

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

  • Error Line 878, Column 539: reference to entity "autoplay" for which no system identifier could be generated
    …D5000%26itag%3Dw160%26sigh%3DSm2A8EU_kdmcu2gptph8aFuIV9I&autoplay=0&ps=blogger"

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

  • Info Line 611, Column 530: entity was defined here
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"
  • Warning Line 878, Column 544: reference not terminated by REFC delimiter
    …D5000%26itag%3Dw160%26sigh%3DSm2A8EU_kdmcu2gptph8aFuIV9I&autoplay=0&ps=blogger"

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

  • Warning Line 878, Column 544: reference to external entity in attribute value
    …D5000%26itag%3Dw160%26sigh%3DSm2A8EU_kdmcu2gptph8aFuIV9I&autoplay=0&ps=blogger"

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

  • Error Line 878, Column 544: reference to entity "ps" for which no system identifier could be generated
    …D5000%26itag%3Dw160%26sigh%3DSm2A8EU_kdmcu2gptph8aFuIV9I&autoplay=0&ps=blogger"

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

  • Info Line 611, Column 541: entity was defined here
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"
  • Error Line 879, Column 25: element "embed" undefined
    allowFullScreen="true" /></object>

    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).
  • Error Line 880, Column 395: end tag for "img" omitted, but OMITTAG NO was specified
    …ss="BLOG_mobile_video_class" id="BLOG_mobile_video-fbbd0b2c98aa121e"></a></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 ">".

  • Info Line 880, Column 119: start tag was here
    …==/0/0/0/video.3gp" type="video/3gpp"><img width="320" height="266" alt="video…
  • Error Line 959, Column 37: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div id='summary7588082026277262817'>

    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>").

  • Error Line 961, Column 298: end tag for "param" omitted, but OMITTAG NO was specified
    …cab#version=6,0,40,0"><param name="movie" value="//www.youtube.com/get_player">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 961, Column 241: start tag was here
    …s/flash/swflash.cab#version=6,0,40,0"><param name="movie" value="//www.youtube…
  • Error Line 962, Column 39: end tag for "param" omitted, but OMITTAG NO was specified
    <param name="bgcolor" value="#FFFFFF">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 962, Column 1: start tag was here
    <param name="bgcolor" value="#FFFFFF">
  • Error Line 963, Column 44: end tag for "param" omitted, but OMITTAG NO was specified
    <param name="allowfullscreen" value="true">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 963, Column 1: start tag was here
    <param name="allowfullscreen" value="true">
  • Error Line 964, Column 586: end tag for "param" omitted, but OMITTAG NO was specified
    …tag%3Dw160%26sigh%3DPZpZULqpQsKh0-4G4jLJwVcLkTw&amp;autoplay=0&amp;ps=blogger">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 964, Column 1: start tag was here
    <param name="flashvars" value="flvurl=http://redirector.googlevideo.com/videopl…
  • Warning Line 967, Column 375: reference not terminated by REFC delimiter
    …AF5C9D044766077E401B9%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Warning Line 967, Column 375: reference to external entity in attribute value
    …AF5C9D044766077E401B9%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Error Line 967, Column 375: reference to entity "iurl" for which no system identifier could be generated
    …AF5C9D044766077E401B9%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Info Line 611, Column 370: entity was defined here
    …D5FA5BF22D7FFFDBF017BD1658%26key%3Dck2&iurl=http://video.google.com/ThumbnailS…
  • Warning Line 967, Column 539: reference not terminated by REFC delimiter
    …D5000%26itag%3Dw160%26sigh%3DPZpZULqpQsKh0-4G4jLJwVcLkTw&autoplay=0&ps=blogger"

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

  • Warning Line 967, Column 539: reference to external entity in attribute value
    …D5000%26itag%3Dw160%26sigh%3DPZpZULqpQsKh0-4G4jLJwVcLkTw&autoplay=0&ps=blogger"

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

  • Error Line 967, Column 539: reference to entity "autoplay" for which no system identifier could be generated
    …D5000%26itag%3Dw160%26sigh%3DPZpZULqpQsKh0-4G4jLJwVcLkTw&autoplay=0&ps=blogger"

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

  • Info Line 611, Column 530: entity was defined here
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"
  • Warning Line 967, Column 544: reference not terminated by REFC delimiter
    …D5000%26itag%3Dw160%26sigh%3DPZpZULqpQsKh0-4G4jLJwVcLkTw&autoplay=0&ps=blogger"

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

  • Warning Line 967, Column 544: reference to external entity in attribute value
    …D5000%26itag%3Dw160%26sigh%3DPZpZULqpQsKh0-4G4jLJwVcLkTw&autoplay=0&ps=blogger"

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

  • Error Line 967, Column 544: reference to entity "ps" for which no system identifier could be generated
    …D5000%26itag%3Dw160%26sigh%3DPZpZULqpQsKh0-4G4jLJwVcLkTw&autoplay=0&ps=blogger"

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

  • Info Line 611, Column 541: entity was defined here
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"
  • Error Line 968, Column 25: element "embed" undefined
    allowFullScreen="true" /></object>

    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).
  • Error Line 969, Column 395: end tag for "img" omitted, but OMITTAG NO was specified
    …ss="BLOG_mobile_video_class" id="BLOG_mobile_video-a2aa4d807fa2b251"></a></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 ">".

  • Info Line 969, Column 119: start tag was here
    …==/0/0/0/video.3gp" type="video/3gpp"><img width="320" height="266" alt="video…
  • Error Line 1048, Column 37: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div id='summary4678387705344508455'>

    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>").

  • Error Line 1050, Column 298: end tag for "param" omitted, but OMITTAG NO was specified
    …cab#version=6,0,40,0"><param name="movie" value="//www.youtube.com/get_player">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 1050, Column 241: start tag was here
    …s/flash/swflash.cab#version=6,0,40,0"><param name="movie" value="//www.youtube…
  • Error Line 1051, Column 39: end tag for "param" omitted, but OMITTAG NO was specified
    <param name="bgcolor" value="#FFFFFF">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 1051, Column 1: start tag was here
    <param name="bgcolor" value="#FFFFFF">
  • Error Line 1052, Column 44: end tag for "param" omitted, but OMITTAG NO was specified
    <param name="allowfullscreen" value="true">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 1052, Column 1: start tag was here
    <param name="allowfullscreen" value="true">
  • Error Line 1053, Column 586: end tag for "param" omitted, but OMITTAG NO was specified
    …tag%3Dw160%26sigh%3Dd__7yPgwd1D6oiZ-7JCkWFpm2SY&amp;autoplay=0&amp;ps=blogger">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 1053, Column 1: start tag was here
    <param name="flashvars" value="flvurl=http://redirector.googlevideo.com/videopl…
  • Warning Line 1056, Column 375: reference not terminated by REFC delimiter
    …A486E4C4DB985BD6D1640%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Warning Line 1056, Column 375: reference to external entity in attribute value
    …A486E4C4DB985BD6D1640%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Error Line 1056, Column 375: reference to entity "iurl" for which no system identifier could be generated
    …A486E4C4DB985BD6D1640%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Info Line 611, Column 370: entity was defined here
    …D5FA5BF22D7FFFDBF017BD1658%26key%3Dck2&iurl=http://video.google.com/ThumbnailS…
  • Warning Line 1056, Column 539: reference not terminated by REFC delimiter
    …D5000%26itag%3Dw160%26sigh%3Dd__7yPgwd1D6oiZ-7JCkWFpm2SY&autoplay=0&ps=blogger"

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

  • Warning Line 1056, Column 539: reference to external entity in attribute value
    …D5000%26itag%3Dw160%26sigh%3Dd__7yPgwd1D6oiZ-7JCkWFpm2SY&autoplay=0&ps=blogger"

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

  • Error Line 1056, Column 539: reference to entity "autoplay" for which no system identifier could be generated
    …D5000%26itag%3Dw160%26sigh%3Dd__7yPgwd1D6oiZ-7JCkWFpm2SY&autoplay=0&ps=blogger"

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

  • Info Line 611, Column 530: entity was defined here
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"
  • Warning Line 1056, Column 544: reference not terminated by REFC delimiter
    …D5000%26itag%3Dw160%26sigh%3Dd__7yPgwd1D6oiZ-7JCkWFpm2SY&autoplay=0&ps=blogger"

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

  • Warning Line 1056, Column 544: reference to external entity in attribute value
    …D5000%26itag%3Dw160%26sigh%3Dd__7yPgwd1D6oiZ-7JCkWFpm2SY&autoplay=0&ps=blogger"

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

  • Error Line 1056, Column 544: reference to entity "ps" for which no system identifier could be generated
    …D5000%26itag%3Dw160%26sigh%3Dd__7yPgwd1D6oiZ-7JCkWFpm2SY&autoplay=0&ps=blogger"

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

  • Info Line 611, Column 541: entity was defined here
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"
  • Error Line 1057, Column 25: element "embed" undefined
    allowFullScreen="true" /></object>

    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).
  • Error Line 1058, Column 395: end tag for "img" omitted, but OMITTAG NO was specified
    …ss="BLOG_mobile_video_class" id="BLOG_mobile_video-15024f512a4555a9"></a></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 ">".

  • Info Line 1058, Column 119: start tag was here
    …==/0/0/0/video.3gp" type="video/3gpp"><img width="320" height="266" alt="video…
  • Error Line 1137, Column 37: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div id='summary1248438784908613942'>

    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>").

  • Error Line 1139, Column 298: end tag for "param" omitted, but OMITTAG NO was specified
    …cab#version=6,0,40,0"><param name="movie" value="//www.youtube.com/get_player">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 1139, Column 241: start tag was here
    …s/flash/swflash.cab#version=6,0,40,0"><param name="movie" value="//www.youtube…
  • Error Line 1140, Column 39: end tag for "param" omitted, but OMITTAG NO was specified
    <param name="bgcolor" value="#FFFFFF">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 1140, Column 1: start tag was here
    <param name="bgcolor" value="#FFFFFF">
  • Error Line 1141, Column 44: end tag for "param" omitted, but OMITTAG NO was specified
    <param name="allowfullscreen" value="true">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 1141, Column 1: start tag was here
    <param name="allowfullscreen" value="true">
  • Error Line 1142, Column 586: end tag for "param" omitted, but OMITTAG NO was specified
    …tag%3Dw160%26sigh%3DBha4lJcVy1C5zazZr0P-0bzDQlE&amp;autoplay=0&amp;ps=blogger">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 1142, Column 1: start tag was here
    <param name="flashvars" value="flvurl=http://redirector.googlevideo.com/videopl…
  • Warning Line 1145, Column 375: reference not terminated by REFC delimiter
    …72C4627299055B9211C44%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Warning Line 1145, Column 375: reference to external entity in attribute value
    …72C4627299055B9211C44%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Error Line 1145, Column 375: reference to entity "iurl" for which no system identifier could be generated
    …72C4627299055B9211C44%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Info Line 611, Column 370: entity was defined here
    …D5FA5BF22D7FFFDBF017BD1658%26key%3Dck2&iurl=http://video.google.com/ThumbnailS…
  • Warning Line 1145, Column 539: reference not terminated by REFC delimiter
    …D5000%26itag%3Dw160%26sigh%3DBha4lJcVy1C5zazZr0P-0bzDQlE&autoplay=0&ps=blogger"

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

  • Warning Line 1145, Column 539: reference to external entity in attribute value
    …D5000%26itag%3Dw160%26sigh%3DBha4lJcVy1C5zazZr0P-0bzDQlE&autoplay=0&ps=blogger"

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

  • Error Line 1145, Column 539: reference to entity "autoplay" for which no system identifier could be generated
    …D5000%26itag%3Dw160%26sigh%3DBha4lJcVy1C5zazZr0P-0bzDQlE&autoplay=0&ps=blogger"

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

  • Info Line 611, Column 530: entity was defined here
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"
  • Warning Line 1145, Column 544: reference not terminated by REFC delimiter
    …D5000%26itag%3Dw160%26sigh%3DBha4lJcVy1C5zazZr0P-0bzDQlE&autoplay=0&ps=blogger"

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

  • Warning Line 1145, Column 544: reference to external entity in attribute value
    …D5000%26itag%3Dw160%26sigh%3DBha4lJcVy1C5zazZr0P-0bzDQlE&autoplay=0&ps=blogger"

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

  • Error Line 1145, Column 544: reference to entity "ps" for which no system identifier could be generated
    …D5000%26itag%3Dw160%26sigh%3DBha4lJcVy1C5zazZr0P-0bzDQlE&autoplay=0&ps=blogger"

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

  • Info Line 611, Column 541: entity was defined here
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"
  • Error Line 1146, Column 25: element "embed" undefined
    allowFullScreen="true" /></object>

    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).
  • Error Line 1147, Column 395: end tag for "img" omitted, but OMITTAG NO was specified
    …ss="BLOG_mobile_video_class" id="BLOG_mobile_video-b9409ab1a31f584a"></a></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 ">".

  • Info Line 1147, Column 119: start tag was here
    …==/0/0/0/video.3gp" type="video/3gpp"><img width="320" height="266" alt="video…
  • Error Line 1226, Column 37: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div id='summary8809615324966940331'>

    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>").

  • Error Line 1228, Column 298: end tag for "param" omitted, but OMITTAG NO was specified
    …cab#version=6,0,40,0"><param name="movie" value="//www.youtube.com/get_player">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 1228, Column 241: start tag was here
    …s/flash/swflash.cab#version=6,0,40,0"><param name="movie" value="//www.youtube…
  • Error Line 1229, Column 39: end tag for "param" omitted, but OMITTAG NO was specified
    <param name="bgcolor" value="#FFFFFF">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 1229, Column 1: start tag was here
    <param name="bgcolor" value="#FFFFFF">
  • Error Line 1230, Column 44: end tag for "param" omitted, but OMITTAG NO was specified
    <param name="allowfullscreen" value="true">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 1230, Column 1: start tag was here
    <param name="allowfullscreen" value="true">
  • Error Line 1231, Column 585: end tag for "param" omitted, but OMITTAG NO was specified
    …tag%3Dw160%26sigh%3DzllDKGtMYoHP3lEgEmNp0X20Ev4&amp;autoplay=0&amp;ps=blogger">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 1231, Column 1: start tag was here
    <param name="flashvars" value="flvurl=http://redirector.googlevideo.com/videopl…
  • Warning Line 1234, Column 374: reference not terminated by REFC delimiter
    …F12CF606008BF9D559953%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Warning Line 1234, Column 374: reference to external entity in attribute value
    …F12CF606008BF9D559953%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Error Line 1234, Column 374: reference to entity "iurl" for which no system identifier could be generated
    …F12CF606008BF9D559953%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Info Line 611, Column 370: entity was defined here
    …D5FA5BF22D7FFFDBF017BD1658%26key%3Dck2&iurl=http://video.google.com/ThumbnailS…
  • Warning Line 1234, Column 538: reference not terminated by REFC delimiter
    …D5000%26itag%3Dw160%26sigh%3DzllDKGtMYoHP3lEgEmNp0X20Ev4&autoplay=0&ps=blogger"

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

  • Warning Line 1234, Column 538: reference to external entity in attribute value
    …D5000%26itag%3Dw160%26sigh%3DzllDKGtMYoHP3lEgEmNp0X20Ev4&autoplay=0&ps=blogger"

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

  • Error Line 1234, Column 538: reference to entity "autoplay" for which no system identifier could be generated
    …D5000%26itag%3Dw160%26sigh%3DzllDKGtMYoHP3lEgEmNp0X20Ev4&autoplay=0&ps=blogger"

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

  • Info Line 611, Column 530: entity was defined here
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"
  • Warning Line 1234, Column 543: reference not terminated by REFC delimiter
    …D5000%26itag%3Dw160%26sigh%3DzllDKGtMYoHP3lEgEmNp0X20Ev4&autoplay=0&ps=blogger"

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

  • Warning Line 1234, Column 543: reference to external entity in attribute value
    …D5000%26itag%3Dw160%26sigh%3DzllDKGtMYoHP3lEgEmNp0X20Ev4&autoplay=0&ps=blogger"

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

  • Error Line 1234, Column 543: reference to entity "ps" for which no system identifier could be generated
    …D5000%26itag%3Dw160%26sigh%3DzllDKGtMYoHP3lEgEmNp0X20Ev4&autoplay=0&ps=blogger"

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

  • Info Line 611, Column 541: entity was defined here
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"
  • Error Line 1235, Column 25: element "embed" undefined
    allowFullScreen="true" /></object>

    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).
  • Error Line 1236, Column 395: end tag for "img" omitted, but OMITTAG NO was specified
    …ss="BLOG_mobile_video_class" id="BLOG_mobile_video-167d7fe104e2eee1"></a></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 ">".

  • Info Line 1236, Column 119: start tag was here
    …==/0/0/0/video.3gp" type="video/3gpp"><img width="320" height="266" alt="video…
  • Error Line 1315, Column 37: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div id='summary8398565452238017199'>

    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>").

  • Error Line 1317, Column 298: end tag for "param" omitted, but OMITTAG NO was specified
    …cab#version=6,0,40,0"><param name="movie" value="//www.youtube.com/get_player">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 1317, Column 241: start tag was here
    …s/flash/swflash.cab#version=6,0,40,0"><param name="movie" value="//www.youtube…
  • Error Line 1318, Column 39: end tag for "param" omitted, but OMITTAG NO was specified
    <param name="bgcolor" value="#FFFFFF">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 1318, Column 1: start tag was here
    <param name="bgcolor" value="#FFFFFF">
  • Error Line 1319, Column 44: end tag for "param" omitted, but OMITTAG NO was specified
    <param name="allowfullscreen" value="true">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 1319, Column 1: start tag was here
    <param name="allowfullscreen" value="true">
  • Error Line 1320, Column 586: end tag for "param" omitted, but OMITTAG NO was specified
    …tag%3Dw160%26sigh%3Dw7paTvSC_xrpNPgbJqRnNL2o8rU&amp;autoplay=0&amp;ps=blogger">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 1320, Column 1: start tag was here
    <param name="flashvars" value="flvurl=http://redirector.googlevideo.com/videopl…
  • Warning Line 1323, Column 375: reference not terminated by REFC delimiter
    …9389797839FAABBF4B0BF%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Warning Line 1323, Column 375: reference to external entity in attribute value
    …9389797839FAABBF4B0BF%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Error Line 1323, Column 375: reference to entity "iurl" for which no system identifier could be generated
    …9389797839FAABBF4B0BF%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Info Line 611, Column 370: entity was defined here
    …D5FA5BF22D7FFFDBF017BD1658%26key%3Dck2&iurl=http://video.google.com/ThumbnailS…
  • Warning Line 1323, Column 539: reference not terminated by REFC delimiter
    …D5000%26itag%3Dw160%26sigh%3Dw7paTvSC_xrpNPgbJqRnNL2o8rU&autoplay=0&ps=blogger"

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

  • Warning Line 1323, Column 539: reference to external entity in attribute value
    …D5000%26itag%3Dw160%26sigh%3Dw7paTvSC_xrpNPgbJqRnNL2o8rU&autoplay=0&ps=blogger"

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

  • Error Line 1323, Column 539: reference to entity "autoplay" for which no system identifier could be generated
    …D5000%26itag%3Dw160%26sigh%3Dw7paTvSC_xrpNPgbJqRnNL2o8rU&autoplay=0&ps=blogger"

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

  • Info Line 611, Column 530: entity was defined here
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"
  • Warning Line 1323, Column 544: reference not terminated by REFC delimiter
    …D5000%26itag%3Dw160%26sigh%3Dw7paTvSC_xrpNPgbJqRnNL2o8rU&autoplay=0&ps=blogger"

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

  • Warning Line 1323, Column 544: reference to external entity in attribute value
    …D5000%26itag%3Dw160%26sigh%3Dw7paTvSC_xrpNPgbJqRnNL2o8rU&autoplay=0&ps=blogger"

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

  • Error Line 1323, Column 544: reference to entity "ps" for which no system identifier could be generated
    …D5000%26itag%3Dw160%26sigh%3Dw7paTvSC_xrpNPgbJqRnNL2o8rU&autoplay=0&ps=blogger"

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

  • Info Line 611, Column 541: entity was defined here
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"
  • Error Line 1324, Column 25: element "embed" undefined
    allowFullScreen="true" /></object>

    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).
  • Error Line 1325, Column 395: end tag for "img" omitted, but OMITTAG NO was specified
    …ss="BLOG_mobile_video_class" id="BLOG_mobile_video-a6b8f4336d7d6fd7"></a></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 ">".

  • Info Line 1325, Column 119: start tag was here
    …==/0/0/0/video.3gp" type="video/3gpp"><img width="320" height="266" alt="video…
  • Error Line 1404, Column 37: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div id='summary6593916330398369932'>

    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>").

  • Error Line 1406, Column 298: end tag for "param" omitted, but OMITTAG NO was specified
    …cab#version=6,0,40,0"><param name="movie" value="//www.youtube.com/get_player">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 1406, Column 241: start tag was here
    …s/flash/swflash.cab#version=6,0,40,0"><param name="movie" value="//www.youtube…
  • Error Line 1407, Column 39: end tag for "param" omitted, but OMITTAG NO was specified
    <param name="bgcolor" value="#FFFFFF">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 1407, Column 1: start tag was here
    <param name="bgcolor" value="#FFFFFF">
  • Error Line 1408, Column 44: end tag for "param" omitted, but OMITTAG NO was specified
    <param name="allowfullscreen" value="true">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 1408, Column 1: start tag was here
    <param name="allowfullscreen" value="true">
  • Error Line 1409, Column 586: end tag for "param" omitted, but OMITTAG NO was specified
    …tag%3Dw160%26sigh%3DSQc1DC4EqGdeg3SkqbsF51PynxE&amp;autoplay=0&amp;ps=blogger">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 1409, Column 1: start tag was here
    <param name="flashvars" value="flvurl=http://redirector.googlevideo.com/videopl…
  • Warning Line 1412, Column 375: reference not terminated by REFC delimiter
    …DDBAEE8788EBF77B4092E%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Warning Line 1412, Column 375: reference to external entity in attribute value
    …DDBAEE8788EBF77B4092E%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Error Line 1412, Column 375: reference to entity "iurl" for which no system identifier could be generated
    …DDBAEE8788EBF77B4092E%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Info Line 611, Column 370: entity was defined here
    …D5FA5BF22D7FFFDBF017BD1658%26key%3Dck2&iurl=http://video.google.com/ThumbnailS…
  • Warning Line 1412, Column 539: reference not terminated by REFC delimiter
    …D5000%26itag%3Dw160%26sigh%3DSQc1DC4EqGdeg3SkqbsF51PynxE&autoplay=0&ps=blogger"

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

  • Warning Line 1412, Column 539: reference to external entity in attribute value
    …D5000%26itag%3Dw160%26sigh%3DSQc1DC4EqGdeg3SkqbsF51PynxE&autoplay=0&ps=blogger"

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

  • Error Line 1412, Column 539: reference to entity "autoplay" for which no system identifier could be generated
    …D5000%26itag%3Dw160%26sigh%3DSQc1DC4EqGdeg3SkqbsF51PynxE&autoplay=0&ps=blogger"

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

  • Info Line 611, Column 530: entity was defined here
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"
  • Warning Line 1412, Column 544: reference not terminated by REFC delimiter
    …D5000%26itag%3Dw160%26sigh%3DSQc1DC4EqGdeg3SkqbsF51PynxE&autoplay=0&ps=blogger"

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

  • Warning Line 1412, Column 544: reference to external entity in attribute value
    …D5000%26itag%3Dw160%26sigh%3DSQc1DC4EqGdeg3SkqbsF51PynxE&autoplay=0&ps=blogger"

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

  • Error Line 1412, Column 544: reference to entity "ps" for which no system identifier could be generated
    …D5000%26itag%3Dw160%26sigh%3DSQc1DC4EqGdeg3SkqbsF51PynxE&autoplay=0&ps=blogger"

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

  • Info Line 611, Column 541: entity was defined here
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"
  • Error Line 1413, Column 25: element "embed" undefined
    allowFullScreen="true" /></object>

    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).
  • Error Line 1414, Column 395: end tag for "img" omitted, but OMITTAG NO was specified
    …ss="BLOG_mobile_video_class" id="BLOG_mobile_video-76a938639a74cb35"></a></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 ">".

  • Info Line 1414, Column 119: start tag was here
    …==/0/0/0/video.3gp" type="video/3gpp"><img width="320" height="266" alt="video…
  • Error Line 1493, Column 37: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div id='summary3210135192818391183'>

    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>").

  • Error Line 1495, Column 298: end tag for "param" omitted, but OMITTAG NO was specified
    …cab#version=6,0,40,0"><param name="movie" value="//www.youtube.com/get_player">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 1495, Column 241: start tag was here
    …s/flash/swflash.cab#version=6,0,40,0"><param name="movie" value="//www.youtube…
  • Error Line 1496, Column 39: end tag for "param" omitted, but OMITTAG NO was specified
    <param name="bgcolor" value="#FFFFFF">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 1496, Column 1: start tag was here
    <param name="bgcolor" value="#FFFFFF">
  • Error Line 1497, Column 44: end tag for "param" omitted, but OMITTAG NO was specified
    <param name="allowfullscreen" value="true">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 1497, Column 1: start tag was here
    <param name="allowfullscreen" value="true">
  • Error Line 1498, Column 586: end tag for "param" omitted, but OMITTAG NO was specified
    …tag%3Dw160%26sigh%3Dw4JR5O5o57iDM8HI47JZ5EsF01I&amp;autoplay=0&amp;ps=blogger">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 1498, Column 1: start tag was here
    <param name="flashvars" value="flvurl=http://redirector.googlevideo.com/videopl…
  • Warning Line 1501, Column 375: reference not terminated by REFC delimiter
    …305CD07B4F4C47B006977%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Warning Line 1501, Column 375: reference to external entity in attribute value
    …305CD07B4F4C47B006977%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Error Line 1501, Column 375: reference to entity "iurl" for which no system identifier could be generated
    …305CD07B4F4C47B006977%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Info Line 611, Column 370: entity was defined here
    …D5FA5BF22D7FFFDBF017BD1658%26key%3Dck2&iurl=http://video.google.com/ThumbnailS…
  • Warning Line 1501, Column 539: reference not terminated by REFC delimiter
    …D5000%26itag%3Dw160%26sigh%3Dw4JR5O5o57iDM8HI47JZ5EsF01I&autoplay=0&ps=blogger"

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

  • Warning Line 1501, Column 539: reference to external entity in attribute value
    …D5000%26itag%3Dw160%26sigh%3Dw4JR5O5o57iDM8HI47JZ5EsF01I&autoplay=0&ps=blogger"

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

  • Error Line 1501, Column 539: reference to entity "autoplay" for which no system identifier could be generated
    …D5000%26itag%3Dw160%26sigh%3Dw4JR5O5o57iDM8HI47JZ5EsF01I&autoplay=0&ps=blogger"

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

  • Info Line 611, Column 530: entity was defined here
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"
  • Warning Line 1501, Column 544: reference not terminated by REFC delimiter
    …D5000%26itag%3Dw160%26sigh%3Dw4JR5O5o57iDM8HI47JZ5EsF01I&autoplay=0&ps=blogger"

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

  • Warning Line 1501, Column 544: reference to external entity in attribute value
    …D5000%26itag%3Dw160%26sigh%3Dw4JR5O5o57iDM8HI47JZ5EsF01I&autoplay=0&ps=blogger"

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

  • Error Line 1501, Column 544: reference to entity "ps" for which no system identifier could be generated
    …D5000%26itag%3Dw160%26sigh%3Dw4JR5O5o57iDM8HI47JZ5EsF01I&autoplay=0&ps=blogger"

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

  • Info Line 611, Column 541: entity was defined here
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"
  • Error Line 1502, Column 25: element "embed" undefined
    allowFullScreen="true" /></object>

    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).
  • Error Line 1503, Column 395: end tag for "img" omitted, but OMITTAG NO was specified
    …ss="BLOG_mobile_video_class" id="BLOG_mobile_video-c4549227c49fbda4"></a></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 ">".

  • Info Line 1503, Column 119: start tag was here
    …==/0/0/0/video.3gp" type="video/3gpp"><img width="320" height="266" alt="video…
  • Error Line 1582, Column 36: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div id='summary873999180391458215'>

    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>").

  • Error Line 1584, Column 298: end tag for "param" omitted, but OMITTAG NO was specified
    …cab#version=6,0,40,0"><param name="movie" value="//www.youtube.com/get_player">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 1584, Column 241: start tag was here
    …s/flash/swflash.cab#version=6,0,40,0"><param name="movie" value="//www.youtube…
  • Error Line 1585, Column 39: end tag for "param" omitted, but OMITTAG NO was specified
    <param name="bgcolor" value="#FFFFFF">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 1585, Column 1: start tag was here
    <param name="bgcolor" value="#FFFFFF">
  • Error Line 1586, Column 44: end tag for "param" omitted, but OMITTAG NO was specified
    <param name="allowfullscreen" value="true">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 1586, Column 1: start tag was here
    <param name="allowfullscreen" value="true">
  • Error Line 1587, Column 586: end tag for "param" omitted, but OMITTAG NO was specified
    …tag%3Dw160%26sigh%3DaC76lZ5SVySF09FZBm0t0OWBG28&amp;autoplay=0&amp;ps=blogger">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 1587, Column 1: start tag was here
    <param name="flashvars" value="flvurl=http://redirector.googlevideo.com/videopl…
  • Warning Line 1590, Column 375: reference not terminated by REFC delimiter
    …C3A6CA8800F8D7605B52B%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Warning Line 1590, Column 375: reference to external entity in attribute value
    …C3A6CA8800F8D7605B52B%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Error Line 1590, Column 375: reference to entity "iurl" for which no system identifier could be generated
    …C3A6CA8800F8D7605B52B%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Info Line 611, Column 370: entity was defined here
    …D5FA5BF22D7FFFDBF017BD1658%26key%3Dck2&iurl=http://video.google.com/ThumbnailS…
  • Warning Line 1590, Column 539: reference not terminated by REFC delimiter
    …D5000%26itag%3Dw160%26sigh%3DaC76lZ5SVySF09FZBm0t0OWBG28&autoplay=0&ps=blogger"

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

  • Warning Line 1590, Column 539: reference to external entity in attribute value
    …D5000%26itag%3Dw160%26sigh%3DaC76lZ5SVySF09FZBm0t0OWBG28&autoplay=0&ps=blogger"

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

  • Error Line 1590, Column 539: reference to entity "autoplay" for which no system identifier could be generated
    …D5000%26itag%3Dw160%26sigh%3DaC76lZ5SVySF09FZBm0t0OWBG28&autoplay=0&ps=blogger"

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

  • Info Line 611, Column 530: entity was defined here
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"
  • Warning Line 1590, Column 544: reference not terminated by REFC delimiter
    …D5000%26itag%3Dw160%26sigh%3DaC76lZ5SVySF09FZBm0t0OWBG28&autoplay=0&ps=blogger"

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

  • Warning Line 1590, Column 544: reference to external entity in attribute value
    …D5000%26itag%3Dw160%26sigh%3DaC76lZ5SVySF09FZBm0t0OWBG28&autoplay=0&ps=blogger"

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

  • Error Line 1590, Column 544: reference to entity "ps" for which no system identifier could be generated
    …D5000%26itag%3Dw160%26sigh%3DaC76lZ5SVySF09FZBm0t0OWBG28&autoplay=0&ps=blogger"

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

  • Info Line 611, Column 541: entity was defined here
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"
  • Error Line 1591, Column 25: element "embed" undefined
    allowFullScreen="true" /></object>

    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).
  • Error Line 1592, Column 395: end tag for "img" omitted, but OMITTAG NO was specified
    …ss="BLOG_mobile_video_class" id="BLOG_mobile_video-2d53dfdcd0b7341d"></a></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 ">".

  • Info Line 1592, Column 119: start tag was here
    …==/0/0/0/video.3gp" type="video/3gpp"><img width="320" height="266" alt="video…
  • Error Line 1671, Column 37: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div id='summary2987454808030505069'>

    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>").

  • Error Line 1673, Column 298: end tag for "param" omitted, but OMITTAG NO was specified
    …cab#version=6,0,40,0"><param name="movie" value="//www.youtube.com/get_player">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 1673, Column 241: start tag was here
    …s/flash/swflash.cab#version=6,0,40,0"><param name="movie" value="//www.youtube…
  • Error Line 1674, Column 39: end tag for "param" omitted, but OMITTAG NO was specified
    <param name="bgcolor" value="#FFFFFF">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 1674, Column 1: start tag was here
    <param name="bgcolor" value="#FFFFFF">
  • Error Line 1675, Column 44: end tag for "param" omitted, but OMITTAG NO was specified
    <param name="allowfullscreen" value="true">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 1675, Column 1: start tag was here
    <param name="allowfullscreen" value="true">
  • Error Line 1676, Column 586: end tag for "param" omitted, but OMITTAG NO was specified
    …tag%3Dw160%26sigh%3DKSL1CCTgP0LOLya_R56ohc2NMWA&amp;autoplay=0&amp;ps=blogger">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 1676, Column 1: start tag was here
    <param name="flashvars" value="flvurl=http://redirector.googlevideo.com/videopl…
  • Warning Line 1679, Column 375: reference not terminated by REFC delimiter
    …FFBCD6F2225E448C9780E%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Warning Line 1679, Column 375: reference to external entity in attribute value
    …FFBCD6F2225E448C9780E%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Error Line 1679, Column 375: reference to entity "iurl" for which no system identifier could be generated
    …FFBCD6F2225E448C9780E%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Info Line 611, Column 370: entity was defined here
    …D5FA5BF22D7FFFDBF017BD1658%26key%3Dck2&iurl=http://video.google.com/ThumbnailS…
  • Warning Line 1679, Column 539: reference not terminated by REFC delimiter
    …D5000%26itag%3Dw160%26sigh%3DKSL1CCTgP0LOLya_R56ohc2NMWA&autoplay=0&ps=blogger"

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

  • Warning Line 1679, Column 539: reference to external entity in attribute value
    …D5000%26itag%3Dw160%26sigh%3DKSL1CCTgP0LOLya_R56ohc2NMWA&autoplay=0&ps=blogger"

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

  • Error Line 1679, Column 539: reference to entity "autoplay" for which no system identifier could be generated
    …D5000%26itag%3Dw160%26sigh%3DKSL1CCTgP0LOLya_R56ohc2NMWA&autoplay=0&ps=blogger"

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

  • Info Line 611, Column 530: entity was defined here
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"
  • Warning Line 1679, Column 544: reference not terminated by REFC delimiter
    …D5000%26itag%3Dw160%26sigh%3DKSL1CCTgP0LOLya_R56ohc2NMWA&autoplay=0&ps=blogger"

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

  • Warning Line 1679, Column 544: reference to external entity in attribute value
    …D5000%26itag%3Dw160%26sigh%3DKSL1CCTgP0LOLya_R56ohc2NMWA&autoplay=0&ps=blogger"

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

  • Error Line 1679, Column 544: reference to entity "ps" for which no system identifier could be generated
    …D5000%26itag%3Dw160%26sigh%3DKSL1CCTgP0LOLya_R56ohc2NMWA&autoplay=0&ps=blogger"

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

  • Info Line 611, Column 541: entity was defined here
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"
  • Error Line 1680, Column 25: element "embed" undefined
    allowFullScreen="true" /></object>

    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).
  • Error Line 1681, Column 395: end tag for "img" omitted, but OMITTAG NO was specified
    …ss="BLOG_mobile_video_class" id="BLOG_mobile_video-fb9daec0541f366d"></a></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 ">".

  • Info Line 1681, Column 119: start tag was here
    …==/0/0/0/video.3gp" type="video/3gpp"><img width="320" height="266" alt="video…
  • Error Line 1760, Column 37: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div id='summary3353804842774699051'>

    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>").

  • Error Line 1762, Column 298: end tag for "param" omitted, but OMITTAG NO was specified
    …cab#version=6,0,40,0"><param name="movie" value="//www.youtube.com/get_player">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 1762, Column 241: start tag was here
    …s/flash/swflash.cab#version=6,0,40,0"><param name="movie" value="//www.youtube…
  • Error Line 1763, Column 39: end tag for "param" omitted, but OMITTAG NO was specified
    <param name="bgcolor" value="#FFFFFF">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 1763, Column 1: start tag was here
    <param name="bgcolor" value="#FFFFFF">
  • Error Line 1764, Column 44: end tag for "param" omitted, but OMITTAG NO was specified
    <param name="allowfullscreen" value="true">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 1764, Column 1: start tag was here
    <param name="allowfullscreen" value="true">
  • Error Line 1765, Column 586: end tag for "param" omitted, but OMITTAG NO was specified
    …tag%3Dw160%26sigh%3DLpRMjGCoZzK7D0MAbsMyIJAUkmA&amp;autoplay=0&amp;ps=blogger">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 1765, Column 1: start tag was here
    <param name="flashvars" value="flvurl=http://redirector.googlevideo.com/videopl…
  • Warning Line 1768, Column 375: reference not terminated by REFC delimiter
    …6B771285C336FA0A38A75%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Warning Line 1768, Column 375: reference to external entity in attribute value
    …6B771285C336FA0A38A75%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Error Line 1768, Column 375: reference to entity "iurl" for which no system identifier could be generated
    …6B771285C336FA0A38A75%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Info Line 611, Column 370: entity was defined here
    …D5FA5BF22D7FFFDBF017BD1658%26key%3Dck2&iurl=http://video.google.com/ThumbnailS…
  • Warning Line 1768, Column 539: reference not terminated by REFC delimiter
    …D5000%26itag%3Dw160%26sigh%3DLpRMjGCoZzK7D0MAbsMyIJAUkmA&autoplay=0&ps=blogger"

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

  • Warning Line 1768, Column 539: reference to external entity in attribute value
    …D5000%26itag%3Dw160%26sigh%3DLpRMjGCoZzK7D0MAbsMyIJAUkmA&autoplay=0&ps=blogger"

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

  • Error Line 1768, Column 539: reference to entity "autoplay" for which no system identifier could be generated
    …D5000%26itag%3Dw160%26sigh%3DLpRMjGCoZzK7D0MAbsMyIJAUkmA&autoplay=0&ps=blogger"

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

  • Info Line 611, Column 530: entity was defined here
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"
  • Warning Line 1768, Column 544: reference not terminated by REFC delimiter
    …D5000%26itag%3Dw160%26sigh%3DLpRMjGCoZzK7D0MAbsMyIJAUkmA&autoplay=0&ps=blogger"

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

  • Warning Line 1768, Column 544: reference to external entity in attribute value
    …D5000%26itag%3Dw160%26sigh%3DLpRMjGCoZzK7D0MAbsMyIJAUkmA&autoplay=0&ps=blogger"

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

  • Error Line 1768, Column 544: reference to entity "ps" for which no system identifier could be generated
    …D5000%26itag%3Dw160%26sigh%3DLpRMjGCoZzK7D0MAbsMyIJAUkmA&autoplay=0&ps=blogger"

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

  • Info Line 611, Column 541: entity was defined here
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"
  • Error Line 1769, Column 25: element "embed" undefined
    allowFullScreen="true" /></object>

    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).
  • Error Line 1770, Column 395: end tag for "img" omitted, but OMITTAG NO was specified
    …ss="BLOG_mobile_video_class" id="BLOG_mobile_video-5f96ae9666d41aa1"></a></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 ">".

  • Info Line 1770, Column 119: start tag was here
    …==/0/0/0/video.3gp" type="video/3gpp"><img width="320" height="266" alt="video…
  • Error Line 1849, Column 37: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div id='summary1327873591052742190'>

    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>").

  • Error Line 1851, Column 298: end tag for "param" omitted, but OMITTAG NO was specified
    …cab#version=6,0,40,0"><param name="movie" value="//www.youtube.com/get_player">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 1851, Column 241: start tag was here
    …s/flash/swflash.cab#version=6,0,40,0"><param name="movie" value="//www.youtube…
  • Error Line 1852, Column 39: end tag for "param" omitted, but OMITTAG NO was specified
    <param name="bgcolor" value="#FFFFFF">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 1852, Column 1: start tag was here
    <param name="bgcolor" value="#FFFFFF">
  • Error Line 1853, Column 44: end tag for "param" omitted, but OMITTAG NO was specified
    <param name="allowfullscreen" value="true">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 1853, Column 1: start tag was here
    <param name="allowfullscreen" value="true">
  • Error Line 1854, Column 586: end tag for "param" omitted, but OMITTAG NO was specified
    …tag%3Dw160%26sigh%3DhGt4oV3OktvZgY08Yz5T_wJwZJs&amp;autoplay=0&amp;ps=blogger">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 1854, Column 1: start tag was here
    <param name="flashvars" value="flvurl=http://redirector.googlevideo.com/videopl…
  • Warning Line 1857, Column 375: reference not terminated by REFC delimiter
    …73EC96A469815A8A9F193%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Warning Line 1857, Column 375: reference to external entity in attribute value
    …73EC96A469815A8A9F193%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Error Line 1857, Column 375: reference to entity "iurl" for which no system identifier could be generated
    …73EC96A469815A8A9F193%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Info Line 611, Column 370: entity was defined here
    …D5FA5BF22D7FFFDBF017BD1658%26key%3Dck2&iurl=http://video.google.com/ThumbnailS…
  • Warning Line 1857, Column 539: reference not terminated by REFC delimiter
    …D5000%26itag%3Dw160%26sigh%3DhGt4oV3OktvZgY08Yz5T_wJwZJs&autoplay=0&ps=blogger"

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

  • Warning Line 1857, Column 539: reference to external entity in attribute value
    …D5000%26itag%3Dw160%26sigh%3DhGt4oV3OktvZgY08Yz5T_wJwZJs&autoplay=0&ps=blogger"

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

  • Error Line 1857, Column 539: reference to entity "autoplay" for which no system identifier could be generated
    …D5000%26itag%3Dw160%26sigh%3DhGt4oV3OktvZgY08Yz5T_wJwZJs&autoplay=0&ps=blogger"

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

  • Info Line 611, Column 530: entity was defined here
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"
  • Warning Line 1857, Column 544: reference not terminated by REFC delimiter
    …D5000%26itag%3Dw160%26sigh%3DhGt4oV3OktvZgY08Yz5T_wJwZJs&autoplay=0&ps=blogger"

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

  • Warning Line 1857, Column 544: reference to external entity in attribute value
    …D5000%26itag%3Dw160%26sigh%3DhGt4oV3OktvZgY08Yz5T_wJwZJs&autoplay=0&ps=blogger"

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

  • Error Line 1857, Column 544: reference to entity "ps" for which no system identifier could be generated
    …D5000%26itag%3Dw160%26sigh%3DhGt4oV3OktvZgY08Yz5T_wJwZJs&autoplay=0&ps=blogger"

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

  • Info Line 611, Column 541: entity was defined here
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"
  • Error Line 1858, Column 25: element "embed" undefined
    allowFullScreen="true" /></object>

    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).
  • Error Line 1859, Column 395: end tag for "img" omitted, but OMITTAG NO was specified
    …ss="BLOG_mobile_video_class" id="BLOG_mobile_video-75c6ebc03111106e"></a></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 ">".

  • Info Line 1859, Column 119: start tag was here
    …==/0/0/0/video.3gp" type="video/3gpp"><img width="320" height="266" alt="video…
  • Error Line 1938, Column 37: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div id='summary7123092908908862075'>

    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>").

  • Error Line 1940, Column 298: end tag for "param" omitted, but OMITTAG NO was specified
    …cab#version=6,0,40,0"><param name="movie" value="//www.youtube.com/get_player">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 1940, Column 241: start tag was here
    …s/flash/swflash.cab#version=6,0,40,0"><param name="movie" value="//www.youtube…
  • Error Line 1941, Column 39: end tag for "param" omitted, but OMITTAG NO was specified
    <param name="bgcolor" value="#FFFFFF">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 1941, Column 1: start tag was here
    <param name="bgcolor" value="#FFFFFF">
  • Error Line 1942, Column 44: end tag for "param" omitted, but OMITTAG NO was specified
    <param name="allowfullscreen" value="true">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 1942, Column 1: start tag was here
    <param name="allowfullscreen" value="true">
  • Error Line 1943, Column 586: end tag for "param" omitted, but OMITTAG NO was specified
    …tag%3Dw160%26sigh%3DRhkcLtPgYFIWqR6i4LBDrRoUpio&amp;autoplay=0&amp;ps=blogger">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 1943, Column 1: start tag was here
    <param name="flashvars" value="flvurl=http://redirector.googlevideo.com/videopl…
  • Warning Line 1946, Column 375: reference not terminated by REFC delimiter
    …45044DFD152C6429A9981%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Warning Line 1946, Column 375: reference to external entity in attribute value
    …45044DFD152C6429A9981%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Error Line 1946, Column 375: reference to entity "iurl" for which no system identifier could be generated
    …45044DFD152C6429A9981%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Info Line 611, Column 370: entity was defined here
    …D5FA5BF22D7FFFDBF017BD1658%26key%3Dck2&iurl=http://video.google.com/ThumbnailS…
  • Warning Line 1946, Column 539: reference not terminated by REFC delimiter
    …D5000%26itag%3Dw160%26sigh%3DRhkcLtPgYFIWqR6i4LBDrRoUpio&autoplay=0&ps=blogger"

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

  • Warning Line 1946, Column 539: reference to external entity in attribute value
    …D5000%26itag%3Dw160%26sigh%3DRhkcLtPgYFIWqR6i4LBDrRoUpio&autoplay=0&ps=blogger"

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

  • Error Line 1946, Column 539: reference to entity "autoplay" for which no system identifier could be generated
    …D5000%26itag%3Dw160%26sigh%3DRhkcLtPgYFIWqR6i4LBDrRoUpio&autoplay=0&ps=blogger"

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

  • Info Line 611, Column 530: entity was defined here
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"
  • Warning Line 1946, Column 544: reference not terminated by REFC delimiter
    …D5000%26itag%3Dw160%26sigh%3DRhkcLtPgYFIWqR6i4LBDrRoUpio&autoplay=0&ps=blogger"

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

  • Warning Line 1946, Column 544: reference to external entity in attribute value
    …D5000%26itag%3Dw160%26sigh%3DRhkcLtPgYFIWqR6i4LBDrRoUpio&autoplay=0&ps=blogger"

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

  • Error Line 1946, Column 544: reference to entity "ps" for which no system identifier could be generated
    …D5000%26itag%3Dw160%26sigh%3DRhkcLtPgYFIWqR6i4LBDrRoUpio&autoplay=0&ps=blogger"

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

  • Info Line 611, Column 541: entity was defined here
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"
  • Error Line 1947, Column 25: element "embed" undefined
    allowFullScreen="true" /></object>

    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).
  • Error Line 1948, Column 395: end tag for "img" omitted, but OMITTAG NO was specified
    …ss="BLOG_mobile_video_class" id="BLOG_mobile_video-acdf9498df85f4ed"></a></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 ">".

  • Info Line 1948, Column 119: start tag was here
    …==/0/0/0/video.3gp" type="video/3gpp"><img width="320" height="266" alt="video…
  • Error Line 2027, Column 37: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div id='summary8751978189681681892'>

    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>").

  • Error Line 2029, Column 298: end tag for "param" omitted, but OMITTAG NO was specified
    …cab#version=6,0,40,0"><param name="movie" value="//www.youtube.com/get_player">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 2029, Column 241: start tag was here
    …s/flash/swflash.cab#version=6,0,40,0"><param name="movie" value="//www.youtube…
  • Error Line 2030, Column 39: end tag for "param" omitted, but OMITTAG NO was specified
    <param name="bgcolor" value="#FFFFFF">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 2030, Column 1: start tag was here
    <param name="bgcolor" value="#FFFFFF">
  • Error Line 2031, Column 44: end tag for "param" omitted, but OMITTAG NO was specified
    <param name="allowfullscreen" value="true">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 2031, Column 1: start tag was here
    <param name="allowfullscreen" value="true">
  • Error Line 2032, Column 586: end tag for "param" omitted, but OMITTAG NO was specified
    …tag%3Dw160%26sigh%3DmIdObdDRQfa3Dc0XdXWn15XlIy0&amp;autoplay=0&amp;ps=blogger">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 2032, Column 1: start tag was here
    <param name="flashvars" value="flvurl=http://redirector.googlevideo.com/videopl…
  • Warning Line 2035, Column 375: reference not terminated by REFC delimiter
    …19940F7D1F273D2D68896%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Warning Line 2035, Column 375: reference to external entity in attribute value
    …19940F7D1F273D2D68896%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Error Line 2035, Column 375: reference to entity "iurl" for which no system identifier could be generated
    …19940F7D1F273D2D68896%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Info Line 611, Column 370: entity was defined here
    …D5FA5BF22D7FFFDBF017BD1658%26key%3Dck2&iurl=http://video.google.com/ThumbnailS…
  • Warning Line 2035, Column 539: reference not terminated by REFC delimiter
    …D5000%26itag%3Dw160%26sigh%3DmIdObdDRQfa3Dc0XdXWn15XlIy0&autoplay=0&ps=blogger"

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

  • Warning Line 2035, Column 539: reference to external entity in attribute value
    …D5000%26itag%3Dw160%26sigh%3DmIdObdDRQfa3Dc0XdXWn15XlIy0&autoplay=0&ps=blogger"

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

  • Error Line 2035, Column 539: reference to entity "autoplay" for which no system identifier could be generated
    …D5000%26itag%3Dw160%26sigh%3DmIdObdDRQfa3Dc0XdXWn15XlIy0&autoplay=0&ps=blogger"

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

  • Info Line 611, Column 530: entity was defined here
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"
  • Warning Line 2035, Column 544: reference not terminated by REFC delimiter
    …D5000%26itag%3Dw160%26sigh%3DmIdObdDRQfa3Dc0XdXWn15XlIy0&autoplay=0&ps=blogger"

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

  • Warning Line 2035, Column 544: reference to external entity in attribute value
    …D5000%26itag%3Dw160%26sigh%3DmIdObdDRQfa3Dc0XdXWn15XlIy0&autoplay=0&ps=blogger"

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

  • Error Line 2035, Column 544: reference to entity "ps" for which no system identifier could be generated
    …D5000%26itag%3Dw160%26sigh%3DmIdObdDRQfa3Dc0XdXWn15XlIy0&autoplay=0&ps=blogger"

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

  • Info Line 611, Column 541: entity was defined here
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"
  • Error Line 2036, Column 25: element "embed" undefined
    allowFullScreen="true" /></object>

    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).
  • Error Line 2037, Column 395: end tag for "img" omitted, but OMITTAG NO was specified
    …ss="BLOG_mobile_video_class" id="BLOG_mobile_video-dafcb31f289fdac4"></a></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 ">".

  • Info Line 2037, Column 119: start tag was here
    …==/0/0/0/video.3gp" type="video/3gpp"><img width="320" height="266" alt="video…
  • Error Line 2116, Column 37: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div id='summary7517667512889728576'>

    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>").

  • Error Line 2118, Column 298: end tag for "param" omitted, but OMITTAG NO was specified
    …cab#version=6,0,40,0"><param name="movie" value="//www.youtube.com/get_player">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 2118, Column 241: start tag was here
    …s/flash/swflash.cab#version=6,0,40,0"><param name="movie" value="//www.youtube…
  • Error Line 2119, Column 39: end tag for "param" omitted, but OMITTAG NO was specified
    <param name="bgcolor" value="#FFFFFF">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 2119, Column 1: start tag was here
    <param name="bgcolor" value="#FFFFFF">
  • Error Line 2120, Column 44: end tag for "param" omitted, but OMITTAG NO was specified
    <param name="allowfullscreen" value="true">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 2120, Column 1: start tag was here
    <param name="allowfullscreen" value="true">
  • Error Line 2121, Column 586: end tag for "param" omitted, but OMITTAG NO was specified
    …tag%3Dw160%26sigh%3D82VRZfLLsOESSBqiVoUHIJ_5q9o&amp;autoplay=0&amp;ps=blogger">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 2121, Column 1: start tag was here
    <param name="flashvars" value="flvurl=http://redirector.googlevideo.com/videopl…
  • Warning Line 2124, Column 375: reference not terminated by REFC delimiter
    …9E45D22640840F1722D39%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Warning Line 2124, Column 375: reference to external entity in attribute value
    …9E45D22640840F1722D39%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Error Line 2124, Column 375: reference to entity "iurl" for which no system identifier could be generated
    …9E45D22640840F1722D39%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Info Line 611, Column 370: entity was defined here
    …D5FA5BF22D7FFFDBF017BD1658%26key%3Dck2&iurl=http://video.google.com/ThumbnailS…
  • Warning Line 2124, Column 539: reference not terminated by REFC delimiter
    …D5000%26itag%3Dw160%26sigh%3D82VRZfLLsOESSBqiVoUHIJ_5q9o&autoplay=0&ps=blogger"

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

  • Warning Line 2124, Column 539: reference to external entity in attribute value
    …D5000%26itag%3Dw160%26sigh%3D82VRZfLLsOESSBqiVoUHIJ_5q9o&autoplay=0&ps=blogger"

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

  • Error Line 2124, Column 539: reference to entity "autoplay" for which no system identifier could be generated
    …D5000%26itag%3Dw160%26sigh%3D82VRZfLLsOESSBqiVoUHIJ_5q9o&autoplay=0&ps=blogger"

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

  • Info Line 611, Column 530: entity was defined here
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"
  • Warning Line 2124, Column 544: reference not terminated by REFC delimiter
    …D5000%26itag%3Dw160%26sigh%3D82VRZfLLsOESSBqiVoUHIJ_5q9o&autoplay=0&ps=blogger"

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

  • Warning Line 2124, Column 544: reference to external entity in attribute value
    …D5000%26itag%3Dw160%26sigh%3D82VRZfLLsOESSBqiVoUHIJ_5q9o&autoplay=0&ps=blogger"

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

  • Error Line 2124, Column 544: reference to entity "ps" for which no system identifier could be generated
    …D5000%26itag%3Dw160%26sigh%3D82VRZfLLsOESSBqiVoUHIJ_5q9o&autoplay=0&ps=blogger"

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

  • Info Line 611, Column 541: entity was defined here
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"
  • Error Line 2125, Column 25: element "embed" undefined
    allowFullScreen="true" /></object>

    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).
  • Error Line 2126, Column 395: end tag for "img" omitted, but OMITTAG NO was specified
    …ss="BLOG_mobile_video_class" id="BLOG_mobile_video-e4a45ff9898e86b9"></a></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 ">".

  • Info Line 2126, Column 119: start tag was here
    …==/0/0/0/video.3gp" type="video/3gpp"><img width="320" height="266" alt="video…
  • Error Line 2205, Column 37: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div id='summary8060201518920061171'>

    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>").

  • Error Line 2207, Column 298: end tag for "param" omitted, but OMITTAG NO was specified
    …cab#version=6,0,40,0"><param name="movie" value="//www.youtube.com/get_player">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 2207, Column 241: start tag was here
    …s/flash/swflash.cab#version=6,0,40,0"><param name="movie" value="//www.youtube…
  • Error Line 2208, Column 39: end tag for "param" omitted, but OMITTAG NO was specified
    <param name="bgcolor" value="#FFFFFF">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 2208, Column 1: start tag was here
    <param name="bgcolor" value="#FFFFFF">
  • Error Line 2209, Column 44: end tag for "param" omitted, but OMITTAG NO was specified
    <param name="allowfullscreen" value="true">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 2209, Column 1: start tag was here
    <param name="allowfullscreen" value="true">
  • Error Line 2210, Column 586: end tag for "param" omitted, but OMITTAG NO was specified
    …tag%3Dw160%26sigh%3DJ6YW37xzhr4LqM2ol9OOW-uPTc8&amp;autoplay=0&amp;ps=blogger">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 2210, Column 1: start tag was here
    <param name="flashvars" value="flvurl=http://redirector.googlevideo.com/videopl…
  • Warning Line 2213, Column 375: reference not terminated by REFC delimiter
    …A0EF863CCCF37868A6D2C%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Warning Line 2213, Column 375: reference to external entity in attribute value
    …A0EF863CCCF37868A6D2C%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Error Line 2213, Column 375: reference to entity "iurl" for which no system identifier could be generated
    …A0EF863CCCF37868A6D2C%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Info Line 611, Column 370: entity was defined here
    …D5FA5BF22D7FFFDBF017BD1658%26key%3Dck2&iurl=http://video.google.com/ThumbnailS…
  • Warning Line 2213, Column 539: reference not terminated by REFC delimiter
    …D5000%26itag%3Dw160%26sigh%3DJ6YW37xzhr4LqM2ol9OOW-uPTc8&autoplay=0&ps=blogger"

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

  • Warning Line 2213, Column 539: reference to external entity in attribute value
    …D5000%26itag%3Dw160%26sigh%3DJ6YW37xzhr4LqM2ol9OOW-uPTc8&autoplay=0&ps=blogger"

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

  • Error Line 2213, Column 539: reference to entity "autoplay" for which no system identifier could be generated
    …D5000%26itag%3Dw160%26sigh%3DJ6YW37xzhr4LqM2ol9OOW-uPTc8&autoplay=0&ps=blogger"

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

  • Info Line 611, Column 530: entity was defined here
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"
  • Warning Line 2213, Column 544: reference not terminated by REFC delimiter
    …D5000%26itag%3Dw160%26sigh%3DJ6YW37xzhr4LqM2ol9OOW-uPTc8&autoplay=0&ps=blogger"

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

  • Warning Line 2213, Column 544: reference to external entity in attribute value
    …D5000%26itag%3Dw160%26sigh%3DJ6YW37xzhr4LqM2ol9OOW-uPTc8&autoplay=0&ps=blogger"

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

  • Error Line 2213, Column 544: reference to entity "ps" for which no system identifier could be generated
    …D5000%26itag%3Dw160%26sigh%3DJ6YW37xzhr4LqM2ol9OOW-uPTc8&autoplay=0&ps=blogger"

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

  • Info Line 611, Column 541: entity was defined here
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"
  • Error Line 2214, Column 25: element "embed" undefined
    allowFullScreen="true" /></object>

    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).
  • Error Line 2215, Column 395: end tag for "img" omitted, but OMITTAG NO was specified
    …ss="BLOG_mobile_video_class" id="BLOG_mobile_video-84264d4c1d0bbbd1"></a></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 ">".

  • Info Line 2215, Column 119: start tag was here
    …==/0/0/0/video.3gp" type="video/3gpp"><img width="320" height="266" alt="video…
  • Error Line 2294, Column 37: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div id='summary6674580848962541396'>

    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>").

  • Error Line 2296, Column 298: end tag for "param" omitted, but OMITTAG NO was specified
    …cab#version=6,0,40,0"><param name="movie" value="//www.youtube.com/get_player">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 2296, Column 241: start tag was here
    …s/flash/swflash.cab#version=6,0,40,0"><param name="movie" value="//www.youtube…
  • Error Line 2297, Column 39: end tag for "param" omitted, but OMITTAG NO was specified
    <param name="bgcolor" value="#FFFFFF">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 2297, Column 1: start tag was here
    <param name="bgcolor" value="#FFFFFF">
  • Error Line 2298, Column 44: end tag for "param" omitted, but OMITTAG NO was specified
    <param name="allowfullscreen" value="true">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 2298, Column 1: start tag was here
    <param name="allowfullscreen" value="true">
  • Error Line 2299, Column 585: end tag for "param" omitted, but OMITTAG NO was specified
    …tag%3Dw160%26sigh%3DDkdzNW7oIwBYBdKY0Qs-Os7EJJ8&amp;autoplay=0&amp;ps=blogger">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 2299, Column 1: start tag was here
    <param name="flashvars" value="flvurl=http://redirector.googlevideo.com/videopl…
  • Warning Line 2302, Column 374: reference not terminated by REFC delimiter
    …DDAAB3E1CF96F979D052A%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Warning Line 2302, Column 374: reference to external entity in attribute value
    …DDAAB3E1CF96F979D052A%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Error Line 2302, Column 374: reference to entity "iurl" for which no system identifier could be generated
    …DDAAB3E1CF96F979D052A%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Info Line 611, Column 370: entity was defined here
    …D5FA5BF22D7FFFDBF017BD1658%26key%3Dck2&iurl=http://video.google.com/ThumbnailS…
  • Warning Line 2302, Column 538: reference not terminated by REFC delimiter
    …D5000%26itag%3Dw160%26sigh%3DDkdzNW7oIwBYBdKY0Qs-Os7EJJ8&autoplay=0&ps=blogger"

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

  • Warning Line 2302, Column 538: reference to external entity in attribute value
    …D5000%26itag%3Dw160%26sigh%3DDkdzNW7oIwBYBdKY0Qs-Os7EJJ8&autoplay=0&ps=blogger"

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

  • Error Line 2302, Column 538: reference to entity "autoplay" for which no system identifier could be generated
    …D5000%26itag%3Dw160%26sigh%3DDkdzNW7oIwBYBdKY0Qs-Os7EJJ8&autoplay=0&ps=blogger"

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

  • Info Line 611, Column 530: entity was defined here
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"
  • Warning Line 2302, Column 543: reference not terminated by REFC delimiter
    …D5000%26itag%3Dw160%26sigh%3DDkdzNW7oIwBYBdKY0Qs-Os7EJJ8&autoplay=0&ps=blogger"

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

  • Warning Line 2302, Column 543: reference to external entity in attribute value
    …D5000%26itag%3Dw160%26sigh%3DDkdzNW7oIwBYBdKY0Qs-Os7EJJ8&autoplay=0&ps=blogger"

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

  • Error Line 2302, Column 543: reference to entity "ps" for which no system identifier could be generated
    …D5000%26itag%3Dw160%26sigh%3DDkdzNW7oIwBYBdKY0Qs-Os7EJJ8&autoplay=0&ps=blogger"

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

  • Info Line 611, Column 541: entity was defined here
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"
  • Error Line 2303, Column 25: element "embed" undefined
    allowFullScreen="true" /></object>

    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).
  • Error Line 2304, Column 395: end tag for "img" omitted, but OMITTAG NO was specified
    …ss="BLOG_mobile_video_class" id="BLOG_mobile_video-52291f7c4521d55d"></a></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 ">".

  • Info Line 2304, Column 119: start tag was here
    …==/0/0/0/video.3gp" type="video/3gpp"><img width="320" height="266" alt="video…
  • Error Line 2383, Column 37: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div id='summary1254572974568992075'>

    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>").

  • Error Line 2385, Column 298: end tag for "param" omitted, but OMITTAG NO was specified
    …cab#version=6,0,40,0"><param name="movie" value="//www.youtube.com/get_player">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 2385, Column 241: start tag was here
    …s/flash/swflash.cab#version=6,0,40,0"><param name="movie" value="//www.youtube…
  • Error Line 2386, Column 39: end tag for "param" omitted, but OMITTAG NO was specified
    <param name="bgcolor" value="#FFFFFF">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 2386, Column 1: start tag was here
    <param name="bgcolor" value="#FFFFFF">
  • Error Line 2387, Column 44: end tag for "param" omitted, but OMITTAG NO was specified
    <param name="allowfullscreen" value="true">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 2387, Column 1: start tag was here
    <param name="allowfullscreen" value="true">
  • Error Line 2388, Column 586: end tag for "param" omitted, but OMITTAG NO was specified
    …tag%3Dw160%26sigh%3DaC1ztB1sl9VtRXyKXO8-aUw8M9A&amp;autoplay=0&amp;ps=blogger">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 2388, Column 1: start tag was here
    <param name="flashvars" value="flvurl=http://redirector.googlevideo.com/videopl…
  • Warning Line 2391, Column 375: reference not terminated by REFC delimiter
    …CDEFBADEC746D23A9C110%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Warning Line 2391, Column 375: reference to external entity in attribute value
    …CDEFBADEC746D23A9C110%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Error Line 2391, Column 375: reference to entity "iurl" for which no system identifier could be generated
    …CDEFBADEC746D23A9C110%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Info Line 611, Column 370: entity was defined here
    …D5FA5BF22D7FFFDBF017BD1658%26key%3Dck2&iurl=http://video.google.com/ThumbnailS…
  • Warning Line 2391, Column 539: reference not terminated by REFC delimiter
    …D5000%26itag%3Dw160%26sigh%3DaC1ztB1sl9VtRXyKXO8-aUw8M9A&autoplay=0&ps=blogger"

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

  • Warning Line 2391, Column 539: reference to external entity in attribute value
    …D5000%26itag%3Dw160%26sigh%3DaC1ztB1sl9VtRXyKXO8-aUw8M9A&autoplay=0&ps=blogger"

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

  • Error Line 2391, Column 539: reference to entity "autoplay" for which no system identifier could be generated
    …D5000%26itag%3Dw160%26sigh%3DaC1ztB1sl9VtRXyKXO8-aUw8M9A&autoplay=0&ps=blogger"

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

  • Info Line 611, Column 530: entity was defined here
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"
  • Warning Line 2391, Column 544: reference not terminated by REFC delimiter
    …D5000%26itag%3Dw160%26sigh%3DaC1ztB1sl9VtRXyKXO8-aUw8M9A&autoplay=0&ps=blogger"

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

  • Warning Line 2391, Column 544: reference to external entity in attribute value
    …D5000%26itag%3Dw160%26sigh%3DaC1ztB1sl9VtRXyKXO8-aUw8M9A&autoplay=0&ps=blogger"

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

  • Error Line 2391, Column 544: reference to entity "ps" for which no system identifier could be generated
    …D5000%26itag%3Dw160%26sigh%3DaC1ztB1sl9VtRXyKXO8-aUw8M9A&autoplay=0&ps=blogger"

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

  • Info Line 611, Column 541: entity was defined here
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"
  • Error Line 2392, Column 25: element "embed" undefined
    allowFullScreen="true" /></object>

    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).
  • Error Line 2393, Column 395: end tag for "img" omitted, but OMITTAG NO was specified
    …ss="BLOG_mobile_video_class" id="BLOG_mobile_video-c9ad14dca6735977"></a></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 ">".

  • Info Line 2393, Column 119: start tag was here
    …==/0/0/0/video.3gp" type="video/3gpp"><img width="320" height="266" alt="video…
  • Error Line 2472, Column 36: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div id='summary154271393709394573'>

    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>").

  • Error Line 2474, Column 298: end tag for "param" omitted, but OMITTAG NO was specified
    …cab#version=6,0,40,0"><param name="movie" value="//www.youtube.com/get_player">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 2474, Column 241: start tag was here
    …s/flash/swflash.cab#version=6,0,40,0"><param name="movie" value="//www.youtube…
  • Error Line 2475, Column 39: end tag for "param" omitted, but OMITTAG NO was specified
    <param name="bgcolor" value="#FFFFFF">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 2475, Column 1: start tag was here
    <param name="bgcolor" value="#FFFFFF">
  • Error Line 2476, Column 44: end tag for "param" omitted, but OMITTAG NO was specified
    <param name="allowfullscreen" value="true">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 2476, Column 1: start tag was here
    <param name="allowfullscreen" value="true">
  • Error Line 2477, Column 586: end tag for "param" omitted, but OMITTAG NO was specified
    …tag%3Dw160%26sigh%3DGow8VEaU02MoO-9bfZ-KL6WktKY&amp;autoplay=0&amp;ps=blogger">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 2477, Column 1: start tag was here
    <param name="flashvars" value="flvurl=http://redirector.googlevideo.com/videopl…
  • Warning Line 2480, Column 375: reference not terminated by REFC delimiter
    …87D8C6CAB3B8A31A54764%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Warning Line 2480, Column 375: reference to external entity in attribute value
    …87D8C6CAB3B8A31A54764%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Error Line 2480, Column 375: reference to entity "iurl" for which no system identifier could be generated
    …87D8C6CAB3B8A31A54764%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Info Line 611, Column 370: entity was defined here
    …D5FA5BF22D7FFFDBF017BD1658%26key%3Dck2&iurl=http://video.google.com/ThumbnailS…
  • Warning Line 2480, Column 539: reference not terminated by REFC delimiter
    …D5000%26itag%3Dw160%26sigh%3DGow8VEaU02MoO-9bfZ-KL6WktKY&autoplay=0&ps=blogger"

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

  • Warning Line 2480, Column 539: reference to external entity in attribute value
    …D5000%26itag%3Dw160%26sigh%3DGow8VEaU02MoO-9bfZ-KL6WktKY&autoplay=0&ps=blogger"

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

  • Error Line 2480, Column 539: reference to entity "autoplay" for which no system identifier could be generated
    …D5000%26itag%3Dw160%26sigh%3DGow8VEaU02MoO-9bfZ-KL6WktKY&autoplay=0&ps=blogger"

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

  • Info Line 611, Column 530: entity was defined here
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"
  • Warning Line 2480, Column 544: reference not terminated by REFC delimiter
    …D5000%26itag%3Dw160%26sigh%3DGow8VEaU02MoO-9bfZ-KL6WktKY&autoplay=0&ps=blogger"

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

  • Warning Line 2480, Column 544: reference to external entity in attribute value
    …D5000%26itag%3Dw160%26sigh%3DGow8VEaU02MoO-9bfZ-KL6WktKY&autoplay=0&ps=blogger"

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

  • Error Line 2480, Column 544: reference to entity "ps" for which no system identifier could be generated
    …D5000%26itag%3Dw160%26sigh%3DGow8VEaU02MoO-9bfZ-KL6WktKY&autoplay=0&ps=blogger"

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

  • Info Line 611, Column 541: entity was defined here
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"
  • Error Line 2481, Column 25: element "embed" undefined
    allowFullScreen="true" /></object>

    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).
  • Error Line 2482, Column 395: end tag for "img" omitted, but OMITTAG NO was specified
    …ss="BLOG_mobile_video_class" id="BLOG_mobile_video-fd6aeedf1347f0cc"></a></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 ">".

  • Info Line 2482, Column 119: start tag was here
    …==/0/0/0/video.3gp" type="video/3gpp"><img width="320" height="266" alt="video…
  • Error Line 2561, Column 37: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div id='summary2545381861279389748'>

    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>").

  • Error Line 2563, Column 298: end tag for "param" omitted, but OMITTAG NO was specified
    …cab#version=6,0,40,0"><param name="movie" value="//www.youtube.com/get_player">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 2563, Column 241: start tag was here
    …s/flash/swflash.cab#version=6,0,40,0"><param name="movie" value="//www.youtube…
  • Error Line 2564, Column 39: end tag for "param" omitted, but OMITTAG NO was specified
    <param name="bgcolor" value="#FFFFFF">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 2564, Column 1: start tag was here
    <param name="bgcolor" value="#FFFFFF">
  • Error Line 2565, Column 44: end tag for "param" omitted, but OMITTAG NO was specified
    <param name="allowfullscreen" value="true">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 2565, Column 1: start tag was here
    <param name="allowfullscreen" value="true">
  • Error Line 2566, Column 586: end tag for "param" omitted, but OMITTAG NO was specified
    …tag%3Dw160%26sigh%3DbbLL0Z_G7DcBjsMyhpfkv604XLE&amp;autoplay=0&amp;ps=blogger">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 2566, Column 1: start tag was here
    <param name="flashvars" value="flvurl=http://redirector.googlevideo.com/videopl…
  • Warning Line 2569, Column 375: reference not terminated by REFC delimiter
    …1A33BB34E542BB78919F9%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Warning Line 2569, Column 375: reference to external entity in attribute value
    …1A33BB34E542BB78919F9%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Error Line 2569, Column 375: reference to entity "iurl" for which no system identifier could be generated
    …1A33BB34E542BB78919F9%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Info Line 611, Column 370: entity was defined here
    …D5FA5BF22D7FFFDBF017BD1658%26key%3Dck2&iurl=http://video.google.com/ThumbnailS…
  • Warning Line 2569, Column 539: reference not terminated by REFC delimiter
    …D5000%26itag%3Dw160%26sigh%3DbbLL0Z_G7DcBjsMyhpfkv604XLE&autoplay=0&ps=blogger"

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

  • Warning Line 2569, Column 539: reference to external entity in attribute value
    …D5000%26itag%3Dw160%26sigh%3DbbLL0Z_G7DcBjsMyhpfkv604XLE&autoplay=0&ps=blogger"

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

  • Error Line 2569, Column 539: reference to entity "autoplay" for which no system identifier could be generated
    …D5000%26itag%3Dw160%26sigh%3DbbLL0Z_G7DcBjsMyhpfkv604XLE&autoplay=0&ps=blogger"

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

  • Info Line 611, Column 530: entity was defined here
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"
  • Warning Line 2569, Column 544: reference not terminated by REFC delimiter
    …D5000%26itag%3Dw160%26sigh%3DbbLL0Z_G7DcBjsMyhpfkv604XLE&autoplay=0&ps=blogger"

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

  • Warning Line 2569, Column 544: reference to external entity in attribute value
    …D5000%26itag%3Dw160%26sigh%3DbbLL0Z_G7DcBjsMyhpfkv604XLE&autoplay=0&ps=blogger"

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

  • Error Line 2569, Column 544: reference to entity "ps" for which no system identifier could be generated
    …D5000%26itag%3Dw160%26sigh%3DbbLL0Z_G7DcBjsMyhpfkv604XLE&autoplay=0&ps=blogger"

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

  • Info Line 611, Column 541: entity was defined here
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"
  • Error Line 2570, Column 25: element "embed" undefined
    allowFullScreen="true" /></object>

    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).
  • Error Line 2571, Column 395: end tag for "img" omitted, but OMITTAG NO was specified
    …ss="BLOG_mobile_video_class" id="BLOG_mobile_video-9ddb19a891003e81"></a></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 ">".

  • Info Line 2571, Column 119: start tag was here
    …==/0/0/0/video.3gp" type="video/3gpp"><img width="320" height="266" alt="video…
  • Error Line 2650, Column 37: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div id='summary9152018199681889292'>

    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>").

  • Error Line 2652, Column 298: end tag for "param" omitted, but OMITTAG NO was specified
    …cab#version=6,0,40,0"><param name="movie" value="//www.youtube.com/get_player">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 2652, Column 241: start tag was here
    …s/flash/swflash.cab#version=6,0,40,0"><param name="movie" value="//www.youtube…
  • Error Line 2653, Column 39: end tag for "param" omitted, but OMITTAG NO was specified
    <param name="bgcolor" value="#FFFFFF">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 2653, Column 1: start tag was here
    <param name="bgcolor" value="#FFFFFF">
  • Error Line 2654, Column 44: end tag for "param" omitted, but OMITTAG NO was specified
    <param name="allowfullscreen" value="true">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 2654, Column 1: start tag was here
    <param name="allowfullscreen" value="true">
  • Error Line 2655, Column 585: end tag for "param" omitted, but OMITTAG NO was specified
    …tag%3Dw160%26sigh%3DBPlzMeHL_q9V1PVmkhRSx0hxez4&amp;autoplay=0&amp;ps=blogger">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 2655, Column 1: start tag was here
    <param name="flashvars" value="flvurl=http://redirector.googlevideo.com/videopl…
  • Warning Line 2658, Column 374: reference not terminated by REFC delimiter
    …12D519DFC3E5D088CEE27%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Warning Line 2658, Column 374: reference to external entity in attribute value
    …12D519DFC3E5D088CEE27%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Error Line 2658, Column 374: reference to entity "iurl" for which no system identifier could be generated
    …12D519DFC3E5D088CEE27%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Info Line 611, Column 370: entity was defined here
    …D5FA5BF22D7FFFDBF017BD1658%26key%3Dck2&iurl=http://video.google.com/ThumbnailS…
  • Warning Line 2658, Column 538: reference not terminated by REFC delimiter
    …D5000%26itag%3Dw160%26sigh%3DBPlzMeHL_q9V1PVmkhRSx0hxez4&autoplay=0&ps=blogger"

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

  • Warning Line 2658, Column 538: reference to external entity in attribute value
    …D5000%26itag%3Dw160%26sigh%3DBPlzMeHL_q9V1PVmkhRSx0hxez4&autoplay=0&ps=blogger"

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

  • Error Line 2658, Column 538: reference to entity "autoplay" for which no system identifier could be generated
    …D5000%26itag%3Dw160%26sigh%3DBPlzMeHL_q9V1PVmkhRSx0hxez4&autoplay=0&ps=blogger"

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

  • Info Line 611, Column 530: entity was defined here
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"
  • Warning Line 2658, Column 543: reference not terminated by REFC delimiter
    …D5000%26itag%3Dw160%26sigh%3DBPlzMeHL_q9V1PVmkhRSx0hxez4&autoplay=0&ps=blogger"

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

  • Warning Line 2658, Column 543: reference to external entity in attribute value
    …D5000%26itag%3Dw160%26sigh%3DBPlzMeHL_q9V1PVmkhRSx0hxez4&autoplay=0&ps=blogger"

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

  • Error Line 2658, Column 543: reference to entity "ps" for which no system identifier could be generated
    …D5000%26itag%3Dw160%26sigh%3DBPlzMeHL_q9V1PVmkhRSx0hxez4&autoplay=0&ps=blogger"

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

  • Info Line 611, Column 541: entity was defined here
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"
  • Error Line 2659, Column 25: element "embed" undefined
    allowFullScreen="true" /></object>

    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).
  • Error Line 2660, Column 395: end tag for "img" omitted, but OMITTAG NO was specified
    …ss="BLOG_mobile_video_class" id="BLOG_mobile_video-f134bcb0ebc7d72b"></a></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 ">".

  • Info Line 2660, Column 119: start tag was here
    …==/0/0/0/video.3gp" type="video/3gpp"><img width="320" height="266" alt="video…
  • Error Line 2739, Column 37: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div id='summary5263425084616483638'>

    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>").

  • Error Line 2741, Column 298: end tag for "param" omitted, but OMITTAG NO was specified
    …cab#version=6,0,40,0"><param name="movie" value="//www.youtube.com/get_player">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 2741, Column 241: start tag was here
    …s/flash/swflash.cab#version=6,0,40,0"><param name="movie" value="//www.youtube…
  • Error Line 2742, Column 39: end tag for "param" omitted, but OMITTAG NO was specified
    <param name="bgcolor" value="#FFFFFF">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 2742, Column 1: start tag was here
    <param name="bgcolor" value="#FFFFFF">
  • Error Line 2743, Column 44: end tag for "param" omitted, but OMITTAG NO was specified
    <param name="allowfullscreen" value="true">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 2743, Column 1: start tag was here
    <param name="allowfullscreen" value="true">
  • Error Line 2744, Column 586: end tag for "param" omitted, but OMITTAG NO was specified
    …tag%3Dw160%26sigh%3DLBXO7dws9VEDBHuzQDpOoBRfxbg&amp;autoplay=0&amp;ps=blogger">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 2744, Column 1: start tag was here
    <param name="flashvars" value="flvurl=http://redirector.googlevideo.com/videopl…
  • Warning Line 2747, Column 375: reference not terminated by REFC delimiter
    …1E90AC5C98C3C057DCAA2%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Warning Line 2747, Column 375: reference to external entity in attribute value
    …1E90AC5C98C3C057DCAA2%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Error Line 2747, Column 375: reference to entity "iurl" for which no system identifier could be generated
    …1E90AC5C98C3C057DCAA2%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Info Line 611, Column 370: entity was defined here
    …D5FA5BF22D7FFFDBF017BD1658%26key%3Dck2&iurl=http://video.google.com/ThumbnailS…
  • Warning Line 2747, Column 539: reference not terminated by REFC delimiter
    …D5000%26itag%3Dw160%26sigh%3DLBXO7dws9VEDBHuzQDpOoBRfxbg&autoplay=0&ps=blogger"

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

  • Warning Line 2747, Column 539: reference to external entity in attribute value
    …D5000%26itag%3Dw160%26sigh%3DLBXO7dws9VEDBHuzQDpOoBRfxbg&autoplay=0&ps=blogger"

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

  • Error Line 2747, Column 539: reference to entity "autoplay" for which no system identifier could be generated
    …D5000%26itag%3Dw160%26sigh%3DLBXO7dws9VEDBHuzQDpOoBRfxbg&autoplay=0&ps=blogger"

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

  • Info Line 611, Column 530: entity was defined here
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"
  • Warning Line 2747, Column 544: reference not terminated by REFC delimiter
    …D5000%26itag%3Dw160%26sigh%3DLBXO7dws9VEDBHuzQDpOoBRfxbg&autoplay=0&ps=blogger"

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

  • Warning Line 2747, Column 544: reference to external entity in attribute value
    …D5000%26itag%3Dw160%26sigh%3DLBXO7dws9VEDBHuzQDpOoBRfxbg&autoplay=0&ps=blogger"

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

  • Error Line 2747, Column 544: reference to entity "ps" for which no system identifier could be generated
    …D5000%26itag%3Dw160%26sigh%3DLBXO7dws9VEDBHuzQDpOoBRfxbg&autoplay=0&ps=blogger"

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

  • Info Line 611, Column 541: entity was defined here
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"
  • Error Line 2748, Column 25: element "embed" undefined
    allowFullScreen="true" /></object>

    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).
  • Error Line 2749, Column 395: end tag for "img" omitted, but OMITTAG NO was specified
    …ss="BLOG_mobile_video_class" id="BLOG_mobile_video-af5c6335fdd235cc"></a></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 ">".

  • Info Line 2749, Column 119: start tag was here
    …==/0/0/0/video.3gp" type="video/3gpp"><img width="320" height="266" alt="video…
  • Error Line 2828, Column 36: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div id='summary651259581205171889'>

    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>").

  • Error Line 2830, Column 298: end tag for "param" omitted, but OMITTAG NO was specified
    …cab#version=6,0,40,0"><param name="movie" value="//www.youtube.com/get_player">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 2830, Column 241: start tag was here
    …s/flash/swflash.cab#version=6,0,40,0"><param name="movie" value="//www.youtube…
  • Error Line 2831, Column 39: end tag for "param" omitted, but OMITTAG NO was specified
    <param name="bgcolor" value="#FFFFFF">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 2831, Column 1: start tag was here
    <param name="bgcolor" value="#FFFFFF">
  • Error Line 2832, Column 44: end tag for "param" omitted, but OMITTAG NO was specified
    <param name="allowfullscreen" value="true">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 2832, Column 1: start tag was here
    <param name="allowfullscreen" value="true">
  • Error Line 2833, Column 586: end tag for "param" omitted, but OMITTAG NO was specified
    …tag%3Dw160%26sigh%3DuV-DIiu-MaIIv9Cmyxm70WjywKU&amp;autoplay=0&amp;ps=blogger">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 2833, Column 1: start tag was here
    <param name="flashvars" value="flvurl=http://redirector.googlevideo.com/videopl…
  • Warning Line 2836, Column 375: reference not terminated by REFC delimiter
    …9610242B504F890F444AA%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Warning Line 2836, Column 375: reference to external entity in attribute value
    …9610242B504F890F444AA%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Error Line 2836, Column 375: reference to entity "iurl" for which no system identifier could be generated
    …9610242B504F890F444AA%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Info Line 611, Column 370: entity was defined here
    …D5FA5BF22D7FFFDBF017BD1658%26key%3Dck2&iurl=http://video.google.com/ThumbnailS…
  • Warning Line 2836, Column 539: reference not terminated by REFC delimiter
    …D5000%26itag%3Dw160%26sigh%3DuV-DIiu-MaIIv9Cmyxm70WjywKU&autoplay=0&ps=blogger"

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

  • Warning Line 2836, Column 539: reference to external entity in attribute value
    …D5000%26itag%3Dw160%26sigh%3DuV-DIiu-MaIIv9Cmyxm70WjywKU&autoplay=0&ps=blogger"

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

  • Error Line 2836, Column 539: reference to entity "autoplay" for which no system identifier could be generated
    …D5000%26itag%3Dw160%26sigh%3DuV-DIiu-MaIIv9Cmyxm70WjywKU&autoplay=0&ps=blogger"

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

  • Info Line 611, Column 530: entity was defined here
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"
  • Warning Line 2836, Column 544: reference not terminated by REFC delimiter
    …D5000%26itag%3Dw160%26sigh%3DuV-DIiu-MaIIv9Cmyxm70WjywKU&autoplay=0&ps=blogger"

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

  • Warning Line 2836, Column 544: reference to external entity in attribute value
    …D5000%26itag%3Dw160%26sigh%3DuV-DIiu-MaIIv9Cmyxm70WjywKU&autoplay=0&ps=blogger"

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

  • Error Line 2836, Column 544: reference to entity "ps" for which no system identifier could be generated
    …D5000%26itag%3Dw160%26sigh%3DuV-DIiu-MaIIv9Cmyxm70WjywKU&autoplay=0&ps=blogger"

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

  • Info Line 611, Column 541: entity was defined here
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"
  • Error Line 2837, Column 25: element "embed" undefined
    allowFullScreen="true" /></object>

    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).
  • Error Line 2838, Column 395: end tag for "img" omitted, but OMITTAG NO was specified
    …ss="BLOG_mobile_video_class" id="BLOG_mobile_video-21bcf18ee6ee86a5"></a></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 ">".

  • Info Line 2838, Column 119: start tag was here
    …==/0/0/0/video.3gp" type="video/3gpp"><img width="320" height="266" alt="video…
  • Error Line 2917, Column 37: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div id='summary4714354726139779700'>

    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>").

  • Error Line 2919, Column 298: end tag for "param" omitted, but OMITTAG NO was specified
    …cab#version=6,0,40,0"><param name="movie" value="//www.youtube.com/get_player">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 2919, Column 241: start tag was here
    …s/flash/swflash.cab#version=6,0,40,0"><param name="movie" value="//www.youtube…
  • Error Line 2920, Column 39: end tag for "param" omitted, but OMITTAG NO was specified
    <param name="bgcolor" value="#FFFFFF">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 2920, Column 1: start tag was here
    <param name="bgcolor" value="#FFFFFF">
  • Error Line 2921, Column 44: end tag for "param" omitted, but OMITTAG NO was specified
    <param name="allowfullscreen" value="true">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 2921, Column 1: start tag was here
    <param name="allowfullscreen" value="true">
  • Error Line 2922, Column 586: end tag for "param" omitted, but OMITTAG NO was specified
    …tag%3Dw160%26sigh%3DB9L2IIL2PpK6aDIf_CeGXe2OPKE&amp;autoplay=0&amp;ps=blogger">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 2922, Column 1: start tag was here
    <param name="flashvars" value="flvurl=http://redirector.googlevideo.com/videopl…
  • Warning Line 2925, Column 375: reference not terminated by REFC delimiter
    …34CD83AE8B02E34B53F5A%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Warning Line 2925, Column 375: reference to external entity in attribute value
    …34CD83AE8B02E34B53F5A%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Error Line 2925, Column 375: reference to entity "iurl" for which no system identifier could be generated
    …34CD83AE8B02E34B53F5A%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Info Line 611, Column 370: entity was defined here
    …D5FA5BF22D7FFFDBF017BD1658%26key%3Dck2&iurl=http://video.google.com/ThumbnailS…
  • Warning Line 2925, Column 539: reference not terminated by REFC delimiter
    …D5000%26itag%3Dw160%26sigh%3DB9L2IIL2PpK6aDIf_CeGXe2OPKE&autoplay=0&ps=blogger"

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

  • Warning Line 2925, Column 539: reference to external entity in attribute value
    …D5000%26itag%3Dw160%26sigh%3DB9L2IIL2PpK6aDIf_CeGXe2OPKE&autoplay=0&ps=blogger"

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

  • Error Line 2925, Column 539: reference to entity "autoplay" for which no system identifier could be generated
    …D5000%26itag%3Dw160%26sigh%3DB9L2IIL2PpK6aDIf_CeGXe2OPKE&autoplay=0&ps=blogger"

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

  • Info Line 611, Column 530: entity was defined here
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"
  • Warning Line 2925, Column 544: reference not terminated by REFC delimiter
    …D5000%26itag%3Dw160%26sigh%3DB9L2IIL2PpK6aDIf_CeGXe2OPKE&autoplay=0&ps=blogger"

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

  • Warning Line 2925, Column 544: reference to external entity in attribute value
    …D5000%26itag%3Dw160%26sigh%3DB9L2IIL2PpK6aDIf_CeGXe2OPKE&autoplay=0&ps=blogger"

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

  • Error Line 2925, Column 544: reference to entity "ps" for which no system identifier could be generated
    …D5000%26itag%3Dw160%26sigh%3DB9L2IIL2PpK6aDIf_CeGXe2OPKE&autoplay=0&ps=blogger"

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

  • Info Line 611, Column 541: entity was defined here
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"
  • Error Line 2926, Column 25: element "embed" undefined
    allowFullScreen="true" /></object>

    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).
  • Error Line 2927, Column 395: end tag for "img" omitted, but OMITTAG NO was specified
    …ss="BLOG_mobile_video_class" id="BLOG_mobile_video-20f93a4db76b3480"></a></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 ">".

  • Info Line 2927, Column 119: start tag was here
    …==/0/0/0/video.3gp" type="video/3gpp"><img width="320" height="266" alt="video…
  • Error Line 3006, Column 37: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div id='summary2136976922036390594'>

    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>").

  • Error Line 3008, Column 298: end tag for "param" omitted, but OMITTAG NO was specified
    …cab#version=6,0,40,0"><param name="movie" value="//www.youtube.com/get_player">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 3008, Column 241: start tag was here
    …s/flash/swflash.cab#version=6,0,40,0"><param name="movie" value="//www.youtube…
  • Error Line 3009, Column 39: end tag for "param" omitted, but OMITTAG NO was specified
    <param name="bgcolor" value="#FFFFFF">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 3009, Column 1: start tag was here
    <param name="bgcolor" value="#FFFFFF">
  • Error Line 3010, Column 44: end tag for "param" omitted, but OMITTAG NO was specified
    <param name="allowfullscreen" value="true">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 3010, Column 1: start tag was here
    <param name="allowfullscreen" value="true">
  • Error Line 3011, Column 586: end tag for "param" omitted, but OMITTAG NO was specified
    …tag%3Dw160%26sigh%3D7HWWBOsc2yf85O6Knjv6ZcRkSTE&amp;autoplay=0&amp;ps=blogger">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 3011, Column 1: start tag was here
    <param name="flashvars" value="flvurl=http://redirector.googlevideo.com/videopl…
  • Warning Line 3014, Column 375: reference not terminated by REFC delimiter
    …61F0A04FB15FB7BB4B685%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Warning Line 3014, Column 375: reference to external entity in attribute value
    …61F0A04FB15FB7BB4B685%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Error Line 3014, Column 375: reference to entity "iurl" for which no system identifier could be generated
    …61F0A04FB15FB7BB4B685%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Info Line 611, Column 370: entity was defined here
    …D5FA5BF22D7FFFDBF017BD1658%26key%3Dck2&iurl=http://video.google.com/ThumbnailS…
  • Warning Line 3014, Column 539: reference not terminated by REFC delimiter
    …D5000%26itag%3Dw160%26sigh%3D7HWWBOsc2yf85O6Knjv6ZcRkSTE&autoplay=0&ps=blogger"

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

  • Warning Line 3014, Column 539: reference to external entity in attribute value
    …D5000%26itag%3Dw160%26sigh%3D7HWWBOsc2yf85O6Knjv6ZcRkSTE&autoplay=0&ps=blogger"

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

  • Error Line 3014, Column 539: reference to entity "autoplay" for which no system identifier could be generated
    …D5000%26itag%3Dw160%26sigh%3D7HWWBOsc2yf85O6Knjv6ZcRkSTE&autoplay=0&ps=blogger"

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

  • Info Line 611, Column 530: entity was defined here
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"
  • Warning Line 3014, Column 544: reference not terminated by REFC delimiter
    …D5000%26itag%3Dw160%26sigh%3D7HWWBOsc2yf85O6Knjv6ZcRkSTE&autoplay=0&ps=blogger"

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

  • Warning Line 3014, Column 544: reference to external entity in attribute value
    …D5000%26itag%3Dw160%26sigh%3D7HWWBOsc2yf85O6Knjv6ZcRkSTE&autoplay=0&ps=blogger"

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

  • Error Line 3014, Column 544: reference to entity "ps" for which no system identifier could be generated
    …D5000%26itag%3Dw160%26sigh%3D7HWWBOsc2yf85O6Knjv6ZcRkSTE&autoplay=0&ps=blogger"

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

  • Info Line 611, Column 541: entity was defined here
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"
  • Error Line 3015, Column 25: element "embed" undefined
    allowFullScreen="true" /></object>

    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).
  • Error Line 3016, Column 395: end tag for "img" omitted, but OMITTAG NO was specified
    …ss="BLOG_mobile_video_class" id="BLOG_mobile_video-23a8f2fc4485db35"></a></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 ">".

  • Info Line 3016, Column 119: start tag was here
    …==/0/0/0/video.3gp" type="video/3gpp"><img width="320" height="266" alt="video…
  • Error Line 3095, Column 37: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div id='summary7220380570591944714'>

    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>").

  • Error Line 3097, Column 298: end tag for "param" omitted, but OMITTAG NO was specified
    …cab#version=6,0,40,0"><param name="movie" value="//www.youtube.com/get_player">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 3097, Column 241: start tag was here
    …s/flash/swflash.cab#version=6,0,40,0"><param name="movie" value="//www.youtube…
  • Error Line 3098, Column 39: end tag for "param" omitted, but OMITTAG NO was specified
    <param name="bgcolor" value="#FFFFFF">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 3098, Column 1: start tag was here
    <param name="bgcolor" value="#FFFFFF">
  • Error Line 3099, Column 44: end tag for "param" omitted, but OMITTAG NO was specified
    <param name="allowfullscreen" value="true">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 3099, Column 1: start tag was here
    <param name="allowfullscreen" value="true">
  • Error Line 3100, Column 586: end tag for "param" omitted, but OMITTAG NO was specified
    …tag%3Dw160%26sigh%3DstCdHARmsnQrtT7a1ztqwtB4id4&amp;autoplay=0&amp;ps=blogger">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 3100, Column 1: start tag was here
    <param name="flashvars" value="flvurl=http://redirector.googlevideo.com/videopl…
  • Warning Line 3103, Column 375: reference not terminated by REFC delimiter
    …BC00F34FA392A76BCB3AF%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Warning Line 3103, Column 375: reference to external entity in attribute value
    …BC00F34FA392A76BCB3AF%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Error Line 3103, Column 375: reference to entity "iurl" for which no system identifier could be generated
    …BC00F34FA392A76BCB3AF%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Info Line 611, Column 370: entity was defined here
    …D5FA5BF22D7FFFDBF017BD1658%26key%3Dck2&iurl=http://video.google.com/ThumbnailS…
  • Warning Line 3103, Column 539: reference not terminated by REFC delimiter
    …D5000%26itag%3Dw160%26sigh%3DstCdHARmsnQrtT7a1ztqwtB4id4&autoplay=0&ps=blogger"

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

  • Warning Line 3103, Column 539: reference to external entity in attribute value
    …D5000%26itag%3Dw160%26sigh%3DstCdHARmsnQrtT7a1ztqwtB4id4&autoplay=0&ps=blogger"

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

  • Error Line 3103, Column 539: reference to entity "autoplay" for which no system identifier could be generated
    …D5000%26itag%3Dw160%26sigh%3DstCdHARmsnQrtT7a1ztqwtB4id4&autoplay=0&ps=blogger"

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

  • Info Line 611, Column 530: entity was defined here
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"
  • Warning Line 3103, Column 544: reference not terminated by REFC delimiter
    …D5000%26itag%3Dw160%26sigh%3DstCdHARmsnQrtT7a1ztqwtB4id4&autoplay=0&ps=blogger"

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

  • Warning Line 3103, Column 544: reference to external entity in attribute value
    …D5000%26itag%3Dw160%26sigh%3DstCdHARmsnQrtT7a1ztqwtB4id4&autoplay=0&ps=blogger"

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

  • Error Line 3103, Column 544: reference to entity "ps" for which no system identifier could be generated
    …D5000%26itag%3Dw160%26sigh%3DstCdHARmsnQrtT7a1ztqwtB4id4&autoplay=0&ps=blogger"

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

  • Info Line 611, Column 541: entity was defined here
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"
  • Error Line 3104, Column 25: element "embed" undefined
    allowFullScreen="true" /></object>

    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).
  • Error Line 3105, Column 395: end tag for "img" omitted, but OMITTAG NO was specified
    …ss="BLOG_mobile_video_class" id="BLOG_mobile_video-1886c2ff1c4ca94a"></a></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 ">".

  • Info Line 3105, Column 119: start tag was here
    …==/0/0/0/video.3gp" type="video/3gpp"><img width="320" height="266" alt="video…
  • Error Line 3184, Column 37: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div id='summary7105849480213287987'>

    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>").

  • Error Line 3186, Column 298: end tag for "param" omitted, but OMITTAG NO was specified
    …cab#version=6,0,40,0"><param name="movie" value="//www.youtube.com/get_player">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 3186, Column 241: start tag was here
    …s/flash/swflash.cab#version=6,0,40,0"><param name="movie" value="//www.youtube…
  • Error Line 3187, Column 39: end tag for "param" omitted, but OMITTAG NO was specified
    <param name="bgcolor" value="#FFFFFF">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 3187, Column 1: start tag was here
    <param name="bgcolor" value="#FFFFFF">
  • Error Line 3188, Column 44: end tag for "param" omitted, but OMITTAG NO was specified
    <param name="allowfullscreen" value="true">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 3188, Column 1: start tag was here
    <param name="allowfullscreen" value="true">
  • Error Line 3189, Column 586: end tag for "param" omitted, but OMITTAG NO was specified
    …tag%3Dw160%26sigh%3DNv6IpH7H9JvxLyryGmDHAF5P-pc&amp;autoplay=0&amp;ps=blogger">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 3189, Column 1: start tag was here
    <param name="flashvars" value="flvurl=http://redirector.googlevideo.com/videopl…
  • Warning Line 3192, Column 375: reference not terminated by REFC delimiter
    …A900FD8058D28BE126538%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Warning Line 3192, Column 375: reference to external entity in attribute value
    …A900FD8058D28BE126538%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Error Line 3192, Column 375: reference to entity "iurl" for which no system identifier could be generated
    …A900FD8058D28BE126538%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Info Line 611, Column 370: entity was defined here
    …D5FA5BF22D7FFFDBF017BD1658%26key%3Dck2&iurl=http://video.google.com/ThumbnailS…
  • Warning Line 3192, Column 539: reference not terminated by REFC delimiter
    …D5000%26itag%3Dw160%26sigh%3DNv6IpH7H9JvxLyryGmDHAF5P-pc&autoplay=0&ps=blogger"

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

  • Warning Line 3192, Column 539: reference to external entity in attribute value
    …D5000%26itag%3Dw160%26sigh%3DNv6IpH7H9JvxLyryGmDHAF5P-pc&autoplay=0&ps=blogger"

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

  • Error Line 3192, Column 539: reference to entity "autoplay" for which no system identifier could be generated
    …D5000%26itag%3Dw160%26sigh%3DNv6IpH7H9JvxLyryGmDHAF5P-pc&autoplay=0&ps=blogger"

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

  • Info Line 611, Column 530: entity was defined here
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"
  • Warning Line 3192, Column 544: reference not terminated by REFC delimiter
    …D5000%26itag%3Dw160%26sigh%3DNv6IpH7H9JvxLyryGmDHAF5P-pc&autoplay=0&ps=blogger"

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

  • Warning Line 3192, Column 544: reference to external entity in attribute value
    …D5000%26itag%3Dw160%26sigh%3DNv6IpH7H9JvxLyryGmDHAF5P-pc&autoplay=0&ps=blogger"

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

  • Error Line 3192, Column 544: reference to entity "ps" for which no system identifier could be generated
    …D5000%26itag%3Dw160%26sigh%3DNv6IpH7H9JvxLyryGmDHAF5P-pc&autoplay=0&ps=blogger"

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

  • Info Line 611, Column 541: entity was defined here
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"
  • Error Line 3193, Column 25: element "embed" undefined
    allowFullScreen="true" /></object>

    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).
  • Error Line 3194, Column 395: end tag for "img" omitted, but OMITTAG NO was specified
    …ss="BLOG_mobile_video_class" id="BLOG_mobile_video-2f618aadfc72a38c"></a></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 ">".

  • Info Line 3194, Column 119: start tag was here
    …==/0/0/0/video.3gp" type="video/3gpp"><img width="320" height="266" alt="video…
  • Error Line 3273, Column 37: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div id='summary2508232651299137506'>

    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>").

  • Error Line 3275, Column 297: end tag for "param" omitted, but OMITTAG NO was specified
    …cab#version=6,0,40,0"><param name="movie" value="//www.youtube.com/get_player">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 3275, Column 240: start tag was here
    …s/flash/swflash.cab#version=6,0,40,0"><param name="movie" value="//www.youtube…
  • Error Line 3276, Column 39: end tag for "param" omitted, but OMITTAG NO was specified
    <param name="bgcolor" value="#FFFFFF">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 3276, Column 1: start tag was here
    <param name="bgcolor" value="#FFFFFF">
  • Error Line 3277, Column 44: end tag for "param" omitted, but OMITTAG NO was specified
    <param name="allowfullscreen" value="true">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 3277, Column 1: start tag was here
    <param name="allowfullscreen" value="true">
  • Error Line 3278, Column 585: end tag for "param" omitted, but OMITTAG NO was specified
    …tag%3Dw160%26sigh%3DtnRh5_ng6uiIBx-51N1RmxSjzP4&amp;autoplay=0&amp;ps=blogger">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 3278, Column 1: start tag was here
    <param name="flashvars" value="flvurl=http://redirector.googlevideo.com/videopl…
  • Warning Line 3281, Column 375: reference not terminated by REFC delimiter
    …4ACDFF2025CFD694D3EC9%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Warning Line 3281, Column 375: reference to external entity in attribute value
    …4ACDFF2025CFD694D3EC9%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Error Line 3281, Column 375: reference to entity "iurl" for which no system identifier could be generated
    …4ACDFF2025CFD694D3EC9%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Info Line 611, Column 370: entity was defined here
    …D5FA5BF22D7FFFDBF017BD1658%26key%3Dck2&iurl=http://video.google.com/ThumbnailS…
  • Warning Line 3281, Column 538: reference not terminated by REFC delimiter
    …D5000%26itag%3Dw160%26sigh%3DtnRh5_ng6uiIBx-51N1RmxSjzP4&autoplay=0&ps=blogger"

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

  • Warning Line 3281, Column 538: reference to external entity in attribute value
    …D5000%26itag%3Dw160%26sigh%3DtnRh5_ng6uiIBx-51N1RmxSjzP4&autoplay=0&ps=blogger"

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

  • Error Line 3281, Column 538: reference to entity "autoplay" for which no system identifier could be generated
    …D5000%26itag%3Dw160%26sigh%3DtnRh5_ng6uiIBx-51N1RmxSjzP4&autoplay=0&ps=blogger"

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

  • Info Line 611, Column 530: entity was defined here
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"
  • Warning Line 3281, Column 543: reference not terminated by REFC delimiter
    …D5000%26itag%3Dw160%26sigh%3DtnRh5_ng6uiIBx-51N1RmxSjzP4&autoplay=0&ps=blogger"

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

  • Warning Line 3281, Column 543: reference to external entity in attribute value
    …D5000%26itag%3Dw160%26sigh%3DtnRh5_ng6uiIBx-51N1RmxSjzP4&autoplay=0&ps=blogger"

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

  • Error Line 3281, Column 543: reference to entity "ps" for which no system identifier could be generated
    …D5000%26itag%3Dw160%26sigh%3DtnRh5_ng6uiIBx-51N1RmxSjzP4&autoplay=0&ps=blogger"

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

  • Info Line 611, Column 541: entity was defined here
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"
  • Error Line 3282, Column 25: element "embed" undefined
    allowFullScreen="true" /></object>

    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).
  • Error Line 3283, Column 393: end tag for "img" omitted, but OMITTAG NO was specified
    …ass="BLOG_mobile_video_class" id="BLOG_mobile_video-a4ede5330aecdf9"></a></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 ">".

  • Info Line 3283, Column 119: start tag was here
    …==/0/0/0/video.3gp" type="video/3gpp"><img width="320" height="266" alt="video…
  • Error Line 3362, Column 37: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div id='summary4175864858266791148'>

    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>").

  • Error Line 3364, Column 298: end tag for "param" omitted, but OMITTAG NO was specified
    …cab#version=6,0,40,0"><param name="movie" value="//www.youtube.com/get_player">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 3364, Column 241: start tag was here
    …s/flash/swflash.cab#version=6,0,40,0"><param name="movie" value="//www.youtube…
  • Error Line 3365, Column 39: end tag for "param" omitted, but OMITTAG NO was specified
    <param name="bgcolor" value="#FFFFFF">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 3365, Column 1: start tag was here
    <param name="bgcolor" value="#FFFFFF">
  • Error Line 3366, Column 44: end tag for "param" omitted, but OMITTAG NO was specified
    <param name="allowfullscreen" value="true">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 3366, Column 1: start tag was here
    <param name="allowfullscreen" value="true">
  • Error Line 3367, Column 586: end tag for "param" omitted, but OMITTAG NO was specified
    …tag%3Dw160%26sigh%3DM3DHoPsR9EakpUvW0xL5SNFbdnU&amp;autoplay=0&amp;ps=blogger">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 3367, Column 1: start tag was here
    <param name="flashvars" value="flvurl=http://redirector.googlevideo.com/videopl…
  • Warning Line 3370, Column 375: reference not terminated by REFC delimiter
    …BBAFD3C61657FFDDAFA4B%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Warning Line 3370, Column 375: reference to external entity in attribute value
    …BBAFD3C61657FFDDAFA4B%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Error Line 3370, Column 375: reference to entity "iurl" for which no system identifier could be generated
    …BBAFD3C61657FFDDAFA4B%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Info Line 611, Column 370: entity was defined here
    …D5FA5BF22D7FFFDBF017BD1658%26key%3Dck2&iurl=http://video.google.com/ThumbnailS…
  • Warning Line 3370, Column 539: reference not terminated by REFC delimiter
    …D5000%26itag%3Dw160%26sigh%3DM3DHoPsR9EakpUvW0xL5SNFbdnU&autoplay=0&ps=blogger"

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

  • Warning Line 3370, Column 539: reference to external entity in attribute value
    …D5000%26itag%3Dw160%26sigh%3DM3DHoPsR9EakpUvW0xL5SNFbdnU&autoplay=0&ps=blogger"

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

  • Error Line 3370, Column 539: reference to entity "autoplay" for which no system identifier could be generated
    …D5000%26itag%3Dw160%26sigh%3DM3DHoPsR9EakpUvW0xL5SNFbdnU&autoplay=0&ps=blogger"

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

  • Info Line 611, Column 530: entity was defined here
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"
  • Warning Line 3370, Column 544: reference not terminated by REFC delimiter
    …D5000%26itag%3Dw160%26sigh%3DM3DHoPsR9EakpUvW0xL5SNFbdnU&autoplay=0&ps=blogger"

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

  • Warning Line 3370, Column 544: reference to external entity in attribute value
    …D5000%26itag%3Dw160%26sigh%3DM3DHoPsR9EakpUvW0xL5SNFbdnU&autoplay=0&ps=blogger"

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

  • Error Line 3370, Column 544: reference to entity "ps" for which no system identifier could be generated
    …D5000%26itag%3Dw160%26sigh%3DM3DHoPsR9EakpUvW0xL5SNFbdnU&autoplay=0&ps=blogger"

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

  • Info Line 611, Column 541: entity was defined here
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"
  • Error Line 3371, Column 25: element "embed" undefined
    allowFullScreen="true" /></object>

    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).
  • Error Line 3372, Column 395: end tag for "img" omitted, but OMITTAG NO was specified
    …ss="BLOG_mobile_video_class" id="BLOG_mobile_video-82c752e316ad123a"></a></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 ">".

  • Info Line 3372, Column 119: start tag was here
    …==/0/0/0/video.3gp" type="video/3gpp"><img width="320" height="266" alt="video…
  • Error Line 3451, Column 37: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div id='summary1453712058034643655'>

    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>").

  • Error Line 3453, Column 298: end tag for "param" omitted, but OMITTAG NO was specified
    …cab#version=6,0,40,0"><param name="movie" value="//www.youtube.com/get_player">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 3453, Column 241: start tag was here
    …s/flash/swflash.cab#version=6,0,40,0"><param name="movie" value="//www.youtube…
  • Error Line 3454, Column 39: end tag for "param" omitted, but OMITTAG NO was specified
    <param name="bgcolor" value="#FFFFFF">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 3454, Column 1: start tag was here
    <param name="bgcolor" value="#FFFFFF">
  • Error Line 3455, Column 44: end tag for "param" omitted, but OMITTAG NO was specified
    <param name="allowfullscreen" value="true">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 3455, Column 1: start tag was here
    <param name="allowfullscreen" value="true">
  • Error Line 3456, Column 586: end tag for "param" omitted, but OMITTAG NO was specified
    …tag%3Dw160%26sigh%3D8eNBu8CG9B5zkN6ODpbB29y0-fQ&amp;autoplay=0&amp;ps=blogger">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 3456, Column 1: start tag was here
    <param name="flashvars" value="flvurl=http://redirector.googlevideo.com/videopl…
  • Warning Line 3459, Column 375: reference not terminated by REFC delimiter
    …2E5D7AA4E42D77B75695E%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Warning Line 3459, Column 375: reference to external entity in attribute value
    …2E5D7AA4E42D77B75695E%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Error Line 3459, Column 375: reference to entity "iurl" for which no system identifier could be generated
    …2E5D7AA4E42D77B75695E%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Info Line 611, Column 370: entity was defined here
    …D5FA5BF22D7FFFDBF017BD1658%26key%3Dck2&iurl=http://video.google.com/ThumbnailS…
  • Warning Line 3459, Column 539: reference not terminated by REFC delimiter
    …D5000%26itag%3Dw160%26sigh%3D8eNBu8CG9B5zkN6ODpbB29y0-fQ&autoplay=0&ps=blogger"

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

  • Warning Line 3459, Column 539: reference to external entity in attribute value
    …D5000%26itag%3Dw160%26sigh%3D8eNBu8CG9B5zkN6ODpbB29y0-fQ&autoplay=0&ps=blogger"

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

  • Error Line 3459, Column 539: reference to entity "autoplay" for which no system identifier could be generated
    …D5000%26itag%3Dw160%26sigh%3D8eNBu8CG9B5zkN6ODpbB29y0-fQ&autoplay=0&ps=blogger"

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

  • Info Line 611, Column 530: entity was defined here
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"
  • Warning Line 3459, Column 544: reference not terminated by REFC delimiter
    …D5000%26itag%3Dw160%26sigh%3D8eNBu8CG9B5zkN6ODpbB29y0-fQ&autoplay=0&ps=blogger"

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

  • Warning Line 3459, Column 544: reference to external entity in attribute value
    …D5000%26itag%3Dw160%26sigh%3D8eNBu8CG9B5zkN6ODpbB29y0-fQ&autoplay=0&ps=blogger"

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

  • Error Line 3459, Column 544: reference to entity "ps" for which no system identifier could be generated
    …D5000%26itag%3Dw160%26sigh%3D8eNBu8CG9B5zkN6ODpbB29y0-fQ&autoplay=0&ps=blogger"

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

  • Info Line 611, Column 541: entity was defined here
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"
  • Error Line 3460, Column 25: element "embed" undefined
    allowFullScreen="true" /></object>

    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).
  • Error Line 3461, Column 395: end tag for "img" omitted, but OMITTAG NO was specified
    …ss="BLOG_mobile_video_class" id="BLOG_mobile_video-b14a644dd5e430e6"></a></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 ">".

  • Info Line 3461, Column 119: start tag was here
    …==/0/0/0/video.3gp" type="video/3gpp"><img width="320" height="266" alt="video…
  • Error Line 3540, Column 37: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div id='summary1102593352012187333'>

    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>").

  • Error Line 3542, Column 298: end tag for "param" omitted, but OMITTAG NO was specified
    …cab#version=6,0,40,0"><param name="movie" value="//www.youtube.com/get_player">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 3542, Column 241: start tag was here
    …s/flash/swflash.cab#version=6,0,40,0"><param name="movie" value="//www.youtube…
  • Error Line 3543, Column 39: end tag for "param" omitted, but OMITTAG NO was specified
    <param name="bgcolor" value="#FFFFFF">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 3543, Column 1: start tag was here
    <param name="bgcolor" value="#FFFFFF">
  • Error Line 3544, Column 44: end tag for "param" omitted, but OMITTAG NO was specified
    <param name="allowfullscreen" value="true">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 3544, Column 1: start tag was here
    <param name="allowfullscreen" value="true">
  • Error Line 3545, Column 586: end tag for "param" omitted, but OMITTAG NO was specified
    …tag%3Dw160%26sigh%3D6mAVUGEO3ZZKSAM0taMHTPSnGqM&amp;autoplay=0&amp;ps=blogger">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 3545, Column 1: start tag was here
    <param name="flashvars" value="flvurl=http://redirector.googlevideo.com/videopl…
  • Warning Line 3548, Column 375: reference not terminated by REFC delimiter
    …89BDB66C9AC3DB5CD3540%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Warning Line 3548, Column 375: reference to external entity in attribute value
    …89BDB66C9AC3DB5CD3540%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Error Line 3548, Column 375: reference to entity "iurl" for which no system identifier could be generated
    …89BDB66C9AC3DB5CD3540%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Info Line 611, Column 370: entity was defined here
    …D5FA5BF22D7FFFDBF017BD1658%26key%3Dck2&iurl=http://video.google.com/ThumbnailS…
  • Warning Line 3548, Column 539: reference not terminated by REFC delimiter
    …D5000%26itag%3Dw160%26sigh%3D6mAVUGEO3ZZKSAM0taMHTPSnGqM&autoplay=0&ps=blogger"

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

  • Warning Line 3548, Column 539: reference to external entity in attribute value
    …D5000%26itag%3Dw160%26sigh%3D6mAVUGEO3ZZKSAM0taMHTPSnGqM&autoplay=0&ps=blogger"

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

  • Error Line 3548, Column 539: reference to entity "autoplay" for which no system identifier could be generated
    …D5000%26itag%3Dw160%26sigh%3D6mAVUGEO3ZZKSAM0taMHTPSnGqM&autoplay=0&ps=blogger"

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

  • Info Line 611, Column 530: entity was defined here
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"
  • Warning Line 3548, Column 544: reference not terminated by REFC delimiter
    …D5000%26itag%3Dw160%26sigh%3D6mAVUGEO3ZZKSAM0taMHTPSnGqM&autoplay=0&ps=blogger"

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

  • Warning Line 3548, Column 544: reference to external entity in attribute value
    …D5000%26itag%3Dw160%26sigh%3D6mAVUGEO3ZZKSAM0taMHTPSnGqM&autoplay=0&ps=blogger"

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

  • Error Line 3548, Column 544: reference to entity "ps" for which no system identifier could be generated
    …D5000%26itag%3Dw160%26sigh%3D6mAVUGEO3ZZKSAM0taMHTPSnGqM&autoplay=0&ps=blogger"

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

  • Info Line 611, Column 541: entity was defined here
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"
  • Error Line 3549, Column 25: element "embed" undefined
    allowFullScreen="true" /></object>

    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).
  • Error Line 3550, Column 395: end tag for "img" omitted, but OMITTAG NO was specified
    …ss="BLOG_mobile_video_class" id="BLOG_mobile_video-a2f63fb96be6a281"></a></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 ">".

  • Info Line 3550, Column 119: start tag was here
    …==/0/0/0/video.3gp" type="video/3gpp"><img width="320" height="266" alt="video…
  • Error Line 3629, Column 37: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div id='summary2886746888865749776'>

    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>").

  • Error Line 3631, Column 298: end tag for "param" omitted, but OMITTAG NO was specified
    …cab#version=6,0,40,0"><param name="movie" value="//www.youtube.com/get_player">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 3631, Column 241: start tag was here
    …s/flash/swflash.cab#version=6,0,40,0"><param name="movie" value="//www.youtube…
  • Error Line 3632, Column 39: end tag for "param" omitted, but OMITTAG NO was specified
    <param name="bgcolor" value="#FFFFFF">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 3632, Column 1: start tag was here
    <param name="bgcolor" value="#FFFFFF">
  • Error Line 3633, Column 44: end tag for "param" omitted, but OMITTAG NO was specified
    <param name="allowfullscreen" value="true">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 3633, Column 1: start tag was here
    <param name="allowfullscreen" value="true">
  • Error Line 3634, Column 586: end tag for "param" omitted, but OMITTAG NO was specified
    …tag%3Dw160%26sigh%3DhOJPebGV4imS035-iIwSyPZn5ec&amp;autoplay=0&amp;ps=blogger">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 3634, Column 1: start tag was here
    <param name="flashvars" value="flvurl=http://redirector.googlevideo.com/videopl…
  • Warning Line 3637, Column 375: reference not terminated by REFC delimiter
    …3C5D7DE92FAE741D85287%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Warning Line 3637, Column 375: reference to external entity in attribute value
    …3C5D7DE92FAE741D85287%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Error Line 3637, Column 375: reference to entity "iurl" for which no system identifier could be generated
    …3C5D7DE92FAE741D85287%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Info Line 611, Column 370: entity was defined here
    …D5FA5BF22D7FFFDBF017BD1658%26key%3Dck2&iurl=http://video.google.com/ThumbnailS…
  • Warning Line 3637, Column 539: reference not terminated by REFC delimiter
    …D5000%26itag%3Dw160%26sigh%3DhOJPebGV4imS035-iIwSyPZn5ec&autoplay=0&ps=blogger"

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

  • Warning Line 3637, Column 539: reference to external entity in attribute value
    …D5000%26itag%3Dw160%26sigh%3DhOJPebGV4imS035-iIwSyPZn5ec&autoplay=0&ps=blogger"

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

  • Error Line 3637, Column 539: reference to entity "autoplay" for which no system identifier could be generated
    …D5000%26itag%3Dw160%26sigh%3DhOJPebGV4imS035-iIwSyPZn5ec&autoplay=0&ps=blogger"

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

  • Info Line 611, Column 530: entity was defined here
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"
  • Warning Line 3637, Column 544: reference not terminated by REFC delimiter
    …D5000%26itag%3Dw160%26sigh%3DhOJPebGV4imS035-iIwSyPZn5ec&autoplay=0&ps=blogger"

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

  • Warning Line 3637, Column 544: reference to external entity in attribute value
    …D5000%26itag%3Dw160%26sigh%3DhOJPebGV4imS035-iIwSyPZn5ec&autoplay=0&ps=blogger"

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

  • Error Line 3637, Column 544: reference to entity "ps" for which no system identifier could be generated
    …D5000%26itag%3Dw160%26sigh%3DhOJPebGV4imS035-iIwSyPZn5ec&autoplay=0&ps=blogger"

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

  • Info Line 611, Column 541: entity was defined here
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"
  • Error Line 3638, Column 25: element "embed" undefined
    allowFullScreen="true" /></object>

    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).
  • Error Line 3639, Column 395: end tag for "img" omitted, but OMITTAG NO was specified
    …ss="BLOG_mobile_video_class" id="BLOG_mobile_video-8068fcc1f6bfdf31"></a></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 ">".

  • Info Line 3639, Column 119: start tag was here
    …==/0/0/0/video.3gp" type="video/3gpp"><img width="320" height="266" alt="video…
  • Error Line 3718, Column 37: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div id='summary1725665136298520527'>

    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>").

  • Error Line 3720, Column 298: end tag for "param" omitted, but OMITTAG NO was specified
    …cab#version=6,0,40,0"><param name="movie" value="//www.youtube.com/get_player">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 3720, Column 241: start tag was here
    …s/flash/swflash.cab#version=6,0,40,0"><param name="movie" value="//www.youtube…
  • Error Line 3721, Column 39: end tag for "param" omitted, but OMITTAG NO was specified
    <param name="bgcolor" value="#FFFFFF">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 3721, Column 1: start tag was here
    <param name="bgcolor" value="#FFFFFF">
  • Error Line 3722, Column 44: end tag for "param" omitted, but OMITTAG NO was specified
    <param name="allowfullscreen" value="true">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 3722, Column 1: start tag was here
    <param name="allowfullscreen" value="true">
  • Error Line 3723, Column 586: end tag for "param" omitted, but OMITTAG NO was specified
    …tag%3Dw160%26sigh%3DD9kuYoFhwc4MCyMlTIjUzEogD8w&amp;autoplay=0&amp;ps=blogger">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 3723, Column 1: start tag was here
    <param name="flashvars" value="flvurl=http://redirector.googlevideo.com/videopl…
  • Warning Line 3726, Column 375: reference not terminated by REFC delimiter
    …E8706F5C134A05A404AE8%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Warning Line 3726, Column 375: reference to external entity in attribute value
    …E8706F5C134A05A404AE8%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Error Line 3726, Column 375: reference to entity "iurl" for which no system identifier could be generated
    …E8706F5C134A05A404AE8%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Info Line 611, Column 370: entity was defined here
    …D5FA5BF22D7FFFDBF017BD1658%26key%3Dck2&iurl=http://video.google.com/ThumbnailS…
  • Warning Line 3726, Column 539: reference not terminated by REFC delimiter
    …D5000%26itag%3Dw160%26sigh%3DD9kuYoFhwc4MCyMlTIjUzEogD8w&autoplay=0&ps=blogger"

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

  • Warning Line 3726, Column 539: reference to external entity in attribute value
    …D5000%26itag%3Dw160%26sigh%3DD9kuYoFhwc4MCyMlTIjUzEogD8w&autoplay=0&ps=blogger"

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

  • Error Line 3726, Column 539: reference to entity "autoplay" for which no system identifier could be generated
    …D5000%26itag%3Dw160%26sigh%3DD9kuYoFhwc4MCyMlTIjUzEogD8w&autoplay=0&ps=blogger"

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

  • Info Line 611, Column 530: entity was defined here
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"
  • Warning Line 3726, Column 544: reference not terminated by REFC delimiter
    …D5000%26itag%3Dw160%26sigh%3DD9kuYoFhwc4MCyMlTIjUzEogD8w&autoplay=0&ps=blogger"

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

  • Warning Line 3726, Column 544: reference to external entity in attribute value
    …D5000%26itag%3Dw160%26sigh%3DD9kuYoFhwc4MCyMlTIjUzEogD8w&autoplay=0&ps=blogger"

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

  • Error Line 3726, Column 544: reference to entity "ps" for which no system identifier could be generated
    …D5000%26itag%3Dw160%26sigh%3DD9kuYoFhwc4MCyMlTIjUzEogD8w&autoplay=0&ps=blogger"

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

  • Info Line 611, Column 541: entity was defined here
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"
  • Error Line 3727, Column 25: element "embed" undefined
    allowFullScreen="true" /></object>

    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).
  • Error Line 3728, Column 395: end tag for "img" omitted, but OMITTAG NO was specified
    …ss="BLOG_mobile_video_class" id="BLOG_mobile_video-d99b161713585d72"></a></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 ">".

  • Info Line 3728, Column 119: start tag was here
    …==/0/0/0/video.3gp" type="video/3gpp"><img width="320" height="266" alt="video…
  • Error Line 3807, Column 37: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div id='summary8734811007420046993'>

    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>").

  • Error Line 3809, Column 298: end tag for "param" omitted, but OMITTAG NO was specified
    …cab#version=6,0,40,0"><param name="movie" value="//www.youtube.com/get_player">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 3809, Column 241: start tag was here
    …s/flash/swflash.cab#version=6,0,40,0"><param name="movie" value="//www.youtube…
  • Error Line 3810, Column 39: end tag for "param" omitted, but OMITTAG NO was specified
    <param name="bgcolor" value="#FFFFFF">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 3810, Column 1: start tag was here
    <param name="bgcolor" value="#FFFFFF">
  • Error Line 3811, Column 44: end tag for "param" omitted, but OMITTAG NO was specified
    <param name="allowfullscreen" value="true">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 3811, Column 1: start tag was here
    <param name="allowfullscreen" value="true">
  • Error Line 3812, Column 586: end tag for "param" omitted, but OMITTAG NO was specified
    …tag%3Dw160%26sigh%3Dac0qyemHB4XTabgfd_rrhs3M4oM&amp;autoplay=0&amp;ps=blogger">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 3812, Column 1: start tag was here
    <param name="flashvars" value="flvurl=http://redirector.googlevideo.com/videopl…
  • Warning Line 3815, Column 375: reference not terminated by REFC delimiter
    …988B1B24D0D4F845FC0B7%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Warning Line 3815, Column 375: reference to external entity in attribute value
    …988B1B24D0D4F845FC0B7%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Error Line 3815, Column 375: reference to entity "iurl" for which no system identifier could be generated
    …988B1B24D0D4F845FC0B7%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Info Line 611, Column 370: entity was defined here
    …D5FA5BF22D7FFFDBF017BD1658%26key%3Dck2&iurl=http://video.google.com/ThumbnailS…
  • Warning Line 3815, Column 539: reference not terminated by REFC delimiter
    …D5000%26itag%3Dw160%26sigh%3Dac0qyemHB4XTabgfd_rrhs3M4oM&autoplay=0&ps=blogger"

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

  • Warning Line 3815, Column 539: reference to external entity in attribute value
    …D5000%26itag%3Dw160%26sigh%3Dac0qyemHB4XTabgfd_rrhs3M4oM&autoplay=0&ps=blogger"

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

  • Error Line 3815, Column 539: reference to entity "autoplay" for which no system identifier could be generated
    …D5000%26itag%3Dw160%26sigh%3Dac0qyemHB4XTabgfd_rrhs3M4oM&autoplay=0&ps=blogger"

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

  • Info Line 611, Column 530: entity was defined here
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"
  • Warning Line 3815, Column 544: reference not terminated by REFC delimiter
    …D5000%26itag%3Dw160%26sigh%3Dac0qyemHB4XTabgfd_rrhs3M4oM&autoplay=0&ps=blogger"

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

  • Warning Line 3815, Column 544: reference to external entity in attribute value
    …D5000%26itag%3Dw160%26sigh%3Dac0qyemHB4XTabgfd_rrhs3M4oM&autoplay=0&ps=blogger"

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

  • Error Line 3815, Column 544: reference to entity "ps" for which no system identifier could be generated
    …D5000%26itag%3Dw160%26sigh%3Dac0qyemHB4XTabgfd_rrhs3M4oM&autoplay=0&ps=blogger"

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

  • Info Line 611, Column 541: entity was defined here
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"
  • Error Line 3816, Column 25: element "embed" undefined
    allowFullScreen="true" /></object>

    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).
  • Error Line 3817, Column 395: end tag for "img" omitted, but OMITTAG NO was specified
    …ss="BLOG_mobile_video_class" id="BLOG_mobile_video-5dd4f70b834c7a1d"></a></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 ">".

  • Info Line 3817, Column 119: start tag was here
    …==/0/0/0/video.3gp" type="video/3gpp"><img width="320" height="266" alt="video…
  • Error Line 3896, Column 37: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div id='summary2210299263546374909'>

    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>").

  • Error Line 3898, Column 298: end tag for "param" omitted, but OMITTAG NO was specified
    …cab#version=6,0,40,0"><param name="movie" value="//www.youtube.com/get_player">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 3898, Column 241: start tag was here
    …s/flash/swflash.cab#version=6,0,40,0"><param name="movie" value="//www.youtube…
  • Error Line 3899, Column 39: end tag for "param" omitted, but OMITTAG NO was specified
    <param name="bgcolor" value="#FFFFFF">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 3899, Column 1: start tag was here
    <param name="bgcolor" value="#FFFFFF">
  • Error Line 3900, Column 44: end tag for "param" omitted, but OMITTAG NO was specified
    <param name="allowfullscreen" value="true">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 3900, Column 1: start tag was here
    <param name="allowfullscreen" value="true">
  • Error Line 3901, Column 586: end tag for "param" omitted, but OMITTAG NO was specified
    …tag%3Dw160%26sigh%3Dj97OtcRtUT5UJ2v3XXxi_z05GOc&amp;autoplay=0&amp;ps=blogger">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 3901, Column 1: start tag was here
    <param name="flashvars" value="flvurl=http://redirector.googlevideo.com/videopl…
  • Warning Line 3904, Column 375: reference not terminated by REFC delimiter
    …A6B0F86290A6BA14E9CCD%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Warning Line 3904, Column 375: reference to external entity in attribute value
    …A6B0F86290A6BA14E9CCD%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Error Line 3904, Column 375: reference to entity "iurl" for which no system identifier could be generated
    …A6B0F86290A6BA14E9CCD%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Info Line 611, Column 370: entity was defined here
    …D5FA5BF22D7FFFDBF017BD1658%26key%3Dck2&iurl=http://video.google.com/ThumbnailS…
  • Warning Line 3904, Column 539: reference not terminated by REFC delimiter
    …D5000%26itag%3Dw160%26sigh%3Dj97OtcRtUT5UJ2v3XXxi_z05GOc&autoplay=0&ps=blogger"

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

  • Warning Line 3904, Column 539: reference to external entity in attribute value
    …D5000%26itag%3Dw160%26sigh%3Dj97OtcRtUT5UJ2v3XXxi_z05GOc&autoplay=0&ps=blogger"

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

  • Error Line 3904, Column 539: reference to entity "autoplay" for which no system identifier could be generated
    …D5000%26itag%3Dw160%26sigh%3Dj97OtcRtUT5UJ2v3XXxi_z05GOc&autoplay=0&ps=blogger"

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

  • Info Line 611, Column 530: entity was defined here
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"
  • Warning Line 3904, Column 544: reference not terminated by REFC delimiter
    …D5000%26itag%3Dw160%26sigh%3Dj97OtcRtUT5UJ2v3XXxi_z05GOc&autoplay=0&ps=blogger"

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

  • Warning Line 3904, Column 544: reference to external entity in attribute value
    …D5000%26itag%3Dw160%26sigh%3Dj97OtcRtUT5UJ2v3XXxi_z05GOc&autoplay=0&ps=blogger"

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

  • Error Line 3904, Column 544: reference to entity "ps" for which no system identifier could be generated
    …D5000%26itag%3Dw160%26sigh%3Dj97OtcRtUT5UJ2v3XXxi_z05GOc&autoplay=0&ps=blogger"

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

  • Info Line 611, Column 541: entity was defined here
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"
  • Error Line 3905, Column 25: element "embed" undefined
    allowFullScreen="true" /></object>

    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).
  • Error Line 3906, Column 395: end tag for "img" omitted, but OMITTAG NO was specified
    …ss="BLOG_mobile_video_class" id="BLOG_mobile_video-fc4a12ee940a66c0"></a></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 ">".

  • Info Line 3906, Column 119: start tag was here
    …==/0/0/0/video.3gp" type="video/3gpp"><img width="320" height="266" alt="video…
  • Error Line 3985, Column 37: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div id='summary4642776785016042809'>

    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>").

  • Error Line 3987, Column 298: end tag for "param" omitted, but OMITTAG NO was specified
    …cab#version=6,0,40,0"><param name="movie" value="//www.youtube.com/get_player">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 3987, Column 241: start tag was here
    …s/flash/swflash.cab#version=6,0,40,0"><param name="movie" value="//www.youtube…
  • Error Line 3988, Column 39: end tag for "param" omitted, but OMITTAG NO was specified
    <param name="bgcolor" value="#FFFFFF">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 3988, Column 1: start tag was here
    <param name="bgcolor" value="#FFFFFF">
  • Error Line 3989, Column 44: end tag for "param" omitted, but OMITTAG NO was specified
    <param name="allowfullscreen" value="true">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 3989, Column 1: start tag was here
    <param name="allowfullscreen" value="true">
  • Error Line 3990, Column 586: end tag for "param" omitted, but OMITTAG NO was specified
    …tag%3Dw160%26sigh%3D3xnZNT1E0FkyoAXEJUPb4cDQMZ4&amp;autoplay=0&amp;ps=blogger">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 3990, Column 1: start tag was here
    <param name="flashvars" value="flvurl=http://redirector.googlevideo.com/videopl…
  • Warning Line 3993, Column 375: reference not terminated by REFC delimiter
    …D5EEA5ACC69F8B18B0E96%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Warning Line 3993, Column 375: reference to external entity in attribute value
    …D5EEA5ACC69F8B18B0E96%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Error Line 3993, Column 375: reference to entity "iurl" for which no system identifier could be generated
    …D5EEA5ACC69F8B18B0E96%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Info Line 611, Column 370: entity was defined here
    …D5FA5BF22D7FFFDBF017BD1658%26key%3Dck2&iurl=http://video.google.com/ThumbnailS…
  • Warning Line 3993, Column 539: reference not terminated by REFC delimiter
    …D5000%26itag%3Dw160%26sigh%3D3xnZNT1E0FkyoAXEJUPb4cDQMZ4&autoplay=0&ps=blogger"

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

  • Warning Line 3993, Column 539: reference to external entity in attribute value
    …D5000%26itag%3Dw160%26sigh%3D3xnZNT1E0FkyoAXEJUPb4cDQMZ4&autoplay=0&ps=blogger"

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

  • Error Line 3993, Column 539: reference to entity "autoplay" for which no system identifier could be generated
    …D5000%26itag%3Dw160%26sigh%3D3xnZNT1E0FkyoAXEJUPb4cDQMZ4&autoplay=0&ps=blogger"

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

  • Info Line 611, Column 530: entity was defined here
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"
  • Warning Line 3993, Column 544: reference not terminated by REFC delimiter
    …D5000%26itag%3Dw160%26sigh%3D3xnZNT1E0FkyoAXEJUPb4cDQMZ4&autoplay=0&ps=blogger"

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

  • Warning Line 3993, Column 544: reference to external entity in attribute value
    …D5000%26itag%3Dw160%26sigh%3D3xnZNT1E0FkyoAXEJUPb4cDQMZ4&autoplay=0&ps=blogger"

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

  • Error Line 3993, Column 544: reference to entity "ps" for which no system identifier could be generated
    …D5000%26itag%3Dw160%26sigh%3D3xnZNT1E0FkyoAXEJUPb4cDQMZ4&autoplay=0&ps=blogger"

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

  • Info Line 611, Column 541: entity was defined here
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"
  • Error Line 3994, Column 25: element "embed" undefined
    allowFullScreen="true" /></object>

    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).
  • Error Line 3995, Column 395: end tag for "img" omitted, but OMITTAG NO was specified
    …ss="BLOG_mobile_video_class" id="BLOG_mobile_video-705bbc90ce7cac31"></a></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 ">".

  • Info Line 3995, Column 119: start tag was here
    …==/0/0/0/video.3gp" type="video/3gpp"><img width="320" height="266" alt="video…
  • Error Line 4074, Column 37: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div id='summary7429482892379118418'>

    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>").

  • Error Line 4076, Column 298: end tag for "param" omitted, but OMITTAG NO was specified
    …cab#version=6,0,40,0"><param name="movie" value="//www.youtube.com/get_player">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 4076, Column 241: start tag was here
    …s/flash/swflash.cab#version=6,0,40,0"><param name="movie" value="//www.youtube…
  • Error Line 4077, Column 39: end tag for "param" omitted, but OMITTAG NO was specified
    <param name="bgcolor" value="#FFFFFF">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 4077, Column 1: start tag was here
    <param name="bgcolor" value="#FFFFFF">
  • Error Line 4078, Column 44: end tag for "param" omitted, but OMITTAG NO was specified
    <param name="allowfullscreen" value="true">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 4078, Column 1: start tag was here
    <param name="allowfullscreen" value="true">
  • Error Line 4079, Column 586: end tag for "param" omitted, but OMITTAG NO was specified
    …tag%3Dw160%26sigh%3DVX6-WOCoIP41I5sPdjQId6hdMio&amp;autoplay=0&amp;ps=blogger">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 4079, Column 1: start tag was here
    <param name="flashvars" value="flvurl=http://redirector.googlevideo.com/videopl…
  • Warning Line 4082, Column 375: reference not terminated by REFC delimiter
    …EE45B2421CEB4320718DB%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Warning Line 4082, Column 375: reference to external entity in attribute value
    …EE45B2421CEB4320718DB%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Error Line 4082, Column 375: reference to entity "iurl" for which no system identifier could be generated
    …EE45B2421CEB4320718DB%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Info Line 611, Column 370: entity was defined here
    …D5FA5BF22D7FFFDBF017BD1658%26key%3Dck2&iurl=http://video.google.com/ThumbnailS…
  • Warning Line 4082, Column 539: reference not terminated by REFC delimiter
    …D5000%26itag%3Dw160%26sigh%3DVX6-WOCoIP41I5sPdjQId6hdMio&autoplay=0&ps=blogger"

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

  • Warning Line 4082, Column 539: reference to external entity in attribute value
    …D5000%26itag%3Dw160%26sigh%3DVX6-WOCoIP41I5sPdjQId6hdMio&autoplay=0&ps=blogger"

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

  • Error Line 4082, Column 539: reference to entity "autoplay" for which no system identifier could be generated
    …D5000%26itag%3Dw160%26sigh%3DVX6-WOCoIP41I5sPdjQId6hdMio&autoplay=0&ps=blogger"

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

  • Info Line 611, Column 530: entity was defined here
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"
  • Warning Line 4082, Column 544: reference not terminated by REFC delimiter
    …D5000%26itag%3Dw160%26sigh%3DVX6-WOCoIP41I5sPdjQId6hdMio&autoplay=0&ps=blogger"

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

  • Warning Line 4082, Column 544: reference to external entity in attribute value
    …D5000%26itag%3Dw160%26sigh%3DVX6-WOCoIP41I5sPdjQId6hdMio&autoplay=0&ps=blogger"

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

  • Error Line 4082, Column 544: reference to entity "ps" for which no system identifier could be generated
    …D5000%26itag%3Dw160%26sigh%3DVX6-WOCoIP41I5sPdjQId6hdMio&autoplay=0&ps=blogger"

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

  • Info Line 611, Column 541: entity was defined here
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"
  • Error Line 4083, Column 25: element "embed" undefined
    allowFullScreen="true" /></object>

    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).
  • Error Line 4084, Column 395: end tag for "img" omitted, but OMITTAG NO was specified
    …ss="BLOG_mobile_video_class" id="BLOG_mobile_video-d5c81e02c1afa849"></a></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 ">".

  • Info Line 4084, Column 119: start tag was here
    …==/0/0/0/video.3gp" type="video/3gpp"><img width="320" height="266" alt="video…
  • Error Line 4163, Column 37: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div id='summary3792519737421432166'>

    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>").

  • Error Line 4165, Column 298: end tag for "param" omitted, but OMITTAG NO was specified
    …cab#version=6,0,40,0"><param name="movie" value="//www.youtube.com/get_player">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 4165, Column 241: start tag was here
    …s/flash/swflash.cab#version=6,0,40,0"><param name="movie" value="//www.youtube…
  • Error Line 4166, Column 39: end tag for "param" omitted, but OMITTAG NO was specified
    <param name="bgcolor" value="#FFFFFF">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 4166, Column 1: start tag was here
    <param name="bgcolor" value="#FFFFFF">
  • Error Line 4167, Column 44: end tag for "param" omitted, but OMITTAG NO was specified
    <param name="allowfullscreen" value="true">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 4167, Column 1: start tag was here
    <param name="allowfullscreen" value="true">
  • Error Line 4168, Column 586: end tag for "param" omitted, but OMITTAG NO was specified
    …tag%3Dw160%26sigh%3Da9KaXqP8s3zeDJNql-zKJg5-EEM&amp;autoplay=0&amp;ps=blogger">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 4168, Column 1: start tag was here
    <param name="flashvars" value="flvurl=http://redirector.googlevideo.com/videopl…
  • Warning Line 4171, Column 375: reference not terminated by REFC delimiter
    …69470DD22422E9E5A0C00%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Warning Line 4171, Column 375: reference to external entity in attribute value
    …69470DD22422E9E5A0C00%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Error Line 4171, Column 375: reference to entity "iurl" for which no system identifier could be generated
    …69470DD22422E9E5A0C00%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Info Line 611, Column 370: entity was defined here
    …D5FA5BF22D7FFFDBF017BD1658%26key%3Dck2&iurl=http://video.google.com/ThumbnailS…
  • Warning Line 4171, Column 539: reference not terminated by REFC delimiter
    …D5000%26itag%3Dw160%26sigh%3Da9KaXqP8s3zeDJNql-zKJg5-EEM&autoplay=0&ps=blogger"

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

  • Warning Line 4171, Column 539: reference to external entity in attribute value
    …D5000%26itag%3Dw160%26sigh%3Da9KaXqP8s3zeDJNql-zKJg5-EEM&autoplay=0&ps=blogger"

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

  • Error Line 4171, Column 539: reference to entity "autoplay" for which no system identifier could be generated
    …D5000%26itag%3Dw160%26sigh%3Da9KaXqP8s3zeDJNql-zKJg5-EEM&autoplay=0&ps=blogger"

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

  • Info Line 611, Column 530: entity was defined here
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"
  • Warning Line 4171, Column 544: reference not terminated by REFC delimiter
    …D5000%26itag%3Dw160%26sigh%3Da9KaXqP8s3zeDJNql-zKJg5-EEM&autoplay=0&ps=blogger"

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

  • Warning Line 4171, Column 544: reference to external entity in attribute value
    …D5000%26itag%3Dw160%26sigh%3Da9KaXqP8s3zeDJNql-zKJg5-EEM&autoplay=0&ps=blogger"

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

  • Error Line 4171, Column 544: reference to entity "ps" for which no system identifier could be generated
    …D5000%26itag%3Dw160%26sigh%3Da9KaXqP8s3zeDJNql-zKJg5-EEM&autoplay=0&ps=blogger"

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

  • Info Line 611, Column 541: entity was defined here
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"
  • Error Line 4172, Column 25: element "embed" undefined
    allowFullScreen="true" /></object>

    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).
  • Error Line 4173, Column 395: end tag for "img" omitted, but OMITTAG NO was specified
    …ss="BLOG_mobile_video_class" id="BLOG_mobile_video-8084f889111fdbb9"></a></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 ">".

  • Info Line 4173, Column 119: start tag was here
    …==/0/0/0/video.3gp" type="video/3gpp"><img width="320" height="266" alt="video…
  • Error Line 4252, Column 37: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div id='summary6289333393551963147'>

    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>").

  • Error Line 4254, Column 298: end tag for "param" omitted, but OMITTAG NO was specified
    …cab#version=6,0,40,0"><param name="movie" value="//www.youtube.com/get_player">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 4254, Column 241: start tag was here
    …s/flash/swflash.cab#version=6,0,40,0"><param name="movie" value="//www.youtube…
  • Error Line 4255, Column 39: end tag for "param" omitted, but OMITTAG NO was specified
    <param name="bgcolor" value="#FFFFFF">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 4255, Column 1: start tag was here
    <param name="bgcolor" value="#FFFFFF">
  • Error Line 4256, Column 44: end tag for "param" omitted, but OMITTAG NO was specified
    <param name="allowfullscreen" value="true">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 4256, Column 1: start tag was here
    <param name="allowfullscreen" value="true">
  • Error Line 4257, Column 586: end tag for "param" omitted, but OMITTAG NO was specified
    …tag%3Dw160%26sigh%3DL1ySkpqnmeFUIYsLDrqyV_HraPg&amp;autoplay=0&amp;ps=blogger">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 4257, Column 1: start tag was here
    <param name="flashvars" value="flvurl=http://redirector.googlevideo.com/videopl…
  • Warning Line 4260, Column 375: reference not terminated by REFC delimiter
    …5AE96D80DEEA7032B8E4C%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Warning Line 4260, Column 375: reference to external entity in attribute value
    …5AE96D80DEEA7032B8E4C%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Error Line 4260, Column 375: reference to entity "iurl" for which no system identifier could be generated
    …5AE96D80DEEA7032B8E4C%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Info Line 611, Column 370: entity was defined here
    …D5FA5BF22D7FFFDBF017BD1658%26key%3Dck2&iurl=http://video.google.com/ThumbnailS…
  • Warning Line 4260, Column 539: reference not terminated by REFC delimiter
    …D5000%26itag%3Dw160%26sigh%3DL1ySkpqnmeFUIYsLDrqyV_HraPg&autoplay=0&ps=blogger"

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

  • Warning Line 4260, Column 539: reference to external entity in attribute value
    …D5000%26itag%3Dw160%26sigh%3DL1ySkpqnmeFUIYsLDrqyV_HraPg&autoplay=0&ps=blogger"

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

  • Error Line 4260, Column 539: reference to entity "autoplay" for which no system identifier could be generated
    …D5000%26itag%3Dw160%26sigh%3DL1ySkpqnmeFUIYsLDrqyV_HraPg&autoplay=0&ps=blogger"

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

  • Info Line 611, Column 530: entity was defined here
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"
  • Warning Line 4260, Column 544: reference not terminated by REFC delimiter
    …D5000%26itag%3Dw160%26sigh%3DL1ySkpqnmeFUIYsLDrqyV_HraPg&autoplay=0&ps=blogger"

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

  • Warning Line 4260, Column 544: reference to external entity in attribute value
    …D5000%26itag%3Dw160%26sigh%3DL1ySkpqnmeFUIYsLDrqyV_HraPg&autoplay=0&ps=blogger"

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

  • Error Line 4260, Column 544: reference to entity "ps" for which no system identifier could be generated
    …D5000%26itag%3Dw160%26sigh%3DL1ySkpqnmeFUIYsLDrqyV_HraPg&autoplay=0&ps=blogger"

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

  • Info Line 611, Column 541: entity was defined here
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"
  • Error Line 4261, Column 25: element "embed" undefined
    allowFullScreen="true" /></object>

    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).
  • Error Line 4262, Column 395: end tag for "img" omitted, but OMITTAG NO was specified
    …ss="BLOG_mobile_video_class" id="BLOG_mobile_video-cf5fa83c42cba8ab"></a></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 ">".

  • Info Line 4262, Column 119: start tag was here
    …==/0/0/0/video.3gp" type="video/3gpp"><img width="320" height="266" alt="video…
  • Error Line 4341, Column 37: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div id='summary2700504263341115738'>

    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>").

  • Error Line 4343, Column 298: end tag for "param" omitted, but OMITTAG NO was specified
    …cab#version=6,0,40,0"><param name="movie" value="//www.youtube.com/get_player">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 4343, Column 241: start tag was here
    …s/flash/swflash.cab#version=6,0,40,0"><param name="movie" value="//www.youtube…
  • Error Line 4344, Column 39: end tag for "param" omitted, but OMITTAG NO was specified
    <param name="bgcolor" value="#FFFFFF">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 4344, Column 1: start tag was here
    <param name="bgcolor" value="#FFFFFF">
  • Error Line 4345, Column 44: end tag for "param" omitted, but OMITTAG NO was specified
    <param name="allowfullscreen" value="true">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 4345, Column 1: start tag was here
    <param name="allowfullscreen" value="true">
  • Error Line 4346, Column 586: end tag for "param" omitted, but OMITTAG NO was specified
    …tag%3Dw160%26sigh%3DJUQG-Q3wsVYgfCwSqmGYX7sKdJA&amp;autoplay=0&amp;ps=blogger">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 4346, Column 1: start tag was here
    <param name="flashvars" value="flvurl=http://redirector.googlevideo.com/videopl…
  • Warning Line 4349, Column 375: reference not terminated by REFC delimiter
    …30A02ABC9852280786394%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Warning Line 4349, Column 375: reference to external entity in attribute value
    …30A02ABC9852280786394%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Error Line 4349, Column 375: reference to entity "iurl" for which no system identifier could be generated
    …30A02ABC9852280786394%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Info Line 611, Column 370: entity was defined here
    …D5FA5BF22D7FFFDBF017BD1658%26key%3Dck2&iurl=http://video.google.com/ThumbnailS…
  • Warning Line 4349, Column 539: reference not terminated by REFC delimiter
    …D5000%26itag%3Dw160%26sigh%3DJUQG-Q3wsVYgfCwSqmGYX7sKdJA&autoplay=0&ps=blogger"

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

  • Warning Line 4349, Column 539: reference to external entity in attribute value
    …D5000%26itag%3Dw160%26sigh%3DJUQG-Q3wsVYgfCwSqmGYX7sKdJA&autoplay=0&ps=blogger"

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

  • Error Line 4349, Column 539: reference to entity "autoplay" for which no system identifier could be generated
    …D5000%26itag%3Dw160%26sigh%3DJUQG-Q3wsVYgfCwSqmGYX7sKdJA&autoplay=0&ps=blogger"

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

  • Info Line 611, Column 530: entity was defined here
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"
  • Warning Line 4349, Column 544: reference not terminated by REFC delimiter
    …D5000%26itag%3Dw160%26sigh%3DJUQG-Q3wsVYgfCwSqmGYX7sKdJA&autoplay=0&ps=blogger"

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

  • Warning Line 4349, Column 544: reference to external entity in attribute value
    …D5000%26itag%3Dw160%26sigh%3DJUQG-Q3wsVYgfCwSqmGYX7sKdJA&autoplay=0&ps=blogger"

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

  • Error Line 4349, Column 544: reference to entity "ps" for which no system identifier could be generated
    …D5000%26itag%3Dw160%26sigh%3DJUQG-Q3wsVYgfCwSqmGYX7sKdJA&autoplay=0&ps=blogger"

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

  • Info Line 611, Column 541: entity was defined here
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"
  • Error Line 4350, Column 25: element "embed" undefined
    allowFullScreen="true" /></object>

    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).
  • Error Line 4351, Column 395: end tag for "img" omitted, but OMITTAG NO was specified
    …ss="BLOG_mobile_video_class" id="BLOG_mobile_video-14cd64f6d723a6a2"></a></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 ">".

  • Info Line 4351, Column 119: start tag was here
    …==/0/0/0/video.3gp" type="video/3gpp"><img width="320" height="266" alt="video…
  • Error Line 4430, Column 37: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div id='summary7104018137059557467'>

    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>").

  • Error Line 4432, Column 297: end tag for "param" omitted, but OMITTAG NO was specified
    …cab#version=6,0,40,0"><param name="movie" value="//www.youtube.com/get_player">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 4432, Column 240: start tag was here
    …s/flash/swflash.cab#version=6,0,40,0"><param name="movie" value="//www.youtube…
  • Error Line 4433, Column 39: end tag for "param" omitted, but OMITTAG NO was specified
    <param name="bgcolor" value="#FFFFFF">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 4433, Column 1: start tag was here
    <param name="bgcolor" value="#FFFFFF">
  • Error Line 4434, Column 44: end tag for "param" omitted, but OMITTAG NO was specified
    <param name="allowfullscreen" value="true">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 4434, Column 1: start tag was here
    <param name="allowfullscreen" value="true">
  • Error Line 4435, Column 584: end tag for "param" omitted, but OMITTAG NO was specified
    …tag%3Dw160%26sigh%3DIT705rPAbsu05xp7r2DwdNFR4UA&amp;autoplay=0&amp;ps=blogger">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 4435, Column 1: start tag was here
    <param name="flashvars" value="flvurl=http://redirector.googlevideo.com/videopl…
  • Warning Line 4438, Column 374: reference not terminated by REFC delimiter
    …4062CCB63B5472A2587C9%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Warning Line 4438, Column 374: reference to external entity in attribute value
    …4062CCB63B5472A2587C9%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Error Line 4438, Column 374: reference to entity "iurl" for which no system identifier could be generated
    …4062CCB63B5472A2587C9%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Info Line 611, Column 370: entity was defined here
    …D5FA5BF22D7FFFDBF017BD1658%26key%3Dck2&iurl=http://video.google.com/ThumbnailS…
  • Warning Line 4438, Column 537: reference not terminated by REFC delimiter
    …D5000%26itag%3Dw160%26sigh%3DIT705rPAbsu05xp7r2DwdNFR4UA&autoplay=0&ps=blogger"

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

  • Warning Line 4438, Column 537: reference to external entity in attribute value
    …D5000%26itag%3Dw160%26sigh%3DIT705rPAbsu05xp7r2DwdNFR4UA&autoplay=0&ps=blogger"

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

  • Error Line 4438, Column 537: reference to entity "autoplay" for which no system identifier could be generated
    …D5000%26itag%3Dw160%26sigh%3DIT705rPAbsu05xp7r2DwdNFR4UA&autoplay=0&ps=blogger"

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

  • Info Line 611, Column 530: entity was defined here
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"
  • Warning Line 4438, Column 542: reference not terminated by REFC delimiter
    …D5000%26itag%3Dw160%26sigh%3DIT705rPAbsu05xp7r2DwdNFR4UA&autoplay=0&ps=blogger"

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

  • Warning Line 4438, Column 542: reference to external entity in attribute value
    …D5000%26itag%3Dw160%26sigh%3DIT705rPAbsu05xp7r2DwdNFR4UA&autoplay=0&ps=blogger"

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

  • Error Line 4438, Column 542: reference to entity "ps" for which no system identifier could be generated
    …D5000%26itag%3Dw160%26sigh%3DIT705rPAbsu05xp7r2DwdNFR4UA&autoplay=0&ps=blogger"

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

  • Info Line 611, Column 541: entity was defined here
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"
  • Error Line 4439, Column 25: element "embed" undefined
    allowFullScreen="true" /></object>

    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).
  • Error Line 4440, Column 393: end tag for "img" omitted, but OMITTAG NO was specified
    …ass="BLOG_mobile_video_class" id="BLOG_mobile_video-a36fd8823779c0e"></a></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 ">".

  • Info Line 4440, Column 119: start tag was here
    …==/0/0/0/video.3gp" type="video/3gpp"><img width="320" height="266" alt="video…
  • Error Line 4519, Column 36: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div id='summary766627269031385468'>

    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>").

  • Error Line 4521, Column 298: end tag for "param" omitted, but OMITTAG NO was specified
    …cab#version=6,0,40,0"><param name="movie" value="//www.youtube.com/get_player">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 4521, Column 241: start tag was here
    …s/flash/swflash.cab#version=6,0,40,0"><param name="movie" value="//www.youtube…
  • Error Line 4522, Column 39: end tag for "param" omitted, but OMITTAG NO was specified
    <param name="bgcolor" value="#FFFFFF">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 4522, Column 1: start tag was here
    <param name="bgcolor" value="#FFFFFF">
  • Error Line 4523, Column 44: end tag for "param" omitted, but OMITTAG NO was specified
    <param name="allowfullscreen" value="true">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 4523, Column 1: start tag was here
    <param name="allowfullscreen" value="true">
  • Error Line 4524, Column 586: end tag for "param" omitted, but OMITTAG NO was specified
    …tag%3Dw160%26sigh%3DuLFh46eihB2PyLGOs3iJ_bEX7sA&amp;autoplay=0&amp;ps=blogger">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 4524, Column 1: start tag was here
    <param name="flashvars" value="flvurl=http://redirector.googlevideo.com/videopl…
  • Warning Line 4527, Column 375: reference not terminated by REFC delimiter
    …A0951015D104096246116%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Warning Line 4527, Column 375: reference to external entity in attribute value
    …A0951015D104096246116%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Error Line 4527, Column 375: reference to entity "iurl" for which no system identifier could be generated
    …A0951015D104096246116%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Info Line 611, Column 370: entity was defined here
    …D5FA5BF22D7FFFDBF017BD1658%26key%3Dck2&iurl=http://video.google.com/ThumbnailS…
  • Warning Line 4527, Column 539: reference not terminated by REFC delimiter
    …D5000%26itag%3Dw160%26sigh%3DuLFh46eihB2PyLGOs3iJ_bEX7sA&autoplay=0&ps=blogger"

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

  • Warning Line 4527, Column 539: reference to external entity in attribute value
    …D5000%26itag%3Dw160%26sigh%3DuLFh46eihB2PyLGOs3iJ_bEX7sA&autoplay=0&ps=blogger"

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

  • Error Line 4527, Column 539: reference to entity "autoplay" for which no system identifier could be generated
    …D5000%26itag%3Dw160%26sigh%3DuLFh46eihB2PyLGOs3iJ_bEX7sA&autoplay=0&ps=blogger"

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

  • Info Line 611, Column 530: entity was defined here
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"
  • Warning Line 4527, Column 544: reference not terminated by REFC delimiter
    …D5000%26itag%3Dw160%26sigh%3DuLFh46eihB2PyLGOs3iJ_bEX7sA&autoplay=0&ps=blogger"

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

  • Warning Line 4527, Column 544: reference to external entity in attribute value
    …D5000%26itag%3Dw160%26sigh%3DuLFh46eihB2PyLGOs3iJ_bEX7sA&autoplay=0&ps=blogger"

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

  • Error Line 4527, Column 544: reference to entity "ps" for which no system identifier could be generated
    …D5000%26itag%3Dw160%26sigh%3DuLFh46eihB2PyLGOs3iJ_bEX7sA&autoplay=0&ps=blogger"

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

  • Info Line 611, Column 541: entity was defined here
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"
  • Error Line 4528, Column 25: element "embed" undefined
    allowFullScreen="true" /></object>

    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).
  • Error Line 4529, Column 395: end tag for "img" omitted, but OMITTAG NO was specified
    …ss="BLOG_mobile_video_class" id="BLOG_mobile_video-e870a04828447995"></a></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 ">".

  • Info Line 4529, Column 119: start tag was here
    …==/0/0/0/video.3gp" type="video/3gpp"><img width="320" height="266" alt="video…
  • Error Line 4608, Column 37: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div id='summary7654570832389685247'>

    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>").

  • Error Line 4610, Column 298: end tag for "param" omitted, but OMITTAG NO was specified
    …cab#version=6,0,40,0"><param name="movie" value="//www.youtube.com/get_player">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 4610, Column 241: start tag was here
    …s/flash/swflash.cab#version=6,0,40,0"><param name="movie" value="//www.youtube…
  • Error Line 4611, Column 39: end tag for "param" omitted, but OMITTAG NO was specified
    <param name="bgcolor" value="#FFFFFF">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 4611, Column 1: start tag was here
    <param name="bgcolor" value="#FFFFFF">
  • Error Line 4612, Column 44: end tag for "param" omitted, but OMITTAG NO was specified
    <param name="allowfullscreen" value="true">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 4612, Column 1: start tag was here
    <param name="allowfullscreen" value="true">
  • Error Line 4613, Column 586: end tag for "param" omitted, but OMITTAG NO was specified
    …tag%3Dw160%26sigh%3D03jgaFh-x-pnNq0thNfqexlIIzY&amp;autoplay=0&amp;ps=blogger">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 4613, Column 1: start tag was here
    <param name="flashvars" value="flvurl=http://redirector.googlevideo.com/videopl…
  • Warning Line 4616, Column 375: reference not terminated by REFC delimiter
    …3B00B9D44FFF4E3F5AB02%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Warning Line 4616, Column 375: reference to external entity in attribute value
    …3B00B9D44FFF4E3F5AB02%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Error Line 4616, Column 375: reference to entity "iurl" for which no system identifier could be generated
    …3B00B9D44FFF4E3F5AB02%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Info Line 611, Column 370: entity was defined here
    …D5FA5BF22D7FFFDBF017BD1658%26key%3Dck2&iurl=http://video.google.com/ThumbnailS…
  • Warning Line 4616, Column 539: reference not terminated by REFC delimiter
    …D5000%26itag%3Dw160%26sigh%3D03jgaFh-x-pnNq0thNfqexlIIzY&autoplay=0&ps=blogger"

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

  • Warning Line 4616, Column 539: reference to external entity in attribute value
    …D5000%26itag%3Dw160%26sigh%3D03jgaFh-x-pnNq0thNfqexlIIzY&autoplay=0&ps=blogger"

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

  • Error Line 4616, Column 539: reference to entity "autoplay" for which no system identifier could be generated
    …D5000%26itag%3Dw160%26sigh%3D03jgaFh-x-pnNq0thNfqexlIIzY&autoplay=0&ps=blogger"

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

  • Info Line 611, Column 530: entity was defined here
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"
  • Warning Line 4616, Column 544: reference not terminated by REFC delimiter
    …D5000%26itag%3Dw160%26sigh%3D03jgaFh-x-pnNq0thNfqexlIIzY&autoplay=0&ps=blogger"

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

  • Warning Line 4616, Column 544: reference to external entity in attribute value
    …D5000%26itag%3Dw160%26sigh%3D03jgaFh-x-pnNq0thNfqexlIIzY&autoplay=0&ps=blogger"

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

  • Error Line 4616, Column 544: reference to entity "ps" for which no system identifier could be generated
    …D5000%26itag%3Dw160%26sigh%3D03jgaFh-x-pnNq0thNfqexlIIzY&autoplay=0&ps=blogger"

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

  • Info Line 611, Column 541: entity was defined here
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"
  • Error Line 4617, Column 25: element "embed" undefined
    allowFullScreen="true" /></object>

    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).
  • Error Line 4618, Column 395: end tag for "img" omitted, but OMITTAG NO was specified
    …ss="BLOG_mobile_video_class" id="BLOG_mobile_video-ccb57e1c1b94a52c"></a></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 ">".

  • Info Line 4618, Column 119: start tag was here
    …==/0/0/0/video.3gp" type="video/3gpp"><img width="320" height="266" alt="video…
  • Error Line 4697, Column 37: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div id='summary6557440618311645473'>

    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>").

  • Error Line 4699, Column 298: end tag for "param" omitted, but OMITTAG NO was specified
    …cab#version=6,0,40,0"><param name="movie" value="//www.youtube.com/get_player">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 4699, Column 241: start tag was here
    …s/flash/swflash.cab#version=6,0,40,0"><param name="movie" value="//www.youtube…
  • Error Line 4700, Column 39: end tag for "param" omitted, but OMITTAG NO was specified
    <param name="bgcolor" value="#FFFFFF">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 4700, Column 1: start tag was here
    <param name="bgcolor" value="#FFFFFF">
  • Error Line 4701, Column 44: end tag for "param" omitted, but OMITTAG NO was specified
    <param name="allowfullscreen" value="true">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 4701, Column 1: start tag was here
    <param name="allowfullscreen" value="true">
  • Error Line 4702, Column 586: end tag for "param" omitted, but OMITTAG NO was specified
    …tag%3Dw160%26sigh%3DxIpcTAHTITK0P7NQHXTu613h2QE&amp;autoplay=0&amp;ps=blogger">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 4702, Column 1: start tag was here
    <param name="flashvars" value="flvurl=http://redirector.googlevideo.com/videopl…
  • Warning Line 4705, Column 375: reference not terminated by REFC delimiter
    …EEFB37F2CDE4AE1D5929D%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Warning Line 4705, Column 375: reference to external entity in attribute value
    …EEFB37F2CDE4AE1D5929D%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Error Line 4705, Column 375: reference to entity "iurl" for which no system identifier could be generated
    …EEFB37F2CDE4AE1D5929D%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Info Line 611, Column 370: entity was defined here
    …D5FA5BF22D7FFFDBF017BD1658%26key%3Dck2&iurl=http://video.google.com/ThumbnailS…
  • Warning Line 4705, Column 539: reference not terminated by REFC delimiter
    …D5000%26itag%3Dw160%26sigh%3DxIpcTAHTITK0P7NQHXTu613h2QE&autoplay=0&ps=blogger"

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

  • Warning Line 4705, Column 539: reference to external entity in attribute value
    …D5000%26itag%3Dw160%26sigh%3DxIpcTAHTITK0P7NQHXTu613h2QE&autoplay=0&ps=blogger"

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

  • Error Line 4705, Column 539: reference to entity "autoplay" for which no system identifier could be generated
    …D5000%26itag%3Dw160%26sigh%3DxIpcTAHTITK0P7NQHXTu613h2QE&autoplay=0&ps=blogger"

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

  • Info Line 611, Column 530: entity was defined here
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"
  • Warning Line 4705, Column 544: reference not terminated by REFC delimiter
    …D5000%26itag%3Dw160%26sigh%3DxIpcTAHTITK0P7NQHXTu613h2QE&autoplay=0&ps=blogger"

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

  • Warning Line 4705, Column 544: reference to external entity in attribute value
    …D5000%26itag%3Dw160%26sigh%3DxIpcTAHTITK0P7NQHXTu613h2QE&autoplay=0&ps=blogger"

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

  • Error Line 4705, Column 544: reference to entity "ps" for which no system identifier could be generated
    …D5000%26itag%3Dw160%26sigh%3DxIpcTAHTITK0P7NQHXTu613h2QE&autoplay=0&ps=blogger"

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

  • Info Line 611, Column 541: entity was defined here
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"
  • Error Line 4706, Column 25: element "embed" undefined
    allowFullScreen="true" /></object>

    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).
  • Error Line 4707, Column 395: end tag for "img" omitted, but OMITTAG NO was specified
    …ss="BLOG_mobile_video_class" id="BLOG_mobile_video-6ce98bcf8b6c1a25"></a></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 ">".

  • Info Line 4707, Column 119: start tag was here
    …==/0/0/0/video.3gp" type="video/3gpp"><img width="320" height="266" alt="video…
  • Error Line 4786, Column 37: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div id='summary8864690090455020495'>

    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>").

  • Error Line 4788, Column 298: end tag for "param" omitted, but OMITTAG NO was specified
    …cab#version=6,0,40,0"><param name="movie" value="//www.youtube.com/get_player">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 4788, Column 241: start tag was here
    …s/flash/swflash.cab#version=6,0,40,0"><param name="movie" value="//www.youtube…
  • Error Line 4789, Column 39: end tag for "param" omitted, but OMITTAG NO was specified
    <param name="bgcolor" value="#FFFFFF">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 4789, Column 1: start tag was here
    <param name="bgcolor" value="#FFFFFF">
  • Error Line 4790, Column 44: end tag for "param" omitted, but OMITTAG NO was specified
    <param name="allowfullscreen" value="true">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 4790, Column 1: start tag was here
    <param name="allowfullscreen" value="true">
  • Error Line 4791, Column 586: end tag for "param" omitted, but OMITTAG NO was specified
    …tag%3Dw160%26sigh%3Ddvwqi1-0zGHpNcqtGOMcmSf1o1Q&amp;autoplay=0&amp;ps=blogger">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 4791, Column 1: start tag was here
    <param name="flashvars" value="flvurl=http://redirector.googlevideo.com/videopl…
  • Warning Line 4794, Column 375: reference not terminated by REFC delimiter
    …41A2BD15A25A47F43E46E%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Warning Line 4794, Column 375: reference to external entity in attribute value
    …41A2BD15A25A47F43E46E%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Error Line 4794, Column 375: reference to entity "iurl" for which no system identifier could be generated
    …41A2BD15A25A47F43E46E%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Info Line 611, Column 370: entity was defined here
    …D5FA5BF22D7FFFDBF017BD1658%26key%3Dck2&iurl=http://video.google.com/ThumbnailS…
  • Warning Line 4794, Column 539: reference not terminated by REFC delimiter
    …D5000%26itag%3Dw160%26sigh%3Ddvwqi1-0zGHpNcqtGOMcmSf1o1Q&autoplay=0&ps=blogger"

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

  • Warning Line 4794, Column 539: reference to external entity in attribute value
    …D5000%26itag%3Dw160%26sigh%3Ddvwqi1-0zGHpNcqtGOMcmSf1o1Q&autoplay=0&ps=blogger"

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

  • Error Line 4794, Column 539: reference to entity "autoplay" for which no system identifier could be generated
    …D5000%26itag%3Dw160%26sigh%3Ddvwqi1-0zGHpNcqtGOMcmSf1o1Q&autoplay=0&ps=blogger"

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

  • Info Line 611, Column 530: entity was defined here
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"
  • Warning Line 4794, Column 544: reference not terminated by REFC delimiter
    …D5000%26itag%3Dw160%26sigh%3Ddvwqi1-0zGHpNcqtGOMcmSf1o1Q&autoplay=0&ps=blogger"

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

  • Warning Line 4794, Column 544: reference to external entity in attribute value
    …D5000%26itag%3Dw160%26sigh%3Ddvwqi1-0zGHpNcqtGOMcmSf1o1Q&autoplay=0&ps=blogger"

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

  • Error Line 4794, Column 544: reference to entity "ps" for which no system identifier could be generated
    …D5000%26itag%3Dw160%26sigh%3Ddvwqi1-0zGHpNcqtGOMcmSf1o1Q&autoplay=0&ps=blogger"

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

  • Info Line 611, Column 541: entity was defined here
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"
  • Error Line 4795, Column 25: element "embed" undefined
    allowFullScreen="true" /></object>

    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).
  • Error Line 4796, Column 395: end tag for "img" omitted, but OMITTAG NO was specified
    …ss="BLOG_mobile_video_class" id="BLOG_mobile_video-7d185224634d96a2"></a></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 ">".

  • Info Line 4796, Column 119: start tag was here
    …==/0/0/0/video.3gp" type="video/3gpp"><img width="320" height="266" alt="video…
  • Error Line 4875, Column 37: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div id='summary2241604444957546039'>

    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>").

  • Error Line 4877, Column 298: end tag for "param" omitted, but OMITTAG NO was specified
    …cab#version=6,0,40,0"><param name="movie" value="//www.youtube.com/get_player">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 4877, Column 241: start tag was here
    …s/flash/swflash.cab#version=6,0,40,0"><param name="movie" value="//www.youtube…
  • Error Line 4878, Column 39: end tag for "param" omitted, but OMITTAG NO was specified
    <param name="bgcolor" value="#FFFFFF">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 4878, Column 1: start tag was here
    <param name="bgcolor" value="#FFFFFF">
  • Error Line 4879, Column 44: end tag for "param" omitted, but OMITTAG NO was specified
    <param name="allowfullscreen" value="true">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 4879, Column 1: start tag was here
    <param name="allowfullscreen" value="true">
  • Error Line 4880, Column 586: end tag for "param" omitted, but OMITTAG NO was specified
    …tag%3Dw160%26sigh%3Dtzh50CKNCs3E79B3r3z5sKjbmKk&amp;autoplay=0&amp;ps=blogger">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 4880, Column 1: start tag was here
    <param name="flashvars" value="flvurl=http://redirector.googlevideo.com/videopl…
  • Warning Line 4883, Column 375: reference not terminated by REFC delimiter
    …D55D3E3D44CC1504CE18C%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Warning Line 4883, Column 375: reference to external entity in attribute value
    …D55D3E3D44CC1504CE18C%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Error Line 4883, Column 375: reference to entity "iurl" for which no system identifier could be generated
    …D55D3E3D44CC1504CE18C%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Info Line 611, Column 370: entity was defined here
    …D5FA5BF22D7FFFDBF017BD1658%26key%3Dck2&iurl=http://video.google.com/ThumbnailS…
  • Warning Line 4883, Column 539: reference not terminated by REFC delimiter
    …D5000%26itag%3Dw160%26sigh%3Dtzh50CKNCs3E79B3r3z5sKjbmKk&autoplay=0&ps=blogger"

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

  • Warning Line 4883, Column 539: reference to external entity in attribute value
    …D5000%26itag%3Dw160%26sigh%3Dtzh50CKNCs3E79B3r3z5sKjbmKk&autoplay=0&ps=blogger"

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

  • Error Line 4883, Column 539: reference to entity "autoplay" for which no system identifier could be generated
    …D5000%26itag%3Dw160%26sigh%3Dtzh50CKNCs3E79B3r3z5sKjbmKk&autoplay=0&ps=blogger"

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

  • Info Line 611, Column 530: entity was defined here
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"
  • Warning Line 4883, Column 544: reference not terminated by REFC delimiter
    …D5000%26itag%3Dw160%26sigh%3Dtzh50CKNCs3E79B3r3z5sKjbmKk&autoplay=0&ps=blogger"

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

  • Warning Line 4883, Column 544: reference to external entity in attribute value
    …D5000%26itag%3Dw160%26sigh%3Dtzh50CKNCs3E79B3r3z5sKjbmKk&autoplay=0&ps=blogger"

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

  • Error Line 4883, Column 544: reference to entity "ps" for which no system identifier could be generated
    …D5000%26itag%3Dw160%26sigh%3Dtzh50CKNCs3E79B3r3z5sKjbmKk&autoplay=0&ps=blogger"

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

  • Info Line 611, Column 541: entity was defined here
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"
  • Error Line 4884, Column 25: element "embed" undefined
    allowFullScreen="true" /></object>

    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).
  • Error Line 4885, Column 395: end tag for "img" omitted, but OMITTAG NO was specified
    …ss="BLOG_mobile_video_class" id="BLOG_mobile_video-918404fa6a4fabdc"></a></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 ">".

  • Info Line 4885, Column 119: start tag was here
    …==/0/0/0/video.3gp" type="video/3gpp"><img width="320" height="266" alt="video…
  • Error Line 4964, Column 37: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div id='summary4778729281180910125'>

    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>").

  • Error Line 4966, Column 298: end tag for "param" omitted, but OMITTAG NO was specified
    …cab#version=6,0,40,0"><param name="movie" value="//www.youtube.com/get_player">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 4966, Column 241: start tag was here
    …s/flash/swflash.cab#version=6,0,40,0"><param name="movie" value="//www.youtube…
  • Error Line 4967, Column 39: end tag for "param" omitted, but OMITTAG NO was specified
    <param name="bgcolor" value="#FFFFFF">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 4967, Column 1: start tag was here
    <param name="bgcolor" value="#FFFFFF">
  • Error Line 4968, Column 44: end tag for "param" omitted, but OMITTAG NO was specified
    <param name="allowfullscreen" value="true">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 4968, Column 1: start tag was here
    <param name="allowfullscreen" value="true">
  • Error Line 4969, Column 585: end tag for "param" omitted, but OMITTAG NO was specified
    …tag%3Dw160%26sigh%3DTPX8U00XQQvLqezT1s_R3mArEXI&amp;autoplay=0&amp;ps=blogger">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 4969, Column 1: start tag was here
    <param name="flashvars" value="flvurl=http://redirector.googlevideo.com/videopl…
  • Warning Line 4972, Column 374: reference not terminated by REFC delimiter
    …93627B0887D5F57D65913%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Warning Line 4972, Column 374: reference to external entity in attribute value
    …93627B0887D5F57D65913%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Error Line 4972, Column 374: reference to entity "iurl" for which no system identifier could be generated
    …93627B0887D5F57D65913%26key%3Dck2&iurl=http://video.google.com/ThumbnailServer…

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

  • Info Line 611, Column 370: entity was defined here
    …D5FA5BF22D7FFFDBF017BD1658%26key%3Dck2&iurl=http://video.google.com/ThumbnailS…
  • Warning Line 4972, Column 538: reference not terminated by REFC delimiter
    …D5000%26itag%3Dw160%26sigh%3DTPX8U00XQQvLqezT1s_R3mArEXI&autoplay=0&ps=blogger"

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

  • Warning Line 4972, Column 538: reference to external entity in attribute value
    …D5000%26itag%3Dw160%26sigh%3DTPX8U00XQQvLqezT1s_R3mArEXI&autoplay=0&ps=blogger"

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

  • Error Line 4972, Column 538: reference to entity "autoplay" for which no system identifier could be generated
    …D5000%26itag%3Dw160%26sigh%3DTPX8U00XQQvLqezT1s_R3mArEXI&autoplay=0&ps=blogger"

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

  • Info Line 611, Column 530: entity was defined here
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"
  • Warning Line 4972, Column 543: reference not terminated by REFC delimiter
    …D5000%26itag%3Dw160%26sigh%3DTPX8U00XQQvLqezT1s_R3mArEXI&autoplay=0&ps=blogger"

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

  • Warning Line 4972, Column 543: reference to external entity in attribute value
    …D5000%26itag%3Dw160%26sigh%3DTPX8U00XQQvLqezT1s_R3mArEXI&autoplay=0&ps=blogger"

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

  • Error Line 4972, Column 543: reference to entity "ps" for which no system identifier could be generated
    …D5000%26itag%3Dw160%26sigh%3DTPX8U00XQQvLqezT1s_R3mArEXI&autoplay=0&ps=blogger"

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

  • Info Line 611, Column 541: entity was defined here
    …D5000%26itag%3Dw160%26sigh%3DsYVfjnFHTnkUbCHEr0s7-bkAvpM&autoplay=0&ps=blogger"
  • Error Line 4973, Column 25: element "embed" undefined
    allowFullScreen="true" /></object>

    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).
  • Error Line 4974, Column 395: end tag for "img" omitted, but OMITTAG NO was specified
    …ss="BLOG_mobile_video_class" id="BLOG_mobile_video-a09104e8843f862c"></a></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 ">".

  • Info Line 4974, Column 119: start tag was here
    …==/0/0/0/video.3gp" type="video/3gpp"><img width="320" height="266" alt="video…
  • Error Line 5027, Column 59: 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
    …ttp://www.histats.com" target="_blank"><img src="http://sstatic1.histats.com/0…

    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>").

  • Warning Line 5033, Column 91: reference not terminated by REFC delimiter
    …ge?blogID=51421036228529037&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.

  • Warning Line 5033, Column 91: reference to external entity in attribute value
    …ge?blogID=51421036228529037&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;'.

  • Error Line 5033, Column 91: reference to entity "widgetType" for which no system identifier could be generated
    …ge?blogID=51421036228529037&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.

  • Info Line 484, Column 80: entity was defined here
    …com/rearrange?blogID=51421036228529037&widgetType=HTML&widgetId=HTML6&action=e…
  • Warning Line 5033, Column 105: reference not terminated by REFC delimiter
    …1036228529037&widgetType=HTML&widgetId=HTML3&action=editWidget&sectionId=main'…

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

  • Warning Line 5033, Column 105: reference to external entity in attribute value
    …1036228529037&widgetType=HTML&widgetId=HTML3&action=editWidget&sectionId=main'…

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

  • Error Line 5033, Column 105: reference to entity "widgetId" for which no system identifier could be generated
    …1036228529037&widgetType=HTML&widgetId=HTML3&action=editWidget&sectionId=main'…

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

  • Info Line 484, Column 96: entity was defined here
    …ogID=51421036228529037&widgetType=HTML&widgetId=HTML6&action=editWidget&sectio…
  • Warning Line 5033, Column 118: reference not terminated by REFC delimiter
    …&widgetType=HTML&widgetId=HTML3&action=editWidget&sectionId=main' onclick='ret…

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

  • Warning Line 5033, Column 118: reference to external entity in attribute value
    …&widgetType=HTML&widgetId=HTML3&action=editWidget&sectionId=main' onclick='ret…

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

  • Error Line 5033, Column 118: reference to entity "action" for which no system identifier could be generated
    …&widgetType=HTML&widgetId=HTML3&action=editWidget&sectionId=main' onclick='ret…

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

  • Info Line 484, Column 111: entity was defined here
    …8529037&widgetType=HTML&widgetId=HTML6&action=editWidget&sectionId=header2' on…
  • Warning Line 5033, Column 139: reference not terminated by REFC delimiter
    …etId=HTML3&action=editWidget&sectionId=main' onclick='return _WidgetManager._P…

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

  • Warning Line 5033, Column 139: reference to external entity in attribute value
    …etId=HTML3&action=editWidget&sectionId=main' onclick='return _WidgetManager._P…

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

  • Error Line 5033, Column 139: reference to entity "sectionId" for which no system identifier could be generated
    …etId=HTML3&action=editWidget&sectionId=main' onclick='return _WidgetManager._P…

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

  • Info Line 484, Column 129: entity was defined here
    …=HTML&widgetId=HTML6&action=editWidget&sectionId=header2' onclick='return _Wid…
  • Error Line 5045, Column 33: ID "footer" already defined
    <div class='footer section' id='footer'><div class='widget HTML' id='HTML4'>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 5044, Column 10: ID "footer" first defined here
    <div id='footer'>
  • Warning Line 5052, Column 91: reference not terminated by REFC delimiter
    …ge?blogID=51421036228529037&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.

  • Warning Line 5052, Column 91: reference to external entity in attribute value
    …ge?blogID=51421036228529037&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;'.

  • Error Line 5052, Column 91: reference to entity "widgetType" for which no system identifier could be generated
    …ge?blogID=51421036228529037&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.

  • Info Line 484, Column 80: entity was defined here
    …com/rearrange?blogID=51421036228529037&widgetType=HTML&widgetId=HTML6&action=e…
  • Warning Line 5052, Column 105: reference not terminated by REFC delimiter
    …1036228529037&widgetType=HTML&widgetId=HTML4&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.

  • Warning Line 5052, Column 105: reference to external entity in attribute value
    …1036228529037&widgetType=HTML&widgetId=HTML4&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;'.

  • Error Line 5052, Column 105: reference to entity "widgetId" for which no system identifier could be generated
    …1036228529037&widgetType=HTML&widgetId=HTML4&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.

  • Info Line 484, Column 96: entity was defined here
    …ogID=51421036228529037&widgetType=HTML&widgetId=HTML6&action=editWidget&sectio…
  • Warning Line 5052, Column 118: reference not terminated by REFC delimiter
    …&widgetType=HTML&widgetId=HTML4&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.

  • Warning Line 5052, Column 118: reference to external entity in attribute value
    …&widgetType=HTML&widgetId=HTML4&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;'.

  • Error Line 5052, Column 118: reference to entity "action" for which no system identifier could be generated
    …&widgetType=HTML&widgetId=HTML4&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.

  • Info Line 484, Column 111: entity was defined here
    …8529037&widgetType=HTML&widgetId=HTML6&action=editWidget&sectionId=header2' on…
  • Warning Line 5052, Column 139: reference not terminated by REFC delimiter
    …etId=HTML4&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.

  • Warning Line 5052, Column 139: reference to external entity in attribute value
    …etId=HTML4&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;'.

  • Error Line 5052, Column 139: reference to entity "sectionId" for which no system identifier could be generated
    …etId=HTML4&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.

  • Info Line 484, Column 129: entity was defined here
    …=HTML&widgetId=HTML6&action=editWidget&sectionId=header2' onclick='return _Wid…
  • Error Line 5063, Column 21: required attribute "type" not specified
    <script id="_wautv9">var _wau = _wau || []; _wau.push(["small", "qlgx13lcxps3",…

    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>.

  • Warning Line 5072, Column 91: reference not terminated by REFC delimiter
    …ge?blogID=51421036228529037&widgetType=HTML&widgetId=HTML8&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.

  • Warning Line 5072, Column 91: reference to external entity in attribute value
    …ge?blogID=51421036228529037&widgetType=HTML&widgetId=HTML8&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;'.

  • Error Line 5072, Column 91: reference to entity "widgetType" for which no system identifier could be generated
    …ge?blogID=51421036228529037&widgetType=HTML&widgetId=HTML8&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.

  • Info Line 484, Column 80: entity was defined here
    …com/rearrange?blogID=51421036228529037&widgetType=HTML&widgetId=HTML6&action=e…
  • Warning Line 5072, Column 105: reference not terminated by REFC delimiter
    …1036228529037&widgetType=HTML&widgetId=HTML8&action=editWidget&sectionId=col1'…

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

  • Warning Line 5072, Column 105: reference to external entity in attribute value
    …1036228529037&widgetType=HTML&widgetId=HTML8&action=editWidget&sectionId=col1'…

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

  • Error Line 5072, Column 105: reference to entity "widgetId" for which no system identifier could be generated
    …1036228529037&widgetType=HTML&widgetId=HTML8&action=editWidget&sectionId=col1'…

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

  • Info Line 484, Column 96: entity was defined here
    …ogID=51421036228529037&widgetType=HTML&widgetId=HTML6&action=editWidget&sectio…
  • Warning Line 5072, Column 118: reference not terminated by REFC delimiter
    …&widgetType=HTML&widgetId=HTML8&action=editWidget&sectionId=col1' onclick='ret…

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

  • Warning Line 5072, Column 118: reference to external entity in attribute value
    …&widgetType=HTML&widgetId=HTML8&action=editWidget&sectionId=col1' onclick='ret…

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

  • Error Line 5072, Column 118: reference to entity "action" for which no system identifier could be generated
    …&widgetType=HTML&widgetId=HTML8&action=editWidget&sectionId=col1' onclick='ret…

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

  • Info Line 484, Column 111: entity was defined here
    …8529037&widgetType=HTML&widgetId=HTML6&action=editWidget&sectionId=header2' on…
  • Warning Line 5072, Column 139: reference not terminated by REFC delimiter
    …etId=HTML8&action=editWidget&sectionId=col1' onclick='return _WidgetManager._P…

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

  • Warning Line 5072, Column 139: reference to external entity in attribute value
    …etId=HTML8&action=editWidget&sectionId=col1' onclick='return _WidgetManager._P…

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

  • Error Line 5072, Column 139: reference to entity "sectionId" for which no system identifier could be generated
    …etId=HTML8&action=editWidget&sectionId=col1' onclick='return _WidgetManager._P…

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

  • Info Line 484, Column 129: entity was defined here
    …=HTML&widgetId=HTML6&action=editWidget&sectionId=header2' onclick='return _Wid…
  • Warning Line 5091, Column 91: reference not terminated by REFC delimiter
    …ge?blogID=51421036228529037&widgetType=HTML&widgetId=HTML5&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.

  • Warning Line 5091, Column 91: reference to external entity in attribute value
    …ge?blogID=51421036228529037&widgetType=HTML&widgetId=HTML5&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;'.

  • Error Line 5091, Column 91: reference to entity "widgetType" for which no system identifier could be generated
    …ge?blogID=51421036228529037&widgetType=HTML&widgetId=HTML5&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.

  • Info Line 484, Column 80: entity was defined here
    …com/rearrange?blogID=51421036228529037&widgetType=HTML&widgetId=HTML6&action=e…
  • Warning Line 5091, Column 105: reference not terminated by REFC delimiter
    …1036228529037&widgetType=HTML&widgetId=HTML5&action=editWidget&sectionId=col3'…

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

  • Warning Line 5091, Column 105: reference to external entity in attribute value
    …1036228529037&widgetType=HTML&widgetId=HTML5&action=editWidget&sectionId=col3'…

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

  • Error Line 5091, Column 105: reference to entity "widgetId" for which no system identifier could be generated
    …1036228529037&widgetType=HTML&widgetId=HTML5&action=editWidget&sectionId=col3'…

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

  • Info Line 484, Column 96: entity was defined here
    …ogID=51421036228529037&widgetType=HTML&widgetId=HTML6&action=editWidget&sectio…
  • Warning Line 5091, Column 118: reference not terminated by REFC delimiter
    …&widgetType=HTML&widgetId=HTML5&action=editWidget&sectionId=col3' onclick='ret…

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

  • Warning Line 5091, Column 118: reference to external entity in attribute value
    …&widgetType=HTML&widgetId=HTML5&action=editWidget&sectionId=col3' onclick='ret…

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

  • Error Line 5091, Column 118: reference to entity "action" for which no system identifier could be generated
    …&widgetType=HTML&widgetId=HTML5&action=editWidget&sectionId=col3' onclick='ret…

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

  • Info Line 484, Column 111: entity was defined here
    …8529037&widgetType=HTML&widgetId=HTML6&action=editWidget&sectionId=header2' on…
  • Warning Line 5091, Column 139: reference not terminated by REFC delimiter
    …etId=HTML5&action=editWidget&sectionId=col3' onclick='return _WidgetManager._P…

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

  • Warning Line 5091, Column 139: reference to external entity in attribute value
    …etId=HTML5&action=editWidget&sectionId=col3' onclick='return _WidgetManager._P…

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

  • Error Line 5091, Column 139: reference to entity "sectionId" for which no system identifier could be generated
    …etId=HTML5&action=editWidget&sectionId=col3' onclick='return _WidgetManager._P…

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

  • Info Line 484, Column 129: entity was defined here
    …=HTML&widgetId=HTML6&action=editWidget&sectionId=header2' onclick='return _Wid…
  • Warning Line 5113, Column 49: character "&" is the first character of a delimiter but occurred as data
    …(BLOG_attachCsiOnload) != 'undefined' && BLOG_attachCsiOnload != null) { windo…

    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.
  • Warning Line 5113, Column 50: character "&" is the first character of a delimiter but occurred as data
    …BLOG_attachCsiOnload) != 'undefined' && BLOG_attachCsiOnload != null) { window…

    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.

Visitor Analysis

Daily Visitor
  • 5.133 visits