Ofertas de empleo en Chile. Sitio de empleo líder con miles de trabajos. Ingrese su Curriculum Gratis ahora y comience la búsqueda de una oportunidad de Empleo. ...

trabajando.cl
  • Domain Name
    trabajando.cl
  • Favicon
  • Google Page Rank
    3
  • Alexa Rank
    #36018
  • Page Size
    65.6 KB
  • Ip Address
    200.29.145.52
  • Heading
    H1: 1, H2: 9, H3: 3, H4: 0, H5: 0, H6: 0
  • Images
    24 GIF, 0 JPG, 5 PNG

Website Meta Analysis

  • Title
    Home | Trabajo y Empleos en Chile. Ingresa tu Currículum. Trabajando.com
  • Meta Keyword
    Trabajo, trabajos, empleos, empleo, curriculum, trabajo Chile, curriculum vitae, busco trabajo, empleo joven, buscar trabajo, bolsa de trabajo, empleo en, trabajando, ofertas de empleo, ofertas de trabajo, vacantes de empleo, vacantes de trabajo, curriculum vitae, curriculo, practicas, trabajando.com
  • Meta Description
    Ofertas de empleo en Chile. Sitio de empleo líder con miles de trabajos. Ingrese su Curriculum Gratis ahora y comience la búsqueda de una oportunidad de Empleo.

Technical Analysis

  • Webserver
    Apache
  • Ip Address
    200.29.145.52
  • Domain Age
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from trabajando.cl.

HTML Analysis

  • server: Apache
  • max-age: 15
  • nocache:
  • content-type: text/html; charset=UTF-8
  • content-length: 78161
  • date: Thu, 14 Feb 2013 20:03:01 GMT
  • x-varnish: 2278465876
  • age: 0
  • connection: close
  • x-google-cache-control: remote-cache-hit
  • via: HTTP/1.1 GWA (remote cache hit)
No data whois for trabajando.cl

DNS Analysis


DNS servers
ns.telmexchile.cl [200.27.2.2]
ns2.telmexchile.cl [200.27.2.7]


DNS Records

Answer records
trabajando.cl SOA
server: ns.telmexchile.cl
email: hostmaster@telmexchile.cl
serial: 2005050614
refresh: 7200
retry: 10800
expire: 604800
minimum ttl: 86400
3600s
trabajando.cl NS  ns2.telmexchile.cl 3600s
trabajando.cl NS  ns.telmexchile.cl 3600s
trabajando.cl MX
preference: 0
exchange: centauro.iholding.cl
3600s
trabajando.cl A 200.29.145.52 3600s

Authority records

Additional records
ns.telmexchile.cl A 200.27.2.2 7200s
ns2.telmexchile.cl A 200.27.2.7 7200s

IP 200.29.145.52 Analysis

  • Country Code
    CL
  • Country Code3
    CHL
  • Country Name
    Chile
  • City
    Rinconada
  • Continent Code
    SA
  • Latitude
    30.
  • Longitude
    71.3333

  • % Joint Whois - whois.lacnic.net
    % This server accepts single ASN, IPv4 or IPv6 queries

    % LACNIC resource: whois.lacnic.net


    % Copyright LACNIC lacnic.net
    % The data below is provided for information purposes
    % and to assist persons in obtaining information about or
    % related to AS and IP numbers registrations
    % By submitting a whois query, you agree to use this data
    % only for lawful purposes.
    % 2013-02-14 18:07:09 (BRST -02:00)

    inetnum: 200.29.145.48/29
    status: reallocated
    owner: Trabajando.com Chile s.a.
    ownerid: CL-TCSA9-LACNIC
    responsible: Juan Swett Amenabar
    address: El Matico, 3868, Vitacura
    address: - - Vitacura -
    country: CL
    phone: +56 2 2428798 []
    owner-c: AIC2
    tech-c: AIC2
    abuse-c: AIC2
    created: 20090226
    changed: 20090226
    inetnum-up: 200.29.128/19

    nic-hdl: AIC2
    person: Core Internet Telmex Chile
    e-mail: netadmin@IP.TELMEXCHILE.CL
    address: Rinconada el Salto, 202, Huechuraba
    address: -- - Santiago -
    country: CL
    phone: +56 2 5825365 []
    created: 20030314
    changed: 20070417

    % whois.lacnic.net accepts only direct match queries.
    % Types of queries are: POCs, ownerid, CIDR blocks, IP
    % and AS numbers.

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 138 Errors
  • 88 Warnings
Ratio Text/Html
  • 0.6906037073402957
Message Error
  • Error Line 146, Column 13: there is no attribute "name"
    	<META name="y_key" content="91837ae4214e9750">

    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 146, Column 29: there is no attribute "content"
    	<META name="y_key" content="91837ae4214e9750">

    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 146, Column 47: element "META" undefined
    	<META name="y_key" content="91837ae4214e9750">

    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 147, Column 52: end tag for "meta" omitted, but OMITTAG NO was specified
    	<meta http-equiv="X-UA-Compatible" content="IE=8">

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

  • Info Line 147, Column 2: start tag was here
    	<meta http-equiv="X-UA-Compatible" content="IE=8">
  • Error Line 223, Column 16: there is no attribute "property"
    <meta property="og:title" content="Trabajando.com Chile" />

    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 276, Column 171: end tag for "link" omitted, but OMITTAG NO was specified
    …docl" title="Trabajo y Empleos en Chile. Ingresa tu Currículum. Trabajando.cl">

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

  • Info Line 276, Column 1: start tag was here
    <link rel="alternate" type="application/rss+xml" href="http://feeds.feedburner.…
  • Error Line 291, Column 32: required attribute "type" not specified
    		<script language="JavaScript">

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

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

  • Error Line 365, Column 8: required attribute "type" not specified
    <script>(function(d, s, id) {

    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 398, Column 7: end tag for "META" omitted, but OMITTAG NO was specified
    </head>

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

  • Info Line 146, Column 2: start tag was here
    	<META name="y_key" content="91837ae4214e9750">
  • Error Line 398, Column 7: end tag for "head" which is not finished
    </head>

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

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

  • Error Line 432, Column 22: there is no attribute "alt"
    	<h1><a href="/" alt="Logo Trabajando.com Empleos Chile" title="Trabajo y Emple…

    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 439, Column 53: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
                        <div class="buscadorSelectStyle">

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

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

  • Error Line 490, Column 141: end tag for "input" omitted, but OMITTAG NO was specified
    …squeda', 'Boton Buscar Home');" value="Buscar" class="btnSearch" type="submit">

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

  • Info Line 490, Column 6: start tag was here
    					<input onclick="pageTrackerCons._trackEvent('Forms', 'Busqueda', 'Boton Bu…
  • Error Line 491, Column 61: end tag for "input" omitted, but OMITTAG NO was specified
    					<input name="busquedaavanzada" value="1" type="hidden">

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

  • Info Line 491, Column 6: start tag was here
    					<input name="busquedaavanzada" value="1" type="hidden">
  • Error Line 538, Column 49: there is no attribute "honclick"
    …      <a class="btnEmpresas" honclick="pageTrackerCons._trackEvent('Links', 'C…

    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 570, Column 38: invalid comment declaration: found name character outside comment but inside comment declaration
                	<!-- INICIO NAVEGADOR --->
  • Info Line 570, Column 14: comment declaration started here
                	<!-- INICIO NAVEGADOR --->
  • Error Line 607, Column 14: ID "BoxCategorias" already defined
    				<div id="BoxCategorias">

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

  • Info Line 605, Column 24: ID "BoxCategorias" first defined here
               	  <div id="BoxCategorias">
  • Error Line 823, Column 61: end tag for "input" omitted, but OMITTAG NO was specified
    <input type="hidden" id="segundo" name="segundo" value="59">

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

  • Info Line 823, Column 1: start tag was here
    <input type="hidden" id="segundo" name="segundo" value="59">
  • Error Line 839, Column 32: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                                <li> 

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

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

  • Error Line 849, Column 32: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                                <li> 

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

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

  • Error Line 859, Column 48: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                                <li class="section"> 

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

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

  • Error Line 869, Column 32: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                                <li> 

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

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

  • Error Line 879, Column 32: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                                <li> 

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

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

  • Error Line 889, Column 48: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                                <li class="section"> 

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

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

  • Error Line 899, Column 32: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                                <li> 

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

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

  • Error Line 909, Column 32: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                                <li> 

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

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

  • Error Line 919, Column 48: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                                <li class="section"> 

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

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

  • Error Line 929, Column 32: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                                <li> 

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

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

  • Error Line 939, Column 32: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                                <li> 

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

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

  • Error Line 949, Column 48: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                                <li class="section"> 

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

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

  • Error Line 959, Column 32: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                                <li> 

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

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

  • Error Line 969, Column 32: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                                <li> 

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

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

  • Error Line 979, Column 48: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                                <li class="section"> 

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

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

  • Error Line 989, Column 32: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                                <li> 

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

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

  • Error Line 999, Column 32: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                                <li> 

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

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

  • Error Line 1009, Column 48: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                                <li class="section"> 

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

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

  • Error Line 1019, Column 32: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                                <li> 

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

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

  • Error Line 1029, Column 32: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                                <li> 

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

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

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

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

  • Info Line 1029, Column 29: start tag was here
                                <li> 
  • Error Line 1039, Column 25: end tag for "li" omitted, but OMITTAG NO was specified
                        </ul>

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

  • Info Line 1019, Column 29: start tag was here
                                <li> 
  • Error Line 1039, Column 25: end tag for "li" omitted, but OMITTAG NO was specified
                        </ul>

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

  • Info Line 1009, Column 29: start tag was here
                                <li class="section"> 
  • Error Line 1039, Column 25: end tag for "li" omitted, but OMITTAG NO was specified
                        </ul>

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

  • Info Line 999, Column 29: start tag was here
                                <li> 
  • Error Line 1039, Column 25: end tag for "li" omitted, but OMITTAG NO was specified
                        </ul>

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

  • Info Line 989, Column 29: start tag was here
                                <li> 
  • Error Line 1039, Column 25: end tag for "li" omitted, but OMITTAG NO was specified
                        </ul>

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

  • Info Line 979, Column 29: start tag was here
                                <li class="section"> 
  • Error Line 1039, Column 25: end tag for "li" omitted, but OMITTAG NO was specified
                        </ul>

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

  • Info Line 969, Column 29: start tag was here
                                <li> 
  • Error Line 1039, Column 25: end tag for "li" omitted, but OMITTAG NO was specified
                        </ul>

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

  • Info Line 959, Column 29: start tag was here
                                <li> 
  • Error Line 1039, Column 25: end tag for "li" omitted, but OMITTAG NO was specified
                        </ul>

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

  • Info Line 949, Column 29: start tag was here
                                <li class="section"> 
  • Error Line 1039, Column 25: end tag for "li" omitted, but OMITTAG NO was specified
                        </ul>

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

  • Info Line 939, Column 29: start tag was here
                                <li> 
  • Error Line 1039, Column 25: end tag for "li" omitted, but OMITTAG NO was specified
                        </ul>

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

  • Info Line 929, Column 29: start tag was here
                                <li> 
  • Error Line 1039, Column 25: end tag for "li" omitted, but OMITTAG NO was specified
                        </ul>

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

  • Info Line 919, Column 29: start tag was here
                                <li class="section"> 
  • Error Line 1039, Column 25: end tag for "li" omitted, but OMITTAG NO was specified
                        </ul>

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

  • Info Line 909, Column 29: start tag was here
                                <li> 
  • Error Line 1039, Column 25: end tag for "li" omitted, but OMITTAG NO was specified
                        </ul>

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

  • Info Line 899, Column 29: start tag was here
                                <li> 
  • Error Line 1039, Column 25: end tag for "li" omitted, but OMITTAG NO was specified
                        </ul>

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

  • Info Line 889, Column 29: start tag was here
                                <li class="section"> 
  • Error Line 1039, Column 25: end tag for "li" omitted, but OMITTAG NO was specified
                        </ul>

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

  • Info Line 879, Column 29: start tag was here
                                <li> 
  • Error Line 1039, Column 25: end tag for "li" omitted, but OMITTAG NO was specified
                        </ul>

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

  • Info Line 869, Column 29: start tag was here
                                <li> 
  • Error Line 1039, Column 25: end tag for "li" omitted, but OMITTAG NO was specified
                        </ul>

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

  • Info Line 859, Column 29: start tag was here
                                <li class="section"> 
  • Error Line 1039, Column 25: end tag for "li" omitted, but OMITTAG NO was specified
                        </ul>

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

  • Info Line 849, Column 29: start tag was here
                                <li> 
  • Error Line 1039, Column 25: end tag for "li" omitted, but OMITTAG NO was specified
                        </ul>

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

  • Info Line 839, Column 29: start tag was here
                                <li> 
  • Error Line 1039, Column 25: end tag for "li" omitted, but OMITTAG NO was specified
                        </ul>

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

  • Info Line 829, Column 29: start tag was here
                                <li class="section"> 
  • Error Line 1045, Column 263: required attribute "alt" not specified
    …if" class="spt navegacionPaginacion" /> Anterior</a><span class="hide"> | </sp…

    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 1045, Column 571: required attribute "alt" not specified
    …o.com/ver1.0/img/asset/comunes/dot.gif" class="spt navegacionPaginacion" /></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 1050, 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>.

  • Warning Line 1815, Column 87: cannot generate system identifier for general entity "pag"
    …os', 'Paginación', 'Pag 2');" href="?&pag=2&ordenarpor=avisofechapublicacion&t…

    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 1815, Column 87: general entity "pag" not defined and no default entity
    …os', 'Paginación', 'Pag 2');" href="?&pag=2&ordenarpor=avisofechapublicacion&t…

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

  • Warning Line 1815, Column 90: reference not terminated by REFC delimiter
    …, 'Paginación', 'Pag 2');" href="?&pag=2&ordenarpor=avisofechapublicacion&tipo…

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

  • Warning Line 1815, Column 90: reference to external entity in attribute value
    …, 'Paginación', 'Pag 2');" href="?&pag=2&ordenarpor=avisofechapublicacion&tipo…

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

  • Error Line 1815, Column 90: reference to entity "pag" for which no system identifier could be generated
    …, 'Paginación', 'Pag 2');" href="?&pag=2&ordenarpor=avisofechapublicacion&tipo…

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

  • Info Line 1815, Column 86: entity was defined here
    …sos', 'Paginación', 'Pag 2');" href="?&pag=2&ordenarpor=avisofechapublicacion&…
  • Warning Line 1815, Column 93: cannot generate system identifier for general entity "ordenarpor"
    …Paginación', 'Pag 2');" href="?&pag=2&ordenarpor=avisofechapublicacion&tipoord…

    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 1815, Column 93: general entity "ordenarpor" not defined and no default entity
    …Paginación', 'Pag 2');" href="?&pag=2&ordenarpor=avisofechapublicacion&tipoord…

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

  • Warning Line 1815, Column 103: reference not terminated by REFC delimiter
    …', 'Pag 2');" href="?&pag=2&ordenarpor=avisofechapublicacion&tipoorden=desc&#U…

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

  • Warning Line 1815, Column 103: reference to external entity in attribute value
    …', 'Pag 2');" href="?&pag=2&ordenarpor=avisofechapublicacion&tipoorden=desc&#U…

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

  • Error Line 1815, Column 103: reference to entity "ordenarpor" for which no system identifier could be generated
    …', 'Pag 2');" href="?&pag=2&ordenarpor=avisofechapublicacion&tipoorden=desc&#U…

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

  • Info Line 1815, Column 92: entity was defined here
    …'Paginación', 'Pag 2');" href="?&pag=2&ordenarpor=avisofechapublicacion&tipoor…
  • Warning Line 1815, Column 126: cannot generate system identifier for general entity "tipoorden"
    …f="?&pag=2&ordenarpor=avisofechapublicacion&tipoorden=desc&#UIofertas">2</a> - 

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

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

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

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

  • Error Line 1815, Column 126: general entity "tipoorden" not defined and no default entity
    …f="?&pag=2&ordenarpor=avisofechapublicacion&tipoorden=desc&#UIofertas">2</a> - 

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

  • Warning Line 1815, Column 135: reference not terminated by REFC delimiter
    …f="?&pag=2&ordenarpor=avisofechapublicacion&tipoorden=desc&#UIofertas">2</a> - 

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

  • Warning Line 1815, Column 135: reference to external entity in attribute value
    …f="?&pag=2&ordenarpor=avisofechapublicacion&tipoorden=desc&#UIofertas">2</a> - 

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

  • Error Line 1815, Column 135: reference to entity "tipoorden" for which no system identifier could be generated
    …f="?&pag=2&ordenarpor=avisofechapublicacion&tipoorden=desc&#UIofertas">2</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 1815, Column 125: entity was defined here
    …f="?&pag=2&ordenarpor=avisofechapublicacion&tipoorden=desc&#UIofertas">2</a> - 
  • Warning Line 1815, Column 140: named character reference
    …f="?&pag=2&ordenarpor=avisofechapublicacion&tipoorden=desc&#UIofertas">2</a> - 
  • Error Line 1815, Column 142: "UIofertas" is not a function name
    …f="?&pag=2&ordenarpor=avisofechapublicacion&tipoorden=desc&#UIofertas">2</a> - 
  • Warning Line 1815, Column 151: reference not terminated by REFC delimiter
    …f="?&pag=2&ordenarpor=avisofechapublicacion&tipoorden=desc&#UIofertas">2</a> - 

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

  • Warning Line 1819, Column 90: reference not terminated by REFC delimiter
    …, 'Paginación', 'Pag 3');" href="?&pag=3&ordenarpor=avisofechapublicacion&tipo…

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

  • Warning Line 1819, Column 90: reference to external entity in attribute value
    …, 'Paginación', 'Pag 3');" href="?&pag=3&ordenarpor=avisofechapublicacion&tipo…

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

  • Error Line 1819, Column 90: reference to entity "pag" for which no system identifier could be generated
    …, 'Paginación', 'Pag 3');" href="?&pag=3&ordenarpor=avisofechapublicacion&tipo…

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

  • Info Line 1815, Column 86: entity was defined here
    …sos', 'Paginación', 'Pag 2');" href="?&pag=2&ordenarpor=avisofechapublicacion&…
  • Warning Line 1819, Column 103: reference not terminated by REFC delimiter
    …', 'Pag 3');" href="?&pag=3&ordenarpor=avisofechapublicacion&tipoorden=desc&#U…

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

  • Warning Line 1819, Column 103: reference to external entity in attribute value
    …', 'Pag 3');" href="?&pag=3&ordenarpor=avisofechapublicacion&tipoorden=desc&#U…

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

  • Error Line 1819, Column 103: reference to entity "ordenarpor" for which no system identifier could be generated
    …', 'Pag 3');" href="?&pag=3&ordenarpor=avisofechapublicacion&tipoorden=desc&#U…

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

  • Info Line 1815, Column 92: entity was defined here
    …'Paginación', 'Pag 2');" href="?&pag=2&ordenarpor=avisofechapublicacion&tipoor…
  • Warning Line 1819, Column 135: reference not terminated by REFC delimiter
    …f="?&pag=3&ordenarpor=avisofechapublicacion&tipoorden=desc&#UIofertas">3</a> - 

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

  • Warning Line 1819, Column 135: reference to external entity in attribute value
    …f="?&pag=3&ordenarpor=avisofechapublicacion&tipoorden=desc&#UIofertas">3</a> - 

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

  • Error Line 1819, Column 135: reference to entity "tipoorden" for which no system identifier could be generated
    …f="?&pag=3&ordenarpor=avisofechapublicacion&tipoorden=desc&#UIofertas">3</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 1815, Column 125: entity was defined here
    …f="?&pag=2&ordenarpor=avisofechapublicacion&tipoorden=desc&#UIofertas">2</a> - 
  • Warning Line 1819, Column 140: named character reference
    …f="?&pag=3&ordenarpor=avisofechapublicacion&tipoorden=desc&#UIofertas">3</a> - 
  • Error Line 1819, Column 142: "UIofertas" is not a function name
    …f="?&pag=3&ordenarpor=avisofechapublicacion&tipoorden=desc&#UIofertas">3</a> - 
  • Warning Line 1819, Column 151: reference not terminated by REFC delimiter
    …f="?&pag=3&ordenarpor=avisofechapublicacion&tipoorden=desc&#UIofertas">3</a> - 

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

  • Warning Line 1823, Column 90: reference not terminated by REFC delimiter
    …, 'Paginación', 'Pag 4');" href="?&pag=4&ordenarpor=avisofechapublicacion&tipo…

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

  • Warning Line 1823, Column 90: reference to external entity in attribute value
    …, 'Paginación', 'Pag 4');" href="?&pag=4&ordenarpor=avisofechapublicacion&tipo…

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

  • Error Line 1823, Column 90: reference to entity "pag" for which no system identifier could be generated
    …, 'Paginación', 'Pag 4');" href="?&pag=4&ordenarpor=avisofechapublicacion&tipo…

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

  • Info Line 1815, Column 86: entity was defined here
    …sos', 'Paginación', 'Pag 2');" href="?&pag=2&ordenarpor=avisofechapublicacion&…
  • Warning Line 1823, Column 103: reference not terminated by REFC delimiter
    …', 'Pag 4');" href="?&pag=4&ordenarpor=avisofechapublicacion&tipoorden=desc&#U…

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

  • Warning Line 1823, Column 103: reference to external entity in attribute value
    …', 'Pag 4');" href="?&pag=4&ordenarpor=avisofechapublicacion&tipoorden=desc&#U…

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

  • Error Line 1823, Column 103: reference to entity "ordenarpor" for which no system identifier could be generated
    …', 'Pag 4');" href="?&pag=4&ordenarpor=avisofechapublicacion&tipoorden=desc&#U…

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

  • Info Line 1815, Column 92: entity was defined here
    …'Paginación', 'Pag 2');" href="?&pag=2&ordenarpor=avisofechapublicacion&tipoor…
  • Warning Line 1823, Column 135: reference not terminated by REFC delimiter
    …f="?&pag=4&ordenarpor=avisofechapublicacion&tipoorden=desc&#UIofertas">4</a> - 

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

  • Warning Line 1823, Column 135: reference to external entity in attribute value
    …f="?&pag=4&ordenarpor=avisofechapublicacion&tipoorden=desc&#UIofertas">4</a> - 

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

  • Error Line 1823, Column 135: reference to entity "tipoorden" for which no system identifier could be generated
    …f="?&pag=4&ordenarpor=avisofechapublicacion&tipoorden=desc&#UIofertas">4</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 1815, Column 125: entity was defined here
    …f="?&pag=2&ordenarpor=avisofechapublicacion&tipoorden=desc&#UIofertas">2</a> - 
  • Warning Line 1823, Column 140: named character reference
    …f="?&pag=4&ordenarpor=avisofechapublicacion&tipoorden=desc&#UIofertas">4</a> - 
  • Error Line 1823, Column 142: "UIofertas" is not a function name
    …f="?&pag=4&ordenarpor=avisofechapublicacion&tipoorden=desc&#UIofertas">4</a> - 
  • Warning Line 1823, Column 151: reference not terminated by REFC delimiter
    …f="?&pag=4&ordenarpor=avisofechapublicacion&tipoorden=desc&#UIofertas">4</a> - 

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

  • Warning Line 1827, Column 90: reference not terminated by REFC delimiter
    …, 'Paginación', 'Pag 5');" href="?&pag=5&ordenarpor=avisofechapublicacion&tipo…

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

  • Warning Line 1827, Column 90: reference to external entity in attribute value
    …, 'Paginación', 'Pag 5');" href="?&pag=5&ordenarpor=avisofechapublicacion&tipo…

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

  • Error Line 1827, Column 90: reference to entity "pag" for which no system identifier could be generated
    …, 'Paginación', 'Pag 5');" href="?&pag=5&ordenarpor=avisofechapublicacion&tipo…

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

  • Info Line 1815, Column 86: entity was defined here
    …sos', 'Paginación', 'Pag 2');" href="?&pag=2&ordenarpor=avisofechapublicacion&…
  • Warning Line 1827, Column 103: reference not terminated by REFC delimiter
    …', 'Pag 5');" href="?&pag=5&ordenarpor=avisofechapublicacion&tipoorden=desc&#U…

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

  • Warning Line 1827, Column 103: reference to external entity in attribute value
    …', 'Pag 5');" href="?&pag=5&ordenarpor=avisofechapublicacion&tipoorden=desc&#U…

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

  • Error Line 1827, Column 103: reference to entity "ordenarpor" for which no system identifier could be generated
    …', 'Pag 5');" href="?&pag=5&ordenarpor=avisofechapublicacion&tipoorden=desc&#U…

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

  • Info Line 1815, Column 92: entity was defined here
    …'Paginación', 'Pag 2');" href="?&pag=2&ordenarpor=avisofechapublicacion&tipoor…
  • Warning Line 1827, Column 135: reference not terminated by REFC delimiter
    …f="?&pag=5&ordenarpor=avisofechapublicacion&tipoorden=desc&#UIofertas">5</a> - 

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

  • Warning Line 1827, Column 135: reference to external entity in attribute value
    …f="?&pag=5&ordenarpor=avisofechapublicacion&tipoorden=desc&#UIofertas">5</a> - 

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

  • Error Line 1827, Column 135: reference to entity "tipoorden" for which no system identifier could be generated
    …f="?&pag=5&ordenarpor=avisofechapublicacion&tipoorden=desc&#UIofertas">5</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 1815, Column 125: entity was defined here
    …f="?&pag=2&ordenarpor=avisofechapublicacion&tipoorden=desc&#UIofertas">2</a> - 
  • Warning Line 1827, Column 140: named character reference
    …f="?&pag=5&ordenarpor=avisofechapublicacion&tipoorden=desc&#UIofertas">5</a> - 
  • Error Line 1827, Column 142: "UIofertas" is not a function name
    …f="?&pag=5&ordenarpor=avisofechapublicacion&tipoorden=desc&#UIofertas">5</a> - 
  • Warning Line 1827, Column 151: reference not terminated by REFC delimiter
    …f="?&pag=5&ordenarpor=avisofechapublicacion&tipoorden=desc&#UIofertas">5</a> - 

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

  • Warning Line 1831, Column 90: reference not terminated by REFC delimiter
    …, 'Paginación', 'Pag 6');" href="?&pag=6&ordenarpor=avisofechapublicacion&tipo…

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

  • Warning Line 1831, Column 90: reference to external entity in attribute value
    …, 'Paginación', 'Pag 6');" href="?&pag=6&ordenarpor=avisofechapublicacion&tipo…

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

  • Error Line 1831, Column 90: reference to entity "pag" for which no system identifier could be generated
    …, 'Paginación', 'Pag 6');" href="?&pag=6&ordenarpor=avisofechapublicacion&tipo…

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

  • Info Line 1815, Column 86: entity was defined here
    …sos', 'Paginación', 'Pag 2');" href="?&pag=2&ordenarpor=avisofechapublicacion&…
  • Warning Line 1831, Column 103: reference not terminated by REFC delimiter
    …', 'Pag 6');" href="?&pag=6&ordenarpor=avisofechapublicacion&tipoorden=desc&#U…

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

  • Warning Line 1831, Column 103: reference to external entity in attribute value
    …', 'Pag 6');" href="?&pag=6&ordenarpor=avisofechapublicacion&tipoorden=desc&#U…

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

  • Error Line 1831, Column 103: reference to entity "ordenarpor" for which no system identifier could be generated
    …', 'Pag 6');" href="?&pag=6&ordenarpor=avisofechapublicacion&tipoorden=desc&#U…

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

  • Info Line 1815, Column 92: entity was defined here
    …'Paginación', 'Pag 2');" href="?&pag=2&ordenarpor=avisofechapublicacion&tipoor…
  • Warning Line 1831, Column 135: reference not terminated by REFC delimiter
    …f="?&pag=6&ordenarpor=avisofechapublicacion&tipoorden=desc&#UIofertas">6</a> - 

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

  • Warning Line 1831, Column 135: reference to external entity in attribute value
    …f="?&pag=6&ordenarpor=avisofechapublicacion&tipoorden=desc&#UIofertas">6</a> - 

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

  • Error Line 1831, Column 135: reference to entity "tipoorden" for which no system identifier could be generated
    …f="?&pag=6&ordenarpor=avisofechapublicacion&tipoorden=desc&#UIofertas">6</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 1815, Column 125: entity was defined here
    …f="?&pag=2&ordenarpor=avisofechapublicacion&tipoorden=desc&#UIofertas">2</a> - 
  • Warning Line 1831, Column 140: named character reference
    …f="?&pag=6&ordenarpor=avisofechapublicacion&tipoorden=desc&#UIofertas">6</a> - 
  • Error Line 1831, Column 142: "UIofertas" is not a function name
    …f="?&pag=6&ordenarpor=avisofechapublicacion&tipoorden=desc&#UIofertas">6</a> - 
  • Warning Line 1831, Column 151: reference not terminated by REFC delimiter
    …f="?&pag=6&ordenarpor=avisofechapublicacion&tipoorden=desc&#UIofertas">6</a> - 

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

  • Warning Line 1835, Column 90: reference not terminated by REFC delimiter
    …, 'Paginación', 'Pag 7');" href="?&pag=7&ordenarpor=avisofechapublicacion&tipo…

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

  • Warning Line 1835, Column 90: reference to external entity in attribute value
    …, 'Paginación', 'Pag 7');" href="?&pag=7&ordenarpor=avisofechapublicacion&tipo…

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

  • Error Line 1835, Column 90: reference to entity "pag" for which no system identifier could be generated
    …, 'Paginación', 'Pag 7');" href="?&pag=7&ordenarpor=avisofechapublicacion&tipo…

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

  • Info Line 1815, Column 86: entity was defined here
    …sos', 'Paginación', 'Pag 2');" href="?&pag=2&ordenarpor=avisofechapublicacion&…
  • Warning Line 1835, Column 103: reference not terminated by REFC delimiter
    …', 'Pag 7');" href="?&pag=7&ordenarpor=avisofechapublicacion&tipoorden=desc&#U…

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

  • Warning Line 1835, Column 103: reference to external entity in attribute value
    …', 'Pag 7');" href="?&pag=7&ordenarpor=avisofechapublicacion&tipoorden=desc&#U…

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

  • Error Line 1835, Column 103: reference to entity "ordenarpor" for which no system identifier could be generated
    …', 'Pag 7');" href="?&pag=7&ordenarpor=avisofechapublicacion&tipoorden=desc&#U…

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

  • Info Line 1815, Column 92: entity was defined here
    …'Paginación', 'Pag 2');" href="?&pag=2&ordenarpor=avisofechapublicacion&tipoor…
  • Warning Line 1835, Column 135: reference not terminated by REFC delimiter
    …f="?&pag=7&ordenarpor=avisofechapublicacion&tipoorden=desc&#UIofertas">7</a> - 

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

  • Warning Line 1835, Column 135: reference to external entity in attribute value
    …f="?&pag=7&ordenarpor=avisofechapublicacion&tipoorden=desc&#UIofertas">7</a> - 

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

  • Error Line 1835, Column 135: reference to entity "tipoorden" for which no system identifier could be generated
    …f="?&pag=7&ordenarpor=avisofechapublicacion&tipoorden=desc&#UIofertas">7</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 1815, Column 125: entity was defined here
    …f="?&pag=2&ordenarpor=avisofechapublicacion&tipoorden=desc&#UIofertas">2</a> - 
  • Warning Line 1835, Column 140: named character reference
    …f="?&pag=7&ordenarpor=avisofechapublicacion&tipoorden=desc&#UIofertas">7</a> - 
  • Error Line 1835, Column 142: "UIofertas" is not a function name
    …f="?&pag=7&ordenarpor=avisofechapublicacion&tipoorden=desc&#UIofertas">7</a> - 
  • Warning Line 1835, Column 151: reference not terminated by REFC delimiter
    …f="?&pag=7&ordenarpor=avisofechapublicacion&tipoorden=desc&#UIofertas">7</a> - 

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

  • Warning Line 1839, Column 90: reference not terminated by REFC delimiter
    …, 'Paginación', 'Pag 8');" href="?&pag=8&ordenarpor=avisofechapublicacion&tipo…

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

  • Warning Line 1839, Column 90: reference to external entity in attribute value
    …, 'Paginación', 'Pag 8');" href="?&pag=8&ordenarpor=avisofechapublicacion&tipo…

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

  • Error Line 1839, Column 90: reference to entity "pag" for which no system identifier could be generated
    …, 'Paginación', 'Pag 8');" href="?&pag=8&ordenarpor=avisofechapublicacion&tipo…

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

  • Info Line 1815, Column 86: entity was defined here
    …sos', 'Paginación', 'Pag 2');" href="?&pag=2&ordenarpor=avisofechapublicacion&…
  • Warning Line 1839, Column 103: reference not terminated by REFC delimiter
    …', 'Pag 8');" href="?&pag=8&ordenarpor=avisofechapublicacion&tipoorden=desc&#U…

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

  • Warning Line 1839, Column 103: reference to external entity in attribute value
    …', 'Pag 8');" href="?&pag=8&ordenarpor=avisofechapublicacion&tipoorden=desc&#U…

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

  • Error Line 1839, Column 103: reference to entity "ordenarpor" for which no system identifier could be generated
    …', 'Pag 8');" href="?&pag=8&ordenarpor=avisofechapublicacion&tipoorden=desc&#U…

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

  • Info Line 1815, Column 92: entity was defined here
    …'Paginación', 'Pag 2');" href="?&pag=2&ordenarpor=avisofechapublicacion&tipoor…
  • Warning Line 1839, Column 135: reference not terminated by REFC delimiter
    …f="?&pag=8&ordenarpor=avisofechapublicacion&tipoorden=desc&#UIofertas">8</a> - 

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

  • Warning Line 1839, Column 135: reference to external entity in attribute value
    …f="?&pag=8&ordenarpor=avisofechapublicacion&tipoorden=desc&#UIofertas">8</a> - 

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

  • Error Line 1839, Column 135: reference to entity "tipoorden" for which no system identifier could be generated
    …f="?&pag=8&ordenarpor=avisofechapublicacion&tipoorden=desc&#UIofertas">8</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 1815, Column 125: entity was defined here
    …f="?&pag=2&ordenarpor=avisofechapublicacion&tipoorden=desc&#UIofertas">2</a> - 
  • Warning Line 1839, Column 140: named character reference
    …f="?&pag=8&ordenarpor=avisofechapublicacion&tipoorden=desc&#UIofertas">8</a> - 
  • Error Line 1839, Column 142: "UIofertas" is not a function name
    …f="?&pag=8&ordenarpor=avisofechapublicacion&tipoorden=desc&#UIofertas">8</a> - 
  • Warning Line 1839, Column 151: reference not terminated by REFC delimiter
    …f="?&pag=8&ordenarpor=avisofechapublicacion&tipoorden=desc&#UIofertas">8</a> - 

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

  • Warning Line 1843, Column 90: reference not terminated by REFC delimiter
    …, 'Paginación', 'Pag 9');" href="?&pag=9&ordenarpor=avisofechapublicacion&tipo…

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

  • Warning Line 1843, Column 90: reference to external entity in attribute value
    …, 'Paginación', 'Pag 9');" href="?&pag=9&ordenarpor=avisofechapublicacion&tipo…

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

  • Error Line 1843, Column 90: reference to entity "pag" for which no system identifier could be generated
    …, 'Paginación', 'Pag 9');" href="?&pag=9&ordenarpor=avisofechapublicacion&tipo…

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

  • Info Line 1815, Column 86: entity was defined here
    …sos', 'Paginación', 'Pag 2');" href="?&pag=2&ordenarpor=avisofechapublicacion&…
  • Warning Line 1843, Column 103: reference not terminated by REFC delimiter
    …', 'Pag 9');" href="?&pag=9&ordenarpor=avisofechapublicacion&tipoorden=desc&#U…

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

  • Warning Line 1843, Column 103: reference to external entity in attribute value
    …', 'Pag 9');" href="?&pag=9&ordenarpor=avisofechapublicacion&tipoorden=desc&#U…

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

  • Error Line 1843, Column 103: reference to entity "ordenarpor" for which no system identifier could be generated
    …', 'Pag 9');" href="?&pag=9&ordenarpor=avisofechapublicacion&tipoorden=desc&#U…

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

  • Info Line 1815, Column 92: entity was defined here
    …'Paginación', 'Pag 2');" href="?&pag=2&ordenarpor=avisofechapublicacion&tipoor…
  • Warning Line 1843, Column 135: reference not terminated by REFC delimiter
    …f="?&pag=9&ordenarpor=avisofechapublicacion&tipoorden=desc&#UIofertas">9</a> - 

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

  • Warning Line 1843, Column 135: reference to external entity in attribute value
    …f="?&pag=9&ordenarpor=avisofechapublicacion&tipoorden=desc&#UIofertas">9</a> - 

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

  • Error Line 1843, Column 135: reference to entity "tipoorden" for which no system identifier could be generated
    …f="?&pag=9&ordenarpor=avisofechapublicacion&tipoorden=desc&#UIofertas">9</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 1815, Column 125: entity was defined here
    …f="?&pag=2&ordenarpor=avisofechapublicacion&tipoorden=desc&#UIofertas">2</a> - 
  • Warning Line 1843, Column 140: named character reference
    …f="?&pag=9&ordenarpor=avisofechapublicacion&tipoorden=desc&#UIofertas">9</a> - 
  • Error Line 1843, Column 142: "UIofertas" is not a function name
    …f="?&pag=9&ordenarpor=avisofechapublicacion&tipoorden=desc&#UIofertas">9</a> - 
  • Warning Line 1843, Column 151: reference not terminated by REFC delimiter
    …f="?&pag=9&ordenarpor=avisofechapublicacion&tipoorden=desc&#UIofertas">9</a> - 

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

  • Warning Line 1847, Column 91: reference not terminated by REFC delimiter
    … 'Paginación', 'Pag 10');" href="?&pag=10&ordenarpor=avisofechapublicacion&tip…

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

  • Warning Line 1847, Column 91: reference to external entity in attribute value
    … 'Paginación', 'Pag 10');" href="?&pag=10&ordenarpor=avisofechapublicacion&tip…

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

  • Error Line 1847, Column 91: reference to entity "pag" for which no system identifier could be generated
    … 'Paginación', 'Pag 10');" href="?&pag=10&ordenarpor=avisofechapublicacion&tip…

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

  • Info Line 1815, Column 86: entity was defined here
    …sos', 'Paginación', 'Pag 2');" href="?&pag=2&ordenarpor=avisofechapublicacion&…
  • Warning Line 1847, Column 105: reference not terminated by REFC delimiter
    … 'Pag 10');" href="?&pag=10&ordenarpor=avisofechapublicacion&tipoorden=desc&#U…

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

  • Warning Line 1847, Column 105: reference to external entity in attribute value
    … 'Pag 10');" href="?&pag=10&ordenarpor=avisofechapublicacion&tipoorden=desc&#U…

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

  • Error Line 1847, Column 105: reference to entity "ordenarpor" for which no system identifier could be generated
    … 'Pag 10');" href="?&pag=10&ordenarpor=avisofechapublicacion&tipoorden=desc&#U…

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

  • Info Line 1815, Column 92: entity was defined here
    …'Paginación', 'Pag 2');" href="?&pag=2&ordenarpor=avisofechapublicacion&tipoor…
  • Warning Line 1847, Column 137: reference not terminated by REFC delimiter
    …"?&pag=10&ordenarpor=avisofechapublicacion&tipoorden=desc&#UIofertas">10</a> - 

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

  • Warning Line 1847, Column 137: reference to external entity in attribute value
    …"?&pag=10&ordenarpor=avisofechapublicacion&tipoorden=desc&#UIofertas">10</a> - 

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

  • Error Line 1847, Column 137: reference to entity "tipoorden" for which no system identifier could be generated
    …"?&pag=10&ordenarpor=avisofechapublicacion&tipoorden=desc&#UIofertas">10</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 1815, Column 125: entity was defined here
    …f="?&pag=2&ordenarpor=avisofechapublicacion&tipoorden=desc&#UIofertas">2</a> - 
  • Warning Line 1847, Column 142: named character reference
    …"?&pag=10&ordenarpor=avisofechapublicacion&tipoorden=desc&#UIofertas">10</a> - 
  • Error Line 1847, Column 144: "UIofertas" is not a function name
    …"?&pag=10&ordenarpor=avisofechapublicacion&tipoorden=desc&#UIofertas">10</a> - 
  • Warning Line 1847, Column 153: reference not terminated by REFC delimiter
    …"?&pag=10&ordenarpor=avisofechapublicacion&tipoorden=desc&#UIofertas">10</a> - 

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

  • Warning Line 1851, Column 94: reference not terminated by REFC delimiter
    …aginación', 'Siguiente');" href="?&pag=2&ordenarpor=avisofechapublicacion&tipo…

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

  • Warning Line 1851, Column 94: reference to external entity in attribute value
    …aginación', 'Siguiente');" href="?&pag=2&ordenarpor=avisofechapublicacion&tipo…

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

  • Error Line 1851, Column 94: reference to entity "pag" for which no system identifier could be generated
    …aginación', 'Siguiente');" href="?&pag=2&ordenarpor=avisofechapublicacion&tipo…

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

  • Info Line 1815, Column 86: entity was defined here
    …sos', 'Paginación', 'Pag 2');" href="?&pag=2&ordenarpor=avisofechapublicacion&…
  • Warning Line 1851, Column 107: reference not terminated by REFC delimiter
    …Siguiente');" href="?&pag=2&ordenarpor=avisofechapublicacion&tipoorden=desc&#U…

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

  • Warning Line 1851, Column 107: reference to external entity in attribute value
    …Siguiente');" href="?&pag=2&ordenarpor=avisofechapublicacion&tipoorden=desc&#U…

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

  • Error Line 1851, Column 107: reference to entity "ordenarpor" for which no system identifier could be generated
    …Siguiente');" href="?&pag=2&ordenarpor=avisofechapublicacion&tipoorden=desc&#U…

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

  • Info Line 1815, Column 92: entity was defined here
    …'Paginación', 'Pag 2');" href="?&pag=2&ordenarpor=avisofechapublicacion&tipoor…
  • Warning Line 1851, Column 139: reference not terminated by REFC delimiter
    …?&pag=2&ordenarpor=avisofechapublicacion&tipoorden=desc&#UIofertas">Avanzar</a>

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

  • Warning Line 1851, Column 139: reference to external entity in attribute value
    …?&pag=2&ordenarpor=avisofechapublicacion&tipoorden=desc&#UIofertas">Avanzar</a>

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

  • Error Line 1851, Column 139: reference to entity "tipoorden" for which no system identifier could be generated
    …?&pag=2&ordenarpor=avisofechapublicacion&tipoorden=desc&#UIofertas">Avanzar</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 1815, Column 125: entity was defined here
    …f="?&pag=2&ordenarpor=avisofechapublicacion&tipoorden=desc&#UIofertas">2</a> - 
  • Warning Line 1851, Column 144: named character reference
    …?&pag=2&ordenarpor=avisofechapublicacion&tipoorden=desc&#UIofertas">Avanzar</a>
  • Error Line 1851, Column 146: "UIofertas" is not a function name
    …?&pag=2&ordenarpor=avisofechapublicacion&tipoorden=desc&#UIofertas">Avanzar</a>
  • Warning Line 1851, Column 155: reference not terminated by REFC delimiter
    …?&pag=2&ordenarpor=avisofechapublicacion&tipoorden=desc&#UIofertas">Avanzar</a>

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

  • Error Line 1898, Column 114: there is no attribute "data-show-count"
    …witter-follow-button" data-show-count="true" data-lang="es">Seguir a @trabajan…

    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 1898, Column 131: there is no attribute "data-lang"
    …follow-button" data-show-count="true" data-lang="es">Seguir a @trabajandocl</a>

    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 1899, Column 8: required attribute "type" not specified
    <script>!function(d,s,id){var js,fjs=d.getElementsByTagName(s)[0];if(!d.getElem…

    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 1903, Column 56: there is no attribute "data-href"
    …       <div class="fb-like" data-href="https://www.facebook.com/trabajandocom.…

    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 1903, Column 113: there is no attribute "data-send"
    …ok.com/trabajandocom.chile" data-send="false" data-width="270" data-show-faces…

    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 1903, Column 132: there is no attribute "data-width"
    …m.chile" data-send="false" data-width="270" data-show-faces="true" data-font="…

    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 1903, Column 154: there is no attribute "data-show-faces"
    …a-send="false" data-width="270" data-show-faces="true" data-font="arial"></div>

    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 1903, Column 171: there is no attribute "data-font"
    …a-send="false" data-width="270" data-show-faces="true" data-font="arial"></div>

    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 1909, Column 17: there is no attribute "size"
    <g:plusone size="medium" annotation="inline" width="299" href="http://www.traba…

    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 1909, Column 37: there is no attribute "annotation"
    <g:plusone size="medium" annotation="inline" width="299" href="http://www.traba…

    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 1909, Column 52: there is no attribute "width"
    …ze="medium" annotation="inline" width="299" href="http://www.trabajando.cl"></…

    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 1909, Column 63: there is no attribute "href"
    …m" annotation="inline" width="299" href="http://www.trabajando.cl"></g:plusone>

    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 1909, Column 89: element "g:plusone" undefined
    …m" annotation="inline" width="299" href="http://www.trabajando.cl"></g:plusone>

    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 2033, Column 123: end tag for element "li" which is not open
    … una gran oportunidad para abrir puertas en el mundo laboral, sin embar...</li>

    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 2038, Column 123: end tag for element "li" which is not open
    …a carrera va más allá de la renta a la cual podemos aspirar una vez egr...</li>

    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 2043, Column 123: end tag for element "li" which is not open
    …ca que en algunos años más en Chile habrá más técnicos que universitari...</li>

    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 2062, Column 107: required attribute "alt" not specified
    …<img src="../uiglobales/img/Links_AyudandoLatam.png" width="100" height="75" />

    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 2074, Column 97: required attribute "alt" not specified
    …          <img src="../uiglobales/img/Links_FEd.png" width="100" height="75" />

    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 2085, Column 103: required attribute "alt" not specified
    …    <img src="../uiglobales/img/Links_JobHunter.png" width="100" height="75" />

    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 2128, Column 198: cannot generate system identifier for general entity "universia"
    …="/portalescomunidad.cfm?listaTipoDominio=1&universia=1">Universidades</a></li>

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

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

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

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

  • Error Line 2128, Column 198: general entity "universia" not defined and no default entity
    …="/portalescomunidad.cfm?listaTipoDominio=1&universia=1">Universidades</a></li>

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

  • Warning Line 2128, Column 207: reference not terminated by REFC delimiter
    …="/portalescomunidad.cfm?listaTipoDominio=1&universia=1">Universidades</a></li>

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

  • Warning Line 2128, Column 207: reference to external entity in attribute value
    …="/portalescomunidad.cfm?listaTipoDominio=1&universia=1">Universidades</a></li>

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

  • Error Line 2128, Column 207: reference to entity "universia" for which no system identifier could be generated
    …="/portalescomunidad.cfm?listaTipoDominio=1&universia=1">Universidades</a></li>

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

  • Info Line 2128, Column 197: entity was defined here
    …="/portalescomunidad.cfm?listaTipoDominio=1&universia=1">Universidades</a></li>
  • Error Line 2137, Column 55: document type does not allow element "span" here; assuming missing "li" start-tag
    … 		<ul class="linksHolding"><span class="title">Sitios de Trabajando.com</span>
  • Error Line 2138, Column 21: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                    	<li><a class="spt100p Universia"  rel="me" title="Empleos Univ…

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

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

  • Error Line 2139, Column 24: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                        <li><a class="spt100p FMLLatam" rel="me" title="Feria Merca…

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

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

  • Error Line 2140, Column 24: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                        <li><a class="spt100p ExpoLatam" rel="me" title="Expo Capit…

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

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

  • Error Line 2141, Column 24: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                        <li><a class="spt100p FEd" rel="me" title="Portal de Formac…

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

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

  • Error Line 2142, Column 24: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                        <li><a class="spt100p JobHunter" rel="me" title="Portal de …

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

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

  • Error Line 2143, Column 24: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                        <li><a class="spt100p AyudandoLatam" rel="me" title="Portal…

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

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

  • Error Line 2144, Column 24: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                        <li><a class="spt100p ConsultingChile" rel="me" title="Port…

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

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

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

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

  • Info Line 2137, Column 36: start tag was here
            		<ul class="linksHolding"><span class="title">Sitios de Trabajando.com…
  • Error Line 2148, Column 73: end tag for element "br" which is not open
    …99 - 2013. <strong>Trabajando.com</strong> </br> Todos Los derechos Reservados.

    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 2170, Column 89: required attribute "alt" not specified
    …     <li><img src="/uiglobales/img/logo_IAB.png" width="62" height="44" /></li>

    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 2171, Column 263: required attribute "alt" not specified
    …img src="/uiglobales/img/logo_Endeavor.png" width="120" height="44" /></a></li>

    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 2316, Column 13: character "&" is the first character of a delimiter but occurred as data
    	if ( (obj) && (obj2) )

    This message may appear in several cases:

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

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.

Visitor Analysis

Daily Visitor
  • 5.950 visits
Daily Visitor