Live Cricket Streaming ...

footcric.com
  • Domain Name
    footcric.com
  • Favicon
  • Google Page Rank
    1
  • Alexa Rank
    #277782
  • Page Size
    767 B
  • Ip Address
    75.126.101.234
  • Heading
    H1: 0, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    0 GIF, 0 JPG, 0 PNG

Website Meta Analysis

  • Title
    Footcric - Watch Live Cricket Streaming, Live Cricket Video
  • Meta Keyword
    hitcric, live cricket, live cricket streaming, watch live cricket, free cricket, live cricket match, online cricket, cricket online, test, pakistan, sri lanka, england, west indies, cricpower
  • Meta Description
    Live Cricket Streaming

Technical Analysis

  • Webserver
    Apache
  • Ip Address
    75.126.101.234
  • Domain Age
    2 Years, 2 Months, 0 days.
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from footcric.com.

HTML Analysis

  • date: Tue, 14 May 2013 12:05:34 GMT
  • server: Apache
  • content-length: 756
  • connection: close
  • content-type: text/html; charset=UTF-8
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for footcric.com

DNS Analysis


DNS servers
ns2071.hostgator.com [174.120.150.226]
ns2072.hostgator.com [174.120.150.227]


DNS Records

Answer records
footcric.com TXT v=spf1 a mx include:websitewelcome.com ~all 14400s
footcric.com MX
preference: 0
exchange: footcric.com
14400s
footcric.com SOA
server: ns2071.hostgator.com
email: root@gator1036.hostgator.com
serial: 2013020702
refresh: 86400
retry: 7200
expire: 3600000
minimum ttl: 86400
86400s
footcric.com NS  ns2071.hostgator.com 86400s
footcric.com NS  ns2072.hostgator.com 86400s
footcric.com A 174.120.150.250 14400s

Authority records

Additional records
footcric.com A 174.120.150.250 14400s
ns2071.hostgator.com A 174.120.150.226 14400s
ns2072.hostgator.com A 174.120.150.227 14400s

IP 75.126.101.234 Analysis

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 212 Errors
  • 76 Warnings
Ratio Text/Html
  • 0.877444589308996
Message Error
  • Warning Line 5, Column 245: character "&" is the first character of a delimiter but occurred as data
    …r:c,load:f};try{var g=null;if(a.chrome&&a.chrome.csi)g=Math.floor(a.chrome.csi…

    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 5, Column 247: cannot generate system identifier for general entity "a.chrome.csi"
    …c,load:f};try{var g=null;if(a.chrome&&a.chrome.csi)g=Math.floor(a.chrome.csi()…

    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 5, Column 247: general entity "a.chrome.csi" not defined and no default entity
    …c,load:f};try{var g=null;if(a.chrome&&a.chrome.csi)g=Math.floor(a.chrome.csi()…

    This is usually a cascading error caused by 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 5, Column 259: reference not terminated by REFC delimiter
    …y{var g=null;if(a.chrome&&a.chrome.csi)g=Math.floor(a.chrome.csi().pageT);if(g…

    If you meant to include an entity that starts with "&", then you should terminate it 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 5, Column 259: reference to entity "a.chrome.csi" for which no system identifier could be generated
    …y{var g=null;if(a.chrome&&a.chrome.csi)g=Math.floor(a.chrome.csi().pageT);if(g…

    This is usually a cascading error caused by 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 5, Column 246: entity was defined here
    …:c,load:f};try{var g=null;if(a.chrome&&a.chrome.csi)g=Math.floor(a.chrome.csi(…
  • Warning Line 5, Column 525: character "<" is the first character of a delimiter but occurred as data
    …ffsetTop;while(b=b.offsetParent)}b=d;b<=750&&a.jstiming.load.tick("aft")};var …

    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 5, Column 530: character "&" is the first character of a delimiter but occurred as data
    …Top;while(b=b.offsetParent)}b=d;b<=750&&a.jstiming.load.tick("aft")};var j=fal…

    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 5, Column 532: cannot generate system identifier for general entity "a.jstiming.load.tick"
    …p;while(b=b.offsetParent)}b=d;b<=750&&a.jstiming.load.tick("aft")};var j=false…

    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 5, Column 532: general entity "a.jstiming.load.tick" not defined and no default entity
    …p;while(b=b.offsetParent)}b=d;b<=750&&a.jstiming.load.tick("aft")};var j=false…

    This is usually a cascading error caused by 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 5, Column 552: reference not terminated by REFC delimiter
    …rent)}b=d;b<=750&&a.jstiming.load.tick("aft")};var j=false;function k(){if(!j)…

    If you meant to include an entity that starts with "&", then you should terminate it 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 5, Column 552: reference to entity "a.jstiming.load.tick" for which no system identifier could be generated
    …rent)}b=d;b<=750&&a.jstiming.load.tick("aft")};var j=false;function k(){if(!j)…

    This is usually a cascading error caused by 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 5, Column 531: entity was defined here
    …op;while(b=b.offsetParent)}b=d;b<=750&&a.jstiming.load.tick("aft")};var j=fals…
  • Warning Line 24, Column 129: cannot generate system identifier for general entity "zx"
    ….css?targetBlogID=4130086795270491146&zx=0da7ad6d-f4f7-4c48-aa2e-f7505497ecdd"…

    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 24, Column 129: general entity "zx" not defined and no default entity
    ….css?targetBlogID=4130086795270491146&zx=0da7ad6d-f4f7-4c48-aa2e-f7505497ecdd"…

    This is usually a cascading error caused by 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 24, Column 131: reference not terminated by REFC delimiter
    …css?targetBlogID=4130086795270491146&zx=0da7ad6d-f4f7-4c48-aa2e-f7505497ecdd"/>

    If you meant to include an entity that starts with "&", then you should terminate it 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 24, Column 131: reference to external entity in attribute value
    …css?targetBlogID=4130086795270491146&zx=0da7ad6d-f4f7-4c48-aa2e-f7505497ecdd"/>

    This is generally the sign of an ampersand that 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 24, Column 131: reference to entity "zx" for which no system identifier could be generated
    …css?targetBlogID=4130086795270491146&zx=0da7ad6d-f4f7-4c48-aa2e-f7505497ecdd"/>

    This is usually a cascading error caused by 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 24, Column 128: entity was defined here
    …n.css?targetBlogID=4130086795270491146&zx=0da7ad6d-f4f7-4c48-aa2e-f7505497ecdd…
  • Warning Line 30, Column 5: multiple comments in comment declaration
    -----------------------------------------------
  • Warning Line 30, Column 9: multiple comments in comment declaration
    -----------------------------------------------
  • Warning Line 30, Column 13: multiple comments in comment declaration
    -----------------------------------------------
  • Warning Line 30, Column 17: multiple comments in comment declaration
    -----------------------------------------------
  • Warning Line 30, Column 21: multiple comments in comment declaration
    -----------------------------------------------
  • Warning Line 30, Column 25: multiple comments in comment declaration
    -----------------------------------------------
  • Warning Line 30, Column 29: multiple comments in comment declaration
    -----------------------------------------------
  • Warning Line 30, Column 33: multiple comments in comment declaration
    -----------------------------------------------
  • Warning Line 30, Column 37: multiple comments in comment declaration
    -----------------------------------------------
  • Warning Line 30, Column 41: multiple comments in comment declaration
    -----------------------------------------------
  • Warning Line 30, Column 45: multiple comments in comment declaration
    -----------------------------------------------
  • Error Line 30, Column 47: invalid comment declaration: found name character outside comment but inside comment declaration
    -----------------------------------------------
  • Info Line 28, Column 41: comment declaration started here
    <style id='page-skin-1' type='text/css'><!--
  • Error Line 38, Column 16: there is no attribute "name"
    <Variable name="bgcolor" description="Page Background Color"

    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 38, Column 38: there is no attribute "description"
    <Variable name="bgcolor" description="Page Background Color"

    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 39, Column 6: there is no attribute "type"
    type="color" default="#000">

    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 39, Column 22: there is no attribute "default"
    type="color" default="#000">

    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 39, Column 28: element "Variable" undefined
    type="color" default="#000">

    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 41, Column 28: element "Variable" undefined
    type="color" default="#333">

    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 43, Column 28: element "Variable" undefined
    type="color" default="#58a">

    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 45, Column 28: element "Variable" undefined
    type="color" default="#666">

    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 47, Column 28: element "Variable" undefined
    type="color" default="#999">

    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 49, Column 28: element "Variable" undefined
    type="color" default="#c60">

    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 51, Column 28: element "Variable" undefined
    type="color" default="#ccc">

    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 53, Column 28: element "Variable" undefined
    type="color" default="#999">

    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 55, Column 28: element "Variable" undefined
    type="color" default="#666">

    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 57, Column 28: element "Variable" undefined
    type="color" default="#999">

    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 59, Column 56: element "Variable" undefined
    type="font" default="normal normal 100% Georgia, Serif">

    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 62, Column 78: element "Variable" undefined
    default="normal normal 78% 'Trebuchet MS',Trebuchet,Arial,Verdana,Sans-serif">

    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 65, Column 44: element "Variable" undefined
    default="normal normal 200% Georgia, Serif">

    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 68, Column 82: element "Variable" undefined
    …ault="normal normal 78% 'Trebuchet MS', Trebuchet, Arial, Verdana, Sans-serif">

    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 71, Column 82: element "Variable" undefined
    …ault="normal normal 78% 'Trebuchet MS', Trebuchet, Arial, Verdana, Sans-serif">

    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 73, Column 32: element "Variable" undefined
    type="automatic" default="left">

    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 75, Column 33: element "Variable" undefined
    type="automatic" default="right">

    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 360, Column 11: end tag for "Variable" omitted, but OMITTAG NO was specified
    --></style>

    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 74, Column 1: start tag was here
    <Variable name="endSide" description="Side where text ends in blog language"
  • Error Line 360, Column 11: end tag for "Variable" omitted, but OMITTAG NO was specified
    --></style>

    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 72, Column 1: start tag was here
    <Variable name="startSide" description="Side where text starts in blog language"
  • Error Line 360, Column 11: end tag for "Variable" omitted, but OMITTAG NO was specified
    --></style>

    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 69, Column 1: start tag was here
    <Variable name="postfooterfont" description="Post Footer Font"
  • Error Line 360, Column 11: end tag for "Variable" omitted, but OMITTAG NO was specified
    --></style>

    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 66, Column 1: start tag was here
    <Variable name="descriptionfont" description="Blog Description Font"
  • Error Line 360, Column 11: end tag for "Variable" omitted, but OMITTAG NO was specified
    --></style>

    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 63, Column 1: start tag was here
    <Variable name="pagetitlefont" description="Blog Title Font"
  • Error Line 360, Column 11: end tag for "Variable" omitted, but OMITTAG NO was specified
    --></style>

    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 60, Column 1: start tag was here
    <Variable name="headerfont" description="Sidebar Title Font"
  • Error Line 360, Column 11: end tag for "Variable" omitted, but OMITTAG NO was specified
    --></style>

    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 58, Column 1: start tag was here
    <Variable name="bodyfont" description="Text Font"
  • Error Line 360, Column 11: end tag for "Variable" omitted, but OMITTAG NO was specified
    --></style>

    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 56, Column 1: start tag was here
    <Variable name="visitedlinkcolor" description="Visited Link Color"
  • Error Line 360, Column 11: end tag for "Variable" omitted, but OMITTAG NO was specified
    --></style>

    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 54, Column 1: start tag was here
    <Variable name="sidebartextcolor" description="Sidebar Text Color"
  • Error Line 360, Column 11: end tag for "Variable" omitted, but OMITTAG NO was specified
    --></style>

    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 52, Column 1: start tag was here
    <Variable name="sidebarcolor" description="Sidebar Title Color"
  • Error Line 360, Column 11: end tag for "Variable" omitted, but OMITTAG NO was specified
    --></style>

    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 50, Column 1: start tag was here
    <Variable name="bordercolor" description="Border Color"
  • Error Line 360, Column 11: end tag for "Variable" omitted, but OMITTAG NO was specified
    --></style>

    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 48, Column 1: start tag was here
    <Variable name="titlecolor" description="Post Title Color"
  • Error Line 360, Column 11: end tag for "Variable" omitted, but OMITTAG NO was specified
    --></style>

    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 46, Column 1: start tag was here
    <Variable name="descriptioncolor" description="Blog Description Color"
  • Error Line 360, Column 11: end tag for "Variable" omitted, but OMITTAG NO was specified
    --></style>

    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 44, Column 1: start tag was here
    <Variable name="pagetitlecolor" description="Blog Title Color"
  • Error Line 360, Column 11: end tag for "Variable" omitted, but OMITTAG NO was specified
    --></style>

    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 42, Column 1: start tag was here
    <Variable name="linkcolor" description="Link Color"
  • Error Line 360, Column 11: end tag for "Variable" omitted, but OMITTAG NO was specified
    --></style>

    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 40, Column 1: start tag was here
    <Variable name="textcolor" description="Text Color"
  • Error Line 360, Column 11: end tag for "Variable" omitted, but OMITTAG NO was specified
    --></style>

    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 38, Column 1: start tag was here
    <Variable name="bgcolor" description="Page Background Color"
  • Error Line 377, Column 13: there is no attribute "src"
    <iframe src="http://www.blogger.com/navbar.g?targetBlogID=4130086795270491146&a…

    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 377, Column 350: there is no attribute "marginwidth"
    …%2Fwww.footcric.info/%2F" marginwidth="0" marginheight="0" scrolling="no" fram…

    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 377, Column 367: there is no attribute "marginheight"
    …nfo/%2F" marginwidth="0" marginheight="0" scrolling="no" frameborder="0" heigh…

    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 377, Column 381: there is no attribute "scrolling"
    …nwidth="0" marginheight="0" scrolling="no" frameborder="0" height="30px" width…

    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 377, Column 398: there is no attribute "frameborder"
    …height="0" scrolling="no" frameborder="0" height="30px" width="100%" id="navba…

    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 377, Column 409: there is no attribute "height"
    …scrolling="no" frameborder="0" height="30px" width="100%" id="navbar-iframe" a…

    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 377, Column 422: there is no attribute "width"
    …" frameborder="0" height="30px" width="100%" id="navbar-iframe" allowtranspare…

    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 377, Column 432: there is no attribute "id"
    …der="0" height="30px" width="100%" id="navbar-iframe" allowtransparency="true"…

    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 377, Column 466: there is no attribute "allowtransparency"
    … id="navbar-iframe" allowtransparency="true" title="Blogger Navigation and Sea…

    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 377, Column 479: there is no attribute "title"
    …frame" allowtransparency="true" title="Blogger Navigation and Search"></iframe…

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

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

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

  • Error Line 377, Column 510: element "iframe" undefined
    …frame" allowtransparency="true" title="Blogger Navigation and Search"></iframe>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 390, Column 134: there is no attribute "copyhistory"
    …rolling="no" height="150" copyhistory="false" name="iframe" align="center"></i…

    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 390, Column 147: there is no attribute "name"
    …no" height="150" copyhistory="false" name="iframe" align="center"></iframe></a>

    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 390, Column 162: there is no attribute "align"
    …no" height="150" copyhistory="false" name="iframe" align="center"></iframe></a>

    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 390, Column 170: element "iframe" undefined
    …no" height="150" copyhistory="false" name="iframe" align="center"></iframe></a>

    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 399, Column 18: there is no attribute "language"
    <script language='javascript'>

    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 399, Column 30: required attribute "type" not specified
    <script language='javascript'>

    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 423, Column 5: invalid comment declaration: found name start character outside comment but inside comment declaration
    <!--INFOLINKS_ON-->
  • Info Line 400, Column 1: comment declaration started here
    <!--
  • Error Line 425, Column 24: there is no attribute "height"
    <td colspan="1" height="1" align="center">

    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 425, Column 42: document type does not allow element "td" here
    <td colspan="1" height="1" align="center">

    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 426, Column 22: there is no attribute "align"
                <p align="center">

    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 428, Column 19: document type does not allow element "p" here; missing one of "object", "ins", "del", "map", "button" start-tag
     <p align="center">

    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 432, Column 29: document type does not allow element "p" here; missing one of "object", "ins", "del", "map", "button" start-tag
               <p align="center">

    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 433, Column 15: there is no attribute "face"
    <b><font face="Verdana" color="#FF7700" style="font-size: 12pt; ">

    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 433, Column 31: there is no attribute "color"
    <b><font face="Verdana" color="#FF7700" style="font-size: 12pt; ">

    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 433, Column 47: there is no attribute "style"
    <b><font face="Verdana" color="#FF7700" style="font-size: 12pt; ">

    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 433, Column 66: element "font" undefined
    <b><font face="Verdana" color="#FF7700" style="font-size: 12pt; ">

    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).
  • Warning Line 435, Column 61: character "&" is the first character of a delimiter but occurred as data
    …b(2, 145, 57); font-size: 100%;">Live & Highlights<br /></span></font></b></p>…

    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 435, Column 105: end tag for "p" omitted, but OMITTAG NO was specified
    … 145, 57); font-size: 100%;">Live & Highlights<br /></span></font></b></p></td>

    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 428, Column 2: start tag was here
     <p align="center">
  • Error Line 435, Column 105: end tag for "p" omitted, but OMITTAG NO was specified
    … 145, 57); font-size: 100%;">Live & Highlights<br /></span></font></b></p></td>

    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 426, Column 13: start tag was here
                <p align="center">
  • Error Line 438, Column 56: document type does not allow element "input" here
    <input type="hidden" name="IL_RELATED_TAGS" value="1" />

    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 439, Column 8: element "center" undefined
    <center><!-- AddThis Button BEGIN -->

    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 444, Column 6: end tag for "script" omitted, but OMITTAG NO was specified
    </div>

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

  • Info Line 399, Column 1: start tag was here
    <script language='javascript'>
  • Warning Line 448, Column 88: cannot generate system identifier for general entity "widgetType"
    …/rearrange?blogID=4130086795270491146&widgetType=HTML&widgetId=HTML3&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 448, Column 88: general entity "widgetType" not defined and no default entity
    …/rearrange?blogID=4130086795270491146&widgetType=HTML&widgetId=HTML3&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 448, Column 98: reference not terminated by REFC delimiter
    …?blogID=4130086795270491146&widgetType=HTML&widgetId=HTML3&action=editWidget' …

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

  • Warning Line 448, Column 98: reference to external entity in attribute value
    …?blogID=4130086795270491146&widgetType=HTML&widgetId=HTML3&action=editWidget' …

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

  • Error Line 448, Column 98: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=4130086795270491146&widgetType=HTML&widgetId=HTML3&action=editWidget' …

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

  • Info Line 448, Column 87: entity was defined here
    …m/rearrange?blogID=4130086795270491146&widgetType=HTML&widgetId=HTML3&action=e…
  • Warning Line 448, Column 104: cannot generate system identifier for general entity "widgetId"
    …D=4130086795270491146&widgetType=HTML&widgetId=HTML3&action=editWidget' onclic…

    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 448, Column 104: general entity "widgetId" not defined and no default entity
    …D=4130086795270491146&widgetType=HTML&widgetId=HTML3&action=editWidget' onclic…

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

  • Warning Line 448, Column 112: reference not terminated by REFC delimiter
    …6795270491146&widgetType=HTML&widgetId=HTML3&action=editWidget' onclick='retur…

    If you meant to include an entity that starts with "&", then you should terminate it 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 448, Column 112: reference to external entity in attribute value
    …6795270491146&widgetType=HTML&widgetId=HTML3&action=editWidget' onclick='retur…

    This is generally the sign of an ampersand that 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 448, Column 112: reference to entity "widgetId" for which no system identifier could be generated
    …6795270491146&widgetType=HTML&widgetId=HTML3&action=editWidget' onclick='retur…

    This is usually a cascading error caused by 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 448, Column 103: entity was defined here
    …ID=4130086795270491146&widgetType=HTML&widgetId=HTML3&action=editWidget' oncli…
  • Warning Line 448, Column 119: cannot generate system identifier for general entity "action"
    …491146&widgetType=HTML&widgetId=HTML3&action=editWidget' 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 448, Column 119: general entity "action" not defined and no default entity
    …491146&widgetType=HTML&widgetId=HTML3&action=editWidget' 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 448, Column 125: reference not terminated by REFC delimiter
    …&widgetType=HTML&widgetId=HTML3&action=editWidget' onclick='return _WidgetMana…

    If you meant to include an entity that starts with "&", then you should terminate it 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 448, Column 125: reference to external entity in attribute value
    …&widgetType=HTML&widgetId=HTML3&action=editWidget' onclick='return _WidgetMana…

    This is generally the sign of an ampersand that 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 448, Column 125: reference to entity "action" for which no system identifier could be generated
    …&widgetType=HTML&widgetId=HTML3&action=editWidget' onclick='return _WidgetMana…

    This is usually a cascading error caused by 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 448, Column 118: entity was defined here
    …0491146&widgetType=HTML&widgetId=HTML3&action=editWidget' onclick='return _Wid…
  • Error Line 448, Column 225: there is no attribute "target"
    …upConfig(document.getElementById("HTML3"));' target='configHTML3' title='Edit'>

    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 459, Column 157: element "iframe" undefined
    …lling="no" width="680" name="iframe1"/>Your browser does not support iframes.<…

    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 459, Column 204: end tag for element "iframe" which is not open
    …no" width="680" name="iframe1"/>Your browser does not support iframes.</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 465, Column 98: reference not terminated by REFC delimiter
    …?blogID=4130086795270491144&widgetType=HTML&widgetId=HTML4&action=editWidget' …

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

  • Warning Line 465, Column 98: reference to external entity in attribute value
    …?blogID=4130086795270491144&widgetType=HTML&widgetId=HTML4&action=editWidget' …

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

  • Error Line 465, Column 98: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=4130086795270491144&widgetType=HTML&widgetId=HTML4&action=editWidget' …

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

  • Info Line 448, Column 87: entity was defined here
    …m/rearrange?blogID=4130086795270491146&widgetType=HTML&widgetId=HTML3&action=e…
  • Warning Line 465, Column 112: reference not terminated by REFC delimiter
    …6795270491144&widgetType=HTML&widgetId=HTML4&action=editWidget' onclick='retur…

    If you meant to include an entity that starts with "&", then you should terminate it 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 465, Column 112: reference to external entity in attribute value
    …6795270491144&widgetType=HTML&widgetId=HTML4&action=editWidget' onclick='retur…

    This is generally the sign of an ampersand that 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 465, Column 112: reference to entity "widgetId" for which no system identifier could be generated
    …6795270491144&widgetType=HTML&widgetId=HTML4&action=editWidget' onclick='retur…

    This is usually a cascading error caused by 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 448, Column 103: entity was defined here
    …ID=4130086795270491146&widgetType=HTML&widgetId=HTML3&action=editWidget' oncli…
  • Warning Line 465, Column 125: reference not terminated by REFC delimiter
    …&widgetType=HTML&widgetId=HTML4&action=editWidget' onclick='return _WidgetMana…

    If you meant to include an entity that starts with "&", then you should terminate it 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 465, Column 125: reference to external entity in attribute value
    …&widgetType=HTML&widgetId=HTML4&action=editWidget' onclick='return _WidgetMana…

    This is generally the sign of an ampersand that 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 465, Column 125: reference to entity "action" for which no system identifier could be generated
    …&widgetType=HTML&widgetId=HTML4&action=editWidget' onclick='return _WidgetMana…

    This is usually a cascading error caused by 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 448, Column 118: entity was defined here
    …0491146&widgetType=HTML&widgetId=HTML3&action=editWidget' onclick='return _Wid…
  • Error Line 473, Column 8: element "center" undefined
    <center>

    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 474, Column 77: there is no attribute "border"
    …tcr.php" target="iframe1"><img border="2" width="115" src="http://2.bp.blogspo…

    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 474, Column 227: required attribute "alt" not specified
    …AAAACM/yEjWaeF7LrA/s1600/CHANNEL%2B1.jpg" class="cssbutton2" height="45" /></a>

    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 476, Column 226: required attribute "alt" not specified
    …AAAACU/urlbbrNrJvs/s1600/CHANNEL%2B2.jpg" class="cssbutton2" height="45" /></a>

    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 478, Column 226: required attribute "alt" not specified
    …AAAACc/S5FjOc0W5xQ/s1600/CHANNEL%2B3.jpg" class="cssbutton2" height="45" /></a>

    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 480, Column 222: required attribute "alt" not specified
    …AAAACk/IsWJWU9zplk/s1600/CHANNEL%2B4.jpg" class="cssbutton2" height="45" /></a>

    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 482, Column 232: required attribute "alt" not specified
    …AAAACs/n4AXwJvfc4M/s1600/CHANNEL%2B5.jpg" class="cssbutton2" height="45" /></a>

    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 484, Column 225: required attribute "alt" not specified
    …AAAAC0/40edsfhvKkg/s1600/CHANNEL%2B6.jpg" class="cssbutton2" height="45" /></a>

    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 486, Column 223: required attribute "alt" not specified
    …AAAAC8/NcZyuUOjF3E/s1600/CHANNEL%2B7.jpg" class="cssbutton2" height="45" /></a>

    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 488, Column 230: required attribute "alt" not specified
    …AAAADE/fcS0xmotbC4/s1600/CHANNEL%2B8.jpg" class="cssbutton2" height="45" /></a>

    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 490, Column 220: required attribute "alt" not specified
    …AAAADM/cSKMDp386ec/s1600/CHANNEL%2B9.jpg" class="cssbutton2" height="45" /></a>

    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 492, Column 230: required attribute "alt" not specified
    …AAAADk/lCiV59Qgg_Y/s128/CHANNEL%2010.jpg" class="cssbutton2" height="45" /></a>

    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 494, Column 218: required attribute "alt" not specified
    …-53I/AAAAAAAAADw/3hrXGGhuAqI/s128/11.jpg" class="cssbutton2" height="45" /></a>

    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 496, Column 235: required attribute "alt" not specified
    …ZEfI/AAAAAAAAAD8/bRQs2pxja4g/s128/12.jpg" class="cssbutton2" height="45" /></a>

    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 498, Column 235: required attribute "alt" not specified
    …jOSI/AAAAAAAAAA0/jY7PBt1nIbI/s128/13.jpg" class="cssbutton2" height="45" /></a>

    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 500, Column 235: required attribute "alt" not specified
    …WQhI/AAAAAAAAABA/W8zbDidwfj8/s128/14.jpg" class="cssbutton2" height="45" /></a>

    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 502, Column 235: required attribute "alt" not specified
    …RgrI/AAAAAAAAABM/kM4tlnpbDuA/s128/15.jpg" class="cssbutton2" height="45" /></a>

    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 504, Column 235: required attribute "alt" not specified
    …F5-I/AAAAAAAAABY/tM5t31zTpao/s128/16.jpg" class="cssbutton2" height="45" /></a>

    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 506, Column 235: required attribute "alt" not specified
    …nJDI/AAAAAAAAAB8/UhR-Kwd8gY4/s128/17.jpg" class="cssbutton2" height="45" /></a>

    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 508, Column 235: required attribute "alt" not specified
    …BDTI/AAAAAAAAABw/-6roDG1QspE/s128/18.jpg" class="cssbutton2" height="45" /></a>

    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 510, Column 234: required attribute "alt" not specified
    …uaXI/AAAAAAAAAB0/EkYFvmy28zU/s128/19.jpg" class="cssbutton2" height="45" /></a>

    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 512, Column 236: required attribute "alt" not specified
    …L2eI/AAAAAAAAACA/frCbc-yKcV8/s128/20.jpg" class="cssbutton2" height="45" /></a>

    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 514, Column 211: required attribute "alt" not specified
    …a/site/DPT75J2B9RWT3HFV/uploads/espn.PNG" class="cssbutton2" height="45" /></a>

    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 516, Column 237: required attribute "alt" not specified
    …AAAIc/KLrig13WmjQ/s1600/sky%2Bsports.jpg" class="cssbutton2" height="45" /></a>

    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 518, Column 210: required attribute "alt" not specified
    …F3G13SSGRR7DD/uploads/ten-cricket-hd.jpg" class="cssbutton2" height="45" /></a>

    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 520, Column 228: required attribute "alt" not specified
    …AAAD4/XwB1VXWrfw4/s1600/star+cricket.png" class="cssbutton2" height="45" /></a>

    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 522, Column 224: required attribute "alt" not specified
    …AAAAEE/sr9pheV2qrc/s1600/neo+cricket.png" class="cssbutton2" height="45" /></a>

    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 524, Column 213: required attribute "alt" not specified
    …a/site/1D5F3G13SSGRR7DD/uploads/euro.jpg" class="cssbutton2" height="45" /></a>

    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 526, Column 222: required attribute "alt" not specified
    …F3G13SSGRR7DD/uploads/sky_sport_hd_2.jpg" class="cssbutton2" height="45" /></a>

    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 528, Column 219: required attribute "alt" not specified
    …G13SSGRR7DD/uploads/sky_it_sport_hd3.jpg" class="cssbutton2" height="45" /></a>

    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 530, Column 230: required attribute "alt" not specified
    …/uploads/Sky-Sport-4-TV-Watch-Online.png" class="cssbutton2" height="45" /></a>

    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 532, Column 222: required attribute "alt" not specified
    …G13SSGRR7DD/uploads/espn_america_hd_.jpg" class="cssbutton2" height="45" /></a>

    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 534, Column 219: required attribute "alt" not specified
    …3G13SSGRR7DD/uploads/Eurosport_2_HD-.jpg" class="cssbutton2" height="45" /></a>

    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 536, Column 198: required attribute "alt" not specified
    …a/site/QG9V0W2VL3CRJ9Z5/uploads/alja.jpg" class="cssbutton2" height="45" /></a>

    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 538, Column 219: required attribute "alt" not specified
    …0W2VL3CRJ9Z5/uploads/Fox_Sports_logo.jpg" class="cssbutton2" height="45" /></a>

    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 540, Column 206: required attribute "alt" not specified
    …9V0W2VL3CRJ9Z5/uploads/LOGO-SPORT-TV.jpg" class="cssbutton2" height="45" /></a>

    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 542, Column 216: required attribute "alt" not specified
    …J9Z5/uploads/SuperSport-HD_2009_logo.jpg" class="cssbutton2" height="45" /></a>

    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 544, Column 208: required attribute "alt" not specified
    …0W2VL3CRJ9Z5/uploads/Zee_Sports-logo.jpg" class="cssbutton2" height="45" /></a>

    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 547, Column 95: there is no attribute "FRAMEBORDER"
    … DO NOT MODIFY --><IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING…

    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 547, Column 95: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    … DO NOT MODIFY --><IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING…
  • Error Line 547, Column 109: there is no attribute "MARGINWIDTH"
    … --><IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=300 …

    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 547, Column 109: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    … --><IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=300 …
  • Error Line 547, Column 124: there is no attribute "MARGINHEIGHT"
    …MEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=300 HEIGHT=250 SRC=…

    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 547, Column 124: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …MEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=300 HEIGHT=250 SRC=…
  • Error Line 547, Column 136: there is no attribute "SCROLLING"
    …ARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=300 HEIGHT=250 SRC="http://adse…

    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 547, Column 136: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=300 HEIGHT=250 SRC="http://adse…
  • Error Line 547, Column 145: there is no attribute "WIDTH"
    …H=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=300 HEIGHT=250 SRC="http://adserving.cpx…

    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 547, Column 145: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …H=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=300 HEIGHT=250 SRC="http://adserving.cpx…
  • Error Line 547, Column 156: there is no attribute "HEIGHT"
    …EIGHT=0 SCROLLING=NO WIDTH=300 HEIGHT=250 SRC="http://adserving.cpxinteractive…

    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 547, Column 156: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …EIGHT=0 SCROLLING=NO WIDTH=300 HEIGHT=250 SRC="http://adserving.cpxinteractive…
  • Error Line 547, Column 164: there is no attribute "SRC"
    …SCROLLING=NO WIDTH=300 HEIGHT=250 SRC="http://adserving.cpxinteractive.com/st?…

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

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

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

  • Warning Line 547, Column 219: cannot generate system identifier for general entity "ad_size"
    ….cpxinteractive.com/st?ad_type=iframe&ad_size=300x250&section=3672968&pub_url=…

    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 547, Column 219: general entity "ad_size" not defined and no default entity
    ….cpxinteractive.com/st?ad_type=iframe&ad_size=300x250&section=3672968&pub_url=…

    This is usually a cascading error caused by 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 547, Column 226: reference not terminated by REFC delimiter
    …eractive.com/st?ad_type=iframe&ad_size=300x250&section=3672968&pub_url=${PUB_U…

    If you meant to include an entity that starts with "&", then you should terminate it 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 547, Column 226: reference to external entity in attribute value
    …eractive.com/st?ad_type=iframe&ad_size=300x250&section=3672968&pub_url=${PUB_U…

    This is generally the sign of an ampersand that 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 547, Column 226: reference to entity "ad_size" for which no system identifier could be generated
    …eractive.com/st?ad_type=iframe&ad_size=300x250&section=3672968&pub_url=${PUB_U…

    This is usually a cascading error caused by 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 547, Column 218: entity was defined here
    …g.cpxinteractive.com/st?ad_type=iframe&ad_size=300x250&section=3672968&pub_url…
  • Warning Line 547, Column 235: cannot generate system identifier for general entity "section"
    …com/st?ad_type=iframe&ad_size=300x250&section=3672968&pub_url=${PUB_URL}"></IF…

    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 547, Column 235: general entity "section" not defined and no default entity
    …com/st?ad_type=iframe&ad_size=300x250&section=3672968&pub_url=${PUB_URL}"></IF…

    This is usually a cascading error caused by 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 547, Column 242: reference not terminated by REFC delimiter
    …ad_type=iframe&ad_size=300x250&section=3672968&pub_url=${PUB_URL}"></IFRAME><!…

    If you meant to include an entity that starts with "&", then you should terminate it 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 547, Column 242: reference to external entity in attribute value
    …ad_type=iframe&ad_size=300x250&section=3672968&pub_url=${PUB_URL}"></IFRAME><!…

    This is generally the sign of an ampersand that 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 547, Column 242: reference to entity "section" for which no system identifier could be generated
    …ad_type=iframe&ad_size=300x250&section=3672968&pub_url=${PUB_URL}"></IFRAME><!…

    This is usually a cascading error caused by 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 547, Column 234: entity was defined here
    ….com/st?ad_type=iframe&ad_size=300x250&section=3672968&pub_url=${PUB_URL}"></I…
  • Warning Line 547, Column 251: cannot generate system identifier for general entity "pub_url"
    …frame&ad_size=300x250&section=3672968&pub_url=${PUB_URL}"></IFRAME><!-- END TA…

    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 547, Column 251: general entity "pub_url" not defined and no default entity
    …frame&ad_size=300x250&section=3672968&pub_url=${PUB_URL}"></IFRAME><!-- END TA…

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

  • Warning Line 547, Column 258: reference not terminated by REFC delimiter
    …e&ad_size=300x250&section=3672968&pub_url=${PUB_URL}"></IFRAME><!-- END TAG -->

    If you meant to include an entity that starts with "&", then you should terminate it 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 547, Column 258: reference to external entity in attribute value
    …e&ad_size=300x250&section=3672968&pub_url=${PUB_URL}"></IFRAME><!-- END TAG -->

    This is generally the sign of an ampersand that 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 547, Column 258: reference to entity "pub_url" for which no system identifier could be generated
    …e&ad_size=300x250&section=3672968&pub_url=${PUB_URL}"></IFRAME><!-- END TAG -->

    This is usually a cascading error caused by 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 547, Column 250: entity was defined here
    …iframe&ad_size=300x250&section=3672968&pub_url=${PUB_URL}"></IFRAME><!-- END T…
  • Error Line 547, Column 270: element "IFRAME" undefined
    …e&ad_size=300x250&section=3672968&pub_url=${PUB_URL}"></IFRAME><!-- END TAG -->

    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 548, Column 95: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    … DO NOT MODIFY --><IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING…
  • Error Line 548, Column 109: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    … --><IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=300 …
  • Error Line 548, Column 124: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …MEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=300 HEIGHT=250 SRC=…
  • Error Line 548, Column 136: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=300 HEIGHT=250 SRC="http://adse…
  • Error Line 548, Column 145: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …H=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=300 HEIGHT=250 SRC="http://adserving.cpx…
  • Error Line 548, Column 156: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …EIGHT=0 SCROLLING=NO WIDTH=300 HEIGHT=250 SRC="http://adserving.cpxinteractive…
  • Warning Line 548, Column 226: reference not terminated by REFC delimiter
    …eractive.com/st?ad_type=iframe&ad_size=300x250&section=3672968&pub_url=${PUB_U…

    If you meant to include an entity that starts with "&", then you should terminate it 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 548, Column 226: reference to external entity in attribute value
    …eractive.com/st?ad_type=iframe&ad_size=300x250&section=3672968&pub_url=${PUB_U…

    This is generally the sign of an ampersand that 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 548, Column 226: reference to entity "ad_size" for which no system identifier could be generated
    …eractive.com/st?ad_type=iframe&ad_size=300x250&section=3672968&pub_url=${PUB_U…

    This is usually a cascading error caused by 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 547, Column 218: entity was defined here
    …g.cpxinteractive.com/st?ad_type=iframe&ad_size=300x250&section=3672968&pub_url…
  • Warning Line 548, Column 242: reference not terminated by REFC delimiter
    …ad_type=iframe&ad_size=300x250&section=3672968&pub_url=${PUB_URL}"></IFRAME><!…

    If you meant to include an entity that starts with "&", then you should terminate it 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 548, Column 242: reference to external entity in attribute value
    …ad_type=iframe&ad_size=300x250&section=3672968&pub_url=${PUB_URL}"></IFRAME><!…

    This is generally the sign of an ampersand that 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 548, Column 242: reference to entity "section" for which no system identifier could be generated
    …ad_type=iframe&ad_size=300x250&section=3672968&pub_url=${PUB_URL}"></IFRAME><!…

    This is usually a cascading error caused by 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 547, Column 234: entity was defined here
    ….com/st?ad_type=iframe&ad_size=300x250&section=3672968&pub_url=${PUB_URL}"></I…
  • Warning Line 548, Column 258: reference not terminated by REFC delimiter
    …e&ad_size=300x250&section=3672968&pub_url=${PUB_URL}"></IFRAME><!-- END TAG -->

    If you meant to include an entity that starts with "&", then you should terminate it 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 548, Column 258: reference to external entity in attribute value
    …e&ad_size=300x250&section=3672968&pub_url=${PUB_URL}"></IFRAME><!-- END TAG -->

    This is generally the sign of an ampersand that 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 548, Column 258: reference to entity "pub_url" for which no system identifier could be generated
    …e&ad_size=300x250&section=3672968&pub_url=${PUB_URL}"></IFRAME><!-- END TAG -->

    This is usually a cascading error caused by 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 547, Column 250: entity was defined here
    …iframe&ad_size=300x250&section=3672968&pub_url=${PUB_URL}"></IFRAME><!-- END T…
  • Error Line 548, Column 270: element "IFRAME" undefined
    …e&ad_size=300x250&section=3672968&pub_url=${PUB_URL}"></IFRAME><!-- END TAG -->

    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 549, Column 4: end tag for element "a" which is not open
    </a>

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

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 551, Column 7: end tag for element "span" which is not open
    </span>

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

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 552, Column 7: end tag for element "span" which is not open
    </span>

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

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 559, Column 147: element "iframe" undefined
    …border="0" height="510" scrolling="no">Your browser does not support iframes.<…

    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 561, Column 7: end tag for element "span" which is not open
    </span>

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

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 565, Column 10: ID "sidebar-wrapper" already defined
    <div id='sidebar-wrapper'>

    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 556, Column 10: ID "sidebar-wrapper" first defined here
    <div id='sidebar-wrapper'>
  • Error Line 566, Column 34: ID "sidebar" already defined
    <div class='sidebar section' id='sidebar'><div class='widget HTML' id='HTML6'>

    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 557, Column 34: ID "sidebar" first defined here
    <div class='sidebar section' id='sidebar'><div class='widget HTML' id='HTML6'>
  • Error Line 566, Column 72: ID "HTML6" already defined
    <div class='sidebar section' id='sidebar'><div class='widget HTML' id='HTML6'>

    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 557, Column 72: ID "HTML6" first defined here
    <div class='sidebar section' id='sidebar'><div class='widget HTML' id='HTML6'>
  • Error Line 568, Column 95: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    … DO NOT MODIFY --><IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING…
  • Error Line 568, Column 109: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    … --><IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=160 …
  • Error Line 568, Column 124: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …MEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=160 HEIGHT=600 SRC=…
  • Error Line 568, Column 136: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=160 HEIGHT=600 SRC="http://adse…
  • Error Line 568, Column 145: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …H=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=160 HEIGHT=600 SRC="http://adserving.cpx…
  • Error Line 568, Column 156: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …EIGHT=0 SCROLLING=NO WIDTH=160 HEIGHT=600 SRC="http://adserving.cpxinteractive…
  • Warning Line 568, Column 226: reference not terminated by REFC delimiter
    …eractive.com/st?ad_type=iframe&ad_size=160x600&section=3672968&pub_url=${PUB_U…

    If you meant to include an entity that starts with "&", then you should terminate it 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 568, Column 226: reference to external entity in attribute value
    …eractive.com/st?ad_type=iframe&ad_size=160x600&section=3672968&pub_url=${PUB_U…

    This is generally the sign of an ampersand that 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 568, Column 226: reference to entity "ad_size" for which no system identifier could be generated
    …eractive.com/st?ad_type=iframe&ad_size=160x600&section=3672968&pub_url=${PUB_U…

    This is usually a cascading error caused by 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 547, Column 218: entity was defined here
    …g.cpxinteractive.com/st?ad_type=iframe&ad_size=300x250&section=3672968&pub_url…
  • Warning Line 568, Column 242: reference not terminated by REFC delimiter
    …ad_type=iframe&ad_size=160x600&section=3672968&pub_url=${PUB_URL}"></IFRAME><!…

    If you meant to include an entity that starts with "&", then you should terminate it 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 568, Column 242: reference to external entity in attribute value
    …ad_type=iframe&ad_size=160x600&section=3672968&pub_url=${PUB_URL}"></IFRAME><!…

    This is generally the sign of an ampersand that 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 568, Column 242: reference to entity "section" for which no system identifier could be generated
    …ad_type=iframe&ad_size=160x600&section=3672968&pub_url=${PUB_URL}"></IFRAME><!…

    This is usually a cascading error caused by 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 547, Column 234: entity was defined here
    ….com/st?ad_type=iframe&ad_size=300x250&section=3672968&pub_url=${PUB_URL}"></I…
  • Warning Line 568, Column 258: reference not terminated by REFC delimiter
    …e&ad_size=160x600&section=3672968&pub_url=${PUB_URL}"></IFRAME><!-- END TAG -->

    If you meant to include an entity that starts with "&", then you should terminate it 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 568, Column 258: reference to external entity in attribute value
    …e&ad_size=160x600&section=3672968&pub_url=${PUB_URL}"></IFRAME><!-- END TAG -->

    This is generally the sign of an ampersand that 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 568, Column 258: reference to entity "pub_url" for which no system identifier could be generated
    …e&ad_size=160x600&section=3672968&pub_url=${PUB_URL}"></IFRAME><!-- END TAG -->

    This is usually a cascading error caused by 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 547, Column 250: entity was defined here
    …iframe&ad_size=300x250&section=3672968&pub_url=${PUB_URL}"></IFRAME><!-- END T…
  • Error Line 568, Column 270: element "IFRAME" undefined
    …e&ad_size=160x600&section=3672968&pub_url=${PUB_URL}"></IFRAME><!-- END TAG -->

    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 569, Column 95: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    … DO NOT MODIFY --><IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING…
  • Error Line 569, Column 109: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    … --><IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=160 …
  • Error Line 569, Column 124: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …MEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=160 HEIGHT=600 SRC=…
  • Error Line 569, Column 136: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=160 HEIGHT=600 SRC="http://adse…
  • Error Line 569, Column 145: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …H=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=160 HEIGHT=600 SRC="http://adserving.cpx…
  • Error Line 569, Column 156: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …EIGHT=0 SCROLLING=NO WIDTH=160 HEIGHT=600 SRC="http://adserving.cpxinteractive…
  • Warning Line 569, Column 226: reference not terminated by REFC delimiter
    …eractive.com/st?ad_type=iframe&ad_size=160x600&section=3672968&pub_url=${PUB_U…

    If you meant to include an entity that starts with "&", then you should terminate it 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 569, Column 226: reference to external entity in attribute value
    …eractive.com/st?ad_type=iframe&ad_size=160x600&section=3672968&pub_url=${PUB_U…

    This is generally the sign of an ampersand that 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 569, Column 226: reference to entity "ad_size" for which no system identifier could be generated
    …eractive.com/st?ad_type=iframe&ad_size=160x600&section=3672968&pub_url=${PUB_U…

    This is usually a cascading error caused by 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 547, Column 218: entity was defined here
    …g.cpxinteractive.com/st?ad_type=iframe&ad_size=300x250&section=3672968&pub_url…
  • Warning Line 569, Column 242: reference not terminated by REFC delimiter
    …ad_type=iframe&ad_size=160x600&section=3672968&pub_url=${PUB_URL}"></IFRAME><!…

    If you meant to include an entity that starts with "&", then you should terminate it 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 569, Column 242: reference to external entity in attribute value
    …ad_type=iframe&ad_size=160x600&section=3672968&pub_url=${PUB_URL}"></IFRAME><!…

    This is generally the sign of an ampersand that 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 569, Column 242: reference to entity "section" for which no system identifier could be generated
    …ad_type=iframe&ad_size=160x600&section=3672968&pub_url=${PUB_URL}"></IFRAME><!…

    This is usually a cascading error caused by 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 547, Column 234: entity was defined here
    ….com/st?ad_type=iframe&ad_size=300x250&section=3672968&pub_url=${PUB_URL}"></I…
  • Warning Line 569, Column 258: reference not terminated by REFC delimiter
    …e&ad_size=160x600&section=3672968&pub_url=${PUB_URL}"></IFRAME><!-- END TAG -->

    If you meant to include an entity that starts with "&", then you should terminate it 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 569, Column 258: reference to external entity in attribute value
    …e&ad_size=160x600&section=3672968&pub_url=${PUB_URL}"></IFRAME><!-- END TAG -->

    This is generally the sign of an ampersand that 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 569, Column 258: reference to entity "pub_url" for which no system identifier could be generated
    …e&ad_size=160x600&section=3672968&pub_url=${PUB_URL}"></IFRAME><!-- END TAG -->

    This is usually a cascading error caused by 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 547, Column 250: entity was defined here
    …iframe&ad_size=300x250&section=3672968&pub_url=${PUB_URL}"></IFRAME><!-- END T…
  • Error Line 569, Column 270: element "IFRAME" undefined
    …e&ad_size=160x600&section=3672968&pub_url=${PUB_URL}"></IFRAME><!-- END TAG -->

    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).
  • Warning Line 577, Column 98: reference not terminated by REFC delimiter
    …?blogID=4130086795270491146&widgetType=HTML&widgetId=HTML1&action=editWidget' …

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

  • Warning Line 577, Column 98: reference to external entity in attribute value
    …?blogID=4130086795270491146&widgetType=HTML&widgetId=HTML1&action=editWidget' …

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

  • Error Line 577, Column 98: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=4130086795270491146&widgetType=HTML&widgetId=HTML1&action=editWidget' …

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

  • Info Line 448, Column 87: entity was defined here
    …m/rearrange?blogID=4130086795270491146&widgetType=HTML&widgetId=HTML3&action=e…
  • Warning Line 577, Column 112: reference not terminated by REFC delimiter
    …6795270491146&widgetType=HTML&widgetId=HTML1&action=editWidget' onclick='retur…

    If you meant to include an entity that starts with "&", then you should terminate it 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 577, Column 112: reference to external entity in attribute value
    …6795270491146&widgetType=HTML&widgetId=HTML1&action=editWidget' onclick='retur…

    This is generally the sign of an ampersand that 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 577, Column 112: reference to entity "widgetId" for which no system identifier could be generated
    …6795270491146&widgetType=HTML&widgetId=HTML1&action=editWidget' onclick='retur…

    This is usually a cascading error caused by 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 448, Column 103: entity was defined here
    …ID=4130086795270491146&widgetType=HTML&widgetId=HTML3&action=editWidget' oncli…
  • Warning Line 577, Column 125: reference not terminated by REFC delimiter
    …&widgetType=HTML&widgetId=HTML1&action=editWidget' onclick='return _WidgetMana…

    If you meant to include an entity that starts with "&", then you should terminate it 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 577, Column 125: reference to external entity in attribute value
    …&widgetType=HTML&widgetId=HTML1&action=editWidget' onclick='return _WidgetMana…

    This is generally the sign of an ampersand that 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 577, Column 125: reference to entity "action" for which no system identifier could be generated
    …&widgetType=HTML&widgetId=HTML1&action=editWidget' onclick='return _WidgetMana…

    This is usually a cascading error caused by 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 448, Column 118: entity was defined here
    …0491146&widgetType=HTML&widgetId=HTML3&action=editWidget' onclick='return _Wid…
  • Error Line 596, Column 449: element "iframe" undefined
    …" id="myfr" scrolling="no" width="625">Your Browser Do not Support Iframe</ifr…

    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 606, Column 9: end tag for element "script" which is not open
    </script><script type="text/javascript" src="http://www.blogger.com/static/v1/w…

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

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 607, Column 94: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    … DO NOT MODIFY --><IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING…
  • Error Line 607, Column 108: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    … --><IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=728 …
  • Error Line 607, Column 123: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …MEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=728 HEIGHT=90 SRC="…
  • Error Line 607, Column 135: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=728 HEIGHT=90 SRC="http://adser…
  • Error Line 607, Column 144: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …H=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=728 HEIGHT=90 SRC="http://adserving.cpxi…
  • Error Line 607, Column 155: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …EIGHT=0 SCROLLING=NO WIDTH=728 HEIGHT=90 SRC="http://adserving.cpxinteractive.…
  • Warning Line 607, Column 224: reference not terminated by REFC delimiter
    …eractive.com/st?ad_type=iframe&ad_size=728x90&section=3672968&pub_url=${PUB_UR…

    If you meant to include an entity that starts with "&", then you should terminate it 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 607, Column 224: reference to external entity in attribute value
    …eractive.com/st?ad_type=iframe&ad_size=728x90&section=3672968&pub_url=${PUB_UR…

    This is generally the sign of an ampersand that 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 607, Column 224: reference to entity "ad_size" for which no system identifier could be generated
    …eractive.com/st?ad_type=iframe&ad_size=728x90&section=3672968&pub_url=${PUB_UR…

    This is usually a cascading error caused by 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 547, Column 218: entity was defined here
    …g.cpxinteractive.com/st?ad_type=iframe&ad_size=300x250&section=3672968&pub_url…
  • Warning Line 607, Column 239: reference not terminated by REFC delimiter
    …?ad_type=iframe&ad_size=728x90&section=3672968&pub_url=${PUB_URL}"></IFRAME><!…

    If you meant to include an entity that starts with "&", then you should terminate it 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 607, Column 239: reference to external entity in attribute value
    …?ad_type=iframe&ad_size=728x90&section=3672968&pub_url=${PUB_URL}"></IFRAME><!…

    This is generally the sign of an ampersand that 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 607, Column 239: reference to entity "section" for which no system identifier could be generated
    …?ad_type=iframe&ad_size=728x90&section=3672968&pub_url=${PUB_URL}"></IFRAME><!…

    This is usually a cascading error caused by 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 547, Column 234: entity was defined here
    ….com/st?ad_type=iframe&ad_size=300x250&section=3672968&pub_url=${PUB_URL}"></I…
  • Warning Line 607, Column 255: reference not terminated by REFC delimiter
    …me&ad_size=728x90&section=3672968&pub_url=${PUB_URL}"></IFRAME><!-- END TAG -->

    If you meant to include an entity that starts with "&", then you should terminate it 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 607, Column 255: reference to external entity in attribute value
    …me&ad_size=728x90&section=3672968&pub_url=${PUB_URL}"></IFRAME><!-- END TAG -->

    This is generally the sign of an ampersand that 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 607, Column 255: reference to entity "pub_url" for which no system identifier could be generated
    …me&ad_size=728x90&section=3672968&pub_url=${PUB_URL}"></IFRAME><!-- END TAG -->

    This is usually a cascading error caused by 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 547, Column 250: entity was defined here
    …iframe&ad_size=300x250&section=3672968&pub_url=${PUB_URL}"></IFRAME><!-- END T…
  • Error Line 607, Column 267: element "IFRAME" undefined
    …me&ad_size=728x90&section=3672968&pub_url=${PUB_URL}"></IFRAME><!-- END TAG -->

    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 609, Column 21: required attribute "type" not specified
    <script id="_waui7c">var _wau = _wau || []; _wau.push(["small", "7gl3cszvycm6",…

    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 614, Column 12: there is no attribute "align"
    <div align="center" class="common-footer-ad-holder"><iframe src="" frameborder=…

    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 614, Column 80: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …common-footer-ad-holder"><iframe src="" frameborder=0 scrolling="no" width="0" 
  • Error Line 615, Column 11: element "iframe" undefined
    height="0"></iframe> 

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 616, Column 7: end tag for "div" omitted, but OMITTAG NO was specified
    </html>

    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 614, Column 1: start tag was here
    <div align="center" class="common-footer-ad-holder"><iframe src="" frameborder=…
  • Error Line 616, Column 7: end tag for "div" omitted, but OMITTAG NO was specified
    </html>

    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 593, Column 41: start tag was here
    <div class='footer section' id='footer'><div class='widget HTML' id='HTML11'>
  • Error Line 616, Column 7: end tag for "div" omitted, but OMITTAG NO was specified
    </html>

    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 593, Column 1: start tag was here
    <div class='footer section' id='footer'><div class='widget HTML' id='HTML11'>
  • Error Line 616, Column 7: end tag for "div" omitted, but OMITTAG NO was specified
    </html>

    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 592, Column 1: start tag was here
    <div id='footer-wrapper'>
  • Error Line 616, Column 7: end tag for "div" omitted, but OMITTAG NO was specified
    </html>

    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 395, Column 1: start tag was here
    <div id='content-wrapper'>
  • Error Line 616, Column 7: end tag for "div" omitted, but OMITTAG NO was specified
    </html>

    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 379, Column 25: start tag was here
    <div id='outer-wrapper'><div id='wrap2'>
  • Error Line 616, Column 7: end tag for "div" omitted, but OMITTAG NO was specified
    </html>

    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 379, Column 1: start tag was here
    <div id='outer-wrapper'><div id='wrap2'>
  • Error Line 616, Column 7: end tag for "body" omitted, but OMITTAG NO was specified
    </html>

    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 364, Column 1: start tag was here
    <body>

Visitor Analysis

Daily Visitor
  • 793 visits
Daily Visitor