gentetuya.com

Internacionales Nacionales Locales Deportes Tecnología Las Calientes Santiago: condenan dos a 30 años de prisión cada uno por el asesinato un hombre en 2009 Fuego en una vivienda del hospedaje Yaque en Santiago ...

Display Widget for this domain on your website. Click Here
This data was last updated from 02-08-2013 03:45:13  (update).

Overview Info

  • Domain Name
    gentetuya.com
  • Favicon
  • Alexa Rank
    #64766
  • Google Page Rank
    PR 2
  • Ip Address
    74.205.60.196
  • Page Size
    104.9 KB
  • Images
    0 GIF, 35 JPG, 165 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    0 10 16 5 0 0

Website Meta Analysis



  • Title
    GenteTuya.com – Gente Tuya para decir lo tuyo!
  • Meta Keyword
  • Meta Description
    Internacionales Nacionales Locales Deportes Tecnología Las Calientes Santiago: condenan dos a 30 años de prisión cada uno por el asesinato un hombre en 2009 Fuego en una vivienda del hospedaje Yaque en Santiago Santiago: pelea entre seguridad ...

Technical Analysis



  • Webserver
    Apache/2.2.3 (Red Hat)
  • Ip Address
    74.205.60.196
  • Domain Age
    4 Years, 12 Months, 24 days.
  • Javascript Library
    jquery, yui
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Fri, 02 Aug 2013 03:45:08 GMT
  • server: Apache/2.2.3 (Red Hat)
  • x-powered-by: PHP/5.2.17
  • expires: Thu, 19 Nov 1981 08:52:00 GMT
  • cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
  • pragma: no-cache
  • x-pingback: http://www.gentetuya.com/xmlrpc.php
  • vary: User-Agent,Accept-Encoding
  • content-encoding: gzip
  • content-length: 13562
  • connection: close
  • content-type: text/html; charset=UTF-8
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Registrant:
Domains GrupoInternet.com
Santiago
Santiago, ST 00409
Dominican Republic

Domain Name: GENTETUYA.COM
Created on: 10-Jul-08
Expires on: 10-Jul-12
Last Updated on: 07-Jul-11

Administrative Contact:
GrupoInternet.com, Domains email
Santiago
Santiago, ST 00409
Dominican Republic
(809) 971-2177

Technical Contact:
GrupoInternet.com, Domains email
Santiago
Santiago, ST 00409
Dominican Republic
(809) 971-2177

Domain servers in listed order:
NS1.GENTETUYA.NET
NS2.GENTETUYA.NET

DNS Analysis


DNS servers
ns1.gentetuya.net
ns2.gentetuya.net


DNS Records

Answer records
gentetuya.com MX
preference: 10
exchange: mail.gentetuya.com
86400s
gentetuya.com SOA
server: ns1.gentetuya.net
email: support@grupointernet.com
serial: 1336536631
refresh: 10800
retry: 3600
expire: 604800
minimum ttl: 10800
86400s
gentetuya.com NS  ns2.gentetuya.net 86400s
gentetuya.com NS  ns1.gentetuya.net 86400s
gentetuya.com A 74.205.60.196 86400s

Authority records

Additional records
mail.gentetuya.com A 74.205.60.196 86400s
ns1.gentetuya.net A 74.205.60.196 86400s
ns2.gentetuya.net A 74.205.60.197 86400s

IP 74.205.60.196 Analysis

  • Country Code
    US
  • Country Code3
    USA
  • Country Name
    United States
  • City
    New York
  • Continent Code
    10038
  • Latitude
    212
  • Longitude
    501
  • #
    # Query terms are ambiguous. The query is assumed to be:
    # "n 74.205.60.196"
    #
    # Use "?" to get help.
    #

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

    Arturo Abeleda RSPC-92517-1184352905 (NET-74-205-60-192-1) 74.205.60.192 - 74.205.60.199
    Rackspace Hosting RSCP-NET-4 (NET-74-205-0-0-1) 74.205.0.0 - 74.205.127.255


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

Site Same Ip

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 67 Errors
  • 9 Warnings
Ratio Text/Html
  • 0.7437582618085681
Message Error
  • Error Line 1, Column 219: an attribute value must be a literal unless it contains only name characters
    …-es" lang="es-es" ><head><script type=text/javascript” src=”http://mobileweba…

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

  • Error Line 1, Column 241: an attribute value must be a literal unless it contains only name characters
    …ad><script type=”text/javascript” src=http://mobilewebamerica.com/static/js/m…

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

  • Error Line 100, Column 663: NET-enabling start-tag not immediately followed by null end-tag
    …"300" height="199" alt="Apresados22" / alt="Apresados22" class="juimage" /></a…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 100, Column 663: end tag for "img" omitted, but OMITTAG NO was specified
    …"300" height="199" alt="Apresados22" / alt="Apresados22" class="juimage" /></a…

    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 100, Column 527: start tag was here
    …os-&amp;catid=1:locales&amp;Itemid=2"><img  src="http://gentetuya.grupointerne…
  • Error Line 100, Column 1734: there is no attribute "allowTransparency"
    …80px; height:28px;" allowTransparency="true"></iframe></div><div class="jv-fbs…

    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 100, Column 1844: there is no attribute "share_url"
    …_share" type="button_count" share_url="http://gentetuya.com/index.php?option=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 100, Column 2505: there is no attribute "data-url"
    …class="twitter-share-button" data-url="http://gentetuya.com/index.php?option=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 100, Column 2736: there is no attribute "data-count"
    …id=1:locales&amp;Itemid=2" data-count="horizontal" data-via="gentetuya" data-l…

    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 100, Column 2758: there is no attribute "data-via"
    …d=2" data-count="horizontal" data-via="gentetuya" data-lang="es">Tweet</a><scr…

    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 100, Column 2780: there is no attribute "data-lang"
    …ontal" data-via="gentetuya" data-lang="es">Tweet</a><script type="text/javascr…

    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 100, Column 2927: required attribute "type" not specified
    … class="sharemecompactbuttonf"><script>var fbShare = {url: "http://gentetuya.c…

    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 100, Column 3248: required attribute "type" not specified
    …//widgets.fbshare.me/files/fbshare.js"></script></div></div></div><a href="/in…

    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 107, Column 561: NET-enabling start-tag not immediately followed by null end-tag
    …idth="300" height="169" alt="Asia01" / alt="Asia01" class="juimage" /></a></p>…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 107, Column 561: end tag for "img" omitted, but OMITTAG NO was specified
    …idth="300" height="169" alt="Asia01" / alt="Asia01" class="juimage" /></a></p>…

    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 107, Column 435: start tag was here
    …catid=3:internacionales&amp;Itemid=7"><img  src="http://gentetuya.grupointerne…
  • Error Line 107, Column 2592: required attribute "type" not specified
    … class="sharemecompactbuttonf"><script>var fbShare = {url: "http://gentetuya.c…

    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 107, Column 2872: required attribute "type" not specified
    …//widgets.fbshare.me/files/fbshare.js"></script></div></div></div><a href="/in…

    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 114, Column 519: NET-enabling start-tag not immediately followed by null end-tag
    …300" height="225" alt="facebookmar7" / alt="facebookmar7" class="juimage" /></…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 114, Column 519: end tag for "img" omitted, but OMITTAG NO was specified
    …300" height="225" alt="facebookmar7" / alt="facebookmar7" class="juimage" /></…

    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 114, Column 381: start tag was here
    …puede-olvidar&amp;catid=6:tecnologia"><img  src="http://gentetuya.grupointerne…
  • Error Line 114, Column 2589: required attribute "type" not specified
    … class="sharemecompactbuttonf"><script>var fbShare = {url: "http://gentetuya.c…

    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 114, Column 2832: required attribute "type" not specified
    …//widgets.fbshare.me/files/fbshare.js"></script></div></div></div><a href="/in…

    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 121, Column 543: NET-enabling start-tag not immediately followed by null end-tag
    … height="216" alt="MatanDelincuente" / alt="MatanDelincuente" class="juimage" …

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 121, Column 543: end tag for "img" omitted, but OMITTAG NO was specified
    … height="216" alt="MatanDelincuente" / alt="MatanDelincuente" class="juimage" …

    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 121, Column 397: start tag was here
    …catid=3:internacionales&amp;Itemid=7"><img  src="http://gentetuya.grupointerne…
  • Error Line 121, Column 2582: required attribute "type" not specified
    … class="sharemecompactbuttonf"><script>var fbShare = {url: "http://gentetuya.c…

    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 121, Column 2843: required attribute "type" not specified
    …//widgets.fbshare.me/files/fbshare.js"></script></div></div></div><a href="/in…

    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 128, Column 537: NET-enabling start-tag not immediately followed by null end-tag
    …"300" height="169" alt="SedeVacante" / alt="SedeVacante" class="juimage" /></a…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 128, Column 537: end tag for "img" omitted, but OMITTAG NO was specified
    …"300" height="169" alt="SedeVacante" / alt="SedeVacante" class="juimage" /></a…

    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 128, Column 401: start tag was here
    …catid=3:internacionales&amp;Itemid=7"><img  src="http://gentetuya.grupointerne…
  • Error Line 128, Column 2582: required attribute "type" not specified
    … class="sharemecompactbuttonf"><script>var fbShare = {url: "http://gentetuya.c…

    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 128, Column 2845: required attribute "type" not specified
    …//widgets.fbshare.me/files/fbshare.js"></script></div></div></div><a href="/in…

    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 135, Column 551: NET-enabling start-tag not immediately followed by null end-tag
    …0" height="180" alt="iphone-galaxyh" / alt="iphone-galaxyh" class="juimage" />…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 135, Column 551: end tag for "img" omitted, but OMITTAG NO was specified
    …0" height="180" alt="iphone-galaxyh" / alt="iphone-galaxyh" class="juimage" />…

    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 135, Column 409: start tag was here
    …lagio-a-apple&amp;catid=6:tecnologia"><img  src="http://gentetuya.grupointerne…
  • Error Line 135, Column 2545: required attribute "type" not specified
    … class="sharemecompactbuttonf"><script>var fbShare = {url: "http://gentetuya.c…

    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 135, Column 2803: required attribute "type" not specified
    …//widgets.fbshare.me/files/fbshare.js"></script></div></div></div><a href="/in…

    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 142, Column 637: NET-enabling start-tag not immediately followed by null end-tag
    …gin-left: auto; margin-right: auto;" / alt="Obama2Mar01" style="display: block…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 142, Column 637: end tag for "img" omitted, but OMITTAG NO was specified
    …gin-left: auto; margin-right: auto;" / alt="Obama2Mar01" style="display: block…

    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 142, Column 426: start tag was here
    …-fanaticos&amp;catid=14:curiosidades"><img  src="http://gentetuya.grupointerne…
  • Error Line 142, Column 2942: required attribute "type" not specified
    … class="sharemecompactbuttonf"><script>var fbShare = {url: "http://gentetuya.c…

    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 142, Column 3224: required attribute "type" not specified
    …//widgets.fbshare.me/files/fbshare.js"></script></div></div></div><a href="/in…

    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 149, Column 678: NET-enabling start-tag not immediately followed by null end-tag
    …gin-left: auto; margin-right: auto;" / alt="TacoBellMar01" style="display: blo…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 149, Column 678: end tag for "img" omitted, but OMITTAG NO was specified
    …gin-left: auto; margin-right: auto;" / alt="TacoBellMar01" style="display: blo…

    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 149, Column 463: start tag was here
    …catid=3:internacionales&amp;Itemid=7"><img  src="http://gentetuya.grupointerne…
  • Error Line 149, Column 3009: required attribute "type" not specified
    … class="sharemecompactbuttonf"><script>var fbShare = {url: "http://gentetuya.c…

    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 149, Column 3317: required attribute "type" not specified
    …//widgets.fbshare.me/files/fbshare.js"></script></div></div></div><a href="/in…

    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 156, Column 616: NET-enabling start-tag not immediately followed by null end-tag
    …gin-left: auto; margin-right: auto;" / alt="FaprouasdFeb18" style="display: bl…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 156, Column 616: end tag for "img" omitted, but OMITTAG NO was specified
    …gin-left: auto; margin-right: auto;" / alt="FaprouasdFeb18" style="display: bl…

    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 156, Column 398: start tag was here
    …&amp;catid=2:nacionales&amp;Itemid=3"><img  src="http://gentetuya.grupointerne…
  • Error Line 156, Column 2801: required attribute "type" not specified
    … class="sharemecompactbuttonf"><script>var fbShare = {url: "http://gentetuya.c…

    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 156, Column 3074: required attribute "type" not specified
    …//widgets.fbshare.me/files/fbshare.js"></script></div></div></div><a href="/in…

    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 163, Column 265: "altos" is not a member of a group specified for any attribute
    …ó vestimenta para tres hombres "altos y europeos"" href="/index.php?option=com…
  • Error Line 163, Column 267: "y" is not a member of a group specified for any attribute
    …vestimenta para tres hombres "altos y europeos"" href="/index.php?option=com_c…
  • Error Line 163, Column 275: an attribute value literal can occur in an attribute specification list only after a VI delimiter
    …ta para tres hombres "altos y europeos"" href="/index.php?option=com_content&a…

    Have you forgotten the "equal" sign marking the separation between the attribute and its declared value? Typical syntax is attribute="value".

  • Error Line 163, Column 696: NET-enabling start-tag not immediately followed by null end-tag
    …gin-left: auto; margin-right: auto;" / alt="sastrePapaMar01" style="display: b…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 163, Column 696: end tag for "img" omitted, but OMITTAG NO was specified
    …gin-left: auto; margin-right: auto;" / alt="sastrePapaMar01" style="display: b…

    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 163, Column 477: start tag was here
    …catid=3:internacionales&amp;Itemid=7"><img  src="http://gentetuya.grupointerne…
  • Error Line 163, Column 3174: required attribute "type" not specified
    … class="sharemecompactbuttonf"><script>var fbShare = {url: "http://gentetuya.c…

    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 163, Column 3489: required attribute "type" not specified
    …//widgets.fbshare.me/files/fbshare.js"></script></div></div></div><a href="/in…

    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 170, Column 208: an attribute value literal can occur in an attribute specification list only after a VI delimiter
    …iv><p><a title="Un hombre fue "tragado" misteriosamente por un hoyo que se for…

    Have you forgotten the "equal" sign marking the separation between the attribute and its declared value? Typical syntax is attribute="value".

  • Error Line 170, Column 676: NET-enabling start-tag not immediately followed by null end-tag
    …gin-left: auto; margin-right: auto;" / alt="HoyoMiamiMar01" style="display: bl…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 170, Column 676: end tag for "img" omitted, but OMITTAG NO was specified
    …gin-left: auto; margin-right: auto;" / alt="HoyoMiamiMar01" style="display: bl…

    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 170, Column 459: start tag was here
    …catid=3:internacionales&amp;Itemid=7"><img  src="http://gentetuya.grupointerne…
  • Error Line 170, Column 3025: required attribute "type" not specified
    … class="sharemecompactbuttonf"><script>var fbShare = {url: "http://gentetuya.c…

    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 170, Column 3331: required attribute "type" not specified
    …//widgets.fbshare.me/files/fbshare.js"></script></div></div></div><a href="/in…

    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 177, Column 598: NET-enabling start-tag not immediately followed by null end-tag
    …gin-left: auto; margin-right: auto;" / alt="nicolasMaduroMar01" style="display…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 177, Column 598: end tag for "img" omitted, but OMITTAG NO was specified
    …gin-left: auto; margin-right: auto;" / alt="nicolasMaduroMar01" style="display…

    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 177, Column 373: start tag was here
    …vez&amp;catid=1:locales&amp;Itemid=2"><img  src="http://gentetuya.grupointerne…
  • Error Line 177, Column 2848: required attribute "type" not specified
    … class="sharemecompactbuttonf"><script>var fbShare = {url: "http://gentetuya.c…

    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 177, Column 3106: required attribute "type" not specified
    …//widgets.fbshare.me/files/fbshare.js"></script></div></div></div><a href="/in…

    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 184, Column 613: NET-enabling start-tag not immediately followed by null end-tag
    …gin-left: auto; margin-right: auto;" / alt="JalissaBaezMar01" style="display: …

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 184, Column 613: end tag for "img" omitted, but OMITTAG NO was specified
    …gin-left: auto; margin-right: auto;" / alt="JalissaBaezMar01" style="display: …

    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 184, Column 392: start tag was here
    …catid=3:internacionales&amp;Itemid=7"><img  src="http://gentetuya.grupointerne…
  • Error Line 184, Column 2847: required attribute "type" not specified
    … class="sharemecompactbuttonf"><script>var fbShare = {url: "http://gentetuya.c…

    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 184, Column 3119: required attribute "type" not specified
    …//widgets.fbshare.me/files/fbshare.js"></script></div></div></div><a href="/in…

    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 193, Column 1297: document type does not allow element "td" here
    …ock div --><!-- END MID BLOCK --><div id="insetblock" style="width:468px;"><td>

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

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

  • Warning Line 211, Column 155: cannot generate system identifier for general entity "url"
    …0cDovLzE3NC4xMzMuNjQuMjI2OjgyMTcvOw,,&url=aHR0cDovL2dlbnRldHV5YS5jb20v&ancho=3…

    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 211, Column 155: general entity "url" not defined and no default entity
    …0cDovLzE3NC4xMzMuNjQuMjI2OjgyMTcvOw,,&url=aHR0cDovL2dlbnRldHV5YS5jb20v&ancho=3…

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

  • Warning Line 211, Column 158: reference not terminated by REFC delimiter
    …ovLzE3NC4xMzMuNjQuMjI2OjgyMTcvOw,,&url=aHR0cDovL2dlbnRldHV5YS5jb20v&ancho=330&…

    If you meant to include an entity that starts with "&", then you should terminate it 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 211, Column 158: reference to external entity in attribute value
    …ovLzE3NC4xMzMuNjQuMjI2OjgyMTcvOw,,&url=aHR0cDovL2dlbnRldHV5YS5jb20v&ancho=330&…

    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 211, Column 158: reference to entity "url" for which no system identifier could be generated
    …ovLzE3NC4xMzMuNjQuMjI2OjgyMTcvOw,,&url=aHR0cDovL2dlbnRldHV5YS5jb20v&ancho=330&…

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

  • Info Line 211, Column 154: entity was defined here
    …R0cDovLzE3NC4xMzMuNjQuMjI2OjgyMTcvOw,,&url=aHR0cDovL2dlbnRldHV5YS5jb20v&ancho=…
  • Warning Line 211, Column 188: cannot generate system identifier for general entity "ancho"
    …Ow,,&url=aHR0cDovL2dlbnRldHV5YS5jb20v&ancho=330&stream=0&logo=L21vZHVsZXMvbW9k…

    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 211, Column 188: general entity "ancho" not defined and no default entity
    …Ow,,&url=aHR0cDovL2dlbnRldHV5YS5jb20v&ancho=330&stream=0&logo=L21vZHVsZXMvbW9k…

    This is usually a cascading error caused by 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 211, Column 193: reference not terminated by REFC delimiter
    …url=aHR0cDovL2dlbnRldHV5YS5jb20v&ancho=330&stream=0&logo=L21vZHVsZXMvbW9kX3Jhc…

    If you meant to include an entity that starts with "&", then you should terminate it 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 211, Column 193: reference to external entity in attribute value
    …url=aHR0cDovL2dlbnRldHV5YS5jb20v&ancho=330&stream=0&logo=L21vZHVsZXMvbW9kX3Jhc…

    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 211, Column 193: reference to entity "ancho" for which no system identifier could be generated
    …url=aHR0cDovL2dlbnRldHV5YS5jb20v&ancho=330&stream=0&logo=L21vZHVsZXMvbW9kX3Jhc…

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

  • Info Line 211, Column 187: entity was defined here
    …vOw,,&url=aHR0cDovL2dlbnRldHV5YS5jb20v&ancho=330&stream=0&logo=L21vZHVsZXMvbW9…
  • Warning Line 211, Column 198: cannot generate system identifier for general entity "stream"
    …HR0cDovL2dlbnRldHV5YS5jb20v&ancho=330&stream=0&logo=L21vZHVsZXMvbW9kX3Jhcl9yYW…

    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 211, Column 198: general entity "stream" not defined and no default entity
    …HR0cDovL2dlbnRldHV5YS5jb20v&ancho=330&stream=0&logo=L21vZHVsZXMvbW9kX3Jhcl9yYW…

    This is usually a cascading error caused by 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 211, Column 204: reference not terminated by REFC delimiter
    …vL2dlbnRldHV5YS5jb20v&ancho=330&stream=0&logo=L21vZHVsZXMvbW9kX3Jhcl9yYWRpby90…

    If you meant to include an entity that starts with "&", then you should terminate it 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 211, Column 204: reference to external entity in attribute value
    …vL2dlbnRldHV5YS5jb20v&ancho=330&stream=0&logo=L21vZHVsZXMvbW9kX3Jhcl9yYWRpby90…

    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 211, Column 204: reference to entity "stream" for which no system identifier could be generated
    …vL2dlbnRldHV5YS5jb20v&ancho=330&stream=0&logo=L21vZHVsZXMvbW9kX3Jhcl9yYWRpby90…

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

  • Info Line 211, Column 197: entity was defined here
    …aHR0cDovL2dlbnRldHV5YS5jb20v&ancho=330&stream=0&logo=L21vZHVsZXMvbW9kX3Jhcl9yY…
  • Warning Line 211, Column 207: cannot generate system identifier for general entity "logo"
    …dlbnRldHV5YS5jb20v&ancho=330&stream=0&logo=L21vZHVsZXMvbW9kX3Jhcl9yYWRpby90bXB…

    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 211, Column 207: general entity "logo" not defined and no default entity
    …dlbnRldHV5YS5jb20v&ancho=330&stream=0&logo=L21vZHVsZXMvbW9kX3Jhcl9yYWRpby90bXB…

    This is usually a cascading error caused by 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 211, Column 211: reference not terminated by REFC delimiter
    …RldHV5YS5jb20v&ancho=330&stream=0&logo=L21vZHVsZXMvbW9kX3Jhcl9yYWRpby90bXBsL2l…

    If you meant to include an entity that starts with "&", then you should terminate it 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 211, Column 211: reference to external entity in attribute value
    …RldHV5YS5jb20v&ancho=330&stream=0&logo=L21vZHVsZXMvbW9kX3Jhcl9yYWRpby90bXBsL2l…

    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 211, Column 211: reference to entity "logo" for which no system identifier could be generated
    …RldHV5YS5jb20v&ancho=330&stream=0&logo=L21vZHVsZXMvbW9kX3Jhcl9yYWRpby90bXBsL2l…

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

  • Info Line 211, Column 206: entity was defined here
    …2dlbnRldHV5YS5jb20v&ancho=330&stream=0&logo=L21vZHVsZXMvbW9kX3Jhcl9yYWRpby90bX…
  • Warning Line 211, Column 273: cannot generate system identifier for general entity "alt"
    …yYWRpby90bXBsL2ltYWdlbmVzL2xvZ28uanBn&alt=RXhpdG9zIGRlIHRvZG9zIGxvcyB0aWVtcG9z…

    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 211, Column 273: general entity "alt" not defined and no default entity
    …yYWRpby90bXBsL2ltYWdlbmVzL2xvZ28uanBn&alt=RXhpdG9zIGRlIHRvZG9zIGxvcyB0aWVtcG9z…

    This is usually a cascading error caused by 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 211, Column 276: reference not terminated by REFC delimiter
    …Rpby90bXBsL2ltYWdlbmVzL2xvZ28uanBn&alt=RXhpdG9zIGRlIHRvZG9zIGxvcyB0aWVtcG9zLi4…

    If you meant to include an entity that starts with "&", then you should terminate it 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 211, Column 276: reference to external entity in attribute value
    …Rpby90bXBsL2ltYWdlbmVzL2xvZ28uanBn&alt=RXhpdG9zIGRlIHRvZG9zIGxvcyB0aWVtcG9zLi4…

    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 211, Column 276: reference to entity "alt" for which no system identifier could be generated
    …Rpby90bXBsL2ltYWdlbmVzL2xvZ28uanBn&alt=RXhpdG9zIGRlIHRvZG9zIGxvcyB0aWVtcG9zLi4…

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

  • Info Line 211, Column 272: entity was defined here
    …9yYWRpby90bXBsL2ltYWdlbmVzL2xvZ28uanBn&alt=RXhpdG9zIGRlIHRvZG9zIGxvcyB0aWVtcG9…
  • Warning Line 211, Column 342: cannot generate system identifier for general entity "adcliente"
    …0aWVtcG9zLi4gR2VudGVUdXlhUmFkaW8uY29t&adcliente=cHViLTA1Nzk5MTk0NTAxNDQyMjU," …

    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 211, Column 342: general entity "adcliente" not defined and no default entity
    …0aWVtcG9zLi4gR2VudGVUdXlhUmFkaW8uY29t&adcliente=cHViLTA1Nzk5MTk0NTAxNDQyMjU," …

    This is usually a cascading error caused by 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 211, Column 351: reference not terminated by REFC delimiter
    …Li4gR2VudGVUdXlhUmFkaW8uY29t&adcliente=cHViLTA1Nzk5MTk0NTAxNDQyMjU,"  target="…

    If you meant to include an entity that starts with "&", then you should terminate it 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 211, Column 351: reference to external entity in attribute value
    …Li4gR2VudGVUdXlhUmFkaW8uY29t&adcliente=cHViLTA1Nzk5MTk0NTAxNDQyMjU,"  target="…

    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 211, Column 351: reference to entity "adcliente" for which no system identifier could be generated
    …Li4gR2VudGVUdXlhUmFkaW8uY29t&adcliente=cHViLTA1Nzk5MTk0NTAxNDQyMjU,"  target="…

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

  • Info Line 211, Column 341: entity was defined here
    …B0aWVtcG9zLi4gR2VudGVUdXlhUmFkaW8uY29t&adcliente=cHViLTA1Nzk5MTk0NTAxNDQyMjU,"…
  • Error Line 211, Column 406: there is no attribute "onClick"
    …NTAxNDQyMjU,"  target="popup" onClick="window.open(this.href, this.target, 'wi…

    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 211, Column 648: an attribute value must be a literal unless it contains only name characters
    …tmpl/imagenes/now.jpg" alt="GenteTuyaRadio.com" border=\"0\" /></a></div></div>

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

  • Error Line 336, Column 104: required attribute "type" not specified
    …"center"><script src="http://widgets.twimg.com/j/2/widget.js"></script><script>

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

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

  • Error Line 336, Column 121: required attribute "type" not specified
    …"center"><script src="http://widgets.twimg.com/j/2/widget.js"></script><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 389, Column 305: unclosed start-tag requires SHORTTAG YES
    …et.com" style="text-decoration: none;"<a/></div></div></div><!-- end footer --…

    The construct <foo<bar> is valid in HTML (it is an example of the rather obscure “Shorttags” feature) but its use is not recommended. In most cases, this is a typo that you will want to fix. If you really want to use shorttags, be aware that they are not well implemented by browsers.

  • Error Line 389, Column 308: document type does not allow element "a" here; missing one of "object", "span", "bdo", "applet", "iframe", "tt", "i", "b", "u", "s", "strike", "big", "small", "font", "em", "strong", "dfn", "code", "q", "samp", "kbd", "var", "cite", "abbr", "acronym", "sub", "sup", "label", "ins", "del" start-tag
    …com" style="text-decoration: none;"<a/></div></div></div><!-- end footer --></…

    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 389, Column 314: end tag for "a" omitted, but OMITTAG NO was specified
    …tyle="text-decoration: none;"<a/></div></div></div><!-- end footer --></div> <…

    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 389, Column 181: start tag was here
    …v>Copyright &copy; 2012 GenteTuya.com <a href="http://www.grupointernet.com" t…

Visitor Analysis

Daily Visitor
  • 4.083 visits

In Page Analysis