Guerras Tribales es un juego online en donde cada jugador es el soberano de un pequeño pueblo con el que debe esforzarse para ganar poder y gloria. ...

guerrastribales.es
  • Domain Name
    guerrastribales.es
  • Favicon
  • Google Page Rank
    4
  • Alexa Rank
    #47102
  • Page Size
    62.9 KB
  • Ip Address
    213.239.206.103
  • Heading
    H1: 1, H2: 2, H3: 1, H4: 6, H5: 0, H6: 0
  • Images
    0 GIF, 6 JPG, 2 PNG

Website Meta Analysis

  • Title
    Guerras Tribales - El juego online
  • Meta Keyword
    juegos online, juego online, multiplayer, gratis, estrategia, Edad Media
  • Meta Description
    Guerras Tribales es un juego online en donde cada jugador es el soberano de un pequeño pueblo con el que debe esforzarse para ganar poder y gloria.

Technical Analysis

  • Webserver
    lighttpd/1.4.28
  • Ip Address
    213.239.206.103
  • Domain Age
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • x-powered-by: PHP/5.3.3-7+squeeze8
  • cache-control: no-cache
  • pragma: no-cache
  • content-encoding: gzip
  • vary: Accept-Encoding
  • content-type: text/html; charset=utf-8
  • date: Thu, 14 Feb 2013 03:38:18 GMT
  • server: lighttpd/1.4.28
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for guerrastribales.es

DNS Analysis


DNS servers
ns2.inwx.de [213.239.206.103]
ns3.inwx.de
ns.inwx.de [217.70.142.66]


DNS Records

Answer records
guerrastribales.es SOA
server: ns.inwx.de
email: hostmaster@inwx.de
serial: 2013020400
refresh: 10800
retry: 3600
expire: 604800
minimum ttl: 3600
3600s
guerrastribales.es NS  ns.inwx.de 3600s
guerrastribales.es TXT google-site-verification=kFqwTNZQvzEPZ9MoiUhBaHFOd0tCpUTpOzBhJsB8rpg 3600s
guerrastribales.es NS  ns2.inwx.de 3600s
guerrastribales.es NS  ns3.inwx.de 3600s
guerrastribales.es A 217.70.142.73 3600s

Authority records

Additional records
ns2.inwx.de A 213.239.206.103 3600s
ns.inwx.de A 217.70.142.66 3600s
ns3.inwx.de A 46.165.212.97 3600s
ns3.inwx.de 28 [16 bytes] 3600s
ns2.inwx.de 28 [16 bytes] 3600s

IP 213.239.206.103 Analysis

  • Country Code
    DE
  • Country Code3
    DEU
  • Country Name
    Germany
  • City
    N�rnberg
  • Continent Code
    EU
  • Latitude
    49.4478
  • Longitude
    11.0683
  • No whois ip data for 213.239.206.103

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 83 Errors
  • 50 Warnings
Ratio Text/Html
  • 0.2853591460667174
Message Error
  • Error Line 7, Column 32: there is no attribute "property"
    		<meta id="og_title" property="og:title" content="Guerras Tribales"/>

    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 36, Column 24: 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).

  • Warning Line 42, Column 1148: character "&" is the first character of a delimiter but occurred as data
    …e('pBarVisibility');if(sPBarVisibility&&sPBarVisibility=='hide'){_eContainer.f…

    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 42, Column 1150: cannot generate system identifier for general entity "sPBarVisibility"
    …'pBarVisibility');if(sPBarVisibility&&sPBarVisibility=='hide'){_eContainer.fin…

    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 42, Column 1150: general entity "sPBarVisibility" not defined and no default entity
    …'pBarVisibility');if(sPBarVisibility&&sPBarVisibility=='hide'){_eContainer.fin…

    This is usually a cascading error caused by 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 42, Column 1165: reference not terminated by REFC delimiter
    …');if(sPBarVisibility&&sPBarVisibility=='hide'){_eContainer.find('.pb-outer').…

    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 42, Column 1165: reference to entity "sPBarVisibility" for which no system identifier could be generated
    …');if(sPBarVisibility&&sPBarVisibility=='hide'){_eContainer.find('.pb-outer').…

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

  • Info Line 42, Column 1149: entity was defined here
    …('pBarVisibility');if(sPBarVisibility&&sPBarVisibility=='hide'){_eContainer.fi…
  • Warning Line 45, Column 150: character "&" is the first character of a delimiter but occurred as data
    …Query!=''){aKeysAndVals=sQuery.split('&');for(i=0;i<aKeysAndVals.length;++i){a…

    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 45, Column 183: character ";" not allowed in attribute specification list
    …lit('&');for(i=0;i<aKeysAndVals.length;++i){aKeyValTuple=aKeysAndVals[i].split…
  • Error Line 45, Column 183: element "aKeysAndVals.length" undefined
    …lit('&');for(i=0;i<aKeysAndVals.length;++i){aKeyValTuple=aKeysAndVals[i].split…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 46, Column 177: character ";" not allowed in attribute specification list
    …plit(';');for(var i=0;i<aPieces.length;i++){var sValue=aPieces[i];while(sValue…
  • Error Line 46, Column 177: element "aPieces.length" undefined
    …plit(';');for(var i=0;i<aPieces.length;i++){var sValue=aPieces[i];while(sValue…

    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 52, Column 63: character "<" is the first character of a delimiter but occurred as data
    var iIdx=$j.inArray(fCallback,_aObservers[sEventName]);if(iIdx<0){return false;}

    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 54, Column 476: character ")" not allowed in attribute specification list
    …X-cX)+Math.abs(pY-cY))<cfg.sensitivity){$(ob).unbind("mousemove",track);ob.hov…
  • Error Line 54, Column 476: element "cfg.sensitivity" undefined
    …X-cX)+Math.abs(pY-cY))<cfg.sensitivity){$(ob).unbind("mousemove",track);ob.hov…

    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 55, Column 1018: character "&" is the first character of a delimiter but occurred as data
    …ID:'#pb-play-pause'}};if(tagType!='UL'&&tagType!='OL'&&opts.htmlFeed===true){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 55, Column 1020: cannot generate system identifier for general entity "tagType"
    …:'#pb-play-pause'}};if(tagType!='UL'&&tagType!='OL'&&opts.htmlFeed===true){deb…

    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 55, Column 1020: general entity "tagType" not defined and no default entity
    …:'#pb-play-pause'}};if(tagType!='UL'&&tagType!='OL'&&opts.htmlFeed===true){deb…

    This is usually a cascading error caused by 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 55, Column 1027: reference not terminated by REFC delimiter
    …lay-pause'}};if(tagType!='UL'&&tagType!='OL'&&opts.htmlFeed===true){debugError…

    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 55, Column 1027: reference to entity "tagType" for which no system identifier could be generated
    …lay-pause'}};if(tagType!='UL'&&tagType!='OL'&&opts.htmlFeed===true){debugError…

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

  • Info Line 55, Column 1019: entity was defined here
    …D:'#pb-play-pause'}};if(tagType!='UL'&&tagType!='OL'&&opts.htmlFeed===true){de…
  • Warning Line 55, Column 1033: character "&" is the first character of a delimiter but occurred as data
    …use'}};if(tagType!='UL'&&tagType!='OL'&&opts.htmlFeed===true){debugError('Cann…

    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 55, Column 1035: cannot generate system identifier for general entity "opts.htmlFeed"
    …e'}};if(tagType!='UL'&&tagType!='OL'&&opts.htmlFeed===true){debugError('Cannot…

    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 55, Column 1035: general entity "opts.htmlFeed" not defined and no default entity
    …e'}};if(tagType!='UL'&&tagType!='OL'&&opts.htmlFeed===true){debugError('Cannot…

    This is usually a cascading error caused by 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 55, Column 1048: reference not terminated by REFC delimiter
    …pe!='UL'&&tagType!='OL'&&opts.htmlFeed===true){debugError('Cannot use <'+tagTy…

    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 55, Column 1048: reference to entity "opts.htmlFeed" for which no system identifier could be generated
    …pe!='UL'&&tagType!='OL'&&opts.htmlFeed===true){debugError('Cannot use <'+tagTy…

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

  • Info Line 55, Column 1034: entity was defined here
    …se'}};if(tagType!='UL'&&tagType!='OL'&&opts.htmlFeed===true){debugError('Canno…
  • Warning Line 55, Column 1080: character "<" is the first character of a delimiter but occurred as data
    …mlFeed===true){debugError('Cannot use <'+tagType.toLowerCase()+'> type of elem…

    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 55, Column 1160: character data is not allowed here
    …'> type of element for this plugin - must of type <ul> or <ol>');return false;}

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

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 55, Column 1166: document type does not allow element "ol" here; assuming missing "li" start-tag
    …'> type of element for this plugin - must of type <ul> or <ol>');return false;}
  • Error Line 55, Column 1167: character data is not allowed here
    …'> type of element for this plugin - must of type <ul> or <ol>');return false;}

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

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Warning Line 57, Column 76: character "&" is the first character of a delimiter but occurred as data
    …){if(opts.debugMode){if(window.console&&window.console.log){window.console.log…

    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 57, Column 78: cannot generate system identifier for general entity "window.console.log"
    …if(opts.debugMode){if(window.console&&window.console.log){window.console.log(o…

    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 57, Column 78: general entity "window.console.log" not defined and no default entity
    …if(opts.debugMode){if(window.console&&window.console.log){window.console.log(o…

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

  • Warning Line 57, Column 96: reference not terminated by REFC delimiter
    …pts.debugMode){if(window.console&&window.console.log){window.console.log(obj);}

    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 57, Column 96: reference to entity "window.console.log" for which no system identifier could be generated
    …pts.debugMode){if(window.console&&window.console.log){window.console.log(obj);}

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

  • Info Line 57, Column 77: entity was defined here
    …{if(opts.debugMode){if(window.console&&window.console.log){window.console.log(…
  • Error Line 59, Column 71: character "'" is not allowed in the value of attribute "id"
    …tings.dom.wrapperID).append('<div id="'+settings.dom.tickerID.replace('#','')+…

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

  • Error Line 59, Column 113: document type does not allow element "div" here; assuming missing "li" start-tag
    …ttings.dom.tickerID.replace('#','')+'"><div id="'+settings.dom.titleID.replace…
  • Error Line 59, Column 123: character "'" is not allowed in the value of attribute "id"
    ….tickerID.replace('#','')+'"><div id="'+settings.dom.titleID.replace('#','')+'…

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

  • Error Line 59, Column 199: character "'" is not allowed in the value of attribute "id"
    …+'"><span><!-- --></span></div><p id="'+settings.dom.contentID.replace('#','')…

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

  • Error Line 59, Column 256: character "'" is not allowed in the value of attribute "id"
    …entID.replace('#','')+'"></p><div id="'+settings.dom.revealID.replace('#','')+…

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

  • Warning Line 62, Column 28: character "&" is the first character of a delimiter but occurred as data
    else if(e.type=='mouseover'&&$j('#'+button).hasClass('controls')){$j('#'+button…

    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 62, Column 29: character "&" is the first character of a delimiter but occurred as data
    else if(e.type=='mouseover'&&$j('#'+button).hasClass('controls')){$j('#'+button…

    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 63, Column 28: character "&" is the first character of a delimiter but occurred as data
    else if(e.type=='mousedown'&&$j('#'+button).hasClass('controls')){$j('#'+button…

    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 63, Column 29: character "&" is the first character of a delimiter but occurred as data
    else if(e.type=='mousedown'&&$j('#'+button).hasClass('controls')){$j('#'+button…

    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 64, Column 26: character "&" is the first character of a delimiter but occurred as data
    else if(e.type=='mouseup'&&$j('#'+button).hasClass('controls')){$j('#'+button).…

    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 64, Column 27: character "&" is the first character of a delimiter but occurred as data
    else if(e.type=='mouseup'&&$j('#'+button).hasClass('controls')){$j('#'+button).…

    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 65, Column 27: character "&" is the first character of a delimiter but occurred as data
    else if(e.type=='mouseout'&&$j('#'+button).hasClass('controls')){$j('#'+button)…

    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 65, Column 28: character "&" is the first character of a delimiter but occurred as data
    else if(e.type=='mouseout'&&$j('#'+button).hasClass('controls')){$j('#'+button)…

    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 65, Column 148: character "'" is not allowed in the value of attribute "id"
    …ttings.dom.wrapperID).append('<ul id="'+settings.dom.controlsID.replace('#',''…

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

  • Error Line 65, Column 201: character "'" is not allowed in the value of attribute "id"
    …controlsID.replace('#','')+'"><li id="'+settings.dom.playPauseID.replace('#','…

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

  • Error Line 65, Column 277: character "'" is not allowed in the value of attribute "id"
    …,'')+'" class="controls"></li><li id="'+settings.dom.prevID.replace('#','')+'"…

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

  • Error Line 65, Column 348: character "'" is not allowed in the value of attribute "id"
    …,'')+'" class="controls"></li><li id="'+settings.dom.nextID.replace('#','')+'"…

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

  • Error Line 68, Column 243: character ";" not allowed in attribute specification list
    …0;for(var a=0;a<data.childNodes.length;a++){if(data.childNodes[a].nodeName=='r…
  • Error Line 68, Column 243: element "data.childNodes.length" undefined
    …0;for(var a=0;a<data.childNodes.length;a++){if(data.childNodes[a].nodeName=='r…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 69, Column 43: character ";" not allowed in attribute specification list
    …var i=0;i<xmlContent.childNodes.length;i++){if(xmlContent.childNodes[i].nodeNa…
  • Error Line 69, Column 43: element "xmlContent.childNodes.length" undefined
    …var i=0;i<xmlContent.childNodes.length;i++){if(xmlContent.childNodes[i].nodeNa…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 70, Column 43: character ";" not allowed in attribute specification list
    …var x=0;x<xmlChannel.childNodes.length;x++){if(xmlChannel.childNodes[x].nodeNa…
  • Error Line 70, Column 43: element "xmlChannel.childNodes.length" undefined
    …var x=0;x<xmlChannel.childNodes.length;x++){if(xmlChannel.childNodes[x].nodeNa…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 70, Column 190: character ";" not allowed in attribute specification list
    …r(var y=0;y<xmlItems.childNodes.length;y++){if(xmlItems.childNodes[y].nodeName…
  • Error Line 70, Column 190: element "xmlItems.childNodes.length" undefined
    …r(var y=0;y<xmlItems.childNodes.length;y++){if(xmlItems.childNodes[y].nodeName…

    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 72, Column 18: character "&" is the first character of a delimiter but occurred as data
    if((title!==false&&title!='')&&link!==false){settings.newsArr['item-'+count]={t…

    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 72, Column 20: cannot generate system identifier for general entity "title"
    if((title!==false&&title!='')&&link!==false){settings.newsArr['item-'+count]={t…

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

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

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

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

  • Error Line 72, Column 20: general entity "title" not defined and no default entity
    if((title!==false&&title!='')&&link!==false){settings.newsArr['item-'+count]={t…

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

  • Warning Line 72, Column 25: reference not terminated by REFC delimiter
    if((title!==false&&title!='')&&link!==false){settings.newsArr['item-'+count]={t…

    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 72, Column 25: reference to entity "title" for which no system identifier could be generated
    if((title!==false&&title!='')&&link!==false){settings.newsArr['item-'+count]={t…

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

  • Info Line 72, Column 19: entity was defined here
    if((title!==false&&title!='')&&link!==false){settings.newsArr['item-'+count]={t…
  • Warning Line 72, Column 30: character "&" is the first character of a delimiter but occurred as data
    if((title!==false&&title!='')&&link!==false){settings.newsArr['item-'+count]={t…

    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 72, Column 32: cannot generate system identifier for general entity "link"
    if((title!==false&&title!='')&&link!==false){settings.newsArr['item-'+count]={t…

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

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

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

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

  • Error Line 72, Column 32: general entity "link" not defined and no default entity
    if((title!==false&&title!='')&&link!==false){settings.newsArr['item-'+count]={t…

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

  • Warning Line 72, Column 36: reference not terminated by REFC delimiter
    if((title!==false&&title!='')&&link!==false){settings.newsArr['item-'+count]={t…

    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 72, Column 36: reference to entity "link" for which no system identifier could be generated
    if((title!==false&&title!='')&&link!==false){settings.newsArr['item-'+count]={t…

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

  • Info Line 72, Column 31: entity was defined here
    if((title!==false&&title!='')&&link!==false){settings.newsArr['item-'+count]={t…
  • Warning Line 73, Column 30: character "<" is the first character of a delimiter but occurred as data
    if(countSize(settings.newsArr<1)){debugError('Couldn\'t find any content from t…

    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 95, Column 284: end tag for "xmlItems.childNodes.length" omitted, but OMITTAG NO was specified
    …eOnItems:3000,fadeInSpeed:600,fadeOutSpeed:300};})(jQuery);}catch(e){}</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 70, Column 163: start tag was here
    …[x];var title,link=false;for(var y=0;y<xmlItems.childNodes.length;y++){if(xmlI…
  • Error Line 95, Column 284: end tag for "xmlChannel.childNodes.length" omitted, but OMITTAG NO was specified
    …eOnItems:3000,fadeInSpeed:600,fadeOutSpeed:300};})(jQuery);}catch(e){}</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 70, Column 14: start tag was here
    for(var x=0;x<xmlChannel.childNodes.length;x++){if(xmlChannel.childNodes[x].nod…
  • Error Line 95, Column 284: end tag for "xmlContent.childNodes.length" omitted, but OMITTAG NO was specified
    …eOnItems:3000,fadeInSpeed:600,fadeOutSpeed:300};})(jQuery);}catch(e){}</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 69, Column 14: start tag was here
    for(var i=0;i<xmlContent.childNodes.length;i++){if(xmlContent.childNodes[i].nod…
  • Error Line 95, Column 284: end tag for "data.childNodes.length" omitted, but OMITTAG NO was specified
    …eOnItems:3000,fadeInSpeed:600,fadeOutSpeed:300};})(jQuery);}catch(e){}</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 68, Column 220: start tag was here
    …s:function(data){count=0;for(var a=0;a<data.childNodes.length;a++){if(data.chi…
  • Error Line 95, Column 284: end tag for "li" omitted, but OMITTAG NO was specified
    …eOnItems:3000,fadeInSpeed:600,fadeOutSpeed:300};})(jQuery);}catch(e){}</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 59, Column 62: start tag was here
    …(){$j(settings.dom.wrapperID).append('<div id="'+settings.dom.tickerID.replace…
  • Error Line 95, Column 284: end tag for "ol" omitted, but OMITTAG NO was specified
    …eOnItems:3000,fadeInSpeed:600,fadeOutSpeed:300};})(jQuery);}catch(e){}</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 55, Column 1163: start tag was here
    …'> type of element for this plugin - must of type <ul> or <ol>');return false;}
  • Error Line 95, Column 284: end tag for "li" omitted, but OMITTAG NO was specified
    …eOnItems:3000,fadeInSpeed:600,fadeOutSpeed:300};})(jQuery);}catch(e){}</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 55, Column 1163: start tag was here
    …'> type of element for this plugin - must of type <ul> or <ol>');return false;}
  • Error Line 95, Column 284: end tag for "ul" omitted, but OMITTAG NO was specified
    …eOnItems:3000,fadeInSpeed:600,fadeOutSpeed:300};})(jQuery);}catch(e){}</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 55, Column 1155: start tag was here
    …'> type of element for this plugin - must of type <ul> or <ol>');return false;}
  • Error Line 95, Column 284: end tag for "cfg.sensitivity" omitted, but OMITTAG NO was specified
    …eOnItems:3000,fadeInSpeed:600,fadeOutSpeed:300};})(jQuery);}catch(e){}</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 54, Column 460: start tag was here
    …);if((Math.abs(pX-cX)+Math.abs(pY-cY))<cfg.sensitivity){$(ob).unbind("mousemov…
  • Error Line 95, Column 284: end tag for "aPieces.length" omitted, but OMITTAG NO was specified
    …eOnItems:3000,fadeInSpeed:600,fadeOutSpeed:300};})(jQuery);}catch(e){}</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 46, Column 162: start tag was here
    …cument.cookie.split(';');for(var i=0;i<aPieces.length;i++){var sValue=aPieces[…
  • Error Line 95, Column 284: end tag for "aKeysAndVals.length" omitted, but OMITTAG NO was specified
    …eOnItems:3000,fadeInSpeed:600,fadeOutSpeed:300};})(jQuery);}catch(e){}</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 45, Column 163: start tag was here
    …eysAndVals=sQuery.split('&');for(i=0;i<aKeysAndVals.length;++i){aKeyValTuple=a…
  • Error Line 180, Column 93: ID "pb-flag-es" already defined
    …ef="http://www.guerrastribales.es?ref=ds_portalbar_flags"><span id="pb-flag-es"

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

  • Info Line 115, Column 40: ID "pb-flag-es" first defined here
    						<div class="pb-lang-content" id="pb-flag-es"></div>
  • Error Line 229, Column 46: value of attribute "id" must be a single token
    																								<li id="pb_game_thumb pb_game_foe">

    This attribute cannot take a space-separated list of words as a value, but only one word ("token"). This may also be caused by the use of a space for the value of an attribute which does not permit it.

  • Error Line 233, Column 62: required attribute "alt" not specified
    											title="Forge Of Empires" width="558" height="106"/></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 235, Column 43: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    											<div class="pb-caption feature">

    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 241, Column 54: value of attribute "id" must be a single token
    																																<li id="pb_game_thumb pb_game_grepo">

    This attribute cannot take a space-separated list of words as a value, but only one word ("token"). This may also be caused by the use of a space for the value of an attribute which does not permit it.

  • Error Line 244, Column 54: required attribute "alt" not specified
    											title="Grepolis" width="180" height="106"/></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 246, Column 35: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    											<div class="pb-caption">

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

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

  • Error Line 252, Column 54: value of attribute "id" must be a single token
    																																<li id="pb_game_thumb pb_game_lagoonia">

    This attribute cannot take a space-separated list of words as a value, but only one word ("token"). This may also be caused by the use of a space for the value of an attribute which does not permit it.

  • Error Line 255, Column 54: required attribute "alt" not specified
    											title="Lagoonia" width="180" height="106"/></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 257, Column 35: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    											<div class="pb-caption">

    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 263, Column 54: value of attribute "id" must be a single token
    																																<li id="pb_game_thumb pb_game_west">

    This attribute cannot take a space-separated list of words as a value, but only one word ("token"). This may also be caused by the use of a space for the value of an attribute which does not permit it.

  • Error Line 266, Column 54: required attribute "alt" not specified
    											title="The West" width="180" height="106"/></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 268, Column 35: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    											<div class="pb-caption">

    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 274, Column 54: value of attribute "id" must be a single token
    																																<li id="pb_game_thumb pb_game_kartuga">

    This attribute cannot take a space-separated list of words as a value, but only one word ("token"). This may also be caused by the use of a space for the value of an attribute which does not permit it.

  • Error Line 279, Column 53: required attribute "alt" not specified
    											title="Kartuga" width="180" height="106"/></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 281, Column 35: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    											<div class="pb-caption">

    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 290, Column 60: required attribute "alt" not specified
    										title="Diversión móvil" width="180" height="106"/></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 292, Column 34: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    										<div class="pb-caption">

    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 306, Column 32: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    										   target="_blank"><p>The West - &iexcl;Seguro que eres un gran vaque…

    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 308, Column 32: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    										   target="_blank"><p>Forge of Empires - &iexcl;Supera una &eacute;po…

    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 310, Column 32: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    										   target="_blank"><p>Grepolis: &iexcl;Conquista Grecia!</p></a></li>

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

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

  • Warning Line 330, Column 585: cannot generate system identifier for general entity "mt"
    …nes.apple.com/es/app/tribal-wars/id435365767?l=da&mt=8">App iOS</a>&nbsp;&nbsp;

    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 330, Column 585: general entity "mt" not defined and no default entity
    …nes.apple.com/es/app/tribal-wars/id435365767?l=da&mt=8">App iOS</a>&nbsp;&nbsp;

    This is usually a cascading error caused by 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 330, Column 587: reference not terminated by REFC delimiter
    …nes.apple.com/es/app/tribal-wars/id435365767?l=da&mt=8">App iOS</a>&nbsp;&nbsp;

    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 330, Column 587: reference to external entity in attribute value
    …nes.apple.com/es/app/tribal-wars/id435365767?l=da&mt=8">App iOS</a>&nbsp;&nbsp;

    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 330, Column 587: reference to entity "mt" for which no system identifier could be generated
    …nes.apple.com/es/app/tribal-wars/id435365767?l=da&mt=8">App iOS</a>&nbsp;&nbsp;

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

  • Info Line 330, Column 584: entity was defined here
    …nes.apple.com/es/app/tribal-wars/id435365767?l=da&mt=8">App iOS</a>&nbsp;&nbsp;
  • Warning Line 354, Column 84: reference not terminated by REFC delimiter
    …es/app/tribal-wars/id435365767?l=da&mt=8" target="_blank"><img src="http://cdn…

    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 354, Column 84: reference to external entity in attribute value
    …es/app/tribal-wars/id435365767?l=da&mt=8" target="_blank"><img src="http://cdn…

    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 354, Column 84: reference to entity "mt" for which no system identifier could be generated
    …es/app/tribal-wars/id435365767?l=da&mt=8" target="_blank"><img src="http://cdn…

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

  • Info Line 330, Column 584: entity was defined here
    …nes.apple.com/es/app/tribal-wars/id435365767?l=da&mt=8">App iOS</a>&nbsp;&nbsp;
  • Warning Line 395, Column 55: cannot generate system identifier for general entity "t"
    …g src="http://ads.bluelithium.com/pixel?id=1570365&t=2" width="1" height="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 395, Column 55: general entity "t" not defined and no default entity
    …g src="http://ads.bluelithium.com/pixel?id=1570365&t=2" width="1" height="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 395, Column 56: reference not terminated by REFC delimiter
    …g src="http://ads.bluelithium.com/pixel?id=1570365&t=2" width="1" height="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 395, Column 56: reference to external entity in attribute value
    …g src="http://ads.bluelithium.com/pixel?id=1570365&t=2" width="1" height="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 395, Column 56: reference to entity "t" for which no system identifier could be generated
    …g src="http://ads.bluelithium.com/pixel?id=1570365&t=2" width="1" height="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 395, Column 54: entity was defined here
    …g src="http://ads.bluelithium.com/pixel?id=1570365&t=2" width="1" height="1" />
  • Error Line 395, Column 82: required attribute "alt" not specified
    …g src="http://ads.bluelithium.com/pixel?id=1570365&t=2" width="1" height="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>.

  • Warning Line 426, Column 66: character "&" is the first character of a delimiter but occurred as data
    …onkeydown="if((e=window.event||event) && e.keyCode == 13 && $('#user').val() &…

    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 426, Column 67: character "&" is the first character of a delimiter but occurred as data
    …nkeydown="if((e=window.event||event) && e.keyCode == 13 && $('#user').val() &&…

    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 426, Column 85: character "&" is the first character of a delimiter but occurred as data
    …ndow.event||event) && e.keyCode == 13 && $('#user').val() && $('#password').va…

    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 426, Column 86: character "&" is the first character of a delimiter but occurred as data
    …dow.event||event) && e.keyCode == 13 && $('#user').val() && $('#password').val…

    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 426, Column 105: character "&" is the first character of a delimiter but occurred as data
    …& e.keyCode == 13 && $('#user').val() && $('#password').val()) $('#login_butto…

    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 426, Column 106: character "&" is the first character of a delimiter but occurred as data
    … e.keyCode == 13 && $('#user').val() && $('#password').val()) $('#login_button…

    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 434, Column 48: character "&" is the first character of a delimiter but occurred as data
    …onkeydown="if((e=window.event||event) && e.keyCode == 13 && $('#user').val() &…

    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 434, Column 49: character "&" is the first character of a delimiter but occurred as data
    …nkeydown="if((e=window.event||event) && e.keyCode == 13 && $('#user').val() &&…

    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 434, Column 67: character "&" is the first character of a delimiter but occurred as data
    …ndow.event||event) && e.keyCode == 13 && $('#user').val() && $('#password').va…

    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 434, Column 68: character "&" is the first character of a delimiter but occurred as data
    …dow.event||event) && e.keyCode == 13 && $('#user').val() && $('#password').val…

    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 434, Column 87: character "&" is the first character of a delimiter but occurred as data
    …& e.keyCode == 13 && $('#user').val() && $('#password').val()) $('#login_butto…

    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 434, Column 88: character "&" is the first character of a delimiter but occurred as data
    … e.keyCode == 13 && $('#user').val() && $('#password').val()) $('#login_button…

    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 543, Column 382: there is no attribute "allowTransparency"
    …rflow:hidden; width:150px; height:21px;" allowTransparency="true"></a></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.

  • Error Line 543, Column 392: end tag for element "a" which is not open
    …rflow:hidden; width:150px; height:21px;" allowTransparency="true"></a></iframe>

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

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

  • Error Line 545, Column 93: there is no attribute "data-show-count"
    …witter-follow-button" data-show-count="false" data-lang="es">Seguir a @Guerras…

    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 545, Column 111: there is no attribute "data-lang"
    …ow-button" data-show-count="false" data-lang="es">Seguir a @GuerrasTribales</a>

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

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

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

  • Error Line 546, Column 8: required attribute "type" not specified
    <script>!function(d,s,id){var js,fjs=d.getElementsByTagName(s)[0];if(!d.getElem…

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

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

Visitor Analysis

Daily Visitor
  • 2.683 visits
Daily Visitor