honeybakedonline.com

Store Locator My Account My Gift List Help Shopping Cart 1-800-367-7720 Catalog local stores Gift Center catering business gifts Store Coupons Store Coupons Ham Ham Dinners Turkey Breast Whole Turkey Beef Pork Desserts ...

Display Widget for this domain on your website. Click Here
This data was last updated from 28-07-2013 05:41:29  (update).

Overview Info

  • Domain Name
    honeybakedonline.com
  • Favicon
  • Alexa Rank
    #74000
  • Google Page Rank
    PR 2
  • Ip Address
    107.7.182.102
  • Page Size
    21.4 KB
  • Images
    2 GIF, 7 JPG, 8 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    1 1 3 0 0 0

Website Meta Analysis



  • Title
    HoneyBaked - Online Home
  • Meta Keyword
  • Meta Description
    Store Locator My Account My Gift List Help Shopping Cart 1-800-367-7720 Catalog local stores Gift Center catering business gifts Store Coupons Store Coupons Ham Ham Dinners Turkey Breast Whole Turkey Beef Pork Desserts Side Dishes Gift Baskets ...

Technical Analysis



  • Webserver
    Microsoft-IIS/6.0
  • Ip Address
    107.7.182.102
  • Domain Age
    14 Years, 5 Months, 17 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • content-encoding: gzip
  • date: Sun, 28 Jul 2013 17:41:27 GMT
  • server: Microsoft-IIS/6.0
  • x-powered-by: ASP.NET
  • cache-control: private
  • pragma: no-cache
  • content-type: text/html
  • expires: Sat, 27 Jul 2013 17:41:26 GMT
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for honeybakedonline.com

DNS Analysis


DNS servers
ns1.easydns.com [64.68.192.210]
ns2.easydns.com [72.52.2.1]
remote1.easydns.com [64.68.192.210]
remote2.easydns.com [72.52.2.1]


DNS Records

Answer records
honeybakedonline.com SOA
server: dns1.easydns.com
email: zone@easydns.com
serial: 1360741467
refresh: 43200
retry: 10800
expire: 604800
minimum ttl: 900
900s
honeybakedonline.com NS  dns2.easydns.net 900s
honeybakedonline.com NS  dns3.easydns.ca 900s
honeybakedonline.com NS  dns1.easydns.com 900s
honeybakedonline.com A 107.7.182.102 900s

Authority records

Additional records

IP 107.7.182.102 Analysis

  • Country Code
    US
  • Country Code3
    USA
  • Country Name
    United States
  • City
    Anniston
  • Continent Code
    36207
  • Latitude
    256
  • Longitude
    630
  • #
    # Query terms are ambiguous. The query is assumed to be:
    # "n 107.7.182.102"
    #
    # Use "?" to get help.
    #

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

    ITC^Deltacom NETBLCK-ITCD-7 (NET-107-7-0-0-1) 107.7.0.0 - 107.7.255.255
    THE ORIGINAL HONEY BAKED HAM CO OF GA IN ITCD-107-7-182-96 (NET-107-7-182-96-1) 107.7.182.96 - 107.7.182.111


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

Site Same Ip

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 91 Errors
  • 102 Warnings
Ratio Text/Html
  • 0.6743165401846942
Message Error
  • Error Line 7, Column 61: end tag for "meta" omitted, but OMITTAG NO was specified
    <meta http-equiv="X-UA-Compatible" content="IE=EmulateIE7" >

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

  • Info Line 7, Column 1: start tag was here
    <meta http-equiv="X-UA-Compatible" content="IE=EmulateIE7" >
  • Error Line 10, Column 12: there is no attribute "NAME"
    <meta NAME="ROBOTS" CONTENT="NOINDEX, NOFOLLOW">

    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 10, Column 29: there is no attribute "CONTENT"
    <meta NAME="ROBOTS" CONTENT="NOINDEX, NOFOLLOW">

    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 10, Column 48: required attribute "content" not specified
    <meta NAME="ROBOTS" CONTENT="NOINDEX, NOFOLLOW">

    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 10, Column 49: end tag for "meta" omitted, but OMITTAG NO was specified
    <meta NAME="ROBOTS" CONTENT="NOINDEX, NOFOLLOW">

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

  • Info Line 10, Column 1: start tag was here
    <meta NAME="ROBOTS" CONTENT="NOINDEX, NOFOLLOW">
  • Warning Line 36, Column 28: character "&" is the first character of a delimiter but occurred as data
             if (charCode > 31 && (charCode < 48 || charCode > 57))

    This message may appear in several cases:

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

    This message may appear in several cases:

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

    This message may appear in several cases:

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

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

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

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

  • Error Line 113, Column 168: required attribute "alt" not specified
    …x.asp?Ref=35140649:96195131"><img src="../images/Content/logo.gif" /></a> </h1>

    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 122, Column 88: cannot generate system identifier for general entity "Ref"
    …com/HBOnline/GiftList/Login.asp?GL=-1&Ref=35140649:96195131">My Gift List</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 122, Column 88: general entity "Ref" not defined and no default entity
    …com/HBOnline/GiftList/Login.asp?GL=-1&Ref=35140649:96195131">My Gift List</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.

  • Warning Line 122, Column 91: reference not terminated by REFC delimiter
    …/HBOnline/GiftList/Login.asp?GL=-1&Ref=35140649:96195131">My Gift List</a></li…

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

  • Warning Line 122, Column 91: reference to external entity in attribute value
    …/HBOnline/GiftList/Login.asp?GL=-1&Ref=35140649:96195131">My Gift List</a></li…

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

  • Error Line 122, Column 91: reference to entity "Ref" for which no system identifier could be generated
    …/HBOnline/GiftList/Login.asp?GL=-1&Ref=35140649:96195131">My Gift List</a></li…

    This is usually a cascading error caused by 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 122, Column 87: entity was defined here
    ….com/HBOnline/GiftList/Login.asp?GL=-1&Ref=35140649:96195131">My Gift List</a>…
  • Error Line 135, Column 44: there is no attribute "onClick"
    … <li id="catalog" class="top" onClick="javascript: window.location='http://www…

    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 165, Column 145: reference not terminated by REFC delimiter
    …ine/Shop/CouponLinks.asp?WCID=3263&Ref=35140649:96195131'"><a class="tip" href…

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

  • Warning Line 165, Column 145: reference to external entity in attribute value
    …ine/Shop/CouponLinks.asp?WCID=3263&Ref=35140649:96195131'"><a class="tip" href…

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

  • Error Line 165, Column 145: reference to entity "Ref" for which no system identifier could be generated
    …ine/Shop/CouponLinks.asp?WCID=3263&Ref=35140649:96195131'"><a class="tip" href…

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

  • Info Line 122, Column 87: entity was defined here
    ….com/HBOnline/GiftList/Login.asp?GL=-1&Ref=35140649:96195131">My Gift List</a>…
  • Error Line 180, 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>.

  • Error Line 194, Column 18: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
        <form method=get action="../shop/SearchResults.asp?Ref=35140649:96195131" >
  • Error Line 196, Column 99: there is no attribute "onFocus"
    …20px !IMPORTANT;" type="text" onFocus="SearchControlEvent(this)"  value="Enter…

    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 198, Column 74: end tag for "input" omitted, but OMITTAG NO was specified
            <input type="hidden" name="cmbSearchOptions" value="Entire Site">

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

  • Info Line 198, Column 9: start tag was here
            <input type="hidden" name="cmbSearchOptions" value="Entire Site">
  • Error Line 201, Column 15: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    	 <input type=hidden id="ref" name="ref" value="35140649:96195131">
  • Error Line 201, Column 68: end tag for "input" omitted, but OMITTAG NO was specified
    	 <input type=hidden id="ref" name="ref" value="35140649:96195131">

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

  • Info Line 201, Column 3: start tag was here
    	 <input type=hidden id="ref" name="ref" value="35140649:96195131">
  • Error Line 203, Column 35: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
          <button id="btnSearch" type=submit> <img src="../images/Content/btnSearch…
  • Error Line 217, Column 12: required attribute "type" not specified
        <script>var hrefs = new Array();hrefs[0]='../Shop/Item.asp?CATID=3001&Ref=3…

    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 217, Column 78: reference not terminated by REFC delimiter
    …fs[0]='../Shop/Item.asp?CATID=3001&Ref=35140649:96195131';hrefs[1]='../Shop/It…

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

  • Error Line 217, Column 78: reference to entity "Ref" for which no system identifier could be generated
    …fs[0]='../Shop/Item.asp?CATID=3001&Ref=35140649:96195131';hrefs[1]='../Shop/It…

    This is usually a cascading error caused by 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 122, Column 87: entity was defined here
    ….com/HBOnline/GiftList/Login.asp?GL=-1&Ref=35140649:96195131">My Gift List</a>…
  • Warning Line 217, Column 140: cannot generate system identifier for general entity "WCWSC"
    …s[1]='../Shop/ItemList.asp?CATID=3320&WCWSC=3320&Ref=35140649:96195131';hrefs[…

    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 217, Column 140: general entity "WCWSC" not defined and no default entity
    …s[1]='../Shop/ItemList.asp?CATID=3320&WCWSC=3320&Ref=35140649:96195131';hrefs[…

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

  • Warning Line 217, Column 145: reference not terminated by REFC delimiter
    …'../Shop/ItemList.asp?CATID=3320&WCWSC=3320&Ref=35140649:96195131';hrefs[2]='.…

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

  • Error Line 217, Column 145: reference to entity "WCWSC" for which no system identifier could be generated
    …'../Shop/ItemList.asp?CATID=3320&WCWSC=3320&Ref=35140649:96195131';hrefs[2]='.…

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

  • Info Line 217, Column 139: entity was defined here
    …fs[1]='../Shop/ItemList.asp?CATID=3320&WCWSC=3320&Ref=35140649:96195131';hrefs…
  • Warning Line 217, Column 154: reference not terminated by REFC delimiter
    …ItemList.asp?CATID=3320&WCWSC=3320&Ref=35140649:96195131';hrefs[2]='../Shop/It…

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

  • Error Line 217, Column 154: reference to entity "Ref" for which no system identifier could be generated
    …ItemList.asp?CATID=3320&WCWSC=3320&Ref=35140649:96195131';hrefs[2]='../Shop/It…

    This is usually a cascading error caused by 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 122, Column 87: entity was defined here
    ….com/HBOnline/GiftList/Login.asp?GL=-1&Ref=35140649:96195131">My Gift List</a>…
  • Warning Line 217, Column 221: reference not terminated by REFC delimiter
    …'../Shop/ItemList.asp?CATID=3320&WCWSC=3327&Ref=35140649:96195131';hrefs[3]='.…

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

  • Error Line 217, Column 221: reference to entity "WCWSC" for which no system identifier could be generated
    …'../Shop/ItemList.asp?CATID=3320&WCWSC=3327&Ref=35140649:96195131';hrefs[3]='.…

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

  • Info Line 217, Column 139: entity was defined here
    …fs[1]='../Shop/ItemList.asp?CATID=3320&WCWSC=3320&Ref=35140649:96195131';hrefs…
  • Warning Line 217, Column 230: reference not terminated by REFC delimiter
    …ItemList.asp?CATID=3320&WCWSC=3327&Ref=35140649:96195131';hrefs[3]='../Shop/It…

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

  • Error Line 217, Column 230: reference to entity "Ref" for which no system identifier could be generated
    …ItemList.asp?CATID=3320&WCWSC=3327&Ref=35140649:96195131';hrefs[3]='../Shop/It…

    This is usually a cascading error caused by 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 122, Column 87: entity was defined here
    ….com/HBOnline/GiftList/Login.asp?GL=-1&Ref=35140649:96195131">My Gift List</a>…
  • Warning Line 217, Column 297: reference not terminated by REFC delimiter
    …'../Shop/ItemList.asp?CATID=3320&WCWSC=3334&Ref=35140649:96195131';var slideSh…

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

  • Error Line 217, Column 297: reference to entity "WCWSC" for which no system identifier could be generated
    …'../Shop/ItemList.asp?CATID=3320&WCWSC=3334&Ref=35140649:96195131';var slideSh…

    This is usually a cascading error caused by 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 217, Column 139: entity was defined here
    …fs[1]='../Shop/ItemList.asp?CATID=3320&WCWSC=3320&Ref=35140649:96195131';hrefs…
  • Warning Line 217, Column 306: reference not terminated by REFC delimiter
    …ItemList.asp?CATID=3320&WCWSC=3334&Ref=35140649:96195131';var slideShowSpeed =…

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

  • Error Line 217, Column 306: reference to entity "Ref" for which no system identifier could be generated
    …ItemList.asp?CATID=3320&WCWSC=3334&Ref=35140649:96195131';var slideShowSpeed =…

    This is usually a cascading error caused by 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 122, Column 87: entity was defined here
    ….com/HBOnline/GiftList/Login.asp?GL=-1&Ref=35140649:96195131">My Gift List</a>…
  • Warning Line 217, Column 636: character "<" is the first character of a delimiter but occurred as data
    …r preLoad = new Array();for (i = 0; i < p; i++){   preLoad[i] = new Image();  …

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 217, Column 2200: reference not terminated by REFC delimiter
    …rmation2.asp?Promo=" + somevar + "&Ref=35140649:96195131","","width=450,height…

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

  • Error Line 217, Column 2200: reference to entity "Ref" for which no system identifier could be generated
    …rmation2.asp?Promo=" + somevar + "&Ref=35140649:96195131","","width=450,height…

    This is usually a cascading error caused by 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 122, Column 87: entity was defined here
    ….com/HBOnline/GiftList/Login.asp?GL=-1&Ref=35140649:96195131">My Gift List</a>…
  • Error Line 217, Column 3259: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …and;' id='reveal' name='reveal' width=505 height=307 border="0" /></div>    </…
  • Error Line 217, Column 3270: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …eveal' name='reveal' width=505 height=307 border="0" /></div>    </div>    <di…
  • Error Line 217, Column 3286: required attribute "alt" not specified
    …eal' width=505 height=307 border="0" /></div>    </div>    <div id="nav">     …

    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 217, Column 3464: reference not terminated by REFC delimiter
    … href="../Shop/Item.asp?CATID=3001&Ref=35140649:96195131" onMouseOver="SetImg(…

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

  • Warning Line 217, Column 3464: reference to external entity in attribute value
    … href="../Shop/Item.asp?CATID=3001&Ref=35140649:96195131" onMouseOver="SetImg(…

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

  • Error Line 217, Column 3464: reference to entity "Ref" for which no system identifier could be generated
    … href="../Shop/Item.asp?CATID=3001&Ref=35140649:96195131" onMouseOver="SetImg(…

    This is usually a cascading error caused by 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 122, Column 87: entity was defined here
    ….com/HBOnline/GiftList/Login.asp?GL=-1&Ref=35140649:96195131">My Gift List</a>…
  • Error Line 217, Column 3496: there is no attribute "onMouseOver"
    …01&Ref=35140649:96195131" onMouseOver="SetImg('../images/content/ID4472.jpg','…

    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 217, Column 3567: reference not terminated by REFC delimiter
    ….jpg','../Shop/Item.asp?CATID=3001&Ref=35140649:96195131');">Ham</a></div>    …

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

  • Warning Line 217, Column 3567: reference to external entity in attribute value
    ….jpg','../Shop/Item.asp?CATID=3001&Ref=35140649:96195131');">Ham</a></div>    …

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

  • Error Line 217, Column 3567: reference to entity "Ref" for which no system identifier could be generated
    ….jpg','../Shop/Item.asp?CATID=3001&Ref=35140649:96195131');">Ham</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 122, Column 87: entity was defined here
    ….com/HBOnline/GiftList/Login.asp?GL=-1&Ref=35140649:96195131">My Gift List</a>…
  • Warning Line 217, Column 3718: reference not terminated by REFC delimiter
    …"../Shop/ItemList.asp?CATID=3320&WCWSC=3319&Ref=35140649:96195131" onMouseOver…

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

  • Warning Line 217, Column 3718: reference to external entity in attribute value
    …"../Shop/ItemList.asp?CATID=3320&WCWSC=3319&Ref=35140649:96195131" onMouseOver…

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

  • Error Line 217, Column 3718: reference to entity "WCWSC" for which no system identifier could be generated
    …"../Shop/ItemList.asp?CATID=3320&WCWSC=3319&Ref=35140649:96195131" onMouseOver…

    This is usually a cascading error caused by 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 217, Column 139: entity was defined here
    …fs[1]='../Shop/ItemList.asp?CATID=3320&WCWSC=3320&Ref=35140649:96195131';hrefs…
  • Warning Line 217, Column 3727: reference not terminated by REFC delimiter
    …ItemList.asp?CATID=3320&WCWSC=3319&Ref=35140649:96195131" onMouseOver="SetImg(…

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

  • Warning Line 217, Column 3727: reference to external entity in attribute value
    …ItemList.asp?CATID=3320&WCWSC=3319&Ref=35140649:96195131" onMouseOver="SetImg(…

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

  • Error Line 217, Column 3727: reference to entity "Ref" for which no system identifier could be generated
    …ItemList.asp?CATID=3320&WCWSC=3319&Ref=35140649:96195131" onMouseOver="SetImg(…

    This is usually a cascading error caused by 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 122, Column 87: entity was defined here
    ….com/HBOnline/GiftList/Login.asp?GL=-1&Ref=35140649:96195131">My Gift List</a>…
  • Warning Line 217, Column 3836: reference not terminated by REFC delimiter
    …'../Shop/ItemList.asp?CATID=3320&WCWSC=3319&Ref=35140649:96195131');">Ham Dinn…

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

  • Warning Line 217, Column 3836: reference to external entity in attribute value
    …'../Shop/ItemList.asp?CATID=3320&WCWSC=3319&Ref=35140649:96195131');">Ham Dinn…

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

  • Error Line 217, Column 3836: reference to entity "WCWSC" for which no system identifier could be generated
    …'../Shop/ItemList.asp?CATID=3320&WCWSC=3319&Ref=35140649:96195131');">Ham Dinn…

    This is usually a cascading error caused by 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 217, Column 139: entity was defined here
    …fs[1]='../Shop/ItemList.asp?CATID=3320&WCWSC=3320&Ref=35140649:96195131';hrefs…
  • Warning Line 217, Column 3845: reference not terminated by REFC delimiter
    …ItemList.asp?CATID=3320&WCWSC=3319&Ref=35140649:96195131');">Ham Dinners</a></…

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

  • Warning Line 217, Column 3845: reference to external entity in attribute value
    …ItemList.asp?CATID=3320&WCWSC=3319&Ref=35140649:96195131');">Ham Dinners</a></…

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

  • Error Line 217, Column 3845: reference to entity "Ref" for which no system identifier could be generated
    …ItemList.asp?CATID=3320&WCWSC=3319&Ref=35140649:96195131');">Ham Dinners</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 122, Column 87: entity was defined here
    ….com/HBOnline/GiftList/Login.asp?GL=-1&Ref=35140649:96195131">My Gift List</a>…
  • Warning Line 217, Column 4006: reference not terminated by REFC delimiter
    …"../Shop/ItemList.asp?CATID=3320&WCWSC=3320&Ref=35140649:96195131" onMouseOver…

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

  • Warning Line 217, Column 4006: reference to external entity in attribute value
    …"../Shop/ItemList.asp?CATID=3320&WCWSC=3320&Ref=35140649:96195131" onMouseOver…

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

  • Error Line 217, Column 4006: reference to entity "WCWSC" for which no system identifier could be generated
    …"../Shop/ItemList.asp?CATID=3320&WCWSC=3320&Ref=35140649:96195131" onMouseOver…

    This is usually a cascading error caused by 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 217, Column 139: entity was defined here
    …fs[1]='../Shop/ItemList.asp?CATID=3320&WCWSC=3320&Ref=35140649:96195131';hrefs…
  • Warning Line 217, Column 4015: reference not terminated by REFC delimiter
    …ItemList.asp?CATID=3320&WCWSC=3320&Ref=35140649:96195131" onMouseOver="SetImg(…

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

  • Warning Line 217, Column 4015: reference to external entity in attribute value
    …ItemList.asp?CATID=3320&WCWSC=3320&Ref=35140649:96195131" onMouseOver="SetImg(…

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

  • Error Line 217, Column 4015: reference to entity "Ref" for which no system identifier could be generated
    …ItemList.asp?CATID=3320&WCWSC=3320&Ref=35140649:96195131" onMouseOver="SetImg(…

    This is usually a cascading error caused by 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 122, Column 87: entity was defined here
    ….com/HBOnline/GiftList/Login.asp?GL=-1&Ref=35140649:96195131">My Gift List</a>…
  • Warning Line 217, Column 4124: reference not terminated by REFC delimiter
    …'../Shop/ItemList.asp?CATID=3320&WCWSC=3320&Ref=35140649:96195131')">Turkey Br…

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

  • Warning Line 217, Column 4124: reference to external entity in attribute value
    …'../Shop/ItemList.asp?CATID=3320&WCWSC=3320&Ref=35140649:96195131')">Turkey Br…

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

  • Error Line 217, Column 4124: reference to entity "WCWSC" for which no system identifier could be generated
    …'../Shop/ItemList.asp?CATID=3320&WCWSC=3320&Ref=35140649:96195131')">Turkey Br…

    This is usually a cascading error caused by 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 217, Column 139: entity was defined here
    …fs[1]='../Shop/ItemList.asp?CATID=3320&WCWSC=3320&Ref=35140649:96195131';hrefs…
  • Warning Line 217, Column 4133: reference not terminated by REFC delimiter
    …ItemList.asp?CATID=3320&WCWSC=3320&Ref=35140649:96195131')">Turkey Breast</a><…

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

  • Warning Line 217, Column 4133: reference to external entity in attribute value
    …ItemList.asp?CATID=3320&WCWSC=3320&Ref=35140649:96195131')">Turkey Breast</a><…

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

  • Error Line 217, Column 4133: reference to entity "Ref" for which no system identifier could be generated
    …ItemList.asp?CATID=3320&WCWSC=3320&Ref=35140649:96195131')">Turkey Breast</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 122, Column 87: entity was defined here
    ….com/HBOnline/GiftList/Login.asp?GL=-1&Ref=35140649:96195131">My Gift List</a>…
  • Warning Line 217, Column 4294: reference not terminated by REFC delimiter
    …"../Shop/ItemList.asp?CATID=3320&WCWSC=3334&Ref=35140649:96195131" onMouseOver…

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

  • Warning Line 217, Column 4294: reference to external entity in attribute value
    …"../Shop/ItemList.asp?CATID=3320&WCWSC=3334&Ref=35140649:96195131" onMouseOver…

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

  • Error Line 217, Column 4294: reference to entity "WCWSC" for which no system identifier could be generated
    …"../Shop/ItemList.asp?CATID=3320&WCWSC=3334&Ref=35140649:96195131" onMouseOver…

    This is usually a cascading error caused by 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 217, Column 139: entity was defined here
    …fs[1]='../Shop/ItemList.asp?CATID=3320&WCWSC=3320&Ref=35140649:96195131';hrefs…
  • Warning Line 217, Column 4303: reference not terminated by REFC delimiter
    …ItemList.asp?CATID=3320&WCWSC=3334&Ref=35140649:96195131" onMouseOver="SetImg(…

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

  • Warning Line 217, Column 4303: reference to external entity in attribute value
    …ItemList.asp?CATID=3320&WCWSC=3334&Ref=35140649:96195131" onMouseOver="SetImg(…

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

  • Error Line 217, Column 4303: reference to entity "Ref" for which no system identifier could be generated
    …ItemList.asp?CATID=3320&WCWSC=3334&Ref=35140649:96195131" onMouseOver="SetImg(…

    This is usually a cascading error caused by 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 122, Column 87: entity was defined here
    ….com/HBOnline/GiftList/Login.asp?GL=-1&Ref=35140649:96195131">My Gift List</a>…
  • Warning Line 217, Column 4412: reference not terminated by REFC delimiter
    …'../Shop/ItemList.asp?CATID=3320&WCWSC=3334&Ref=35140649:96195131');">Whole Tu…

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

  • Warning Line 217, Column 4412: reference to external entity in attribute value
    …'../Shop/ItemList.asp?CATID=3320&WCWSC=3334&Ref=35140649:96195131');">Whole Tu…

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

  • Error Line 217, Column 4412: reference to entity "WCWSC" for which no system identifier could be generated
    …'../Shop/ItemList.asp?CATID=3320&WCWSC=3334&Ref=35140649:96195131');">Whole Tu…

    This is usually a cascading error caused by 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 217, Column 139: entity was defined here
    …fs[1]='../Shop/ItemList.asp?CATID=3320&WCWSC=3320&Ref=35140649:96195131';hrefs…
  • Warning Line 217, Column 4421: reference not terminated by REFC delimiter
    …ItemList.asp?CATID=3320&WCWSC=3334&Ref=35140649:96195131');">Whole Turkey</a><…

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

  • Warning Line 217, Column 4421: reference to external entity in attribute value
    …ItemList.asp?CATID=3320&WCWSC=3334&Ref=35140649:96195131');">Whole Turkey</a><…

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

  • Error Line 217, Column 4421: reference to entity "Ref" for which no system identifier could be generated
    …ItemList.asp?CATID=3320&WCWSC=3334&Ref=35140649:96195131');">Whole Turkey</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 122, Column 87: entity was defined here
    ….com/HBOnline/GiftList/Login.asp?GL=-1&Ref=35140649:96195131">My Gift List</a>…
  • Warning Line 217, Column 4575: reference not terminated by REFC delimiter
    …"../Shop/ItemList.asp?CATID=3320&WCWSC=3321&Ref=35140649:96195131" onMouseOver…

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

  • Warning Line 217, Column 4575: reference to external entity in attribute value
    …"../Shop/ItemList.asp?CATID=3320&WCWSC=3321&Ref=35140649:96195131" onMouseOver…

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

  • Error Line 217, Column 4575: reference to entity "WCWSC" for which no system identifier could be generated
    …"../Shop/ItemList.asp?CATID=3320&WCWSC=3321&Ref=35140649:96195131" onMouseOver…

    This is usually a cascading error caused by 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 217, Column 139: entity was defined here
    …fs[1]='../Shop/ItemList.asp?CATID=3320&WCWSC=3320&Ref=35140649:96195131';hrefs…
  • Warning Line 217, Column 4584: reference not terminated by REFC delimiter
    …ItemList.asp?CATID=3320&WCWSC=3321&Ref=35140649:96195131" onMouseOver="SetImg(…

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

  • Warning Line 217, Column 4584: reference to external entity in attribute value
    …ItemList.asp?CATID=3320&WCWSC=3321&Ref=35140649:96195131" onMouseOver="SetImg(…

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

  • Error Line 217, Column 4584: reference to entity "Ref" for which no system identifier could be generated
    …ItemList.asp?CATID=3320&WCWSC=3321&Ref=35140649:96195131" onMouseOver="SetImg(…

    This is usually a cascading error caused by 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 122, Column 87: entity was defined here
    ….com/HBOnline/GiftList/Login.asp?GL=-1&Ref=35140649:96195131">My Gift List</a>…
  • Warning Line 217, Column 4693: reference not terminated by REFC delimiter
    …'../Shop/ItemList.asp?CATID=3320&WCWSC=3321&Ref=35140649:96195131');">Beef</a>…

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

  • Warning Line 217, Column 4693: reference to external entity in attribute value
    …'../Shop/ItemList.asp?CATID=3320&WCWSC=3321&Ref=35140649:96195131');">Beef</a>…

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

  • Error Line 217, Column 4693: reference to entity "WCWSC" for which no system identifier could be generated
    …'../Shop/ItemList.asp?CATID=3320&WCWSC=3321&Ref=35140649:96195131');">Beef</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 217, Column 139: entity was defined here
    …fs[1]='../Shop/ItemList.asp?CATID=3320&WCWSC=3320&Ref=35140649:96195131';hrefs…
  • Warning Line 217, Column 4702: reference not terminated by REFC delimiter
    …ItemList.asp?CATID=3320&WCWSC=3321&Ref=35140649:96195131');">Beef</a></div>   …

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

  • Warning Line 217, Column 4702: reference to external entity in attribute value
    …ItemList.asp?CATID=3320&WCWSC=3321&Ref=35140649:96195131');">Beef</a></div>   …

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

  • Error Line 217, Column 4702: reference to entity "Ref" for which no system identifier could be generated
    …ItemList.asp?CATID=3320&WCWSC=3321&Ref=35140649:96195131');">Beef</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 122, Column 87: entity was defined here
    ….com/HBOnline/GiftList/Login.asp?GL=-1&Ref=35140649:96195131">My Gift List</a>…
  • Warning Line 217, Column 4848: reference not terminated by REFC delimiter
    …"../Shop/ItemList.asp?CATID=3320&WCWSC=3322&Ref=35140649:96195131" onMouseOver…

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

  • Warning Line 217, Column 4848: reference to external entity in attribute value
    …"../Shop/ItemList.asp?CATID=3320&WCWSC=3322&Ref=35140649:96195131" onMouseOver…

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

  • Error Line 217, Column 4848: reference to entity "WCWSC" for which no system identifier could be generated
    …"../Shop/ItemList.asp?CATID=3320&WCWSC=3322&Ref=35140649:96195131" onMouseOver…

    This is usually a cascading error caused by 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 217, Column 139: entity was defined here
    …fs[1]='../Shop/ItemList.asp?CATID=3320&WCWSC=3320&Ref=35140649:96195131';hrefs…
  • Warning Line 217, Column 4857: reference not terminated by REFC delimiter
    …ItemList.asp?CATID=3320&WCWSC=3322&Ref=35140649:96195131" onMouseOver="SetImg(…

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

  • Warning Line 217, Column 4857: reference to external entity in attribute value
    …ItemList.asp?CATID=3320&WCWSC=3322&Ref=35140649:96195131" onMouseOver="SetImg(…

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

  • Error Line 217, Column 4857: reference to entity "Ref" for which no system identifier could be generated
    …ItemList.asp?CATID=3320&WCWSC=3322&Ref=35140649:96195131" onMouseOver="SetImg(…

    This is usually a cascading error caused by 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 122, Column 87: entity was defined here
    ….com/HBOnline/GiftList/Login.asp?GL=-1&Ref=35140649:96195131">My Gift List</a>…
  • Warning Line 217, Column 4966: reference not terminated by REFC delimiter
    …'../Shop/ItemList.asp?CATID=3320&WCWSC=3322&Ref=35140649:96195131');">Pork</a>…

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

  • Warning Line 217, Column 4966: reference to external entity in attribute value
    …'../Shop/ItemList.asp?CATID=3320&WCWSC=3322&Ref=35140649:96195131');">Pork</a>…

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

  • Error Line 217, Column 4966: reference to entity "WCWSC" for which no system identifier could be generated
    …'../Shop/ItemList.asp?CATID=3320&WCWSC=3322&Ref=35140649:96195131');">Pork</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 217, Column 139: entity was defined here
    …fs[1]='../Shop/ItemList.asp?CATID=3320&WCWSC=3320&Ref=35140649:96195131';hrefs…
  • Warning Line 217, Column 4975: reference not terminated by REFC delimiter
    …ItemList.asp?CATID=3320&WCWSC=3322&Ref=35140649:96195131');">Pork</a></div>   …

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

  • Warning Line 217, Column 4975: reference to external entity in attribute value
    …ItemList.asp?CATID=3320&WCWSC=3322&Ref=35140649:96195131');">Pork</a></div>   …

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

  • Error Line 217, Column 4975: reference to entity "Ref" for which no system identifier could be generated
    …ItemList.asp?CATID=3320&WCWSC=3322&Ref=35140649:96195131');">Pork</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 122, Column 87: entity was defined here
    ….com/HBOnline/GiftList/Login.asp?GL=-1&Ref=35140649:96195131">My Gift List</a>…
  • Warning Line 217, Column 5125: reference not terminated by REFC delimiter
    …"../Shop/ItemList.asp?CATID=3320&WCWSC=3327&Ref=35140649:96195131" onMouseOver…

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

  • Warning Line 217, Column 5125: reference to external entity in attribute value
    …"../Shop/ItemList.asp?CATID=3320&WCWSC=3327&Ref=35140649:96195131" onMouseOver…

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

  • Error Line 217, Column 5125: reference to entity "WCWSC" for which no system identifier could be generated
    …"../Shop/ItemList.asp?CATID=3320&WCWSC=3327&Ref=35140649:96195131" onMouseOver…

    This is usually a cascading error caused by 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 217, Column 139: entity was defined here
    …fs[1]='../Shop/ItemList.asp?CATID=3320&WCWSC=3320&Ref=35140649:96195131';hrefs…
  • Warning Line 217, Column 5134: reference not terminated by REFC delimiter
    …ItemList.asp?CATID=3320&WCWSC=3327&Ref=35140649:96195131" onMouseOver="SetImg(…

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

  • Warning Line 217, Column 5134: reference to external entity in attribute value
    …ItemList.asp?CATID=3320&WCWSC=3327&Ref=35140649:96195131" onMouseOver="SetImg(…

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

  • Error Line 217, Column 5134: reference to entity "Ref" for which no system identifier could be generated
    …ItemList.asp?CATID=3320&WCWSC=3327&Ref=35140649:96195131" onMouseOver="SetImg(…

    This is usually a cascading error caused by 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 122, Column 87: entity was defined here
    ….com/HBOnline/GiftList/Login.asp?GL=-1&Ref=35140649:96195131">My Gift List</a>…
  • Warning Line 217, Column 5243: reference not terminated by REFC delimiter
    …'../Shop/ItemList.asp?CATID=3320&WCWSC=3327&Ref=35140649:96195131');">Desserts…

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

  • Warning Line 217, Column 5243: reference to external entity in attribute value
    …'../Shop/ItemList.asp?CATID=3320&WCWSC=3327&Ref=35140649:96195131');">Desserts…

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

  • Error Line 217, Column 5243: reference to entity "WCWSC" for which no system identifier could be generated
    …'../Shop/ItemList.asp?CATID=3320&WCWSC=3327&Ref=35140649:96195131');">Desserts…

    This is usually a cascading error caused by 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 217, Column 139: entity was defined here
    …fs[1]='../Shop/ItemList.asp?CATID=3320&WCWSC=3320&Ref=35140649:96195131';hrefs…
  • Warning Line 217, Column 5252: reference not terminated by REFC delimiter
    …ItemList.asp?CATID=3320&WCWSC=3327&Ref=35140649:96195131');">Desserts</a></div…

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

  • Warning Line 217, Column 5252: reference to external entity in attribute value
    …ItemList.asp?CATID=3320&WCWSC=3327&Ref=35140649:96195131');">Desserts</a></div…

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

  • Error Line 217, Column 5252: reference to entity "Ref" for which no system identifier could be generated
    …ItemList.asp?CATID=3320&WCWSC=3327&Ref=35140649:96195131');">Desserts</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 122, Column 87: entity was defined here
    ….com/HBOnline/GiftList/Login.asp?GL=-1&Ref=35140649:96195131">My Gift List</a>…
  • Warning Line 217, Column 5404: reference not terminated by REFC delimiter
    …ref="../Shop/Item.asp?CATID=3320&WCWSC=3325&Ref=35140649:96195131" onMouseOver…

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

  • Warning Line 217, Column 5404: reference to external entity in attribute value
    …ref="../Shop/Item.asp?CATID=3320&WCWSC=3325&Ref=35140649:96195131" onMouseOver…

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

  • Error Line 217, Column 5404: reference to entity "WCWSC" for which no system identifier could be generated
    …ref="../Shop/Item.asp?CATID=3320&WCWSC=3325&Ref=35140649:96195131" onMouseOver…

    This is usually a cascading error caused by 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 217, Column 139: entity was defined here
    …fs[1]='../Shop/ItemList.asp?CATID=3320&WCWSC=3320&Ref=35140649:96195131';hrefs…
  • Warning Line 217, Column 5413: reference not terminated by REFC delimiter
    …hop/Item.asp?CATID=3320&WCWSC=3325&Ref=35140649:96195131" onMouseOver="SetImg(…

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

  • Warning Line 217, Column 5413: reference to external entity in attribute value
    …hop/Item.asp?CATID=3320&WCWSC=3325&Ref=35140649:96195131" onMouseOver="SetImg(…

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

  • Error Line 217, Column 5413: reference to entity "Ref" for which no system identifier could be generated
    …hop/Item.asp?CATID=3320&WCWSC=3325&Ref=35140649:96195131" onMouseOver="SetImg(…

    This is usually a cascading error caused by 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 122, Column 87: entity was defined here
    ….com/HBOnline/GiftList/Login.asp?GL=-1&Ref=35140649:96195131">My Gift List</a>…
  • Warning Line 217, Column 5518: reference not terminated by REFC delimiter
    …pg','../Shop/Item.asp?CATID=3320&WCWSC=3325&Ref=35140649:96195131');">Side Dis…

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

  • Warning Line 217, Column 5518: reference to external entity in attribute value
    …pg','../Shop/Item.asp?CATID=3320&WCWSC=3325&Ref=35140649:96195131');">Side Dis…

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

  • Error Line 217, Column 5518: reference to entity "WCWSC" for which no system identifier could be generated
    …pg','../Shop/Item.asp?CATID=3320&WCWSC=3325&Ref=35140649:96195131');">Side Dis…

    This is usually a cascading error caused by 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 217, Column 139: entity was defined here
    …fs[1]='../Shop/ItemList.asp?CATID=3320&WCWSC=3320&Ref=35140649:96195131';hrefs…
  • Warning Line 217, Column 5527: reference not terminated by REFC delimiter
    …hop/Item.asp?CATID=3320&WCWSC=3325&Ref=35140649:96195131');">Side Dishes</a></…

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

  • Warning Line 217, Column 5527: reference to external entity in attribute value
    …hop/Item.asp?CATID=3320&WCWSC=3325&Ref=35140649:96195131');">Side Dishes</a></…

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

  • Error Line 217, Column 5527: reference to entity "Ref" for which no system identifier could be generated
    …hop/Item.asp?CATID=3320&WCWSC=3325&Ref=35140649:96195131');">Side Dishes</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 122, Column 87: entity was defined here
    ….com/HBOnline/GiftList/Login.asp?GL=-1&Ref=35140649:96195131">My Gift List</a>…
  • Warning Line 217, Column 5687: reference not terminated by REFC delimiter
    …"../Shop/ItemList.asp?CATID=3320&WCWSC=3332&Ref=35140649:96195131" onMouseOver…

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

  • Warning Line 217, Column 5687: reference to external entity in attribute value
    …"../Shop/ItemList.asp?CATID=3320&WCWSC=3332&Ref=35140649:96195131" onMouseOver…

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

  • Error Line 217, Column 5687: reference to entity "WCWSC" for which no system identifier could be generated
    …"../Shop/ItemList.asp?CATID=3320&WCWSC=3332&Ref=35140649:96195131" onMouseOver…

    This is usually a cascading error caused by 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 217, Column 139: entity was defined here
    …fs[1]='../Shop/ItemList.asp?CATID=3320&WCWSC=3320&Ref=35140649:96195131';hrefs…
  • Warning Line 217, Column 5696: reference not terminated by REFC delimiter
    …ItemList.asp?CATID=3320&WCWSC=3332&Ref=35140649:96195131" onMouseOver="SetImg(…

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

  • Warning Line 217, Column 5696: reference to external entity in attribute value
    …ItemList.asp?CATID=3320&WCWSC=3332&Ref=35140649:96195131" onMouseOver="SetImg(…

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

  • Error Line 217, Column 5696: reference to entity "Ref" for which no system identifier could be generated
    …ItemList.asp?CATID=3320&WCWSC=3332&Ref=35140649:96195131" onMouseOver="SetImg(…

    This is usually a cascading error caused by 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 122, Column 87: entity was defined here
    ….com/HBOnline/GiftList/Login.asp?GL=-1&Ref=35140649:96195131">My Gift List</a>…
  • Warning Line 217, Column 5805: reference not terminated by REFC delimiter
    …'../Shop/ItemList.asp?CATID=3320&WCWSC=3332&Ref=35140649:96195131');">Gift Bas…

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

  • Warning Line 217, Column 5805: reference to external entity in attribute value
    …'../Shop/ItemList.asp?CATID=3320&WCWSC=3332&Ref=35140649:96195131');">Gift Bas…

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

  • Error Line 217, Column 5805: reference to entity "WCWSC" for which no system identifier could be generated
    …'../Shop/ItemList.asp?CATID=3320&WCWSC=3332&Ref=35140649:96195131');">Gift Bas…

    This is usually a cascading error caused by 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 217, Column 139: entity was defined here
    …fs[1]='../Shop/ItemList.asp?CATID=3320&WCWSC=3320&Ref=35140649:96195131';hrefs…
  • Warning Line 217, Column 5814: reference not terminated by REFC delimiter
    …ItemList.asp?CATID=3320&WCWSC=3332&Ref=35140649:96195131');">Gift Baskets</a><…

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

  • Warning Line 217, Column 5814: reference to external entity in attribute value
    …ItemList.asp?CATID=3320&WCWSC=3332&Ref=35140649:96195131');">Gift Baskets</a><…

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

  • Error Line 217, Column 5814: reference to entity "Ref" for which no system identifier could be generated
    …ItemList.asp?CATID=3320&WCWSC=3332&Ref=35140649:96195131');">Gift Baskets</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 122, Column 87: entity was defined here
    ….com/HBOnline/GiftList/Login.asp?GL=-1&Ref=35140649:96195131">My Gift List</a>…
  • Error Line 220, Column 393: required attribute "alt" not specified
    …  src="../images/Content/ID3054.jpg" /></a>          <ul>            <li><a hr…

    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 220, Column 564: cannot generate system identifier for general entity "CATID"
    …><a href="../Shop/Item.asp?InvID=4031&CATID=3320&WCWSC=3318&Ref=35140649:96195…

    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 220, Column 564: general entity "CATID" not defined and no default entity
    …><a href="../Shop/Item.asp?InvID=4031&CATID=3320&WCWSC=3318&Ref=35140649:96195…

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

  • Warning Line 220, Column 569: reference not terminated by REFC delimiter
    …ref="../Shop/Item.asp?InvID=4031&CATID=3320&WCWSC=3318&Ref=35140649:96195131">…

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

  • Warning Line 220, Column 569: reference to external entity in attribute value
    …ref="../Shop/Item.asp?InvID=4031&CATID=3320&WCWSC=3318&Ref=35140649:96195131">…

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

  • Error Line 220, Column 569: reference to entity "CATID" for which no system identifier could be generated
    …ref="../Shop/Item.asp?InvID=4031&CATID=3320&WCWSC=3318&Ref=35140649:96195131">…

    This is usually a cascading error caused by 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 220, Column 563: entity was defined here
    …i><a href="../Shop/Item.asp?InvID=4031&CATID=3320&WCWSC=3318&Ref=35140649:9619…
  • Warning Line 220, Column 580: reference not terminated by REFC delimiter
    …p/Item.asp?InvID=4031&CATID=3320&WCWSC=3318&Ref=35140649:96195131">Send a Hone…

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

  • Warning Line 220, Column 580: reference to external entity in attribute value
    …p/Item.asp?InvID=4031&CATID=3320&WCWSC=3318&Ref=35140649:96195131">Send a Hone…

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

  • Error Line 220, Column 580: reference to entity "WCWSC" for which no system identifier could be generated
    …p/Item.asp?InvID=4031&CATID=3320&WCWSC=3318&Ref=35140649:96195131">Send a Hone…

    This is usually a cascading error caused by 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 217, Column 139: entity was defined here
    …fs[1]='../Shop/ItemList.asp?CATID=3320&WCWSC=3320&Ref=35140649:96195131';hrefs…
  • Warning Line 220, Column 589: reference not terminated by REFC delimiter
    …p?InvID=4031&CATID=3320&WCWSC=3318&Ref=35140649:96195131">Send a HoneyBaked Ha…

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

  • Warning Line 220, Column 589: reference to external entity in attribute value
    …p?InvID=4031&CATID=3320&WCWSC=3318&Ref=35140649:96195131">Send a HoneyBaked Ha…

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

  • Error Line 220, Column 589: reference to entity "Ref" for which no system identifier could be generated
    …p?InvID=4031&CATID=3320&WCWSC=3318&Ref=35140649:96195131">Send a HoneyBaked Ha…

    This is usually a cascading error caused by 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 122, Column 87: entity was defined here
    ….com/HBOnline/GiftList/Login.asp?GL=-1&Ref=35140649:96195131">My Gift List</a>…
  • Error Line 220, Column 1067: required attribute "alt" not specified
    …  src="../images/Content/ID3055.jpg" /></a>          <ul>            <li><a hr…

    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 220, Column 1830: required attribute "alt" not specified
    …  src="../images/Content/ID3056.jpg" /></a>          <ul>               <li><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 220, Column 1914: reference not terminated by REFC delimiter
    …"../Shop/ItemList.asp?CATID=3335&WCWSC=3357&Ref=35140649:96195131">Customer Fa…

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

  • Warning Line 220, Column 1914: reference to external entity in attribute value
    …"../Shop/ItemList.asp?CATID=3335&WCWSC=3357&Ref=35140649:96195131">Customer Fa…

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

  • Error Line 220, Column 1914: reference to entity "WCWSC" for which no system identifier could be generated
    …"../Shop/ItemList.asp?CATID=3335&WCWSC=3357&Ref=35140649:96195131">Customer Fa…

    This is usually a cascading error caused by 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 217, Column 139: entity was defined here
    …fs[1]='../Shop/ItemList.asp?CATID=3320&WCWSC=3320&Ref=35140649:96195131';hrefs…
  • Warning Line 220, Column 1923: reference not terminated by REFC delimiter
    …ItemList.asp?CATID=3335&WCWSC=3357&Ref=35140649:96195131">Customer Favorites</…

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

  • Warning Line 220, Column 1923: reference to external entity in attribute value
    …ItemList.asp?CATID=3335&WCWSC=3357&Ref=35140649:96195131">Customer Favorites</…

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

  • Error Line 220, Column 1923: reference to entity "Ref" for which no system identifier could be generated
    …ItemList.asp?CATID=3335&WCWSC=3357&Ref=35140649:96195131">Customer Favorites</…

    This is usually a cascading error caused by 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 122, Column 87: entity was defined here
    ….com/HBOnline/GiftList/Login.asp?GL=-1&Ref=35140649:96195131">My Gift List</a>…
  • Error Line 280, Column 22: document type does not allow element "form" here; missing one of "th", "td" start-tag
    					 <form action="">

    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 281, Column 68: document type does not allow element "td" here
    …12px; width:276px; padding-left:16px;"><img src="../images/Content/label_signu…

    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 283, Column 36: document type does not allow element "td" here
    						<td style="padding-left:5px;"><input type="text" id="signup" name="signup…

    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 285, Column 10: document type does not allow element "td" here
    						<td><input type="image" src="../images/Content/btn_arrow.png" align="righ…

    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 292, Column 55: required attribute "alt" not specified
    							<img src="../images/Content/footer_about.png" />

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

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

  • Error Line 294, Column 86: required attribute "alt" not specified
    …le="line-height:14px;"><img src="../images/Content/dotBorder4x13px.png" /></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>.

  • Error Line 297, Column 61: required attribute "alt" not specified
    							<img src="../images/Content/footer_fundraising.png" />

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

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

  • Error Line 299, Column 86: required attribute "alt" not specified
    …le="line-height:14px;"><img src="../images/Content/dotBorder4x13px.png" /></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>.

  • Error Line 302, Column 62: required attribute "alt" not specified
    						 <img src="../images/Content/footer_storelocator.png" />

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

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

  • Warning Line 319, Column 104: reference not terminated by REFC delimiter
    …vacyPolicy/Index.asp?MIDS=560:-1:0&Ref=35140649:96195131">Privacy Policy</a></…

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

  • Warning Line 319, Column 104: reference to external entity in attribute value
    …vacyPolicy/Index.asp?MIDS=560:-1:0&Ref=35140649:96195131">Privacy Policy</a></…

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

  • Error Line 319, Column 104: reference to entity "Ref" for which no system identifier could be generated
    …vacyPolicy/Index.asp?MIDS=560:-1:0&Ref=35140649:96195131">Privacy Policy</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 122, Column 87: entity was defined here
    ….com/HBOnline/GiftList/Login.asp?GL=-1&Ref=35140649:96195131">My Gift List</a>…
  • Error Line 342, Column 7: end tag for "br" omitted, but OMITTAG NO was specified
      <br><br><br>

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

  • Info Line 342, Column 3: start tag was here
      <br><br><br>
  • Error Line 342, Column 11: end tag for "br" omitted, but OMITTAG NO was specified
      <br><br><br>

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

  • Info Line 342, Column 7: start tag was here
      <br><br><br>
  • Error Line 342, Column 15: end tag for "br" omitted, but OMITTAG NO was specified
      <br><br><br>

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

  • Info Line 342, Column 11: start tag was here
      <br><br><br>

Visitor Analysis

Daily Visitor
  • 257 visits

In Page Analysis