Minilua - Seu mundo de curiosidades ...

minilua.com
  • Domain Name
    minilua.com
  • Favicon
  • Google Page Rank
    5
  • Alexa Rank
    #14617
  • Page Size
    80.9 KB
  • Ip Address
    66.7.203.170
  • Heading
    H1: 18, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    46 GIF, 0 JPG, 2 PNG

Website Meta Analysis

  • Title
    Minilua - Seu mundo de curiosidades
  • Meta Keyword
    minilua,curiosidades,humor,creepypasta,mindfuck,mistérios
  • Meta Description
    Minilua - Seu mundo de curiosidades

Technical Analysis

  • Webserver
    nginx
  • Ip Address
    66.7.203.170
  • Domain Age
    3 Years, 6 Months, 7 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • server: nginx
  • date: Sun, 24 Feb 2013 23:50:16 GMT
  • content-type: text/html; charset=utf-8
  • last-modified: Sun, 24 Feb 2013 23:50:07 GMT
  • connection: close
  • expires: Sun, 24 Feb 2013 23:50:26 GMT
  • cache-control: max-age=10
  • x-megacache: 1
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Registrado por: RAVE HOST INTERNET
Contato: email
WebSite: http://www.ravehost.com.br
Telefone: 0800 891 6900


Nome do dominio: MINILUA.COM


Registrado por: PrivacyProtect.org
Domain Admin ( email )
ID#10760, PO Box 16
Note - All Postal Mails Rejected, visit Privacyprotect.org
Nobby Beach
null,QLD 4218
AU
Tel. +45.36946676

Contato Administrativo:
PrivacyProtect.org
Domain Admin ( email )
ID#10760, PO Box 16
Note - All Postal Mails Rejected, visit Privacyprotect.org
Nobby Beach
null,QLD 4218
AU
Tel. +45.36946676

Contato Tecnico:
PrivacyProtect.org
Domain Admin ( email )
ID#10760, PO Box 16
Note - All Postal Mails Rejected, visit Privacyprotect.org
Nobby Beach
null,QLD 4218
AU
Tel. +45.36946676

Contato Financeiro:
PrivacyProtect.org
Domain Admin ( email )
ID#10760, PO Box 16
Note - All Postal Mails Rejected, visit Privacyprotect.org
Nobby Beach
null,QLD 4218
AU
Tel. +45.36946676

Status: LOCKED



Servidores DNS:
dns25339.dizinc.com
dns25340.dizinc.com


Criado em: 07-Aug-2009
Expira em: 07-Aug-2013

DNS Analysis


DNS servers
dns25339.dizinc.com [66.7.203.171]
dns25340.dizinc.com [66.7.203.172]

DNS Records

Answer records
minilua.com TXT v=spf1 +a +mx +ip4:66.7.203.170 ?all 14400s
minilua.com MX
preference: 0
exchange: minilua.com
14400s
minilua.com SOA
server: dns25339.dizinc.com
email: equipe@minilua.com
serial: 2012091503
refresh: 86400
retry: 7200
expire: 3600000
minimum ttl: 86400
86400s
minilua.com NS  dns25339.dizinc.com 86400s
minilua.com NS  dns25340.dizinc.com 86400s
minilua.com A 66.7.203.170 14400s

Authority records

Additional records
minilua.com A 66.7.203.170 14400s
dns25339.dizinc.com A 66.7.203.171 14400s
dns25340.dizinc.com A 66.7.203.172 14400s

IP 66.7.203.170 Analysis

  • Country Code
    US
  • Country Code3
    USA
  • Country Name
    United States
  • City
    Orlando
  • Continent Code
    32801
  • Latitude
    407
  • Longitude
    534
  • %rwhois V-1.5:0000a0:00 rwhois.dimenoc.com (by HostDime.com, Inc. v0.1)
    network:id:DIMENOC-342293
    network:ip-network:66.7.203.170/31
    network:network-name:DIMENOC-342293
    network:org-name:minilua.com
    network:street-address:440 West Kennedy Blvd Suite #1
    network:city:Orlando
    network:state:FL
    network:postal-code:32810
    network:country-code:US
    network:tech-contact:abuse@dimenoc.com
    network:updated:2013-02-24 23:39:43
    network:updated-by:network@dimenoc.com

    %ok

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 131 Errors
  • 85 Warnings
Ratio Text/Html
  • 0.6789411452426342
Message Error
  • Error Line 17, Column 65: end tag for "meta" omitted, but OMITTAG NO was specified
    		<meta http-equiv="X-UA-Compatible" content="IE=Edge,chrome=1">

    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 17, Column 3: start tag was here
    		<meta http-equiv="X-UA-Compatible" content="IE=Edge,chrome=1">
  • Error Line 22, Column 18: there is no attribute "property"
    		<meta property="og:title" content="Minilua" />

    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 83, Column 27: character ";" not allowed in attribute specification list
    for(var i=0;i<touch.length;i++){
  • Error Line 83, Column 27: element "touch.length" undefined
    for(var i=0;i<touch.length;i++){

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 85, Column 26: character "&" is the first character of a delimiter but occurred as data
    		if(touch[i]=='android' && n.indexOf('obile')==-1){continue;}

    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 85, Column 27: character "&" is the first character of a delimiter but occurred as data
    		if(touch[i]=='android' && n.indexOf('obile')==-1){continue;}

    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 99, Column 25: character "&" is the first character of a delimiter but occurred as data
    		if(document.domain==d && (!document.referrer||document.referrer.indexOf('/'+d…

    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 99, Column 26: character "&" is the first character of a delimiter but occurred as data
    		if(document.domain==d && (!document.referrer||document.referrer.indexOf('/'+d…

    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 109, Column 30: character "&" is the first character of a delimiter but occurred as data
    		if(document.domain=='m.'+d && (!document.referrer||document.referrer.indexOf(…

    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 109, Column 31: character "&" is the first character of a delimiter but occurred as data
    		if(document.domain=='m.'+d && (!document.referrer||document.referrer.indexOf(…

    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.
  • Error Line 117, Column 9: end tag for "touch.length" omitted, but OMITTAG NO was specified
    </script>    <script type="text/javascript">

    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 83, Column 14: start tag was here
    for(var i=0;i<touch.length;i++){
  • Warning Line 120, Column 23: character "&" is the first character of a delimiter but occurred as data
                if(el.alt && el.alt.indexOf('://')!=-1 && el.alt!=el.src) {

    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 120, Column 24: character "&" is the first character of a delimiter but occurred as data
                if(el.alt && el.alt.indexOf('://')!=-1 && el.alt!=el.src) {

    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 120, Column 52: character "&" is the first character of a delimiter but occurred as data
                if(el.alt && el.alt.indexOf('://')!=-1 && el.alt!=el.src) {

    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 120, Column 53: character "&" is the first character of a delimiter but occurred as data
                if(el.alt && el.alt.indexOf('://')!=-1 && el.alt!=el.src) {

    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 125, Column 34: character "&" is the first character of a delimiter but occurred as data
                    var uri = (el.alt&&el.alt.indexOf('://')!=-1)?el.alt:el.src;

    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 125, Column 36: cannot generate system identifier for general entity "el.alt.indexOf"
                    var uri = (el.alt&&el.alt.indexOf('://')!=-1)?el.alt:el.src;

    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 125, Column 36: general entity "el.alt.indexOf" not defined and no default entity
                    var uri = (el.alt&&el.alt.indexOf('://')!=-1)?el.alt:el.src;

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

  • Warning Line 125, Column 50: reference not terminated by REFC delimiter
                    var uri = (el.alt&&el.alt.indexOf('://')!=-1)?el.alt:el.src;

    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 125, Column 50: reference to entity "el.alt.indexOf" for which no system identifier could be generated
                    var uri = (el.alt&&el.alt.indexOf('://')!=-1)?el.alt:el.src;

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

  • Info Line 125, Column 35: entity was defined here
                    var uri = (el.alt&&el.alt.indexOf('://')!=-1)?el.alt:el.src;
  • Error Line 128, Column 98: document type does not allow element "a" here
    …With('<a href="'+uri+'" rel="external nofollow" target="_blank">'+suri+'</a>');

    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 226, Column 51: character "&" is the first character of a delimiter but occurred as data
    …        : typeof(expires) == 'number' && (expires = (new Date(+(new Date) + ex…

    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 226, Column 52: character "&" is the first character of a delimiter but occurred as data
    …       : typeof(expires) == 'number' && (expires = (new Date(+(new Date) + exp…

    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 229, Column 30: character "&" is the first character of a delimiter but occurred as data
                            s[i] && r.push(i + "=" + s[i]);

    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 229, Column 31: character "&" is the first character of a delimiter but occurred as data
                            s[i] && r.push(i + "=" + s[i]);

    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 230, Column 35: character "&" is the first character of a delimiter but occurred as data
                        return secure && r.push("secure"), document.cookie = r.join…

    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 230, Column 36: character "&" is the first character of a delimiter but occurred as data
                        return secure && r.push("secure"), document.cookie = r.join…

    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 237, Column 34: character "<" is the first character of a delimiter but occurred as data
                        for(var i=0;i<10;i++){

    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 248, Column 28: character "<" is the first character of a delimiter but occurred as data
    					if(r.split('/').length<=3)

    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 254, Column 40: character "&" is the first character of a delimiter but occurred as data
    							r += ((r.indexOf('?')==-1)?'?':'&')+'widget=1';

    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 264, Column 22: character "&" is the first character of a delimiter but occurred as data
    					if(document.all && !window['XMLHttpRequest'])

    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 264, Column 23: character "&" is the first character of a delimiter but occurred as data
    					if(document.all && !window['XMLHttpRequest'])

    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 270, Column 38: character "&" is the first character of a delimiter but occurred as data
    					if(u.indexOf('gateway.php')==-1 && u.charAt(u.length-1)!='/')

    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 270, Column 39: character "&" is the first character of a delimiter but occurred as data
    					if(u.indexOf('gateway.php')==-1 && u.charAt(u.length-1)!='/')

    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 280, Column 20: character "&" is the first character of a delimiter but occurred as data
    							if(t.length && t.indexOf('://')!=-1)

    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 280, Column 21: character "&" is the first character of a delimiter but occurred as data
    							if(t.length && t.indexOf('://')!=-1)

    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.
  • Error Line 282, Column 35: character ";" not allowed in attribute specification list
    									for(var i=0;i<safe.length;i++)
  • Error Line 282, Column 35: element "safe.length" undefined
    									for(var i=0;i<safe.length;i++)

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 284, Column 37: character "&" is the first character of a delimiter but occurred as data
    											if(t.indexOf(safe[i])!=-1&&t.indexOf(safe[i])<15)

    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 284, Column 39: cannot generate system identifier for general entity "t.indexOf"
    											if(t.indexOf(safe[i])!=-1&&t.indexOf(safe[i])<15)

    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 284, Column 39: general entity "t.indexOf" not defined and no default entity
    											if(t.indexOf(safe[i])!=-1&&t.indexOf(safe[i])<15)

    This is usually a cascading error caused by 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 284, Column 48: reference not terminated by REFC delimiter
    											if(t.indexOf(safe[i])!=-1&&t.indexOf(safe[i])<15)

    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 284, Column 48: reference to entity "t.indexOf" for which no system identifier could be generated
    											if(t.indexOf(safe[i])!=-1&&t.indexOf(safe[i])<15)

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

  • Info Line 284, Column 38: entity was defined here
    											if(t.indexOf(safe[i])!=-1&&t.indexOf(safe[i])<15)
  • Warning Line 284, Column 57: character "<" is the first character of a delimiter but occurred as data
    											if(t.indexOf(safe[i])!=-1&&t.indexOf(safe[i])<15)

    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 301, Column 28: character "&" is the first character of a delimiter but occurred as data
    							if(window['jQuery'] && jQuery.easing.easeOutQuad)

    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 301, Column 29: character "&" is the first character of a delimiter but occurred as data
    							if(window['jQuery'] && jQuery.easing.easeOutQuad)

    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.
  • Error Line 348, Column 11: end tag for "safe.length" omitted, but OMITTAG NO was specified
    		</script>

    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 282, Column 23: start tag was here
    									for(var i=0;i<safe.length;i++)
  • Error Line 368, Column 137: required attribute "alt" not specified
    …lua.com/wp-content/uploads/media/imagens/transp.gif" class="supra-main-logo" />

    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 372, Column 23: there is no attribute "name"
    		<div id="main" name="main">

    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 381, Column 331: required attribute "alt" not specified
    ….com/wp-content/uploads/media/imagens/transp.gif" class="topo-tray-sort" /></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 389, Column 54: value of attribute "method" cannot be "GET"; must be one of "get", "post"
    …bmit="return search(this)" method="GET" id="searchform" style="margin-bottom: …

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Error Line 389, Column 114: required attribute "action" not specified
    …this)" method="GET" id="searchform" style="margin-bottom: 0px" class="radius4">

    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 393, Column 64: there is no attribute "autocomplete"
    …"text" value="" name="q" id="q" autocomplete="on" placeholder="Pesquisar..." />

    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 393, Column 81: there is no attribute "placeholder"
    …"text" value="" name="q" id="q" autocomplete="on" placeholder="Pesquisar..." />

    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 394, Column 209: required attribute "alt" not specified
    …/imagens/transp.gif" class="search-submit-icon maincolor radius4 radiusright"/>

    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 402, Column 80: required attribute "alt" not specified
    		<img src="http://static.minilua.com/wp-content/uploads/media/fb-loader.gif" />

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

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

  • Error Line 406, Column 157: required attribute "alt" not specified
    …ploads/media/keyb-a.png" width="300" height="144" title="Atalhos de teclado" />

    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 411, Column 180: required attribute "alt" not specified
    …th="300" height="206" class="radius4" title="Receba as novidades do Minilua" />

    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 416, Column 97: there is no attribute "allowtransparency"
    …ilua.com/m/users.php" allowtransparency="true" style="height: 408px;"></iframe>

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

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

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

  • Warning Line 499, Column 490: cannot generate system identifier for general entity "t"
    …com/veja-o-iphone-abridor-de-cerveja/&t=Veja+o+iPhone+abridor+de+cerveja%21',8…

    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 499, Column 490: general entity "t" not defined and no default entity
    …com/veja-o-iphone-abridor-de-cerveja/&t=Veja+o+iPhone+abridor+de+cerveja%21',8…

    This is usually a cascading error caused by 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 499, Column 491: reference not terminated by REFC delimiter
    …om/veja-o-iphone-abridor-de-cerveja/&t=Veja+o+iPhone+abridor+de+cerveja%21',80…

    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 499, Column 491: reference to external entity in attribute value
    …om/veja-o-iphone-abridor-de-cerveja/&t=Veja+o+iPhone+abridor+de+cerveja%21',80…

    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 499, Column 491: reference to entity "t" for which no system identifier could be generated
    …om/veja-o-iphone-abridor-de-cerveja/&t=Veja+o+iPhone+abridor+de+cerveja%21',80…

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

  • Info Line 499, Column 489: entity was defined here
    ….com/veja-o-iphone-abridor-de-cerveja/&t=Veja+o+iPhone+abridor+de+cerveja%21',…
  • Error Line 499, Column 930: required attribute "alt" not specified
    …imagens/transp.gif" class="fb-icon"  /></a><a href="http://minilua.com/especia…

    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 499, Column 1202: document type does not allow element "h1" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …></span></span>			<h1 id="post-213755"><a href="http://minilua.com/veja-o-ipho…

    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 499, Column 1312: duplicate specification of attribute "rel"
    …"_blank" rel="nofollow external"  rel="bookmark" title='Veja o iPhone abridor …

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Warning Line 502, Column 455: reference not terminated by REFC delimiter
    …lua.com/imagens-doidas-internet-115/&t=As+imagens+mais+doidas+da+internet+%231…

    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 502, Column 455: reference to external entity in attribute value
    …lua.com/imagens-doidas-internet-115/&t=As+imagens+mais+doidas+da+internet+%231…

    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 502, Column 455: reference to entity "t" for which no system identifier could be generated
    …lua.com/imagens-doidas-internet-115/&t=As+imagens+mais+doidas+da+internet+%231…

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

  • Info Line 499, Column 489: entity was defined here
    ….com/veja-o-iphone-abridor-de-cerveja/&t=Veja+o+iPhone+abridor+de+cerveja%21',…
  • Error Line 502, Column 834: required attribute "alt" not specified
    …imagens/transp.gif" class="fb-icon"  /></a><a href="http://minilua.com/imagens…

    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 502, Column 1206: required attribute "alt" not specified
    …nsp.gif" class="transp-comment-icon" /></a><a href="http://minilua.com/humor/"…

    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 502, Column 1469: document type does not allow element "h1" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …></span></span>			<h1 id="post-213843"><a href="http://minilua.com/imagens-doi…

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

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

  • Warning Line 505, Column 392: reference not terminated by REFC delimiter
    …hp?u=http://minilua.com/fuck-origem/&t=Uma+%22Fucking+History%22',800,350);voi…

    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 505, Column 392: reference to external entity in attribute value
    …hp?u=http://minilua.com/fuck-origem/&t=Uma+%22Fucking+History%22',800,350);voi…

    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 505, Column 392: reference to entity "t" for which no system identifier could be generated
    …hp?u=http://minilua.com/fuck-origem/&t=Uma+%22Fucking+History%22',800,350);voi…

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

  • Info Line 499, Column 489: entity was defined here
    ….com/veja-o-iphone-abridor-de-cerveja/&t=Veja+o+iPhone+abridor+de+cerveja%21',…
  • Error Line 505, Column 757: required attribute "alt" not specified
    …imagens/transp.gif" class="fb-icon"  /></a><a href="http://minilua.com/fuck-or…

    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 505, Column 1115: required attribute "alt" not specified
    …nsp.gif" class="transp-comment-icon" /></a><a href="http://minilua.com/curiosi…

    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 505, Column 1399: document type does not allow element "h1" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …></span></span>			<h1 id="post-213533"><a href="http://minilua.com/fuck-origem…

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

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

  • Warning Line 508, Column 468: reference not terminated by REFC delimiter
    …ua.com/tv-pc-podem-estar-te-matando/&t=A+TV+e+o+PC+podem+estar+te+matando',800…

    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 508, Column 468: reference to external entity in attribute value
    …ua.com/tv-pc-podem-estar-te-matando/&t=A+TV+e+o+PC+podem+estar+te+matando',800…

    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 508, Column 468: reference to entity "t" for which no system identifier could be generated
    …ua.com/tv-pc-podem-estar-te-matando/&t=A+TV+e+o+PC+podem+estar+te+matando',800…

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

  • Info Line 499, Column 489: entity was defined here
    ….com/veja-o-iphone-abridor-de-cerveja/&t=Veja+o+iPhone+abridor+de+cerveja%21',…
  • Error Line 508, Column 842: required attribute "alt" not specified
    …imagens/transp.gif" class="fb-icon"  /></a><a href="http://minilua.com/tv-pc-p…

    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 508, Column 1215: required attribute "alt" not specified
    …nsp.gif" class="transp-comment-icon" /></a><a href="http://minilua.com/curiosi…

    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 508, Column 1499: document type does not allow element "h1" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …></span></span>			<h1 id="post-213729"><a href="http://minilua.com/tv-pc-podem…

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

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

  • Warning Line 511, Column 443: reference not terminated by REFC delimiter
    …ttp://minilua.com/costumes-epoca-61/&t=Costumes+de+uma+%E9poca+%2361',800,350)…

    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 511, Column 443: reference to external entity in attribute value
    …ttp://minilua.com/costumes-epoca-61/&t=Costumes+de+uma+%E9poca+%2361',800,350)…

    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 511, Column 443: reference to entity "t" for which no system identifier could be generated
    …ttp://minilua.com/costumes-epoca-61/&t=Costumes+de+uma+%E9poca+%2361',800,350)…

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

  • Info Line 499, Column 489: entity was defined here
    ….com/veja-o-iphone-abridor-de-cerveja/&t=Veja+o+iPhone+abridor+de+cerveja%21',…
  • Error Line 511, Column 810: required attribute "alt" not specified
    …imagens/transp.gif" class="fb-icon"  /></a><a href="http://minilua.com/costume…

    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 511, Column 1174: required attribute "alt" not specified
    …nsp.gif" class="transp-comment-icon" /></a><a href="http://minilua.com/nostalg…

    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 511, Column 1449: document type does not allow element "h1" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …></span></span>			<h1 id="post-213758"><a href="http://minilua.com/costumes-ep…

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

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

  • Warning Line 514, Column 487: reference not terminated by REFC delimiter
    …com/contos-minilua-shopping-v-final/&t=Contos+Minilua+-+O+shopping+%28parte+V%…

    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 514, Column 487: reference to external entity in attribute value
    …com/contos-minilua-shopping-v-final/&t=Contos+Minilua+-+O+shopping+%28parte+V%…

    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 514, Column 487: reference to entity "t" for which no system identifier could be generated
    …com/contos-minilua-shopping-v-final/&t=Contos+Minilua+-+O+shopping+%28parte+V%…

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

  • Info Line 499, Column 489: entity was defined here
    ….com/veja-o-iphone-abridor-de-cerveja/&t=Veja+o+iPhone+abridor+de+cerveja%21',…
  • Error Line 514, Column 874: required attribute "alt" not specified
    …imagens/transp.gif" class="fb-icon"  /></a><a href="http://minilua.com/contos-…

    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 514, Column 1252: required attribute "alt" not specified
    …nsp.gif" class="transp-comment-icon" /></a><a href="http://minilua.com/assusta…

    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 514, Column 1530: document type does not allow element "h1" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …></span></span>			<h1 id="post-213635"><a href="http://minilua.com/contos-mini…

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

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

  • Warning Line 517, Column 507: reference not terminated by REFC delimiter
    …sidades-curiosas-the-walking-dead-2/&t=%22Curiosidades+curiosas%22+sobre+The+W…

    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 517, Column 507: reference to external entity in attribute value
    …sidades-curiosas-the-walking-dead-2/&t=%22Curiosidades+curiosas%22+sobre+The+W…

    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 517, Column 507: reference to entity "t" for which no system identifier could be generated
    …sidades-curiosas-the-walking-dead-2/&t=%22Curiosidades+curiosas%22+sobre+The+W…

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

  • Info Line 499, Column 489: entity was defined here
    ….com/veja-o-iphone-abridor-de-cerveja/&t=Veja+o+iPhone+abridor+de+cerveja%21',…
  • Error Line 517, Column 904: required attribute "alt" not specified
    …imagens/transp.gif" class="fb-icon"  /></a><a href="http://minilua.com/curiosi…

    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 517, Column 1291: required attribute "alt" not specified
    …nsp.gif" class="transp-comment-icon" /></a><a href="http://minilua.com/curiosi…

    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 517, Column 1575: document type does not allow element "h1" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …></span></span>			<h1 id="post-213482"><a href="http://minilua.com/curiosidade…

    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 517, Column 2039: required attribute "alt" not specified
    …/transp.gif" style="width: 14px !important; height: 13px !important;"></a></h1>

    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 517, Column 2043: end tag for "img" omitted, but OMITTAG NO was specified
    …/transp.gif" style="width: 14px !important; height: 13px !important;"></a></h1>

    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 517, Column 1826: start tag was here
    … sobre The Walking Dead #2&nbsp;&nbsp;<img title="Este artigo obteve mais de 2…
  • Warning Line 520, Column 522: reference not terminated by REFC delimiter
    …-desmotivacionais-que-voc-j-viu-112/&t=As+melhores+placas+desmotivacionais+que…

    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 520, Column 522: reference to external entity in attribute value
    …-desmotivacionais-que-voc-j-viu-112/&t=As+melhores+placas+desmotivacionais+que…

    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 520, Column 522: reference to entity "t" for which no system identifier could be generated
    …-desmotivacionais-que-voc-j-viu-112/&t=As+melhores+placas+desmotivacionais+que…

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

  • Info Line 499, Column 489: entity was defined here
    ….com/veja-o-iphone-abridor-de-cerveja/&t=Veja+o+iPhone+abridor+de+cerveja%21',…
  • Error Line 520, Column 924: required attribute "alt" not specified
    …imagens/transp.gif" class="fb-icon"  /></a><a href="http://minilua.com/as-melh…

    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 520, Column 1324: required attribute "alt" not specified
    …nsp.gif" class="transp-comment-icon" /></a><a href="http://minilua.com/humor/"…

    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 520, Column 1587: document type does not allow element "h1" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …></span></span>			<h1 id="post-213330"><a href="http://minilua.com/as-melhores…

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

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

  • Warning Line 523, Column 479: reference not terminated by REFC delimiter
    …inilua.com/isso-sim-amizade-valiosa/&t=Isso+sim+%E9+uma+amizade+valiosa',800,3…

    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 523, Column 479: reference to external entity in attribute value
    …inilua.com/isso-sim-amizade-valiosa/&t=Isso+sim+%E9+uma+amizade+valiosa',800,3…

    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 523, Column 479: reference to entity "t" for which no system identifier could be generated
    …inilua.com/isso-sim-amizade-valiosa/&t=Isso+sim+%E9+uma+amizade+valiosa',800,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.

  • Info Line 499, Column 489: entity was defined here
    ….com/veja-o-iphone-abridor-de-cerveja/&t=Veja+o+iPhone+abridor+de+cerveja%21',…
  • Error Line 523, Column 853: required attribute "alt" not specified
    …imagens/transp.gif" class="fb-icon"  /></a><a href="http://minilua.com/isso-si…

    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 523, Column 1224: required attribute "alt" not specified
    …nsp.gif" class="transp-comment-icon" /></a><a href="http://minilua.com/curiosi…

    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 523, Column 1508: document type does not allow element "h1" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …></span></span>			<h1 id="post-213631"><a href="http://minilua.com/isso-sim-am…

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

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

  • Warning Line 526, Column 441: reference not terminated by REFC delimiter
    …lua.com/trabalhar-pode-salvar-mundo/&t=Trabalhar+menos+pode+salvar+o+mundo',80…

    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 526, Column 441: reference to external entity in attribute value
    …lua.com/trabalhar-pode-salvar-mundo/&t=Trabalhar+menos+pode+salvar+o+mundo',80…

    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 526, Column 441: reference to entity "t" for which no system identifier could be generated
    …lua.com/trabalhar-pode-salvar-mundo/&t=Trabalhar+menos+pode+salvar+o+mundo',80…

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

  • Info Line 499, Column 489: entity was defined here
    ….com/veja-o-iphone-abridor-de-cerveja/&t=Veja+o+iPhone+abridor+de+cerveja%21',…
  • Error Line 526, Column 816: required attribute "alt" not specified
    …imagens/transp.gif" class="fb-icon"  /></a><a href="http://minilua.com/trabalh…

    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 526, Column 1188: required attribute "alt" not specified
    …nsp.gif" class="transp-comment-icon" /></a><a href="http://minilua.com/curiosi…

    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 526, Column 1472: document type does not allow element "h1" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …></span></span>			<h1 id="post-213562"><a href="http://minilua.com/trabalhar-p…

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

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

  • Warning Line 529, Column 491: reference not terminated by REFC delimiter
    …nks-interessantes-para-fim-semana-3/&t=Links+interessantes+para+o+seu+fim+de+s…

    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 529, Column 491: reference to external entity in attribute value
    …nks-interessantes-para-fim-semana-3/&t=Links+interessantes+para+o+seu+fim+de+s…

    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 529, Column 491: reference to entity "t" for which no system identifier could be generated
    …nks-interessantes-para-fim-semana-3/&t=Links+interessantes+para+o+seu+fim+de+s…

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

  • Info Line 499, Column 489: entity was defined here
    ….com/veja-o-iphone-abridor-de-cerveja/&t=Veja+o+iPhone+abridor+de+cerveja%21',…
  • Error Line 529, Column 873: required attribute "alt" not specified
    …imagens/transp.gif" class="fb-icon"  /></a><a href="http://minilua.com/links-i…

    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 529, Column 1255: required attribute "alt" not specified
    …nsp.gif" class="transp-comment-icon" /></a><a href="http://minilua.com/curiosi…

    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 529, Column 1539: document type does not allow element "h1" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …></span></span>			<h1 id="post-213671"><a href="http://minilua.com/links-inter…

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

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

  • Warning Line 532, Column 465: reference not terminated by REFC delimiter
    …do-negro-de-sonic-a-fase-do-inferno/&t=O+lado+negro+de+Sonic%3A+A+Fase+do+Infe…

    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 532, Column 465: reference to external entity in attribute value
    …do-negro-de-sonic-a-fase-do-inferno/&t=O+lado+negro+de+Sonic%3A+A+Fase+do+Infe…

    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 532, Column 465: reference to entity "t" for which no system identifier could be generated
    …do-negro-de-sonic-a-fase-do-inferno/&t=O+lado+negro+de+Sonic%3A+A+Fase+do+Infe…

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

  • Info Line 499, Column 489: entity was defined here
    ….com/veja-o-iphone-abridor-de-cerveja/&t=Veja+o+iPhone+abridor+de+cerveja%21',…
  • Error Line 532, Column 847: required attribute "alt" not specified
    …imagens/transp.gif" class="fb-icon"  /></a><a href="http://minilua.com/o-lado-…

    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 532, Column 1233: required attribute "alt" not specified
    …nsp.gif" class="transp-comment-icon" /></a><a href="http://minilua.com/assusta…

    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 532, Column 1511: document type does not allow element "h1" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …></span></span>			<h1 id="post-212713"><a href="http://minilua.com/o-lado-negr…

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

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

  • Warning Line 535, Column 436: reference not terminated by REFC delimiter
    …nilua.com/eu-sei-que-voc-j-fez-isso/&t=Eu+sei+que+voc%EA+j%E1+fez+isso',800,35…

    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 535, Column 436: reference to external entity in attribute value
    …nilua.com/eu-sei-que-voc-j-fez-isso/&t=Eu+sei+que+voc%EA+j%E1+fez+isso',800,35…

    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 535, Column 436: reference to entity "t" for which no system identifier could be generated
    …nilua.com/eu-sei-que-voc-j-fez-isso/&t=Eu+sei+que+voc%EA+j%E1+fez+isso',800,35…

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

  • Info Line 499, Column 489: entity was defined here
    ….com/veja-o-iphone-abridor-de-cerveja/&t=Veja+o+iPhone+abridor+de+cerveja%21',…
  • Error Line 535, Column 809: required attribute "alt" not specified
    …imagens/transp.gif" class="fb-icon"  /></a><a href="http://minilua.com/eu-sei-…

    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 535, Column 1181: required attribute "alt" not specified
    …nsp.gif" class="transp-comment-icon" /></a><a href="http://minilua.com/humor/"…

    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 535, Column 1444: document type does not allow element "h1" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …></span></span>			<h1 id="post-213352"><a href="http://minilua.com/eu-sei-que-…

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

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

  • Warning Line 538, Column 455: reference not terminated by REFC delimiter
    …lua.com/cemiterios-inusitados-mundo/&t=Os+cemit%E9rios+mais+inusitados+do+mund…

    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 538, Column 455: reference to external entity in attribute value
    …lua.com/cemiterios-inusitados-mundo/&t=Os+cemit%E9rios+mais+inusitados+do+mund…

    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 538, Column 455: reference to entity "t" for which no system identifier could be generated
    …lua.com/cemiterios-inusitados-mundo/&t=Os+cemit%E9rios+mais+inusitados+do+mund…

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

  • Info Line 499, Column 489: entity was defined here
    ….com/veja-o-iphone-abridor-de-cerveja/&t=Veja+o+iPhone+abridor+de+cerveja%21',…
  • Error Line 538, Column 837: required attribute "alt" not specified
    …imagens/transp.gif" class="fb-icon"  /></a><a href="http://minilua.com/cemiter…

    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 538, Column 1211: required attribute "alt" not specified
    …nsp.gif" class="transp-comment-icon" /></a><a href="http://minilua.com/curiosi…

    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 538, Column 1495: document type does not allow element "h1" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …></span></span>			<h1 id="post-213284"><a href="http://minilua.com/cemiterios-…

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

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

  • Warning Line 541, Column 503: reference not terminated by REFC delimiter
    …ente-que-ainda-acha-que-montagem-13/&t=E+tem+gente+que+ainda+acha+que+%E9+mont…

    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 541, Column 503: reference to external entity in attribute value
    …ente-que-ainda-acha-que-montagem-13/&t=E+tem+gente+que+ainda+acha+que+%E9+mont…

    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 541, Column 503: reference to entity "t" for which no system identifier could be generated
    …ente-que-ainda-acha-que-montagem-13/&t=E+tem+gente+que+ainda+acha+que+%E9+mont…

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

  • Info Line 499, Column 489: entity was defined here
    ….com/veja-o-iphone-abridor-de-cerveja/&t=Veja+o+iPhone+abridor+de+cerveja%21',…
  • Error Line 541, Column 895: required attribute "alt" not specified
    …imagens/transp.gif" class="fb-icon"  /></a><a href="http://minilua.com/gente-q…

    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 541, Column 1278: required attribute "alt" not specified
    …nsp.gif" class="transp-comment-icon" /></a><a href="http://minilua.com/humor/"…

    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 541, Column 1541: document type does not allow element "h1" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …></span></span>			<h1 id="post-213517"><a href="http://minilua.com/gente-que-a…

    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 544, Column 477: required attribute "alt" not specified
    …p:150px;left:158px" class="hasvideo" /> </a><span class="float-cat"><span clas…

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

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

  • Warning Line 544, Column 653: reference not terminated by REFC delimiter
    ….com/andando-sp-parque-ibirapuera-2/&t=Andando+por+SP%3A+Parque+do+Ibirapuera+…

    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 544, Column 653: reference to external entity in attribute value
    ….com/andando-sp-parque-ibirapuera-2/&t=Andando+por+SP%3A+Parque+do+Ibirapuera+…

    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 544, Column 653: reference to entity "t" for which no system identifier could be generated
    ….com/andando-sp-parque-ibirapuera-2/&t=Andando+por+SP%3A+Parque+do+Ibirapuera+…

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

  • Info Line 499, Column 489: entity was defined here
    ….com/veja-o-iphone-abridor-de-cerveja/&t=Veja+o+iPhone+abridor+de+cerveja%21',…
  • Error Line 544, Column 1034: required attribute "alt" not specified
    …imagens/transp.gif" class="fb-icon"  /></a><a href="http://minilua.com/andando…

    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 544, Column 1409: required attribute "alt" not specified
    …nsp.gif" class="transp-comment-icon" /></a><a href="http://minilua.com/curiosi…

    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 544, Column 1693: document type does not allow element "h1" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …></span></span>			<h1 id="post-213523"><a href="http://minilua.com/andando-sp-…

    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 547, Column 457: required attribute "alt" not specified
    …p:150px;left:158px" class="hasvideo" /> </a><span class="float-cat"><span clas…

    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 547, Column 644: reference not terminated by REFC delimiter
    …ado-oficialmente-novo-playstation-4/&t=Divulgado+oficialmente+o+novo+Playstati…

    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 547, Column 644: reference to external entity in attribute value
    …ado-oficialmente-novo-playstation-4/&t=Divulgado+oficialmente+o+novo+Playstati…

    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 547, Column 644: reference to entity "t" for which no system identifier could be generated
    …ado-oficialmente-novo-playstation-4/&t=Divulgado+oficialmente+o+novo+Playstati…

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

  • Info Line 499, Column 489: entity was defined here
    ….com/veja-o-iphone-abridor-de-cerveja/&t=Veja+o+iPhone+abridor+de+cerveja%21',…
  • Error Line 547, Column 1029: required attribute "alt" not specified
    …imagens/transp.gif" class="fb-icon"  /></a><a href="http://minilua.com/divulga…

    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 547, Column 1417: required attribute "alt" not specified
    …nsp.gif" class="transp-comment-icon" /></a><a href="http://minilua.com/games/"…

    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 547, Column 1680: document type does not allow element "h1" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …></span></span>			<h1 id="post-213534"><a href="http://minilua.com/divulgado-o…

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

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

  • Warning Line 550, Column 469: reference not terminated by REFC delimiter
    …://minilua.com/queimando-no-inferno/&t=Quantas+pessoas+est%E3o+queimando+no+in…

    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 550, Column 469: reference to external entity in attribute value
    …://minilua.com/queimando-no-inferno/&t=Quantas+pessoas+est%E3o+queimando+no+in…

    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 550, Column 469: reference to entity "t" for which no system identifier could be generated
    …://minilua.com/queimando-no-inferno/&t=Quantas+pessoas+est%E3o+queimando+no+in…

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

  • Info Line 499, Column 489: entity was defined here
    ….com/veja-o-iphone-abridor-de-cerveja/&t=Veja+o+iPhone+abridor+de+cerveja%21',…
  • Error Line 550, Column 872: required attribute "alt" not specified
    …imagens/transp.gif" class="fb-icon"  /></a><a href="http://minilua.com/queiman…

    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 550, Column 1239: required attribute "alt" not specified
    …nsp.gif" class="transp-comment-icon" /></a><a href="http://minilua.com/religia…

    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 550, Column 1511: document type does not allow element "h1" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …></span></span>			<h1 id="post-213396"><a href="http://minilua.com/queimando-n…

    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 552, Column 485: required attribute "alt" not specified
    …nt/uploads/media/imagens/transp.gif" /></div></div><br/><br />&nbsp;    		</di…

    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 560, Column 29: document type does not allow element "style" here
    						<style type="text/css">

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

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

  • Error Line 595, Column 146: document type does not allow element "img" here
    …ins/wp-comment-likes/liked2.png" alt="Curtir" /> <span class="count"></span>');

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

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

  • Error Line 595, Column 167: document type does not allow element "span" here
    …ins/wp-comment-likes/liked2.png" alt="Curtir" /> <span class="count"></span>');

    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 600, Column 97: cannot generate system identifier for general entity "u"
    ….com/wp-content/plugins/wp-comment-likes/vote.php?id='+id+'&u='+Math.random());

    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 600, Column 97: general entity "u" not defined and no default entity
    ….com/wp-content/plugins/wp-comment-likes/vote.php?id='+id+'&u='+Math.random());

    This is usually a cascading error caused by 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 600, Column 98: reference not terminated by REFC delimiter
    ….com/wp-content/plugins/wp-comment-likes/vote.php?id='+id+'&u='+Math.random());

    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 600, Column 98: reference to entity "u" for which no system identifier could be generated
    ….com/wp-content/plugins/wp-comment-likes/vote.php?id='+id+'&u='+Math.random());

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

  • Info Line 600, Column 96: entity was defined here
    ….com/wp-content/plugins/wp-comment-likes/vote.php?id='+id+'&u='+Math.random());
  • Warning Line 605, Column 10: character "&" is the first character of a delimiter but occurred as data
        if(r && r.length){

    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 605, Column 11: character "&" is the first character of a delimiter but occurred as data
        if(r && r.length){

    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.
  • Error Line 618, Column 46: document type does not allow element "span" here
            $(el).html('Curtir<span class="count"></span>');

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

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

  • Error Line 621, Column 142: document type does not allow element "img" here
    …omment-likes/liked2.png" alt="Curtir" /> <span class="count">1 curtiu</span>');

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

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

  • Error Line 621, Column 163: document type does not allow element "span" here
    …omment-likes/liked2.png" alt="Curtir" /> <span class="count">1 curtiu</span>');

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

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

  • Error Line 624, Column 142: document type does not allow element "img" here
    …mment-likes/liked2.png" alt="Curtir" /> <span class="count">'+count+' curtiram…

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

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

  • Error Line 624, Column 163: document type does not allow element "span" here
    …es/liked2.png" alt="Curtir" /> <span class="count">'+count+' curtiram</span>');

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

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

  • Error Line 640, Column 192: required attribute "alt" not specified
    …s="tray-logo" title="Voltar para a inicial" onclick="location.href='../../'" />

    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 650, Column 82: required attribute "alt" not specified
    …		<img src="http://static.minilua.com/wp-content/uploads/media/fb-loader.gif"/>

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

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

  • Warning Line 658, Column 48: character "&" is the first character of a delimiter but occurred as data
                    	if(typeof oQuery!='undefined' && typeof jQuery!='undefined')

    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 658, Column 49: character "&" is the first character of a delimiter but occurred as data
                    	if(typeof oQuery!='undefined' && typeof jQuery!='undefined')

    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.
  • Error Line 692, Column 35: required attribute "type" not specified
    	              var _html = '<style> *{font-family:"Segoe UI",Tahoma;font-size:1…

    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 692, Column 35: document type does not allow element "style" here
    	              var _html = '<style> *{font-family:"Segoe UI",Tahoma;font-size:1…

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

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

  • Error Line 693, Column 26: document type does not allow element "div" here
                        '<div><img src="http://static.minilua.com/wp-content/upload…

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

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

  • Error Line 693, Column 113: required attribute "alt" not specified
    …/static.minilua.com/wp-content/uploads/media/imagens/logo-fbmail.png"/></div>'+

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

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

  • Error Line 694, Column 70: value of attribute "method" cannot be "POST"; must be one of "get", "post"
    …ype="multipart/form-data" method="POST" action="http://minilua.com/?p='+ID+'&c…

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Warning Line 694, Column 109: cannot generate system identifier for general entity "corrector"
    …t/form-data" method="POST" action="http://minilua.com/?p='+ID+'&corrector=1">';

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

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

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

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

  • Error Line 694, Column 109: general entity "corrector" not defined and no default entity
    …t/form-data" method="POST" action="http://minilua.com/?p='+ID+'&corrector=1">';

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

  • Warning Line 694, Column 118: reference not terminated by REFC delimiter
    …t/form-data" method="POST" action="http://minilua.com/?p='+ID+'&corrector=1">';

    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 694, Column 118: reference to external entity in attribute value
    …t/form-data" method="POST" action="http://minilua.com/?p='+ID+'&corrector=1">';

    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 694, Column 118: reference to entity "corrector" for which no system identifier could be generated
    …t/form-data" method="POST" action="http://minilua.com/?p='+ID+'&corrector=1">';

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

  • Info Line 694, Column 108: entity was defined here
    …t/form-data" method="POST" action="http://minilua.com/?p='+ID+'&corrector=1">';
  • Error Line 694, Column 121: document type does not allow element "form" here
    …t/form-data" method="POST" action="http://minilua.com/?p='+ID+'&corrector=1">';

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

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

  • Error Line 696, Column 66: required attribute "rows" not specified
    …          _html += '<p><textarea name="message" id="message"></textarea></p>'+ 

    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 696, Column 66: required attribute "cols" not specified
    …          _html += '<p><textarea name="message" id="message"></textarea></p>'+ 

    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 709, Column 160: document type does not allow element "link" here
    …ua.com/wp-content/themes/supra-2013/style-mobile.043.css" type="text/css" />');

    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 715, Column 79: character "&" is the first character of a delimiter but occurred as data
    …click(function (event){if(event.target&&event.target.id=='topad')location.href…

    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 715, Column 81: cannot generate system identifier for general entity "event.target.id"
    …ick(function (event){if(event.target&&event.target.id=='topad')location.href="…

    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 715, Column 81: general entity "event.target.id" not defined and no default entity
    …ick(function (event){if(event.target&&event.target.id=='topad')location.href="…

    This is usually a cascading error caused by 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 715, Column 96: reference not terminated by REFC delimiter
    …vent){if(event.target&&event.target.id=='topad')location.href="http://minilua.…

    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 715, Column 96: reference to entity "event.target.id" for which no system identifier could be generated
    …vent){if(event.target&&event.target.id=='topad')location.href="http://minilua.…

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

  • Info Line 715, Column 80: entity was defined here
    …lick(function (event){if(event.target&&event.target.id=='topad')location.href=…
  • Warning Line 724, Column 92: character "&" is the first character of a delimiter but occurred as data
    … (){if($(this).prev().html().replace(/&[A-Za-z0-9]{1,7};/g, '').replace(/<[^>]…

    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 724, Column 127: character "<" is the first character of a delimiter but occurred as data
    …e(/&[A-Za-z0-9]{1,7};/g, '').replace(/<[^>]*>/g, '').match(/[a-z]/)){$(this).b…

    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.
  • Error Line 724, Column 176: document type does not allow element "p" here
    …'').replace(/<[^>]*>/g, '').match(/[a-z]/)){$(this).before('<p>&nbsp;</p>')}});

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

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

  • Error Line 793, Column 7: document type does not allow element "head" here
    	<head>

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

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

  • Error Line 796, Column 8: 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.

Visitor Analysis

Daily Visitor
  • 15.633 visits
Daily Visitor