avon.ru

Россия Главная     |     Помощь     |     Представителям Добавить в Избранное JOIN THE COMMUNITY Если у тебя есть знакомый Представитель Avon – обратись к нему и размести заказ Если у тебя нет знакомого Представителя Avon: ...

Display Widget for this domain on your website. Click Here
This data was last updated from 02-02-2013 05:06:17  (update).

Overview Info

  • Domain Name
    avon.ru
  • Favicon
  • Alexa Rank
    #23692
  • Google Page Rank
    PR 5
  • Ip Address
    134.65.6.50
  • Page Size
    65.1 KB
  • Images
    7 GIF, 45 JPG, 29 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    0 0 0 0 0 0

Website Meta Analysis



  • Title
    AVON Россия
  • Meta Keyword
  • Meta Description
    Россия Главная     |     Помощь     |     Представителям Добавить в Избранное JOIN THE COMMUNITY Если у тебя есть знакомый Представитель Avon – обратись к нему и размести заказ Если у тебя нет знакомого Представителя Avon: Если ты Представитель ...

Technical Analysis



  • Webserver
    IBM_HTTP_Server
  • Ip Address
    134.65.6.50
  • Domain Age
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from avon.ru.

HTML Analysis

  • date: Sat, 02 Feb 2013 05:04:26 GMT
  • server: IBM_HTTP_Server
  • x-powered-by: Servlet/3.0
  • expires: Thu, 01 Dec 1994 16:00:00 GMT
  • cache-control: no-cache="set-cookie, set-cookie2"
  • content-type: text/html; charset=UTF-8
  • content-language: ru-ru
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
% By submitting a query to RIPN's Whois Service
% you agree to abide by the following terms of use:
% http://www.ripn.net/about/servpol.html#3.2 (in Russian)
% http://www.ripn.net/about/en/servpol.html#3.2 (in English).

domain: AVON.RU
nserver: dns1.avon.com.
nserver: dns4.avon.com.
state: REGISTERED, DELEGATED, VERIFIED
org: Avon Products, Inc.
registrar: RU-CENTER-REG-RIPN
admin-contact: https://www.nic.ru/whois
created: 2000.04.01
paid-till: 2013.05.01
free-date: 2013.06.01
source: TCI

Last updated on 2012.10.09 23:57:02 MSK

DNS Analysis


DNS servers
dns4.avon.com [134.65.42.140]
dns1.avon.com [134.65.2.131]


DNS Records

Answer records
avon.ru MX
preference: 6
exchange: alt1.aspmx.l.google.com
86400s
avon.ru MX
preference: 5
exchange: aspmx.l.google.com
86400s
avon.ru MX
preference: 4
exchange: avon.ru.s200b2.psmtp.com
86400s
avon.ru MX
preference: 3
exchange: avon.ru.s200b1.psmtp.comavon.ru.s200b1.psmtp.com
86400s
avon.ru MX
preference: 2
exchange: avon.ru.s200a2.psmtp.com
86400s
avon.ru MX
preference: 1
exchange: avon.ru.s200a1.psmtp.com
86400s
avon.ru MX
preference: 10
exchange: aspmx3.googlemail.com
86400s
avon.ru MX
preference: 10
exchange: aspmx2.googlemail.com
86400s
avon.ru MX
preference: 6
exchange: alt2.aspmx.l.google.com
86400s
avon.ru NS  dns1.avon.com 86400s
avon.ru NS  dns4.avon.com 86400s
avon.ru SOA
server: dns1.avon.com
email: ismael@lezcano.avon.com
serial: 2005062170
refresh: 10800
retry: 3600
expire: 2592000
minimum ttl: 900
86400s
avon.ru TXT google-site-verification=YK2Si5UaXay3Y8DpQEbTDBOgttxLhfaI6NP3MiMbHTo 86400s
avon.ru A 134.65.6.50 600s

Authority records

Additional records

IP 134.65.6.50 Analysis

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

Site Same Ip

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 132 Errors
  • 102 Warnings
Ratio Text/Html
  • 0.494057801386513
Message Error
  • Error Line 5, Column 1: no document type declaration; will parse without validation
    <script type="text/javascript">	

    The document type could not be determined, because the document had no correct DOCTYPE declaration. The document does not look like HTML, therefore automatic fallback could not be performed, and the document was only checked against basic markup syntax.

    Learn how to add a doctype to your document from our FAQ, or use the validator's Document Type option to validate your document against a specific Document Type.

  • Error Line 17, Column 6: document type does not allow element "HTML" here
    <html>

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

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

  • Warning Line 21, Column 43: NET-enabling start-tag requires SHORTTAG YES
    <LINK href="static/css/usec.css" type=text/css rel=stylesheet>

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

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

  • Warning Line 22, Column 59: NET-enabling start-tag requires SHORTTAG YES
    <LINK title=Style href="static/css/mt_style.css" type=text/css

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

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

  • Warning Line 24, Column 54: NET-enabling start-tag requires SHORTTAG YES
    <LINK title=Style href="static/css/win.css" type=text/css rel=STYLESHEET>

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

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

  • Warning Line 116, Column 99: cannot generate system identifier for general entity "location.search.indexOf"
    …tion.search.indexOf("endcount")!=-1 &&location.search.indexOf("pagename")!=-1)…

    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 116, Column 99: general entity "location.search.indexOf" not defined and no default entity
    …tion.search.indexOf("endcount")!=-1 &&location.search.indexOf("pagename")!=-1)…

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

  • Error Line 116, Column 122: reference to entity "location.search.indexOf" for which no system identifier could be generated
    …tion.search.indexOf("endcount")!=-1 &&location.search.indexOf("pagename")!=-1){

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

  • Info Line 116, Column 98: entity was defined here
    …ation.search.indexOf("endcount")!=-1 &&location.search.indexOf("pagename")!=-1…
  • Error Line 301, Column 6: end tag for element "DIV" which is not open
    </div>

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

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

  • Error Line 359, Column 5: invalid comment declaration: found name start character outside comment but inside comment declaration
    <!--Function to open navigations in a new window - 19th August -->
  • Info Line 356, Column 31: comment declaration started here
    <script language="JavaScript"><!--
  • Warning Line 378, Column 20: cannot generate system identifier for general entity "LangCodeVal"
    		if(url.indexOf('&LangCodeVal') > 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 378, Column 20: general entity "LangCodeVal" not defined and no default entity
    		if(url.indexOf('&LangCodeVal') > 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.

  • Error Line 378, Column 31: reference to entity "LangCodeVal" for which no system identifier could be generated
    		if(url.indexOf('&LangCodeVal') > 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 378, Column 19: entity was defined here
    		if(url.indexOf('&LangCodeVal') > 0){
  • Error Line 382, Column 41: reference to entity "LangCodeVal" for which no system identifier could be generated
    		formObj.action=urlString+"&LangCodeVal="+langVal;

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

  • Info Line 378, Column 19: entity was defined here
    		if(url.indexOf('&LangCodeVal') > 0){
  • Error Line 386, Column 69: reference to entity "LangCodeVal" for which no system identifier could be generated
    			        	formObj.action=formObj.CURR_PAGE_URL.value+"&LangCodeVal="+langVal;

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

  • Info Line 378, Column 19: entity was defined here
    		if(url.indexOf('&LangCodeVal') > 0){
  • Warning Line 411, Column 68: cannot generate system identifier for general entity "currPage"
    …ngChange.page?LangCodeVal="+langVal+"&currPage="+currpage+"&"+requestParameter…

    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 411, Column 68: general entity "currPage" not defined and no default entity
    …ngChange.page?LangCodeVal="+langVal+"&currPage="+currpage+"&"+requestParameter…

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

  • Error Line 411, Column 76: reference to entity "currPage" for which no system identifier could be generated
    …ngChange.page?LangCodeVal="+langVal+"&currPage="+currpage+"&"+requestParameter;

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

  • Info Line 411, Column 67: entity was defined here
    …angChange.page?LangCodeVal="+langVal+"&currPage="+currpage+"&"+requestParamete…
  • Error Line 446, Column 27: character ";" not allowed in attribute specification list
    	    for(count=0;count<len;count++)
  • Error Line 508, Column 77: reference to entity "currPage" for which no system identifier could be generated
    …ngChange.page?LangCodeVal="+langVal+"&currPage="+currpage+"&"+requestParameter;

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

  • Info Line 411, Column 67: entity was defined here
    …angChange.page?LangCodeVal="+langVal+"&currPage="+currpage+"&"+requestParamete…
  • Warning Line 539, Column 12: cannot generate system identifier for general entity "langCd"
    		return "&langCd="+lng;

    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 539, Column 12: general entity "langCd" not defined and no default entity
    		return "&langCd="+lng;

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

  • Error Line 539, Column 18: reference to entity "langCd" for which no system identifier could be generated
    		return "&langCd="+lng;

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

  • Info Line 539, Column 11: entity was defined here
    		return "&langCd="+lng;
  • Warning Line 601, Column 27: NET-enabling start-tag requires SHORTTAG YES
    	NAME="NAV_PAGE" VALUE="" />

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

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

  • Warning Line 615, Column 51: NET-enabling start-tag requires SHORTTAG YES
    				<INPUT TYPE="HIDDEN" NAME="NAV_PAGE" VALUE="" />

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

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

  • Error Line 621, Column 33: an attribute value must be a literal unless it contains only name characters
    						<td height="99%" width=100%><a

    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 632, Column 20: an attribute value must be a literal unless it contains only name characters
    						<td width=100%><IMG

    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 646, Column 55: "NOWRAP" is not a member of a group specified for any attribute
    								<td class="topLinksBold" align="center" nowrap>Главная</td>
  • Warning Line 648, Column 42: cannot generate system identifier for general entity "nbsp"
    …					<td class=spacer align="center">&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nbs…

    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 648, Column 42: general entity "nbsp" not defined and no default entity
    …					<td class=spacer align="center">&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nbs…

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

  • Error Line 648, Column 46: reference to entity "nbsp" for which no system identifier could be generated
    …	<td class=spacer align="center">&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp;&n…

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

  • Info Line 648, Column 41: entity was defined here
    …						<td class=spacer align="center">&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nb…
  • Error Line 648, Column 52: reference to entity "nbsp" for which no system identifier could be generated
    …lass=spacer align="center">&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp;&nbsp;</…

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

  • Info Line 648, Column 41: entity was defined here
    …						<td class=spacer align="center">&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nb…
  • Error Line 648, Column 58: reference to entity "nbsp" for which no system identifier could be generated
    …ss=spacer align="center">&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp;&nbsp;</td>

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

  • Info Line 648, Column 41: entity was defined here
    …						<td class=spacer align="center">&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nb…
  • Error Line 648, Column 64: reference to entity "nbsp" for which no system identifier could be generated
    …ss=spacer align="center">&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp;&nbsp;</td>

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

  • Info Line 648, Column 41: entity was defined here
    …						<td class=spacer align="center">&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nb…
  • Error Line 648, Column 71: reference to entity "nbsp" for which no system identifier could be generated
    …ss=spacer align="center">&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp;&nbsp;</td>

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

  • Info Line 648, Column 41: entity was defined here
    …						<td class=spacer align="center">&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nb…
  • Error Line 648, Column 77: reference to entity "nbsp" for which no system identifier could be generated
    …ss=spacer align="center">&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp;&nbsp;</td>

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

  • Info Line 648, Column 41: entity was defined here
    …						<td class=spacer align="center">&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nb…
  • Error Line 648, Column 83: reference to entity "nbsp" for which no system identifier could be generated
    …ss=spacer align="center">&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp;&nbsp;</td>

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

  • Info Line 648, Column 41: entity was defined here
    …						<td class=spacer align="center">&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nb…
  • Error Line 648, Column 89: reference to entity "nbsp" for which no system identifier could be generated
    …ss=spacer align="center">&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp;&nbsp;</td>

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

  • Info Line 648, Column 41: entity was defined here
    …						<td class=spacer align="center">&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nb…
  • Error Line 650, Column 51: "NOWRAP" is not a member of a group specified for any attribute
    								<td align="center" class="topLinks" nowrap><a href="#"
  • Error Line 654, Column 46: reference to entity "nbsp" for which no system identifier could be generated
    …	<td class=spacer align="center">&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp;&n…

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

  • Info Line 648, Column 41: entity was defined here
    …						<td class=spacer align="center">&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nb…
  • Error Line 654, Column 52: reference to entity "nbsp" for which no system identifier could be generated
    …lass=spacer align="center">&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp;&nbsp;</…

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

  • Info Line 648, Column 41: entity was defined here
    …						<td class=spacer align="center">&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nb…
  • Error Line 654, Column 58: reference to entity "nbsp" for which no system identifier could be generated
    …ss=spacer align="center">&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp;&nbsp;</td>

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

  • Info Line 648, Column 41: entity was defined here
    …						<td class=spacer align="center">&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nb…
  • Error Line 654, Column 64: reference to entity "nbsp" for which no system identifier could be generated
    …ss=spacer align="center">&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp;&nbsp;</td>

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

  • Info Line 648, Column 41: entity was defined here
    …						<td class=spacer align="center">&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nb…
  • Error Line 654, Column 71: reference to entity "nbsp" for which no system identifier could be generated
    …ss=spacer align="center">&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp;&nbsp;</td>

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

  • Info Line 648, Column 41: entity was defined here
    …						<td class=spacer align="center">&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nb…
  • Error Line 654, Column 77: reference to entity "nbsp" for which no system identifier could be generated
    …ss=spacer align="center">&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp;&nbsp;</td>

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

  • Info Line 648, Column 41: entity was defined here
    …						<td class=spacer align="center">&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nb…
  • Error Line 654, Column 83: reference to entity "nbsp" for which no system identifier could be generated
    …ss=spacer align="center">&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp;&nbsp;</td>

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

  • Info Line 648, Column 41: entity was defined here
    …						<td class=spacer align="center">&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nb…
  • Error Line 654, Column 89: reference to entity "nbsp" for which no system identifier could be generated
    …ss=spacer align="center">&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp;&nbsp;</td>

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

  • Info Line 648, Column 41: entity was defined here
    …						<td class=spacer align="center">&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nb…
  • Error Line 656, Column 51: "NOWRAP" is not a member of a group specified for any attribute
    								<td align="center" class="topLinks" nowrap><a href="#"
  • Warning Line 682, Column 56: NET-enabling start-tag requires SHORTTAG YES
    									onkeypress="return checkSearchSubmit(event);" /></td>

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

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

  • Warning Line 719, Column 71: cannot generate system identifier for general entity "requestId"
    …ref="/REPSuite/customerRegistration.page?actionType=REJECTEDBAR&requestId=null"

    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 719, Column 71: general entity "requestId" not defined and no default entity
    …ref="/REPSuite/customerRegistration.page?actionType=REJECTEDBAR&requestId=null"

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

  • Error Line 719, Column 80: reference to entity "requestId" for which no system identifier could be generated
    …ref="/REPSuite/customerRegistration.page?actionType=REJECTEDBAR&requestId=null"

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

  • Info Line 719, Column 70: entity was defined here
    …ref="/REPSuite/customerRegistration.page?actionType=REJECTEDBAR&requestId=null"
  • Warning Line 722, Column 50: NET-enabling start-tag requires SHORTTAG YES
    			<INPUT TYPE="HIDDEN" NAME="CURR_URL" VALUE="" />

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

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

  • Warning Line 780, Column 19: NET-enabling start-tag requires SHORTTAG YES
    					width="100%" /></TD>

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

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

  • Error Line 878, Column 460: invalid comment declaration: found delimiter "[" outside comment but inside comment declaration
    …el="stylesheet" type="text/css" /><!--[if IE]><link href="http://www.avon.ru/P…
  • Info Line 878, Column 104: comment declaration started here
    …de(obj) {s.tl(this,'o',obj);}</script><!--------------------------------------…
  • Warning Line 878, Column 587: NET-enabling start-tag requires SHORTTAG YES
    …een" rel="stylesheet" type="text/css" /><![endif]--><script type="text/javascr…

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

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

  • Error Line 878, Column 592: "ENDIF" is not a reserved name
    …rel="stylesheet" type="text/css" /><![endif]--><script type="text/javascript" …
  • Error Line 878, Column 1308: invalid comment declaration: found name start character outside comment but inside comment declaration
    ….ru/js/swfobject.min.js"></script><!--div id="viva_banner_block"><div id="viva…
  • Info Line 878, Column 1072: comment declaration started here
    ….ru/js/jquery.cookie.min.js"></script><!--------------------------------------…
  • Warning Line 878, Column 1476: NET-enabling start-tag requires SHORTTAG YES
    …e/static/images/empty.gif" border="0" /></div--><!----------------------------…

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

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

  • Error Line 878, Column 1485: end tag for element "DIV--" which is not open
    …images/empty.gif" border="0" /></div--><!-------------------------------------…

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

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

  • Error Line 878, Column 1636: invalid comment declaration: found name start character outside comment but inside comment declaration
    …---------------------------------><!--div id="viva_countdown"></div--><!---pop…
  • Info Line 878, Column 1486: comment declaration started here
    …mages/empty.gif" border="0" /></div--><!--------------------------------------…
  • Error Line 878, Column 1667: end tag for element "DIV--" which is not open
    …--><!--div id="viva_countdown"></div--><!---popup_video eshe --><!-- <link hre…

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

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

  • Error Line 878, Column 2332: invalid comment declaration: found name start character outside comment but inside comment declaration
    …ru/a/02/close.png" alt="X"/></div><!--div id="popup_go_video_eshe"><A href="ht…
  • Info Line 878, Column 1693: comment declaration started here
    …own"></div--><!---popup_video eshe --><!-- <link href="http://avonmedia.ru/css…
  • Warning Line 878, Column 2532: NET-enabling start-tag requires SHORTTAG YES
    …/knopka.png" alt="Выбери свой подарок"/></A></div--><!--       </div><!---popu…

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

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

  • Error Line 878, Column 2545: end tag for element "DIV--" which is not open
    …alt="Выбери свой подарок"/></A></div--><!--       </div><!---popup_video eshe …

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

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

  • Error Line 878, Column 2567: invalid comment declaration: found name character outside comment but inside comment declaration
    …ок"/></A></div--><!--       </div><!---popup_video eshe --><div id="clickable_…
  • Info Line 878, Column 2546: comment declaration started here
    …lt="Выбери свой подарок"/></A></div--><!--       </div><!---popup_video eshe -…
  • Warning Line 878, Column 3322: NET-enabling start-tag requires SHORTTAG YES
    …" border="0" id="link_for_popup_video"/><!--/a--></div><div id="extra_prods"> …

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

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

  • Warning Line 878, Column 3484: NET-enabling start-tag requires SHORTTAG YES
    …gn_images/extra_prods.png" border="0" /> </A> </div><div class="widget"><div c…

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

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

  • Warning Line 878, Column 3771: NET-enabling start-tag requires SHORTTAG YES
    …edia.ru/a/02/XXL_kiss.jpg" border="0" /> </A></div><div imgid="lotereya" style…

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

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

  • Warning Line 878, Column 4048: NET-enabling start-tag requires SHORTTAG YES
    …reya_usloviya_c02.pdf"  target="_top" /><AREA shape="rect" coords="265,241,455…

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

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

  • Warning Line 878, Column 4154: NET-enabling start-tag requires SHORTTAG YES
    …on-promo.ru/#/lottery"  target="_top" /></map></div><div imgid="newsmssms"><A …

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

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

  • Warning Line 878, Column 4354: NET-enabling start-tag requires SHORTTAG YES
    ….ru/a/02/XXL_kiss_sms.jpg" border="0" /> </A></div><div imgid="prodolzhaem_raz…

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

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

  • Warning Line 878, Column 4648: NET-enabling start-tag requires SHORTTAG YES
    …02/XXL_sale_continius.jpg" border="0" /> </A></div><div imgid="fs" style="disp…

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

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

  • Warning Line 878, Column 4870: NET-enabling start-tag requires SHORTTAG YES
    …ia.ru/a/02/XXL_banner.jpg" border="0" /> </A></div><div imgid="fragrance_test"…

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

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

  • Warning Line 878, Column 5098: NET-enabling start-tag requires SHORTTAG YES
    …edia.ru/a/02/XXL_test.jpg" border="0" /> </A></div><div imgid="konferen"><A hr…

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

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

  • Warning Line 878, Column 5340: NET-enabling start-tag requires SHORTTAG YES
    …u/a/02/XXL_conference.jpg" border="0" /> </A></div><div imgid="zaschitniki"><A…

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

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

  • Warning Line 878, Column 5548: NET-enabling start-tag requires SHORTTAG YES
    …nmedia.ru/a/02/XXL_23.jpg" border="0" /> </A></div><div imgid="valya"><A href=…

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

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

  • Warning Line 878, Column 5639: cannot generate system identifier for general entity "cmpgnYrNr"
    …von.ru/PRSuite/eBrochure.page?index=1&cmpgnYrNr=201302&pageNo=104" onclick="li…

    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 878, Column 5639: general entity "cmpgnYrNr" not defined and no default entity
    …von.ru/PRSuite/eBrochure.page?index=1&cmpgnYrNr=201302&pageNo=104" onclick="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.

  • Error Line 878, Column 5648: reference to entity "cmpgnYrNr" for which no system identifier could be generated
    …Suite/eBrochure.page?index=1&cmpgnYrNr=201302&pageNo=104" onclick="linkCode('p…

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

  • Info Line 878, Column 5638: entity was defined here
    …avon.ru/PRSuite/eBrochure.page?index=1&cmpgnYrNr=201302&pageNo=104" onclick="l…
  • Warning Line 878, Column 5656: cannot generate system identifier for general entity "pageNo"
    …rochure.page?index=1&cmpgnYrNr=201302&pageNo=104" onclick="linkCode('pr.hp.mrq…

    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 878, Column 5656: general entity "pageNo" not defined and no default entity
    …rochure.page?index=1&cmpgnYrNr=201302&pageNo=104" onclick="linkCode('pr.hp.mrq…

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

  • Error Line 878, Column 5662: reference to entity "pageNo" for which no system identifier could be generated
    …e.page?index=1&cmpgnYrNr=201302&pageNo=104" onclick="linkCode('pr.hp.mrq.top.v…

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

  • Info Line 878, Column 5655: entity was defined here
    …Brochure.page?index=1&cmpgnYrNr=201302&pageNo=104" onclick="linkCode('pr.hp.mr…
  • Warning Line 878, Column 5790: NET-enabling start-tag requires SHORTTAG YES
    …u/a/02/XXL_valentines.jpg" border="0" /> </A></div>            <div imgid="soc…

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

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

  • Warning Line 878, Column 6063: NET-enabling start-tag requires SHORTTAG YES
    …tore/social_store_XXL.jpg" border="0" /> </A></div>           <div imgid="spa_…

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

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

  • Error Line 878, Column 6174: reference to entity "cmpgnYrNr" for which no system identifier could be generated
    …Suite/eBrochure.page?index=1&cmpgnYrNr=201302&pageNo=16" onclick="linkCode('pr…

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

  • Info Line 878, Column 5638: entity was defined here
    …avon.ru/PRSuite/eBrochure.page?index=1&cmpgnYrNr=201302&pageNo=104" onclick="l…
  • Error Line 878, Column 6188: reference to entity "pageNo" for which no system identifier could be generated
    …e.page?index=1&cmpgnYrNr=201302&pageNo=16" onclick="linkCode('pr.hp.mrq.top.sp…

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

  • Info Line 878, Column 5655: entity was defined here
    …Brochure.page?index=1&cmpgnYrNr=201302&pageNo=104" onclick="linkCode('pr.hp.mr…
  • Warning Line 878, Column 6319: NET-enabling start-tag requires SHORTTAG YES
    …a/02/XXL_banner_spa_2.jpg" border="0" /> </A></div><div imgid="sms_bigga"><A o…

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

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

  • Warning Line 878, Column 6519: NET-enabling start-tag requires SHORTTAG YES
    …media.ru/a/02/XXL_sms.jpg" border="0" /> </A></div></div><!-- Большие баннеры …

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

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

  • Warning Line 878, Column 6810: NET-enabling start-tag requires SHORTTAG YES
    …a.ru/a/17/catalogs_PR.png" border="0" /> </A> </div><div id="catbutton"> <A on…

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

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

  • Warning Line 878, Column 7038: NET-enabling start-tag requires SHORTTAG YES
    …/button/open_brochure.png" border="0" /> </A> </div><!-- Каталоги конец --></d…

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

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

  • Warning Line 878, Column 7276: NET-enabling start-tag requires SHORTTAG YES
    …a.ru/a/02/XXL_kiss_sm.jpg" border="0" /> </li><li> <img class="thumb" imgid="l…

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

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

  • Warning Line 878, Column 7385: NET-enabling start-tag requires SHORTTAG YES
    …ru/a/02/XXL_lotery_sm.jpg" border="0" /> </li><li> <img class="thumb" imgid="n…

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

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

  • Warning Line 878, Column 7492: NET-enabling start-tag requires SHORTTAG YES
    …ia.ru/a/02/XXL_sm_sms.jpg" border="0" /> </li><li> <img class="thumb" imgid="p…

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

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

  • Warning Line 878, Column 7621: NET-enabling start-tag requires SHORTTAG YES
    …XXL_sale_continius_sm.jpg" border="0" /> </li><li> <img class="thumb" imgid="f…

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

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

  • Warning Line 878, Column 7726: NET-enabling start-tag requires SHORTTAG YES
    …/a/02/XXL_banner_mini.jpg" border="0" /> </li><li> <img class="thumb" imgid="f…

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

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

  • Warning Line 878, Column 7839: NET-enabling start-tag requires SHORTTAG YES
    …a.ru/a/02/XXL_test_sm.jpg" border="0" /> </li><li> <img class="thumb" imgid="k…

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

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

  • Warning Line 878, Column 7944: NET-enabling start-tag requires SHORTTAG YES
    …dia.ru/a/02/XXL_iq_sm.jpg" border="0" /> </li><li> <img class="thumb" imgid="z…

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

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

  • Warning Line 878, Column 8052: NET-enabling start-tag requires SHORTTAG YES
    …dia.ru/a/02/XXL_23_sm.jpg" border="0" /> </li><li> <img class="thumb" imgid="v…

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

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

  • Warning Line 878, Column 8162: NET-enabling start-tag requires SHORTTAG YES
    …/02/XXL_valentines_sm.jpg" border="0" /> </li><li> <img class="thumb" imgid="s…

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

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

  • Warning Line 878, Column 8290: NET-enabling start-tag requires SHORTTAG YES
    …store/social_store_sm.jpg" border="0" /> </li><li> <img class="thumb" imgid="s…

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

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

  • Warning Line 878, Column 8402: NET-enabling start-tag requires SHORTTAG YES
    …2/XXL_banner_spa_mini.jpg" border="0" /> </li><li> <img class="thumb" imgid="s…

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

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

  • Warning Line 878, Column 8511: NET-enabling start-tag requires SHORTTAG YES
    ….ru/a/02/XXL_sms_mini.jpg" border="0" /> </li></ul><!-- Мини-версии больших ба…

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

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

  • Warning Line 878, Column 8858: NET-enabling start-tag requires SHORTTAG YES
    …ia.ru/a/01/pr_avondom.jpg" border="0" /></A><A onclick="linkCode('pr.hp.bnr.to…

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

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

  • Warning Line 878, Column 9071: NET-enabling start-tag requires SHORTTAG YES
    …/banners/recruiting_1.jpg" border="0" /></A><A onclick="linkCode('pr.hp.bnr.to…

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

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

  • Warning Line 878, Column 9274: NET-enabling start-tag requires SHORTTAG YES
    …/banners/recruiting_2.jpg" border="0" /></A><A onclick="linkCode('pr.hp.bnr.to…

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

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

  • Warning Line 878, Column 9433: NET-enabling start-tag requires SHORTTAG YES
    …dia.ru/a/15/banner_PR.gif" border="0" /></A></div></div><div id="nrdp"><div cl…

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

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

  • Warning Line 878, Column 9672: NET-enabling start-tag requires SHORTTAG YES
    ….ru/a/16/nrdp_465x280.jpg" border="0" /></A> </div></div><div class="clr"></di…

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

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

  • Warning Line 878, Column 9988: NET-enabling start-tag requires SHORTTAG YES
    …avonmedia.ru/a/02/MA+.jpg" border="0" /></A></div></div><div id="bcc"><div cla…

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

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

  • Warning Line 878, Column 10287: NET-enabling start-tag requires SHORTTAG YES
    …mages/banners/glamour.jpg" border="0" /></A> </div></div><div id="video"><div …

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

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

  • Warning Line 878, Column 10600: cannot generate system identifier for general entity "rel"
    …ie.com/embed/4U9C-xq_aDc?wmode=opaque&rel=0" frameborder="0" allowfullscreen><…

    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 878, Column 10600: general entity "rel" not defined and no default entity
    …ie.com/embed/4U9C-xq_aDc?wmode=opaque&rel=0" frameborder="0" allowfullscreen><…

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

  • Error Line 878, Column 10603: reference to entity "rel" for which no system identifier could be generated
    …com/embed/4U9C-xq_aDc?wmode=opaque&rel=0" frameborder="0" allowfullscreen></if…

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

  • Info Line 878, Column 10599: entity was defined here
    …kie.com/embed/4U9C-xq_aDc?wmode=opaque&rel=0" frameborder="0" allowfullscreen>…
  • Error Line 878, Column 10638: "ALLOWFULLSCREEN" is not a member of a group specified for any attribute
    …rel=0" frameborder="0" allowfullscreen></iframe><A onclick="linkCode('pr.hp.bn…
  • Warning Line 878, Column 10854: NET-enabling start-tag requires SHORTTAG YES
    …ages/button/all_video.png" border="0" /></A> </div></div><div class="clr"></di…

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

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

  • Warning Line 878, Column 11208: NET-enabling start-tag requires SHORTTAG YES
    …gn_images/brands/luxe.png" border="0" /></A></li><li><A onclick="linkCode('pr.…

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

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

  • Warning Line 878, Column 11392: NET-enabling start-tag requires SHORTTAG YES
    …ages/brands/avon_baby.png" border="0" /></A></li><li><A onclick="linkCode('pr.…

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

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

  • Warning Line 878, Column 11573: NET-enabling start-tag requires SHORTTAG YES
    …gn_images/brands/anew.png" border="0" /></A></li><li><A onclick="linkCode('pr.…

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

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

  • Warning Line 878, Column 11766: NET-enabling start-tag requires SHORTTAG YES
    …ges/brands/colortrend.png" border="0" /></A></li><li><A onclick="linkCode('pr.…

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

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

  • Warning Line 878, Column 11962: NET-enabling start-tag requires SHORTTAG YES
    …ages/brands/solutions.png" border="0" /></A></li><li><A onclick="linkCode('pr.…

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

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

  • Warning Line 878, Column 12184: NET-enabling start-tag requires SHORTTAG YES
    …ds/advance_techniques.png" border="0" /></A></li><li><A onclick="linkCode('pr.…

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

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

  • Warning Line 878, Column 12382: NET-enabling start-tag requires SHORTTAG YES
    …ages/brands/outspoken.png" border="0" /></A></li><li><A onclick="linkCode('pr.…

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

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

  • Warning Line 878, Column 12628: NET-enabling start-tag requires SHORTTAG YES
    …nds/christian_lacroix.png" border="0" /></A></li><li><A onclick="linkCode('pr.…

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

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

  • Warning Line 878, Column 12852: NET-enabling start-tag requires SHORTTAG YES
    …mages/brands/in_bloom.png" border="0" /></A></li></ul></div><div class="clr"><…

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

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

  • Warning Line 878, Column 13068: NET-enabling start-tag requires SHORTTAG YES
    …ign_images/howtoorder.png" border="0" /> </div><div class="three_col"><div cla…

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

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

  • Warning Line 878, Column 13288: cannot generate system identifier for general entity "acNo"
    …lineOrderEBrochure.page?custRepOrdr=1&acNo=MTIxMjEzMjI=&source=V0lER1Q=&c=vbro…

    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 878, Column 13288: general entity "acNo" not defined and no default entity
    …lineOrderEBrochure.page?custRepOrdr=1&acNo=MTIxMjEzMjI=&source=V0lER1Q=&c=vbro…

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

  • Error Line 878, Column 13292: reference to entity "acNo" for which no system identifier could be generated
    …OrderEBrochure.page?custRepOrdr=1&acNo=MTIxMjEzMjI=&source=V0lER1Q=&c=vbrochur…

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

  • Info Line 878, Column 13287: entity was defined here
    …nlineOrderEBrochure.page?custRepOrdr=1&acNo=MTIxMjEzMjI=&source=V0lER1Q=&c=vbr…
  • Warning Line 878, Column 13306: cannot generate system identifier for general entity "source"
    ….page?custRepOrdr=1&acNo=MTIxMjEzMjI=&source=V0lER1Q=&c=vbrochure&s=brochurewi…

    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 878, Column 13306: general entity "source" not defined and no default entity
    ….page?custRepOrdr=1&acNo=MTIxMjEzMjI=&source=V0lER1Q=&c=vbrochure&s=brochurewi…

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

  • Error Line 878, Column 13312: reference to entity "source" for which no system identifier could be generated
    …custRepOrdr=1&acNo=MTIxMjEzMjI=&source=V0lER1Q=&c=vbrochure&s=brochurewidget_v…

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

  • Info Line 878, Column 13305: entity was defined here
    …e.page?custRepOrdr=1&acNo=MTIxMjEzMjI=&source=V0lER1Q=&c=vbrochure&s=brochurew…
  • Warning Line 878, Column 13322: cannot generate system identifier for general entity "c"
    …r=1&acNo=MTIxMjEzMjI=&source=V0lER1Q=&c=vbrochure&s=brochurewidget_vbrochure" …

    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 878, Column 13322: general entity "c" not defined and no default entity
    …r=1&acNo=MTIxMjEzMjI=&source=V0lER1Q=&c=vbrochure&s=brochurewidget_vbrochure" …

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

  • Error Line 878, Column 13323: reference to entity "c" for which no system identifier could be generated
    …=1&acNo=MTIxMjEzMjI=&source=V0lER1Q=&c=vbrochure&s=brochurewidget_vbrochure" 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 878, Column 13321: entity was defined here
    …dr=1&acNo=MTIxMjEzMjI=&source=V0lER1Q=&c=vbrochure&s=brochurewidget_vbrochure"…
  • Warning Line 878, Column 13334: cannot generate system identifier for general entity "s"
    …xMjEzMjI=&source=V0lER1Q=&c=vbrochure&s=brochurewidget_vbrochure" target="_top…

    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 878, Column 13334: general entity "s" not defined and no default entity
    …xMjEzMjI=&source=V0lER1Q=&c=vbrochure&s=brochurewidget_vbrochure" target="_top…

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

  • Error Line 878, Column 13335: reference to entity "s" for which no system identifier could be generated
    …MjEzMjI=&source=V0lER1Q=&c=vbrochure&s=brochurewidget_vbrochure" target="_top"…

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

  • Info Line 878, Column 13333: entity was defined here
    …IxMjEzMjI=&source=V0lER1Q=&c=vbrochure&s=brochurewidget_vbrochure" target="_to…
  • Warning Line 878, Column 13698: NET-enabling start-tag requires SHORTTAG YES
    …mages/button/findarep.png" border="0" /></A> </div><div class="col last"><p>Ес…

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

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

  • Warning Line 878, Column 13747: NET-enabling start-tag requires SHORTTAG YES
    …v><div class="col last"><p>Если ты<br />Представитель Avon:</p><A onclick="lin…

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

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

  • Warning Line 878, Column 13990: NET-enabling start-tag requires SHORTTAG YES
    …ges/button/placeorder.png" border="0" /></A> </div><div class="clr"></div></di…

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

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

  • Warning Line 878, Column 14232: NET-enabling start-tag requires SHORTTAG YES
    …gn_images/bestsellers.png" border="0" /></div><div id="bestsellers_carousel"><…

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

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

  • Error Line 878, Column 14369: reference to entity "cmpgnYrNr" for which no system identifier could be generated
    …Suite/eBrochure.page?index=1&cmpgnYrNr=201302&pageNo=58" target="_top"><img sr…

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

  • Info Line 878, Column 5638: entity was defined here
    …avon.ru/PRSuite/eBrochure.page?index=1&cmpgnYrNr=201302&pageNo=104" onclick="l…
  • Error Line 878, Column 14383: reference to entity "pageNo" for which no system identifier could be generated
    …e.page?index=1&cmpgnYrNr=201302&pageNo=58" target="_top"><img src="http://avon…

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

  • Info Line 878, Column 5655: entity was defined here
    …Brochure.page?index=1&cmpgnYrNr=201302&pageNo=104" onclick="linkCode('pr.hp.mr…
  • Warning Line 878, Column 14460: NET-enabling start-tag requires SHORTTAG YES
    …nmedia.ru/a/02/best/1.png" border="0" /></A></li><li><A onclick="linkCode('pr.…

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

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

  • Error Line 878, Column 14565: reference to entity "cmpgnYrNr" for which no system identifier could be generated
    …Suite/eBrochure.page?index=1&cmpgnYrNr=201302&pageNo=80" target="_top"><img sr…

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

  • Info Line 878, Column 5638: entity was defined here
    …avon.ru/PRSuite/eBrochure.page?index=1&cmpgnYrNr=201302&pageNo=104" onclick="l…
  • Error Line 878, Column 14579: reference to entity "pageNo" for which no system identifier could be generated
    …e.page?index=1&cmpgnYrNr=201302&pageNo=80" target="_top"><img src="http://avon…

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

  • Info Line 878, Column 5655: entity was defined here
    …Brochure.page?index=1&cmpgnYrNr=201302&pageNo=104" onclick="linkCode('pr.hp.mr…
  • Warning Line 878, Column 14656: NET-enabling start-tag requires SHORTTAG YES
    …nmedia.ru/a/02/best/2.png" border="0" /></A></li><li><A onclick="linkCode('pr.…

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

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

  • Error Line 878, Column 14761: reference to entity "cmpgnYrNr" for which no system identifier could be generated
    …Suite/eBrochure.page?index=1&cmpgnYrNr=201302&pageNo=164" target="_top"><img s…

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

  • Info Line 878, Column 5638: entity was defined here
    …avon.ru/PRSuite/eBrochure.page?index=1&cmpgnYrNr=201302&pageNo=104" onclick="l…
  • Error Line 878, Column 14775: reference to entity "pageNo" for which no system identifier could be generated
    …e.page?index=1&cmpgnYrNr=201302&pageNo=164" target="_top"><img src="http://avo…

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

  • Info Line 878, Column 5655: entity was defined here
    …Brochure.page?index=1&cmpgnYrNr=201302&pageNo=104" onclick="linkCode('pr.hp.mr…
  • Warning Line 878, Column 14853: NET-enabling start-tag requires SHORTTAG YES
    …nmedia.ru/a/02/best/3.png" border="0" /></A></li><li><A onclick="linkCode('pr.…

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

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

  • Error Line 878, Column 14958: reference to entity "cmpgnYrNr" for which no system identifier could be generated
    …Suite/eBrochure.page?index=1&cmpgnYrNr=201302&pageNo=188" target="_top"><img s…

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

  • Info Line 878, Column 5638: entity was defined here
    …avon.ru/PRSuite/eBrochure.page?index=1&cmpgnYrNr=201302&pageNo=104" onclick="l…
  • Error Line 878, Column 14972: reference to entity "pageNo" for which no system identifier could be generated
    …e.page?index=1&cmpgnYrNr=201302&pageNo=188" target="_top"><img src="http://avo…

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

  • Info Line 878, Column 5655: entity was defined here
    …Brochure.page?index=1&cmpgnYrNr=201302&pageNo=104" onclick="linkCode('pr.hp.mr…
  • Warning Line 878, Column 15050: NET-enabling start-tag requires SHORTTAG YES
    …nmedia.ru/a/02/best/4.png" border="0" /></A></li></ul></div><div class="clr"><…

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

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

  • Warning Line 878, Column 15215: NET-enabling start-tag requires SHORTTAG YES
    …/redesign_images/news.png" border="0" /></div><div class="two_col"><div class=…

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

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

  • Error Line 878, Column 15372: reference to entity "cmpgnYrNr" for which no system identifier could be generated
    …Suite/eBrochure.page?index=1&cmpgnYrNr=201302&pageNo=2" target="_top"><img src…

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

  • Info Line 878, Column 5638: entity was defined here
    …avon.ru/PRSuite/eBrochure.page?index=1&cmpgnYrNr=201302&pageNo=104" onclick="l…
  • Error Line 878, Column 15386: reference to entity "pageNo" for which no system identifier could be generated
    …e.page?index=1&cmpgnYrNr=201302&pageNo=2" target="_top"><img src="http://avonm…

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

  • Info Line 878, Column 5655: entity was defined here
    …Brochure.page?index=1&cmpgnYrNr=201302&pageNo=104" onclick="linkCode('pr.hp.mr…
  • Warning Line 878, Column 15458: NET-enabling start-tag requires SHORTTAG YES
    …/avonmedia.ru/a/02/n1.jpg" border="0" /></A> </div><div class="news_short"><di…

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

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

  • Error Line 878, Column 15604: reference to entity "cmpgnYrNr" for which no system identifier could be generated
    …Suite/eBrochure.page?index=1&cmpgnYrNr=201302&pageNo=2" target="_top">Ирина Ше…

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

  • Info Line 878, Column 5638: entity was defined here
    …avon.ru/PRSuite/eBrochure.page?index=1&cmpgnYrNr=201302&pageNo=104" onclick="l…
  • Error Line 878, Column 15618: reference to entity "pageNo" for which no system identifier could be generated
    …e.page?index=1&cmpgnYrNr=201302&pageNo=2" target="_top">Ирина Шейк Представляе…

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

  • Info Line 878, Column 5655: entity was defined here
    …Brochure.page?index=1&cmpgnYrNr=201302&pageNo=104" onclick="linkCode('pr.hp.mr…
  • Error Line 878, Column 16009: reference to entity "cmpgnYrNr" for which no system identifier could be generated
    …Suite/eBrochure.page?index=1&cmpgnYrNr=201302&pageNo=6" target="_top"><img src…

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

  • Info Line 878, Column 5638: entity was defined here
    …avon.ru/PRSuite/eBrochure.page?index=1&cmpgnYrNr=201302&pageNo=104" onclick="l…
  • Error Line 878, Column 16023: reference to entity "pageNo" for which no system identifier could be generated
    …e.page?index=1&cmpgnYrNr=201302&pageNo=6" target="_top"><img src="http://avonm…

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

  • Info Line 878, Column 5655: entity was defined here
    …Brochure.page?index=1&cmpgnYrNr=201302&pageNo=104" onclick="linkCode('pr.hp.mr…
  • Warning Line 878, Column 16095: NET-enabling start-tag requires SHORTTAG YES
    …/avonmedia.ru/a/02/n2.jpg" border="0" /></A> </div><div class="news_short"><di…

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

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

  • Error Line 878, Column 16241: reference to entity "cmpgnYrNr" for which no system identifier could be generated
    …Suite/eBrochure.page?index=1&cmpgnYrNr=201302&pageNo=6" target="_top">Венеция …

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

  • Info Line 878, Column 5638: entity was defined here
    …avon.ru/PRSuite/eBrochure.page?index=1&cmpgnYrNr=201302&pageNo=104" onclick="l…
  • Error Line 878, Column 16255: reference to entity "pageNo" for which no system identifier could be generated
    …e.page?index=1&cmpgnYrNr=201302&pageNo=6" target="_top">Венеция ждет! Покупайт…

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

  • Info Line 878, Column 5655: entity was defined here
    …Brochure.page?index=1&cmpgnYrNr=201302&pageNo=104" onclick="linkCode('pr.hp.mr…
  • Warning Line 878, Column 16738: NET-enabling start-tag requires SHORTTAG YES
    …/avonmedia.ru/a/02/n3.jpg" border="0" /></A> </div><div class="news_short"><di…

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

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

  • Error Line 878, Column 17123: end tag for element "DIV" which is not open
    …те забавный тест на avon.ru</div></div></div><div class="col last"><div class=…

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

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

  • Error Line 878, Column 17129: end tag for element "DIV" which is not open
    …авный тест на avon.ru</div></div></div><div class="col last"><div class="news_…

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

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

  • Error Line 878, Column 17263: reference to entity "cmpgnYrNr" for which no system identifier could be generated
    …Suite/eBrochure.page?index=1&cmpgnYrNr=201302&pageNo=104" target="_top"><img s…

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

  • Info Line 878, Column 5638: entity was defined here
    …avon.ru/PRSuite/eBrochure.page?index=1&cmpgnYrNr=201302&pageNo=104" onclick="l…
  • Error Line 878, Column 17277: reference to entity "pageNo" for which no system identifier could be generated
    …e.page?index=1&cmpgnYrNr=201302&pageNo=104" target="_top"><img src="http://avo…

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

  • Info Line 878, Column 5655: entity was defined here
    …Brochure.page?index=1&cmpgnYrNr=201302&pageNo=104" onclick="linkCode('pr.hp.mr…
  • Warning Line 878, Column 17351: NET-enabling start-tag requires SHORTTAG YES
    …/avonmedia.ru/a/02/n4.jpg" border="0" /></A> </div><div class="news_short"><di…

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

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

  • Error Line 878, Column 17497: reference to entity "cmpgnYrNr" for which no system identifier could be generated
    …Suite/eBrochure.page?index=1&cmpgnYrNr=201302&pageNo=104" target="_top">Выбери…

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

  • Info Line 878, Column 5638: entity was defined here
    …avon.ru/PRSuite/eBrochure.page?index=1&cmpgnYrNr=201302&pageNo=104" onclick="l…
  • Error Line 878, Column 17511: reference to entity "pageNo" for which no system identifier could be generated
    …e.page?index=1&cmpgnYrNr=201302&pageNo=104" target="_top">Выбери романтичные п…

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

  • Info Line 878, Column 5655: entity was defined here
    …Brochure.page?index=1&cmpgnYrNr=201302&pageNo=104" onclick="linkCode('pr.hp.mr…
  • Error Line 878, Column 17857: reference to entity "cmpgnYrNr" for which no system identifier could be generated
    …Suite/eBrochure.page?index=1&cmpgnYrNr=201302&pageNo=196" target="_top"><img s…

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

  • Info Line 878, Column 5638: entity was defined here
    …avon.ru/PRSuite/eBrochure.page?index=1&cmpgnYrNr=201302&pageNo=104" onclick="l…
  • Error Line 878, Column 17871: reference to entity "pageNo" for which no system identifier could be generated
    …e.page?index=1&cmpgnYrNr=201302&pageNo=196" target="_top"><img src="http://avo…

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

  • Info Line 878, Column 5655: entity was defined here
    …Brochure.page?index=1&cmpgnYrNr=201302&pageNo=104" onclick="linkCode('pr.hp.mr…
  • Warning Line 878, Column 17945: NET-enabling start-tag requires SHORTTAG YES
    …/avonmedia.ru/a/02/n5.jpg" border="0" /></A> </div><div class="news_short"><di…

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

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

  • Error Line 878, Column 18091: reference to entity "cmpgnYrNr" for which no system identifier could be generated
    …Suite/eBrochure.page?index=1&cmpgnYrNr=201302&pageNo=196" target="_top">Специа…

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

  • Info Line 878, Column 5638: entity was defined here
    …avon.ru/PRSuite/eBrochure.page?index=1&cmpgnYrNr=201302&pageNo=104" onclick="l…
  • Error Line 878, Column 18105: reference to entity "pageNo" for which no system identifier could be generated
    …e.page?index=1&cmpgnYrNr=201302&pageNo=196" target="_top">Специальное предложе…

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

  • Info Line 878, Column 5655: entity was defined here
    …Brochure.page?index=1&cmpgnYrNr=201302&pageNo=104" onclick="linkCode('pr.hp.mr…
  • Error Line 878, Column 18407: reference to entity "cmpgnYrNr" for which no system identifier could be generated
    …Suite/eBrochure.page?index=1&cmpgnYrNr=201302&pageNo=10" target="_blank"><img …

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

  • Info Line 878, Column 5638: entity was defined here
    …avon.ru/PRSuite/eBrochure.page?index=1&cmpgnYrNr=201302&pageNo=104" onclick="l…
  • Error Line 878, Column 18421: reference to entity "pageNo" for which no system identifier could be generated
    …e.page?index=1&cmpgnYrNr=201302&pageNo=10" target="_blank"><img src="http://av…

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

  • Info Line 878, Column 5655: entity was defined here
    …Brochure.page?index=1&cmpgnYrNr=201302&pageNo=104" onclick="linkCode('pr.hp.mr…
  • Warning Line 878, Column 18496: NET-enabling start-tag requires SHORTTAG YES
    …/avonmedia.ru/a/02/n6.jpg" border="0" /></A> </div><div class="news_short"><di…

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

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

  • Error Line 878, Column 18642: reference to entity "cmpgnYrNr" for which no system identifier could be generated
    …Suite/eBrochure.page?index=1&cmpgnYrNr=201302&pageNo=10" target="_blank">Новая…

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

  • Info Line 878, Column 5638: entity was defined here
    …avon.ru/PRSuite/eBrochure.page?index=1&cmpgnYrNr=201302&pageNo=104" onclick="l…
  • Error Line 878, Column 18656: reference to entity "pageNo" for which no system identifier could be generated
    …e.page?index=1&cmpgnYrNr=201302&pageNo=10" target="_blank">Новая коллекция для…

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

  • Info Line 878, Column 5655: entity was defined here
    …Brochure.page?index=1&cmpgnYrNr=201302&pageNo=104" onclick="linkCode('pr.hp.mr…
  • Error Line 878, Column 18832: end tag for element "DIV" which is not open
    …div></div><div class="clr"></div></div><div id="all_news"><A onclick="linkCode…

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

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

  • Warning Line 878, Column 19034: NET-enabling start-tag requires SHORTTAG YES
    …mages/button/all_news.png" border="0" /></A></div></div></div><div id="socmedi…

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

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

  • Error Line 878, Column 19051: end tag for element "DIV" which is not open
    …news.png" border="0" /></A></div></div></div><div id="socmedia_block"><!-- Add…

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

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

  • Error Line 878, Column 19057: end tag for element "DIV" which is not open
    …ng" border="0" /></A></div></div></div><div id="socmedia_block"><!-- AddThis B…

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

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

  • Warning Line 878, Column 19898: cannot generate system identifier for general entity "amp"
    …://www.addthis.com/bookmark.php?v=250&amp;pubid=ra-4d91b5ae50a40589" class="ad…

    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 878, Column 19898: general entity "amp" not defined and no default entity
    …://www.addthis.com/bookmark.php?v=250&amp;pubid=ra-4d91b5ae50a40589" class="ad…

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

  • Error Line 878, Column 19901: reference to entity "amp" for which no system identifier could be generated
    …www.addthis.com/bookmark.php?v=250&amp;pubid=ra-4d91b5ae50a40589" class="addth…

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

  • Info Line 878, Column 19897: entity was defined here
    …p://www.addthis.com/bookmark.php?v=250&amp;pubid=ra-4d91b5ae50a40589" class="a…
  • Warning Line 878, Column 20283: cannot generate system identifier for general entity "st._surl"
    …//odnoklassniki.ru/dk?st.cmd=addShare&st._surl={{url}}&title={{title}}",		icon…

    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 878, Column 20283: general entity "st._surl" not defined and no default entity
    …//odnoklassniki.ru/dk?st.cmd=addShare&st._surl={{url}}&title={{title}}",		icon…

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

  • Error Line 878, Column 20291: reference to entity "st._surl" for which no system identifier could be generated
    …assniki.ru/dk?st.cmd=addShare&st._surl={{url}}&title={{title}}",		icon: "http:…

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

  • Info Line 878, Column 20282: entity was defined here
    …://odnoklassniki.ru/dk?st.cmd=addShare&st._surl={{url}}&title={{title}}",		ico…
  • Warning Line 878, Column 20300: cannot generate system identifier for general entity "title"
    …u/dk?st.cmd=addShare&st._surl={{url}}&title={{title}}",		icon: "http://avonmed…

    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 878, Column 20300: general entity "title" not defined and no default entity
    …u/dk?st.cmd=addShare&st._surl={{url}}&title={{title}}",		icon: "http://avonmed…

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

  • Error Line 878, Column 20305: reference to entity "title" for which no system identifier could be generated
    …st.cmd=addShare&st._surl={{url}}&title={{title}}",		icon: "http://avonmedia.ru…

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

  • Info Line 878, Column 20299: entity was defined here
    …ru/dk?st.cmd=addShare&st._surl={{url}}&title={{title}}",		icon: "http://avonme…
  • Error Line 878, Column 20452: reference to entity "title" for which no system identifier could be generated
    …u/posts_add_link.xml?URL={{url}}&title={{title}}",icon: "http://avonmedia.ru/n…

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

  • Info Line 878, Column 20299: entity was defined here
    …ru/dk?st.cmd=addShare&st._surl={{url}}&title={{title}}",		icon: "http://avonme…
  • Error Line 878, Column 21135: reference to entity "amp" for which no system identifier could be generated
    …2Fwww.facebook.com%2FAvonRussia%2F&amp;width=313&amp;height=258&amp;colorschem…

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

  • Info Line 878, Column 19897: entity was defined here
    …p://www.addthis.com/bookmark.php?v=250&amp;pubid=ra-4d91b5ae50a40589" class="a…
  • Error Line 878, Column 21149: reference to entity "amp" for which no system identifier could be generated
    ….com%2FAvonRussia%2F&amp;width=313&amp;height=258&amp;colorscheme=light&amp;sh…

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

  • Info Line 878, Column 19897: entity was defined here
    …p://www.addthis.com/bookmark.php?v=250&amp;pubid=ra-4d91b5ae50a40589" class="a…
  • Error Line 878, Column 21164: reference to entity "amp" for which no system identifier could be generated
    …ia%2F&amp;width=313&amp;height=258&amp;colorscheme=light&amp;show_faces=true&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 878, Column 19897: entity was defined here
    …p://www.addthis.com/bookmark.php?v=250&amp;pubid=ra-4d91b5ae50a40589" class="a…
  • Error Line 878, Column 21186: reference to entity "amp" for which no system identifier could be generated
    …p;height=258&amp;colorscheme=light&amp;show_faces=true&amp;border_color&amp;st…

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

  • Info Line 878, Column 19897: entity was defined here
    …p://www.addthis.com/bookmark.php?v=250&amp;pubid=ra-4d91b5ae50a40589" class="a…
  • Error Line 878, Column 21206: reference to entity "amp" for which no system identifier could be generated
    …orscheme=light&amp;show_faces=true&amp;border_color&amp;stream=false&amp;heade…

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

  • Info Line 878, Column 19897: entity was defined here
    …p://www.addthis.com/bookmark.php?v=250&amp;pubid=ra-4d91b5ae50a40589" class="a…
  • Error Line 878, Column 21223: reference to entity "amp" for which no system identifier could be generated
    …p;show_faces=true&amp;border_color&amp;stream=false&amp;header=false&amp;appId…

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

  • Info Line 878, Column 19897: entity was defined here
    …p://www.addthis.com/bookmark.php?v=250&amp;pubid=ra-4d91b5ae50a40589" class="a…
  • Error Line 878, Column 21240: reference to entity "amp" for which no system identifier could be generated
    …&amp;border_color&amp;stream=false&amp;header=false&amp;appId=196097110436116"…

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

  • Info Line 878, Column 19897: entity was defined here
    …p://www.addthis.com/bookmark.php?v=250&amp;pubid=ra-4d91b5ae50a40589" class="a…
  • Error Line 878, Column 21257: reference to entity "amp" for which no system identifier could be generated
    …&amp;stream=false&amp;header=false&amp;appId=196097110436116" id="fb_groups" s…

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

  • Info Line 878, Column 19897: entity was defined here
    …p://www.addthis.com/bookmark.php?v=250&amp;pubid=ra-4d91b5ae50a40589" class="a…
  • Warning Line 878, Column 21857: NET-enabling start-tag requires SHORTTAG YES
    …ges/footer/production.png" border="0" /><ul><li><A href="/PRSuite/avon_select.…

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

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

  • Warning Line 878, Column 22211: NET-enabling start-tag requires SHORTTAG YES
    …n_images/footer/about.png" border="0" /><ul><li><A href="/PRSuite/avon_about.p…

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

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

  • Warning Line 878, Column 22592: NET-enabling start-tag requires SHORTTAG YES
    …_images/footer/career.png" border="0" /><ul><li><A href="/PRSuite/dreamJobAppl…

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

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

  • Warning Line 878, Column 23004: NET-enabling start-tag requires SHORTTAG YES
    …ign_images/footer/buy.png" border="0" /><ul><li><A href="/PRSuite/avon_select.…

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

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

  • Warning Line 878, Column 23409: NET-enabling start-tag requires SHORTTAG YES
    …es/footer/interactive.png" border="0" /><ul><li><A href="http://avonsocialtool…

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

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

  • Error Line 878, Column 23605: reference to entity "acNo" for which no system identifier could be generated
    …OrderEBrochure.page?custRepOrdr=1&acNo=MTIxMjEzMjI=&source=V0lER1Q=&c=vbrochur…

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

  • Info Line 878, Column 13287: entity was defined here
    …nlineOrderEBrochure.page?custRepOrdr=1&acNo=MTIxMjEzMjI=&source=V0lER1Q=&c=vbr…
  • Error Line 878, Column 23625: reference to entity "source" for which no system identifier could be generated
    …custRepOrdr=1&acNo=MTIxMjEzMjI=&source=V0lER1Q=&c=vbrochure&s=brochurewidget_v…

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

  • Info Line 878, Column 13305: entity was defined here
    …e.page?custRepOrdr=1&acNo=MTIxMjEzMjI=&source=V0lER1Q=&c=vbrochure&s=brochurew…
  • Error Line 878, Column 23636: reference to entity "c" for which no system identifier could be generated
    …=1&acNo=MTIxMjEzMjI=&source=V0lER1Q=&c=vbrochure&s=brochurewidget_vbrochure" 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 878, Column 13321: entity was defined here
    …dr=1&acNo=MTIxMjEzMjI=&source=V0lER1Q=&c=vbrochure&s=brochurewidget_vbrochure"…
  • Error Line 878, Column 23648: reference to entity "s" for which no system identifier could be generated
    …MjEzMjI=&source=V0lER1Q=&c=vbrochure&s=brochurewidget_vbrochure" target="_top"…

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

  • Info Line 878, Column 13333: entity was defined here
    …IxMjEzMjI=&source=V0lER1Q=&c=vbrochure&s=brochurewidget_vbrochure" target="_to…
  • Warning Line 878, Column 24004: NET-enabling start-tag requires SHORTTAG YES
    …een" rel="stylesheet" type="text/css" /><script type="text/javascript" src="ht…

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

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

  • Error Line 878, Column 24353: "ALLOWFULLSCREEN" is not a member of a group specified for any attribute
    …rel=0" frameborder="0" allowfullscreen></iframe></div><div id="popup_close_vid…
  • Warning Line 878, Column 24556: NET-enabling start-tag requires SHORTTAG YES
    …rc="http://avonmedia.ru/_.gif" alt="X"/></A></div><div id="popup_go_video"><A …

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

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

  • Warning Line 878, Column 24762: NET-enabling start-tag requires SHORTTAG YES
    …onmedia.ru/_.gif" alt="Заполни анкету"/></A></div></div><!---popup_video--></d…

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

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

  • Error Line 878, Column 24804: end tag for element "DIV" which is not open
    …A></div></div><!---popup_video--></div><!-------------------------------------…

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

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

  • Error Line 1025, Column 172: invalid comment declaration: found name start character outside comment but inside comment declaration
    …atic/js/larisa4ever.js"></script><!-- Yandex.Metrika counter --><script type="…
  • Info Line 878, Column 24805: comment declaration started here
    …></div></div><!---popup_video--></div><!--------------------------------------…
  • Error Line 1025, Column 838: end tag for element "SCRIPT" which is not open
    …, "yandex_metrika_callbacks");</script><noscript><div><img src="//mc.yandex.ru…

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

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

  • Warning Line 1025, Column 942: NET-enabling start-tag requires SHORTTAG YES
    …ition:absolute; left:-9999px;" alt="" /></div></noscript><!-- /Yandex.Metrika …

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

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

  • Error Line 1025, Column 999: end tag for element "FONT" which is not open
    …9999px;" alt="" /></div></noscript><!-- /Yandex.Metrika counter --></font></td>

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

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

  • Warning Line 1028, Column 47: NET-enabling start-tag requires SHORTTAG YES
    	<INPUT TYPE="HIDDEN" NAME="CURR_URL" VALUE=""/>

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

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

  • Error Line 1034, Column 7: end tag for element "FORM" which is not open
    </form>

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

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

  • Error Line 1039, Column 11: end tag for element "TD" which is not open
          </td>

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

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

  • Error Line 1040, Column 7: end tag for element "TR" which is not open
      </tr> 

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

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

  • Error Line 1041, Column 10: end tag for element "TABLE" which is not open
    		</table>

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

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

  • Error Line 1042, Column 7: end tag for element "TD" which is not open
    		</td>

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

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

  • Error Line 1043, Column 6: end tag for element "TR" which is not open
    	</tr>

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

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

  • Error Line 1044, Column 8: end tag for element "TABLE" which is not open
    </table>

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

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

  • Error Line 1045, Column 7: end tag for element "BODY" which is not open
    </body>

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

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

  • Error Line 1046, Column 7: end tag for element "HTML" which is not open
    </html>

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

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

Visitor Analysis

Daily Visitor
  • 4.900 visits
Daily Visitor

In Page Analysis