enelenergia.it

Enel Energia è la società di Enel per la fornitura di energia elettrica e gas sul mercato libero. ...

Display Widget for this domain on your website. Click Here
This data was last updated from 09-07-2013 09:19:39  (update).

Overview Info

  • Domain Name
    enelenergia.it
  • Favicon
  • Alexa Rank
    #35103
  • Google Page Rank
    PR 6
  • Ip Address
    146.133.2.119
  • Page Size
    39.5 KB
  • Images
    0 GIF, 0 JPG, 0 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    1 1 16 12 0 7

Website Meta Analysis



  • Title
    Home - Enel Energia
  • Meta Keyword
  • Meta Description
    Enel Energia è la società di Enel per la fornitura di energia elettrica e gas sul mercato libero.

Technical Analysis



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

Hyper Text Transfer Protocol (HTTP) header show data header response from enelenergia.it.

HTML Analysis

  • connection: Keep-Alive
  • date: Tue, 09 Jul 2013 09:19:28 GMT
  • content-type: text/html; charset=UTF-8
  • cache-control: no-store
  • last-modified: Tue, 09 Jul 2013 09:19:28 GMT
  • host_service: FutureTenseContentServer:11.1.1.6.0
  • x-powered-by: Servlet/2.5 JSP/2.1
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA

*********************************************************************
* Please note that the following result could be a subgroup of *
* the data contained in the database. *
* *
* Additional information can be visualized at: *
* http://www.nic.it/cgi-bin/Whois/whois.cgi *
*********************************************************************

Domain: enelenergia.it
Status: ok
Created: 2002-12-30 00:00:00
Last Update: 2013-01-15 00:52:55
Expire Date: 2013-12-30

Registrant
Name: Enel S.p.A.
Organization: Enel S.p.A.
ContactID: ENEL1
Address: viale Regina Margherita, 137
Roma
00198
RM
IT
Created: 2007-03-01 10:26:49
Last Update: 2011-08-01 10:27:33

Admin Contact
Name: Salvatore Cardillo
Organization: Enel Servizi S.r.l.
ContactID: SC4774
Address: viale Regina Margherita, 137
Roma
00198
RM
IT
Created: 2002-02-08 00:00:00
Last Update: 2011-08-01 10:27:33

Technical Contacts
Name: Alberto Fiorini
Organization: Enel Servizi S.r.l.
ContactID: AF9431
Address: V.le Italia, 26
Sesto San Giovanni
20099
MI
IT
Created: 2003-03-05 00:00:00
Last Update: 2011-08-01 10:27:33

Name: Diego Fiorucci
ContactID: DF843
Address: V.le Italia, 26
Sesto San Giovanni
20099
MI
IT
Created: 2003-03-05 00:00:00
Last Update: 2011-08-01 10:27:33

Name: Luca Chiari
ContactID: LC4523
Address: V.le Italia, 26
Sesto San Giovanni
20099
MI
IT
Created: 2003-03-05 00:00:00
Last Update: 2011-08-01 10:27:33

Name: Valerio Verona
ContactID: VV500
Address: V.le Italia, 26
Sesto San Giovanni
20099
MI
IT
Created: 2003-03-05 00:00:00
Last Update: 2011-08-01 10:27:33

Registrar
Organization: Enel Servizi S.r.l.
Name: ENEL-REG
Web: http://www.enel.com

Nameservers
dns.enel.it
bdns.enel.it
cdns.enel.it

DNS Analysis


DNS servers
dns.enel.it [146.133.2.20]
cdns.enel.it [146.133.226.5]
bdns.enel.it [146.133.2.21]


DNS Records

Answer records
enelenergia.it SOA
server: dns.enel.it
email: boxdns@enel.it
serial: 2013011401
refresh: 7200
retry: 1800
expire: 2592000
minimum ttl: 7200
7200s
enelenergia.it NS  bdns.enel.it 7200s
enelenergia.it NS  cdns.enel.it 7200s
enelenergia.it NS  dns.enel.it 7200s
enelenergia.it A 146.133.2.119 7200s
enelenergia.it MX
preference: 50
exchange: relaya.enel.it
7200s
enelenergia.it MX
preference: 50
exchange: relayb.enel.it
7200s
enelenergia.it MX
preference: 50
exchange: relayc.enel.it
7200s
enelenergia.it MX
preference: 50
exchange: relayd.enel.it
7200s
enelenergia.it MX
preference: 10
exchange: cluster8.eu.messagelabs.com
7200s
enelenergia.it MX
preference: 10
exchange: cluster8a.eu.messagelabs.com
7200s

Authority records

Additional records
dns.enel.it A 146.133.2.20 7200s
bdns.enel.it A 146.133.2.21 7200s
cdns.enel.it A 146.133.226.5 7200s
relaya.enel.it A 146.133.2.231 7200s
relayb.enel.it A 146.133.2.232 7200s
relayc.enel.it A 146.133.226.32 7200s
relayd.enel.it A 146.133.226.34 7200s

IP 146.133.2.119 Analysis

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

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 202 Errors
  • 214 Warnings
Ratio Text/Html
  • 0.7074092368486046
Message Error
  • Error Line 14, Column 48: required attribute "type" not specified
    <script src="/cs/wemresources/js/WemContext.js"></script>

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

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

  • Error Line 15, Column 44: required attribute "type" not specified
    <script src="/cs/wemresources/js/wemxdm.js"></script>

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

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

  • Error Line 28, Column 8: required attribute "type" not specified
    <script>

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

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

  • Error Line 214, Column 88: end tag for "link" omitted, but OMITTAG NO was specified
    …l="stylesheet" type="text/css" href="/cs_static/share/css/skinning/common.css">

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

  • Info Line 214, Column 1: start tag was here
    <link rel="stylesheet" type="text/css" href="/cs_static/share/css/skinning/comm…
  • Error Line 215, Column 96: end tag for "link" omitted, but OMITTAG NO was specified
    …sheet" type="text/css" href="/cs_static/share/css/skinning/layout1/layout.css">

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

  • Info Line 215, Column 1: start tag was here
    <link rel="stylesheet" type="text/css" href="/cs_static/share/css/skinning/layo…
  • Error Line 216, Column 78: end tag for "link" omitted, but OMITTAG NO was specified
    <link rel="stylesheet" type="text/css" href="/cs_static/common/css/skin.css">

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

  • Info Line 216, Column 1: start tag was here
    <link rel="stylesheet" type="text/css" href="/cs_static/common/css/skin.css">
  • Error Line 217, Column 84: end tag for "link" omitted, but OMITTAG NO was specified
    …k rel="stylesheet" type="text/css" href="/cs_static/common/css/switchlogo.css">

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

  • Info Line 217, Column 1: start tag was here
    <link rel="stylesheet" type="text/css" href="/cs_static/common/css/switchlogo.c…
  • Error Line 218, Column 78: end tag for "link" omitted, but OMITTAG NO was specified
    <link rel="stylesheet" type="text/css" href="/cs_static/common/css/form.css">

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

  • Info Line 218, Column 1: start tag was here
    <link rel="stylesheet" type="text/css" href="/cs_static/common/css/form.css">
  • Error Line 219, Column 91: end tag for "link" omitted, but OMITTAG NO was specified
    …stylesheet" type="text/css" href="/cs_static/enelenergia/common/css/popup.css">

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

  • Info Line 219, Column 1: start tag was here
    <link rel="stylesheet" type="text/css" href="/cs_static/enelenergia/common/css/…
  • Error Line 247, Column 28: there is no attribute "name"
    <form id="LogoutForm" name="LogoutForm" method="post" action="Satellite">

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

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

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

  • Error Line 248, Column 57: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    <input type="hidden" name="pagename" value="EEWrapper" />

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

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

  • Error Line 249, Column 55: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    <input type="hidden" name="site" value="EnelEnergia" />

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

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

  • Error Line 250, Column 45: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    <input type="hidden" name="c" value="Page" />

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

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

  • Error Line 251, Column 59: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    <input type="hidden" name="locale" value='1351706410412' />

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

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

  • Error Line 252, Column 78: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    <input type="hidden" name="childpagename" value="EnelEnergia/Page/EELayout" />

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

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

  • Error Line 253, Column 56: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    <input type="hidden" name="cid" value='1353090633347' />

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

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

  • Error Line 254, Column 50: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    <input type="hidden" name="logout" value="true" />	

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

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

  • Warning Line 259, Column 74: cannot generate system identifier for general entity "returnPath"
    …ogin.enel.com/adfs/ls/?wa=wsignout1.0&returnPath=http%3a%2f%2fwww.enelenergia.…

    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 259, Column 74: general entity "returnPath" not defined and no default entity
    …ogin.enel.com/adfs/ls/?wa=wsignout1.0&returnPath=http%3a%2f%2fwww.enelenergia.…

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

  • Warning Line 259, Column 84: reference not terminated by REFC delimiter
    …com/adfs/ls/?wa=wsignout1.0&returnPath=http%3a%2f%2fwww.enelenergia.it%2fmerca…

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

  • Error Line 259, Column 84: reference to entity "returnPath" for which no system identifier could be generated
    …com/adfs/ls/?wa=wsignout1.0&returnPath=http%3a%2f%2fwww.enelenergia.it%2fmerca…

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

  • Info Line 259, Column 73: entity was defined here
    …login.enel.com/adfs/ls/?wa=wsignout1.0&returnPath=http%3a%2f%2fwww.enelenergia…
  • Error Line 306, Column 85: there is no attribute "ix:url-thumbnail"
    …nel' alt='Logo Enel' ix:url-thumbnail="" ix:peso="6285" ix:dim="" ix:formato="…

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

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

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

  • Error Line 306, Column 96: there is no attribute "ix:peso"
    …ogo Enel' ix:url-thumbnail="" ix:peso="6285" ix:dim="" ix:formato="gif" ix:lin…

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

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

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

  • Error Line 306, Column 110: there is no attribute "ix:dim"
    …rl-thumbnail="" ix:peso="6285" ix:dim="" ix:formato="gif" ix:lingua="it" ix:dt…

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

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

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

  • Error Line 306, Column 124: there is no attribute "ix:formato"
    …" ix:peso="6285" ix:dim="" ix:formato="gif" ix:lingua="it" ix:dt-redaz="0001-0…

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

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

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

  • Error Line 306, Column 140: there is no attribute "ix:lingua"
    … ix:dim="" ix:formato="gif" ix:lingua="it" ix:dt-redaz="0001-01-01" ix:tag="" …

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

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

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

  • Error Line 306, Column 157: there is no attribute "ix:dt-redaz"
    …mato="gif" ix:lingua="it" ix:dt-redaz="0001-01-01" ix:tag="" xmlns:ix="http://…

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

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

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

  • Error Line 306, Column 177: there is no attribute "ix:tag"
    …="it" ix:dt-redaz="0001-01-01" ix:tag="" xmlns:ix="http://www.enel.com" src='/…

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

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

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

  • Warning Line 306, Column 248: cannot generate system identifier for general entity "blobkey"
    … src='/mercato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwher…

    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 306, Column 248: general entity "blobkey" not defined and no default entity
    … src='/mercato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwher…

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

  • Warning Line 306, Column 255: reference not terminated by REFC delimiter
    …mercato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=13535…

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

  • Warning Line 306, Column 255: reference to external entity in attribute value
    …mercato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=13535…

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

  • Error Line 306, Column 255: reference to entity "blobkey" for which no system identifier could be generated
    …mercato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=13535…

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

  • Info Line 306, Column 247: entity was defined here
    …" src='/mercato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhe…
  • Warning Line 306, Column 259: cannot generate system identifier for general entity "blobtable"
    …ato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=135352288…

    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 306, Column 259: general entity "blobtable" not defined and no default entity
    …ato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=135352288…

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

  • Warning Line 306, Column 268: reference not terminated by REFC delimiter
    …o?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522889213&ssbi…

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

  • Warning Line 306, Column 268: reference to external entity in attribute value
    …o?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522889213&ssbi…

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

  • Error Line 306, Column 268: reference to entity "blobtable" for which no system identifier could be generated
    …o?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522889213&ssbi…

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

  • Info Line 306, Column 258: entity was defined here
    …cato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=13535228…
  • Warning Line 306, Column 280: cannot generate system identifier for general entity "blobwhere"
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522889213&ssbinary=true' /…

    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 306, Column 280: general entity "blobwhere" not defined and no default entity
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522889213&ssbinary=true' /…

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

  • Warning Line 306, Column 289: reference not terminated by REFC delimiter
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522889213&ssbinary=true' />

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

  • Warning Line 306, Column 289: reference to external entity in attribute value
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522889213&ssbinary=true' />

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

  • Error Line 306, Column 289: reference to entity "blobwhere" for which no system identifier could be generated
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522889213&ssbinary=true' />

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

  • Info Line 306, Column 279: entity was defined here
    …rldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522889213&ssbinary=true' …
  • Warning Line 306, Column 304: cannot generate system identifier for general entity "ssbinary"
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522889213&ssbinary=true' />

    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 306, Column 304: general entity "ssbinary" not defined and no default entity
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522889213&ssbinary=true' />

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

  • Warning Line 306, Column 312: reference not terminated by REFC delimiter
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522889213&ssbinary=true' />

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

  • Warning Line 306, Column 312: reference to external entity in attribute value
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522889213&ssbinary=true' />

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

  • Error Line 306, Column 312: reference to entity "ssbinary" for which no system identifier could be generated
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522889213&ssbinary=true' />

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

  • Info Line 306, Column 303: entity was defined here
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522889213&ssbinary=true' />
  • Warning Line 346, Column 263: reference not terminated by REFC delimiter
    …mercato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=13535…

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

  • Warning Line 346, Column 263: reference to external entity in attribute value
    …mercato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=13535…

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

  • Error Line 346, Column 263: reference to entity "blobkey" for which no system identifier could be generated
    …mercato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=13535…

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

  • Info Line 306, Column 247: entity was defined here
    …" src='/mercato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhe…
  • Warning Line 346, Column 276: reference not terminated by REFC delimiter
    …o?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353520148931&ssbi…

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

  • Warning Line 346, Column 276: reference to external entity in attribute value
    …o?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353520148931&ssbi…

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

  • Error Line 346, Column 276: reference to entity "blobtable" for which no system identifier could be generated
    …o?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353520148931&ssbi…

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

  • Info Line 306, Column 258: entity was defined here
    …cato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=13535228…
  • Warning Line 346, Column 297: reference not terminated by REFC delimiter
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353520148931&ssbinary=true' />

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

  • Warning Line 346, Column 297: reference to external entity in attribute value
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353520148931&ssbinary=true' />

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

  • Error Line 346, Column 297: reference to entity "blobwhere" for which no system identifier could be generated
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353520148931&ssbinary=true' />

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

  • Info Line 306, Column 279: entity was defined here
    …rldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522889213&ssbinary=true' …
  • Warning Line 346, Column 320: reference not terminated by REFC delimiter
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353520148931&ssbinary=true' />

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

  • Warning Line 346, Column 320: reference to external entity in attribute value
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353520148931&ssbinary=true' />

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

  • Error Line 346, Column 320: reference to entity "ssbinary" for which no system identifier could be generated
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353520148931&ssbinary=true' />

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

  • Info Line 306, Column 303: entity was defined here
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522889213&ssbinary=true' />
  • Error Line 581, Column 5: value of attribute "id" invalid: "1" cannot start a name
    id='1353090635456' href='/mercato/libero/it-IT/casa' title='Casa' accesskey='1'…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 702, Column 5: value of attribute "id" invalid: "1" cannot start a name
    id='1353090637225' href='/mercato/libero/it-IT/impresa' title='Impresa' accessk…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 763, Column 5: value of attribute "id" invalid: "1" cannot start a name
    id='1353090640054' href='/mercato/libero/it-IT/condominio' title='Condominio' a…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 893, Column 5: value of attribute "id" invalid: "1" cannot start a name
    id='1353090642724' href='/mercato/libero/it-IT/sconti_e_premi' title='Sconti e …

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 948, Column 5: value of attribute "id" invalid: "1" cannot start a name
    id='1353090644131' href='/mercato/libero/it-IT/nuovi_servizi' title='Nuovi Serv…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 1102, Column 5: value of attribute "id" invalid: "1" cannot start a name
    id='1353090645551' href='/mercato/libero/it-IT/info_e_news' title='Info e news'…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 1238, Column 5: value of attribute "id" invalid: "1" cannot start a name
    id='1353090647038' href='/mercato/libero/it-IT/clienti' title='Area Clienti' ac…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 1266, Column 11: there is no attribute "blobtable"
    blobtable=''

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

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

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

  • Error Line 1267, Column 9: there is no attribute "blobkey"
    blobkey=''

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

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

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

  • Error Line 1268, Column 11: there is no attribute "blobwhere"
    blobwhere=''

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

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

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

  • Error Line 1269, Column 9: there is no attribute "blobcol"
    blobcol=''

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

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

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

  • Error Line 1270, Column 14: there is no attribute "cachecontrol"
    cachecontrol="never"

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

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

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

  • Error Line 1271, Column 11: there is no attribute "outstring"
    outstring="imgurl">

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

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

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

  • Error Line 1271, Column 19: element "satellite:blob" undefined
    outstring="imgurl">

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1272, Column 26: there is no attribute "name"
    <satellite:argument name='border' value="0"/>

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

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

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

  • Error Line 1272, Column 41: there is no attribute "value"
    <satellite:argument name='border' value="0"/>

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

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

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

  • Error Line 1272, Column 45: element "satellite:argument" undefined
    <satellite:argument name='border' value="0"/>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 1296, Column 127: reference not terminated by REFC delimiter
    …mercato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=13535…

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

  • Warning Line 1296, Column 127: reference to external entity in attribute value
    …mercato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=13535…

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

  • Error Line 1296, Column 127: reference to entity "blobkey" for which no system identifier could be generated
    …mercato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=13535…

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

  • Info Line 306, Column 247: entity was defined here
    …" src='/mercato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhe…
  • Warning Line 1296, Column 140: reference not terminated by REFC delimiter
    …o?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353520115607&ssbi…

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

  • Warning Line 1296, Column 140: reference to external entity in attribute value
    …o?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353520115607&ssbi…

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

  • Error Line 1296, Column 140: reference to entity "blobtable" for which no system identifier could be generated
    …o?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353520115607&ssbi…

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

  • Info Line 306, Column 258: entity was defined here
    …cato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=13535228…
  • Warning Line 1296, Column 161: reference not terminated by REFC delimiter
    …bkey=id&blobtable=MungoBlobs&blobwhere=1353520115607&ssbinary=true' style="vis…

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

  • Warning Line 1296, Column 161: reference to external entity in attribute value
    …bkey=id&blobtable=MungoBlobs&blobwhere=1353520115607&ssbinary=true' style="vis…

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

  • Error Line 1296, Column 161: reference to entity "blobwhere" for which no system identifier could be generated
    …bkey=id&blobtable=MungoBlobs&blobwhere=1353520115607&ssbinary=true' style="vis…

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

  • Info Line 306, Column 279: entity was defined here
    …rldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522889213&ssbinary=true' …
  • Warning Line 1296, Column 184: reference not terminated by REFC delimiter
    …MungoBlobs&blobwhere=1353520115607&ssbinary=true' style="visibility: visible;">

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

  • Warning Line 1296, Column 184: reference to external entity in attribute value
    …MungoBlobs&blobwhere=1353520115607&ssbinary=true' style="visibility: visible;">

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

  • Error Line 1296, Column 184: reference to entity "ssbinary" for which no system identifier could be generated
    …MungoBlobs&blobwhere=1353520115607&ssbinary=true' style="visibility: visible;">

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

  • Info Line 306, Column 303: entity was defined here
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522889213&ssbinary=true' />
  • Error Line 1297, Column 41: end tag for "param" omitted, but OMITTAG NO was specified
    <param name="wmode" value="transparent">

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

  • Info Line 1297, Column 1: start tag was here
    <param name="wmode" value="transparent">
  • Warning Line 1305, Column 60: reference not terminated by REFC delimiter
    …mercato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=13535…

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

  • Error Line 1305, Column 60: reference to entity "blobkey" for which no system identifier could be generated
    …mercato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=13535…

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

  • Info Line 306, Column 247: entity was defined here
    …" src='/mercato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhe…
  • Warning Line 1305, Column 73: reference not terminated by REFC delimiter
    …o?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353520115607&ssbi…

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

  • Error Line 1305, Column 73: reference to entity "blobtable" for which no system identifier could be generated
    …o?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353520115607&ssbi…

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

  • Info Line 306, Column 258: entity was defined here
    …cato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=13535228…
  • Warning Line 1305, Column 94: reference not terminated by REFC delimiter
    …bkey=id&blobtable=MungoBlobs&blobwhere=1353520115607&ssbinary=true", "flash", …

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

  • Error Line 1305, Column 94: reference to entity "blobwhere" for which no system identifier could be generated
    …bkey=id&blobtable=MungoBlobs&blobwhere=1353520115607&ssbinary=true", "flash", …

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

  • Info Line 306, Column 279: entity was defined here
    …rldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522889213&ssbinary=true' …
  • Warning Line 1305, Column 117: reference not terminated by REFC delimiter
    …Blobs&blobwhere=1353520115607&ssbinary=true", "flash", "949", "270", "9.0.45",…

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

  • Error Line 1305, Column 117: reference to entity "ssbinary" for which no system identifier could be generated
    …Blobs&blobwhere=1353520115607&ssbinary=true", "flash", "949", "270", "9.0.45",…

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

  • Info Line 306, Column 303: entity was defined here
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522889213&ssbinary=true' />
  • Warning Line 1305, Column 198: reference not terminated by REFC delimiter
    …mercato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=13535…

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

  • Error Line 1305, Column 198: reference to entity "blobkey" for which no system identifier could be generated
    …mercato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=13535…

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

  • Info Line 306, Column 247: entity was defined here
    …" src='/mercato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhe…
  • Warning Line 1305, Column 211: reference not terminated by REFC delimiter
    …o?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353520115607&ssbi…

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

  • Error Line 1305, Column 211: reference to entity "blobtable" for which no system identifier could be generated
    …o?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353520115607&ssbi…

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

  • Info Line 306, Column 258: entity was defined here
    …cato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=13535228…
  • Warning Line 1305, Column 232: reference not terminated by REFC delimiter
    …bkey=id&blobtable=MungoBlobs&blobwhere=1353520115607&ssbinary=true", flashvars…

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

  • Error Line 1305, Column 232: reference to entity "blobwhere" for which no system identifier could be generated
    …bkey=id&blobtable=MungoBlobs&blobwhere=1353520115607&ssbinary=true", flashvars…

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

  • Info Line 306, Column 279: entity was defined here
    …rldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522889213&ssbinary=true' …
  • Warning Line 1305, Column 255: reference not terminated by REFC delimiter
    …lobtable=MungoBlobs&blobwhere=1353520115607&ssbinary=true", flashvars, params);

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

  • Error Line 1305, Column 255: reference to entity "ssbinary" for which no system identifier could be generated
    …lobtable=MungoBlobs&blobwhere=1353520115607&ssbinary=true", flashvars, params);

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

  • Info Line 306, Column 303: entity was defined here
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522889213&ssbinary=true' />
  • Warning Line 1387, Column 257: reference not terminated by REFC delimiter
    …mercato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=13535…

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

  • Warning Line 1387, Column 257: reference to external entity in attribute value
    …mercato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=13535…

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

  • Error Line 1387, Column 257: reference to entity "blobkey" for which no system identifier could be generated
    …mercato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=13535…

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

  • Info Line 306, Column 247: entity was defined here
    …" src='/mercato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhe…
  • Warning Line 1387, Column 270: reference not terminated by REFC delimiter
    …o?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522883431&ssbi…

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

  • Warning Line 1387, Column 270: reference to external entity in attribute value
    …o?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522883431&ssbi…

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

  • Error Line 1387, Column 270: reference to entity "blobtable" for which no system identifier could be generated
    …o?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522883431&ssbi…

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

  • Info Line 306, Column 258: entity was defined here
    …cato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=13535228…
  • Warning Line 1387, Column 291: reference not terminated by REFC delimiter
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522883431&ssbinary=true' />

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

  • Warning Line 1387, Column 291: reference to external entity in attribute value
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522883431&ssbinary=true' />

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

  • Error Line 1387, Column 291: reference to entity "blobwhere" for which no system identifier could be generated
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522883431&ssbinary=true' />

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

  • Info Line 306, Column 279: entity was defined here
    …rldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522889213&ssbinary=true' …
  • Warning Line 1387, Column 314: reference not terminated by REFC delimiter
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522883431&ssbinary=true' />

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

  • Warning Line 1387, Column 314: reference to external entity in attribute value
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522883431&ssbinary=true' />

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

  • Error Line 1387, Column 314: reference to entity "ssbinary" for which no system identifier could be generated
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522883431&ssbinary=true' />

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

  • Info Line 306, Column 303: entity was defined here
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522889213&ssbinary=true' />
  • Warning Line 1445, Column 285: reference not terminated by REFC delimiter
    …mercato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=13535…

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

  • Warning Line 1445, Column 285: reference to external entity in attribute value
    …mercato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=13535…

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

  • Error Line 1445, Column 285: reference to entity "blobkey" for which no system identifier could be generated
    …mercato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=13535…

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

  • Info Line 306, Column 247: entity was defined here
    …" src='/mercato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhe…
  • Warning Line 1445, Column 298: reference not terminated by REFC delimiter
    …o?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353557982618&ssbi…

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

  • Warning Line 1445, Column 298: reference to external entity in attribute value
    …o?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353557982618&ssbi…

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

  • Error Line 1445, Column 298: reference to entity "blobtable" for which no system identifier could be generated
    …o?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353557982618&ssbi…

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

  • Info Line 306, Column 258: entity was defined here
    …cato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=13535228…
  • Warning Line 1445, Column 319: reference not terminated by REFC delimiter
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353557982618&ssbinary=true' />

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

  • Warning Line 1445, Column 319: reference to external entity in attribute value
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353557982618&ssbinary=true' />

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

  • Error Line 1445, Column 319: reference to entity "blobwhere" for which no system identifier could be generated
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353557982618&ssbinary=true' />

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

  • Info Line 306, Column 279: entity was defined here
    …rldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522889213&ssbinary=true' …
  • Warning Line 1445, Column 342: reference not terminated by REFC delimiter
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353557982618&ssbinary=true' />

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

  • Warning Line 1445, Column 342: reference to external entity in attribute value
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353557982618&ssbinary=true' />

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

  • Error Line 1445, Column 342: reference to entity "ssbinary" for which no system identifier could be generated
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353557982618&ssbinary=true' />

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

  • Info Line 306, Column 303: entity was defined here
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522889213&ssbinary=true' />
  • Warning Line 1504, Column 257: reference not terminated by REFC delimiter
    …mercato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=13535…

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

  • Warning Line 1504, Column 257: reference to external entity in attribute value
    …mercato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=13535…

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

  • Error Line 1504, Column 257: reference to entity "blobkey" for which no system identifier could be generated
    …mercato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=13535…

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

  • Info Line 306, Column 247: entity was defined here
    …" src='/mercato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhe…
  • Warning Line 1504, Column 270: reference not terminated by REFC delimiter
    …o?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522884547&ssbi…

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

  • Warning Line 1504, Column 270: reference to external entity in attribute value
    …o?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522884547&ssbi…

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

  • Error Line 1504, Column 270: reference to entity "blobtable" for which no system identifier could be generated
    …o?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522884547&ssbi…

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

  • Info Line 306, Column 258: entity was defined here
    …cato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=13535228…
  • Warning Line 1504, Column 291: reference not terminated by REFC delimiter
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522884547&ssbinary=true' />

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

  • Warning Line 1504, Column 291: reference to external entity in attribute value
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522884547&ssbinary=true' />

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

  • Error Line 1504, Column 291: reference to entity "blobwhere" for which no system identifier could be generated
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522884547&ssbinary=true' />

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

  • Info Line 306, Column 279: entity was defined here
    …rldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522889213&ssbinary=true' …
  • Warning Line 1504, Column 314: reference not terminated by REFC delimiter
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522884547&ssbinary=true' />

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

  • Warning Line 1504, Column 314: reference to external entity in attribute value
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522884547&ssbinary=true' />

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

  • Error Line 1504, Column 314: reference to entity "ssbinary" for which no system identifier could be generated
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522884547&ssbinary=true' />

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

  • Info Line 306, Column 303: entity was defined here
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522889213&ssbinary=true' />
  • Error Line 1619, Column 23: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <h3 class="sopra"><div>

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

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

  • Warning Line 1624, Column 230: reference not terminated by REFC delimiter
    …mercato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=13535…

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

  • Warning Line 1624, Column 230: reference to external entity in attribute value
    …mercato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=13535…

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

  • Error Line 1624, Column 230: reference to entity "blobkey" for which no system identifier could be generated
    …mercato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=13535…

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

  • Info Line 306, Column 247: entity was defined here
    …" src='/mercato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhe…
  • Warning Line 1624, Column 243: reference not terminated by REFC delimiter
    …o?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522884556&ssbi…

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

  • Warning Line 1624, Column 243: reference to external entity in attribute value
    …o?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522884556&ssbi…

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

  • Error Line 1624, Column 243: reference to entity "blobtable" for which no system identifier could be generated
    …o?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522884556&ssbi…

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

  • Info Line 306, Column 258: entity was defined here
    …cato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=13535228…
  • Warning Line 1624, Column 264: reference not terminated by REFC delimiter
    …rldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522884556&ssbinary=true'/>

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

  • Warning Line 1624, Column 264: reference to external entity in attribute value
    …rldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522884556&ssbinary=true'/>

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

  • Error Line 1624, Column 264: reference to entity "blobwhere" for which no system identifier could be generated
    …rldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522884556&ssbinary=true'/>

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

  • Info Line 306, Column 279: entity was defined here
    …rldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522889213&ssbinary=true' …
  • Warning Line 1624, Column 287: reference not terminated by REFC delimiter
    …rldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522884556&ssbinary=true'/>

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

  • Warning Line 1624, Column 287: reference to external entity in attribute value
    …rldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522884556&ssbinary=true'/>

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

  • Error Line 1624, Column 287: reference to entity "ssbinary" for which no system identifier could be generated
    …rldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522884556&ssbinary=true'/>

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

  • Info Line 306, Column 303: entity was defined here
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522889213&ssbinary=true' />
  • Error Line 1629, Column 5: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div>

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

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

  • Error Line 1697, Column 23: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <h3 class="sopra"><div>

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

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

  • Warning Line 1702, Column 234: reference not terminated by REFC delimiter
    …mercato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=13535…

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

  • Warning Line 1702, Column 234: reference to external entity in attribute value
    …mercato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=13535…

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

  • Error Line 1702, Column 234: reference to entity "blobkey" for which no system identifier could be generated
    …mercato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=13535…

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

  • Info Line 306, Column 247: entity was defined here
    …" src='/mercato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhe…
  • Warning Line 1702, Column 247: reference not terminated by REFC delimiter
    …o?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522885957&ssbi…

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

  • Warning Line 1702, Column 247: reference to external entity in attribute value
    …o?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522885957&ssbi…

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

  • Error Line 1702, Column 247: reference to entity "blobtable" for which no system identifier could be generated
    …o?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522885957&ssbi…

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

  • Info Line 306, Column 258: entity was defined here
    …cato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=13535228…
  • Warning Line 1702, Column 268: reference not terminated by REFC delimiter
    …rldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522885957&ssbinary=true'/>

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

  • Warning Line 1702, Column 268: reference to external entity in attribute value
    …rldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522885957&ssbinary=true'/>

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

  • Error Line 1702, Column 268: reference to entity "blobwhere" for which no system identifier could be generated
    …rldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522885957&ssbinary=true'/>

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

  • Info Line 306, Column 279: entity was defined here
    …rldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522889213&ssbinary=true' …
  • Warning Line 1702, Column 291: reference not terminated by REFC delimiter
    …rldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522885957&ssbinary=true'/>

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

  • Warning Line 1702, Column 291: reference to external entity in attribute value
    …rldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522885957&ssbinary=true'/>

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

  • Error Line 1702, Column 291: reference to entity "ssbinary" for which no system identifier could be generated
    …rldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522885957&ssbinary=true'/>

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

  • Info Line 306, Column 303: entity was defined here
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522889213&ssbinary=true' />
  • Error Line 1872, Column 18: document type does not allow element "h3" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <h3 class="sopra"><div>

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

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

  • Error Line 1872, Column 23: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <h3 class="sopra"><div>

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

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

  • Warning Line 1879, Column 213: reference not terminated by REFC delimiter
    …mercato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=13535…

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

  • Warning Line 1879, Column 213: reference to external entity in attribute value
    …mercato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=13535…

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

  • Error Line 1879, Column 213: reference to entity "blobkey" for which no system identifier could be generated
    …mercato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=13535…

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

  • Info Line 306, Column 247: entity was defined here
    …" src='/mercato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhe…
  • Warning Line 1879, Column 226: reference not terminated by REFC delimiter
    …o?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522868131&ssbi…

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

  • Warning Line 1879, Column 226: reference to external entity in attribute value
    …o?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522868131&ssbi…

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

  • Error Line 1879, Column 226: reference to entity "blobtable" for which no system identifier could be generated
    …o?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522868131&ssbi…

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

  • Info Line 306, Column 258: entity was defined here
    …cato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=13535228…
  • Warning Line 1879, Column 247: reference not terminated by REFC delimiter
    …rldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522868131&ssbinary=true'/>

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

  • Warning Line 1879, Column 247: reference to external entity in attribute value
    …rldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522868131&ssbinary=true'/>

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

  • Error Line 1879, Column 247: reference to entity "blobwhere" for which no system identifier could be generated
    …rldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522868131&ssbinary=true'/>

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

  • Info Line 306, Column 279: entity was defined here
    …rldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522889213&ssbinary=true' …
  • Warning Line 1879, Column 270: reference not terminated by REFC delimiter
    …rldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522868131&ssbinary=true'/>

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

  • Warning Line 1879, Column 270: reference to external entity in attribute value
    …rldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522868131&ssbinary=true'/>

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

  • Error Line 1879, Column 270: reference to entity "ssbinary" for which no system identifier could be generated
    …rldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522868131&ssbinary=true'/>

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

  • Info Line 306, Column 303: entity was defined here
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522889213&ssbinary=true' />
  • Error Line 2055, Column 49: there is no attribute "autocomplete"
    …formlogin" method="post" autocomplete="off" onsubmit="return CheckNavLogin(thi…

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

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

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

  • Error Line 2056, Column 185: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …text" title="username" id="nomeutenteid" class="textBox" value="Nome Utente" />

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

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

  • Error Line 2058, Column 118: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    ….value=''" type="password" title="password" id="passwordid" value="password" />

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

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

  • Error Line 2060, Column 124: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …value="http://www.enelenergia.it/mercato/libero/it-IT/clienti/area_clienti/" />

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

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

  • Error Line 2062, Column 89: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …e="submit" name="Submit" value="  Accedi  " class="my_bt_blu" title="Accedi" />

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

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

  • Warning Line 2164, Column 251: reference not terminated by REFC delimiter
    …mercato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=13535…

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

  • Warning Line 2164, Column 251: reference to external entity in attribute value
    …mercato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=13535…

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

  • Error Line 2164, Column 251: reference to entity "blobkey" for which no system identifier could be generated
    …mercato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=13535…

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

  • Info Line 306, Column 247: entity was defined here
    …" src='/mercato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhe…
  • Warning Line 2164, Column 264: reference not terminated by REFC delimiter
    …o?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353557982609&ssbi…

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

  • Warning Line 2164, Column 264: reference to external entity in attribute value
    …o?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353557982609&ssbi…

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

  • Error Line 2164, Column 264: reference to entity "blobtable" for which no system identifier could be generated
    …o?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353557982609&ssbi…

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

  • Info Line 306, Column 258: entity was defined here
    …cato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=13535228…
  • Warning Line 2164, Column 285: reference not terminated by REFC delimiter
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353557982609&ssbinary=true' />

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

  • Warning Line 2164, Column 285: reference to external entity in attribute value
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353557982609&ssbinary=true' />

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

  • Error Line 2164, Column 285: reference to entity "blobwhere" for which no system identifier could be generated
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353557982609&ssbinary=true' />

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

  • Info Line 306, Column 279: entity was defined here
    …rldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522889213&ssbinary=true' …
  • Warning Line 2164, Column 308: reference not terminated by REFC delimiter
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353557982609&ssbinary=true' />

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

  • Warning Line 2164, Column 308: reference to external entity in attribute value
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353557982609&ssbinary=true' />

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

  • Error Line 2164, Column 308: reference to entity "ssbinary" for which no system identifier could be generated
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353557982609&ssbinary=true' />

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

  • Info Line 306, Column 303: entity was defined here
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522889213&ssbinary=true' />
  • Error Line 2222, Column 18: document type does not allow element "h3" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <h3 class="sopra"><div>

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

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

  • Error Line 2222, Column 23: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <h3 class="sopra"><div>

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

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

  • Error Line 2231, Column 8: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <p><div>

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

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

  • Error Line 2296, Column 56: there is no attribute "target"
    <a href="http://puntoenelmilano.enelenergia.it/"target="_blank">

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

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

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

  • Warning Line 2297, Column 267: reference not terminated by REFC delimiter
    …mercato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=13535…

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

  • Warning Line 2297, Column 267: reference to external entity in attribute value
    …mercato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=13535…

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

  • Error Line 2297, Column 267: reference to entity "blobkey" for which no system identifier could be generated
    …mercato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=13535…

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

  • Info Line 306, Column 247: entity was defined here
    …" src='/mercato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhe…
  • Warning Line 2297, Column 280: reference not terminated by REFC delimiter
    …o?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522887838&ssbi…

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

  • Warning Line 2297, Column 280: reference to external entity in attribute value
    …o?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522887838&ssbi…

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

  • Error Line 2297, Column 280: reference to entity "blobtable" for which no system identifier could be generated
    …o?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522887838&ssbi…

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

  • Info Line 306, Column 258: entity was defined here
    …cato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=13535228…
  • Warning Line 2297, Column 301: reference not terminated by REFC delimiter
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522887838&ssbinary=true' />

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

  • Warning Line 2297, Column 301: reference to external entity in attribute value
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522887838&ssbinary=true' />

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

  • Error Line 2297, Column 301: reference to entity "blobwhere" for which no system identifier could be generated
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522887838&ssbinary=true' />

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

  • Info Line 306, Column 279: entity was defined here
    …rldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522889213&ssbinary=true' …
  • Warning Line 2297, Column 324: reference not terminated by REFC delimiter
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522887838&ssbinary=true' />

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

  • Warning Line 2297, Column 324: reference to external entity in attribute value
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522887838&ssbinary=true' />

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

  • Error Line 2297, Column 324: reference to entity "ssbinary" for which no system identifier could be generated
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522887838&ssbinary=true' />

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

  • Info Line 306, Column 303: entity was defined here
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522889213&ssbinary=true' />
  • Warning Line 2407, Column 213: reference not terminated by REFC delimiter
    …mercato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=13535…

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

  • Warning Line 2407, Column 213: reference to external entity in attribute value
    …mercato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=13535…

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

  • Error Line 2407, Column 213: reference to entity "blobkey" for which no system identifier could be generated
    …mercato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=13535…

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

  • Info Line 306, Column 247: entity was defined here
    …" src='/mercato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhe…
  • Warning Line 2407, Column 226: reference not terminated by REFC delimiter
    …o?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353520153071&ssbi…

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

  • Warning Line 2407, Column 226: reference to external entity in attribute value
    …o?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353520153071&ssbi…

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

  • Error Line 2407, Column 226: reference to entity "blobtable" for which no system identifier could be generated
    …o?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353520153071&ssbi…

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

  • Info Line 306, Column 258: entity was defined here
    …cato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=13535228…
  • Warning Line 2407, Column 247: reference not terminated by REFC delimiter
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353520153071&ssbinary=true' />

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

  • Warning Line 2407, Column 247: reference to external entity in attribute value
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353520153071&ssbinary=true' />

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

  • Error Line 2407, Column 247: reference to entity "blobwhere" for which no system identifier could be generated
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353520153071&ssbinary=true' />

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

  • Info Line 306, Column 279: entity was defined here
    …rldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522889213&ssbinary=true' …
  • Warning Line 2407, Column 270: reference not terminated by REFC delimiter
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353520153071&ssbinary=true' />

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

  • Warning Line 2407, Column 270: reference to external entity in attribute value
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353520153071&ssbinary=true' />

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

  • Error Line 2407, Column 270: reference to entity "ssbinary" for which no system identifier could be generated
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353520153071&ssbinary=true' />

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

  • Info Line 306, Column 303: entity was defined here
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522889213&ssbinary=true' />
  • Error Line 2413, Column 71: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <h4><a href='/mercato/libero/it-IT/info_e_news/news/sisma_emilia'><div>

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

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

  • Warning Line 2493, Column 253: reference not terminated by REFC delimiter
    …mercato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=13535…

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

  • Warning Line 2493, Column 253: reference to external entity in attribute value
    …mercato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=13535…

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

  • Error Line 2493, Column 253: reference to entity "blobkey" for which no system identifier could be generated
    …mercato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=13535…

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

  • Info Line 306, Column 247: entity was defined here
    …" src='/mercato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhe…
  • Warning Line 2493, Column 266: reference not terminated by REFC delimiter
    …o?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522886285&ssbi…

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

  • Warning Line 2493, Column 266: reference to external entity in attribute value
    …o?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522886285&ssbi…

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

  • Error Line 2493, Column 266: reference to entity "blobtable" for which no system identifier could be generated
    …o?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522886285&ssbi…

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

  • Info Line 306, Column 258: entity was defined here
    …cato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=13535228…
  • Warning Line 2493, Column 287: reference not terminated by REFC delimiter
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522886285&ssbinary=true' />

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

  • Warning Line 2493, Column 287: reference to external entity in attribute value
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522886285&ssbinary=true' />

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

  • Error Line 2493, Column 287: reference to entity "blobwhere" for which no system identifier could be generated
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522886285&ssbinary=true' />

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

  • Info Line 306, Column 279: entity was defined here
    …rldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522889213&ssbinary=true' …
  • Warning Line 2493, Column 310: reference not terminated by REFC delimiter
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522886285&ssbinary=true' />

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

  • Warning Line 2493, Column 310: reference to external entity in attribute value
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522886285&ssbinary=true' />

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

  • Error Line 2493, Column 310: reference to entity "ssbinary" for which no system identifier could be generated
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522886285&ssbinary=true' />

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

  • Info Line 306, Column 303: entity was defined here
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522889213&ssbinary=true' />
  • Error Line 2499, Column 97: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …ato/libero/it-IT/info_e_news/news/la_nuova_area__clienti_di_enel_energia'><div>

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

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

  • Error Line 2504, Column 8: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <p><div>

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

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

  • Warning Line 2583, Column 213: reference not terminated by REFC delimiter
    …mercato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=13535…

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

  • Warning Line 2583, Column 213: reference to external entity in attribute value
    …mercato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=13535…

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

  • Error Line 2583, Column 213: reference to entity "blobkey" for which no system identifier could be generated
    …mercato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=13535…

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

  • Info Line 306, Column 247: entity was defined here
    …" src='/mercato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhe…
  • Warning Line 2583, Column 226: reference not terminated by REFC delimiter
    …o?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353520153071&ssbi…

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

  • Warning Line 2583, Column 226: reference to external entity in attribute value
    …o?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353520153071&ssbi…

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

  • Error Line 2583, Column 226: reference to entity "blobtable" for which no system identifier could be generated
    …o?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353520153071&ssbi…

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

  • Info Line 306, Column 258: entity was defined here
    …cato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=13535228…
  • Warning Line 2583, Column 247: reference not terminated by REFC delimiter
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353520153071&ssbinary=true' />

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

  • Warning Line 2583, Column 247: reference to external entity in attribute value
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353520153071&ssbinary=true' />

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

  • Error Line 2583, Column 247: reference to entity "blobwhere" for which no system identifier could be generated
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353520153071&ssbinary=true' />

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

  • Info Line 306, Column 279: entity was defined here
    …rldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522889213&ssbinary=true' …
  • Warning Line 2583, Column 270: reference not terminated by REFC delimiter
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353520153071&ssbinary=true' />

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

  • Warning Line 2583, Column 270: reference to external entity in attribute value
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353520153071&ssbinary=true' />

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

  • Error Line 2583, Column 270: reference to entity "ssbinary" for which no system identifier could be generated
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353520153071&ssbinary=true' />

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

  • Info Line 306, Column 303: entity was defined here
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522889213&ssbinary=true' />
  • Error Line 2589, Column 52: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <h4><a href='/mercato/libero/it-IT/sales_code'><div>

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

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

  • Error Line 2594, Column 8: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <p><div>

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

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

  • Error Line 2596, Column 5: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div>

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

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

  • Warning Line 2675, Column 229: reference not terminated by REFC delimiter
    …mercato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=13535…

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

  • Warning Line 2675, Column 229: reference to external entity in attribute value
    …mercato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=13535…

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

  • Error Line 2675, Column 229: reference to entity "blobkey" for which no system identifier could be generated
    …mercato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=13535…

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

  • Info Line 306, Column 247: entity was defined here
    …" src='/mercato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhe…
  • Warning Line 2675, Column 242: reference not terminated by REFC delimiter
    …o?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522886299&ssbi…

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

  • Warning Line 2675, Column 242: reference to external entity in attribute value
    …o?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522886299&ssbi…

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

  • Error Line 2675, Column 242: reference to entity "blobtable" for which no system identifier could be generated
    …o?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522886299&ssbi…

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

  • Info Line 306, Column 258: entity was defined here
    …cato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=13535228…
  • Warning Line 2675, Column 263: reference not terminated by REFC delimiter
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522886299&ssbinary=true' />

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

  • Warning Line 2675, Column 263: reference to external entity in attribute value
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522886299&ssbinary=true' />

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

  • Error Line 2675, Column 263: reference to entity "blobwhere" for which no system identifier could be generated
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522886299&ssbinary=true' />

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

  • Info Line 306, Column 279: entity was defined here
    …rldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522889213&ssbinary=true' …
  • Warning Line 2675, Column 286: reference not terminated by REFC delimiter
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522886299&ssbinary=true' />

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

  • Warning Line 2675, Column 286: reference to external entity in attribute value
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522886299&ssbinary=true' />

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

  • Error Line 2675, Column 286: reference to entity "ssbinary" for which no system identifier could be generated
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522886299&ssbinary=true' />

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

  • Info Line 306, Column 303: entity was defined here
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522889213&ssbinary=true' />
  • Error Line 2681, Column 73: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <h4><a href='/mercato/libero/it-IT/sconti_e_premi/promozioni/frimm'><div>

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

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

  • Error Line 2686, Column 8: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <p><div>

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

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

  • Warning Line 2765, Column 257: reference not terminated by REFC delimiter
    …mercato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=13535…

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

  • Warning Line 2765, Column 257: reference to external entity in attribute value
    …mercato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=13535…

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

  • Error Line 2765, Column 257: reference to entity "blobkey" for which no system identifier could be generated
    …mercato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=13535…

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

  • Info Line 306, Column 247: entity was defined here
    …" src='/mercato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhe…
  • Warning Line 2765, Column 270: reference not terminated by REFC delimiter
    …o?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522886315&ssbi…

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

  • Warning Line 2765, Column 270: reference to external entity in attribute value
    …o?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522886315&ssbi…

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

  • Error Line 2765, Column 270: reference to entity "blobtable" for which no system identifier could be generated
    …o?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522886315&ssbi…

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

  • Info Line 306, Column 258: entity was defined here
    …cato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=13535228…
  • Warning Line 2765, Column 291: reference not terminated by REFC delimiter
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522886315&ssbinary=true' />

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

  • Warning Line 2765, Column 291: reference to external entity in attribute value
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522886315&ssbinary=true' />

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

  • Error Line 2765, Column 291: reference to entity "blobwhere" for which no system identifier could be generated
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522886315&ssbinary=true' />

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

  • Info Line 306, Column 279: entity was defined here
    …rldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522889213&ssbinary=true' …
  • Warning Line 2765, Column 314: reference not terminated by REFC delimiter
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522886315&ssbinary=true' />

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

  • Warning Line 2765, Column 314: reference to external entity in attribute value
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522886315&ssbinary=true' />

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

  • Error Line 2765, Column 314: reference to entity "ssbinary" for which no system identifier could be generated
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522886315&ssbinary=true' />

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

  • Info Line 306, Column 303: entity was defined here
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522889213&ssbinary=true' />
  • Error Line 2771, Column 73: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <h4><a href='/mercato/libero/it-IT/casa/offerte/tutto_compreso_gas'><div>

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

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

  • Error Line 2776, Column 8: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <p><div>

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

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

  • Warning Line 2860, Column 243: reference not terminated by REFC delimiter
    …mercato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=13535…

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

  • Warning Line 2860, Column 243: reference to external entity in attribute value
    …mercato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=13535…

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

  • Error Line 2860, Column 243: reference to entity "blobkey" for which no system identifier could be generated
    …mercato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=13535…

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

  • Info Line 306, Column 247: entity was defined here
    …" src='/mercato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhe…
  • Warning Line 2860, Column 256: reference not terminated by REFC delimiter
    …o?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522883322&ssbi…

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

  • Warning Line 2860, Column 256: reference to external entity in attribute value
    …o?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522883322&ssbi…

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

  • Error Line 2860, Column 256: reference to entity "blobtable" for which no system identifier could be generated
    …o?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522883322&ssbi…

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

  • Info Line 306, Column 258: entity was defined here
    …cato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=13535228…
  • Warning Line 2860, Column 277: reference not terminated by REFC delimiter
    …urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522883322&ssbinary=true'>

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

  • Warning Line 2860, Column 277: reference to external entity in attribute value
    …urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522883322&ssbinary=true'>

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

  • Error Line 2860, Column 277: reference to entity "blobwhere" for which no system identifier could be generated
    …urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522883322&ssbinary=true'>

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

  • Info Line 306, Column 279: entity was defined here
    …rldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522889213&ssbinary=true' …
  • Warning Line 2860, Column 300: reference not terminated by REFC delimiter
    …urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522883322&ssbinary=true'>

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

  • Warning Line 2860, Column 300: reference to external entity in attribute value
    …urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522883322&ssbinary=true'>

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

  • Error Line 2860, Column 300: reference to entity "ssbinary" for which no system identifier could be generated
    …urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522883322&ssbinary=true'>

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

  • Info Line 306, Column 303: entity was defined here
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522889213&ssbinary=true' />
  • Error Line 2860, Column 307: end tag for "img" omitted, but OMITTAG NO was specified
    …urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522883322&ssbinary=true'>

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

  • Info Line 2860, Column 1: start tag was here
    <img class="img_small " title='Home enelpremia 4' alt='Home enelpremia 4' ix:ur…
  • Error Line 2867, Column 5: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div>

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

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

  • Error Line 2872, Column 8: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <p><div>

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

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

  • Warning Line 2931, Column 261: reference not terminated by REFC delimiter
    …mercato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=13535…

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

  • Warning Line 2931, Column 261: reference to external entity in attribute value
    …mercato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=13535…

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

  • Error Line 2931, Column 261: reference to entity "blobkey" for which no system identifier could be generated
    …mercato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=13535…

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

  • Info Line 306, Column 247: entity was defined here
    …" src='/mercato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhe…
  • Warning Line 2931, Column 274: reference not terminated by REFC delimiter
    …o?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353520146735&ssbi…

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

  • Warning Line 2931, Column 274: reference to external entity in attribute value
    …o?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353520146735&ssbi…

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

  • Error Line 2931, Column 274: reference to entity "blobtable" for which no system identifier could be generated
    …o?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353520146735&ssbi…

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

  • Info Line 306, Column 258: entity was defined here
    …cato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=13535228…
  • Warning Line 2931, Column 295: reference not terminated by REFC delimiter
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353520146735&ssbinary=true' />

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

  • Warning Line 2931, Column 295: reference to external entity in attribute value
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353520146735&ssbinary=true' />

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

  • Error Line 2931, Column 295: reference to entity "blobwhere" for which no system identifier could be generated
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353520146735&ssbinary=true' />

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

  • Info Line 306, Column 279: entity was defined here
    …rldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522889213&ssbinary=true' …
  • Warning Line 2931, Column 318: reference not terminated by REFC delimiter
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353520146735&ssbinary=true' />

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

  • Warning Line 2931, Column 318: reference to external entity in attribute value
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353520146735&ssbinary=true' />

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

  • Error Line 2931, Column 318: reference to entity "ssbinary" for which no system identifier could be generated
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353520146735&ssbinary=true' />

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

  • Info Line 306, Column 303: entity was defined here
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522889213&ssbinary=true' />
  • Warning Line 2979, Column 271: reference not terminated by REFC delimiter
    …mercato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=13535…

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

  • Warning Line 2979, Column 271: reference to external entity in attribute value
    …mercato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=13535…

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

  • Error Line 2979, Column 271: reference to entity "blobkey" for which no system identifier could be generated
    …mercato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=13535…

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

  • Info Line 306, Column 247: entity was defined here
    …" src='/mercato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhe…
  • Warning Line 2979, Column 284: reference not terminated by REFC delimiter
    …o?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522887104&ssbi…

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

  • Warning Line 2979, Column 284: reference to external entity in attribute value
    …o?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522887104&ssbi…

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

  • Error Line 2979, Column 284: reference to entity "blobtable" for which no system identifier could be generated
    …o?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522887104&ssbi…

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

  • Info Line 306, Column 258: entity was defined here
    …cato/libero?blobcol=urldata&blobkey=id&blobtable=MungoBlobs&blobwhere=13535228…
  • Warning Line 2979, Column 305: reference not terminated by REFC delimiter
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522887104&ssbinary=true' />

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

  • Warning Line 2979, Column 305: reference to external entity in attribute value
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522887104&ssbinary=true' />

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

  • Error Line 2979, Column 305: reference to entity "blobwhere" for which no system identifier could be generated
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522887104&ssbinary=true' />

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

  • Info Line 306, Column 279: entity was defined here
    …rldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522889213&ssbinary=true' …
  • Warning Line 2979, Column 328: reference not terminated by REFC delimiter
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522887104&ssbinary=true' />

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

  • Warning Line 2979, Column 328: reference to external entity in attribute value
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522887104&ssbinary=true' />

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

  • Error Line 2979, Column 328: reference to entity "ssbinary" for which no system identifier could be generated
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522887104&ssbinary=true' />

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

  • Info Line 306, Column 303: entity was defined here
    …ldata&blobkey=id&blobtable=MungoBlobs&blobwhere=1353522889213&ssbinary=true' />
  • Error Line 3722, Column 70: required attribute "action" not specified
    <form method="post" name="form_enelworldwide" id="form_enelworldwide">

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

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

  • Error Line 3740, Column 104: document type does not allow element "a" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …=f49fa35e&amp;cb=3916" target="_blank"><img src="http://adv.enel.it/openx/www/…

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

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

  • Error Line 3756, Column 72: required attribute "type" not specified
    …cript src='HTTP://cloudando.vivocha.com/a/enelenergia/api/vivocha.js'></script>

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

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

  • Error Line 3896, Column 12: there is no attribute "name"
    <FORM name="actionForm" ACTION="Satellite" METHOD="post">

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

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

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

  • Error Line 3896, Column 32: there is no attribute "ACTION"
    <FORM name="actionForm" ACTION="Satellite" METHOD="post">

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

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

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

  • Error Line 3896, Column 51: there is no attribute "METHOD"
    <FORM name="actionForm" ACTION="Satellite" METHOD="post">

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

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

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

  • Error Line 3896, Column 57: element "FORM" undefined
    <FORM name="actionForm" ACTION="Satellite" METHOD="post">

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

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

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

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

  • Error Line 3942, Column 125: document type does not allow element "img" here
    …ite_pregresse&amp;secure=false&amp;timeout=31536000&amp;url=%2F&amp;value=0" />

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

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

  • Error Line 3967, Column 31: document type does not allow element "script" here
    <script type="text/javascript">

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

Visitor Analysis

Daily Visitor
  • 6.417 visits

In Page Analysis