Solvia, Inmobiliaria de Banco Sabadell. Casas, Pisos, Locales... en Venta o Alquiler. ...

solvia.es
  • Domain Name
    solvia.es
  • Favicon
  • Google Page Rank
    5
  • Alexa Rank
    #26246
  • Page Size
    108.1 KB
  • Ip Address
    93.90.20.211
  • Heading
    H1: 2, H2: 0, H3: 1, H4: 0, H5: 0, H6: 0
  • Images
    3 GIF, 72 JPG, 14 PNG

Website Meta Analysis

  • Title
    Solvia, Inmobiliaria de Banco Sabadell. Casas, Pisos, Locales... en Venta o Alquiler.
  • Meta Keyword
  • Meta Description
    Solvia, Inmobiliaria de Banco Sabadell. Casas, Pisos, Locales... en Venta o Alquiler.

Technical Analysis

  • Webserver
    Microsoft-IIS/7.0
  • Ip Address
    93.90.20.211
  • Domain Age
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from solvia.es.

HTML Analysis

  • cache-control: private
  • content-length: 110074
  • content-type: text/html
  • server: Microsoft-IIS/7.0
  • x-powered-by: ASP.NET
  • date: Sat, 10 Aug 2013 00:14:06 GMT
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for solvia.es

DNS Analysis


DNS servers
dns.bancsabadell.com [62.97.120.120]
sdn.bancsabadell.com


DNS Records

Answer records
solvia.es A 93.90.20.211 28800s
solvia.es MX
preference: 20
exchange: cluster8a.eu.messagelabs.com
28800s
solvia.es MX
preference: 10
exchange: cluster8.eu.messagelabs.com
28800s
solvia.es NS  sdn.bancsabadell.com 28800s
solvia.es NS  dns.bancsabadell.com 28800s
solvia.es SOA
server: dns.bancsabadell.com
email: root@dns.bancsabadell.com
serial: 89
refresh: 7200
retry: 3600
expire: 1800
minimum ttl: 1800
28800s
solvia.es TXT v=spf1 a:buzon4.bancsabadell.com a:buzon5.bancsabadell.com a:buzon6.bancsabadell.com a:buzon7.bancsabadell.com include:spf.messagelabs.com -all 28800s

Authority records

Additional records

IP 93.90.20.211 Analysis

  • Country Code
    ES
  • Country Code3
    ESP
  • Country Name
    Spain
  • City
    Madrid
  • Continent Code
    EU
  • Latitude
    40.4.
  • Longitude
    3.6833
  • No whois ip data for 93.90.20.211

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 398 Errors
  • 104 Warnings
Ratio Text/Html
  • 0.6769118152077647
Message Error
  • Warning Line 12, Column 100: NET-enabling start-tag requires SHORTTAG YES
    …href='http://www.solvia.es/css/basicNEW.css' rel='stylesheet' media='screen' />

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

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

  • Error Line 12, Column 101: character data is not allowed here
    …href='http://www.solvia.es/css/basicNEW.css' rel='stylesheet' media='screen' />

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

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Warning Line 17, Column 100: NET-enabling start-tag requires SHORTTAG YES
    … href="http://www.solvia.es/css/lightbox.css" type="text/css" media="screen" />

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

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

  • Error Line 26, Column 63: required attribute "TYPE" not specified
    <script src="http://connect.facebook.net/es_ES/all.js#xfbml=1"></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 32, Column 18: there is no attribute "LANGUAJE"
    <script languaje="javascript" type="text/javascript">

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

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

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

  • Error Line 38, Column 18: document type does not allow element "DIV" here
    <div id="fb-root"></div>

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

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

  • Warning Line 170, Column 52: NET-enabling start-tag requires SHORTTAG YES
    <link rel="canonical" href="http://www.solvia.es/" />

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

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

  • Error Line 171, Column 7: end tag for element "HEAD" which is not open
    </head>

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

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

  • Error Line 172, Column 6: document type does not allow element "BODY" here
    <body>

    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 181, Column 31: there is no attribute "HEIGHT"
    			<tr valign="middle" height="28px">

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

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

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

  • Error Line 198, Column 119: required attribute "ALT" not specified
    …r="0" align="left" src="http://www.solvia.es/img/BSolviaBScolorcas_01.jpg"></a>

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

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

  • Error Line 199, Column 111: required attribute "ALT" not specified
    …="http://www.solvia.es/img/menuSup.jpg" border="0" align="right" usemap="#Map">

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

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

  • Warning Line 208, Column 143: NET-enabling start-tag requires SHORTTAG YES
    …24" href="http://www.solvia.es/areapersonal.asp" title="Servicio de alertas" />

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

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

  • Error Line 208, Column 144: character data is not allowed here
    …24" href="http://www.solvia.es/areapersonal.asp" title="Servicio de alertas" />

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

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Warning Line 209, Column 145: NET-enabling start-tag requires SHORTTAG YES
    …40" href="http://www.solvia.es/areapersonal.asp" title="Servicio de alertas" />

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

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

  • Warning Line 212, Column 141: NET-enabling start-tag requires SHORTTAG YES
    …7,24" href="http://www.solvia.es/attCliente.asp" title="Atencion al cliente" />

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

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

  • Warning Line 213, Column 143: NET-enabling start-tag requires SHORTTAG YES
    …7,42" href="http://www.solvia.es/attCliente.asp" title="Atencion al cliente" />

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

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

  • Warning Line 214, Column 49: NET-enabling start-tag requires SHORTTAG YES
    			<area shape="default" nohref="nohref" alt="" />        

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

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

  • Error Line 222, Column 67: required attribute "ALT" not specified
    	<img class="etABS" src="http://www.solvia.es/img/desbNaranja.png">					

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

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

  • Error Line 226, Column 36: required attribute "TYPE" not specified
    </div><script languaje="javascript">

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

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

  • Error Line 267, Column 96: end tag for element "OPTION" which is not open
    …end('<option value="-">'+convertDecNCR2Ascii("Indiferente")+'</option>'); 					

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

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

  • Error Line 271, Column 121: end tag for element "OPTION" which is not open
    …convertDecNCR2Ascii(resultsSep[0]) + '">' + resultsSep[1] + '</option>'); 					

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

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

  • Error Line 287, Column 89: end tag for element "OPTION" which is not open
    …acion').append('<option value="-">'+convertDecNCR2Ascii("")+'</option>'); 					

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

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

  • Error Line 291, Column 125: end tag for element "OPTION" which is not open
    …convertDecNCR2Ascii(resultsSep[0]) + '">' + resultsSep[1] + '</option>'); 					

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

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

  • Error Line 310, Column 89: end tag for element "OPTION" which is not open
    …acion').append('<option value="-">'+convertDecNCR2Ascii("")+'</option>'); 					

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

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

  • Error Line 314, Column 125: end tag for element "OPTION" which is not open
    …convertDecNCR2Ascii(resultsSep[0]) + '">' + resultsSep[1] + '</option>'); 					

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

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

  • Error Line 319, Column 134: end tag for element "A" which is not open
    …or:#333; text-decoration:none' href='#' onClick='actualizaPoblacion()'>+</a>");

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

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

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

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

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

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

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

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

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

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

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

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

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

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

  • Error Line 404, Column 99: required attribute "ALT" not specified
    …"cursor:pointer" onclick="bgooge()" width="16" height="16" src="img/trans.gif">

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

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

  • Warning Line 408, Column 33: NET-enabling start-tag requires SHORTTAG YES
    								¿Qué estás buscando?<br />

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

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

  • Error Line 409, Column 36: required attribute "TYPE" not specified
    								<script language=JavaScript>function Actualiza_idCategoriaTipoVivienda(…

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

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

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

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

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

  • Warning Line 423, Column 22: NET-enabling start-tag requires SHORTTAG YES
    								Provincia<br />

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

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

  • Error Line 424, Column 36: required attribute "TYPE" not specified
    								<script language=JavaScript>function Actualiza_idProvincia(){}</script>…

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

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

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

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

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

  • Warning Line 476, Column 47: NET-enabling start-tag requires SHORTTAG YES
    								Población <div id="pobDesc"></div><br />

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

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

  • Error Line 478, Column 17: end tag for "SELECT" which is not finished
    								</select><br />

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

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

  • Warning Line 478, Column 22: NET-enabling start-tag requires SHORTTAG YES
    								</select><br />

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

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

  • Error Line 485, Column 160: required attribute "ALT" not specified
    …t:buscarMapa()"><img src="http://www.solvia.es/img/btnBuscarPorMapa.png"></div>

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

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

  • Error Line 486, Column 126: required attribute "ALT" not specified
    …_TMP" usemap="#imgMapaOP" src="http://www.solvia.es/img/mapaOportunidades.png">

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

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

  • Warning Line 488, Column 203: cannot generate system identifier for general entity "filtroTipoObraNueva"
    …a.es/resultadosMapa.asp?idProvincia=3&filtroTipoObraNueva=N&filtroTipoSegundaM…

    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 488, Column 203: general entity "filtroTipoObraNueva" not defined and no default entity
    …a.es/resultadosMapa.asp?idProvincia=3&filtroTipoObraNueva=N&filtroTipoSegundaM…

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

  • Error Line 488, Column 222: reference to entity "filtroTipoObraNueva" for which no system identifier could be generated
    ….asp?idProvincia=3&filtroTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"…

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

  • Info Line 488, Column 202: entity was defined here
    …ia.es/resultadosMapa.asp?idProvincia=3&filtroTipoObraNueva=N&filtroTipoSegunda…
  • Warning Line 488, Column 225: cannot generate system identifier for general entity "filtroTipoSegundaMano"
    …p?idProvincia=3&filtroTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  i…

    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 488, Column 225: general entity "filtroTipoSegundaMano" not defined and no default entity
    …p?idProvincia=3&filtroTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  i…

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

  • Error Line 488, Column 246: reference to entity "filtroTipoSegundaMano" for which no system identifier could be generated
    …oTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  id="alicante"  title="…

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

  • Info Line 488, Column 224: entity was defined here
    …sp?idProvincia=3&filtroTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  …
  • Warning Line 488, Column 249: cannot generate system identifier for general entity "mapa"
    …poObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  id="alicante"  title="Ven…

    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 488, Column 249: general entity "mapa" not defined and no default entity
    …poObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  id="alicante"  title="Ven…

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

  • Error Line 488, Column 253: reference to entity "mapa" for which no system identifier could be generated
    …raNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  id="alicante"  title="Venta d…

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

  • Info Line 488, Column 248: entity was defined here
    …ipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  id="alicante"  title="Ve…
  • Warning Line 488, Column 256: cannot generate system identifier for general entity "web"
    …ueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  id="alicante"  title="Venta de i…

    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 488, Column 256: general entity "web" not defined and no default entity
    …ueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  id="alicante"  title="Venta de i…

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

  • Error Line 488, Column 259: reference to entity "web" for which no system identifier could be generated
    …a=N&filtroTipoSegundaMano=N&mapa=S&web=O"  id="alicante"  title="Venta de inmu…

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

  • Info Line 488, Column 255: entity was defined here
    …Nueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  id="alicante"  title="Venta de …
  • Warning Line 488, Column 318: NET-enabling start-tag requires SHORTTAG YES
    …itle="Venta de inmuebles en Alicante" /><area shape="poly" class="mapaHomeOP" …

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

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

  • Error Line 488, Column 318: required attribute "ALT" not specified
    …itle="Venta de inmuebles en Alicante" /><area shape="poly" class="mapaHomeOP" …

    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 488, Column 319: character data is not allowed here
    …tle="Venta de inmuebles en Alicante" /><area shape="poly" class="mapaHomeOP" c…

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

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 488, Column 594: reference to entity "filtroTipoObraNueva" for which no system identifier could be generated
    ….asp?idProvincia=4&filtroTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"…

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

  • Info Line 488, Column 202: entity was defined here
    …ia.es/resultadosMapa.asp?idProvincia=3&filtroTipoObraNueva=N&filtroTipoSegunda…
  • Error Line 488, Column 618: reference to entity "filtroTipoSegundaMano" for which no system identifier could be generated
    …oTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="almeria"  title="Ve…

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

  • Info Line 488, Column 224: entity was defined here
    …sp?idProvincia=3&filtroTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  …
  • Error Line 488, Column 625: reference to entity "mapa" for which no system identifier could be generated
    …raNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="almeria"  title="Venta de …

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

  • Info Line 488, Column 248: entity was defined here
    …ipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  id="alicante"  title="Ve…
  • Error Line 488, Column 631: reference to entity "web" for which no system identifier could be generated
    …a=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="almeria"  title="Venta de inmueb…

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

  • Info Line 488, Column 255: entity was defined here
    …Nueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  id="alicante"  title="Venta de …
  • Warning Line 488, Column 687: NET-enabling start-tag requires SHORTTAG YES
    …title="Venta de inmuebles en Almería" /><area shape="poly" class="mapaHomeOP" …

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

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

  • Error Line 488, Column 687: required attribute "ALT" not specified
    …title="Venta de inmuebles en Almería" /><area shape="poly" class="mapaHomeOP" …

    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 488, Column 875: reference to entity "filtroTipoObraNueva" for which no system identifier could be generated
    ….asp?idProvincia=5&filtroTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"…

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

  • Info Line 488, Column 202: entity was defined here
    …ia.es/resultadosMapa.asp?idProvincia=3&filtroTipoObraNueva=N&filtroTipoSegunda…
  • Error Line 488, Column 899: reference to entity "filtroTipoSegundaMano" for which no system identifier could be generated
    …oTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="avila"  title="Vent…

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

  • Info Line 488, Column 224: entity was defined here
    …sp?idProvincia=3&filtroTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  …
  • Error Line 488, Column 906: reference to entity "mapa" for which no system identifier could be generated
    …raNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="avila"  title="Venta de in…

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

  • Info Line 488, Column 248: entity was defined here
    …ipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  id="alicante"  title="Ve…
  • Error Line 488, Column 912: reference to entity "web" for which no system identifier could be generated
    …a=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="avila"  title="Venta de inmueble…

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

  • Info Line 488, Column 255: entity was defined here
    …Nueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  id="alicante"  title="Venta de …
  • Warning Line 488, Column 964: NET-enabling start-tag requires SHORTTAG YES
    …  title="Venta de inmuebles en Avila" /><area shape="poly" class="mapaHomeOP" …

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

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

  • Error Line 488, Column 964: required attribute "ALT" not specified
    …  title="Venta de inmuebles en Avila" /><area shape="poly" class="mapaHomeOP" …

    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 488, Column 1247: reference to entity "filtroTipoObraNueva" for which no system identifier could be generated
    ….asp?idProvincia=6&filtroTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"…

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

  • Info Line 488, Column 202: entity was defined here
    …ia.es/resultadosMapa.asp?idProvincia=3&filtroTipoObraNueva=N&filtroTipoSegunda…
  • Error Line 488, Column 1271: reference to entity "filtroTipoSegundaMano" for which no system identifier could be generated
    …oTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="badajoz"  title="Ve…

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

  • Info Line 488, Column 224: entity was defined here
    …sp?idProvincia=3&filtroTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  …
  • Error Line 488, Column 1278: reference to entity "mapa" for which no system identifier could be generated
    …raNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="badajoz"  title="Venta de …

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

  • Info Line 488, Column 248: entity was defined here
    …ipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  id="alicante"  title="Ve…
  • Error Line 488, Column 1284: reference to entity "web" for which no system identifier could be generated
    …a=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="badajoz"  title="Venta de inmueb…

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

  • Info Line 488, Column 255: entity was defined here
    …Nueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  id="alicante"  title="Venta de …
  • Warning Line 488, Column 1340: NET-enabling start-tag requires SHORTTAG YES
    …title="Venta de inmuebles en Badajoz" /><area shape="poly" class="mapaHomeOP" …

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

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

  • Error Line 488, Column 1340: required attribute "ALT" not specified
    …title="Venta de inmuebles en Badajoz" /><area shape="poly" class="mapaHomeOP" …

    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 488, Column 1552: reference to entity "filtroTipoObraNueva" for which no system identifier could be generated
    ….asp?idProvincia=8&filtroTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"…

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

  • Info Line 488, Column 202: entity was defined here
    …ia.es/resultadosMapa.asp?idProvincia=3&filtroTipoObraNueva=N&filtroTipoSegunda…
  • Error Line 488, Column 1576: reference to entity "filtroTipoSegundaMano" for which no system identifier could be generated
    …oTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="barcelona"  title="…

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

  • Info Line 488, Column 224: entity was defined here
    …sp?idProvincia=3&filtroTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  …
  • Error Line 488, Column 1583: reference to entity "mapa" for which no system identifier could be generated
    …raNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="barcelona"  title="Venta d…

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

  • Info Line 488, Column 248: entity was defined here
    …ipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  id="alicante"  title="Ve…
  • Error Line 488, Column 1589: reference to entity "web" for which no system identifier could be generated
    …a=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="barcelona"  title="Venta de inmu…

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

  • Info Line 488, Column 255: entity was defined here
    …Nueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  id="alicante"  title="Venta de …
  • Warning Line 488, Column 1649: NET-enabling start-tag requires SHORTTAG YES
    …tle="Venta de inmuebles en Barcelona" /><area shape="poly" class="mapaHomeOP" …

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

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

  • Error Line 488, Column 1649: required attribute "ALT" not specified
    …tle="Venta de inmuebles en Barcelona" /><area shape="poly" class="mapaHomeOP" …

    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 488, Column 1903: reference to entity "filtroTipoObraNueva" for which no system identifier could be generated
    ….asp?idProvincia=9&filtroTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"…

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

  • Info Line 488, Column 202: entity was defined here
    …ia.es/resultadosMapa.asp?idProvincia=3&filtroTipoObraNueva=N&filtroTipoSegunda…
  • Error Line 488, Column 1927: reference to entity "filtroTipoSegundaMano" for which no system identifier could be generated
    …oTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="burgos"  title="Ven…

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

  • Info Line 488, Column 224: entity was defined here
    …sp?idProvincia=3&filtroTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  …
  • Error Line 488, Column 1934: reference to entity "mapa" for which no system identifier could be generated
    …raNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="burgos"  title="Venta de i…

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

  • Info Line 488, Column 248: entity was defined here
    …ipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  id="alicante"  title="Ve…
  • Error Line 488, Column 1940: reference to entity "web" for which no system identifier could be generated
    …a=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="burgos"  title="Venta de inmuebl…

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

  • Info Line 488, Column 255: entity was defined here
    …Nueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  id="alicante"  title="Venta de …
  • Warning Line 488, Column 1994: NET-enabling start-tag requires SHORTTAG YES
    … title="Venta de inmuebles en Burgos" /><area shape="poly" class="mapaHomeOP" …

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

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

  • Error Line 488, Column 1994: required attribute "ALT" not specified
    … title="Venta de inmuebles en Burgos" /><area shape="poly" class="mapaHomeOP" …

    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 488, Column 2213: reference to entity "filtroTipoObraNueva" for which no system identifier could be generated
    …asp?idProvincia=10&filtroTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"…

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

  • Info Line 488, Column 202: entity was defined here
    …ia.es/resultadosMapa.asp?idProvincia=3&filtroTipoObraNueva=N&filtroTipoSegunda…
  • Error Line 488, Column 2237: reference to entity "filtroTipoSegundaMano" for which no system identifier could be generated
    …oTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="caceres"  title="Ve…

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

  • Info Line 488, Column 224: entity was defined here
    …sp?idProvincia=3&filtroTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  …
  • Error Line 488, Column 2244: reference to entity "mapa" for which no system identifier could be generated
    …raNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="caceres"  title="Venta de …

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

  • Info Line 488, Column 248: entity was defined here
    …ipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  id="alicante"  title="Ve…
  • Error Line 488, Column 2250: reference to entity "web" for which no system identifier could be generated
    …a=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="caceres"  title="Venta de inmueb…

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

  • Info Line 488, Column 255: entity was defined here
    …Nueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  id="alicante"  title="Venta de …
  • Warning Line 488, Column 2306: NET-enabling start-tag requires SHORTTAG YES
    …title="Venta de inmuebles en Cáceres" /><area shape="poly" class="mapaHomeOP" …

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

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

  • Error Line 488, Column 2306: required attribute "ALT" not specified
    …title="Venta de inmuebles en Cáceres" /><area shape="poly" class="mapaHomeOP" …

    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 488, Column 2540: reference to entity "filtroTipoObraNueva" for which no system identifier could be generated
    …asp?idProvincia=11&filtroTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"…

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

  • Info Line 488, Column 202: entity was defined here
    …ia.es/resultadosMapa.asp?idProvincia=3&filtroTipoObraNueva=N&filtroTipoSegunda…
  • Error Line 488, Column 2564: reference to entity "filtroTipoSegundaMano" for which no system identifier could be generated
    …oTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="cadiz"  title="Vent…

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

  • Info Line 488, Column 224: entity was defined here
    …sp?idProvincia=3&filtroTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  …
  • Error Line 488, Column 2571: reference to entity "mapa" for which no system identifier could be generated
    …raNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="cadiz"  title="Venta de in…

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

  • Info Line 488, Column 248: entity was defined here
    …ipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  id="alicante"  title="Ve…
  • Error Line 488, Column 2577: reference to entity "web" for which no system identifier could be generated
    …a=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="cadiz"  title="Venta de inmueble…

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

  • Info Line 488, Column 255: entity was defined here
    …Nueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  id="alicante"  title="Venta de …
  • Warning Line 488, Column 2629: NET-enabling start-tag requires SHORTTAG YES
    …  title="Venta de inmuebles en Cádiz" /><area shape="poly" class="mapaHomeOP" …

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

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

  • Error Line 488, Column 2629: required attribute "ALT" not specified
    …  title="Venta de inmuebles en Cádiz" /><area shape="poly" class="mapaHomeOP" …

    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 488, Column 2821: reference to entity "filtroTipoObraNueva" for which no system identifier could be generated
    …asp?idProvincia=12&filtroTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"…

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

  • Info Line 488, Column 202: entity was defined here
    …ia.es/resultadosMapa.asp?idProvincia=3&filtroTipoObraNueva=N&filtroTipoSegunda…
  • Error Line 488, Column 2845: reference to entity "filtroTipoSegundaMano" for which no system identifier could be generated
    …oTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="castellon"  title="…

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

  • Info Line 488, Column 224: entity was defined here
    …sp?idProvincia=3&filtroTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  …
  • Error Line 488, Column 2852: reference to entity "mapa" for which no system identifier could be generated
    …raNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="castellon"  title="Venta d…

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

  • Info Line 488, Column 248: entity was defined here
    …ipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  id="alicante"  title="Ve…
  • Error Line 488, Column 2858: reference to entity "web" for which no system identifier could be generated
    …a=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="castellon"  title="Venta de inmu…

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

  • Info Line 488, Column 255: entity was defined here
    …Nueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  id="alicante"  title="Venta de …
  • Warning Line 488, Column 2918: NET-enabling start-tag requires SHORTTAG YES
    …tle="Venta de inmuebles en Castellon" /><area shape="poly" class="mapaHomeOP" …

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

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

  • Error Line 488, Column 2918: required attribute "ALT" not specified
    …tle="Venta de inmuebles en Castellon" /><area shape="poly" class="mapaHomeOP" …

    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 488, Column 3154: reference to entity "filtroTipoObraNueva" for which no system identifier could be generated
    …asp?idProvincia=13&filtroTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"…

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

  • Info Line 488, Column 202: entity was defined here
    …ia.es/resultadosMapa.asp?idProvincia=3&filtroTipoObraNueva=N&filtroTipoSegunda…
  • Error Line 488, Column 3178: reference to entity "filtroTipoSegundaMano" for which no system identifier could be generated
    …oTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="ciudadReal"  title=…

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

  • Info Line 488, Column 224: entity was defined here
    …sp?idProvincia=3&filtroTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  …
  • Error Line 488, Column 3185: reference to entity "mapa" for which no system identifier could be generated
    …raNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="ciudadReal"  title="Venta …

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

  • Info Line 488, Column 248: entity was defined here
    …ipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  id="alicante"  title="Ve…
  • Error Line 488, Column 3191: reference to entity "web" for which no system identifier could be generated
    …a=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="ciudadReal"  title="Venta de inm…

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

  • Info Line 488, Column 255: entity was defined here
    …Nueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  id="alicante"  title="Venta de …
  • Warning Line 488, Column 3254: NET-enabling start-tag requires SHORTTAG YES
    …e="Venta de inmuebles en Ciudad Real" /><area shape="poly" class="mapaHomeOP" …

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

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

  • Error Line 488, Column 3254: required attribute "ALT" not specified
    …e="Venta de inmuebles en Ciudad Real" /><area shape="poly" class="mapaHomeOP" …

    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 488, Column 3474: reference to entity "filtroTipoObraNueva" for which no system identifier could be generated
    …asp?idProvincia=14&filtroTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"…

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

  • Info Line 488, Column 202: entity was defined here
    …ia.es/resultadosMapa.asp?idProvincia=3&filtroTipoObraNueva=N&filtroTipoSegunda…
  • Error Line 488, Column 3498: reference to entity "filtroTipoSegundaMano" for which no system identifier could be generated
    …oTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="cordoba"  title="Ve…

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

  • Info Line 488, Column 224: entity was defined here
    …sp?idProvincia=3&filtroTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  …
  • Error Line 488, Column 3505: reference to entity "mapa" for which no system identifier could be generated
    …raNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="cordoba"  title="Venta de …

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

  • Info Line 488, Column 248: entity was defined here
    …ipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  id="alicante"  title="Ve…
  • Error Line 488, Column 3511: reference to entity "web" for which no system identifier could be generated
    …a=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="cordoba"  title="Venta de inmueb…

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

  • Info Line 488, Column 255: entity was defined here
    …Nueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  id="alicante"  title="Venta de …
  • Warning Line 488, Column 3567: NET-enabling start-tag requires SHORTTAG YES
    …title="Venta de inmuebles en Córdoba" /><area shape="poly" class="mapaHomeOP" …

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

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

  • Error Line 488, Column 3567: required attribute "ALT" not specified
    …title="Venta de inmuebles en Córdoba" /><area shape="poly" class="mapaHomeOP" …

    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 488, Column 3777: reference to entity "filtroTipoObraNueva" for which no system identifier could be generated
    …asp?idProvincia=15&filtroTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"…

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

  • Info Line 488, Column 202: entity was defined here
    …ia.es/resultadosMapa.asp?idProvincia=3&filtroTipoObraNueva=N&filtroTipoSegunda…
  • Error Line 488, Column 3801: reference to entity "filtroTipoSegundaMano" for which no system identifier could be generated
    …oTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="laCoruna"  title="V…

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

  • Info Line 488, Column 224: entity was defined here
    …sp?idProvincia=3&filtroTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  …
  • Error Line 488, Column 3808: reference to entity "mapa" for which no system identifier could be generated
    …raNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="laCoruna"  title="Venta de…

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

  • Info Line 488, Column 248: entity was defined here
    …ipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  id="alicante"  title="Ve…
  • Error Line 488, Column 3814: reference to entity "web" for which no system identifier could be generated
    …a=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="laCoruna"  title="Venta de inmue…

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

  • Info Line 488, Column 255: entity was defined here
    …Nueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  id="alicante"  title="Venta de …
  • Warning Line 488, Column 3874: NET-enabling start-tag requires SHORTTAG YES
    …le="Venta de inmuebles en Coruña (A)" /><area shape="poly" class="mapaHomeOP" …

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

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

  • Error Line 488, Column 3874: required attribute "ALT" not specified
    …le="Venta de inmuebles en Coruña (A)" /><area shape="poly" class="mapaHomeOP" …

    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 488, Column 4116: reference to entity "filtroTipoObraNueva" for which no system identifier could be generated
    …asp?idProvincia=16&filtroTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"…

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

  • Info Line 488, Column 202: entity was defined here
    …ia.es/resultadosMapa.asp?idProvincia=3&filtroTipoObraNueva=N&filtroTipoSegunda…
  • Error Line 488, Column 4140: reference to entity "filtroTipoSegundaMano" for which no system identifier could be generated
    …oTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="cuenca"  title="Ven…

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

  • Info Line 488, Column 224: entity was defined here
    …sp?idProvincia=3&filtroTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  …
  • Error Line 488, Column 4147: reference to entity "mapa" for which no system identifier could be generated
    …raNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="cuenca"  title="Venta de i…

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

  • Info Line 488, Column 248: entity was defined here
    …ipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  id="alicante"  title="Ve…
  • Error Line 488, Column 4153: reference to entity "web" for which no system identifier could be generated
    …a=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="cuenca"  title="Venta de inmuebl…

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

  • Info Line 488, Column 255: entity was defined here
    …Nueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  id="alicante"  title="Venta de …
  • Warning Line 488, Column 4207: NET-enabling start-tag requires SHORTTAG YES
    … title="Venta de inmuebles en Cuenca" /><area shape="poly" class="mapaHomeOP" …

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

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

  • Error Line 488, Column 4207: required attribute "ALT" not specified
    … title="Venta de inmuebles en Cuenca" /><area shape="poly" class="mapaHomeOP" …

    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 488, Column 4406: reference to entity "filtroTipoObraNueva" for which no system identifier could be generated
    …asp?idProvincia=17&filtroTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"…

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

  • Info Line 488, Column 202: entity was defined here
    …ia.es/resultadosMapa.asp?idProvincia=3&filtroTipoObraNueva=N&filtroTipoSegunda…
  • Error Line 488, Column 4430: reference to entity "filtroTipoSegundaMano" for which no system identifier could be generated
    …oTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="gerona"  title="Ven…

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

  • Info Line 488, Column 224: entity was defined here
    …sp?idProvincia=3&filtroTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  …
  • Error Line 488, Column 4437: reference to entity "mapa" for which no system identifier could be generated
    …raNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="gerona"  title="Venta de i…

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

  • Info Line 488, Column 248: entity was defined here
    …ipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  id="alicante"  title="Ve…
  • Error Line 488, Column 4443: reference to entity "web" for which no system identifier could be generated
    …a=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="gerona"  title="Venta de inmuebl…

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

  • Info Line 488, Column 255: entity was defined here
    …Nueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  id="alicante"  title="Venta de …
  • Warning Line 488, Column 4497: NET-enabling start-tag requires SHORTTAG YES
    … title="Venta de inmuebles en Girona" /><area shape="poly" class="mapaHomeOP" …

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

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

  • Error Line 488, Column 4497: required attribute "ALT" not specified
    … title="Venta de inmuebles en Girona" /><area shape="poly" class="mapaHomeOP" …

    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 488, Column 4728: reference to entity "filtroTipoObraNueva" for which no system identifier could be generated
    …asp?idProvincia=18&filtroTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"…

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

  • Info Line 488, Column 202: entity was defined here
    …ia.es/resultadosMapa.asp?idProvincia=3&filtroTipoObraNueva=N&filtroTipoSegunda…
  • Error Line 488, Column 4752: reference to entity "filtroTipoSegundaMano" for which no system identifier could be generated
    …oTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="granada"  title="Ve…

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

  • Info Line 488, Column 224: entity was defined here
    …sp?idProvincia=3&filtroTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  …
  • Error Line 488, Column 4759: reference to entity "mapa" for which no system identifier could be generated
    …raNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="granada"  title="Venta de …

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

  • Info Line 488, Column 248: entity was defined here
    …ipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  id="alicante"  title="Ve…
  • Error Line 488, Column 4765: reference to entity "web" for which no system identifier could be generated
    …a=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="granada"  title="Venta de inmueb…

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

  • Info Line 488, Column 255: entity was defined here
    …Nueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  id="alicante"  title="Venta de …
  • Warning Line 488, Column 4821: NET-enabling start-tag requires SHORTTAG YES
    …title="Venta de inmuebles en Granada" /><area shape="poly" class="mapaHomeOP" …

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

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

  • Error Line 488, Column 4821: required attribute "ALT" not specified
    …title="Venta de inmuebles en Granada" /><area shape="poly" class="mapaHomeOP" …

    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 488, Column 5053: reference to entity "filtroTipoObraNueva" for which no system identifier could be generated
    …asp?idProvincia=19&filtroTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"…

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

  • Info Line 488, Column 202: entity was defined here
    …ia.es/resultadosMapa.asp?idProvincia=3&filtroTipoObraNueva=N&filtroTipoSegunda…
  • Error Line 488, Column 5077: reference to entity "filtroTipoSegundaMano" for which no system identifier could be generated
    …oTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="guadalajara"  title…

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

  • Info Line 488, Column 224: entity was defined here
    …sp?idProvincia=3&filtroTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  …
  • Error Line 488, Column 5084: reference to entity "mapa" for which no system identifier could be generated
    …raNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="guadalajara"  title="Venta…

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

  • Info Line 488, Column 248: entity was defined here
    …ipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  id="alicante"  title="Ve…
  • Error Line 488, Column 5090: reference to entity "web" for which no system identifier could be generated
    …a=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="guadalajara"  title="Venta de in…

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

  • Info Line 488, Column 255: entity was defined here
    …Nueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  id="alicante"  title="Venta de …
  • Warning Line 488, Column 5154: NET-enabling start-tag requires SHORTTAG YES
    …e="Venta de inmuebles en Guadalajara" /><area shape="poly" class="mapaHomeOP" …

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

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

  • Error Line 488, Column 5154: required attribute "ALT" not specified
    …e="Venta de inmuebles en Guadalajara" /><area shape="poly" class="mapaHomeOP" …

    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 488, Column 5433: reference to entity "filtroTipoObraNueva" for which no system identifier could be generated
    …sp?idProvincia=203&filtroTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"…

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

  • Info Line 488, Column 202: entity was defined here
    …ia.es/resultadosMapa.asp?idProvincia=3&filtroTipoObraNueva=N&filtroTipoSegunda…
  • Error Line 488, Column 5457: reference to entity "filtroTipoSegundaMano" for which no system identifier could be generated
    …oTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="albacete"  title="V…

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

  • Info Line 488, Column 224: entity was defined here
    …sp?idProvincia=3&filtroTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  …
  • Error Line 488, Column 5464: reference to entity "mapa" for which no system identifier could be generated
    …raNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="albacete"  title="Venta de…

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

  • Info Line 488, Column 248: entity was defined here
    …ipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  id="alicante"  title="Ve…
  • Error Line 488, Column 5470: reference to entity "web" for which no system identifier could be generated
    …a=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="albacete"  title="Venta de inmue…

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

  • Info Line 488, Column 255: entity was defined here
    …Nueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  id="alicante"  title="Venta de …
  • Warning Line 488, Column 5528: NET-enabling start-tag requires SHORTTAG YES
    …itle="Venta de inmuebles en Albacete" /><area shape="poly" class="mapaHomeOP" …

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

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

  • Error Line 488, Column 5528: required attribute "ALT" not specified
    …itle="Venta de inmuebles en Albacete" /><area shape="poly" class="mapaHomeOP" …

    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 488, Column 5731: reference to entity "filtroTipoObraNueva" for which no system identifier could be generated
    …asp?idProvincia=20&filtroTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"…

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

  • Info Line 488, Column 202: entity was defined here
    …ia.es/resultadosMapa.asp?idProvincia=3&filtroTipoObraNueva=N&filtroTipoSegunda…
  • Error Line 488, Column 5755: reference to entity "filtroTipoSegundaMano" for which no system identifier could be generated
    …oTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="guipuzcoa"  title="…

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

  • Info Line 488, Column 224: entity was defined here
    …sp?idProvincia=3&filtroTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  …
  • Error Line 488, Column 5762: reference to entity "mapa" for which no system identifier could be generated
    …raNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="guipuzcoa"  title="Venta d…

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

  • Info Line 488, Column 248: entity was defined here
    …ipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  id="alicante"  title="Ve…
  • Error Line 488, Column 5768: reference to entity "web" for which no system identifier could be generated
    …a=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="guipuzcoa"  title="Venta de inmu…

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

  • Info Line 488, Column 255: entity was defined here
    …Nueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  id="alicante"  title="Venta de …
  • Warning Line 488, Column 5828: NET-enabling start-tag requires SHORTTAG YES
    …tle="Venta de inmuebles en Guipúzcoa" /><area shape="poly" class="mapaHomeOP" …

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

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

  • Error Line 488, Column 5828: required attribute "ALT" not specified
    …tle="Venta de inmuebles en Guipúzcoa" /><area shape="poly" class="mapaHomeOP" …

    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 488, Column 6083: reference to entity "filtroTipoObraNueva" for which no system identifier could be generated
    …asp?idProvincia=21&filtroTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"…

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

  • Info Line 488, Column 202: entity was defined here
    …ia.es/resultadosMapa.asp?idProvincia=3&filtroTipoObraNueva=N&filtroTipoSegunda…
  • Error Line 488, Column 6107: reference to entity "filtroTipoSegundaMano" for which no system identifier could be generated
    …oTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="huelva"  title="Ven…

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

  • Info Line 488, Column 224: entity was defined here
    …sp?idProvincia=3&filtroTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  …
  • Error Line 488, Column 6114: reference to entity "mapa" for which no system identifier could be generated
    …raNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="huelva"  title="Venta de i…

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

  • Info Line 488, Column 248: entity was defined here
    …ipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  id="alicante"  title="Ve…
  • Error Line 488, Column 6120: reference to entity "web" for which no system identifier could be generated
    …a=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="huelva"  title="Venta de inmuebl…

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

  • Info Line 488, Column 255: entity was defined here
    …Nueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  id="alicante"  title="Venta de …
  • Warning Line 488, Column 6174: NET-enabling start-tag requires SHORTTAG YES
    … title="Venta de inmuebles en Huelva" /><area shape="poly" class="mapaHomeOP" …

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

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

  • Error Line 488, Column 6174: required attribute "ALT" not specified
    … title="Venta de inmuebles en Huelva" /><area shape="poly" class="mapaHomeOP" …

    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 488, Column 6401: reference to entity "filtroTipoObraNueva" for which no system identifier could be generated
    …asp?idProvincia=22&filtroTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"…

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

  • Info Line 488, Column 202: entity was defined here
    …ia.es/resultadosMapa.asp?idProvincia=3&filtroTipoObraNueva=N&filtroTipoSegunda…
  • Error Line 488, Column 6425: reference to entity "filtroTipoSegundaMano" for which no system identifier could be generated
    …oTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="huesca"  title="Ven…

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

  • Info Line 488, Column 224: entity was defined here
    …sp?idProvincia=3&filtroTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  …
  • Error Line 488, Column 6432: reference to entity "mapa" for which no system identifier could be generated
    …raNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="huesca"  title="Venta de i…

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

  • Info Line 488, Column 248: entity was defined here
    …ipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  id="alicante"  title="Ve…
  • Error Line 488, Column 6438: reference to entity "web" for which no system identifier could be generated
    …a=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="huesca"  title="Venta de inmuebl…

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

  • Info Line 488, Column 255: entity was defined here
    …Nueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  id="alicante"  title="Venta de …
  • Warning Line 488, Column 6492: NET-enabling start-tag requires SHORTTAG YES
    … title="Venta de inmuebles en Huesca" /><area shape="poly" class="mapaHomeOP" …

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

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

  • Error Line 488, Column 6492: required attribute "ALT" not specified
    … title="Venta de inmuebles en Huesca" /><area shape="poly" class="mapaHomeOP" …

    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 488, Column 6700: reference to entity "filtroTipoObraNueva" for which no system identifier could be generated
    …asp?idProvincia=23&filtroTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"…

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

  • Info Line 488, Column 202: entity was defined here
    …ia.es/resultadosMapa.asp?idProvincia=3&filtroTipoObraNueva=N&filtroTipoSegunda…
  • Error Line 488, Column 6724: reference to entity "filtroTipoSegundaMano" for which no system identifier could be generated
    …oTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="jaen"  title="Venta…

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

  • Info Line 488, Column 224: entity was defined here
    …sp?idProvincia=3&filtroTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  …
  • Error Line 488, Column 6731: reference to entity "mapa" for which no system identifier could be generated
    …raNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="jaen"  title="Venta de inm…

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

  • Info Line 488, Column 248: entity was defined here
    …ipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  id="alicante"  title="Ve…
  • Error Line 488, Column 6737: reference to entity "web" for which no system identifier could be generated
    …a=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="jaen"  title="Venta de inmuebles…

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

  • Info Line 488, Column 255: entity was defined here
    …Nueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  id="alicante"  title="Venta de …
  • Warning Line 488, Column 6787: NET-enabling start-tag requires SHORTTAG YES
    …"  title="Venta de inmuebles en Jaén" /><area shape="poly" class="mapaHomeOP" …

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

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

  • Error Line 488, Column 6787: required attribute "ALT" not specified
    …"  title="Venta de inmuebles en Jaén" /><area shape="poly" class="mapaHomeOP" …

    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 488, Column 7012: reference to entity "filtroTipoObraNueva" for which no system identifier could be generated
    …asp?idProvincia=24&filtroTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"…

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

  • Info Line 488, Column 202: entity was defined here
    …ia.es/resultadosMapa.asp?idProvincia=3&filtroTipoObraNueva=N&filtroTipoSegunda…
  • Error Line 488, Column 7036: reference to entity "filtroTipoSegundaMano" for which no system identifier could be generated
    …oTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="leon"  title="Venta…

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

  • Info Line 488, Column 224: entity was defined here
    …sp?idProvincia=3&filtroTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  …
  • Error Line 488, Column 7043: reference to entity "mapa" for which no system identifier could be generated
    …raNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="leon"  title="Venta de inm…

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

  • Info Line 488, Column 248: entity was defined here
    …ipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  id="alicante"  title="Ve…
  • Error Line 488, Column 7049: reference to entity "web" for which no system identifier could be generated
    …a=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="leon"  title="Venta de inmuebles…

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

  • Info Line 488, Column 255: entity was defined here
    …Nueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  id="alicante"  title="Venta de …
  • Warning Line 488, Column 7099: NET-enabling start-tag requires SHORTTAG YES
    …"  title="Venta de inmuebles en León" /><area shape="poly" class="mapaHomeOP" …

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

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

  • Error Line 488, Column 7099: required attribute "ALT" not specified
    …"  title="Venta de inmuebles en León" /><area shape="poly" class="mapaHomeOP" …

    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 488, Column 7333: reference to entity "filtroTipoObraNueva" for which no system identifier could be generated
    …asp?idProvincia=25&filtroTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"…

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

  • Info Line 488, Column 202: entity was defined here
    …ia.es/resultadosMapa.asp?idProvincia=3&filtroTipoObraNueva=N&filtroTipoSegunda…
  • Error Line 488, Column 7357: reference to entity "filtroTipoSegundaMano" for which no system identifier could be generated
    …oTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="lerida"  title="Ven…

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

  • Info Line 488, Column 224: entity was defined here
    …sp?idProvincia=3&filtroTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  …
  • Error Line 488, Column 7364: reference to entity "mapa" for which no system identifier could be generated
    …raNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="lerida"  title="Venta de i…

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

  • Info Line 488, Column 248: entity was defined here
    …ipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  id="alicante"  title="Ve…
  • Error Line 488, Column 7370: reference to entity "web" for which no system identifier could be generated
    …a=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="lerida"  title="Venta de inmuebl…

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

  • Info Line 488, Column 255: entity was defined here
    …Nueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  id="alicante"  title="Venta de …
  • Warning Line 488, Column 7424: NET-enabling start-tag requires SHORTTAG YES
    … title="Venta de inmuebles en Lleida" /><area shape="poly" class="mapaHomeOP" …

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

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

  • Error Line 488, Column 7424: required attribute "ALT" not specified
    … title="Venta de inmuebles en Lleida" /><area shape="poly" class="mapaHomeOP" …

    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 488, Column 7638: reference to entity "filtroTipoObraNueva" for which no system identifier could be generated
    …asp?idProvincia=26&filtroTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"…

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

  • Info Line 488, Column 202: entity was defined here
    …ia.es/resultadosMapa.asp?idProvincia=3&filtroTipoObraNueva=N&filtroTipoSegunda…
  • Error Line 488, Column 7662: reference to entity "filtroTipoSegundaMano" for which no system identifier could be generated
    …oTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="LaRioja"  title="Ve…

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

  • Info Line 488, Column 224: entity was defined here
    …sp?idProvincia=3&filtroTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  …
  • Error Line 488, Column 7669: reference to entity "mapa" for which no system identifier could be generated
    …raNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="LaRioja"  title="Venta de …

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

  • Info Line 488, Column 248: entity was defined here
    …ipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  id="alicante"  title="Ve…
  • Error Line 488, Column 7675: reference to entity "web" for which no system identifier could be generated
    …a=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="LaRioja"  title="Venta de inmueb…

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

  • Info Line 488, Column 255: entity was defined here
    …Nueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  id="alicante"  title="Venta de …
  • Warning Line 488, Column 7734: NET-enabling start-tag requires SHORTTAG YES
    …le="Venta de inmuebles en Rioja (La)" /><area shape="poly" class="mapaHomeOP" …

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

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

  • Error Line 488, Column 7734: required attribute "ALT" not specified
    …le="Venta de inmuebles en Rioja (La)" /><area shape="poly" class="mapaHomeOP" …

    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 488, Column 7930: reference to entity "filtroTipoObraNueva" for which no system identifier could be generated
    …asp?idProvincia=27&filtroTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"…

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

  • Info Line 488, Column 202: entity was defined here
    …ia.es/resultadosMapa.asp?idProvincia=3&filtroTipoObraNueva=N&filtroTipoSegunda…
  • Error Line 488, Column 7954: reference to entity "filtroTipoSegundaMano" for which no system identifier could be generated
    …oTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="lugo"  title="Venta…

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

  • Info Line 488, Column 224: entity was defined here
    …sp?idProvincia=3&filtroTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  …
  • Error Line 488, Column 7961: reference to entity "mapa" for which no system identifier could be generated
    …raNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="lugo"  title="Venta de inm…

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

  • Info Line 488, Column 248: entity was defined here
    …ipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  id="alicante"  title="Ve…
  • Error Line 488, Column 7967: reference to entity "web" for which no system identifier could be generated
    …a=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="lugo"  title="Venta de inmuebles…

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

  • Info Line 488, Column 255: entity was defined here
    …Nueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  id="alicante"  title="Venta de …
  • Warning Line 488, Column 8017: NET-enabling start-tag requires SHORTTAG YES
    …"  title="Venta de inmuebles en Lugo" /><area shape="poly" class="mapaHomeOP" …

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

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

  • Error Line 488, Column 8017: required attribute "ALT" not specified
    …"  title="Venta de inmuebles en Lugo" /><area shape="poly" class="mapaHomeOP" …

    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 488, Column 8242: reference to entity "filtroTipoObraNueva" for which no system identifier could be generated
    …asp?idProvincia=28&filtroTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"…

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

  • Info Line 488, Column 202: entity was defined here
    …ia.es/resultadosMapa.asp?idProvincia=3&filtroTipoObraNueva=N&filtroTipoSegunda…
  • Error Line 488, Column 8266: reference to entity "filtroTipoSegundaMano" for which no system identifier could be generated
    …oTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="madrid"  title="Ven…

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

  • Info Line 488, Column 224: entity was defined here
    …sp?idProvincia=3&filtroTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  …
  • Error Line 488, Column 8273: reference to entity "mapa" for which no system identifier could be generated
    …raNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="madrid"  title="Venta de i…

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

  • Info Line 488, Column 248: entity was defined here
    …ipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  id="alicante"  title="Ve…
  • Error Line 488, Column 8279: reference to entity "web" for which no system identifier could be generated
    …a=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="madrid"  title="Venta de inmuebl…

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

  • Info Line 488, Column 255: entity was defined here
    …Nueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  id="alicante"  title="Venta de …
  • Warning Line 488, Column 8333: NET-enabling start-tag requires SHORTTAG YES
    … title="Venta de inmuebles en Madrid" /><area shape="poly" class="mapaHomeOP" …

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

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

  • Error Line 488, Column 8333: required attribute "ALT" not specified
    … title="Venta de inmuebles en Madrid" /><area shape="poly" class="mapaHomeOP" …

    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 488, Column 8553: reference to entity "filtroTipoObraNueva" for which no system identifier could be generated
    …asp?idProvincia=29&filtroTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"…

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

  • Info Line 488, Column 202: entity was defined here
    …ia.es/resultadosMapa.asp?idProvincia=3&filtroTipoObraNueva=N&filtroTipoSegunda…
  • Error Line 488, Column 8577: reference to entity "filtroTipoSegundaMano" for which no system identifier could be generated
    …oTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="malaga"  title="Ven…

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

  • Info Line 488, Column 224: entity was defined here
    …sp?idProvincia=3&filtroTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  …
  • Error Line 488, Column 8584: reference to entity "mapa" for which no system identifier could be generated
    …raNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="malaga"  title="Venta de i…

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

  • Info Line 488, Column 248: entity was defined here
    …ipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  id="alicante"  title="Ve…
  • Error Line 488, Column 8590: reference to entity "web" for which no system identifier could be generated
    …a=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="malaga"  title="Venta de inmuebl…

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

  • Info Line 488, Column 255: entity was defined here
    …Nueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  id="alicante"  title="Venta de …
  • Warning Line 488, Column 8644: NET-enabling start-tag requires SHORTTAG YES
    … title="Venta de inmuebles en Málaga" /><area shape="poly" class="mapaHomeOP" …

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

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

  • Error Line 488, Column 8644: required attribute "ALT" not specified
    … title="Venta de inmuebles en Málaga" /><area shape="poly" class="mapaHomeOP" …

    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 488, Column 8941: reference to entity "filtroTipoObraNueva" for which no system identifier could be generated
    …asp?idProvincia=30&filtroTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"…

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

  • Info Line 488, Column 202: entity was defined here
    …ia.es/resultadosMapa.asp?idProvincia=3&filtroTipoObraNueva=N&filtroTipoSegunda…
  • Error Line 488, Column 8965: reference to entity "filtroTipoSegundaMano" for which no system identifier could be generated
    …oTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="murcia"  title="Ven…

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

  • Info Line 488, Column 224: entity was defined here
    …sp?idProvincia=3&filtroTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  …
  • Error Line 488, Column 8972: reference to entity "mapa" for which no system identifier could be generated
    …raNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="murcia"  title="Venta de i…

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

  • Info Line 488, Column 248: entity was defined here
    …ipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  id="alicante"  title="Ve…
  • Error Line 488, Column 8978: reference to entity "web" for which no system identifier could be generated
    …a=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="murcia"  title="Venta de inmuebl…

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

  • Info Line 488, Column 255: entity was defined here
    …Nueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  id="alicante"  title="Venta de …
  • Warning Line 488, Column 9032: NET-enabling start-tag requires SHORTTAG YES
    … title="Venta de inmuebles en Murcia" /><area shape="poly" class="mapaHomeOP" …

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

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

  • Error Line 488, Column 9032: required attribute "ALT" not specified
    … title="Venta de inmuebles en Murcia" /><area shape="poly" class="mapaHomeOP" …

    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 488, Column 9301: reference to entity "filtroTipoObraNueva" for which no system identifier could be generated
    …asp?idProvincia=31&filtroTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"…

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

  • Info Line 488, Column 202: entity was defined here
    …ia.es/resultadosMapa.asp?idProvincia=3&filtroTipoObraNueva=N&filtroTipoSegunda…
  • Error Line 488, Column 9325: reference to entity "filtroTipoSegundaMano" for which no system identifier could be generated
    …oTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="navarra"  title="Ve…

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

  • Info Line 488, Column 224: entity was defined here
    …sp?idProvincia=3&filtroTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  …
  • Error Line 488, Column 9332: reference to entity "mapa" for which no system identifier could be generated
    …raNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="navarra"  title="Venta de …

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

  • Info Line 488, Column 248: entity was defined here
    …ipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  id="alicante"  title="Ve…
  • Error Line 488, Column 9338: reference to entity "web" for which no system identifier could be generated
    …a=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="navarra"  title="Venta de inmueb…

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

  • Info Line 488, Column 255: entity was defined here
    …Nueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  id="alicante"  title="Venta de …
  • Warning Line 488, Column 9394: NET-enabling start-tag requires SHORTTAG YES
    …title="Venta de inmuebles en Navarra" /><area shape="poly" class="mapaHomeOP" …

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

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

  • Error Line 488, Column 9394: required attribute "ALT" not specified
    …title="Venta de inmuebles en Navarra" /><area shape="poly" class="mapaHomeOP" …

    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 488, Column 9637: reference to entity "filtroTipoObraNueva" for which no system identifier could be generated
    …asp?idProvincia=32&filtroTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"…

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

  • Info Line 488, Column 202: entity was defined here
    …ia.es/resultadosMapa.asp?idProvincia=3&filtroTipoObraNueva=N&filtroTipoSegunda…
  • Error Line 488, Column 9661: reference to entity "filtroTipoSegundaMano" for which no system identifier could be generated
    …oTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="orense"  title="Ven…

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

  • Info Line 488, Column 224: entity was defined here
    …sp?idProvincia=3&filtroTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  …
  • Error Line 488, Column 9668: reference to entity "mapa" for which no system identifier could be generated
    …raNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="orense"  title="Venta de i…

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

  • Info Line 488, Column 248: entity was defined here
    …ipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  id="alicante"  title="Ve…
  • Error Line 488, Column 9674: reference to entity "web" for which no system identifier could be generated
    …a=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="orense"  title="Venta de inmuebl…

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

  • Info Line 488, Column 255: entity was defined here
    …Nueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  id="alicante"  title="Venta de …
  • Warning Line 488, Column 9729: NET-enabling start-tag requires SHORTTAG YES
    …title="Venta de inmuebles en Ourense" /><area shape="poly" class="mapaHomeOP" …

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

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

  • Error Line 488, Column 9729: required attribute "ALT" not specified
    …title="Venta de inmuebles en Ourense" /><area shape="poly" class="mapaHomeOP" …

    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 488, Column 9917: reference to entity "filtroTipoObraNueva" for which no system identifier could be generated
    …asp?idProvincia=33&filtroTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"…

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

  • Info Line 488, Column 202: entity was defined here
    …ia.es/resultadosMapa.asp?idProvincia=3&filtroTipoObraNueva=N&filtroTipoSegunda…
  • Error Line 488, Column 9941: reference to entity "filtroTipoSegundaMano" for which no system identifier could be generated
    …oTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="asturias"  title="V…

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

  • Info Line 488, Column 224: entity was defined here
    …sp?idProvincia=3&filtroTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  …
  • Error Line 488, Column 9948: reference to entity "mapa" for which no system identifier could be generated
    …raNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="asturias"  title="Venta de…

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

  • Info Line 488, Column 248: entity was defined here
    …ipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  id="alicante"  title="Ve…
  • Error Line 488, Column 9954: reference to entity "web" for which no system identifier could be generated
    …a=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="asturias"  title="Venta de inmue…

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

  • Info Line 488, Column 255: entity was defined here
    …Nueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  id="alicante"  title="Venta de …
  • Warning Line 488, Column 10012: NET-enabling start-tag requires SHORTTAG YES
    …itle="Venta de inmuebles en Asturias" /><area shape="poly" class="mapaHomeOP" …

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

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

  • Error Line 488, Column 10012: required attribute "ALT" not specified
    …itle="Venta de inmuebles en Asturias" /><area shape="poly" class="mapaHomeOP" …

    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 488, Column 10197: reference to entity "filtroTipoObraNueva" for which no system identifier could be generated
    …asp?idProvincia=35&filtroTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"…

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

  • Info Line 488, Column 202: entity was defined here
    …ia.es/resultadosMapa.asp?idProvincia=3&filtroTipoObraNueva=N&filtroTipoSegunda…
  • Error Line 488, Column 10221: reference to entity "filtroTipoSegundaMano" for which no system identifier could be generated
    …oTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="lasPalmas"  title="…

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

  • Info Line 488, Column 224: entity was defined here
    …sp?idProvincia=3&filtroTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  …
  • Error Line 488, Column 10228: reference to entity "mapa" for which no system identifier could be generated
    …raNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="lasPalmas"  title="Venta d…

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

  • Info Line 488, Column 248: entity was defined here
    …ipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  id="alicante"  title="Ve…
  • Error Line 488, Column 10234: reference to entity "web" for which no system identifier could be generated
    …a=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="lasPalmas"  title="Venta de inmu…

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

  • Info Line 488, Column 255: entity was defined here
    …Nueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  id="alicante"  title="Venta de …
  • Warning Line 488, Column 10297: NET-enabling start-tag requires SHORTTAG YES
    …="Venta de inmuebles en Palmas (Las)" /><area shape="poly" class="mapaHomeOP" …

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

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

  • Error Line 488, Column 10297: required attribute "ALT" not specified
    …="Venta de inmuebles en Palmas (Las)" /><area shape="poly" class="mapaHomeOP" …

    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 488, Column 10503: reference to entity "filtroTipoObraNueva" for which no system identifier could be generated
    …asp?idProvincia=36&filtroTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"…

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

  • Info Line 488, Column 202: entity was defined here
    …ia.es/resultadosMapa.asp?idProvincia=3&filtroTipoObraNueva=N&filtroTipoSegunda…
  • Error Line 488, Column 10527: reference to entity "filtroTipoSegundaMano" for which no system identifier could be generated
    …oTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="pontevedra"  title=…

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

  • Info Line 488, Column 224: entity was defined here
    …sp?idProvincia=3&filtroTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  …
  • Error Line 488, Column 10534: reference to entity "mapa" for which no system identifier could be generated
    …raNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="pontevedra"  title="Venta …

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

  • Info Line 488, Column 248: entity was defined here
    …ipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  id="alicante"  title="Ve…
  • Error Line 488, Column 10540: reference to entity "web" for which no system identifier could be generated
    …a=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="pontevedra"  title="Venta de inm…

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

  • Info Line 488, Column 255: entity was defined here
    …Nueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  id="alicante"  title="Venta de …
  • Warning Line 488, Column 10602: NET-enabling start-tag requires SHORTTAG YES
    …le="Venta de inmuebles en Pontevedra" /><area shape="poly" class="mapaHomeOP" …

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

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

  • Error Line 488, Column 10602: required attribute "ALT" not specified
    …le="Venta de inmuebles en Pontevedra" /><area shape="poly" class="mapaHomeOP" …

    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 488, Column 10815: reference to entity "filtroTipoObraNueva" for which no system identifier could be generated
    …asp?idProvincia=37&filtroTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"…

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

  • Info Line 488, Column 202: entity was defined here
    …ia.es/resultadosMapa.asp?idProvincia=3&filtroTipoObraNueva=N&filtroTipoSegunda…
  • Error Line 488, Column 10839: reference to entity "filtroTipoSegundaMano" for which no system identifier could be generated
    …oTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="salamanca"  title="…

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

  • Info Line 488, Column 224: entity was defined here
    …sp?idProvincia=3&filtroTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  …
  • Error Line 488, Column 10846: reference to entity "mapa" for which no system identifier could be generated
    …raNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="salamanca"  title="Venta d…

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

  • Info Line 488, Column 248: entity was defined here
    …ipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  id="alicante"  title="Ve…
  • Error Line 488, Column 10852: reference to entity "web" for which no system identifier could be generated
    …a=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="salamanca"  title="Venta de inmu…

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

  • Info Line 488, Column 255: entity was defined here
    …Nueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  id="alicante"  title="Venta de …
  • Warning Line 488, Column 10912: NET-enabling start-tag requires SHORTTAG YES
    …tle="Venta de inmuebles en Salamanca" /><area shape="poly" class="mapaHomeOP" …

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

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

  • Error Line 488, Column 10912: required attribute "ALT" not specified
    …tle="Venta de inmuebles en Salamanca" /><area shape="poly" class="mapaHomeOP" …

    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 488, Column 11105: reference to entity "filtroTipoObraNueva" for which no system identifier could be generated
    …asp?idProvincia=38&filtroTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"…

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

  • Info Line 488, Column 202: entity was defined here
    …ia.es/resultadosMapa.asp?idProvincia=3&filtroTipoObraNueva=N&filtroTipoSegunda…
  • Error Line 488, Column 11129: reference to entity "filtroTipoSegundaMano" for which no system identifier could be generated
    …oTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="tenerife"  title="V…

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

  • Info Line 488, Column 224: entity was defined here
    …sp?idProvincia=3&filtroTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  …
  • Error Line 488, Column 11136: reference to entity "mapa" for which no system identifier could be generated
    …raNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="tenerife"  title="Venta de…

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

  • Info Line 488, Column 248: entity was defined here
    …ipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  id="alicante"  title="Ve…
  • Error Line 488, Column 11142: reference to entity "web" for which no system identifier could be generated
    …a=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="tenerife"  title="Venta de inmue…

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

  • Info Line 488, Column 255: entity was defined here
    …Nueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  id="alicante"  title="Venta de …
  • Warning Line 488, Column 11214: NET-enabling start-tag requires SHORTTAG YES
    … inmuebles en Santa Cruz de Tenerife" /><area shape="poly" class="mapaHomeOP" …

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

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

  • Error Line 488, Column 11214: required attribute "ALT" not specified
    … inmuebles en Santa Cruz de Tenerife" /><area shape="poly" class="mapaHomeOP" …

    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 488, Column 11452: reference to entity "filtroTipoObraNueva" for which no system identifier could be generated
    …asp?idProvincia=39&filtroTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"…

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

  • Info Line 488, Column 202: entity was defined here
    …ia.es/resultadosMapa.asp?idProvincia=3&filtroTipoObraNueva=N&filtroTipoSegunda…
  • Error Line 488, Column 11476: reference to entity "filtroTipoSegundaMano" for which no system identifier could be generated
    …oTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="cantabria"  title="…

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

  • Info Line 488, Column 224: entity was defined here
    …sp?idProvincia=3&filtroTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  …
  • Error Line 488, Column 11483: reference to entity "mapa" for which no system identifier could be generated
    …raNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="cantabria"  title="Venta d…

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

  • Info Line 488, Column 248: entity was defined here
    …ipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  id="alicante"  title="Ve…
  • Error Line 488, Column 11489: reference to entity "web" for which no system identifier could be generated
    …a=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="cantabria"  title="Venta de inmu…

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

  • Info Line 488, Column 255: entity was defined here
    …Nueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  id="alicante"  title="Venta de …
  • Warning Line 488, Column 11549: NET-enabling start-tag requires SHORTTAG YES
    …tle="Venta de inmuebles en Cantabria" /><area shape="poly" class="mapaHomeOP" …

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

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

  • Error Line 488, Column 11549: required attribute "ALT" not specified
    …tle="Venta de inmuebles en Cantabria" /><area shape="poly" class="mapaHomeOP" …

    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 488, Column 11738: reference to entity "filtroTipoObraNueva" for which no system identifier could be generated
    …asp?idProvincia=40&filtroTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"…

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

  • Info Line 488, Column 202: entity was defined here
    …ia.es/resultadosMapa.asp?idProvincia=3&filtroTipoObraNueva=N&filtroTipoSegunda…
  • Error Line 488, Column 11762: reference to entity "filtroTipoSegundaMano" for which no system identifier could be generated
    …oTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="segovia"  title="Ve…

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

  • Info Line 488, Column 224: entity was defined here
    …sp?idProvincia=3&filtroTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  …
  • Error Line 488, Column 11769: reference to entity "mapa" for which no system identifier could be generated
    …raNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="segovia"  title="Venta de …

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

  • Info Line 488, Column 248: entity was defined here
    …ipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  id="alicante"  title="Ve…
  • Error Line 488, Column 11775: reference to entity "web" for which no system identifier could be generated
    …a=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="segovia"  title="Venta de inmueb…

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

  • Info Line 488, Column 255: entity was defined here
    …Nueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  id="alicante"  title="Venta de …
  • Warning Line 488, Column 11831: NET-enabling start-tag requires SHORTTAG YES
    …title="Venta de inmuebles en Segovia" /><area shape="poly" class="mapaHomeOP" …

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

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

  • Error Line 488, Column 11831: required attribute "ALT" not specified
    …title="Venta de inmuebles en Segovia" /><area shape="poly" class="mapaHomeOP" …

    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 488, Column 12051: reference to entity "filtroTipoObraNueva" for which no system identifier could be generated
    …asp?idProvincia=41&filtroTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"…

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

  • Info Line 488, Column 202: entity was defined here
    …ia.es/resultadosMapa.asp?idProvincia=3&filtroTipoObraNueva=N&filtroTipoSegunda…
  • Error Line 488, Column 12075: reference to entity "filtroTipoSegundaMano" for which no system identifier could be generated
    …oTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="sevilla"  title="Ve…

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

  • Info Line 488, Column 224: entity was defined here
    …sp?idProvincia=3&filtroTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  …
  • Error Line 488, Column 12082: reference to entity "mapa" for which no system identifier could be generated
    …raNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="sevilla"  title="Venta de …

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

  • Info Line 488, Column 248: entity was defined here
    …ipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  id="alicante"  title="Ve…
  • Error Line 488, Column 12088: reference to entity "web" for which no system identifier could be generated
    …a=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="sevilla"  title="Venta de inmueb…

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

  • Info Line 488, Column 255: entity was defined here
    …Nueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  id="alicante"  title="Venta de …
  • Warning Line 488, Column 12144: NET-enabling start-tag requires SHORTTAG YES
    …title="Venta de inmuebles en Sevilla" /><area shape="poly" class="mapaHomeOP" …

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

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

  • Error Line 488, Column 12144: required attribute "ALT" not specified
    …title="Venta de inmuebles en Sevilla" /><area shape="poly" class="mapaHomeOP" …

    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 488, Column 12358: reference to entity "filtroTipoObraNueva" for which no system identifier could be generated
    …asp?idProvincia=42&filtroTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"…

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

  • Info Line 488, Column 202: entity was defined here
    …ia.es/resultadosMapa.asp?idProvincia=3&filtroTipoObraNueva=N&filtroTipoSegunda…
  • Error Line 488, Column 12382: reference to entity "filtroTipoSegundaMano" for which no system identifier could be generated
    …oTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="soria"  title="Vent…

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

  • Info Line 488, Column 224: entity was defined here
    …sp?idProvincia=3&filtroTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  …
  • Error Line 488, Column 12389: reference to entity "mapa" for which no system identifier could be generated
    …raNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="soria"  title="Venta de in…

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

  • Info Line 488, Column 248: entity was defined here
    …ipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  id="alicante"  title="Ve…
  • Error Line 488, Column 12395: reference to entity "web" for which no system identifier could be generated
    …a=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="soria"  title="Venta de inmueble…

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

  • Info Line 488, Column 255: entity was defined here
    …Nueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  id="alicante"  title="Venta de …
  • Warning Line 488, Column 12447: NET-enabling start-tag requires SHORTTAG YES
    …  title="Venta de inmuebles en Soria" /><area shape="poly" class="mapaHomeOP" …

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

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

  • Error Line 488, Column 12447: required attribute "ALT" not specified
    …  title="Venta de inmuebles en Soria" /><area shape="poly" class="mapaHomeOP" …

    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 488, Column 12660: reference to entity "filtroTipoObraNueva" for which no system identifier could be generated
    …asp?idProvincia=43&filtroTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"…

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

  • Info Line 488, Column 202: entity was defined here
    …ia.es/resultadosMapa.asp?idProvincia=3&filtroTipoObraNueva=N&filtroTipoSegunda…
  • Error Line 488, Column 12684: reference to entity "filtroTipoSegundaMano" for which no system identifier could be generated
    …oTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="tarragona"  title="…

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

  • Info Line 488, Column 224: entity was defined here
    …sp?idProvincia=3&filtroTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  …
  • Error Line 488, Column 12691: reference to entity "mapa" for which no system identifier could be generated
    …raNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="tarragona"  title="Venta d…

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

  • Info Line 488, Column 248: entity was defined here
    …ipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  id="alicante"  title="Ve…
  • Error Line 488, Column 12697: reference to entity "web" for which no system identifier could be generated
    …a=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="tarragona"  title="Venta de inmu…

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

  • Info Line 488, Column 255: entity was defined here
    …Nueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  id="alicante"  title="Venta de …
  • Warning Line 488, Column 12757: NET-enabling start-tag requires SHORTTAG YES
    …tle="Venta de inmuebles en Tarragona" /><area shape="poly" class="mapaHomeOP" …

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

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

  • Error Line 488, Column 12757: required attribute "ALT" not specified
    …tle="Venta de inmuebles en Tarragona" /><area shape="poly" class="mapaHomeOP" …

    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 488, Column 13019: reference to entity "filtroTipoObraNueva" for which no system identifier could be generated
    …asp?idProvincia=44&filtroTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"…

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

  • Info Line 488, Column 202: entity was defined here
    …ia.es/resultadosMapa.asp?idProvincia=3&filtroTipoObraNueva=N&filtroTipoSegunda…
  • Error Line 488, Column 13043: reference to entity "filtroTipoSegundaMano" for which no system identifier could be generated
    …oTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="teruel"  title="Ven…

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

  • Info Line 488, Column 224: entity was defined here
    …sp?idProvincia=3&filtroTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  …
  • Error Line 488, Column 13050: reference to entity "mapa" for which no system identifier could be generated
    …raNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="teruel"  title="Venta de i…

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

  • Info Line 488, Column 248: entity was defined here
    …ipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  id="alicante"  title="Ve…
  • Error Line 488, Column 13056: reference to entity "web" for which no system identifier could be generated
    …a=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="teruel"  title="Venta de inmuebl…

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

  • Info Line 488, Column 255: entity was defined here
    …Nueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  id="alicante"  title="Venta de …
  • Warning Line 488, Column 13110: NET-enabling start-tag requires SHORTTAG YES
    … title="Venta de inmuebles en Teruel" /><area shape="poly" class="mapaHomeOP" …

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

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

  • Error Line 488, Column 13110: required attribute "ALT" not specified
    … title="Venta de inmuebles en Teruel" /><area shape="poly" class="mapaHomeOP" …

    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 488, Column 13341: reference to entity "filtroTipoObraNueva" for which no system identifier could be generated
    …asp?idProvincia=45&filtroTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"…

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

  • Info Line 488, Column 202: entity was defined here
    …ia.es/resultadosMapa.asp?idProvincia=3&filtroTipoObraNueva=N&filtroTipoSegunda…
  • Error Line 488, Column 13365: reference to entity "filtroTipoSegundaMano" for which no system identifier could be generated
    …oTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="toledo"  title="Ven…

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

  • Info Line 488, Column 224: entity was defined here
    …sp?idProvincia=3&filtroTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  …
  • Error Line 488, Column 13372: reference to entity "mapa" for which no system identifier could be generated
    …raNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="toledo"  title="Venta de i…

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

  • Info Line 488, Column 248: entity was defined here
    …ipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  id="alicante"  title="Ve…
  • Error Line 488, Column 13378: reference to entity "web" for which no system identifier could be generated
    …a=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="toledo"  title="Venta de inmuebl…

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

  • Info Line 488, Column 255: entity was defined here
    …Nueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  id="alicante"  title="Venta de …
  • Warning Line 488, Column 13432: NET-enabling start-tag requires SHORTTAG YES
    … title="Venta de inmuebles en Toledo" /><area shape="poly" class="mapaHomeOP" …

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

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

  • Error Line 488, Column 13432: required attribute "ALT" not specified
    … title="Venta de inmuebles en Toledo" /><area shape="poly" class="mapaHomeOP" …

    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 488, Column 13662: reference to entity "filtroTipoObraNueva" for which no system identifier could be generated
    …asp?idProvincia=46&filtroTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"…

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

  • Info Line 488, Column 202: entity was defined here
    …ia.es/resultadosMapa.asp?idProvincia=3&filtroTipoObraNueva=N&filtroTipoSegunda…
  • Error Line 488, Column 13686: reference to entity "filtroTipoSegundaMano" for which no system identifier could be generated
    …oTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="valencia"  title="V…

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

  • Info Line 488, Column 224: entity was defined here
    …sp?idProvincia=3&filtroTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  …
  • Error Line 488, Column 13693: reference to entity "mapa" for which no system identifier could be generated
    …raNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="valencia"  title="Venta de…

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

  • Info Line 488, Column 248: entity was defined here
    …ipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  id="alicante"  title="Ve…
  • Error Line 488, Column 13699: reference to entity "web" for which no system identifier could be generated
    …a=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="valencia"  title="Venta de inmue…

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

  • Info Line 488, Column 255: entity was defined here
    …Nueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  id="alicante"  title="Venta de …
  • Warning Line 488, Column 13757: NET-enabling start-tag requires SHORTTAG YES
    …itle="Venta de inmuebles en Valencia" /><area shape="poly" class="mapaHomeOP" …

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

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

  • Error Line 488, Column 13757: required attribute "ALT" not specified
    …itle="Venta de inmuebles en Valencia" /><area shape="poly" class="mapaHomeOP" …

    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 488, Column 13982: reference to entity "filtroTipoObraNueva" for which no system identifier could be generated
    …asp?idProvincia=47&filtroTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"…

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

  • Info Line 488, Column 202: entity was defined here
    …ia.es/resultadosMapa.asp?idProvincia=3&filtroTipoObraNueva=N&filtroTipoSegunda…
  • Error Line 488, Column 14006: reference to entity "filtroTipoSegundaMano" for which no system identifier could be generated
    …oTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="valladolid"  title=…

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

  • Info Line 488, Column 224: entity was defined here
    …sp?idProvincia=3&filtroTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  …
  • Error Line 488, Column 14013: reference to entity "mapa" for which no system identifier could be generated
    …raNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="valladolid"  title="Venta …

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

  • Info Line 488, Column 248: entity was defined here
    …ipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  id="alicante"  title="Ve…
  • Error Line 488, Column 14019: reference to entity "web" for which no system identifier could be generated
    …a=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="valladolid"  title="Venta de inm…

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

  • Info Line 488, Column 255: entity was defined here
    …Nueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  id="alicante"  title="Venta de …
  • Warning Line 488, Column 14081: NET-enabling start-tag requires SHORTTAG YES
    …le="Venta de inmuebles en Valladolid" /><area shape="poly" class="mapaHomeOP" …

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

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

  • Error Line 488, Column 14081: required attribute "ALT" not specified
    …le="Venta de inmuebles en Valladolid" /><area shape="poly" class="mapaHomeOP" …

    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 488, Column 14280: reference to entity "filtroTipoObraNueva" for which no system identifier could be generated
    …asp?idProvincia=48&filtroTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"…

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

  • Info Line 488, Column 202: entity was defined here
    …ia.es/resultadosMapa.asp?idProvincia=3&filtroTipoObraNueva=N&filtroTipoSegunda…
  • Error Line 488, Column 14304: reference to entity "filtroTipoSegundaMano" for which no system identifier could be generated
    …oTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="vizcaya"  title="Ve…

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

  • Info Line 488, Column 224: entity was defined here
    …sp?idProvincia=3&filtroTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  …
  • Error Line 488, Column 14311: reference to entity "mapa" for which no system identifier could be generated
    …raNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="vizcaya"  title="Venta de …

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

  • Info Line 488, Column 248: entity was defined here
    …ipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  id="alicante"  title="Ve…
  • Error Line 488, Column 14317: reference to entity "web" for which no system identifier could be generated
    …a=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="vizcaya"  title="Venta de inmueb…

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

  • Info Line 488, Column 255: entity was defined here
    …Nueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  id="alicante"  title="Venta de …
  • Warning Line 488, Column 14373: NET-enabling start-tag requires SHORTTAG YES
    …title="Venta de inmuebles en Vizcaya" /><area shape="poly" class="mapaHomeOP" …

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

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

  • Error Line 488, Column 14373: required attribute "ALT" not specified
    …title="Venta de inmuebles en Vizcaya" /><area shape="poly" class="mapaHomeOP" …

    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 488, Column 14598: reference to entity "filtroTipoObraNueva" for which no system identifier could be generated
    …asp?idProvincia=49&filtroTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"…

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

  • Info Line 488, Column 202: entity was defined here
    …ia.es/resultadosMapa.asp?idProvincia=3&filtroTipoObraNueva=N&filtroTipoSegunda…
  • Error Line 488, Column 14622: reference to entity "filtroTipoSegundaMano" for which no system identifier could be generated
    …oTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="zamora"  title="Ven…

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

  • Info Line 488, Column 224: entity was defined here
    …sp?idProvincia=3&filtroTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  …
  • Error Line 488, Column 14629: reference to entity "mapa" for which no system identifier could be generated
    …raNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="zamora"  title="Venta de i…

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

  • Info Line 488, Column 248: entity was defined here
    …ipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  id="alicante"  title="Ve…
  • Error Line 488, Column 14635: reference to entity "web" for which no system identifier could be generated
    …a=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="zamora"  title="Venta de inmuebl…

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

  • Info Line 488, Column 255: entity was defined here
    …Nueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  id="alicante"  title="Venta de …
  • Warning Line 488, Column 14689: NET-enabling start-tag requires SHORTTAG YES
    … title="Venta de inmuebles en Zamora" /><area shape="poly" class="mapaHomeOP" …

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

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

  • Error Line 488, Column 14689: required attribute "ALT" not specified
    … title="Venta de inmuebles en Zamora" /><area shape="poly" class="mapaHomeOP" …

    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 488, Column 14979: reference to entity "filtroTipoObraNueva" for which no system identifier could be generated
    …asp?idProvincia=50&filtroTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"…

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

  • Info Line 488, Column 202: entity was defined here
    …ia.es/resultadosMapa.asp?idProvincia=3&filtroTipoObraNueva=N&filtroTipoSegunda…
  • Error Line 488, Column 15003: reference to entity "filtroTipoSegundaMano" for which no system identifier could be generated
    …oTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="zaragoza"  title="V…

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

  • Info Line 488, Column 224: entity was defined here
    …sp?idProvincia=3&filtroTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  …
  • Error Line 488, Column 15010: reference to entity "mapa" for which no system identifier could be generated
    …raNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="zaragoza"  title="Venta de…

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

  • Info Line 488, Column 248: entity was defined here
    …ipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  id="alicante"  title="Ve…
  • Error Line 488, Column 15016: reference to entity "web" for which no system identifier could be generated
    …a=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="zaragoza"  title="Venta de inmue…

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

  • Info Line 488, Column 255: entity was defined here
    …Nueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  id="alicante"  title="Venta de …
  • Warning Line 488, Column 15074: NET-enabling start-tag requires SHORTTAG YES
    …itle="Venta de inmuebles en Zaragoza" /><area shape="poly" class="mapaHomeOP" …

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

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

  • Error Line 488, Column 15074: required attribute "ALT" not specified
    …itle="Venta de inmuebles en Zaragoza" /><area shape="poly" class="mapaHomeOP" …

    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 488, Column 15293: reference to entity "filtroTipoObraNueva" for which no system identifier could be generated
    …sp?idProvincia=202&filtroTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"…

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

  • Info Line 488, Column 202: entity was defined here
    …ia.es/resultadosMapa.asp?idProvincia=3&filtroTipoObraNueva=N&filtroTipoSegunda…
  • Error Line 488, Column 15317: reference to entity "filtroTipoSegundaMano" for which no system identifier could be generated
    …oTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="alava"  title="Vent…

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

  • Info Line 488, Column 224: entity was defined here
    …sp?idProvincia=3&filtroTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  …
  • Error Line 488, Column 15324: reference to entity "mapa" for which no system identifier could be generated
    …raNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="alava"  title="Venta de in…

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

  • Info Line 488, Column 248: entity was defined here
    …ipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  id="alicante"  title="Ve…
  • Error Line 488, Column 15330: reference to entity "web" for which no system identifier could be generated
    …a=N&filtroTipoSegundaMano=N&mapa=S&web=O" id="alava"  title="Venta de inmueble…

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

  • Info Line 488, Column 255: entity was defined here
    …Nueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  id="alicante"  title="Venta de …
  • Warning Line 488, Column 15382: NET-enabling start-tag requires SHORTTAG YES
    …oSegundaMano=N&mapa=S&web=O" id="alava"  title="Venta de inmuebles en Álava" />

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

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

  • Error Line 488, Column 15382: required attribute "ALT" not specified
    …oSegundaMano=N&mapa=S&web=O" id="alava"  title="Venta de inmuebles en Álava" />

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

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

  • Warning Line 489, Column 46: NET-enabling start-tag requires SHORTTAG YES
    <area shape="default" nohref="nohref" alt="" /> 

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

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

  • Error Line 496, Column 135: required attribute "ALT" not specified
    …ascript: enviaFormHome()" src="http://www.solvia.es/css/OP/img/btnBuscar.png">	

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

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

  • Error Line 501, Column 52: required attribute "ALT" not specified
    	<img src="http://www.solvia.es/img/titSelIsla.jpg">

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

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

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

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

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

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

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

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

  • Error Line 528, Column 200: required attribute "ALT" not specified
    … tú, ¿cuánto pagarías?"  src="http://www.solvia.es/uploaded/img634330.gif"></a>

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

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

  • Warning Line 533, Column 85: NET-enabling start-tag requires SHORTTAG YES
    …put id="direccionBanner"  type="hidden" name="direccionBanner" value="Abajo" />

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

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

  • Warning Line 534, Column 69: NET-enabling start-tag requires SHORTTAG YES
    				<input id="clickActual" type="hidden" name="clickActual" value=1/>

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

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

  • Warning Line 535, Column 62: NET-enabling start-tag requires SHORTTAG YES
    				<input id="inicio" type="hidden" name="inicio" value="S" />

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

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

  • Error Line 537, Column 123: required attribute "ALT" not specified
    …" id="btn_prev_img_HOME" src="http://www.solvia.es/ca/img/btnMas.jpg"></center>

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

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

  • Warning Line 544, Column 123: NET-enabling start-tag requires SHORTTAG YES
    …N" border=0 src="http://www.solvia.es/uploaded/prescriptores/img611780.jpg"  />

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

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

  • Error Line 544, Column 123: required attribute "ALT" not specified
    …N" border=0 src="http://www.solvia.es/uploaded/prescriptores/img611780.jpg"  />

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

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

  • Warning Line 548, Column 123: NET-enabling start-tag requires SHORTTAG YES
    …N" border=0 src="http://www.solvia.es/uploaded/prescriptores/img625101.jpg"  />

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

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

  • Error Line 548, Column 123: required attribute "ALT" not specified
    …N" border=0 src="http://www.solvia.es/uploaded/prescriptores/img625101.jpg"  />

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

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

  • Warning Line 552, Column 123: NET-enabling start-tag requires SHORTTAG YES
    …N" border=0 src="http://www.solvia.es/uploaded/prescriptores/img625107.jpg"  />

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

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

  • Error Line 552, Column 123: required attribute "ALT" not specified
    …N" border=0 src="http://www.solvia.es/uploaded/prescriptores/img625107.jpg"  />

    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 555, Column 135: non SGML character number 128
    …3705_3/vivienda_28880.html" title="Edificio Galileo desde 135.000€" target="" >

    You have used an illegal character in your text. HTML uses the standard UNICODE Consortium character repertoire, and it leaves undefined (among others) 65 character codes (0 to 31 inclusive and 127 to 159 inclusive) that are sometimes used for typographical quote marks and similar in proprietary character sets. The validator has found one of these undefined characters in your document. The character may appear on your browser as a curly quote, or a trademark symbol, or some other fancy glyph; on a different computer, however, it will likely appear as a completely different character, or nothing at all.

    Your best bet is to replace the character with the nearest equivalent ASCII character, or to use an appropriate character entity. For more information on Character Encoding on the web, see Alan Flavell's excellent HTML Character Set Issues reference.

    This error can also be triggered by formatting characters embedded in documents by some word processors. If you use a word processor to edit your HTML documents, be sure to use the "Save as ASCII" or similar command to save the document without formatting information.

  • Warning Line 556, Column 123: NET-enabling start-tag requires SHORTTAG YES
    …N" border=0 src="http://www.solvia.es/uploaded/prescriptores/img625981.jpg"  />

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

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

  • Error Line 556, Column 123: required attribute "ALT" not specified
    …N" border=0 src="http://www.solvia.es/uploaded/prescriptores/img625981.jpg"  />

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

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

  • Warning Line 560, Column 123: NET-enabling start-tag requires SHORTTAG YES
    …N" border=0 src="http://www.solvia.es/uploaded/prescriptores/img629518.jpg"  />

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

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

  • Error Line 560, Column 123: required attribute "ALT" not specified
    …N" border=0 src="http://www.solvia.es/uploaded/prescriptores/img629518.jpg"  />

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

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

  • Warning Line 564, Column 123: NET-enabling start-tag requires SHORTTAG YES
    …N" border=0 src="http://www.solvia.es/uploaded/prescriptores/img633886.jpg"  />

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

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

  • Error Line 564, Column 123: required attribute "ALT" not specified
    …N" border=0 src="http://www.solvia.es/uploaded/prescriptores/img633886.jpg"  />

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

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

  • Warning Line 568, Column 123: NET-enabling start-tag requires SHORTTAG YES
    …N" border=0 src="http://www.solvia.es/uploaded/prescriptores/img543499.jpg"  />

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

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

  • Error Line 568, Column 123: required attribute "ALT" not specified
    …N" border=0 src="http://www.solvia.es/uploaded/prescriptores/img543499.jpg"  />

    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 575, Column 122: required attribute "ALT" not specified
    …e" id="btn_next_img_HOME" src="http://www.solvia.es/img/btnMenos.jpg"></center>

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

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

  • Error Line 577, Column 174: required attribute "ALT" not specified
    …:10px; margin-top:0px " src="http://www.solvia.es/img/btnMasNovedades.jpg"></a>

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

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

  • Error Line 919, Column 65: required attribute "ALT" not specified
    		<img class="etABS" src="http://www.solvia.es/img/desbGris.png">

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

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

  • Error Line 921, Column 121: required attribute "ALT" not specified
    …"http://www.solvia.es/img/siguenosHome.jpg" border="0" usemap="#MapSocialRoom">

    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 923, Column 87: required attribute "ALT" not specified
    … shape="rect" coords="180,3,306,29" href="http://www.solvia.es/socialRoom.asp">

    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 928, Column 205: required attribute "ALT" not specified
    …adell"><img class="social" src="http://www.solvia.es/img/Home_Bann_01.jpg"></a>

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

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

  • Error Line 931, Column 165: required attribute "ALT" not specified
    …ss="imgBTN" border="0" src="http://www.solvia.es/img/Home_Bann_02.jpg"></a>				

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

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

  • Error Line 934, Column 70: there is no attribute "COUNT"
    … margin-left:170px" ><g:plusone count="false" href="http://www.solvia.es/"></g…

    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 934, Column 83: there is no attribute "HREF"
    …170px" ><g:plusone count="false" href="http://www.solvia.es/"></g:plusone></di…

    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 934, Column 106: element "G:PLUSONE" undefined
    …70px" ><g:plusone count="false" href="http://www.solvia.es/"></g:plusone></div>

    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 936, Column 177: required attribute "ALT" not specified
    …ass="social imgBTN" src="http://www.solvia.es/img/banner_home_youtube.jpg"></a>

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

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

  • Error Line 940, Column 67: required attribute "ALT" not specified
    				<img class="etABS" src="http://www.solvia.es/img/desbGris.png">

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

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

  • Error Line 941, Column 87: required attribute "ALT" not specified
    …itle="¿Necesitas Ayuda? - Solvia" src="http://www.solvia.es/img/ayudaHome.jpg">

    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 946, Column 89: required attribute "ALT" not specified
    …olvia" src="http://www.solvia.es/img/ayuda_1Home.jpg"></td><td width="10"></td>

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

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

  • Error Line 954, Column 77: required attribute "ALT" not specified
    						<img border="0" src="http://www.solvia.es/css/OP/img/flechaEnlace.png">

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

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

  • Error Line 958, Column 109: required attribute "ALT" not specified
    …p://www.solvia.es/img/ayuda_2Home.jpg"></td><td width="10"></td><td><p class="…

    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 960, Column 77: required attribute "ALT" not specified
    						<img border="0" src="http://www.solvia.es/css/OP/img/flechaEnlace.png">

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

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

  • Error Line 964, Column 122: required attribute "ALT" not specified
    …p://www.solvia.es/img/ayuda_3Home.jpg"></td><td width="10"></td><td><p class="…

    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 966, Column 77: required attribute "ALT" not specified
    						<img border="0" src="http://www.solvia.es/css/OP/img/flechaEnlace.png">

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

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

  • Error Line 971, Column 126: required attribute "ALT" not specified
    …p://www.solvia.es/img/ayuda_4Home.jpg"></td><td width="10"></td><td><p class="…

    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 973, Column 77: required attribute "ALT" not specified
    						<img border="0" src="http://www.solvia.es/css/OP/img/flechaEnlace.png">

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

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

  • Error Line 981, Column 137: required attribute "ALT" not specified
    …:21px; margin-top:35px;" src="http://www.solvia.es/img/icoAccesosDirectos.jpg">

    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 983, Column 61: required attribute "ALT" not specified
    		<img src="http://www.solvia.es/img/topAccesosDirectos.jpg">

    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 1002, Column 149: reference to entity "filtroTipoSegundaMano" for which no system identifier could be generated
    …oTipoObraNueva=S&filtroTipoSegundaMano=N&mapa=N&web=O">Viviendas de obra nueva…

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

  • Info Line 488, Column 224: entity was defined here
    …sp?idProvincia=3&filtroTipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  …
  • Error Line 1002, Column 156: reference to entity "mapa" for which no system identifier could be generated
    …poObraNueva=S&filtroTipoSegundaMano=N&mapa=N&web=O">Viviendas de obra nueva</a>

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

  • Info Line 488, Column 248: entity was defined here
    …ipoObraNueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  id="alicante"  title="Ve…
  • Error Line 1002, Column 162: reference to entity "web" for which no system identifier could be generated
    …poObraNueva=S&filtroTipoSegundaMano=N&mapa=N&web=O">Viviendas de obra nueva</a>

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

  • Info Line 488, Column 255: entity was defined here
    …Nueva=N&filtroTipoSegundaMano=N&mapa=S&web=O"  id="alicante"  title="Venta de …
  • Error Line 1038, Column 28: there is no attribute "ALT"
    			<td width='420'><a  alt='Pisos en Albacete'  title='Pisos en Albacete'  styl…

    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 1242, Column 50: required attribute "TYPE" not specified
    <script src="http://www.wtp101.com/pixel?id=2394"></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 1250, Column 50: required attribute "ALT" not specified
    	<img src="http://www.solvia.es/img/popup_25.jpg">

    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 1252, Column 30: required attribute "TYPE" not specified
    <script languaje="javascript">

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

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

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

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

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

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

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

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

  • Error Line 1276, Column 84: non SGML character number 149
    … Óscar Esplá nº 37, 03007 Alicante (España) • Teléfono 966 915 050<br /> <br />

    You have used an illegal character in your text. HTML uses the standard UNICODE Consortium character repertoire, and it leaves undefined (among others) 65 character codes (0 to 31 inclusive and 127 to 159 inclusive) that are sometimes used for typographical quote marks and similar in proprietary character sets. The validator has found one of these undefined characters in your document. The character may appear on your browser as a curly quote, or a trademark symbol, or some other fancy glyph; on a different computer, however, it will likely appear as a completely different character, or nothing at all.

    Your best bet is to replace the character with the nearest equivalent ASCII character, or to use an appropriate character entity. For more information on Character Encoding on the web, see Alan Flavell's excellent HTML Character Set Issues reference.

    This error can also be triggered by formatting characters embedded in documents by some word processors. If you use a word processor to edit your HTML documents, be sure to use the "Save as ASCII" or similar command to save the document without formatting information.

  • Warning Line 1276, Column 110: NET-enabling start-tag requires SHORTTAG YES
    … Óscar Esplá nº 37, 03007 Alicante (España) • Teléfono 966 915 050<br /> <br />

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

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

  • Warning Line 1276, Column 117: NET-enabling start-tag requires SHORTTAG YES
    … Óscar Esplá nº 37, 03007 Alicante (España) • Teléfono 966 915 050<br /> <br />

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

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

  • Error Line 1302, Column 205: end tag for element "IFRAME" which is not open
    … a + '?" width="1" height="1" frameborder="0" style="display:none"></iframe>');

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

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

  • Warning Line 1314, Column 62: NET-enabling start-tag requires SHORTTAG YES
             		<img src="http://www.solvia.es/img/icono-RSS.gif" />

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

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

  • Error Line 1314, Column 62: required attribute "ALT" not specified
             		<img src="http://www.solvia.es/img/icono-RSS.gif" />

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

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

  • Error Line 1326, Column 84: there is no attribute "VALIGN"
    …00px" cellspacing="0" border=0 valign="top" style="text-align:left; margin-lef…

    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 1345, Column 181: required attribute "ALT" not specified
    …blank"><img border="0" src="http://www.solvia.es/img/miniICO_RSS.jpg">Álava</a>

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

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

  • Error Line 1355, Column 184: required attribute "ALT" not specified
    …nk"><img border="0" src="http://www.solvia.es/img/miniICO_RSS.jpg">Albacete</a>

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

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

  • Error Line 1365, Column 184: required attribute "ALT" not specified
    …nk"><img border="0" src="http://www.solvia.es/img/miniICO_RSS.jpg">Alicante</a>

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

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

  • Error Line 1375, Column 183: required attribute "ALT" not specified
    …ank"><img border="0" src="http://www.solvia.es/img/miniICO_RSS.jpg">Almería</a>

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

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

  • Error Line 1388, Column 184: required attribute "ALT" not specified
    …nk"><img border="0" src="http://www.solvia.es/img/miniICO_RSS.jpg">Asturias</a>

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

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

  • Error Line 1398, Column 181: required attribute "ALT" not specified
    …blank"><img border="0" src="http://www.solvia.es/img/miniICO_RSS.jpg">Avila</a>

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

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

  • Error Line 1408, Column 183: required attribute "ALT" not specified
    …ank"><img border="0" src="http://www.solvia.es/img/miniICO_RSS.jpg">Badajoz</a>

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

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

  • Error Line 1418, Column 189: required attribute "ALT" not specified
    …g border="0" src="http://www.solvia.es/img/miniICO_RSS.jpg">Balears (Illes)</a>

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

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

  • Error Line 1431, Column 185: required attribute "ALT" not specified
    …k"><img border="0" src="http://www.solvia.es/img/miniICO_RSS.jpg">Barcelona</a>

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

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

  • Error Line 1441, Column 182: required attribute "ALT" not specified
    …lank"><img border="0" src="http://www.solvia.es/img/miniICO_RSS.jpg">Burgos</a>

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

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

  • Error Line 1451, Column 183: required attribute "ALT" not specified
    …ank"><img border="0" src="http://www.solvia.es/img/miniICO_RSS.jpg">Cáceres</a>

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

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

  • Error Line 1461, Column 181: required attribute "ALT" not specified
    …blank"><img border="0" src="http://www.solvia.es/img/miniICO_RSS.jpg">Cádiz</a>

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

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

  • Error Line 1474, Column 185: required attribute "ALT" not specified
    …k"><img border="0" src="http://www.solvia.es/img/miniICO_RSS.jpg">Cantabria</a>

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

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

  • Error Line 1484, Column 194: required attribute "ALT" not specified
    …order="0" src="http://www.solvia.es/img/miniICO_RSS.jpg">Castellón/Castelló</a>

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

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

  • Error Line 1494, Column 187: required attribute "ALT" not specified
    …><img border="0" src="http://www.solvia.es/img/miniICO_RSS.jpg">Ciudad Real</a>

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

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

  • Error Line 1504, Column 183: required attribute "ALT" not specified
    …ank"><img border="0" src="http://www.solvia.es/img/miniICO_RSS.jpg">Córdoba</a>

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

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

  • Error Line 1517, Column 185: required attribute "ALT" not specified
    …"><img border="0" src="http://www.solvia.es/img/miniICO_RSS.jpg">Coruña (A)</a>

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

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

  • Error Line 1527, Column 182: required attribute "ALT" not specified
    …lank"><img border="0" src="http://www.solvia.es/img/miniICO_RSS.jpg">Cuenca</a>

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

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

  • Error Line 1537, Column 182: required attribute "ALT" not specified
    …lank"><img border="0" src="http://www.solvia.es/img/miniICO_RSS.jpg">Girona</a>

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

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

  • Error Line 1547, Column 183: required attribute "ALT" not specified
    …ank"><img border="0" src="http://www.solvia.es/img/miniICO_RSS.jpg">Granada</a>

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

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

  • Error Line 1560, Column 187: required attribute "ALT" not specified
    …><img border="0" src="http://www.solvia.es/img/miniICO_RSS.jpg">Guadalajara</a>

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

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

  • Error Line 1570, Column 185: required attribute "ALT" not specified
    …k"><img border="0" src="http://www.solvia.es/img/miniICO_RSS.jpg">Guipúzcoa</a>

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

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

  • Error Line 1580, Column 182: required attribute "ALT" not specified
    …lank"><img border="0" src="http://www.solvia.es/img/miniICO_RSS.jpg">Huelva</a>

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

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

  • Error Line 1590, Column 182: required attribute "ALT" not specified
    …lank"><img border="0" src="http://www.solvia.es/img/miniICO_RSS.jpg">Huesca</a>

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

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

  • Error Line 1603, Column 180: required attribute "ALT" not specified
    …_blank"><img border="0" src="http://www.solvia.es/img/miniICO_RSS.jpg">Jaén</a>

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

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

  • Error Line 1613, Column 180: required attribute "ALT" not specified
    …_blank"><img border="0" src="http://www.solvia.es/img/miniICO_RSS.jpg">León</a>

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

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

  • Error Line 1623, Column 182: required attribute "ALT" not specified
    …lank"><img border="0" src="http://www.solvia.es/img/miniICO_RSS.jpg">Lleida</a>

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

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

  • Error Line 1633, Column 180: required attribute "ALT" not specified
    …_blank"><img border="0" src="http://www.solvia.es/img/miniICO_RSS.jpg">Lugo</a>

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

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

  • Error Line 1646, Column 182: required attribute "ALT" not specified
    …lank"><img border="0" src="http://www.solvia.es/img/miniICO_RSS.jpg">Madrid</a>

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

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

  • Error Line 1656, Column 182: required attribute "ALT" not specified
    …lank"><img border="0" src="http://www.solvia.es/img/miniICO_RSS.jpg">Málaga</a>

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

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

  • Error Line 1666, Column 182: required attribute "ALT" not specified
    …lank"><img border="0" src="http://www.solvia.es/img/miniICO_RSS.jpg">Murcia</a>

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

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

  • Error Line 1676, Column 183: required attribute "ALT" not specified
    …ank"><img border="0" src="http://www.solvia.es/img/miniICO_RSS.jpg">Navarra</a>

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

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

  • Error Line 1689, Column 183: required attribute "ALT" not specified
    …ank"><img border="0" src="http://www.solvia.es/img/miniICO_RSS.jpg">Ourense</a>

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

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

  • Error Line 1699, Column 186: required attribute "ALT" not specified
    …<img border="0" src="http://www.solvia.es/img/miniICO_RSS.jpg">Palmas (Las)</a>

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

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

  • Error Line 1709, Column 186: required attribute "ALT" not specified
    …"><img border="0" src="http://www.solvia.es/img/miniICO_RSS.jpg">Pontevedra</a>

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

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

  • Error Line 1719, Column 184: required attribute "ALT" not specified
    …"><img border="0" src="http://www.solvia.es/img/miniICO_RSS.jpg">Rioja (La)</a>

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

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

  • Error Line 1732, Column 185: required attribute "ALT" not specified
    …k"><img border="0" src="http://www.solvia.es/img/miniICO_RSS.jpg">Salamanca</a>

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

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

  • Error Line 1742, Column 198: required attribute "ALT" not specified
    …r="0" src="http://www.solvia.es/img/miniICO_RSS.jpg">Santa Cruz de Tenerife</a>

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

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

  • Error Line 1752, Column 183: required attribute "ALT" not specified
    …ank"><img border="0" src="http://www.solvia.es/img/miniICO_RSS.jpg">Segovia</a>

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

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

  • Error Line 1762, Column 183: required attribute "ALT" not specified
    …ank"><img border="0" src="http://www.solvia.es/img/miniICO_RSS.jpg">Sevilla</a>

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

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

  • Error Line 1775, Column 181: required attribute "ALT" not specified
    …blank"><img border="0" src="http://www.solvia.es/img/miniICO_RSS.jpg">Soria</a>

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

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

  • Error Line 1785, Column 185: required attribute "ALT" not specified
    …k"><img border="0" src="http://www.solvia.es/img/miniICO_RSS.jpg">Tarragona</a>

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

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

  • Error Line 1795, Column 182: required attribute "ALT" not specified
    …lank"><img border="0" src="http://www.solvia.es/img/miniICO_RSS.jpg">Teruel</a>

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

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

  • Error Line 1805, Column 182: required attribute "ALT" not specified
    …lank"><img border="0" src="http://www.solvia.es/img/miniICO_RSS.jpg">Toledo</a>

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

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

  • Error Line 1818, Column 184: required attribute "ALT" not specified
    …nk"><img border="0" src="http://www.solvia.es/img/miniICO_RSS.jpg">Valencia</a>

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

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

  • Error Line 1828, Column 186: required attribute "ALT" not specified
    …"><img border="0" src="http://www.solvia.es/img/miniICO_RSS.jpg">Valladolid</a>

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

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

  • Error Line 1838, Column 183: required attribute "ALT" not specified
    …ank"><img border="0" src="http://www.solvia.es/img/miniICO_RSS.jpg">Vizcaya</a>

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

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

  • Error Line 1848, Column 182: required attribute "ALT" not specified
    …lank"><img border="0" src="http://www.solvia.es/img/miniICO_RSS.jpg">Zamora</a>

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

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

  • Error Line 1861, Column 184: required attribute "ALT" not specified
    …nk"><img border="0" src="http://www.solvia.es/img/miniICO_RSS.jpg">Zaragoza</a>

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

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

  • Error Line 1875, 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 1875, Column 8: document type does not allow element "SCRIPT" here
    <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).

Visitor Analysis

Daily Visitor
  • 5.833 visits