Ringtones from Phonezoo - it's easy to create and download FREE ringtones. Phonezoo also offers FREE games, and FREE cell phone wallpaper. ...

phonezoo.com
  • Domain Name
    phonezoo.com
  • Favicon
  • Google Page Rank
    4
  • Alexa Rank
    #43572
  • Page Size
    52.2 KB
  • Ip Address
    72.32.188.187
  • Heading
    H1: 0, H2: 0, H3: 0, H4: 3, H5: 0, H6: 0
  • Images
    2 GIF, 0 JPG, 3 PNG

Website Meta Analysis

  • Title
    Free Ringtones from Phonezoo - Make and Download Free Ringtones, Free Mobile Wallpaper and Play Free Games
  • Meta Keyword
    free ringtone, download ringtone, download free ringtone, create ringtone, make your own ringtone, free mobile ringtone, free music ringtone, free nokia ringtone, free sprint ringtone, free AT&T ringtone, free verizon ringtone, free cell phone ringtone, free t mobile ringtone, free motorola ringtone, free mp3 ringtone, free photos, free mobile wallpaper, free mobile photos, free pics, free mobile pics, free mobile wallpapers, free games, null
  • Meta Description
    Ringtones from Phonezoo - it's easy to create and download FREE ringtones. Phonezoo also offers FREE games, and FREE cell phone wallpaper.

Technical Analysis

  • Webserver
    Apache-Coyote/1.1
  • Ip Address
    72.32.188.187
  • Domain Age
    8 Years, 11 Months, 19 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • server: Apache-Coyote/1.1
  • expires: 0
  • pragma: no-cache
  • cache-control: nocache, no-store, must-revalidate, max-age=0, post-check=0, pre-check=0
  • content-type: text/html;charset=UTF-8
  • content-encoding: gzip
  • vary: Accept-Encoding
  • date: Sat, 21 Sep 2013 19:11:23 GMT
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Registrant:
Phonezoo Communications, Inc

Domain Name: PHONEZOO.COM

Name Servers:
NS.RACKSPACE.COM
NS2.RACKSPACE.COM

For complete domain details go to:
http://who.godaddy.com/whoischeck.aspx?Domain=PHONEZOO.COM

DNS Analysis


DNS servers
ns2.rackspace.com [65.61.188.4]
ns.rackspace.com [69.20.95.4]


DNS Records

Answer records
phonezoo.com NS  ns2.rackspace.com 86400s
phonezoo.com NS  ns.rackspace.com 86400s
phonezoo.com MX
preference: 10
exchange: smtp.secureserver.net
86400s
phonezoo.com MX
preference: 20
exchange: mailstore1.secureserver.net
86400s
phonezoo.com TXT v=spf1 mx ip4:72.32.188.187 a:mail.phonezoo.com a:mail4.phonezoo.com a:mail5.phonezoo.com a:mail9.phonezoo.com a:mail10.phonezoo.com a:mail11.phonezoo.com a:mail12.phonezoo.com a:mail13.phonezoo.com ?all 86400s
phonezoo.com A 72.32.188.187 86400s
phonezoo.com SOA
server: ns.rackspace.com.phonezoo.com
email: hostmaster@rackspace.com.phonezoo.com
serial: 1311660680
refresh: 86400
retry: 7200
expire: 604800
minimum ttl: 300
300s

Authority records

Additional records

IP 72.32.188.187 Analysis

  • Country Code
    US
  • Country Code3
    USA
  • Country Name
    United States
  • City
    Sunnyvale
  • Continent Code
    94085
  • Latitude
    408
  • Longitude
    807
  • #
    # Query terms are ambiguous. The query is assumed to be:
    # "n 72.32.188.187"
    #
    # Use "?" to get help.
    #

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

    Phonezoo Communications RSPC-122887488 (NET-72-32-188-184-1) 72.32.188.184 - 72.32.188.191
    Rackspace Hosting RSCP-NET-4 (NET-72-32-0-0-1) 72.32.0.0 - 72.32.255.255


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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 229 Errors
  • 293 Warnings
Ratio Text/Html
  • 0.6231452895500047
Message Error
  • Warning Line 10, Column 225: cannot generate system identifier for general entity "T"
    …ngtone, free sprint ringtone, free AT&T ringtone, free verizon ringtone, free …

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

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

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

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

  • Error Line 10, Column 225: general entity "T" not defined and no default entity
    …ngtone, free sprint ringtone, free AT&T ringtone, free verizon ringtone, free …

    This is usually a cascading error caused by 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 10, Column 226: reference not terminated by REFC delimiter
    …gtone, free sprint ringtone, free AT&T ringtone, free verizon ringtone, free c…

    If you meant to include an entity that starts with "&", then you should terminate it 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 10, Column 226: reference to external entity in attribute value
    …gtone, free sprint ringtone, free AT&T ringtone, free verizon ringtone, free c…

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

  • Error Line 10, Column 226: reference to entity "T" for which no system identifier could be generated
    …gtone, free sprint ringtone, free AT&T ringtone, free verizon ringtone, free c…

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

  • Info Line 10, Column 224: entity was defined here
    …ingtone, free sprint ringtone, free AT&T ringtone, free verizon ringtone, free…
  • Error Line 29, Column 30: required attribute "type" not specified
    <script language="JavaScript">GA_googleAddAttr("lcnt", "null");</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 30, Column 30: required attribute "type" not specified
    <script language="JavaScript">GA_googleAddAttr("gender", "null");</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 31, Column 30: required attribute "type" not specified
    <script language="JavaScript">GA_googleAddAttr("familyFltr", "on");</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 61, Column 179: required attribute "alt" not specified
    …g/logo.gif" title="Free ringtones, wallpapers, games from Phonezoo"/></a></div>

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

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

  • Error Line 78, Column 104: there is no attribute "onKeyDown"
    …ssword" onfocus="select();" onKeyDown="execOnClickOnEnterKey(event,'signin');"…

    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 79, Column 19: there is no attribute "tabindex"
    <td><div tabindex="1002" id="signin" 	   onclick="signin();" ><b>Sign In</b></d…

    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 84, Column 28: required attribute "alt" not specified
    <img src="img/fblogin.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 113, Column 24: character "&" is the first character of a delimiter but occurred as data
    if(jQuery.browser.msie &&  jQuery.browser.version < 7.0) {

    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 113, Column 25: character "&" is the first character of a delimiter but occurred as data
    if(jQuery.browser.msie &&  jQuery.browser.version < 7.0) {

    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 113, Column 51: character "<" is the first character of a delimiter but occurred as data
    if(jQuery.browser.msie &&  jQuery.browser.version < 7.0) {

    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 114, Column 28: an attribute value must be a literal unless it contains only name characters
    document.write("<div class=\"maintenance\">Our site is not optimized for IE6. P…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 114, Column 43: document type does not allow element "div" here
    …ment.write("<div class=\"maintenance\">Our site is not optimized for IE6. Plea…

    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 126, Column 126: document type does not allow element "form" here; assuming missing "li" start-tag
    …onid=81E6E72BC0CE32F95D340D8A4E48BB8A"><input type="hidden" id="page" name="pa…
  • Error Line 129, Column 22: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    <li class="topsearch">

    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 132, Column 22: value of attribute "selected" cannot be "yes"; must be one of "selected"
    <option selected="yes" value="RT">Ringtones</option>

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

  • Error Line 139, Column 12: end tag for "li" omitted, but OMITTAG NO was specified
    </form></ul>

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

  • Info Line 126, Column 1: start tag was here
    <form name="SearchForm" id="searchRingtonesForm" method="get" action="/search.d…
  • Warning Line 143, Column 26: character "&" is the first character of a delimiter but occurred as data
    if( (jQuery.browser.msie &&  jQuery.browser.version < 7.0) || jQuery.browser.sa…

    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 143, Column 27: character "&" is the first character of a delimiter but occurred as data
    if( (jQuery.browser.msie &&  jQuery.browser.version < 7.0) || jQuery.browser.sa…

    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 143, Column 53: character "<" is the first character of a delimiter but occurred as data
    …jQuery.browser.msie &&  jQuery.browser.version < 7.0) || jQuery.browser.safari)

    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 156, Column 26: character "&" is the first character of a delimiter but occurred as data
    if( (jQuery.browser.msie &&  jQuery.browser.version < 7.0) || jQuery.browser.sa…

    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 156, Column 27: character "&" is the first character of a delimiter but occurred as data
    if( (jQuery.browser.msie &&  jQuery.browser.version < 7.0) || jQuery.browser.sa…

    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 156, Column 53: character "<" is the first character of a delimiter but occurred as data
    …jQuery.browser.msie &&  jQuery.browser.version < 7.0) || jQuery.browser.safari)

    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 170, Column 30: required attribute "type" not specified
    <script language="JavaScript">GA_googleAddAttr('pageType', 'home');</script>

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

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

  • Warning Line 183, Column 200: cannot generate system identifier for general entity "css"
    …ight&amp;connections=10&amp;stream=false&amp;header=false&amp;height=255&css=" 

    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 183, Column 200: general entity "css" not defined and no default entity
    …ight&amp;connections=10&amp;stream=false&amp;header=false&amp;height=255&css=" 

    This is usually a cascading error caused by 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 183, Column 203: reference not terminated by REFC delimiter
    …ight&amp;connections=10&amp;stream=false&amp;header=false&amp;height=255&css=" 

    If you meant to include an entity that starts with "&", then you should terminate it 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 183, Column 203: reference to external entity in attribute value
    …ight&amp;connections=10&amp;stream=false&amp;header=false&amp;height=255&css=" 

    This is generally the sign of an ampersand that 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 183, Column 203: reference to entity "css" for which no system identifier could be generated
    …ight&amp;connections=10&amp;stream=false&amp;header=false&amp;height=255&css=" 

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

  • Info Line 183, Column 199: entity was defined here
    …ight&amp;connections=10&amp;stream=false&amp;header=false&amp;height=255&css=" 
  • Error Line 184, Column 84: there is no attribute "allowTransparency"
    …:hidden; width:292px; height:255px;" allowTransparency="true"></iframe>        

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

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

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

  • Error Line 190, Column 7: required attribute "type" not specified
    <style>

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

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

  • Error Line 190, Column 7: document type does not allow element "style" here
    <style>

    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 205, Column 30: required attribute "alt" not specified
    <img src="img/icon_send.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 216, Column 31: required attribute "alt" not specified
    <img src="img/icon_share.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 226, Column 35: required attribute "alt" not specified
    <img src="img/icon_lightbulb.gif"/>

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

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

  • Error Line 237, Column 89: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …81E6E72BC0CE32F95D340D8A4E48BB8A"><div class="register">Sign up</div></a></div>

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

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

  • Warning Line 286, Column 80: cannot generate system identifier for general entity "sort"
    ….do;jsessionid=81E6E72BC0CE32F95D340D8A4E48BB8A?mode=" + mode + "&sort=" + sort

    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 286, Column 80: general entity "sort" not defined and no default entity
    ….do;jsessionid=81E6E72BC0CE32F95D340D8A4E48BB8A?mode=" + mode + "&sort=" + sort

    This is usually a cascading error caused by 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 286, Column 84: reference not terminated by REFC delimiter
    ….do;jsessionid=81E6E72BC0CE32F95D340D8A4E48BB8A?mode=" + mode + "&sort=" + sort

    If you meant to include an entity that starts with "&", then you should terminate it 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 286, Column 84: reference to entity "sort" for which no system identifier could be generated
    ….do;jsessionid=81E6E72BC0CE32F95D340D8A4E48BB8A?mode=" + mode + "&sort=" + sort

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

  • Info Line 286, Column 79: entity was defined here
    ….do;jsessionid=81E6E72BC0CE32F95D340D8A4E48BB8A?mode=" + mode + "&sort=" + sort
  • Warning Line 287, Column 5: cannot generate system identifier for general entity "value"
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";

    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 287, Column 5: general entity "value" not defined and no default entity
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";

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

  • Warning Line 287, Column 10: reference not terminated by REFC delimiter
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";

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

  • Error Line 287, Column 10: reference to entity "value" for which no system identifier could be generated
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";

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

  • Info Line 287, Column 4: entity was defined here
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";
  • Warning Line 287, Column 24: cannot generate system identifier for general entity "page"
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";

    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 287, Column 24: general entity "page" not defined and no default entity
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";

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

  • Warning Line 287, Column 28: reference not terminated by REFC delimiter
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";

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

  • Error Line 287, Column 28: reference to entity "page" for which no system identifier could be generated
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";

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

  • Info Line 287, Column 23: entity was defined here
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";
  • Warning Line 287, Column 31: cannot generate system identifier for general entity "photoSort"
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";

    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 287, Column 31: general entity "photoSort" not defined and no default entity
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";

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

  • Warning Line 287, Column 40: reference not terminated by REFC delimiter
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";

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

  • Error Line 287, Column 40: reference to entity "photoSort" for which no system identifier could be generated
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";

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

  • Info Line 287, Column 30: entity was defined here
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";
  • Warning Line 287, Column 43: cannot generate system identifier for general entity "photoPage"
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";

    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 287, Column 43: general entity "photoPage" not defined and no default entity
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";

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

  • Warning Line 287, Column 52: reference not terminated by REFC delimiter
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";

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

  • Error Line 287, Column 52: reference to entity "photoPage" for which no system identifier could be generated
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";

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

  • Info Line 287, Column 42: entity was defined here
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";
  • Warning Line 324, Column 73: reference not terminated by REFC delimiter
    …home.do;jsessionid=81E6E72BC0CE32F95D340D8A4E48BB8A?mode=0&sort=3&page=" + page

    If you meant to include an entity that starts with "&", then you should terminate it 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 324, Column 73: reference to entity "sort" for which no system identifier could be generated
    …home.do;jsessionid=81E6E72BC0CE32F95D340D8A4E48BB8A?mode=0&sort=3&page=" + page

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

  • Info Line 286, Column 79: entity was defined here
    ….do;jsessionid=81E6E72BC0CE32F95D340D8A4E48BB8A?mode=" + mode + "&sort=" + sort
  • Warning Line 324, Column 80: reference not terminated by REFC delimiter
    …home.do;jsessionid=81E6E72BC0CE32F95D340D8A4E48BB8A?mode=0&sort=3&page=" + page

    If you meant to include an entity that starts with "&", then you should terminate it 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 324, Column 80: reference to entity "page" for which no system identifier could be generated
    …home.do;jsessionid=81E6E72BC0CE32F95D340D8A4E48BB8A?mode=0&sort=3&page=" + page

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

  • Info Line 287, Column 23: entity was defined here
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";
  • Warning Line 325, Column 10: reference not terminated by REFC delimiter
    + "&value=" + value + "&photoSort=3&photoPage=0";

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

  • Error Line 325, Column 10: reference to entity "value" for which no system identifier could be generated
    + "&value=" + value + "&photoSort=3&photoPage=0";

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

  • Info Line 287, Column 4: entity was defined here
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";
  • Warning Line 325, Column 34: reference not terminated by REFC delimiter
    + "&value=" + value + "&photoSort=3&photoPage=0";

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

  • Error Line 325, Column 34: reference to entity "photoSort" for which no system identifier could be generated
    + "&value=" + value + "&photoSort=3&photoPage=0";

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

  • Info Line 287, Column 30: entity was defined here
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";
  • Warning Line 325, Column 46: reference not terminated by REFC delimiter
    + "&value=" + value + "&photoSort=3&photoPage=0";

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

  • Error Line 325, Column 46: reference to entity "photoPage" for which no system identifier could be generated
    + "&value=" + value + "&photoSort=3&photoPage=0";

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

  • Info Line 287, Column 42: entity was defined here
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";
  • Error Line 335, Column 14: there is no attribute "type"
    <SCRIPT type="text/javascript">

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

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

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

  • Error Line 335, Column 31: element "SCRIPT" undefined
    <SCRIPT type="text/javascript">

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 345, Column 190: document type does not allow element "a" here; missing one of "dt", "dd" start-tag
    …-contentname" title="Your Momma's Calling Back">Your Momma's Callin...</a><br/>

    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 345, Column 221: document type does not allow element "br" here; missing one of "dt", "dd" start-tag
    …-contentname" title="Your Momma's Calling Back">Your Momma's Callin...</a><br/>

    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 352, Column 31: element "SCRIPT" undefined
    <SCRIPT type="text/javascript">

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 362, Column 162: document type does not allow element "a" here; missing one of "dt", "dd" start-tag
    …5D340D8A4E48BB8A" class="pz-contentname" title="Baby Laugh">Baby Laugh</a><br/>

    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 362, Column 181: document type does not allow element "br" here; missing one of "dt", "dd" start-tag
    …5D340D8A4E48BB8A" class="pz-contentname" title="Baby Laugh">Baby Laugh</a><br/>

    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 369, Column 31: element "SCRIPT" undefined
    <SCRIPT type="text/javascript">

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 379, Column 179: document type does not allow element "a" here; missing one of "dt", "dd" start-tag
    …48BB8A" class="pz-contentname" title="Bomchickawahwah">Bomchickawahwah</a><br/>

    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 379, Column 203: document type does not allow element "br" here; missing one of "dt", "dd" start-tag
    …48BB8A" class="pz-contentname" title="Bomchickawahwah">Bomchickawahwah</a><br/>

    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 386, Column 31: element "SCRIPT" undefined
    <SCRIPT type="text/javascript">

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 396, Column 218: document type does not allow element "a" here; missing one of "dt", "dd" start-tag
    …me" title="I want a hippopotamus for Christmas">I want a hippopotam...</a><br/>

    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 396, Column 249: document type does not allow element "br" here; missing one of "dt", "dd" start-tag
    …me" title="I want a hippopotamus for Christmas">I want a hippopotam...</a><br/>

    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 403, Column 31: element "SCRIPT" undefined
    <SCRIPT type="text/javascript">

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 413, Column 146: document type does not allow element "a" here; missing one of "dt", "dd" start-tag
    …CE32F95D340D8A4E48BB8A" class="pz-contentname" title="Message">Message</a><br/>

    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 413, Column 162: document type does not allow element "br" here; missing one of "dt", "dd" start-tag
    …CE32F95D340D8A4E48BB8A" class="pz-contentname" title="Message">Message</a><br/>

    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 420, Column 31: element "SCRIPT" undefined
    <SCRIPT type="text/javascript">

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 430, Column 190: document type does not allow element "a" here; missing one of "dt", "dd" start-tag
    …class="pz-contentname" title="Candy Mountain Song">Candy Mountain Song</a><br/>

    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 430, Column 218: document type does not allow element "br" here; missing one of "dt", "dd" start-tag
    …class="pz-contentname" title="Candy Mountain Song">Candy Mountain Song</a><br/>

    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 437, Column 31: element "SCRIPT" undefined
    <SCRIPT type="text/javascript">

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 447, Column 205: document type does not allow element "a" here; missing one of "dt", "dd" start-tag
    …entname" title="Dance of the Sugar-Plum Fairy ">Dance of the Sugar-...</a><br/>

    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 447, Column 236: document type does not allow element "br" here; missing one of "dt", "dd" start-tag
    …entname" title="Dance of the Sugar-Plum Fairy ">Dance of the Sugar-...</a><br/>

    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 454, Column 31: element "SCRIPT" undefined
    <SCRIPT type="text/javascript">

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 464, Column 159: document type does not allow element "a" here; missing one of "dt", "dd" start-tag
    …8A4E48BB8A" class="pz-contentname" title="the beer song">the beer song</a><br/>

    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 464, Column 181: document type does not allow element "br" here; missing one of "dt", "dd" start-tag
    …8A4E48BB8A" class="pz-contentname" title="the beer song">the beer song</a><br/>

    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 471, Column 31: element "SCRIPT" undefined
    <SCRIPT type="text/javascript">

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 481, Column 168: document type does not allow element "a" here; missing one of "dt", "dd" start-tag
    …4E48BB8A" class="pz-contentname" title="Mom - Suspense">Mom - Suspense</a><br/>

    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 481, Column 191: document type does not allow element "br" here; missing one of "dt", "dd" start-tag
    …4E48BB8A" class="pz-contentname" title="Mom - Suspense">Mom - Suspense</a><br/>

    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 488, Column 31: element "SCRIPT" undefined
    <SCRIPT type="text/javascript">

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 498, Column 189: document type does not allow element "a" here; missing one of "dt", "dd" start-tag
    …z-contentname" title="You Are My Sunshine ring">You Are My Sunshine...</a><br/>

    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 498, Column 220: document type does not allow element "br" here; missing one of "dt", "dd" start-tag
    …z-contentname" title="You Are My Sunshine ring">You Are My Sunshine...</a><br/>

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

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

  • Warning Line 514, Column 84: reference not terminated by REFC delimiter
    …do;jsessionid=81E6E72BC0CE32F95D340D8A4E48BB8A?mode=" + mode + "&sort=3&page=0"

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

  • Error Line 514, Column 84: reference to entity "sort" for which no system identifier could be generated
    …do;jsessionid=81E6E72BC0CE32F95D340D8A4E48BB8A?mode=" + mode + "&sort=3&page=0"

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

  • Info Line 286, Column 79: entity was defined here
    ….do;jsessionid=81E6E72BC0CE32F95D340D8A4E48BB8A?mode=" + mode + "&sort=" + sort
  • Warning Line 514, Column 91: reference not terminated by REFC delimiter
    …do;jsessionid=81E6E72BC0CE32F95D340D8A4E48BB8A?mode=" + mode + "&sort=3&page=0"

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

  • Error Line 514, Column 91: reference to entity "page" for which no system identifier could be generated
    …do;jsessionid=81E6E72BC0CE32F95D340D8A4E48BB8A?mode=" + mode + "&sort=3&page=0"

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

  • Info Line 287, Column 23: entity was defined here
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";
  • Warning Line 515, Column 10: reference not terminated by REFC delimiter
    + "&value=" + value+ "&photoSort=" + photoSort+ "&photoPage=" + photoPage;

    If you meant to include an entity that starts with "&", then you should terminate it 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 515, Column 10: reference to entity "value" for which no system identifier could be generated
    + "&value=" + value+ "&photoSort=" + photoSort+ "&photoPage=" + photoPage;

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

  • Info Line 287, Column 4: entity was defined here
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";
  • Warning Line 515, Column 33: reference not terminated by REFC delimiter
    + "&value=" + value+ "&photoSort=" + photoSort+ "&photoPage=" + photoPage;

    If you meant to include an entity that starts with "&", then you should terminate it 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 515, Column 33: reference to entity "photoSort" for which no system identifier could be generated
    + "&value=" + value+ "&photoSort=" + photoSort+ "&photoPage=" + photoPage;

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

  • Info Line 287, Column 30: entity was defined here
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";
  • Warning Line 515, Column 60: reference not terminated by REFC delimiter
    + "&value=" + value+ "&photoSort=" + photoSort+ "&photoPage=" + photoPage;

    If you meant to include an entity that starts with "&", then you should terminate it 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 515, Column 60: reference to entity "photoPage" for which no system identifier could be generated
    + "&value=" + value+ "&photoSort=" + photoSort+ "&photoPage=" + photoPage;

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

  • Info Line 287, Column 42: entity was defined here
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";
  • Error Line 529, Column 11: ID "ringtonesform" already defined
    <form id="ringtonesform" name="ringtonesform" method="post" action="">

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 304, Column 11: ID "ringtonesform" first defined here
    <form id="ringtonesform" name="ringtonesform" method="post" action="">
  • Warning Line 550, Column 77: reference not terminated by REFC delimiter
    var sURI = "/home.do;jsessionid=81E6E72BC0CE32F95D340D8A4E48BB8A?mode=0&sort=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 550, Column 77: reference to entity "sort" for which no system identifier could be generated
    var sURI = "/home.do;jsessionid=81E6E72BC0CE32F95D340D8A4E48BB8A?mode=0&sort=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 286, Column 79: entity was defined here
    ….do;jsessionid=81E6E72BC0CE32F95D340D8A4E48BB8A?mode=" + mode + "&sort=" + sort
  • Warning Line 551, Column 9: reference not terminated by REFC delimiter
    + "&page=0&value=" + value + "&photoSort=3&photoPage=" + photoPage;

    If you meant to include an entity that starts with "&", then you should terminate it 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 551, Column 9: reference to entity "page" for which no system identifier could be generated
    + "&page=0&value=" + value + "&photoSort=3&photoPage=" + photoPage;

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

  • Info Line 287, Column 23: entity was defined here
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";
  • Warning Line 551, Column 17: reference not terminated by REFC delimiter
    + "&page=0&value=" + value + "&photoSort=3&photoPage=" + photoPage;

    If you meant to include an entity that starts with "&", then you should terminate it 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 551, Column 17: reference to entity "value" for which no system identifier could be generated
    + "&page=0&value=" + value + "&photoSort=3&photoPage=" + photoPage;

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

  • Info Line 287, Column 4: entity was defined here
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";
  • Warning Line 551, Column 41: reference not terminated by REFC delimiter
    + "&page=0&value=" + value + "&photoSort=3&photoPage=" + photoPage;

    If you meant to include an entity that starts with "&", then you should terminate it 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 551, Column 41: reference to entity "photoSort" for which no system identifier could be generated
    + "&page=0&value=" + value + "&photoSort=3&photoPage=" + photoPage;

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

  • Info Line 287, Column 30: entity was defined here
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";
  • Warning Line 551, Column 53: reference not terminated by REFC delimiter
    + "&page=0&value=" + value + "&photoSort=3&photoPage=" + photoPage;

    If you meant to include an entity that starts with "&", then you should terminate it 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 551, Column 53: reference to entity "photoPage" for which no system identifier could be generated
    + "&page=0&value=" + value + "&photoSort=3&photoPage=" + photoPage;

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

  • Info Line 287, Column 42: entity was defined here
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";
  • Error Line 557, Column 10: ID "ringtonecontainer" already defined
    <div id="ringtonecontainer">

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 331, Column 10: ID "ringtonecontainer" first defined here
    <div id="ringtonecontainer">
  • Error Line 571, Column 31: element "SCRIPT" undefined
    <SCRIPT type="text/javascript">

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 592, Column 31: element "SCRIPT" undefined
    <SCRIPT type="text/javascript">

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 613, Column 31: element "SCRIPT" undefined
    <SCRIPT type="text/javascript">

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 635, Column 31: element "SCRIPT" undefined
    <SCRIPT type="text/javascript">

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 656, Column 31: element "SCRIPT" undefined
    <SCRIPT type="text/javascript">

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 677, Column 31: element "SCRIPT" undefined
    <SCRIPT type="text/javascript">

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 699, Column 31: element "SCRIPT" undefined
    <SCRIPT type="text/javascript">

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 720, Column 31: element "SCRIPT" undefined
    <SCRIPT type="text/javascript">

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 741, Column 31: element "SCRIPT" undefined
    <SCRIPT type="text/javascript">

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

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

    Most likely, you nested tags and closed them in the wrong order. For example <p><em>...</p> is not acceptable, as <em> must be closed before <p>. Acceptable nesting is: <p><em>...</em></p>

    Another possibility is that you used an element which requires a child element that you did not include. Hence the parent element is "not finished", not complete. For instance, in HTML the <head> element must contain a <title> child element, lists require appropriate list items (<ul> and <ol> require <li>; <dl> requires <dt> and <dd>), and so on.

  • Error Line 761, Column 10: ID "ringtonepagination" already defined
    <div id="ringtonepagination">                          	  	

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 504, Column 10: ID "ringtonepagination" first defined here
    <div id="ringtonepagination">    
  • Error Line 762, Column 10: ID "top" already defined
    <div id="top" title="Top" class="top_disabled"></div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 505, Column 10: ID "top" first defined here
    <div id="top" title="Top" class="top_disabled"></div>
  • Error Line 763, Column 10: ID "previous" already defined
    <div id="previous" title="Previous" class="previous_disabled"></div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 507, Column 10: ID "previous" first defined here
    <div id="previous" title="Previous" class="previous_disabled"></div>
  • Error Line 764, Column 10: ID "next" already defined
    <div id="next" title="Next" class="next" onclick="return photoListPagingFns.get…

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 506, Column 10: ID "next" first defined here
    <div id="next" title="Next" class="next" onclick="return getRingtonePage(0 + 1)…
  • Warning Line 778, Column 97: reference not terminated by REFC delimiter
    …2BC0CE32F95D340D8A4E48BB8A?mode=9&sort=&photoSort=&value=Everyday+Sounds">Ever…

    If you meant to include an entity that starts with "&", then you should terminate it 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 778, Column 97: reference to external entity in attribute value
    …2BC0CE32F95D340D8A4E48BB8A?mode=9&sort=&photoSort=&value=Everyday+Sounds">Ever…

    This is generally the sign of an ampersand that 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 778, Column 97: reference to entity "sort" for which no system identifier could be generated
    …2BC0CE32F95D340D8A4E48BB8A?mode=9&sort=&photoSort=&value=Everyday+Sounds">Ever…

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

  • Info Line 286, Column 79: entity was defined here
    ….do;jsessionid=81E6E72BC0CE32F95D340D8A4E48BB8A?mode=" + mode + "&sort=" + sort
  • Warning Line 778, Column 108: reference not terminated by REFC delimiter
    …D340D8A4E48BB8A?mode=9&sort=&photoSort=&value=Everyday+Sounds">Everyday Sounds…

    If you meant to include an entity that starts with "&", then you should terminate it 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 778, Column 108: reference to external entity in attribute value
    …D340D8A4E48BB8A?mode=9&sort=&photoSort=&value=Everyday+Sounds">Everyday Sounds…

    This is generally the sign of an ampersand that 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 778, Column 108: reference to entity "photoSort" for which no system identifier could be generated
    …D340D8A4E48BB8A?mode=9&sort=&photoSort=&value=Everyday+Sounds">Everyday Sounds…

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

  • Info Line 287, Column 30: entity was defined here
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";
  • Warning Line 778, Column 115: reference not terminated by REFC delimiter
    …4E48BB8A?mode=9&sort=&photoSort=&value=Everyday+Sounds">Everyday Sounds</a></l…

    If you meant to include an entity that starts with "&", then you should terminate it 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 778, Column 115: reference to external entity in attribute value
    …4E48BB8A?mode=9&sort=&photoSort=&value=Everyday+Sounds">Everyday Sounds</a></l…

    This is generally the sign of an ampersand that 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 778, Column 115: reference to entity "value" for which no system identifier could be generated
    …4E48BB8A?mode=9&sort=&photoSort=&value=Everyday+Sounds">Everyday Sounds</a></l…

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

  • Info Line 287, Column 4: entity was defined here
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";
  • Warning Line 779, Column 97: reference not terminated by REFC delimiter
    …2BC0CE32F95D340D8A4E48BB8A?mode=9&sort=&photoSort=&value=Holiday">Holiday</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 779, Column 97: reference to external entity in attribute value
    …2BC0CE32F95D340D8A4E48BB8A?mode=9&sort=&photoSort=&value=Holiday">Holiday</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 779, Column 97: reference to entity "sort" for which no system identifier could be generated
    …2BC0CE32F95D340D8A4E48BB8A?mode=9&sort=&photoSort=&value=Holiday">Holiday</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 286, Column 79: entity was defined here
    ….do;jsessionid=81E6E72BC0CE32F95D340D8A4E48BB8A?mode=" + mode + "&sort=" + sort
  • Warning Line 779, Column 108: reference not terminated by REFC delimiter
    …0CE32F95D340D8A4E48BB8A?mode=9&sort=&photoSort=&value=Holiday">Holiday</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 779, Column 108: reference to external entity in attribute value
    …0CE32F95D340D8A4E48BB8A?mode=9&sort=&photoSort=&value=Holiday">Holiday</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 779, Column 108: reference to entity "photoSort" for which no system identifier could be generated
    …0CE32F95D340D8A4E48BB8A?mode=9&sort=&photoSort=&value=Holiday">Holiday</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 287, Column 30: entity was defined here
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";
  • Warning Line 779, Column 115: reference not terminated by REFC delimiter
    …0CE32F95D340D8A4E48BB8A?mode=9&sort=&photoSort=&value=Holiday">Holiday</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 779, Column 115: reference to external entity in attribute value
    …0CE32F95D340D8A4E48BB8A?mode=9&sort=&photoSort=&value=Holiday">Holiday</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 779, Column 115: reference to entity "value" for which no system identifier could be generated
    …0CE32F95D340D8A4E48BB8A?mode=9&sort=&photoSort=&value=Holiday">Holiday</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 287, Column 4: entity was defined here
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";
  • Warning Line 780, Column 97: reference not terminated by REFC delimiter
    …72BC0CE32F95D340D8A4E48BB8A?mode=9&sort=&photoSort=&value=Humor">Humor</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 780, Column 97: reference to external entity in attribute value
    …72BC0CE32F95D340D8A4E48BB8A?mode=9&sort=&photoSort=&value=Humor">Humor</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 780, Column 97: reference to entity "sort" for which no system identifier could be generated
    …72BC0CE32F95D340D8A4E48BB8A?mode=9&sort=&photoSort=&value=Humor">Humor</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 286, Column 79: entity was defined here
    ….do;jsessionid=81E6E72BC0CE32F95D340D8A4E48BB8A?mode=" + mode + "&sort=" + sort
  • Warning Line 780, Column 108: reference not terminated by REFC delimiter
    …72BC0CE32F95D340D8A4E48BB8A?mode=9&sort=&photoSort=&value=Humor">Humor</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 780, Column 108: reference to external entity in attribute value
    …72BC0CE32F95D340D8A4E48BB8A?mode=9&sort=&photoSort=&value=Humor">Humor</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 780, Column 108: reference to entity "photoSort" for which no system identifier could be generated
    …72BC0CE32F95D340D8A4E48BB8A?mode=9&sort=&photoSort=&value=Humor">Humor</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 287, Column 30: entity was defined here
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";
  • Warning Line 780, Column 115: reference not terminated by REFC delimiter
    …72BC0CE32F95D340D8A4E48BB8A?mode=9&sort=&photoSort=&value=Humor">Humor</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 780, Column 115: reference to external entity in attribute value
    …72BC0CE32F95D340D8A4E48BB8A?mode=9&sort=&photoSort=&value=Humor">Humor</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 780, Column 115: reference to entity "value" for which no system identifier could be generated
    …72BC0CE32F95D340D8A4E48BB8A?mode=9&sort=&photoSort=&value=Humor">Humor</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 287, Column 4: entity was defined here
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";
  • Warning Line 781, Column 97: reference not terminated by REFC delimiter
    …2BC0CE32F95D340D8A4E48BB8A?mode=9&sort=&photoSort=&value=Movies+%26+TV">Movies…

    If you meant to include an entity that starts with "&", then you should terminate it 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 781, Column 97: reference to external entity in attribute value
    …2BC0CE32F95D340D8A4E48BB8A?mode=9&sort=&photoSort=&value=Movies+%26+TV">Movies…

    This is generally the sign of an ampersand that 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 781, Column 97: reference to entity "sort" for which no system identifier could be generated
    …2BC0CE32F95D340D8A4E48BB8A?mode=9&sort=&photoSort=&value=Movies+%26+TV">Movies…

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

  • Info Line 286, Column 79: entity was defined here
    ….do;jsessionid=81E6E72BC0CE32F95D340D8A4E48BB8A?mode=" + mode + "&sort=" + sort
  • Warning Line 781, Column 108: reference not terminated by REFC delimiter
    …D340D8A4E48BB8A?mode=9&sort=&photoSort=&value=Movies+%26+TV">Movies & TV</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 781, Column 108: reference to external entity in attribute value
    …D340D8A4E48BB8A?mode=9&sort=&photoSort=&value=Movies+%26+TV">Movies & TV</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 781, Column 108: reference to entity "photoSort" for which no system identifier could be generated
    …D340D8A4E48BB8A?mode=9&sort=&photoSort=&value=Movies+%26+TV">Movies & TV</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 287, Column 30: entity was defined here
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";
  • Warning Line 781, Column 115: reference not terminated by REFC delimiter
    …40D8A4E48BB8A?mode=9&sort=&photoSort=&value=Movies+%26+TV">Movies & TV</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 781, Column 115: reference to external entity in attribute value
    …40D8A4E48BB8A?mode=9&sort=&photoSort=&value=Movies+%26+TV">Movies & TV</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 781, Column 115: reference to entity "value" for which no system identifier could be generated
    …40D8A4E48BB8A?mode=9&sort=&photoSort=&value=Movies+%26+TV">Movies & TV</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 287, Column 4: entity was defined here
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";
  • Warning Line 781, Column 138: character "&" is the first character of a delimiter but occurred as data
    …40D8A4E48BB8A?mode=9&sort=&photoSort=&value=Movies+%26+TV">Movies & TV</a></li>

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 782, Column 97: reference not terminated by REFC delimiter
    …72BC0CE32F95D340D8A4E48BB8A?mode=9&sort=&photoSort=&value=Music">Music</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 782, Column 97: reference to external entity in attribute value
    …72BC0CE32F95D340D8A4E48BB8A?mode=9&sort=&photoSort=&value=Music">Music</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 782, Column 97: reference to entity "sort" for which no system identifier could be generated
    …72BC0CE32F95D340D8A4E48BB8A?mode=9&sort=&photoSort=&value=Music">Music</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 286, Column 79: entity was defined here
    ….do;jsessionid=81E6E72BC0CE32F95D340D8A4E48BB8A?mode=" + mode + "&sort=" + sort
  • Warning Line 782, Column 108: reference not terminated by REFC delimiter
    …72BC0CE32F95D340D8A4E48BB8A?mode=9&sort=&photoSort=&value=Music">Music</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 782, Column 108: reference to external entity in attribute value
    …72BC0CE32F95D340D8A4E48BB8A?mode=9&sort=&photoSort=&value=Music">Music</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 782, Column 108: reference to entity "photoSort" for which no system identifier could be generated
    …72BC0CE32F95D340D8A4E48BB8A?mode=9&sort=&photoSort=&value=Music">Music</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 287, Column 30: entity was defined here
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";
  • Warning Line 782, Column 115: reference not terminated by REFC delimiter
    …72BC0CE32F95D340D8A4E48BB8A?mode=9&sort=&photoSort=&value=Music">Music</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 782, Column 115: reference to external entity in attribute value
    …72BC0CE32F95D340D8A4E48BB8A?mode=9&sort=&photoSort=&value=Music">Music</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 782, Column 115: reference to entity "value" for which no system identifier could be generated
    …72BC0CE32F95D340D8A4E48BB8A?mode=9&sort=&photoSort=&value=Music">Music</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 287, Column 4: entity was defined here
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";
  • Warning Line 783, Column 97: reference not terminated by REFC delimiter
    …2BC0CE32F95D340D8A4E48BB8A?mode=9&sort=&photoSort=&value=People">People</a></l…

    If you meant to include an entity that starts with "&", then you should terminate it 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 783, Column 97: reference to external entity in attribute value
    …2BC0CE32F95D340D8A4E48BB8A?mode=9&sort=&photoSort=&value=People">People</a></l…

    This is generally the sign of an ampersand that 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 783, Column 97: reference to entity "sort" for which no system identifier could be generated
    …2BC0CE32F95D340D8A4E48BB8A?mode=9&sort=&photoSort=&value=People">People</a></l…

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

  • Info Line 286, Column 79: entity was defined here
    ….do;jsessionid=81E6E72BC0CE32F95D340D8A4E48BB8A?mode=" + mode + "&sort=" + sort
  • Warning Line 783, Column 108: reference not terminated by REFC delimiter
    …BC0CE32F95D340D8A4E48BB8A?mode=9&sort=&photoSort=&value=People">People</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 783, Column 108: reference to external entity in attribute value
    …BC0CE32F95D340D8A4E48BB8A?mode=9&sort=&photoSort=&value=People">People</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 783, Column 108: reference to entity "photoSort" for which no system identifier could be generated
    …BC0CE32F95D340D8A4E48BB8A?mode=9&sort=&photoSort=&value=People">People</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 287, Column 30: entity was defined here
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";
  • Warning Line 783, Column 115: reference not terminated by REFC delimiter
    …BC0CE32F95D340D8A4E48BB8A?mode=9&sort=&photoSort=&value=People">People</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 783, Column 115: reference to external entity in attribute value
    …BC0CE32F95D340D8A4E48BB8A?mode=9&sort=&photoSort=&value=People">People</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 783, Column 115: reference to entity "value" for which no system identifier could be generated
    …BC0CE32F95D340D8A4E48BB8A?mode=9&sort=&photoSort=&value=People">People</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 287, Column 4: entity was defined here
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";
  • Warning Line 784, Column 97: reference not terminated by REFC delimiter
    …2BC0CE32F95D340D8A4E48BB8A?mode=9&sort=&photoSort=&value=Ringtone+Sounds">Ring…

    If you meant to include an entity that starts with "&", then you should terminate it 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 784, Column 97: reference to external entity in attribute value
    …2BC0CE32F95D340D8A4E48BB8A?mode=9&sort=&photoSort=&value=Ringtone+Sounds">Ring…

    This is generally the sign of an ampersand that 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 784, Column 97: reference to entity "sort" for which no system identifier could be generated
    …2BC0CE32F95D340D8A4E48BB8A?mode=9&sort=&photoSort=&value=Ringtone+Sounds">Ring…

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

  • Info Line 286, Column 79: entity was defined here
    ….do;jsessionid=81E6E72BC0CE32F95D340D8A4E48BB8A?mode=" + mode + "&sort=" + sort
  • Warning Line 784, Column 108: reference not terminated by REFC delimiter
    …D340D8A4E48BB8A?mode=9&sort=&photoSort=&value=Ringtone+Sounds">Ringtone Sounds…

    If you meant to include an entity that starts with "&", then you should terminate it 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 784, Column 108: reference to external entity in attribute value
    …D340D8A4E48BB8A?mode=9&sort=&photoSort=&value=Ringtone+Sounds">Ringtone Sounds…

    This is generally the sign of an ampersand that 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 784, Column 108: reference to entity "photoSort" for which no system identifier could be generated
    …D340D8A4E48BB8A?mode=9&sort=&photoSort=&value=Ringtone+Sounds">Ringtone Sounds…

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

  • Info Line 287, Column 30: entity was defined here
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";
  • Warning Line 784, Column 115: reference not terminated by REFC delimiter
    …4E48BB8A?mode=9&sort=&photoSort=&value=Ringtone+Sounds">Ringtone Sounds</a></l…

    If you meant to include an entity that starts with "&", then you should terminate it 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 784, Column 115: reference to external entity in attribute value
    …4E48BB8A?mode=9&sort=&photoSort=&value=Ringtone+Sounds">Ringtone Sounds</a></l…

    This is generally the sign of an ampersand that 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 784, Column 115: reference to entity "value" for which no system identifier could be generated
    …4E48BB8A?mode=9&sort=&photoSort=&value=Ringtone+Sounds">Ringtone Sounds</a></l…

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

  • Info Line 287, Column 4: entity was defined here
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";
  • Warning Line 785, Column 97: reference not terminated by REFC delimiter
    …2BC0CE32F95D340D8A4E48BB8A?mode=9&sort=&photoSort=&value=Sports">Sports</a></l…

    If you meant to include an entity that starts with "&", then you should terminate it 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 785, Column 97: reference to external entity in attribute value
    …2BC0CE32F95D340D8A4E48BB8A?mode=9&sort=&photoSort=&value=Sports">Sports</a></l…

    This is generally the sign of an ampersand that 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 785, Column 97: reference to entity "sort" for which no system identifier could be generated
    …2BC0CE32F95D340D8A4E48BB8A?mode=9&sort=&photoSort=&value=Sports">Sports</a></l…

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

  • Info Line 286, Column 79: entity was defined here
    ….do;jsessionid=81E6E72BC0CE32F95D340D8A4E48BB8A?mode=" + mode + "&sort=" + sort
  • Warning Line 785, Column 108: reference not terminated by REFC delimiter
    …BC0CE32F95D340D8A4E48BB8A?mode=9&sort=&photoSort=&value=Sports">Sports</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 785, Column 108: reference to external entity in attribute value
    …BC0CE32F95D340D8A4E48BB8A?mode=9&sort=&photoSort=&value=Sports">Sports</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 785, Column 108: reference to entity "photoSort" for which no system identifier could be generated
    …BC0CE32F95D340D8A4E48BB8A?mode=9&sort=&photoSort=&value=Sports">Sports</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 287, Column 30: entity was defined here
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";
  • Warning Line 785, Column 115: reference not terminated by REFC delimiter
    …BC0CE32F95D340D8A4E48BB8A?mode=9&sort=&photoSort=&value=Sports">Sports</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 785, Column 115: reference to external entity in attribute value
    …BC0CE32F95D340D8A4E48BB8A?mode=9&sort=&photoSort=&value=Sports">Sports</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 785, Column 115: reference to entity "value" for which no system identifier could be generated
    …BC0CE32F95D340D8A4E48BB8A?mode=9&sort=&photoSort=&value=Sports">Sports</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 287, Column 4: entity was defined here
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";
  • Warning Line 786, Column 97: reference not terminated by REFC delimiter
    …2BC0CE32F95D340D8A4E48BB8A?mode=9&sort=&photoSort=&value=Miscellaneous">Miscel…

    If you meant to include an entity that starts with "&", then you should terminate it 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 786, Column 97: reference to external entity in attribute value
    …2BC0CE32F95D340D8A4E48BB8A?mode=9&sort=&photoSort=&value=Miscellaneous">Miscel…

    This is generally the sign of an ampersand that 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 786, Column 97: reference to entity "sort" for which no system identifier could be generated
    …2BC0CE32F95D340D8A4E48BB8A?mode=9&sort=&photoSort=&value=Miscellaneous">Miscel…

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

  • Info Line 286, Column 79: entity was defined here
    ….do;jsessionid=81E6E72BC0CE32F95D340D8A4E48BB8A?mode=" + mode + "&sort=" + sort
  • Warning Line 786, Column 108: reference not terminated by REFC delimiter
    …D340D8A4E48BB8A?mode=9&sort=&photoSort=&value=Miscellaneous">Miscellaneous</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 786, Column 108: reference to external entity in attribute value
    …D340D8A4E48BB8A?mode=9&sort=&photoSort=&value=Miscellaneous">Miscellaneous</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 786, Column 108: reference to entity "photoSort" for which no system identifier could be generated
    …D340D8A4E48BB8A?mode=9&sort=&photoSort=&value=Miscellaneous">Miscellaneous</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 287, Column 30: entity was defined here
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";
  • Warning Line 786, Column 115: reference not terminated by REFC delimiter
    …D8A4E48BB8A?mode=9&sort=&photoSort=&value=Miscellaneous">Miscellaneous</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 786, Column 115: reference to external entity in attribute value
    …D8A4E48BB8A?mode=9&sort=&photoSort=&value=Miscellaneous">Miscellaneous</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 786, Column 115: reference to entity "value" for which no system identifier could be generated
    …D8A4E48BB8A?mode=9&sort=&photoSort=&value=Miscellaneous">Miscellaneous</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 287, Column 4: entity was defined here
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";
  • Warning Line 802, Column 92: reference not terminated by REFC delimiter
    …2BC0CE32F95D340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=" class="L3 ">All T…

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

  • Warning Line 802, Column 92: reference to external entity in attribute value
    …2BC0CE32F95D340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=" class="L3 ">All T…

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

  • Error Line 802, Column 92: reference to entity "sort" for which no system identifier could be generated
    …2BC0CE32F95D340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=" class="L3 ">All T…

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

  • Info Line 286, Column 79: entity was defined here
    ….do;jsessionid=81E6E72BC0CE32F95D340D8A4E48BB8A?mode=" + mode + "&sort=" + sort
  • Warning Line 802, Column 104: reference not terminated by REFC delimiter
    …340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=" class="L3 ">All Tags</a><a hr…

    If you meant to include an entity that starts with "&", then you should terminate it 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 802, Column 104: reference to external entity in attribute value
    …340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=" class="L3 ">All Tags</a><a hr…

    This is generally the sign of an ampersand that 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 802, Column 104: reference to entity "photoSort" for which no system identifier could be generated
    …340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=" class="L3 ">All Tags</a><a hr…

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

  • Info Line 287, Column 30: entity was defined here
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";
  • Warning Line 802, Column 112: reference not terminated by REFC delimiter
    …48BB8A?mode=8&sort=3&photoSort=3&value=" class="L3 ">All Tags</a><a href="/pho…

    If you meant to include an entity that starts with "&", then you should terminate it 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 802, Column 112: reference to external entity in attribute value
    …48BB8A?mode=8&sort=3&photoSort=3&value=" class="L3 ">All Tags</a><a href="/pho…

    This is generally the sign of an ampersand that 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 802, Column 112: reference to entity "value" for which no system identifier could be generated
    …48BB8A?mode=8&sort=3&photoSort=3&value=" class="L3 ">All Tags</a><a href="/pho…

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

  • Info Line 287, Column 4: entity was defined here
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";
  • Warning Line 802, Column 230: reference not terminated by REFC delimiter
    …2BC0CE32F95D340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=animals" class="L5 …

    If you meant to include an entity that starts with "&", then you should terminate it 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 802, Column 230: reference to external entity in attribute value
    …2BC0CE32F95D340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=animals" class="L5 …

    This is generally the sign of an ampersand that 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 802, Column 230: reference to entity "sort" for which no system identifier could be generated
    …2BC0CE32F95D340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=animals" class="L5 …

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

  • Info Line 286, Column 79: entity was defined here
    ….do;jsessionid=81E6E72BC0CE32F95D340D8A4E48BB8A?mode=" + mode + "&sort=" + sort
  • Warning Line 802, Column 242: reference not terminated by REFC delimiter
    …340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=animals" class="L5 " title="ani…

    If you meant to include an entity that starts with "&", then you should terminate it 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 802, Column 242: reference to external entity in attribute value
    …340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=animals" class="L5 " title="ani…

    This is generally the sign of an ampersand that 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 802, Column 242: reference to entity "photoSort" for which no system identifier could be generated
    …340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=animals" class="L5 " title="ani…

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

  • Info Line 287, Column 30: entity was defined here
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";
  • Warning Line 802, Column 250: reference not terminated by REFC delimiter
    …48BB8A?mode=8&sort=3&photoSort=3&value=animals" class="L5 " title="animals">an…

    If you meant to include an entity that starts with "&", then you should terminate it 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 802, Column 250: reference to external entity in attribute value
    …48BB8A?mode=8&sort=3&photoSort=3&value=animals" class="L5 " title="animals">an…

    This is generally the sign of an ampersand that 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 802, Column 250: reference to entity "value" for which no system identifier could be generated
    …48BB8A?mode=8&sort=3&photoSort=3&value=animals" class="L5 " title="animals">an…

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

  • Info Line 287, Column 4: entity was defined here
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";
  • Warning Line 802, Column 390: reference not terminated by REFC delimiter
    …2BC0CE32F95D340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=anime" class="L5 " …

    If you meant to include an entity that starts with "&", then you should terminate it 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 802, Column 390: reference to external entity in attribute value
    …2BC0CE32F95D340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=anime" class="L5 " …

    This is generally the sign of an ampersand that 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 802, Column 390: reference to entity "sort" for which no system identifier could be generated
    …2BC0CE32F95D340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=anime" class="L5 " …

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

  • Info Line 286, Column 79: entity was defined here
    ….do;jsessionid=81E6E72BC0CE32F95D340D8A4E48BB8A?mode=" + mode + "&sort=" + sort
  • Warning Line 802, Column 402: reference not terminated by REFC delimiter
    …340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=anime" class="L5 " title="anime…

    If you meant to include an entity that starts with "&", then you should terminate it 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 802, Column 402: reference to external entity in attribute value
    …340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=anime" class="L5 " title="anime…

    This is generally the sign of an ampersand that 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 802, Column 402: reference to entity "photoSort" for which no system identifier could be generated
    …340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=anime" class="L5 " title="anime…

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

  • Info Line 287, Column 30: entity was defined here
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";
  • Warning Line 802, Column 410: reference not terminated by REFC delimiter
    …48BB8A?mode=8&sort=3&photoSort=3&value=anime" class="L5 " title="anime">anime<…

    If you meant to include an entity that starts with "&", then you should terminate it 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 802, Column 410: reference to external entity in attribute value
    …48BB8A?mode=8&sort=3&photoSort=3&value=anime" class="L5 " title="anime">anime<…

    This is generally the sign of an ampersand that 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 802, Column 410: reference to entity "value" for which no system identifier could be generated
    …48BB8A?mode=8&sort=3&photoSort=3&value=anime" class="L5 " title="anime">anime<…

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

  • Info Line 287, Column 4: entity was defined here
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";
  • Warning Line 802, Column 544: reference not terminated by REFC delimiter
    …2BC0CE32F95D340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=awesome" class="L3 …

    If you meant to include an entity that starts with "&", then you should terminate it 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 802, Column 544: reference to external entity in attribute value
    …2BC0CE32F95D340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=awesome" class="L3 …

    This is generally the sign of an ampersand that 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 802, Column 544: reference to entity "sort" for which no system identifier could be generated
    …2BC0CE32F95D340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=awesome" class="L3 …

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

  • Info Line 286, Column 79: entity was defined here
    ….do;jsessionid=81E6E72BC0CE32F95D340D8A4E48BB8A?mode=" + mode + "&sort=" + sort
  • Warning Line 802, Column 556: reference not terminated by REFC delimiter
    …340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=awesome" class="L3 " title="awe…

    If you meant to include an entity that starts with "&", then you should terminate it 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 802, Column 556: reference to external entity in attribute value
    …340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=awesome" class="L3 " title="awe…

    This is generally the sign of an ampersand that 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 802, Column 556: reference to entity "photoSort" for which no system identifier could be generated
    …340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=awesome" class="L3 " title="awe…

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

  • Info Line 287, Column 30: entity was defined here
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";
  • Warning Line 802, Column 564: reference not terminated by REFC delimiter
    …48BB8A?mode=8&sort=3&photoSort=3&value=awesome" class="L3 " title="awesome">aw…

    If you meant to include an entity that starts with "&", then you should terminate it 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 802, Column 564: reference to external entity in attribute value
    …48BB8A?mode=8&sort=3&photoSort=3&value=awesome" class="L3 " title="awesome">aw…

    This is generally the sign of an ampersand that 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 802, Column 564: reference to entity "value" for which no system identifier could be generated
    …48BB8A?mode=8&sort=3&photoSort=3&value=awesome" class="L3 " title="awesome">aw…

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

  • Info Line 287, Column 4: entity was defined here
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";
  • Warning Line 802, Column 704: reference not terminated by REFC delimiter
    …2BC0CE32F95D340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=babe" class="L5 " t…

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

  • Warning Line 802, Column 704: reference to external entity in attribute value
    …2BC0CE32F95D340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=babe" class="L5 " t…

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

  • Error Line 802, Column 704: reference to entity "sort" for which no system identifier could be generated
    …2BC0CE32F95D340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=babe" class="L5 " t…

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

  • Info Line 286, Column 79: entity was defined here
    ….do;jsessionid=81E6E72BC0CE32F95D340D8A4E48BB8A?mode=" + mode + "&sort=" + sort
  • Warning Line 802, Column 716: reference not terminated by REFC delimiter
    …340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=babe" class="L5 " title="babe">…

    If you meant to include an entity that starts with "&", then you should terminate it 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 802, Column 716: reference to external entity in attribute value
    …340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=babe" class="L5 " title="babe">…

    This is generally the sign of an ampersand that 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 802, Column 716: reference to entity "photoSort" for which no system identifier could be generated
    …340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=babe" class="L5 " title="babe">…

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

  • Info Line 287, Column 30: entity was defined here
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";
  • Warning Line 802, Column 724: reference not terminated by REFC delimiter
    …48BB8A?mode=8&sort=3&photoSort=3&value=babe" class="L5 " title="babe">babe</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 802, Column 724: reference to external entity in attribute value
    …48BB8A?mode=8&sort=3&photoSort=3&value=babe" class="L5 " title="babe">babe</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 802, Column 724: reference to entity "value" for which no system identifier could be generated
    …48BB8A?mode=8&sort=3&photoSort=3&value=babe" class="L5 " title="babe">babe</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 287, Column 4: entity was defined here
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";
  • Warning Line 802, Column 855: reference not terminated by REFC delimiter
    …2BC0CE32F95D340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=black" class="L4 " …

    If you meant to include an entity that starts with "&", then you should terminate it 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 802, Column 855: reference to external entity in attribute value
    …2BC0CE32F95D340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=black" class="L4 " …

    This is generally the sign of an ampersand that 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 802, Column 855: reference to entity "sort" for which no system identifier could be generated
    …2BC0CE32F95D340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=black" class="L4 " …

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

  • Info Line 286, Column 79: entity was defined here
    ….do;jsessionid=81E6E72BC0CE32F95D340D8A4E48BB8A?mode=" + mode + "&sort=" + sort
  • Warning Line 802, Column 867: reference not terminated by REFC delimiter
    …340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=black" class="L4 " title="black…

    If you meant to include an entity that starts with "&", then you should terminate it 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 802, Column 867: reference to external entity in attribute value
    …340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=black" class="L4 " title="black…

    This is generally the sign of an ampersand that 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 802, Column 867: reference to entity "photoSort" for which no system identifier could be generated
    …340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=black" class="L4 " title="black…

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

  • Info Line 287, Column 30: entity was defined here
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";
  • Warning Line 802, Column 875: reference not terminated by REFC delimiter
    …48BB8A?mode=8&sort=3&photoSort=3&value=black" class="L4 " title="black">black<…

    If you meant to include an entity that starts with "&", then you should terminate it 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 802, Column 875: reference to external entity in attribute value
    …48BB8A?mode=8&sort=3&photoSort=3&value=black" class="L4 " title="black">black<…

    This is generally the sign of an ampersand that 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 802, Column 875: reference to entity "value" for which no system identifier could be generated
    …48BB8A?mode=8&sort=3&photoSort=3&value=black" class="L4 " title="black">black<…

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

  • Info Line 287, Column 4: entity was defined here
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";
  • Warning Line 802, Column 1009: reference not terminated by REFC delimiter
    …2BC0CE32F95D340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=blue" class="L5 " t…

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

  • Warning Line 802, Column 1009: reference to external entity in attribute value
    …2BC0CE32F95D340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=blue" class="L5 " t…

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

  • Error Line 802, Column 1009: reference to entity "sort" for which no system identifier could be generated
    …2BC0CE32F95D340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=blue" class="L5 " t…

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

  • Info Line 286, Column 79: entity was defined here
    ….do;jsessionid=81E6E72BC0CE32F95D340D8A4E48BB8A?mode=" + mode + "&sort=" + sort
  • Warning Line 802, Column 1021: reference not terminated by REFC delimiter
    …340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=blue" class="L5 " title="blue">…

    If you meant to include an entity that starts with "&", then you should terminate it 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 802, Column 1021: reference to external entity in attribute value
    …340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=blue" class="L5 " title="blue">…

    This is generally the sign of an ampersand that 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 802, Column 1021: reference to entity "photoSort" for which no system identifier could be generated
    …340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=blue" class="L5 " title="blue">…

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

  • Info Line 287, Column 30: entity was defined here
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";
  • Warning Line 802, Column 1029: reference not terminated by REFC delimiter
    …48BB8A?mode=8&sort=3&photoSort=3&value=blue" class="L5 " title="blue">blue</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 802, Column 1029: reference to external entity in attribute value
    …48BB8A?mode=8&sort=3&photoSort=3&value=blue" class="L5 " title="blue">blue</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 802, Column 1029: reference to entity "value" for which no system identifier could be generated
    …48BB8A?mode=8&sort=3&photoSort=3&value=blue" class="L5 " title="blue">blue</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 287, Column 4: entity was defined here
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";
  • Warning Line 802, Column 1160: reference not terminated by REFC delimiter
    …2BC0CE32F95D340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=cat" class="L5 " ti…

    If you meant to include an entity that starts with "&", then you should terminate it 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 802, Column 1160: reference to external entity in attribute value
    …2BC0CE32F95D340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=cat" class="L5 " ti…

    This is generally the sign of an ampersand that 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 802, Column 1160: reference to entity "sort" for which no system identifier could be generated
    …2BC0CE32F95D340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=cat" class="L5 " ti…

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

  • Info Line 286, Column 79: entity was defined here
    ….do;jsessionid=81E6E72BC0CE32F95D340D8A4E48BB8A?mode=" + mode + "&sort=" + sort
  • Warning Line 802, Column 1172: reference not terminated by REFC delimiter
    …340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=cat" class="L5 " title="cat">ca…

    If you meant to include an entity that starts with "&", then you should terminate it 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 802, Column 1172: reference to external entity in attribute value
    …340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=cat" class="L5 " title="cat">ca…

    This is generally the sign of an ampersand that 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 802, Column 1172: reference to entity "photoSort" for which no system identifier could be generated
    …340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=cat" class="L5 " title="cat">ca…

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

  • Info Line 287, Column 30: entity was defined here
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";
  • Warning Line 802, Column 1180: reference not terminated by REFC delimiter
    …48BB8A?mode=8&sort=3&photoSort=3&value=cat" class="L5 " title="cat">cat</a><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 802, Column 1180: reference to external entity in attribute value
    …48BB8A?mode=8&sort=3&photoSort=3&value=cat" class="L5 " title="cat">cat</a><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 802, Column 1180: reference to entity "value" for which no system identifier could be generated
    …48BB8A?mode=8&sort=3&photoSort=3&value=cat" class="L5 " title="cat">cat</a><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 287, Column 4: entity was defined here
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";
  • Warning Line 802, Column 1308: reference not terminated by REFC delimiter
    …2BC0CE32F95D340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=cool" class="L3 " t…

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

  • Warning Line 802, Column 1308: reference to external entity in attribute value
    …2BC0CE32F95D340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=cool" class="L3 " t…

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

  • Error Line 802, Column 1308: reference to entity "sort" for which no system identifier could be generated
    …2BC0CE32F95D340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=cool" class="L3 " t…

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

  • Info Line 286, Column 79: entity was defined here
    ….do;jsessionid=81E6E72BC0CE32F95D340D8A4E48BB8A?mode=" + mode + "&sort=" + sort
  • Warning Line 802, Column 1320: reference not terminated by REFC delimiter
    …340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=cool" class="L3 " title="cool">…

    If you meant to include an entity that starts with "&", then you should terminate it 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 802, Column 1320: reference to external entity in attribute value
    …340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=cool" class="L3 " title="cool">…

    This is generally the sign of an ampersand that 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 802, Column 1320: reference to entity "photoSort" for which no system identifier could be generated
    …340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=cool" class="L3 " title="cool">…

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

  • Info Line 287, Column 30: entity was defined here
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";
  • Warning Line 802, Column 1328: reference not terminated by REFC delimiter
    …48BB8A?mode=8&sort=3&photoSort=3&value=cool" class="L3 " title="cool">cool</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 802, Column 1328: reference to external entity in attribute value
    …48BB8A?mode=8&sort=3&photoSort=3&value=cool" class="L3 " title="cool">cool</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 802, Column 1328: reference to entity "value" for which no system identifier could be generated
    …48BB8A?mode=8&sort=3&photoSort=3&value=cool" class="L3 " title="cool">cool</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 287, Column 4: entity was defined here
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";
  • Warning Line 802, Column 1459: reference not terminated by REFC delimiter
    …2BC0CE32F95D340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=cute" class="L2 " t…

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

  • Warning Line 802, Column 1459: reference to external entity in attribute value
    …2BC0CE32F95D340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=cute" class="L2 " t…

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

  • Error Line 802, Column 1459: reference to entity "sort" for which no system identifier could be generated
    …2BC0CE32F95D340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=cute" class="L2 " t…

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

  • Info Line 286, Column 79: entity was defined here
    ….do;jsessionid=81E6E72BC0CE32F95D340D8A4E48BB8A?mode=" + mode + "&sort=" + sort
  • Warning Line 802, Column 1471: reference not terminated by REFC delimiter
    …340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=cute" class="L2 " title="cute">…

    If you meant to include an entity that starts with "&", then you should terminate it 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 802, Column 1471: reference to external entity in attribute value
    …340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=cute" class="L2 " title="cute">…

    This is generally the sign of an ampersand that 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 802, Column 1471: reference to entity "photoSort" for which no system identifier could be generated
    …340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=cute" class="L2 " title="cute">…

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

  • Info Line 287, Column 30: entity was defined here
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";
  • Warning Line 802, Column 1479: reference not terminated by REFC delimiter
    …48BB8A?mode=8&sort=3&photoSort=3&value=cute" class="L2 " title="cute">cute</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 802, Column 1479: reference to external entity in attribute value
    …48BB8A?mode=8&sort=3&photoSort=3&value=cute" class="L2 " title="cute">cute</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 802, Column 1479: reference to entity "value" for which no system identifier could be generated
    …48BB8A?mode=8&sort=3&photoSort=3&value=cute" class="L2 " title="cute">cute</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 287, Column 4: entity was defined here
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";
  • Warning Line 802, Column 1610: reference not terminated by REFC delimiter
    …2BC0CE32F95D340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=emo" class="L5 " ti…

    If you meant to include an entity that starts with "&", then you should terminate it 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 802, Column 1610: reference to external entity in attribute value
    …2BC0CE32F95D340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=emo" class="L5 " ti…

    This is generally the sign of an ampersand that 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 802, Column 1610: reference to entity "sort" for which no system identifier could be generated
    …2BC0CE32F95D340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=emo" class="L5 " ti…

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

  • Info Line 286, Column 79: entity was defined here
    ….do;jsessionid=81E6E72BC0CE32F95D340D8A4E48BB8A?mode=" + mode + "&sort=" + sort
  • Warning Line 802, Column 1622: reference not terminated by REFC delimiter
    …340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=emo" class="L5 " title="emo">em…

    If you meant to include an entity that starts with "&", then you should terminate it 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 802, Column 1622: reference to external entity in attribute value
    …340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=emo" class="L5 " title="emo">em…

    This is generally the sign of an ampersand that 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 802, Column 1622: reference to entity "photoSort" for which no system identifier could be generated
    …340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=emo" class="L5 " title="emo">em…

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

  • Info Line 287, Column 30: entity was defined here
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";
  • Warning Line 802, Column 1630: reference not terminated by REFC delimiter
    …48BB8A?mode=8&sort=3&photoSort=3&value=emo" class="L5 " title="emo">emo</a><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 802, Column 1630: reference to external entity in attribute value
    …48BB8A?mode=8&sort=3&photoSort=3&value=emo" class="L5 " title="emo">emo</a><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 802, Column 1630: reference to entity "value" for which no system identifier could be generated
    …48BB8A?mode=8&sort=3&photoSort=3&value=emo" class="L5 " title="emo">emo</a><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 287, Column 4: entity was defined here
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";
  • Warning Line 802, Column 1758: reference not terminated by REFC delimiter
    …2BC0CE32F95D340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=Funny" class="L2 " …

    If you meant to include an entity that starts with "&", then you should terminate it 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 802, Column 1758: reference to external entity in attribute value
    …2BC0CE32F95D340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=Funny" class="L2 " …

    This is generally the sign of an ampersand that 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 802, Column 1758: reference to entity "sort" for which no system identifier could be generated
    …2BC0CE32F95D340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=Funny" class="L2 " …

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

  • Info Line 286, Column 79: entity was defined here
    ….do;jsessionid=81E6E72BC0CE32F95D340D8A4E48BB8A?mode=" + mode + "&sort=" + sort
  • Warning Line 802, Column 1770: reference not terminated by REFC delimiter
    …340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=Funny" class="L2 " title="Funny…

    If you meant to include an entity that starts with "&", then you should terminate it 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 802, Column 1770: reference to external entity in attribute value
    …340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=Funny" class="L2 " title="Funny…

    This is generally the sign of an ampersand that 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 802, Column 1770: reference to entity "photoSort" for which no system identifier could be generated
    …340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=Funny" class="L2 " title="Funny…

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

  • Info Line 287, Column 30: entity was defined here
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";
  • Warning Line 802, Column 1778: reference not terminated by REFC delimiter
    …48BB8A?mode=8&sort=3&photoSort=3&value=Funny" class="L2 " title="Funny">Funny<…

    If you meant to include an entity that starts with "&", then you should terminate it 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 802, Column 1778: reference to external entity in attribute value
    …48BB8A?mode=8&sort=3&photoSort=3&value=Funny" class="L2 " title="Funny">Funny<…

    This is generally the sign of an ampersand that 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 802, Column 1778: reference to entity "value" for which no system identifier could be generated
    …48BB8A?mode=8&sort=3&photoSort=3&value=Funny" class="L2 " title="Funny">Funny<…

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

  • Info Line 287, Column 4: entity was defined here
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";
  • Warning Line 802, Column 1912: reference not terminated by REFC delimiter
    …2BC0CE32F95D340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=girl" class="L5 " t…

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

  • Warning Line 802, Column 1912: reference to external entity in attribute value
    …2BC0CE32F95D340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=girl" class="L5 " t…

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

  • Error Line 802, Column 1912: reference to entity "sort" for which no system identifier could be generated
    …2BC0CE32F95D340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=girl" class="L5 " t…

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

  • Info Line 286, Column 79: entity was defined here
    ….do;jsessionid=81E6E72BC0CE32F95D340D8A4E48BB8A?mode=" + mode + "&sort=" + sort
  • Warning Line 802, Column 1924: reference not terminated by REFC delimiter
    …340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=girl" class="L5 " title="girl">…

    If you meant to include an entity that starts with "&", then you should terminate it 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 802, Column 1924: reference to external entity in attribute value
    …340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=girl" class="L5 " title="girl">…

    This is generally the sign of an ampersand that 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 802, Column 1924: reference to entity "photoSort" for which no system identifier could be generated
    …340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=girl" class="L5 " title="girl">…

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

  • Info Line 287, Column 30: entity was defined here
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";
  • Warning Line 802, Column 1932: reference not terminated by REFC delimiter
    …48BB8A?mode=8&sort=3&photoSort=3&value=girl" class="L5 " title="girl">girl</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 802, Column 1932: reference to external entity in attribute value
    …48BB8A?mode=8&sort=3&photoSort=3&value=girl" class="L5 " title="girl">girl</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 802, Column 1932: reference to entity "value" for which no system identifier could be generated
    …48BB8A?mode=8&sort=3&photoSort=3&value=girl" class="L5 " title="girl">girl</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 287, Column 4: entity was defined here
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";
  • Warning Line 802, Column 2063: reference not terminated by REFC delimiter
    …2BC0CE32F95D340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=girls" class="L5 " …

    If you meant to include an entity that starts with "&", then you should terminate it 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 802, Column 2063: reference to external entity in attribute value
    …2BC0CE32F95D340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=girls" class="L5 " …

    This is generally the sign of an ampersand that 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 802, Column 2063: reference to entity "sort" for which no system identifier could be generated
    …2BC0CE32F95D340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=girls" class="L5 " …

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

  • Info Line 286, Column 79: entity was defined here
    ….do;jsessionid=81E6E72BC0CE32F95D340D8A4E48BB8A?mode=" + mode + "&sort=" + sort
  • Warning Line 802, Column 2075: reference not terminated by REFC delimiter
    …340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=girls" class="L5 " title="girls…

    If you meant to include an entity that starts with "&", then you should terminate it 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 802, Column 2075: reference to external entity in attribute value
    …340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=girls" class="L5 " title="girls…

    This is generally the sign of an ampersand that 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 802, Column 2075: reference to entity "photoSort" for which no system identifier could be generated
    …340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=girls" class="L5 " title="girls…

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

  • Info Line 287, Column 30: entity was defined here
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";
  • Warning Line 802, Column 2083: reference not terminated by REFC delimiter
    …48BB8A?mode=8&sort=3&photoSort=3&value=girls" class="L5 " title="girls">girls<…

    If you meant to include an entity that starts with "&", then you should terminate it 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 802, Column 2083: reference to external entity in attribute value
    …48BB8A?mode=8&sort=3&photoSort=3&value=girls" class="L5 " title="girls">girls<…

    This is generally the sign of an ampersand that 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 802, Column 2083: reference to entity "value" for which no system identifier could be generated
    …48BB8A?mode=8&sort=3&photoSort=3&value=girls" class="L5 " title="girls">girls<…

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

  • Info Line 287, Column 4: entity was defined here
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";
  • Warning Line 802, Column 2217: reference not terminated by REFC delimiter
    …2BC0CE32F95D340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=green" class="L5 " …

    If you meant to include an entity that starts with "&", then you should terminate it 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 802, Column 2217: reference to external entity in attribute value
    …2BC0CE32F95D340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=green" class="L5 " …

    This is generally the sign of an ampersand that 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 802, Column 2217: reference to entity "sort" for which no system identifier could be generated
    …2BC0CE32F95D340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=green" class="L5 " …

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

  • Info Line 286, Column 79: entity was defined here
    ….do;jsessionid=81E6E72BC0CE32F95D340D8A4E48BB8A?mode=" + mode + "&sort=" + sort
  • Warning Line 802, Column 2229: reference not terminated by REFC delimiter
    …340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=green" class="L5 " title="green…

    If you meant to include an entity that starts with "&", then you should terminate it 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 802, Column 2229: reference to external entity in attribute value
    …340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=green" class="L5 " title="green…

    This is generally the sign of an ampersand that 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 802, Column 2229: reference to entity "photoSort" for which no system identifier could be generated
    …340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=green" class="L5 " title="green…

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

  • Info Line 287, Column 30: entity was defined here
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";
  • Warning Line 802, Column 2237: reference not terminated by REFC delimiter
    …48BB8A?mode=8&sort=3&photoSort=3&value=green" class="L5 " title="green">green<…

    If you meant to include an entity that starts with "&", then you should terminate it 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 802, Column 2237: reference to external entity in attribute value
    …48BB8A?mode=8&sort=3&photoSort=3&value=green" class="L5 " title="green">green<…

    This is generally the sign of an ampersand that 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 802, Column 2237: reference to entity "value" for which no system identifier could be generated
    …48BB8A?mode=8&sort=3&photoSort=3&value=green" class="L5 " title="green">green<…

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

  • Info Line 287, Column 4: entity was defined here
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";
  • Warning Line 802, Column 2371: reference not terminated by REFC delimiter
    …2BC0CE32F95D340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=Heart" class="L5 " …

    If you meant to include an entity that starts with "&", then you should terminate it 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 802, Column 2371: reference to external entity in attribute value
    …2BC0CE32F95D340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=Heart" class="L5 " …

    This is generally the sign of an ampersand that 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 802, Column 2371: reference to entity "sort" for which no system identifier could be generated
    …2BC0CE32F95D340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=Heart" class="L5 " …

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

  • Info Line 286, Column 79: entity was defined here
    ….do;jsessionid=81E6E72BC0CE32F95D340D8A4E48BB8A?mode=" + mode + "&sort=" + sort
  • Warning Line 802, Column 2383: reference not terminated by REFC delimiter
    …340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=Heart" class="L5 " title="Heart…

    If you meant to include an entity that starts with "&", then you should terminate it 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 802, Column 2383: reference to external entity in attribute value
    …340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=Heart" class="L5 " title="Heart…

    This is generally the sign of an ampersand that 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 802, Column 2383: reference to entity "photoSort" for which no system identifier could be generated
    …340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=Heart" class="L5 " title="Heart…

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

  • Info Line 287, Column 30: entity was defined here
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";
  • Warning Line 802, Column 2391: reference not terminated by REFC delimiter
    …48BB8A?mode=8&sort=3&photoSort=3&value=Heart" class="L5 " title="Heart">Heart<…

    If you meant to include an entity that starts with "&", then you should terminate it 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 802, Column 2391: reference to external entity in attribute value
    …48BB8A?mode=8&sort=3&photoSort=3&value=Heart" class="L5 " title="Heart">Heart<…

    This is generally the sign of an ampersand that 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 802, Column 2391: reference to entity "value" for which no system identifier could be generated
    …48BB8A?mode=8&sort=3&photoSort=3&value=Heart" class="L5 " title="Heart">Heart<…

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

  • Info Line 287, Column 4: entity was defined here
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";
  • Warning Line 802, Column 2525: reference not terminated by REFC delimiter
    …2BC0CE32F95D340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=hot" class="L4 " ti…

    If you meant to include an entity that starts with "&", then you should terminate it 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 802, Column 2525: reference to external entity in attribute value
    …2BC0CE32F95D340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=hot" class="L4 " ti…

    This is generally the sign of an ampersand that 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 802, Column 2525: reference to entity "sort" for which no system identifier could be generated
    …2BC0CE32F95D340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=hot" class="L4 " ti…

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

  • Info Line 286, Column 79: entity was defined here
    ….do;jsessionid=81E6E72BC0CE32F95D340D8A4E48BB8A?mode=" + mode + "&sort=" + sort
  • Warning Line 802, Column 2537: reference not terminated by REFC delimiter
    …340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=hot" class="L4 " title="hot">ho…

    If you meant to include an entity that starts with "&", then you should terminate it 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 802, Column 2537: reference to external entity in attribute value
    …340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=hot" class="L4 " title="hot">ho…

    This is generally the sign of an ampersand that 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 802, Column 2537: reference to entity "photoSort" for which no system identifier could be generated
    …340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=hot" class="L4 " title="hot">ho…

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

  • Info Line 287, Column 30: entity was defined here
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";
  • Warning Line 802, Column 2545: reference not terminated by REFC delimiter
    …48BB8A?mode=8&sort=3&photoSort=3&value=hot" class="L4 " title="hot">hot</a><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 802, Column 2545: reference to external entity in attribute value
    …48BB8A?mode=8&sort=3&photoSort=3&value=hot" class="L4 " title="hot">hot</a><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 802, Column 2545: reference to entity "value" for which no system identifier could be generated
    …48BB8A?mode=8&sort=3&photoSort=3&value=hot" class="L4 " title="hot">hot</a><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 287, Column 4: entity was defined here
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";
  • Warning Line 802, Column 2673: reference not terminated by REFC delimiter
    …2BC0CE32F95D340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=Humor" class="L5 " …

    If you meant to include an entity that starts with "&", then you should terminate it 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 802, Column 2673: reference to external entity in attribute value
    …2BC0CE32F95D340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=Humor" class="L5 " …

    This is generally the sign of an ampersand that 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 802, Column 2673: reference to entity "sort" for which no system identifier could be generated
    …2BC0CE32F95D340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=Humor" class="L5 " …

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

  • Info Line 286, Column 79: entity was defined here
    ….do;jsessionid=81E6E72BC0CE32F95D340D8A4E48BB8A?mode=" + mode + "&sort=" + sort
  • Warning Line 802, Column 2685: reference not terminated by REFC delimiter
    …340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=Humor" class="L5 " title="Humor…

    If you meant to include an entity that starts with "&", then you should terminate it 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 802, Column 2685: reference to external entity in attribute value
    …340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=Humor" class="L5 " title="Humor…

    This is generally the sign of an ampersand that 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 802, Column 2685: reference to entity "photoSort" for which no system identifier could be generated
    …340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=Humor" class="L5 " title="Humor…

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

  • Info Line 287, Column 30: entity was defined here
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";
  • Warning Line 802, Column 2693: reference not terminated by REFC delimiter
    …48BB8A?mode=8&sort=3&photoSort=3&value=Humor" class="L5 " title="Humor">Humor<…

    If you meant to include an entity that starts with "&", then you should terminate it 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 802, Column 2693: reference to external entity in attribute value
    …48BB8A?mode=8&sort=3&photoSort=3&value=Humor" class="L5 " title="Humor">Humor<…

    This is generally the sign of an ampersand that 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 802, Column 2693: reference to entity "value" for which no system identifier could be generated
    …48BB8A?mode=8&sort=3&photoSort=3&value=Humor" class="L5 " title="Humor">Humor<…

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

  • Info Line 287, Column 4: entity was defined here
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";
  • Warning Line 802, Column 2827: reference not terminated by REFC delimiter
    …2BC0CE32F95D340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=logo" class="L5 " t…

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

  • Warning Line 802, Column 2827: reference to external entity in attribute value
    …2BC0CE32F95D340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=logo" class="L5 " t…

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

  • Error Line 802, Column 2827: reference to entity "sort" for which no system identifier could be generated
    …2BC0CE32F95D340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=logo" class="L5 " t…

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

  • Info Line 286, Column 79: entity was defined here
    ….do;jsessionid=81E6E72BC0CE32F95D340D8A4E48BB8A?mode=" + mode + "&sort=" + sort
  • Warning Line 802, Column 2839: reference not terminated by REFC delimiter
    …340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=logo" class="L5 " title="logo">…

    If you meant to include an entity that starts with "&", then you should terminate it 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 802, Column 2839: reference to external entity in attribute value
    …340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=logo" class="L5 " title="logo">…

    This is generally the sign of an ampersand that 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 802, Column 2839: reference to entity "photoSort" for which no system identifier could be generated
    …340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=logo" class="L5 " title="logo">…

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

  • Info Line 287, Column 30: entity was defined here
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";
  • Warning Line 802, Column 2847: reference not terminated by REFC delimiter
    …48BB8A?mode=8&sort=3&photoSort=3&value=logo" class="L5 " title="logo">logo</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 802, Column 2847: reference to external entity in attribute value
    …48BB8A?mode=8&sort=3&photoSort=3&value=logo" class="L5 " title="logo">logo</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 802, Column 2847: reference to entity "value" for which no system identifier could be generated
    …48BB8A?mode=8&sort=3&photoSort=3&value=logo" class="L5 " title="logo">logo</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 287, Column 4: entity was defined here
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";
  • Warning Line 802, Column 2978: reference not terminated by REFC delimiter
    …2BC0CE32F95D340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=Love" class="L1 " t…

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

  • Warning Line 802, Column 2978: reference to external entity in attribute value
    …2BC0CE32F95D340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=Love" class="L1 " t…

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

  • Error Line 802, Column 2978: reference to entity "sort" for which no system identifier could be generated
    …2BC0CE32F95D340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=Love" class="L1 " t…

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

  • Info Line 286, Column 79: entity was defined here
    ….do;jsessionid=81E6E72BC0CE32F95D340D8A4E48BB8A?mode=" + mode + "&sort=" + sort
  • Warning Line 802, Column 2990: reference not terminated by REFC delimiter
    …340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=Love" class="L1 " title="Love">…

    If you meant to include an entity that starts with "&", then you should terminate it 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 802, Column 2990: reference to external entity in attribute value
    …340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=Love" class="L1 " title="Love">…

    This is generally the sign of an ampersand that 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 802, Column 2990: reference to entity "photoSort" for which no system identifier could be generated
    …340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=Love" class="L1 " title="Love">…

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

  • Info Line 287, Column 30: entity was defined here
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";
  • Warning Line 802, Column 2998: reference not terminated by REFC delimiter
    …48BB8A?mode=8&sort=3&photoSort=3&value=Love" class="L1 " title="Love">Love</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 802, Column 2998: reference to external entity in attribute value
    …48BB8A?mode=8&sort=3&photoSort=3&value=Love" class="L1 " title="Love">Love</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 802, Column 2998: reference to entity "value" for which no system identifier could be generated
    …48BB8A?mode=8&sort=3&photoSort=3&value=Love" class="L1 " title="Love">Love</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 287, Column 4: entity was defined here
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";
  • Warning Line 802, Column 3129: reference not terminated by REFC delimiter
    …2BC0CE32F95D340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=me" class="L5 " tit…

    If you meant to include an entity that starts with "&", then you should terminate it 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 802, Column 3129: reference to external entity in attribute value
    …2BC0CE32F95D340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=me" class="L5 " tit…

    This is generally the sign of an ampersand that 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 802, Column 3129: reference to entity "sort" for which no system identifier could be generated
    …2BC0CE32F95D340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=me" class="L5 " tit…

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

  • Info Line 286, Column 79: entity was defined here
    ….do;jsessionid=81E6E72BC0CE32F95D340D8A4E48BB8A?mode=" + mode + "&sort=" + sort
  • Warning Line 802, Column 3141: reference not terminated by REFC delimiter
    …340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=me" class="L5 " title="me">me</…

    If you meant to include an entity that starts with "&", then you should terminate it 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 802, Column 3141: reference to external entity in attribute value
    …340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=me" class="L5 " title="me">me</…

    This is generally the sign of an ampersand that 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 802, Column 3141: reference to entity "photoSort" for which no system identifier could be generated
    …340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=me" class="L5 " title="me">me</…

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

  • Info Line 287, Column 30: entity was defined here
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";
  • Warning Line 802, Column 3149: reference not terminated by REFC delimiter
    …48BB8A?mode=8&sort=3&photoSort=3&value=me" class="L5 " title="me">me</a><a hre…

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

  • Warning Line 802, Column 3149: reference to external entity in attribute value
    …48BB8A?mode=8&sort=3&photoSort=3&value=me" class="L5 " title="me">me</a><a hre…

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

  • Error Line 802, Column 3149: reference to entity "value" for which no system identifier could be generated
    …48BB8A?mode=8&sort=3&photoSort=3&value=me" class="L5 " title="me">me</a><a hre…

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

  • Info Line 287, Column 4: entity was defined here
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";
  • Warning Line 802, Column 3274: reference not terminated by REFC delimiter
    …2BC0CE32F95D340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=Misc." class="L5 " …

    If you meant to include an entity that starts with "&", then you should terminate it 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 802, Column 3274: reference to external entity in attribute value
    …2BC0CE32F95D340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=Misc." class="L5 " …

    This is generally the sign of an ampersand that 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 802, Column 3274: reference to entity "sort" for which no system identifier could be generated
    …2BC0CE32F95D340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=Misc." class="L5 " …

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

  • Info Line 286, Column 79: entity was defined here
    ….do;jsessionid=81E6E72BC0CE32F95D340D8A4E48BB8A?mode=" + mode + "&sort=" + sort
  • Warning Line 802, Column 3286: reference not terminated by REFC delimiter
    …340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=Misc." class="L5 " title="Misc.…

    If you meant to include an entity that starts with "&", then you should terminate it 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 802, Column 3286: reference to external entity in attribute value
    …340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=Misc." class="L5 " title="Misc.…

    This is generally the sign of an ampersand that 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 802, Column 3286: reference to entity "photoSort" for which no system identifier could be generated
    …340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=Misc." class="L5 " title="Misc.…

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

  • Info Line 287, Column 30: entity was defined here
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";
  • Warning Line 802, Column 3294: reference not terminated by REFC delimiter
    …48BB8A?mode=8&sort=3&photoSort=3&value=Misc." class="L5 " title="Misc.">Misc.<…

    If you meant to include an entity that starts with "&", then you should terminate it 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 802, Column 3294: reference to external entity in attribute value
    …48BB8A?mode=8&sort=3&photoSort=3&value=Misc." class="L5 " title="Misc.">Misc.<…

    This is generally the sign of an ampersand that 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 802, Column 3294: reference to entity "value" for which no system identifier could be generated
    …48BB8A?mode=8&sort=3&photoSort=3&value=Misc." class="L5 " title="Misc.">Misc.<…

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

  • Info Line 287, Column 4: entity was defined here
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";
  • Warning Line 802, Column 3428: reference not terminated by REFC delimiter
    …2BC0CE32F95D340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=Music" class="L5 " …

    If you meant to include an entity that starts with "&", then you should terminate it 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 802, Column 3428: reference to external entity in attribute value
    …2BC0CE32F95D340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=Music" class="L5 " …

    This is generally the sign of an ampersand that 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 802, Column 3428: reference to entity "sort" for which no system identifier could be generated
    …2BC0CE32F95D340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=Music" class="L5 " …

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

  • Info Line 286, Column 79: entity was defined here
    ….do;jsessionid=81E6E72BC0CE32F95D340D8A4E48BB8A?mode=" + mode + "&sort=" + sort
  • Warning Line 802, Column 3440: reference not terminated by REFC delimiter
    …340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=Music" class="L5 " title="Music…

    If you meant to include an entity that starts with "&", then you should terminate it 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 802, Column 3440: reference to external entity in attribute value
    …340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=Music" class="L5 " title="Music…

    This is generally the sign of an ampersand that 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 802, Column 3440: reference to entity "photoSort" for which no system identifier could be generated
    …340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=Music" class="L5 " title="Music…

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

  • Info Line 287, Column 30: entity was defined here
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";
  • Warning Line 802, Column 3448: reference not terminated by REFC delimiter
    …48BB8A?mode=8&sort=3&photoSort=3&value=Music" class="L5 " title="Music">Music<…

    If you meant to include an entity that starts with "&", then you should terminate it 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 802, Column 3448: reference to external entity in attribute value
    …48BB8A?mode=8&sort=3&photoSort=3&value=Music" class="L5 " title="Music">Music<…

    This is generally the sign of an ampersand that 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 802, Column 3448: reference to entity "value" for which no system identifier could be generated
    …48BB8A?mode=8&sort=3&photoSort=3&value=Music" class="L5 " title="Music">Music<…

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

  • Info Line 287, Column 4: entity was defined here
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";
  • Warning Line 802, Column 3582: reference not terminated by REFC delimiter
    …2BC0CE32F95D340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=new+moon" class="L5…

    If you meant to include an entity that starts with "&", then you should terminate it 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 802, Column 3582: reference to external entity in attribute value
    …2BC0CE32F95D340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=new+moon" class="L5…

    This is generally the sign of an ampersand that 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 802, Column 3582: reference to entity "sort" for which no system identifier could be generated
    …2BC0CE32F95D340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=new+moon" class="L5…

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

  • Info Line 286, Column 79: entity was defined here
    ….do;jsessionid=81E6E72BC0CE32F95D340D8A4E48BB8A?mode=" + mode + "&sort=" + sort
  • Warning Line 802, Column 3594: reference not terminated by REFC delimiter
    …340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=new+moon" class="L5 " title="ne…

    If you meant to include an entity that starts with "&", then you should terminate it 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 802, Column 3594: reference to external entity in attribute value
    …340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=new+moon" class="L5 " title="ne…

    This is generally the sign of an ampersand that 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 802, Column 3594: reference to entity "photoSort" for which no system identifier could be generated
    …340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=new+moon" class="L5 " title="ne…

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

  • Info Line 287, Column 30: entity was defined here
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";
  • Warning Line 802, Column 3602: reference not terminated by REFC delimiter
    …48BB8A?mode=8&sort=3&photoSort=3&value=new+moon" class="L5 " title="new moon">…

    If you meant to include an entity that starts with "&", then you should terminate it 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 802, Column 3602: reference to external entity in attribute value
    …48BB8A?mode=8&sort=3&photoSort=3&value=new+moon" class="L5 " title="new moon">…

    This is generally the sign of an ampersand that 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 802, Column 3602: reference to entity "value" for which no system identifier could be generated
    …48BB8A?mode=8&sort=3&photoSort=3&value=new+moon" class="L5 " title="new moon">…

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

  • Info Line 287, Column 4: entity was defined here
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";
  • Warning Line 802, Column 3745: reference not terminated by REFC delimiter
    …2BC0CE32F95D340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=Pink" class="L5 " t…

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

  • Warning Line 802, Column 3745: reference to external entity in attribute value
    …2BC0CE32F95D340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=Pink" class="L5 " t…

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

  • Error Line 802, Column 3745: reference to entity "sort" for which no system identifier could be generated
    …2BC0CE32F95D340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=Pink" class="L5 " t…

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

  • Info Line 286, Column 79: entity was defined here
    ….do;jsessionid=81E6E72BC0CE32F95D340D8A4E48BB8A?mode=" + mode + "&sort=" + sort
  • Warning Line 802, Column 3757: reference not terminated by REFC delimiter
    …340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=Pink" class="L5 " title="Pink">…

    If you meant to include an entity that starts with "&", then you should terminate it 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 802, Column 3757: reference to external entity in attribute value
    …340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=Pink" class="L5 " title="Pink">…

    This is generally the sign of an ampersand that 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 802, Column 3757: reference to entity "photoSort" for which no system identifier could be generated
    …340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=Pink" class="L5 " title="Pink">…

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

  • Info Line 287, Column 30: entity was defined here
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";
  • Warning Line 802, Column 3765: reference not terminated by REFC delimiter
    …48BB8A?mode=8&sort=3&photoSort=3&value=Pink" class="L5 " title="Pink">Pink</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 802, Column 3765: reference to external entity in attribute value
    …48BB8A?mode=8&sort=3&photoSort=3&value=Pink" class="L5 " title="Pink">Pink</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 802, Column 3765: reference to entity "value" for which no system identifier could be generated
    …48BB8A?mode=8&sort=3&photoSort=3&value=Pink" class="L5 " title="Pink">Pink</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 287, Column 4: entity was defined here
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";
  • Warning Line 802, Column 3896: reference not terminated by REFC delimiter
    …2BC0CE32F95D340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=pretty" class="L4 "…

    If you meant to include an entity that starts with "&", then you should terminate it 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 802, Column 3896: reference to external entity in attribute value
    …2BC0CE32F95D340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=pretty" class="L4 "…

    This is generally the sign of an ampersand that 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 802, Column 3896: reference to entity "sort" for which no system identifier could be generated
    …2BC0CE32F95D340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=pretty" class="L4 "…

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

  • Info Line 286, Column 79: entity was defined here
    ….do;jsessionid=81E6E72BC0CE32F95D340D8A4E48BB8A?mode=" + mode + "&sort=" + sort
  • Warning Line 802, Column 3908: reference not terminated by REFC delimiter
    …340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=pretty" class="L4 " title="pret…

    If you meant to include an entity that starts with "&", then you should terminate it 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 802, Column 3908: reference to external entity in attribute value
    …340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=pretty" class="L4 " title="pret…

    This is generally the sign of an ampersand that 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 802, Column 3908: reference to entity "photoSort" for which no system identifier could be generated
    …340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=pretty" class="L4 " title="pret…

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

  • Info Line 287, Column 30: entity was defined here
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";
  • Warning Line 802, Column 3916: reference not terminated by REFC delimiter
    …48BB8A?mode=8&sort=3&photoSort=3&value=pretty" class="L4 " title="pretty">pret…

    If you meant to include an entity that starts with "&", then you should terminate it 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 802, Column 3916: reference to external entity in attribute value
    …48BB8A?mode=8&sort=3&photoSort=3&value=pretty" class="L4 " title="pretty">pret…

    This is generally the sign of an ampersand that 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 802, Column 3916: reference to entity "value" for which no system identifier could be generated
    …48BB8A?mode=8&sort=3&photoSort=3&value=pretty" class="L4 " title="pretty">pret…

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

  • Info Line 287, Column 4: entity was defined here
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";
  • Warning Line 802, Column 4053: reference not terminated by REFC delimiter
    …2BC0CE32F95D340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=Red" class="L5 " ti…

    If you meant to include an entity that starts with "&", then you should terminate it 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 802, Column 4053: reference to external entity in attribute value
    …2BC0CE32F95D340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=Red" class="L5 " ti…

    This is generally the sign of an ampersand that 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 802, Column 4053: reference to entity "sort" for which no system identifier could be generated
    …2BC0CE32F95D340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=Red" class="L5 " ti…

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

  • Info Line 286, Column 79: entity was defined here
    ….do;jsessionid=81E6E72BC0CE32F95D340D8A4E48BB8A?mode=" + mode + "&sort=" + sort
  • Warning Line 802, Column 4065: reference not terminated by REFC delimiter
    …340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=Red" class="L5 " title="Red">Re…

    If you meant to include an entity that starts with "&", then you should terminate it 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 802, Column 4065: reference to external entity in attribute value
    …340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=Red" class="L5 " title="Red">Re…

    This is generally the sign of an ampersand that 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 802, Column 4065: reference to entity "photoSort" for which no system identifier could be generated
    …340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=Red" class="L5 " title="Red">Re…

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

  • Info Line 287, Column 30: entity was defined here
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";
  • Warning Line 802, Column 4073: reference not terminated by REFC delimiter
    …48BB8A?mode=8&sort=3&photoSort=3&value=Red" class="L5 " title="Red">Red</a><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 802, Column 4073: reference to external entity in attribute value
    …48BB8A?mode=8&sort=3&photoSort=3&value=Red" class="L5 " title="Red">Red</a><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 802, Column 4073: reference to entity "value" for which no system identifier could be generated
    …48BB8A?mode=8&sort=3&photoSort=3&value=Red" class="L5 " title="Red">Red</a><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 287, Column 4: entity was defined here
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";
  • Warning Line 802, Column 4201: reference not terminated by REFC delimiter
    …2BC0CE32F95D340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=sayings" class="L5 …

    If you meant to include an entity that starts with "&", then you should terminate it 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 802, Column 4201: reference to external entity in attribute value
    …2BC0CE32F95D340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=sayings" class="L5 …

    This is generally the sign of an ampersand that 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 802, Column 4201: reference to entity "sort" for which no system identifier could be generated
    …2BC0CE32F95D340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=sayings" class="L5 …

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

  • Info Line 286, Column 79: entity was defined here
    ….do;jsessionid=81E6E72BC0CE32F95D340D8A4E48BB8A?mode=" + mode + "&sort=" + sort
  • Warning Line 802, Column 4213: reference not terminated by REFC delimiter
    …340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=sayings" class="L5 " title="say…

    If you meant to include an entity that starts with "&", then you should terminate it 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 802, Column 4213: reference to external entity in attribute value
    …340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=sayings" class="L5 " title="say…

    This is generally the sign of an ampersand that 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 802, Column 4213: reference to entity "photoSort" for which no system identifier could be generated
    …340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=sayings" class="L5 " title="say…

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

  • Info Line 287, Column 30: entity was defined here
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";
  • Warning Line 802, Column 4221: reference not terminated by REFC delimiter
    …48BB8A?mode=8&sort=3&photoSort=3&value=sayings" class="L5 " title="sayings">sa…

    If you meant to include an entity that starts with "&", then you should terminate it 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 802, Column 4221: reference to external entity in attribute value
    …48BB8A?mode=8&sort=3&photoSort=3&value=sayings" class="L5 " title="sayings">sa…

    This is generally the sign of an ampersand that 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 802, Column 4221: reference to entity "value" for which no system identifier could be generated
    …48BB8A?mode=8&sort=3&photoSort=3&value=sayings" class="L5 " title="sayings">sa…

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

  • Info Line 287, Column 4: entity was defined here
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";
  • Warning Line 802, Column 4361: reference not terminated by REFC delimiter
    …2BC0CE32F95D340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=Sexy" class="L3 " t…

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

  • Warning Line 802, Column 4361: reference to external entity in attribute value
    …2BC0CE32F95D340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=Sexy" class="L3 " t…

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

  • Error Line 802, Column 4361: reference to entity "sort" for which no system identifier could be generated
    …2BC0CE32F95D340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=Sexy" class="L3 " t…

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

  • Info Line 286, Column 79: entity was defined here
    ….do;jsessionid=81E6E72BC0CE32F95D340D8A4E48BB8A?mode=" + mode + "&sort=" + sort
  • Warning Line 802, Column 4373: reference not terminated by REFC delimiter
    …340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=Sexy" class="L3 " title="Sexy">…

    If you meant to include an entity that starts with "&", then you should terminate it 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 802, Column 4373: reference to external entity in attribute value
    …340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=Sexy" class="L3 " title="Sexy">…

    This is generally the sign of an ampersand that 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 802, Column 4373: reference to entity "photoSort" for which no system identifier could be generated
    …340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=Sexy" class="L3 " title="Sexy">…

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

  • Info Line 287, Column 30: entity was defined here
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";
  • Warning Line 802, Column 4381: reference not terminated by REFC delimiter
    …48BB8A?mode=8&sort=3&photoSort=3&value=Sexy" class="L3 " title="Sexy">Sexy</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 802, Column 4381: reference to external entity in attribute value
    …48BB8A?mode=8&sort=3&photoSort=3&value=Sexy" class="L3 " title="Sexy">Sexy</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 802, Column 4381: reference to entity "value" for which no system identifier could be generated
    …48BB8A?mode=8&sort=3&photoSort=3&value=Sexy" class="L3 " title="Sexy">Sexy</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 287, Column 4: entity was defined here
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";
  • Warning Line 802, Column 4512: reference not terminated by REFC delimiter
    …2BC0CE32F95D340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=sports" class="L5 "…

    If you meant to include an entity that starts with "&", then you should terminate it 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 802, Column 4512: reference to external entity in attribute value
    …2BC0CE32F95D340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=sports" class="L5 "…

    This is generally the sign of an ampersand that 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 802, Column 4512: reference to entity "sort" for which no system identifier could be generated
    …2BC0CE32F95D340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=sports" class="L5 "…

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

  • Info Line 286, Column 79: entity was defined here
    ….do;jsessionid=81E6E72BC0CE32F95D340D8A4E48BB8A?mode=" + mode + "&sort=" + sort
  • Warning Line 802, Column 4524: reference not terminated by REFC delimiter
    …340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=sports" class="L5 " title="spor…

    If you meant to include an entity that starts with "&", then you should terminate it 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 802, Column 4524: reference to external entity in attribute value
    …340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=sports" class="L5 " title="spor…

    This is generally the sign of an ampersand that 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 802, Column 4524: reference to entity "photoSort" for which no system identifier could be generated
    …340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=sports" class="L5 " title="spor…

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

  • Info Line 287, Column 30: entity was defined here
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";
  • Warning Line 802, Column 4532: reference not terminated by REFC delimiter
    …48BB8A?mode=8&sort=3&photoSort=3&value=sports" class="L5 " title="sports">spor…

    If you meant to include an entity that starts with "&", then you should terminate it 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 802, Column 4532: reference to external entity in attribute value
    …48BB8A?mode=8&sort=3&photoSort=3&value=sports" class="L5 " title="sports">spor…

    This is generally the sign of an ampersand that 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 802, Column 4532: reference to entity "value" for which no system identifier could be generated
    …48BB8A?mode=8&sort=3&photoSort=3&value=sports" class="L5 " title="sports">spor…

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

  • Info Line 287, Column 4: entity was defined here
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";
  • Warning Line 802, Column 4669: reference not terminated by REFC delimiter
    …2BC0CE32F95D340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=SWEET" class="L5 " …

    If you meant to include an entity that starts with "&", then you should terminate it 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 802, Column 4669: reference to external entity in attribute value
    …2BC0CE32F95D340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=SWEET" class="L5 " …

    This is generally the sign of an ampersand that 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 802, Column 4669: reference to entity "sort" for which no system identifier could be generated
    …2BC0CE32F95D340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=SWEET" class="L5 " …

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

  • Info Line 286, Column 79: entity was defined here
    ….do;jsessionid=81E6E72BC0CE32F95D340D8A4E48BB8A?mode=" + mode + "&sort=" + sort
  • Warning Line 802, Column 4681: reference not terminated by REFC delimiter
    …340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=SWEET" class="L5 " title="SWEET…

    If you meant to include an entity that starts with "&", then you should terminate it 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 802, Column 4681: reference to external entity in attribute value
    …340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=SWEET" class="L5 " title="SWEET…

    This is generally the sign of an ampersand that 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 802, Column 4681: reference to entity "photoSort" for which no system identifier could be generated
    …340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=SWEET" class="L5 " title="SWEET…

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

  • Info Line 287, Column 30: entity was defined here
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";
  • Warning Line 802, Column 4689: reference not terminated by REFC delimiter
    …48BB8A?mode=8&sort=3&photoSort=3&value=SWEET" class="L5 " title="SWEET">SWEET<…

    If you meant to include an entity that starts with "&", then you should terminate it 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 802, Column 4689: reference to external entity in attribute value
    …48BB8A?mode=8&sort=3&photoSort=3&value=SWEET" class="L5 " title="SWEET">SWEET<…

    This is generally the sign of an ampersand that 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 802, Column 4689: reference to entity "value" for which no system identifier could be generated
    …48BB8A?mode=8&sort=3&photoSort=3&value=SWEET" class="L5 " title="SWEET">SWEET<…

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

  • Info Line 287, Column 4: entity was defined here
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";
  • Warning Line 802, Column 4823: reference not terminated by REFC delimiter
    …2BC0CE32F95D340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=Twilight" class="L4…

    If you meant to include an entity that starts with "&", then you should terminate it 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 802, Column 4823: reference to external entity in attribute value
    …2BC0CE32F95D340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=Twilight" class="L4…

    This is generally the sign of an ampersand that 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 802, Column 4823: reference to entity "sort" for which no system identifier could be generated
    …2BC0CE32F95D340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=Twilight" class="L4…

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

  • Info Line 286, Column 79: entity was defined here
    ….do;jsessionid=81E6E72BC0CE32F95D340D8A4E48BB8A?mode=" + mode + "&sort=" + sort
  • Warning Line 802, Column 4835: reference not terminated by REFC delimiter
    …340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=Twilight" class="L4 " title="Tw…

    If you meant to include an entity that starts with "&", then you should terminate it 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 802, Column 4835: reference to external entity in attribute value
    …340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=Twilight" class="L4 " title="Tw…

    This is generally the sign of an ampersand that 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 802, Column 4835: reference to entity "photoSort" for which no system identifier could be generated
    …340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=Twilight" class="L4 " title="Tw…

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

  • Info Line 287, Column 30: entity was defined here
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";
  • Warning Line 802, Column 4843: reference not terminated by REFC delimiter
    …48BB8A?mode=8&sort=3&photoSort=3&value=Twilight" class="L4 " title="Twilight">…

    If you meant to include an entity that starts with "&", then you should terminate it 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 802, Column 4843: reference to external entity in attribute value
    …48BB8A?mode=8&sort=3&photoSort=3&value=Twilight" class="L4 " title="Twilight">…

    This is generally the sign of an ampersand that 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 802, Column 4843: reference to entity "value" for which no system identifier could be generated
    …48BB8A?mode=8&sort=3&photoSort=3&value=Twilight" class="L4 " title="Twilight">…

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

  • Info Line 287, Column 4: entity was defined here
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";
  • Warning Line 802, Column 4986: reference not terminated by REFC delimiter
    …2BC0CE32F95D340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=White" class="L5 " …

    If you meant to include an entity that starts with "&", then you should terminate it 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 802, Column 4986: reference to external entity in attribute value
    …2BC0CE32F95D340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=White" class="L5 " …

    This is generally the sign of an ampersand that 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 802, Column 4986: reference to entity "sort" for which no system identifier could be generated
    …2BC0CE32F95D340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=White" class="L5 " …

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

  • Info Line 286, Column 79: entity was defined here
    ….do;jsessionid=81E6E72BC0CE32F95D340D8A4E48BB8A?mode=" + mode + "&sort=" + sort
  • Warning Line 802, Column 4998: reference not terminated by REFC delimiter
    …340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=White" class="L5 " title="White…

    If you meant to include an entity that starts with "&", then you should terminate it 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 802, Column 4998: reference to external entity in attribute value
    …340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=White" class="L5 " title="White…

    This is generally the sign of an ampersand that 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 802, Column 4998: reference to entity "photoSort" for which no system identifier could be generated
    …340D8A4E48BB8A?mode=8&sort=3&photoSort=3&value=White" class="L5 " title="White…

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

  • Info Line 287, Column 30: entity was defined here
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";
  • Warning Line 802, Column 5006: reference not terminated by REFC delimiter
    …48BB8A?mode=8&sort=3&photoSort=3&value=White" class="L5 " title="White">White<…

    If you meant to include an entity that starts with "&", then you should terminate it 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 802, Column 5006: reference to external entity in attribute value
    …48BB8A?mode=8&sort=3&photoSort=3&value=White" class="L5 " title="White">White<…

    This is generally the sign of an ampersand that 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 802, Column 5006: reference to entity "value" for which no system identifier could be generated
    …48BB8A?mode=8&sort=3&photoSort=3&value=White" class="L5 " title="White">White<…

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

  • Info Line 287, Column 4: entity was defined here
    + "&value=" + value+ "&page=0&photoSort=3&photoPage=0";
  • Error Line 835, Column 7: end tag for "div" omitted, but OMITTAG NO was specified
    </body></html>

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

  • Info Line 60, Column 1: start tag was here
    <div id="content">

Visitor Analysis

Daily Visitor
  • 2.800 visits