BoCoPreps.com - High school sports for Boulder County ...

bocopreps.com
  • Domain Name
    bocopreps.com
  • Favicon
  • Google Page Rank
    6
  • Alexa Rank
    #1480982
  • Page Size
    117.3 KB
  • Ip Address
    63.147.65.60
  • Heading
    H1: 4, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    12 GIF, 10 JPG, 0 PNG

Website Meta Analysis

  • Title
    Boulder County High School Sports News, Scores and Information - BoCoPreps.com - BoCoPreps.com Boulder County High School Sports
  • Meta Keyword
    boulder county high school sports prep sports boulder valley schools st vrain schools private schools adams 12 schools winter sports fall sports spring sports
  • Meta Description
    BoCoPreps.com - High school sports for Boulder County

Technical Analysis

  • Webserver
    Apache/2.0.52 (Red Hat)
  • Ip Address
    63.147.65.60
  • Domain Age
    1 Years, 8 Months, 26 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • server: Apache/2.0.52 (Red Hat)
  • vary: Accept-encoding
  • content-encoding: gzip
  • expires: Fri, 01 Mar 2013 07:22:36 GMT
  • cache-control: max-age=0, no-cache, no-store
  • pragma: no-cache
  • date: Fri, 01 Mar 2013 07:22:36 GMT
  • content-length: 26102
  • connection: keep-alive
  • content-type: text/html;charset=UTF-8
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for bocopreps.com

IP 63.147.65.60 Analysis

  • Country Code
    US
  • Country Code3
    USA
  • Country Name
    United States
  • City
    NA
  • Continent Code
    38° North
  • Latitude
    97.
  • Longitude
  • #
    # Query terms are ambiguous. The query is assumed to be:
    # "n 63.147.65.60"
    #
    # Use "?" to get help.
    #

    #
    # The following results may also be obtained via:
    # http://whois.arin.net/rest/nets;q=63.147.65.60?showDetails=true&showARIN=false&ext=netref2
    #

    NetRange: 63.144.0.0 - 63.151.255.255
    CIDR: 63.144.0.0/13
    OriginAS:
    NetName: QWEST-INET-8
    NetHandle: NET-63-144-0-0-1
    Parent: NET-63-0-0-0-0
    NetType: Direct Allocation
    Comment: ADDRESSES WITHIN THIS BLOCK ARE NON-PORTABLE
    Comment: NOTE: For abuse issues, please email abuse@qwest.net.
    RegDate: 2000-03-13
    Updated: 2012-02-24
    Ref: http://whois.arin.net/rest/net/NET-63-144-0-0-1

    OrgName: Qwest Communications Company, LLC
    OrgId: QCC-18
    Address: 1801 California Street
    City: Denver
    StateProv: CO
    PostalCode: 80202
    Country: US
    RegDate: 2005-05-09
    Updated: 2011-09-08
    Ref: http://whois.arin.net/rest/org/QCC-18

    OrgAbuseHandle: QIA2-ARIN
    OrgAbuseName: Qwest Abuse
    OrgAbusePhone: +1-877-886-6515
    OrgAbuseEmail: abuse@qwest.net
    OrgAbuseRef: http://whois.arin.net/rest/poc/QIA2-ARIN

    OrgTechHandle: QIA-ARIN
    OrgTechName: Qwest IP Admin
    OrgTechPhone: +1-877-886-6515
    OrgTechEmail: ipadmin@qwest.com
    OrgTechRef: http://whois.arin.net/rest/poc/QIA-ARIN

    OrgNOCHandle: QIN-ARIN
    OrgNOCName: Qwest IP NOC
    OrgNOCPhone: +1-877-886-6515
    OrgNOCEmail: support@qwestip.net
    OrgNOCRef: http://whois.arin.net/rest/poc/QIN-ARIN

    #
    # ARIN WHOIS data and services are subject to the Terms of Use
    # available at: https://www.arin.net/whois_tou.html
    #

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 115 Errors
  • 49 Warnings
Ratio Text/Html
  • 0.44666344777063705
Message Error
  • Warning Line 1, Column 355: NET-enabling start-tag requires SHORTTAG YES
    …nter sports fall sports spring sports"/><meta property="og:url" content="http:…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 1, Column 356: character data is not allowed here
    …ter sports fall sports spring sports"/><meta property="og:url" content="http:/…

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 1, Column 372: there is no attribute "PROPERTY"
    …sports spring sports"/><meta property="og:url" content="http://www.bocopreps.c…

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

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

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

  • Warning Line 1, Column 427: NET-enabling start-tag requires SHORTTAG YES
    …"http://www.bocopreps.com/index.html" /><title>Boulder County High School Spor…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 1, Column 645: required attribute "TYPE" not specified
    …ipt src="http://ajax.googleapis.com/ajax/libs/jquery/1/jquery.min.js"></script>

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

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

  • Warning Line 2, Column 93: NET-enabling start-tag requires SHORTTAG YES
    …gle-site-verification" content="pxf7ISpN_qDZcNh3ZOrWbWFqOdq24RBvW-ymjiVqWO0" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 3, Column 18: NET-enabling start-tag requires SHORTTAG YES
    <script type=text/javascript src="http://extras.mnginteractive.com/live/js/meta…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 3, Column 100: end tag for element "SCRIPT" which is not open
    …ascript src="http://extras.mnginteractive.com/live/js/metaRefresh.js"></script>

    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 22, Column 382: document type does not allow element "LINK" here
    …ve.com/live/css/MNGiDefaultStyles.css'><link type="text/css" rel="stylesheet" …

    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 22, Column 503: document type does not allow element "LINK" here
    …/css/1024_-_2_Column_Multi-Region.css'><!-- LEGOLAS SETUP --><script type="tex…

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

  • Warning Line 22, Column 600: cannot generate system identifier for general entity "ti"
    …http://rt.legolas-media.com/lgrt?ci=2&ti=11263&pbi=10888"></script><script typ…

    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 22, Column 600: general entity "ti" not defined and no default entity
    …http://rt.legolas-media.com/lgrt?ci=2&ti=11263&pbi=10888"></script><script typ…

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

  • Error Line 22, Column 602: reference to entity "ti" for which no system identifier could be generated
    …tp://rt.legolas-media.com/lgrt?ci=2&ti=11263&pbi=10888"></script><script type=…

    This is usually a cascading error caused by 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 22, Column 599: entity was defined here
    …"http://rt.legolas-media.com/lgrt?ci=2&ti=11263&pbi=10888"></script><script ty…
  • Warning Line 22, Column 609: cannot generate system identifier for general entity "pbi"
    ….legolas-media.com/lgrt?ci=2&ti=11263&pbi=10888"></script><script type="text/j…

    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 22, Column 609: general entity "pbi" not defined and no default entity
    ….legolas-media.com/lgrt?ci=2&ti=11263&pbi=10888"></script><script type="text/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.

  • Error Line 22, Column 612: reference to entity "pbi" for which no system identifier could be generated
    …golas-media.com/lgrt?ci=2&ti=11263&pbi=10888"></script><script type="text/java…

    This is usually a cascading error caused by 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 22, Column 608: entity was defined here
    …t.legolas-media.com/lgrt?ci=2&ti=11263&pbi=10888"></script><script type="text/…
  • Error Line 182, Column 323: end tag for element "HEAD" which is not open
    …m/live/css/site54/global.css --></head><body class="bodyStyle"><span id='globa…

    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 182, Column 347: document type does not allow element "BODY" here
    ….css --></head><body class="bodyStyle"><span id='global'><link type='text/css'…

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Error Line 182, Column 471: document type does not allow element "LINK" here
    …active.com/live/css/site54/global.css'><div class="contentStyle"><script type=…

    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 182, Column 497: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …/global.css'><div class="contentStyle"><script type="text/javascript" language…

    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 221, Column 69: required attribute "TYPE" not specified
                http://www.omniture.com --><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 224, Column 425: required attribute "TYPE" not specified
    …s/omniture/OmniUserObjAndHelper.js'></script><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 366, Column 165: required attribute "TYPE" not specified
    …xtras.mnginteractive.com/live/js/omniture/functions.js'></script><script><!--//

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

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

  • Error Line 369, Column 105: required attribute "TYPE" not specified
    …f(s_code)document.write(s_code)//--></script><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>.

  • Warning Line 373, Column 52: NET-enabling start-tag requires SHORTTAG YES
    …eight="1" width="1" border="0" alt="" /></noscript><!--/DO NOT REMOVE/--><!-- …

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 382, Column 88: required attribute "TYPE" not specified
    …//extras.mnginteractive.com/live/js/weather/custom_weather_access.js"></script>

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

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

  • Error Line 400, Column 55: start tag for "LI" omitted, but its declaration does not permit this
    	<ul class="weather"><span id="weather_box_horizontal"></span>
  • Error Line 401, Column 16: required attribute "TYPE" not specified
            <script>loadWeatherBoxHorizontal('weather_box_horizontal','80301','www.…

    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 407, Column 152: required attribute "ALT" not specified
    …ginteractive.com/live/media/site569/2007/0208/20070208_052619_tspacer.gif"></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>.

  • Warning Line 411, Column 53: NET-enabling start-tag requires SHORTTAG YES
    			<input name="query" class="searchbox" type="text"/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 412, Column 181: value of attribute "ALIGN" cannot be "ABSMIDDLE"; must be one of "TOP", "MIDDLE", "BOTTOM", "LEFT", "RIGHT"
    …edia/site19/2009/0506/20090506__btnSearch.gif" type="image" align="absmiddle"/>

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Warning Line 412, Column 182: NET-enabling start-tag requires SHORTTAG YES
    …edia/site19/2009/0506/20090506__btnSearch.gif" type="image" align="absmiddle"/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 414, Column 104: NET-enabling start-tag requires SHORTTAG YES
    … class="radio" value="entiresitesppublished" checked="checked" />This Site</li>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 415, Column 90: NET-enabling start-tag requires SHORTTAG YES
    … class="radio" value="yahoowebsearch" />Web Search powered by <span class="yah…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 433, Column 148: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …0\')')" onMouseOut="fixMouseOut(this, event, 'mouseOut(\'0\')')" class="first">

    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 554, Column 134: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …t, 'mouseIn(\'9\')')" onMouseOut="fixMouseOut(this, event, 'mouseOut(\'9\')')">

    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 565, Column 6: invalid comment declaration: found name start character outside comment but inside comment declaration
    <!-- end Target ad tag -->
  • Info Line 562, Column 1: comment declaration started here
    <!-- begin Target ad tag
  • Warning Line 575, Column 81: cannot generate system identifier for general entity "where"
    …trange.kaango.com/ads/search/?search=&where=Longmont%2C+Colorado&allmarket=0&d…

    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 575, Column 81: general entity "where" not defined and no default entity
    …trange.kaango.com/ads/search/?search=&where=Longmont%2C+Colorado&allmarket=0&d…

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

  • Error Line 575, Column 86: reference to entity "where" for which no system identifier could be generated
    …e.kaango.com/ads/search/?search=&where=Longmont%2C+Colorado&allmarket=0&distan…

    This is usually a cascading error caused by 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 575, Column 80: entity was defined here
    …ntrange.kaango.com/ads/search/?search=&where=Longmont%2C+Colorado&allmarket=0&…
  • Warning Line 575, Column 108: cannot generate system identifier for general entity "allmarket"
    …h/?search=&where=Longmont%2C+Colorado&allmarket=0&distance=15&show=20&sort=dat…

    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 575, Column 108: general entity "allmarket" not defined and no default entity
    …h/?search=&where=Longmont%2C+Colorado&allmarket=0&distance=15&show=20&sort=dat…

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

  • Error Line 575, Column 117: reference to entity "allmarket" for which no system identifier could be generated
    …=&where=Longmont%2C+Colorado&allmarket=0&distance=15&show=20&sort=date&cat=902…

    This is usually a cascading error caused by 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 575, Column 107: entity was defined here
    …ch/?search=&where=Longmont%2C+Colorado&allmarket=0&distance=15&show=20&sort=da…
  • Warning Line 575, Column 120: cannot generate system identifier for general entity "distance"
    …here=Longmont%2C+Colorado&allmarket=0&distance=15&show=20&sort=date&cat=902"><…

    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 575, Column 120: general entity "distance" not defined and no default entity
    …here=Longmont%2C+Colorado&allmarket=0&distance=15&show=20&sort=date&cat=902"><…

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

  • Error Line 575, Column 128: reference to entity "distance" for which no system identifier could be generated
    …gmont%2C+Colorado&allmarket=0&distance=15&show=20&sort=date&cat=902"><span>Cla…

    This is usually a cascading error caused by 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 575, Column 119: entity was defined here
    …where=Longmont%2C+Colorado&allmarket=0&distance=15&show=20&sort=date&cat=902">…
  • Warning Line 575, Column 132: cannot generate system identifier for general entity "show"
    …t%2C+Colorado&allmarket=0&distance=15&show=20&sort=date&cat=902"><span>Classif…

    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 575, Column 132: general entity "show" not defined and no default entity
    …t%2C+Colorado&allmarket=0&distance=15&show=20&sort=date&cat=902"><span>Classif…

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

  • Error Line 575, Column 136: reference to entity "show" for which no system identifier could be generated
    …+Colorado&allmarket=0&distance=15&show=20&sort=date&cat=902"><span>Classifieds…

    This is usually a cascading error caused by 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 575, Column 131: entity was defined here
    …nt%2C+Colorado&allmarket=0&distance=15&show=20&sort=date&cat=902"><span>Classi…
  • Warning Line 575, Column 140: cannot generate system identifier for general entity "sort"
    …orado&allmarket=0&distance=15&show=20&sort=date&cat=902"><span>Classifieds</sp…

    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 575, Column 140: general entity "sort" not defined and no default entity
    …orado&allmarket=0&distance=15&show=20&sort=date&cat=902"><span>Classifieds</sp…

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

  • Error Line 575, Column 144: reference to entity "sort" for which no system identifier could be generated
    …o&allmarket=0&distance=15&show=20&sort=date&cat=902"><span>Classifieds</span><…

    This is usually a cascading error caused by 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 575, Column 139: entity was defined here
    …lorado&allmarket=0&distance=15&show=20&sort=date&cat=902"><span>Classifieds</s…
  • Warning Line 575, Column 150: cannot generate system identifier for general entity "cat"
    …arket=0&distance=15&show=20&sort=date&cat=902"><span>Classifieds</span></a></d…

    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 575, Column 150: general entity "cat" not defined and no default entity
    …arket=0&distance=15&show=20&sort=date&cat=902"><span>Classifieds</span></a></d…

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

  • Error Line 575, Column 153: reference to entity "cat" for which no system identifier could be generated
    …ket=0&distance=15&show=20&sort=date&cat=902"><span>Classifieds</span></a></div>

    This is usually a cascading error caused by 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 575, Column 149: entity was defined here
    …market=0&distance=15&show=20&sort=date&cat=902"><span>Classifieds</span></a></…
  • Error Line 590, Column 151: document type does not allow element "DIV" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …\')')" onMouseOut="fixMouseOut(this, event, 'mouseOut(\'11\')')" class="right">

    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 602, Column 492: required attribute "TYPE" not specified
    …ign="top"><!-- DEBUG: numStories = 1 --><div style="clear:both;"></div><script>

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

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

  • Error Line 614, Column 556: there is no attribute "VALIGN"
    …pg" alt="" title="" border="0" valign="top" hspace="0" vspace="0" class="listi…

    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 619, Column 308: required attribute "ALT" not specified
    …conTypes/slideshow.gif' border="false"><br></a><br><span class="complexListing…

    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 622, Column 53: required attribute "TYPE" not specified
    <script src="http://widgets.twimg.com/j/2/widget.js"></script>

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

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

  • Error Line 623, Column 8: required attribute "TYPE" not specified
    <script>

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

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

  • Warning Line 679, Column 41: NET-enabling start-tag requires SHORTTAG YES
      <param name="bgcolor" value="#FFFFFF" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 680, Column 35: NET-enabling start-tag requires SHORTTAG YES
      <param name="width" value="300" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 681, Column 36: NET-enabling start-tag requires SHORTTAG YES
      <param name="height" value="540" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 682, Column 48: NET-enabling start-tag requires SHORTTAG YES
      <param name="playerID" value="1783827117001" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 683, Column 86: NET-enabling start-tag requires SHORTTAG YES
    … name="playerKey" value="AQ~~,AAAAAFSLizo~,ugsvBtRv1svgBfi87oB90oAl9iXP7jFG" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 684, Column 36: NET-enabling start-tag requires SHORTTAG YES
      <param name="isVid" value="true" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 685, Column 35: NET-enabling start-tag requires SHORTTAG YES
      <param name="isUI" value="true" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 686, Column 47: NET-enabling start-tag requires SHORTTAG YES
      <param name="dynamicStreaming" value="true" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 703, Column 131: required attribute "ALT" not specified
    …teractive.com/live/media/site29/2009/0601/20090601__MediaCenterTitle.gif"></td>

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

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

  • Warning Line 715, Column 201: cannot generate system identifier for general entity "AlbumKey"
    …com/photos/random.mg?AlbumID=27884697&AlbumKey=vXRwMp&Size=Tiny&rand=5865" /><…

    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 715, Column 201: general entity "AlbumKey" not defined and no default entity
    …com/photos/random.mg?AlbumID=27884697&AlbumKey=vXRwMp&Size=Tiny&rand=5865" /><…

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

  • Error Line 715, Column 209: reference to entity "AlbumKey" for which no system identifier could be generated
    …m/photos/random.mg?AlbumID=27884697&AlbumKey=vXRwMp&Size=Tiny&rand=5865" /></a>

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

  • Info Line 715, Column 200: entity was defined here
    ….com/photos/random.mg?AlbumID=27884697&AlbumKey=vXRwMp&Size=Tiny&rand=5865" />…
  • Warning Line 715, Column 217: cannot generate system identifier for general entity "Size"
    …m/photos/random.mg?AlbumID=27884697&AlbumKey=vXRwMp&Size=Tiny&rand=5865" /></a>

    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 715, Column 217: general entity "Size" not defined and no default entity
    …m/photos/random.mg?AlbumID=27884697&AlbumKey=vXRwMp&Size=Tiny&rand=5865" /></a>

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

  • Error Line 715, Column 221: reference to entity "Size" for which no system identifier could be generated
    …m/photos/random.mg?AlbumID=27884697&AlbumKey=vXRwMp&Size=Tiny&rand=5865" /></a>

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

  • Info Line 715, Column 216: entity was defined here
    …m/photos/random.mg?AlbumID=27884697&AlbumKey=vXRwMp&Size=Tiny&rand=5865" /></a>
  • Warning Line 715, Column 227: cannot generate system identifier for general entity "rand"
    …m/photos/random.mg?AlbumID=27884697&AlbumKey=vXRwMp&Size=Tiny&rand=5865" /></a>

    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 715, Column 227: general entity "rand" not defined and no default entity
    …m/photos/random.mg?AlbumID=27884697&AlbumKey=vXRwMp&Size=Tiny&rand=5865" /></a>

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

  • Error Line 715, Column 231: reference to entity "rand" for which no system identifier could be generated
    …m/photos/random.mg?AlbumID=27884697&AlbumKey=vXRwMp&Size=Tiny&rand=5865" /></a>

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

  • Info Line 715, Column 226: entity was defined here
    …m/photos/random.mg?AlbumID=27884697&AlbumKey=vXRwMp&Size=Tiny&rand=5865" /></a>
  • Warning Line 715, Column 238: NET-enabling start-tag requires SHORTTAG YES
    …m/photos/random.mg?AlbumID=27884697&AlbumKey=vXRwMp&Size=Tiny&rand=5865" /></a>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 715, Column 238: required attribute "ALT" not specified
    …m/photos/random.mg?AlbumID=27884697&AlbumKey=vXRwMp&Size=Tiny&rand=5865" /></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 720, Column 213: reference to entity "AlbumKey" for which no system identifier could be generated
    …m/photos/random.mg?AlbumID=27923652&AlbumKey=5wpZ3L&Size=Tiny&rand=2114" /></a>

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

  • Info Line 715, Column 200: entity was defined here
    ….com/photos/random.mg?AlbumID=27884697&AlbumKey=vXRwMp&Size=Tiny&rand=5865" />…
  • Error Line 720, Column 225: reference to entity "Size" for which no system identifier could be generated
    …m/photos/random.mg?AlbumID=27923652&AlbumKey=5wpZ3L&Size=Tiny&rand=2114" /></a>

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

  • Info Line 715, Column 216: entity was defined here
    …m/photos/random.mg?AlbumID=27884697&AlbumKey=vXRwMp&Size=Tiny&rand=5865" /></a>
  • Error Line 720, Column 235: reference to entity "rand" for which no system identifier could be generated
    …m/photos/random.mg?AlbumID=27923652&AlbumKey=5wpZ3L&Size=Tiny&rand=2114" /></a>

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

  • Info Line 715, Column 226: entity was defined here
    …m/photos/random.mg?AlbumID=27884697&AlbumKey=vXRwMp&Size=Tiny&rand=5865" /></a>
  • Warning Line 720, Column 242: NET-enabling start-tag requires SHORTTAG YES
    …m/photos/random.mg?AlbumID=27923652&AlbumKey=5wpZ3L&Size=Tiny&rand=2114" /></a>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 720, Column 242: required attribute "ALT" not specified
    …m/photos/random.mg?AlbumID=27923652&AlbumKey=5wpZ3L&Size=Tiny&rand=2114" /></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 725, Column 210: reference to entity "AlbumKey" for which no system identifier could be generated
    …m/photos/random.mg?AlbumID=27869563&AlbumKey=2xswg4&Size=Tiny&rand=3923" /></a>

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

  • Info Line 715, Column 200: entity was defined here
    ….com/photos/random.mg?AlbumID=27884697&AlbumKey=vXRwMp&Size=Tiny&rand=5865" />…
  • Error Line 725, Column 222: reference to entity "Size" for which no system identifier could be generated
    …m/photos/random.mg?AlbumID=27869563&AlbumKey=2xswg4&Size=Tiny&rand=3923" /></a>

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

  • Info Line 715, Column 216: entity was defined here
    …m/photos/random.mg?AlbumID=27884697&AlbumKey=vXRwMp&Size=Tiny&rand=5865" /></a>
  • Error Line 725, Column 232: reference to entity "rand" for which no system identifier could be generated
    …m/photos/random.mg?AlbumID=27869563&AlbumKey=2xswg4&Size=Tiny&rand=3923" /></a>

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

  • Info Line 715, Column 226: entity was defined here
    …m/photos/random.mg?AlbumID=27884697&AlbumKey=vXRwMp&Size=Tiny&rand=5865" /></a>
  • Warning Line 725, Column 239: NET-enabling start-tag requires SHORTTAG YES
    …m/photos/random.mg?AlbumID=27869563&AlbumKey=2xswg4&Size=Tiny&rand=3923" /></a>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 725, Column 239: required attribute "ALT" not specified
    …m/photos/random.mg?AlbumID=27869563&AlbumKey=2xswg4&Size=Tiny&rand=3923" /></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 731, Column 214: reference to entity "AlbumKey" for which no system identifier could be generated
    …m/photos/random.mg?AlbumID=27809143&AlbumKey=7f24tb&Size=Tiny&rand=4154" /></a>

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

  • Info Line 715, Column 200: entity was defined here
    ….com/photos/random.mg?AlbumID=27884697&AlbumKey=vXRwMp&Size=Tiny&rand=5865" />…
  • Error Line 731, Column 226: reference to entity "Size" for which no system identifier could be generated
    …m/photos/random.mg?AlbumID=27809143&AlbumKey=7f24tb&Size=Tiny&rand=4154" /></a>

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

  • Info Line 715, Column 216: entity was defined here
    …m/photos/random.mg?AlbumID=27884697&AlbumKey=vXRwMp&Size=Tiny&rand=5865" /></a>
  • Error Line 731, Column 236: reference to entity "rand" for which no system identifier could be generated
    …m/photos/random.mg?AlbumID=27809143&AlbumKey=7f24tb&Size=Tiny&rand=4154" /></a>

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

  • Info Line 715, Column 226: entity was defined here
    …m/photos/random.mg?AlbumID=27884697&AlbumKey=vXRwMp&Size=Tiny&rand=5865" /></a>
  • Warning Line 731, Column 243: NET-enabling start-tag requires SHORTTAG YES
    …m/photos/random.mg?AlbumID=27809143&AlbumKey=7f24tb&Size=Tiny&rand=4154" /></a>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 731, Column 243: required attribute "ALT" not specified
    …m/photos/random.mg?AlbumID=27809143&AlbumKey=7f24tb&Size=Tiny&rand=4154" /></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 736, Column 215: reference to entity "AlbumKey" for which no system identifier could be generated
    …m/photos/random.mg?AlbumID=27798733&AlbumKey=F3knKt&Size=Tiny&rand=9781" /></a>

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

  • Info Line 715, Column 200: entity was defined here
    ….com/photos/random.mg?AlbumID=27884697&AlbumKey=vXRwMp&Size=Tiny&rand=5865" />…
  • Error Line 736, Column 227: reference to entity "Size" for which no system identifier could be generated
    …m/photos/random.mg?AlbumID=27798733&AlbumKey=F3knKt&Size=Tiny&rand=9781" /></a>

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

  • Info Line 715, Column 216: entity was defined here
    …m/photos/random.mg?AlbumID=27884697&AlbumKey=vXRwMp&Size=Tiny&rand=5865" /></a>
  • Error Line 736, Column 237: reference to entity "rand" for which no system identifier could be generated
    …m/photos/random.mg?AlbumID=27798733&AlbumKey=F3knKt&Size=Tiny&rand=9781" /></a>

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

  • Info Line 715, Column 226: entity was defined here
    …m/photos/random.mg?AlbumID=27884697&AlbumKey=vXRwMp&Size=Tiny&rand=5865" /></a>
  • Warning Line 736, Column 244: NET-enabling start-tag requires SHORTTAG YES
    …m/photos/random.mg?AlbumID=27798733&AlbumKey=F3knKt&Size=Tiny&rand=9781" /></a>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 736, Column 244: required attribute "ALT" not specified
    …m/photos/random.mg?AlbumID=27798733&AlbumKey=F3knKt&Size=Tiny&rand=9781" /></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 741, Column 214: reference to entity "AlbumKey" for which no system identifier could be generated
    …m/photos/random.mg?AlbumID=27783698&AlbumKey=SF278J&Size=Tiny&rand=5692" /></a>

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

  • Info Line 715, Column 200: entity was defined here
    ….com/photos/random.mg?AlbumID=27884697&AlbumKey=vXRwMp&Size=Tiny&rand=5865" />…
  • Error Line 741, Column 226: reference to entity "Size" for which no system identifier could be generated
    …m/photos/random.mg?AlbumID=27783698&AlbumKey=SF278J&Size=Tiny&rand=5692" /></a>

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

  • Info Line 715, Column 216: entity was defined here
    …m/photos/random.mg?AlbumID=27884697&AlbumKey=vXRwMp&Size=Tiny&rand=5865" /></a>
  • Error Line 741, Column 236: reference to entity "rand" for which no system identifier could be generated
    …m/photos/random.mg?AlbumID=27783698&AlbumKey=SF278J&Size=Tiny&rand=5692" /></a>

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

  • Info Line 715, Column 226: entity was defined here
    …m/photos/random.mg?AlbumID=27884697&AlbumKey=vXRwMp&Size=Tiny&rand=5865" /></a>
  • Warning Line 741, Column 243: NET-enabling start-tag requires SHORTTAG YES
    …m/photos/random.mg?AlbumID=27783698&AlbumKey=SF278J&Size=Tiny&rand=5692" /></a>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 741, Column 243: required attribute "ALT" not specified
    …m/photos/random.mg?AlbumID=27783698&AlbumKey=SF278J&Size=Tiny&rand=5692" /></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>.

  • Warning Line 746, Column 6: NET-enabling start-tag requires SHORTTAG YES
      <br/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 759, Column 10: document type does not allow element "NOSCRIPT" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    <noscript><a href="http://polldaddy.com/poll/6819946/">Are you in favor of the …

    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 797, Column 36: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
              	><li class="listNoImage"><a href="http://www.bocopreps.com/spring-sp…

    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 800, Column 36: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
              	><li class="listNoImage"><a href="http://www.bocopreps.com/spring-sp…

    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 803, Column 36: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
              	><li class="listNoImage"><a href="http://www.bocopreps.com/spring-sp…

    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 806, Column 36: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
              	><li class="listNoImage"><a href="http://www.bocopreps.com/spring-sp…

    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 821, Column 36: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
              	><li class="listNoImage"><a href="http://www.bocopreps.com/dailyscor…

    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 824, Column 36: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
              	><li class="listNoImage"><a href="http://www.bocopreps.com/dailyscor…

    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 827, Column 36: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
              	><li class="listNoImage"><a href="http://www.bocopreps.com/dailyscor…

    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 830, Column 36: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
              	><li class="listNoImage"><a href="http://www.bocopreps.com/dailyscor…

    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 852, Column 36: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
              	><li class="listNoImage"><a href="http://www.bocopreps.com/ci_226229…

    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 855, Column 36: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
              	><li class="listNoImage"><a href="http://www.bocopreps.com/winter-sp…

    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 858, Column 36: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
              	><li class="listNoImage"><a href="http://www.bocopreps.com/ci_226039…

    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 878, Column 36: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
              	><li class="listNoImage"><a href="http://www.bocopreps.com/winter-sp…

    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 881, Column 36: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
              	><li class="listNoImage"><a href="http://www.bocopreps.com/winter-sp…

    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 884, Column 36: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
              	><li class="listNoImage"><a href="http://www.bocopreps.com/winter-sp…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Warning Line 893, Column 5: NET-enabling start-tag requires SHORTTAG YES
    <br />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 895, Column 230: NET-enabling start-tag requires SHORTTAG YES
    …f" alt="Click here to visit the DailyCamera.com" width="300" height="44" /></a>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 897, Column 5: NET-enabling start-tag requires SHORTTAG YES
    <br />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 898, Column 341: there is no attribute "ALLOWTRANSPARENCY"
    …low:hidden; width:300px; height:290px;" allowTransparency="true"></iframe></td>

    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 900, Column 138: there is no attribute "XMLNS:MNGI"
    … encoding="UTF-8"?><script xmlns:mngi="http://www.medianewsgroup.com" type="te…

    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 900, Column 290: there is no attribute "XMLNS:MNGI"
    …tabs.js">/**/</script><div xmlns:mngi="http://www.medianewsgroup.com" class="m…

    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 900, Column 1008: NET-enabling start-tag requires SHORTTAG YES
    …com/live/media/rss/rss.gif" border="0"/></a></span></div><div class="mostClear…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 900, Column 1008: required attribute "ALT" not specified
    …com/live/media/rss/rss.gif" border="0"/></a></span></div><div class="mostClear…

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

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

  • Warning Line 900, Column 1554: NET-enabling start-tag requires SHORTTAG YES
    …ive.com/live/iconTypes/multimedia.gif"/></a></li><li><a href="http://www.bocop…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 900, Column 1554: required attribute "ALT" not specified
    …ive.com/live/iconTypes/multimedia.gif"/></a></li><li><a href="http://www.bocop…

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

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

  • Warning Line 900, Column 2047: NET-enabling start-tag requires SHORTTAG YES
    …ive.com/live/iconTypes/multimedia.gif"/></a></li><li><a href="http://www.bocop…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 900, Column 2047: required attribute "ALT" not specified
    …ive.com/live/iconTypes/multimedia.gif"/></a></li><li><a href="http://www.bocop…

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

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

  • Warning Line 900, Column 3549: NET-enabling start-tag requires SHORTTAG YES
    …com/live/media/rss/rss.gif" border="0"/></a></span></div><div class="mostClear…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 900, Column 3549: required attribute "ALT" not specified
    …com/live/media/rss/rss.gif" border="0"/></a></span></div><div class="mostClear…

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

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

  • Warning Line 900, Column 3890: NET-enabling start-tag requires SHORTTAG YES
    …ive.com/live/iconTypes/multimedia.gif"/></a></li><li><a href="http://www.bocop…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 900, Column 3890: required attribute "ALT" not specified
    …ive.com/live/iconTypes/multimedia.gif"/></a></li><li><a href="http://www.bocop…

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

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

  • Warning Line 900, Column 4212: NET-enabling start-tag requires SHORTTAG YES
    …ive.com/live/iconTypes/multimedia.gif"/></a></li><li><a href="http://www.bocop…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 900, Column 4212: required attribute "ALT" not specified
    …ive.com/live/iconTypes/multimedia.gif"/></a></li><li><a href="http://www.bocop…

    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 900, Column 4465: required attribute "TYPE" not specified
    …21</a></li></ol></div></div><script xmlns:mngi="http://www.medianewsgroup.com">

    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 913, Column 36: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
              	><li class="listNoImage"><a href="http://www.bocopreps.com/fall-spor…

    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 916, Column 36: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
              	><li class="listNoImage"><a href="http://www.bocopreps.com/fall-spor…

    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 919, Column 36: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
              	><li class="listNoImage"><a href="http://www.bocopreps.com/fall-spor…

    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 922, Column 36: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
              	><li class="listNoImage"><a href="http://www.bocopreps.com/fall-spor…

    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 925, Column 36: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
              	><li class="listNoImage"><a href="http://www.bocopreps.com/fall-spor…

    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 928, Column 36: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
              	><li class="listNoImage"><a href="http://www.bocopreps.com/fall-spor…

    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 931, Column 36: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
              	><li class="listNoImage"><a href="http://www.bocopreps.com/fall-spor…

    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 934, Column 36: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
              	><li class="listNoImage"><a href="http://www.bocopreps.com/spring-sp…

    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 937, Column 36: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
              	><li class="listNoImage"><a href="http://www.bocopreps.com/spring-sp…

    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 940, Column 36: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
              	><li class="listNoImage"><a href="http://www.bocopreps.com/spring-sp…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Warning Line 960, Column 64: NET-enabling start-tag requires SHORTTAG YES
                    <a href="/contact-us">Contact Us</a>&nbsp; <br />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 968, Column 165: required attribute "ALT" not specified
    …0/2009/0427/20090427_123112_rssIcon14x14.gif" style="border:none;">&nbsp;&nbsp;

    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 975, Column 105: duplicate specification of attribute "STYLE"
    …lign:middle" class="myyahooHeadButton" id="myyahoo_200539" style="z-index: -1">

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 976, Column 90: required attribute "TYPE" not specified
    …ipt src="http://extras.mnginteractive.com/live/js/myyahoo/myyahoo.js"></script>

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

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

  • Warning Line 981, Column 141: NET-enabling start-tag requires SHORTTAG YES
    …/media/mng_logos/mng_footergraphic.jpg" border="0" alt="Media News Group"/></a>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 984, Column 182: required attribute "TYPE" not specified
    …opyright <script language="JavaScript"><!--Javascript call added to pull curre…

    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 990, Column 119: required attribute "ALT" not specified
    …e.com/live/media/site511/2010/1209/20101209_124714_Dasient_logo.JPG"></center> 

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

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

  • Warning Line 1001, Column 136: NET-enabling start-tag requires SHORTTAG YES
    …Q.gif" style="display: none;" border="0" height="1" width="1" alt="Quantcast"/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 1025, Column 103: document type does not allow element "LINK" here
    …l="stylesheet" href='http://extras.mnginteractive.com/live/css/site21/pmp.css'>

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Warning Line 1030, Column 1852: NET-enabling start-tag requires SHORTTAG YES
    …" target="copyright">Copyright</a><br /><a class="mngFooterImgLink" href="http…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 1030, Column 2030: required attribute "ALT" not specified
    …live/media/mng_logos/MNG_footerGraphic.jpg"></a><script type="text/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 1037, Column 160: end tag for element "A" which is not open
    …tomWeatherCopyrightLink'>Weather data Copyright 2007 CustomWeather, Inc.</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.

Visitor Analysis

Daily Visitor
  • 85 visits
Daily Visitor