Ver peliculas para niños en idioma español gratis sin descargas. ...

pelispekes.com
  • Domain Name
    pelispekes.com
  • Favicon
  • Google Page Rank
    2
  • Alexa Rank
    #67246
  • Page Size
    40.3 KB
  • Ip Address
    108.162.199.75
  • Heading
    H1: 0, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    1 GIF, 26 JPG, 0 PNG

Website Meta Analysis

  • Title
    Peliculas para Niños
  • Meta Keyword
    peliculas para niños, pequeños, disney, animacion,
  • Meta Description
    Ver peliculas para niños en idioma español gratis sin descargas.

Technical Analysis

  • Webserver
    cloudflare-nginx
  • Ip Address
    108.162.199.75
  • Domain Age
    3 Years, 0 Months, 3 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • server: cloudflare-nginx
  • date: Wed, 04 Sep 2013 18:20:06 GMT
  • content-type: text/html; charset=UTF-8
  • connection: keep-alive
  • vary: Accept-Encoding,Cookie
  • last-modified: Wed, 04 Sep 2013 17:53:00 GMT
  • cf-ray: a8cb11d6e2205af
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Domain Name: pelispekes.com
Registrar: Name.com LLC

Expiration Date: 2013-08-18 11:43:02
Creation Date: 2010-08-18 11:43:02

Name Servers:
anna.ns.cloudflare.com
duke.ns.cloudflare.com

REGISTRANT CONTACT INFO
Whois Privacy Protection Service, Inc.
Whois Agent
PMB 368, 14150 NE 20th St - F1
Bellevue
WA
98007
US
Phone: +51.14252740657
Fax: +51.14259744730
Email Address: email

ADMINISTRATIVE CONTACT INFO
Whois Privacy Protection Service, Inc.
Whois Agent
PMB 368, 14150 NE 20th St - F1
Bellevue
WA
98007
US
Phone: +51.14252740657
Fax: +51.14259744730
Email Address: email

TECHNICAL CONTACT INFO
Whois Privacy Protection Service, Inc.
Whois Agent
PMB 368, 14150 NE 20th St - F1
Bellevue
WA
98007
US
Phone: +51.14252740657
Fax: +51.14259744730
Email Address: email

BILLING CONTACT INFO
Whois Privacy Protection Service, Inc.
Whois Agent
PMB 368, 14150 NE 20th St - F1
Bellevue
WA
98007
US
Phone: +51.14252740657
Fax: +51.14259744730
Email Address: email

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 41 Errors
  • 28 Warnings
Ratio Text/Html
  • 0.6289826278680978
Message Error
  • Error Line 18, Column 16: there is no attribute "property"
    <meta property="og:description" content="Ver peliculas para niños en idioma esp…

    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 35, Column 81: required attribute "type" not specified
    …ript src="//ajax.googleapis.com/ajax/libs/jquery/1.8.2/jquery.min.js"></script>

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

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

  • Error Line 52, Column 17: there is no attribute "name"
            <a name="periodoslist"></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 52, Column 31: document type does not allow element "a" here; missing one of "ins", "del", "h1", "h2", "h3", "h4", "h5", "h6", "p", "div", "pre", "address", "fieldset" start-tag
            <a name="periodoslist"></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 57, Column 25: there is no attribute "FRAMEBORDER"
    				<IFRAME FRAMEBORDER="0" MARGINWIDTH="0" MARGINHEIGHT="0" SCROLLING="NO" WID…

    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 57, Column 41: there is no attribute "MARGINWIDTH"
    …		<IFRAME FRAMEBORDER="0" MARGINWIDTH="0" MARGINHEIGHT="0" SCROLLING="NO" WIDT…

    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 57, Column 58: there is no attribute "MARGINHEIGHT"
    …RDER="0" MARGINWIDTH="0" MARGINHEIGHT="0" SCROLLING="NO" WIDTH="728" HEIGHT="9…

    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 57, Column 72: there is no attribute "SCROLLING"
    …NWIDTH="0" MARGINHEIGHT="0" SCROLLING="NO" WIDTH="728" HEIGHT="90" SRC="http:/…

    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 57, Column 83: there is no attribute "WIDTH"
    …MARGINHEIGHT="0" SCROLLING="NO" WIDTH="728" HEIGHT="90" SRC="http://yieldmanag…

    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 57, Column 96: there is no attribute "HEIGHT"
    …"0" SCROLLING="NO" WIDTH="728" HEIGHT="90" SRC="http://yieldmanager.adbooth.ne…

    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 57, Column 105: there is no attribute "SRC"
    …LING="NO" WIDTH="728" HEIGHT="90" SRC="http://yieldmanager.adbooth.net/st?ad_t…

    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 57, Column 156: cannot generate system identifier for general entity "ad_size"
    …manager.adbooth.net/st?ad_type=iframe&ad_size=728x90&section=3636122"></IFRAME…

    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 156: general entity "ad_size" not defined and no default entity
    …manager.adbooth.net/st?ad_type=iframe&ad_size=728x90&section=3636122"></IFRAME…

    This is usually a cascading error caused by 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 163: reference not terminated by REFC delimiter
    ….adbooth.net/st?ad_type=iframe&ad_size=728x90&section=3636122"></IFRAME>      …

    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 57, Column 163: reference to external entity in attribute value
    ….adbooth.net/st?ad_type=iframe&ad_size=728x90&section=3636122"></IFRAME>      …

    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 57, Column 163: reference to entity "ad_size" for which no system identifier could be generated
    ….adbooth.net/st?ad_type=iframe&ad_size=728x90&section=3636122"></IFRAME>      …

    This is usually a cascading error caused by a an 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 155: entity was defined here
    …dmanager.adbooth.net/st?ad_type=iframe&ad_size=728x90&section=3636122"></IFRAM…
  • Warning Line 57, Column 171: cannot generate system identifier for general entity "section"
    …dbooth.net/st?ad_type=iframe&ad_size=728x90&section=3636122"></IFRAME>         

    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 171: general entity "section" not defined and no default entity
    …dbooth.net/st?ad_type=iframe&ad_size=728x90&section=3636122"></IFRAME>         

    This is usually a cascading error caused by 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 178: reference not terminated by REFC delimiter
    …dbooth.net/st?ad_type=iframe&ad_size=728x90&section=3636122"></IFRAME>         

    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 57, Column 178: reference to external entity in attribute value
    …dbooth.net/st?ad_type=iframe&ad_size=728x90&section=3636122"></IFRAME>         

    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 57, Column 178: reference to entity "section" for which no system identifier could be generated
    …dbooth.net/st?ad_type=iframe&ad_size=728x90&section=3636122"></IFRAME>         

    This is usually a cascading error caused by a an 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 170: entity was defined here
    …dbooth.net/st?ad_type=iframe&ad_size=728x90&section=3636122"></IFRAME>         
  • Error Line 57, Column 187: element "IFRAME" undefined
    …dbooth.net/st?ad_type=iframe&ad_size=728x90&section=3636122"></IFRAME>         

    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 67, Column 39: there is no attribute "placeholder"
    		<input class="txtField" placeholder="Buscar en PelisPekes" type="text" value=…

    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 67, Column 98: document type does not allow element "input" here; missing one of "ins", "del", "h1", "h2", "h3", "h4", "h5", "h6", "p", "div", "address", "fieldset" start-tag
    …Field" placeholder="Buscar en PelisPekes" type="text" value="" name="q" id="s">

    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 67, Column 99: end tag for "input" omitted, but OMITTAG NO was specified
    …Field" placeholder="Buscar en PelisPekes" type="text" value="" name="q" id="s">

    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 67, Column 3: start tag was here
    		<input class="txtField" placeholder="Buscar en PelisPekes" type="text" value=…
  • Error Line 68, Column 78: document type does not allow element "input" here; missing one of "ins", "del", "h1", "h2", "h3", "h4", "h5", "h6", "p", "div", "address", "fieldset" start-tag
    		<input type="submit" id="searchsubmit" class="btnSearch" name="sa" value="">

    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 68, Column 79: end tag for "input" omitted, but OMITTAG NO was specified
    		<input type="submit" id="searchsubmit" class="btnSearch" name="sa" value="">

    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 3: start tag was here
    		<input type="submit" id="searchsubmit" class="btnSearch" name="sa" value="">
  • Error Line 69, Column 8: end tag for "form" which is not finished
    	</form>

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

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

  • Warning Line 73, Column 160: reference not terminated by REFC delimiter
    ….adbooth.net/st?ad_type=iframe&ad_size=300x250&section=3636120"></IFRAME>     …

    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 73, Column 160: reference to external entity in attribute value
    ….adbooth.net/st?ad_type=iframe&ad_size=300x250&section=3636120"></IFRAME>     …

    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 73, Column 160: reference to entity "ad_size" for which no system identifier could be generated
    ….adbooth.net/st?ad_type=iframe&ad_size=300x250&section=3636120"></IFRAME>     …

    This is usually a cascading error caused by a an 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 155: entity was defined here
    …dmanager.adbooth.net/st?ad_type=iframe&ad_size=728x90&section=3636122"></IFRAM…
  • Warning Line 73, Column 176: reference not terminated by REFC delimiter
    ….net/st?ad_type=iframe&ad_size=300x250&section=3636120"></IFRAME>        </div>

    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 73, Column 176: reference to external entity in attribute value
    ….net/st?ad_type=iframe&ad_size=300x250&section=3636120"></IFRAME>        </div>

    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 73, Column 176: reference to entity "section" for which no system identifier could be generated
    ….net/st?ad_type=iframe&ad_size=300x250&section=3636120"></IFRAME>        </div>

    This is usually a cascading error caused by a an 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 170: entity was defined here
    …dbooth.net/st?ad_type=iframe&ad_size=728x90&section=3636122"></IFRAME>         
  • Error Line 73, Column 185: element "IFRAME" undefined
    ….net/st?ad_type=iframe&ad_size=300x250&section=3636120"></IFRAME>        </div>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 234, Column 21: there is no attribute "src"
            <iframe src="//www.facebook.com/plugins/likebox.php?href=https%3A%2F%2F…

    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 234, Column 304: there is no attribute "scrolling"
    …&amp;appId=451217681568688" scrolling="no" frameborder="0" style="border:none;…

    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 234, Column 321: there is no attribute "frameborder"
    …681568688" scrolling="no" frameborder="0" style="border:none; overflow:hidden;…

    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 234, Column 331: there is no attribute "style"
    … scrolling="no" frameborder="0" style="border:none; overflow:hidden; width:348…

    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 234, Column 408: there is no attribute "allowTransparency"
    …overflow:hidden; width:348px; height:258px;" allowTransparency="true"></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 234, Column 414: element "iframe" undefined
    …overflow:hidden; width:348px; height:258px;" allowTransparency="true"></iframe>

    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 241, Column 160: reference not terminated by REFC delimiter
    ….adbooth.net/st?ad_type=iframe&ad_size=300x250&section=3636120"></IFRAME>     …

    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 241, Column 160: reference to external entity in attribute value
    ….adbooth.net/st?ad_type=iframe&ad_size=300x250&section=3636120"></IFRAME>     …

    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 241, Column 160: reference to entity "ad_size" for which no system identifier could be generated
    ….adbooth.net/st?ad_type=iframe&ad_size=300x250&section=3636120"></IFRAME>     …

    This is usually a cascading error caused by a an 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 155: entity was defined here
    …dmanager.adbooth.net/st?ad_type=iframe&ad_size=728x90&section=3636122"></IFRAM…
  • Warning Line 241, Column 176: reference not terminated by REFC delimiter
    ….net/st?ad_type=iframe&ad_size=300x250&section=3636120"></IFRAME>        </div>

    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 241, Column 176: reference to external entity in attribute value
    ….net/st?ad_type=iframe&ad_size=300x250&section=3636120"></IFRAME>        </div>

    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 241, Column 176: reference to entity "section" for which no system identifier could be generated
    ….net/st?ad_type=iframe&ad_size=300x250&section=3636120"></IFRAME>        </div>

    This is usually a cascading error caused by a an 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 170: entity was defined here
    …dbooth.net/st?ad_type=iframe&ad_size=728x90&section=3636122"></IFRAME>         
  • Error Line 241, Column 185: element "IFRAME" undefined
    ….net/st?ad_type=iframe&ad_size=300x250&section=3636120"></IFRAME>        </div>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 245, Column 160: reference not terminated by REFC delimiter
    ….adbooth.net/st?ad_type=iframe&ad_size=300x250&section=3636120"></IFRAME>     …

    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 245, Column 160: reference to external entity in attribute value
    ….adbooth.net/st?ad_type=iframe&ad_size=300x250&section=3636120"></IFRAME>     …

    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 245, Column 160: reference to entity "ad_size" for which no system identifier could be generated
    ….adbooth.net/st?ad_type=iframe&ad_size=300x250&section=3636120"></IFRAME>     …

    This is usually a cascading error caused by a an 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 155: entity was defined here
    …dmanager.adbooth.net/st?ad_type=iframe&ad_size=728x90&section=3636122"></IFRAM…
  • Warning Line 245, Column 176: reference not terminated by REFC delimiter
    ….net/st?ad_type=iframe&ad_size=300x250&section=3636120"></IFRAME>        </div>

    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 245, Column 176: reference to external entity in attribute value
    ….net/st?ad_type=iframe&ad_size=300x250&section=3636120"></IFRAME>        </div>

    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 245, Column 176: reference to entity "section" for which no system identifier could be generated
    ….net/st?ad_type=iframe&ad_size=300x250&section=3636120"></IFRAME>        </div>

    This is usually a cascading error caused by a an 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 170: entity was defined here
    …dbooth.net/st?ad_type=iframe&ad_size=728x90&section=3636122"></IFRAME>         
  • Error Line 245, Column 185: element "IFRAME" undefined
    ….net/st?ad_type=iframe&ad_size=300x250&section=3636120"></IFRAME>        </div>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 255, Column 53: there is no attribute "target"
    …                  <li><span><a target="_blank" title="Series para Ni&ntilde;os…

    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 262, Column 70: there is no attribute "border"
    … <img width="145" height="199" border="0" src="http://pelispekes.com/caratula-…

    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 446, Column 196: reference not terminated by REFC delimiter
    ….adbooth.net/st?ad_type=iframe&ad_size=300x250&section=3636120"></IFRAME>     …

    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 446, Column 196: reference to external entity in attribute value
    ….adbooth.net/st?ad_type=iframe&ad_size=300x250&section=3636120"></IFRAME>     …

    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 446, Column 196: reference to entity "ad_size" for which no system identifier could be generated
    ….adbooth.net/st?ad_type=iframe&ad_size=300x250&section=3636120"></IFRAME>     …

    This is usually a cascading error caused by a an 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 155: entity was defined here
    …dmanager.adbooth.net/st?ad_type=iframe&ad_size=728x90&section=3636122"></IFRAM…
  • Warning Line 446, Column 212: reference not terminated by REFC delimiter
    …ad_type=iframe&ad_size=300x250&section=3636120"></IFRAME>                     …

    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 446, Column 212: reference to external entity in attribute value
    …ad_type=iframe&ad_size=300x250&section=3636120"></IFRAME>                     …

    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 446, Column 212: reference to entity "section" for which no system identifier could be generated
    …ad_type=iframe&ad_size=300x250&section=3636120"></IFRAME>                     …

    This is usually a cascading error caused by a an 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 170: entity was defined here
    …dbooth.net/st?ad_type=iframe&ad_size=728x90&section=3636122"></IFRAME>         
  • Error Line 446, Column 221: element "IFRAME" undefined
    …frame&ad_size=300x250&section=3636120"></IFRAME>                              …

    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 448, Column 196: reference not terminated by REFC delimiter
    ….adbooth.net/st?ad_type=iframe&ad_size=300x250&section=3636120"></IFRAME>     …

    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 448, Column 196: reference to external entity in attribute value
    ….adbooth.net/st?ad_type=iframe&ad_size=300x250&section=3636120"></IFRAME>     …

    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 448, Column 196: reference to entity "ad_size" for which no system identifier could be generated
    ….adbooth.net/st?ad_type=iframe&ad_size=300x250&section=3636120"></IFRAME>     …

    This is usually a cascading error caused by a an 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 155: entity was defined here
    …dmanager.adbooth.net/st?ad_type=iframe&ad_size=728x90&section=3636122"></IFRAM…
  • Warning Line 448, Column 212: reference not terminated by REFC delimiter
    …ad_type=iframe&ad_size=300x250&section=3636120"></IFRAME>                     …

    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 448, Column 212: reference to external entity in attribute value
    …ad_type=iframe&ad_size=300x250&section=3636120"></IFRAME>                     …

    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 448, Column 212: reference to entity "section" for which no system identifier could be generated
    …ad_type=iframe&ad_size=300x250&section=3636120"></IFRAME>                     …

    This is usually a cascading error caused by a an 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 170: entity was defined here
    …dbooth.net/st?ad_type=iframe&ad_size=728x90&section=3636122"></IFRAME>         
  • Error Line 448, Column 221: element "IFRAME" undefined
    …frame&ad_size=300x250&section=3636120"></IFRAME>                              …

    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 727, Column 62: ID "banner-modulo" already defined
                                                        <div id="banner-modulo">

    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 444, Column 62: ID "banner-modulo" first defined here
                                                        <div id="banner-modulo">
  • Warning Line 729, Column 196: reference not terminated by REFC delimiter
    ….adbooth.net/st?ad_type=iframe&ad_size=300x250&section=3636120"></IFRAME>     …

    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 729, Column 196: reference to external entity in attribute value
    ….adbooth.net/st?ad_type=iframe&ad_size=300x250&section=3636120"></IFRAME>     …

    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 729, Column 196: reference to entity "ad_size" for which no system identifier could be generated
    ….adbooth.net/st?ad_type=iframe&ad_size=300x250&section=3636120"></IFRAME>     …

    This is usually a cascading error caused by a an 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 155: entity was defined here
    …dmanager.adbooth.net/st?ad_type=iframe&ad_size=728x90&section=3636122"></IFRAM…
  • Warning Line 729, Column 212: reference not terminated by REFC delimiter
    …ad_type=iframe&ad_size=300x250&section=3636120"></IFRAME>                     …

    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 729, Column 212: reference to external entity in attribute value
    …ad_type=iframe&ad_size=300x250&section=3636120"></IFRAME>                     …

    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 729, Column 212: reference to entity "section" for which no system identifier could be generated
    …ad_type=iframe&ad_size=300x250&section=3636120"></IFRAME>                     …

    This is usually a cascading error caused by a an 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 170: entity was defined here
    …dbooth.net/st?ad_type=iframe&ad_size=728x90&section=3636122"></IFRAME>         
  • Error Line 729, Column 221: element "IFRAME" undefined
    …frame&ad_size=300x250&section=3636120"></IFRAME>                              …

    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 731, Column 196: reference not terminated by REFC delimiter
    ….adbooth.net/st?ad_type=iframe&ad_size=300x250&section=3636120"></IFRAME>     …

    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 731, Column 196: reference to external entity in attribute value
    ….adbooth.net/st?ad_type=iframe&ad_size=300x250&section=3636120"></IFRAME>     …

    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 731, Column 196: reference to entity "ad_size" for which no system identifier could be generated
    ….adbooth.net/st?ad_type=iframe&ad_size=300x250&section=3636120"></IFRAME>     …

    This is usually a cascading error caused by a an 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 155: entity was defined here
    …dmanager.adbooth.net/st?ad_type=iframe&ad_size=728x90&section=3636122"></IFRAM…
  • Warning Line 731, Column 212: reference not terminated by REFC delimiter
    …ad_type=iframe&ad_size=300x250&section=3636120"></IFRAME>                     …

    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 731, Column 212: reference to external entity in attribute value
    …ad_type=iframe&ad_size=300x250&section=3636120"></IFRAME>                     …

    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 731, Column 212: reference to entity "section" for which no system identifier could be generated
    …ad_type=iframe&ad_size=300x250&section=3636120"></IFRAME>                     …

    This is usually a cascading error caused by a an 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 170: entity was defined here
    …dbooth.net/st?ad_type=iframe&ad_size=728x90&section=3636122"></IFRAME>         
  • Error Line 731, Column 221: element "IFRAME" undefined
    …frame&ad_size=300x250&section=3636120"></IFRAME>                              …

    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 734, Column 112: there is no attribute "align"
    …                                  <div align="center" class="pagination corte">

    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 763, Column 102: document type does not allow element "img" here; missing one of "ins", "del", "h1", "h2", "h3", "h4", "h5", "h6", "p", "div", "address", "fieldset" start-tag
    …mung.us/swidget/pelispekes.gif" alt="online" width="0" height="0" border="0" />

    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 767, Column 173: character "&" is the first character of a delimiter but occurred as data
    …expression( eval( document.compatMode && document.compatMode=='CSS1Compat' ? 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 767, Column 174: character "&" is the first character of a delimiter but occurred as data
    …xpression( eval( document.compatMode && document.compatMode=='CSS1Compat' ? do…

    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 767, Column 396: character "&" is the first character of a delimiter but occurred as data
    …expression( eval( document.compatMode && document.compatMode=='CSS1Compat' ? 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 767, Column 397: character "&" is the first character of a delimiter but occurred as data
    …xpression( eval( document.compatMode && document.compatMode=='CSS1Compat' ? do…

    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 767, Column 548: character "&" is the first character of a delimiter but occurred as data
    …expression( eval( document.compatMode && document.compatMode=='CSS1Compat' ? 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 767, Column 549: character "&" is the first character of a delimiter but occurred as data
    …xpression( eval( document.compatMode && document.compatMode=='CSS1Compat' ? do…

    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 771, Column 21: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=728 HEIGH…
  • Error Line 771, Column 35: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=728 HEIGH…
  • Error Line 771, Column 50: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …MEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=728 HEIGHT=90 SRC="…
  • Error Line 771, Column 62: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=728 HEIGHT=90 SRC="http://goo.g…
  • Error Line 771, Column 71: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …H=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=728 HEIGHT=90 SRC="http://goo.gl/zGlEF">…
  • Error Line 771, Column 82: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …INHEIGHT=0 SCROLLING=NO WIDTH=728 HEIGHT=90 SRC="http://goo.gl/zGlEF"></IFRAME>
  • Error Line 771, Column 110: element "IFRAME" undefined
    …INHEIGHT=0 SCROLLING=NO WIDTH=728 HEIGHT=90 SRC="http://goo.gl/zGlEF"></IFRAME>

    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 776, Column 58: character "&" is the first character of a delimiter but occurred as data
    …="if('BackCompat'==document.compatMode&&/msie/i.test(navigator.userAgent)||/ms…

    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 776, Column 59: character "&" is the first character of a delimiter but occurred as data
    …"if('BackCompat'==document.compatMode&&/msie/i.test(navigator.userAgent)||/msi…

    This message may appear in several cases:

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

Visitor Analysis

Daily Visitor
  • 1.867 visits