Home Lista Seriale online Filme Artistice Filme 2013 Filme 2012 Filme 2011 Filme 2010 Filme Asiatice Comedie Actiune Drama Animatie Horror Romantic Istorice SF Thriller Crima Razboi Documentar Western Biografic Cereri Social (membri) ...

filmesubtitrate.info
  • Domain Name
    filmesubtitrate.info
  • Favicon
  • Google Page Rank
    3
  • Alexa Rank
    #27173
  • Page Size
    100.6 KB
  • Ip Address
    108.162.203.194
  • Heading
    H1: 0, H2: 24, H3: 13, H4: 0, H5: 0, H6: 0
  • Images
    0 GIF, 37 JPG, 5 PNG

Website Meta Analysis

  • Title
    Seriale Online Gratis Subtitrate - Filme Online
  • Meta Keyword
  • Meta Description
    Home Lista Seriale online Filme Artistice Filme 2013 Filme 2012 Filme 2011 Filme 2010 Filme Asiatice Comedie Actiune Drama Animatie Horror Romantic Istorice SF Thriller Crima Razboi Documentar Western Biografic Cereri Social (membri) Stiri ...

Technical Analysis

  • Webserver
    cloudflare-nginx
  • Ip Address
    108.162.203.194
  • Domain Age
    3 Years, 6 Months, 27 days.
  • Javascript Library
    jquery, yui
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from filmesubtitrate.info.

HTML Analysis

  • server: cloudflare-nginx
  • date: Mon, 19 Aug 2013 06:15:32 GMT
  • content-type: text/html; charset=UTF-8
  • connection: keep-alive
  • vary: Accept-Encoding
  • x-powered-by: PHP/5.3.3
  • cache-control: max-age=86400
  • wp-super-cache: Served supercache file from PHP
  • expires: Tue, 20 Aug 2013 06:15:31 GMT
  • pragma: public
  • cf-ray: a04b5bace4805b5
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for filmesubtitrate.info

IP 108.162.203.194 Analysis

  • Country Code
  • Country Code3
  • Country Name
  • City
  • Continent Code
  • Latitude
  • Longitude
  • No whois ip data for 108.162.203.194

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 175 Errors
  • 33 Warnings
Ratio Text/Html
  • 0.8123762183992855
Message Error
  • Error Line 14, Column 74: end tag for "link" omitted, but OMITTAG NO was specified
    <link rel="shortcut icon" href="/wp-content/uploads/2012/01/favicon.ico">

    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 14, Column 1: start tag was here
    <link rel="shortcut icon" href="/wp-content/uploads/2012/01/favicon.ico">
  • Error Line 38, Column 17: there is no attribute "property"
    	<meta property="og:type" content="blog" />

    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 80, Column 169: document type does not allow element "style" here
    …document.write('<style type="text/css">.tabber{display:none;}</style>');</scri…

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

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

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

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

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

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

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

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

  • Warning Line 120, Column 57: cannot generate system identifier for general entity "appId"
      js.src = "//connect.facebook.net/en_US/all.js#xfbml=1&appId=153496634804835";

    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 120, Column 57: general entity "appId" not defined and no default entity
      js.src = "//connect.facebook.net/en_US/all.js#xfbml=1&appId=153496634804835";

    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 120, Column 62: reference not terminated by REFC delimiter
      js.src = "//connect.facebook.net/en_US/all.js#xfbml=1&appId=153496634804835";

    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 120, Column 62: reference to entity "appId" for which no system identifier could be generated
      js.src = "//connect.facebook.net/en_US/all.js#xfbml=1&appId=153496634804835";

    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 120, Column 56: entity was defined here
      js.src = "//connect.facebook.net/en_US/all.js#xfbml=1&appId=153496634804835";
  • Error Line 323, Column 236: required attribute "alt" not specified
    … src="http://www.seriale.filmesubtitrate.info/wp-content/uploads/18.png" /></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 412, Column 15: ID "closehref" already defined
    					<div id="closehref" onclick="demoDisplay4()" class="close"><a href="#">Clo…

    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 348, Column 15: ID "closehref" first defined here
    					<div id="closehref" onclick="demoDisplay2()" class="close"><a href="#">Clo…
  • Error Line 418, Column 4: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    <li><a class="axcoto-register-modal" href="http://www.seriale.filmesubtitrate.i…

    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 418, Column 133: end tag for "br" omitted, but OMITTAG NO was specified
    ….seriale.filmesubtitrate.info/login.html?action=register">Register</a></li><br>

    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 418, Column 129: start tag was here
    ….seriale.filmesubtitrate.info/login.html?action=register">Register</a></li><br>
  • Warning Line 439, Column 77: cannot generate system identifier for general entity "redirect"
    …trate.info/wp-login.php?loginGoogle=1&redirect=http://www.seriale.filmesubtitr…

    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 439, Column 77: general entity "redirect" not defined and no default entity
    …trate.info/wp-login.php?loginGoogle=1&redirect=http://www.seriale.filmesubtitr…

    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 439, Column 85: reference not terminated by REFC delimiter
    …fo/wp-login.php?loginGoogle=1&redirect=http://www.seriale.filmesubtitrate.info…

    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 439, Column 85: reference to external entity in attribute value
    …fo/wp-login.php?loginGoogle=1&redirect=http://www.seriale.filmesubtitrate.info…

    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 439, Column 85: reference to entity "redirect" for which no system identifier could be generated
    …fo/wp-login.php?loginGoogle=1&redirect=http://www.seriale.filmesubtitrate.info…

    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 439, Column 76: entity was defined here
    …itrate.info/wp-login.php?loginGoogle=1&redirect=http://www.seriale.filmesubtit…
  • Warning Line 439, Column 230: reference not terminated by REFC delimiter
    …fo/wp-login.php?loginGoogle=1&redirect='+window.location.href; return false;">…

    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 439, Column 230: reference to external entity in attribute value
    …fo/wp-login.php?loginGoogle=1&redirect='+window.location.href; return false;">…

    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 439, Column 230: reference to entity "redirect" for which no system identifier could be generated
    …fo/wp-login.php?loginGoogle=1&redirect='+window.location.href; return false;">…

    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 439, Column 76: entity was defined here
    …itrate.info/wp-login.php?loginGoogle=1&redirect=http://www.seriale.filmesubtit…
  • Error Line 439, Column 381: required attribute "alt" not specified
    …titrate.info/wp-content/plugins/social-connect/media/img/google_32.png" /> </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 637, Column 99: there is no attribute "autocomplete"
    …ion="http://www.seriale.filmesubtitrate.info/" method="get" autocomplete="off">

    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 639, Column 194: end tag for "input" omitted, but OMITTAG NO was specified
    …his.value = '';}" onblur="if (this.value == '') {this.value = 'cauta filme';}">

    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 639, Column 1: start tag was here
    <input id="s" class="cautas" type="text" name="s" value="cauta filme" onfocus="…
  • Error Line 640, Column 60: end tag for "input" omitted, but OMITTAG NO was specified
    <input id="searchsubmit" type="submit" value="cauta filme">

    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 640, Column 1: start tag was here
    <input id="searchsubmit" type="submit" value="cauta filme">
  • Error Line 702, Column 466: there is no attribute "allowTransparency"
    …low:hidden; width:292px; height:62px;" allowTransparency="true"></iframe></div>

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

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

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

  • Error Line 704, Column 132: there is no attribute "FRAMEBORDER"
    …lass="textwidget"><IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING…

    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 704, Column 132: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …lass="textwidget"><IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING…
  • Error Line 704, Column 146: there is no attribute "MARGINWIDTH"
    …et"><IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=300 …

    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 704, Column 146: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …et"><IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=300 …
  • Error Line 704, Column 161: there is no attribute "MARGINHEIGHT"
    …MEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=300 HEIGHT=250 SRC=…

    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 704, Column 161: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …MEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=300 HEIGHT=250 SRC=…
  • Error Line 704, Column 173: there is no attribute "SCROLLING"
    …ARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=300 HEIGHT=250 SRC="http://tag.…

    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 704, Column 173: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=300 HEIGHT=250 SRC="http://tag.…
  • Error Line 704, Column 182: there is no attribute "WIDTH"
    …H=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=300 HEIGHT=250 SRC="http://tag.tlvmedia.…

    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 704, Column 182: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …H=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=300 HEIGHT=250 SRC="http://tag.tlvmedia.…
  • Error Line 704, Column 193: there is no attribute "HEIGHT"
    …EIGHT=0 SCROLLING=NO WIDTH=300 HEIGHT=250 SRC="http://tag.tlvmedia.com/?id=102…

    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 704, Column 193: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …EIGHT=0 SCROLLING=NO WIDTH=300 HEIGHT=250 SRC="http://tag.tlvmedia.com/?id=102…
  • Error Line 704, Column 201: there is no attribute "SRC"
    …SCROLLING=NO WIDTH=300 HEIGHT=250 SRC="http://tag.tlvmedia.com/?id=102252_1425…

    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 704, Column 244: cannot generate system identifier for general entity "ad_type"
    …://tag.tlvmedia.com/?id=102252_142575&ad_type=banner&ad_size=300x250"></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 704, Column 244: general entity "ad_type" not defined and no default entity
    …://tag.tlvmedia.com/?id=102252_142575&ad_type=banner&ad_size=300x250"></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 704, Column 251: reference not terminated by REFC delimiter
    ….tlvmedia.com/?id=102252_142575&ad_type=banner&ad_size=300x250"></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 704, Column 251: reference to external entity in attribute value
    ….tlvmedia.com/?id=102252_142575&ad_type=banner&ad_size=300x250"></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 704, Column 251: reference to entity "ad_type" for which no system identifier could be generated
    ….tlvmedia.com/?id=102252_142575&ad_type=banner&ad_size=300x250"></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 704, Column 243: entity was defined here
    …p://tag.tlvmedia.com/?id=102252_142575&ad_type=banner&ad_size=300x250"></IFRAM…
  • Warning Line 704, Column 259: cannot generate system identifier for general entity "ad_size"
    ….tlvmedia.com/?id=102252_142575&ad_type=banner&ad_size=300x250"></IFRAME></div>

    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 704, Column 259: general entity "ad_size" not defined and no default entity
    ….tlvmedia.com/?id=102252_142575&ad_type=banner&ad_size=300x250"></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.

  • Warning Line 704, Column 266: reference not terminated by REFC delimiter
    ….tlvmedia.com/?id=102252_142575&ad_type=banner&ad_size=300x250"></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 704, Column 266: reference to external entity in attribute value
    ….tlvmedia.com/?id=102252_142575&ad_type=banner&ad_size=300x250"></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 704, Column 266: reference to entity "ad_size" for which no system identifier could be generated
    ….tlvmedia.com/?id=102252_142575&ad_type=banner&ad_size=300x250"></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 704, Column 258: entity was defined here
    ….tlvmedia.com/?id=102252_142575&ad_type=banner&ad_size=300x250"></IFRAME></div>
  • Error Line 704, Column 275: element "IFRAME" undefined
    ….tlvmedia.com/?id=102252_142575&ad_type=banner&ad_size=300x250"></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 705, Column 809: name start character invalid: only S separators and TAGC allowed here
    … Un glont la tinta (2012)" /></a></li class="catexx"><li class="catexx" ><a hr…
  • Error Line 705, Column 810: character data is not allowed here
    …Un glont la tinta (2012)" /></a></li class="catexx"><li class="catexx" ><a hre…

    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 705, Column 1349: name start character invalid: only S separators and TAGC allowed here
    …" alt="On the Road (2012)" /></a></li class="catexx"><li class="catexx" ><a hr…
  • Error Line 705, Column 1350: character data is not allowed here
    … alt="On the Road (2012)" /></a></li class="catexx"><li class="catexx" ><a hre…

    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 705, Column 1979: name start character invalid: only S separators and TAGC allowed here
    …" alt="Easy Virtue (2008)" /></a></li class="catexx"><li class="catexx" ><a hr…
  • Error Line 705, Column 1980: character data is not allowed here
    … alt="Easy Virtue (2008)" /></a></li class="catexx"><li class="catexx" ><a hre…

    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 705, Column 2627: name start character invalid: only S separators and TAGC allowed here
    …lt="Gangster Squad (2013)" /></a></li class="catexx"><li class="catexx" ><a hr…
  • Error Line 705, Column 2628: character data is not allowed here
    …t="Gangster Squad (2013)" /></a></li class="catexx"><li class="catexx" ><a hre…

    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 705, Column 3313: name start character invalid: only S separators and TAGC allowed here
    … alt="Hyde Park on Hudson" /></a></li class="catexx"><li class="catexx" ><a hr…
  • Error Line 705, Column 3314: character data is not allowed here
    …alt="Hyde Park on Hudson" /></a></li class="catexx"><li class="catexx" ><a hre…

    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 705, Column 3925: name start character invalid: only S separators and TAGC allowed here
    …view with a Hitman (2012)" /></a></li class="catexx"><li class="catexx" ><a hr…
  • Error Line 705, Column 3926: character data is not allowed here
    …iew with a Hitman (2012)" /></a></li class="catexx"><li class="catexx" ><a hre…

    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 705, Column 4607: name start character invalid: only S separators and TAGC allowed here
    …uta Film Online Subtitrat" /></a></li class="catexx"><li class="catexx" ><a hr…
  • Error Line 705, Column 4608: character data is not allowed here
    …ta Film Online Subtitrat" /></a></li class="catexx"><li class="catexx" ><a hre…

    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 705, Column 5189: name start character invalid: only S separators and TAGC allowed here
    …lt="madly madagascar 2013" /></a></li class="catexx"><li class="catexx" ><a hr…
  • Error Line 705, Column 5190: character data is not allowed here
    …t="madly madagascar 2013" /></a></li class="catexx"><li class="catexx" ><a hre…

    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 705, Column 5815: name start character invalid: only S separators and TAGC allowed here
    …The Warrior Prince (2012)" /></a></li class="catexx"><li class="catexx" ><a hr…
  • Error Line 705, Column 5816: character data is not allowed here
    …he Warrior Prince (2012)" /></a></li class="catexx"><li class="catexx" ><a hre…

    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 705, Column 6395: name start character invalid: only S separators and TAGC allowed here
    …e" alt="Possession (2002)" /></a></li class="catexx"><li class="catexx" ><a hr…
  • Error Line 705, Column 6396: character data is not allowed here
    …" alt="Possession (2002)" /></a></li class="catexx"><li class="catexx" ><a hre…

    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 705, Column 6969: name start character invalid: only S separators and TAGC allowed here
    …t="A Haunted House (2013)" /></a></li class="catexx"><li class="catexx" ><a hr…
  • Error Line 705, Column 6970: character data is not allowed here
    …="A Haunted House (2013)" /></a></li class="catexx"><li class="catexx" ><a hre…

    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 705, Column 7523: name start character invalid: only S separators and TAGC allowed here
    …" alt="Blood Money (2012)" /></a></li class="catexx"><li class="catexx" ><a hr…
  • Error Line 705, Column 7524: character data is not allowed here
    … alt="Blood Money (2012)" /></a></li class="catexx"><li class="catexx" ><a hre…

    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 705, Column 8053: name start character invalid: only S separators and TAGC allowed here
    …mage" alt="Citadel (2012)" /></a></li class="catexx"><li class="catexx" ><a hr…
  • Error Line 705, Column 8054: character data is not allowed here
    …age" alt="Citadel (2012)" /></a></li class="catexx"><li class="catexx" ><a hre…

    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 705, Column 8675: name start character invalid: only S separators and TAGC allowed here
    …-image" alt="a place 2012" /></a></li class="catexx"><li class="catexx" ><a hr…
  • Error Line 705, Column 8676: character data is not allowed here
    …image" alt="a place 2012" /></a></li class="catexx"><li class="catexx" ><a hre…

    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 705, Column 9283: name start character invalid: only S separators and TAGC allowed here
    …-image" alt="The Sessions" /></a></li class="catexx"></ul><a  href="http://www…
  • Error Line 705, Column 9284: character data is not allowed here
    …image" alt="The Sessions" /></a></li class="catexx"></ul><a  href="http://www.…

    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 706, Column 774: name start character invalid: only S separators and TAGC allowed here
    …e-diaries-season-4-poster" /></a></li class="catexx"><li class="catexx" ><a hr…
  • Error Line 706, Column 775: character data is not allowed here
    …-diaries-season-4-poster" /></a></li class="catexx"><li class="catexx" ><a hre…

    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 706, Column 1348: name start character invalid: only S separators and TAGC allowed here
    …rey&#039;s Anatomy (2005)" /></a></li class="catexx"><li class="catexx" ><a hr…
  • Error Line 706, Column 1349: character data is not allowed here
    …ey&#039;s Anatomy (2005)" /></a></li class="catexx"><li class="catexx" ><a hre…

    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 706, Column 1590: name start character invalid: only S separators and TAGC allowed here
    …isod 13 The Strong Survive</a>   </li class="catexx"><li class="catexx" ><a hr…
  • Error Line 706, Column 1591: character data is not allowed here
    …sod 13 The Strong Survive</a>   </li class="catexx"><li class="catexx" ><a hre…

    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 706, Column 2190: name start character invalid: only S separators and TAGC allowed here
    …ty and the Beast season 1" /></a></li class="catexx"><li class="catexx" ><a hr…
  • Error Line 706, Column 2191: character data is not allowed here
    …y and the Beast season 1" /></a></li class="catexx"><li class="catexx" ><a hre…

    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 706, Column 2743: name start character invalid: only S separators and TAGC allowed here
    …e" alt="Elementary (2012)" /></a></li class="catexx"><li class="catexx" ><a hr…
  • Error Line 706, Column 2744: character data is not allowed here
    …" alt="Elementary (2012)" /></a></li class="catexx"><li class="catexx" ><a hre…

    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 706, Column 3313: name start character invalid: only S separators and TAGC allowed here
    …-image" alt="Scandal 2012" /></a></li class="catexx"><li class="catexx" ><a hr…
  • Error Line 706, Column 3314: character data is not allowed here
    …image" alt="Scandal 2012" /></a></li class="catexx"><li class="catexx" ><a hre…

    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 706, Column 3939: name start character invalid: only S separators and TAGC allowed here
    …ge" alt="anger management" /></a></li class="catexx"><li class="catexx" ><a hr…
  • Error Line 706, Column 3940: character data is not allowed here
    …e" alt="anger management" /></a></li class="catexx"><li class="catexx" ><a hre…

    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 706, Column 4571: name start character invalid: only S separators and TAGC allowed here
    … and a Half Men season 10" /></a></li class="catexx"><li class="catexx" ><a hr…
  • Error Line 706, Column 4572: character data is not allowed here
    …and a Half Men season 10" /></a></li class="catexx"><li class="catexx" ><a hre…

    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 706, Column 5235: name start character invalid: only S separators and TAGC allowed here
    …ig Bang Theory (season 6)" /></a></li class="catexx"><li class="catexx" ><a hr…
  • Error Line 706, Column 5236: character data is not allowed here
    …g Bang Theory (season 6)" /></a></li class="catexx"><li class="catexx" ><a hre…

    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 706, Column 5855: name start character invalid: only S separators and TAGC allowed here
    …on-of-interest-season-one" /></a></li class="catexx"><li class="catexx" ><a hr…
  • Error Line 706, Column 5856: character data is not allowed here
    …n-of-interest-season-one" /></a></li class="catexx"><li class="catexx" ><a hre…

    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 706, Column 6357: name start character invalid: only S separators and TAGC allowed here
    …image" alt="Glee Season 4" /></a></li class="catexx"><li class="catexx" ><a hr…
  • Error Line 706, Column 6358: character data is not allowed here
    …mage" alt="Glee Season 4" /></a></li class="catexx"><li class="catexx" ><a hre…

    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 706, Column 6891: name start character invalid: only S separators and TAGC allowed here
    …age" alt="30 Rock Sezon 7" /></a></li class="catexx"><li class="catexx" ><a hr…
  • Error Line 706, Column 6892: character data is not allowed here
    …ge" alt="30 Rock Sezon 7" /></a></li class="catexx"><li class="catexx" ><a hre…

    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 706, Column 7408: name start character invalid: only S separators and TAGC allowed here
    …mage" alt="arrow season 1" /></a></li class="catexx"><li class="catexx" ><a hr…
  • Error Line 706, Column 7409: character data is not allowed here
    …age" alt="arrow season 1" /></a></li class="catexx"><li class="catexx" ><a hre…

    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 706, Column 7976: name start character invalid: only S separators and TAGC allowed here
    …lt="Supernatural season 8" /></a></li class="catexx"><li class="catexx" ><a hr…
  • Error Line 706, Column 7977: character data is not allowed here
    …t="Supernatural season 8" /></a></li class="catexx"><li class="catexx" ><a hre…

    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 706, Column 8550: name start character invalid: only S separators and TAGC allowed here
    …lt="Chicago Fire season 1" /></a></li class="catexx"></ul><a  href="http://www…
  • Error Line 706, Column 8551: character data is not allowed here
    …t="Chicago Fire season 1" /></a></li class="catexx"></ul><a  href="http://www.…

    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 707, Column 173: duplicate specification of attribute "class"
    …oi</h3><ul><li class="catexx" class = current  ><a href="http://www.seriale.fi…

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

  • Error Line 707, Column 173: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …oi</h3><ul><li class="catexx" class = current  ><a href="http://www.seriale.fi…
  • Error Line 707, Column 786: name start character invalid: only S separators and TAGC allowed here
    …"Parade&#039;s End (2012)" /></a></li class="catexx"><li class="catexx" ><a hr…
  • Error Line 707, Column 787: character data is not allowed here
    …Parade&#039;s End (2012)" /></a></li class="catexx"><li class="catexx" ><a hre…

    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 707, Column 1346: name start character invalid: only S separators and TAGC allowed here
    … alt="The Paradise (2012)" /></a></li class="catexx"><li class="catexx" ><a hr…
  • Error Line 707, Column 1347: character data is not allowed here
    …alt="The Paradise (2012)" /></a></li class="catexx"><li class="catexx" ><a hre…

    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 707, Column 1998: name start character invalid: only S separators and TAGC allowed here
    …alt="Spies of Warsaw 2012" /></a></li class="catexx"><li class="catexx" ><a hr…
  • Error Line 707, Column 1999: character data is not allowed here
    …lt="Spies of Warsaw 2012" /></a></li class="catexx"><li class="catexx" ><a hre…

    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 707, Column 2572: name start character invalid: only S separators and TAGC allowed here
    …alt="The Following (2013)" /></a></li class="catexx"><li class="catexx" ><a hr…
  • Error Line 707, Column 2573: character data is not allowed here
    …lt="The Following (2013)" /></a></li class="catexx"><li class="catexx" ><a hre…

    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 707, Column 3134: name start character invalid: only S separators and TAGC allowed here
    …" alt="Fear Itself (2008)" /></a></li class="catexx"><li class="catexx" ><a hr…
  • Error Line 707, Column 3135: character data is not allowed here
    … alt="Fear Itself (2008)" /></a></li class="catexx"><li class="catexx" ><a hre…

    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 707, Column 3696: name start character invalid: only S separators and TAGC allowed here
    …age" alt="Surface Sezon 1" /></a></li class="catexx"><li class="catexx" ><a hr…
  • Error Line 707, Column 3697: character data is not allowed here
    …ge" alt="Surface Sezon 1" /></a></li class="catexx"><li class="catexx" ><a hre…

    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 707, Column 4366: name start character invalid: only S separators and TAGC allowed here
    …lt="Eleventh Hour Sezon 1" /></a></li class="catexx"><li class="catexx" ><a hr…
  • Error Line 707, Column 4367: character data is not allowed here
    …t="Eleventh Hour Sezon 1" /></a></li class="catexx"><li class="catexx" ><a hre…

    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 707, Column 4902: name start character invalid: only S separators and TAGC allowed here
    …-image" alt="Banshee 2013" /></a></li class="catexx"><li class="catexx" ><a hr…
  • Error Line 707, Column 4903: character data is not allowed here
    …image" alt="Banshee 2013" /></a></li class="catexx"><li class="catexx" ><a hre…

    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 707, Column 5536: name start character invalid: only S separators and TAGC allowed here
    …t-image" alt="XIII (2008)" /></a></li class="catexx"><li class="catexx" ><a hr…
  • Error Line 707, Column 5537: character data is not allowed here
    …-image" alt="XIII (2008)" /></a></li class="catexx"><li class="catexx" ><a hre…

    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 707, Column 6086: name start character invalid: only S separators and TAGC allowed here
    …ge" alt="Deception (2013)" /></a></li class="catexx"></ul><a  href="http://www…
  • Error Line 707, Column 6087: character data is not allowed here
    …e" alt="Deception (2013)" /></a></li class="catexx"></ul><a  href="http://www.…

    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 708, Column 57: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
            <table class="nospnopa" width="728" cellspacing=0 cellpadding=0><tr><td>
  • Error Line 708, Column 71: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
            <table class="nospnopa" width="728" cellspacing=0 cellpadding=0><tr><td>
  • Error Line 720, Column 210: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …osition:absolute; z-index:999;" width=25 height=25 src=http://seriale.filmesub…
  • Error Line 720, Column 220: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …solute; z-index:999;" width=25 height=25 src=http://seriale.filmesubtitrate.in…
  • Error Line 720, Column 227: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    … z-index:999;" width=25 height=25 src=http://seriale.filmesubtitrate.info/wp-c…
  • Error Line 720, Column 233: NET-enabling start-tag not immediately followed by null end-tag
    …ex:999;" width=25 height=25 src=http://seriale.filmesubtitrate.info/wp-content…

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

  • Error Line 720, Column 233: required attribute "alt" not specified
    …ex:999;" width=25 height=25 src=http://seriale.filmesubtitrate.info/wp-content…

    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 720, Column 233: end tag for "img" omitted, but OMITTAG NO was specified
    …ex:999;" width=25 height=25 src=http://seriale.filmesubtitrate.info/wp-content…

    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 720, Column 134: start tag was here
    …one&#39;;return false;" title="Close"><img style="margin:-2px 5px 0 -36px; pos…
  • Error Line 775, Column 4: document type does not allow element "td" here
    <td>

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

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

  • Error Line 803, Column 4: document type does not allow element "td" here
    <td>

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

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

  • Error Line 831, Column 4: document type does not allow element "td" here
    <td>

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

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

  • Error Line 864, Column 5: end tag for "td" omitted, but OMITTAG NO was specified
    </tr>

    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 803, Column 1: start tag was here
    <td>
  • Error Line 864, Column 5: end tag for "td" omitted, but OMITTAG NO was specified
    </tr>

    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 775, Column 1: start tag was here
    <td>
  • Error Line 864, Column 5: end tag for "td" omitted, but OMITTAG NO was specified
    </tr>

    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 747, Column 1: start tag was here
    <td>
  • Error Line 918, Column 4: document type does not allow element "td" here
    <td>

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

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

  • Error Line 946, Column 4: document type does not allow element "td" here
    <td>

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

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

  • Error Line 974, Column 4: document type does not allow element "td" here
    <td>

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

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

  • Error Line 1007, Column 5: end tag for "td" omitted, but OMITTAG NO was specified
    </tr>

    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 946, Column 1: start tag was here
    <td>
  • Error Line 1007, Column 5: end tag for "td" omitted, but OMITTAG NO was specified
    </tr>

    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 918, Column 1: start tag was here
    <td>
  • Error Line 1007, Column 5: end tag for "td" omitted, but OMITTAG NO was specified
    </tr>

    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 890, Column 1: start tag was here
    <td>
  • Error Line 1061, Column 4: document type does not allow element "td" here
    <td>

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

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

  • Error Line 1089, Column 4: document type does not allow element "td" here
    <td>

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

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

  • Error Line 1117, Column 4: document type does not allow element "td" here
    <td>

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

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

  • Error Line 1150, Column 5: end tag for "td" omitted, but OMITTAG NO was specified
    </tr>

    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 1089, Column 1: start tag was here
    <td>
  • Error Line 1150, Column 5: end tag for "td" omitted, but OMITTAG NO was specified
    </tr>

    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 1061, Column 1: start tag was here
    <td>
  • Error Line 1150, Column 5: end tag for "td" omitted, but OMITTAG NO was specified
    </tr>

    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 1033, Column 1: start tag was here
    <td>
  • Error Line 1204, Column 4: document type does not allow element "td" here
    <td>

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

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

  • Error Line 1232, Column 4: document type does not allow element "td" here
    <td>

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

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

  • Error Line 1260, Column 4: document type does not allow element "td" here
    <td>

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

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

  • Error Line 1293, Column 5: end tag for "td" omitted, but OMITTAG NO was specified
    </tr>

    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 1232, Column 1: start tag was here
    <td>
  • Error Line 1293, Column 5: end tag for "td" omitted, but OMITTAG NO was specified
    </tr>

    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 1204, Column 1: start tag was here
    <td>
  • Error Line 1293, Column 5: end tag for "td" omitted, but OMITTAG NO was specified
    </tr>

    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 1176, Column 1: start tag was here
    <td>
  • Error Line 1347, Column 4: document type does not allow element "td" here
    <td>

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

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

  • Error Line 1375, Column 4: document type does not allow element "td" here
    <td>

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

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

  • Error Line 1403, Column 4: document type does not allow element "td" here
    <td>

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

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

  • Error Line 1436, Column 5: end tag for "td" omitted, but OMITTAG NO was specified
    </tr>

    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 1375, Column 1: start tag was here
    <td>
  • Error Line 1436, Column 5: end tag for "td" omitted, but OMITTAG NO was specified
    </tr>

    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 1347, Column 1: start tag was here
    <td>
  • Error Line 1436, Column 5: end tag for "td" omitted, but OMITTAG NO was specified
    </tr>

    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 1319, Column 1: start tag was here
    <td>
  • Error Line 1490, Column 4: document type does not allow element "td" here
    <td>

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

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

  • Error Line 1518, Column 4: document type does not allow element "td" here
    <td>

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

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

  • Error Line 1546, Column 4: document type does not allow element "td" here
    <td>

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

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

  • Error Line 1579, Column 5: end tag for "td" omitted, but OMITTAG NO was specified
    </tr>

    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 1518, Column 1: start tag was here
    <td>
  • Error Line 1579, Column 5: end tag for "td" omitted, but OMITTAG NO was specified
    </tr>

    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 1490, Column 1: start tag was here
    <td>
  • Error Line 1579, Column 5: end tag for "td" omitted, but OMITTAG NO was specified
    </tr>

    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 1462, Column 1: start tag was here
    <td>
  • Error Line 1698, Column 80: there is no attribute "placeholder"
    … type="text" name="email" placeholder="" /><input type="hidden" value="filmesu…

    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 1762, Column 295: document type does not allow element "a" here; missing one of "object", "span", "bdo", "applet", "iframe", "tt", "i", "b", "u", "s", "strike", "big", "small", "font", "em", "strong", "dfn", "code", "q", "samp", "kbd", "var", "cite", "abbr", "acronym", "sub", "sup", "label", "ins", "del" start-tag
    …ctronice.ro">Tigara electronica Pret<a></a></a>|<a href="http://ciprian-cipy.b…

    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 1951, Column 44: there is no attribute "rel"
    …label id="modal-register-captcha" rel="http://www.seriale.filmesubtitrate.info…

    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 1965, Column 14: ID "fb-root" already defined
        <div id="fb-root"></div>

    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 10: ID "fb-root" first defined here
    <div id="fb-root"></div>
  • Warning Line 417, Column 28: reference to non-existent ID "user_login"
    <label class="greyx2" for="user_login">Inregistreaza-te folosind o adresa de em…

    This error can be triggered by:

    • A non-existent input, select or textarea element
    • A missing id attribute
    • A typographical error in the id attribute

    Try to check the spelling and case of the id you are referring to.

Visitor Analysis

Daily Visitor
  • 11.317 visits