Alekino.tv - Najlepsze darmowe filmy online i seriale online, Filmy online, filmy online za darmo, bez limitu, premiery kinowe, komedie, horrory, dla dzieci. ...

kinolive.pl
  • Domain Name
    kinolive.pl
  • Favicon
  • Google Page Rank
    0
  • Alexa Rank
    #30921
  • Page Size
    162.8 KB
  • Ip Address
    94.75.221.135
  • Heading
    H1: 0, H2: 10, H3: 1, H4: 21, H5: 0, H6: 0
  • Images
    4 GIF, 56 JPG, 47 PNG

Website Meta Analysis

  • Title
    Filmy online, seriale online z lektorem, za darmo. Alekino.tv
  • Meta Keyword
    filmy, seriale, Filmy online, filmy za darmo, filmy bez limitu, filmy przez internet, filmy online, download film, premiery, darmowe filmy , pobierz film, filmy przez internet, filmy online, seriale, seriale online
  • Meta Description
    Alekino.tv - Najlepsze darmowe filmy online i seriale online, Filmy online, filmy online za darmo, bez limitu, premiery kinowe, komedie, horrory, dla dzieci.

Technical Analysis

  • Webserver
    nginx
  • Ip Address
    94.75.221.135
  • Domain Age
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from kinolive.pl.

HTML Analysis

  • server: nginx
  • date: Sun, 04 Aug 2013 15:54:41 GMT
  • content-type: text/html
  • connection: close
  • x-powered-by: PHP/5.4.17-1~dotdeb.0
  • expires: Thu, 19 Nov 1981 08:52:00 GMT
  • cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
  • pragma: no-cache
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA

DOMAIN NAME: kinolive.pl
registrant type: organization
nameservers: ns4.101domain.com.
ns3.101domain.com.
created: 2009.03.21 16:57:50
last modified: 2012.09.30 13:34:08
renewal date: 2014.03.21 16:57:50

no option

dnssec: Unsigned

TECHNICAL CONTACT:
company: Michau Enterprises Limited
street: Chytron 26, Office 21
city: 1075 Nicosia
location: CY
handle: mjp_tech
phone: +357.22761649
last modified: 2012.04.06

The domain name is under dispute

REGISTRAR:
101Domain, Inc.
5858 Edison Pl
Carlsbad CA, 92008
U.S.A.
Ph. +1.7604448674
Toll Fee US/CA. 18779836624
Fax +1.7605794996

WHOIS displays data with a delay not exceeding 15 minutes in relation to the .pl Registry system
Registrant data available at http://dns.pl/cgi-bin/en_whois.pl

DNS Analysis


DNS servers
ns3.101domain.com
ns4.101domain.com [69.64.77.48]


DNS Records

Answer records
kinolive.pl SOA
server: ns3.101domain.com
email: artloj@gmail.com
serial: 1354230414
refresh: 10800
retry: 3600
expire: 604800
minimum ttl: 10800
600s
kinolive.pl NS  ns3.101domain.com 600s
kinolive.pl NS  ns4.101domain.com 600s
kinolive.pl A 5.39.70.120 600s
kinolive.pl MX
preference: 10
exchange: mail.kinolive.pl
600s

Authority records

Additional records
mail.kinolive.pl A 64.87.16.130 600s

IP 94.75.221.135 Analysis

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 130 Errors
  • 52 Warnings
Ratio Text/Html
  • 0.5832498605454621
Message Error
  • Error Line 12, Column 79: end tag for "meta" omitted, but OMITTAG NO was specified
            <meta name="viewport" content="width=device-width, initial-scale=1.0">

    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 12, Column 9: start tag was here
            <meta name="viewport" content="width=device-width, initial-scale=1.0">
  • Error Line 53, Column 46: there is no attribute "async"
    … <script type="text/javascript" async="" src="http://static.kinolive.pl/_files…

    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 217, Column 62: document type does not allow element "p" here
    …").html('<p style="text-align:center;"><img src="http://static.kinolive.pl/ima…

    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 218, Column 63: document type does not allow element "p" here
    …").html('<p style="text-align:center;"><img src="http://static.kinolive.pl/ima…

    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 219, Column 63: document type does not allow element "p" here
    …").html('<p style="text-align:center;"><img src="http://static.kinolive.pl/ima…

    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 240, Column 66: document type does not allow element "p" here
    …").html('<p style="text-align:center;"><img src="http://static.kinolive.pl/ima…

    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 244, Column 67: document type does not allow element "p" here
    …").html('<p style="text-align:center;"><img src="http://static.kinolive.pl/ima…

    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 248, Column 64: document type does not allow element "p" here
    …").html('<p style="text-align:center;"><img src="http://static.kinolive.pl/ima…

    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 274, Column 15: required attribute "type" not specified
            <style>

    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 289, Column 18: ID "moveThisAd" already defined
            <div id="moveThisAd">

    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 288, Column 27: ID "moveThisAd" first defined here
            	        <div id="moveThisAd">
  • Error Line 294, Column 16: 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 298, Column 67: cannot generate system identifier for general entity "appId"
    …  js.src = "//connect.facebook.net/pl_PL/all.js#xfbml=1&appId=134854226657021";

    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 298, Column 67: general entity "appId" not defined and no default entity
    …  js.src = "//connect.facebook.net/pl_PL/all.js#xfbml=1&appId=134854226657021";

    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 298, Column 72: reference not terminated by REFC delimiter
    …  js.src = "//connect.facebook.net/pl_PL/all.js#xfbml=1&appId=134854226657021";

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

    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 298, Column 66: entity was defined here
    …  js.src = "//connect.facebook.net/pl_PL/all.js#xfbml=1&appId=134854226657021";
  • Error Line 312, Column 41: value of attribute "method" cannot be "GET"; must be one of "get", "post"
    						<form action="/search" method="GET">

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

  • Error Line 313, Column 191: duplicate specification of attribute "id"
    …oby z obsady" onclick="this.value='';" id="search_query"  autocomplete="off" />

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

  • Error Line 313, Column 220: there is no attribute "autocomplete"
    …oby z obsady" onclick="this.value='';" id="search_query"  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 373, Column 252: there is no attribute "href"
    …argin-top:5px;margin-right:8px;" href="/upload/video" onClick="document.locati…

    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 373, Column 276: there is no attribute "onClick"
    …ht:8px;" href="/upload/video" onClick="document.location.href='/upload/video';…

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

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

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

  • Error Line 392, Column 21: there is no attribute "data-width"
    			      data-width="240" data-height="375" 

    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 392, Column 39: there is no attribute "data-height"
    			      data-width="240" data-height="375" 

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

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

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

  • Error Line 393, Column 20: there is no attribute "data-href"
    			      data-href="www.facebook.com/KinoLivePL" 

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

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

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

  • Error Line 394, Column 28: there is no attribute "data-border-color"
    			      data-border-color="#1a1a1a" data-show-faces="true" data-text-color="#f…

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

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

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

  • Error Line 394, Column 54: there is no attribute "data-show-faces"
    …   data-border-color="#1a1a1a" data-show-faces="true" data-text-color="#ffffff"

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

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

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

  • Error Line 394, Column 77: there is no attribute "data-text-color"
    …   data-border-color="#1a1a1a" data-show-faces="true" data-text-color="#ffffff"

    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 395, Column 22: there is no attribute "data-stream"
    			      data-stream="false" data-header="false">

    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 395, Column 42: there is no attribute "data-header"
    			      data-stream="false" data-header="false">

    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 408, Column 717: character "&" is the first character of a delimiter but occurred as data
    …lts,g);f=f||g.duration;g.queue=g.queue&&g.axis.length>1;if(g.queue)f/=2;g.offs…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 408, Column 719: cannot generate system identifier for general entity "g.axis.length"
    …s,g);f=f||g.duration;g.queue=g.queue&&g.axis.length>1;if(g.queue)f/=2;g.offset…

    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 408, Column 719: general entity "g.axis.length" not defined and no default entity
    …s,g);f=f||g.duration;g.queue=g.queue&&g.axis.length>1;if(g.queue)f/=2;g.offset…

    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 408, Column 732: reference not terminated by REFC delimiter
    …uration;g.queue=g.queue&&g.axis.length>1;if(g.queue)f/=2;g.offset=both(g.offse…

    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 408, Column 732: reference to entity "g.axis.length" for which no system identifier could be generated
    …uration;g.queue=g.queue&&g.axis.length>1;if(g.queue)f/=2;g.offset=both(g.offse…

    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 408, Column 718: entity was defined here
    …ts,g);f=f||g.duration;g.queue=g.queue&&g.axis.length>1;if(g.queue)f/=2;g.offse…
  • Warning Line 408, Column 1576: character "&" is the first character of a delimiter but occurred as data
    …else{var c=targ[pos];attr[key]=c.slice&&c.slice(-1)=='%'?parseFloat(c)/100*max…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 408, Column 1578: cannot generate system identifier for general entity "c.slice"
    …se{var c=targ[pos];attr[key]=c.slice&&c.slice(-1)=='%'?parseFloat(c)/100*max:c…

    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 408, Column 1578: general entity "c.slice" not defined and no default entity
    …se{var c=targ[pos];attr[key]=c.slice&&c.slice(-1)=='%'?parseFloat(c)/100*max:c…

    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 408, Column 1585: reference not terminated by REFC delimiter
    …c=targ[pos];attr[key]=c.slice&&c.slice(-1)=='%'?parseFloat(c)/100*max:c}if(g.l…

    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 408, Column 1585: reference to entity "c.slice" for which no system identifier could be generated
    …c=targ[pos];attr[key]=c.slice&&c.slice(-1)=='%'?parseFloat(c)/100*max:c}if(g.l…

    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 408, Column 1577: entity was defined here
    …lse{var c=targ[pos];attr[key]=c.slice&&c.slice(-1)=='%'?parseFloat(c)/100*max:…
  • Warning Line 408, Column 1629: character "&" is the first character of a delimiter but occurred as data
    …'%'?parseFloat(c)/100*max:c}if(g.limit&&/^\d+$/.test(attr[key]))attr[key]=attr…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 408, Column 1630: character "&" is the first character of a delimiter but occurred as data
    …%'?parseFloat(c)/100*max:c}if(g.limit&&/^\d+$/.test(attr[key]))attr[key]=attr[…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 408, Column 1674: character "<" is the first character of a delimiter but occurred as data
    …$/.test(attr[key]))attr[key]=attr[key]<=0?0:Math.min(attr[key],max);if(!i&&g.q…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 408, Column 1709: character "&" is the first character of a delimiter but occurred as data
    …ey]<=0?0:Math.min(attr[key],max);if(!i&&g.queue){if(old!=attr[key])animate(g.o…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 408, Column 1711: cannot generate system identifier for general entity "g.queue"
    …]<=0?0:Math.min(attr[key],max);if(!i&&g.queue){if(old!=attr[key])animate(g.onA…

    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 408, Column 1711: general entity "g.queue" not defined and no default entity
    …]<=0?0:Math.min(attr[key],max);if(!i&&g.queue){if(old!=attr[key])animate(g.onA…

    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 408, Column 1718: reference not terminated by REFC delimiter
    …Math.min(attr[key],max);if(!i&&g.queue){if(old!=attr[key])animate(g.onAfterFir…

    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 408, Column 1718: reference to entity "g.queue" for which no system identifier could be generated
    …Math.min(attr[key],max);if(!i&&g.queue){if(old!=attr[key])animate(g.onAfterFir…

    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 408, Column 1710: entity was defined here
    …y]<=0?0:Math.min(attr[key],max);if(!i&&g.queue){if(old!=attr[key])animate(g.on…
  • Warning Line 408, Column 1852: character "&" is the first character of a delimiter but occurred as data
    …ate(a){$elem.animate(attr,f,g.easing,a&&function(){a.call(this,e,g)})}}).end()…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 408, Column 1854: cannot generate system identifier for general entity "function"
    …e(a){$elem.animate(attr,f,g.easing,a&&function(){a.call(this,e,g)})}}).end()};…

    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 408, Column 1854: general entity "function" not defined and no default entity
    …e(a){$elem.animate(attr,f,g.easing,a&&function(){a.call(this,e,g)})}}).end()};…

    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 408, Column 1862: reference not terminated by REFC delimiter
    …em.animate(attr,f,g.easing,a&&function(){a.call(this,e,g)})}}).end()};h.max=fu…

    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 408, Column 1862: reference to entity "function" for which no system identifier could be generated
    …em.animate(attr,f,g.easing,a&&function(){a.call(this,e,g)})}}).end()};h.max=fu…

    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 408, Column 1853: entity was defined here
    …te(a){$elem.animate(attr,f,g.easing,a&&function(){a.call(this,e,g)})}}).end()}…
  • Warning Line 412, Column 52: character "&" is the first character of a delimiter but occurred as data
    …nt.documentElement.clientWidth > 3500 && document.documentElement.clientWidth …

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 412, Column 53: character "&" is the first character of a delimiter but occurred as data
    …t.documentElement.clientWidth > 3500 && document.documentElement.clientWidth <…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 412, Column 92: character "<" is the first character of a delimiter but occurred as data
    …umentElement.clientWidth > 3500 && document.documentElement.clientWidth < 6000)

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 418, Column 57: character "&" is the first character of a delimiter but occurred as data
    …nt.documentElement.clientWidth > 2300 && document.documentElement.clientWidth …

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 418, Column 58: character "&" is the first character of a delimiter but occurred as data
    …t.documentElement.clientWidth > 2300 && document.documentElement.clientWidth <…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 418, Column 97: character "<" is the first character of a delimiter but occurred as data
    …umentElement.clientWidth > 2300 && document.documentElement.clientWidth < 3500)

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 437, Column 52: character "&" is the first character of a delimiter but occurred as data
    …nt.documentElement.clientWidth > 3500 && document.documentElement.clientWidth …

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 437, Column 53: character "&" is the first character of a delimiter but occurred as data
    …t.documentElement.clientWidth > 3500 && document.documentElement.clientWidth <…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 437, Column 92: character "<" is the first character of a delimiter but occurred as data
    …umentElement.clientWidth > 3500 && document.documentElement.clientWidth < 6000)

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 443, Column 57: character "&" is the first character of a delimiter but occurred as data
    …nt.documentElement.clientWidth > 2300 && document.documentElement.clientWidth …

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 443, Column 58: character "&" is the first character of a delimiter but occurred as data
    …t.documentElement.clientWidth > 2300 && document.documentElement.clientWidth <…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 443, Column 97: character "<" is the first character of a delimiter but occurred as data
    …umentElement.clientWidth > 2300 && document.documentElement.clientWidth < 3500)

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 610, Column 83: document type does not allow element "div" here
    …gn:center;width:755px;margin: 0 auto;"><iframe src="http://www.megustavid.com/…

    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 643, Column 44: there is no attribute "data-vid"
    …			<div class="image-static" data-vid="20545" style="background:url(http://sta…

    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 646, Column 32: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    	    				<div class="more-info">

    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 659, Column 238: there is no attribute "data-screen"
    …ze: 76px 105px;" href="#" data-screen="http://static.kinolive.pl/screen/b79b76…

    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 659, Column 320: there is no attribute "data-year"
    …f3a6eb332731bb2d923264.jpg" data-year="2012" data-name="Dredd 3D " data-vid="2…

    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 659, Column 337: there is no attribute "data-name"
    …23264.jpg" data-year="2012" data-name="Dredd 3D " data-vid="20545" data-href="…

    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 659, Column 358: there is no attribute "data-vid"
    …"2012" data-name="Dredd 3D " data-vid="20545" data-href="/film_online/20545-dr…

    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 659, Column 376: there is no attribute "data-href"
    …Dredd 3D " data-vid="20545" data-href="/film_online/20545-dredd-3d-2012-lektor…

    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 659, Column 436: there is no attribute "data-trailer"
    …edd-3d-2012-lektor.html" data-trailer="http://www.youtube.com/watch?v=T76g6AJO…

    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 659, Column 491: there is no attribute "data-orig"
    …be.com/watch?v=T76g6AJOEnY" data-orig=" Dredd" data-categories="&lt;a class=&q…

    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 659, Column 516: there is no attribute "data-categories"
    …Y" data-orig=" Dredd" data-categories="&lt;a class=&quot;pl-pink-white&quot; h…

    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 679, Column 475: cannot generate system identifier for general entity "feature"
    …//www.youtube.com/watch?v=w6Yd4DVOQ7A&feature=youtu.be" data-orig="&nbsp;" dat…

    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 679, Column 475: general entity "feature" not defined and no default entity
    …//www.youtube.com/watch?v=w6Yd4DVOQ7A&feature=youtu.be" data-orig="&nbsp;" dat…

    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 679, Column 482: reference not terminated by REFC delimiter
    …outube.com/watch?v=w6Yd4DVOQ7A&feature=youtu.be" data-orig="&nbsp;" data-categ…

    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 679, Column 482: reference to external entity in attribute value
    …outube.com/watch?v=w6Yd4DVOQ7A&feature=youtu.be" data-orig="&nbsp;" data-categ…

    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 679, Column 482: reference to entity "feature" for which no system identifier could be generated
    …outube.com/watch?v=w6Yd4DVOQ7A&feature=youtu.be" data-orig="&nbsp;" data-categ…

    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 679, Column 474: entity was defined here
    …://www.youtube.com/watch?v=w6Yd4DVOQ7A&feature=youtu.be" data-orig="&nbsp;" da…
  • Warning Line 683, Column 494: reference not terminated by REFC delimiter
    …outube.com/watch?v=D_2yZQYcJXA&feature=youtu.be" data-orig="&nbsp;" data-categ…

    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 683, Column 494: reference to external entity in attribute value
    …outube.com/watch?v=D_2yZQYcJXA&feature=youtu.be" data-orig="&nbsp;" data-categ…

    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 683, Column 494: reference to entity "feature" for which no system identifier could be generated
    …outube.com/watch?v=D_2yZQYcJXA&feature=youtu.be" data-orig="&nbsp;" data-categ…

    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 679, Column 474: entity was defined here
    …://www.youtube.com/watch?v=w6Yd4DVOQ7A&feature=youtu.be" data-orig="&nbsp;" da…
  • Warning Line 691, Column 473: reference not terminated by REFC delimiter
    …outube.com/watch?v=lJDWXig70gU&feature=youtu.be" data-orig=" Lawless" data-cat…

    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 691, Column 473: reference to external entity in attribute value
    …outube.com/watch?v=lJDWXig70gU&feature=youtu.be" data-orig=" Lawless" data-cat…

    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 691, Column 473: reference to entity "feature" for which no system identifier could be generated
    …outube.com/watch?v=lJDWXig70gU&feature=youtu.be" data-orig=" Lawless" data-cat…

    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 679, Column 474: entity was defined here
    …://www.youtube.com/watch?v=w6Yd4DVOQ7A&feature=youtu.be" data-orig="&nbsp;" da…
  • Warning Line 723, Column 555: reference not terminated by REFC delimiter
    …outube.com/watch?v=K0uS_O4LuzQ&feature=youtu.be" data-orig=" Astérix et Obélix…

    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 723, Column 555: reference to external entity in attribute value
    …outube.com/watch?v=K0uS_O4LuzQ&feature=youtu.be" data-orig=" Astérix et Obélix…

    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 723, Column 555: reference to entity "feature" for which no system identifier could be generated
    …outube.com/watch?v=K0uS_O4LuzQ&feature=youtu.be" data-orig=" Astérix et Obélix…

    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 679, Column 474: entity was defined here
    …://www.youtube.com/watch?v=w6Yd4DVOQ7A&feature=youtu.be" data-orig="&nbsp;" da…
  • Error Line 815, Column 39: document type does not allow element "style" here
                    <style type="text/css">

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

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

  • Error Line 848, Column 134: required attribute "alt" not specified
    …l/okladki/3f4873d3d728d9b874872f2a21053669_thumb.jpg" width="50" height="65" />

    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 861, Column 134: required attribute "alt" not specified
    …l/okladki/3beda14924977eb77a3d71d8a6e43eb6_thumb.jpg" width="50" height="65" />

    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 874, Column 134: required attribute "alt" not specified
    …l/okladki/34d87ea9aaced5e9effedc686720c303_thumb.jpg" width="50" height="65" />

    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 887, Column 134: required attribute "alt" not specified
    …l/okladki/a4c9f830b1a6ca4e6d8fe16cd3794343_thumb.jpg" width="50" height="65" />

    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 900, Column 134: required attribute "alt" not specified
    …l/okladki/e9c25026c629a4b512b8aa6c26dcdc6c_thumb.jpg" width="50" height="65" />

    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 913, Column 134: required attribute "alt" not specified
    …l/okladki/95cbc21f4354e0fc4462447c0807aa26_thumb.jpg" width="50" height="65" />

    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 926, Column 134: required attribute "alt" not specified
    …l/okladki/5f7ec29232d28f80178a382eaff6a66b_thumb.jpg" width="50" height="65" />

    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 939, Column 134: required attribute "alt" not specified
    …l/okladki/34b32cac8558fe68275e890188e32217_thumb.jpg" width="50" height="65" />

    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 952, Column 134: required attribute "alt" not specified
    …l/okladki/5b9e847a630312eaf27aabd419c57ac6_thumb.jpg" width="50" height="65" />

    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 965, Column 134: required attribute "alt" not specified
    …l/okladki/ce26af944d83c41e6a97a13260424bc6_thumb.jpg" width="50" height="65" />

    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 976, Column 60: document type does not allow element "div" here; assuming missing "li" start-tag
    		                					            <div style="clear:both;"></div>
  • Error Line 978, Column 23: end tag for "li" omitted, but OMITTAG NO was specified
    		                </ul>

    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 976, Column 36: start tag was here
    		                					            <div style="clear:both;"></div>
  • Error Line 984, Column 134: required attribute "alt" not specified
    …l/okladki/86fc0077891197f1fc159b30f045bf6f_thumb.jpg" width="50" height="65" />

    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 998, Column 134: required attribute "alt" not specified
    …l/okladki/6dec800dcc4b98ee39ae79a77ec7853b_thumb.jpg" width="50" height="65" />

    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 1012, Column 134: required attribute "alt" not specified
    …l/okladki/e4fa49a808f87eb75bda22ce6b8b907d_thumb.jpg" width="50" height="65" />

    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 1026, Column 134: required attribute "alt" not specified
    …l/okladki/d0c6a7fb9cc829d999ac6750018f8a24_thumb.jpg" width="50" height="65" />

    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 1040, Column 134: required attribute "alt" not specified
    …l/okladki/5c6f1102933336efdc4ca5e68c6540dc_thumb.jpg" width="50" height="65" />

    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 1054, Column 134: required attribute "alt" not specified
    …l/okladki/86fc0077891197f1fc159b30f045bf6f_thumb.jpg" width="50" height="65" />

    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 1068, Column 134: required attribute "alt" not specified
    …l/okladki/5a8c4a0103756461cd8212a04d293dfd_thumb.jpg" width="50" height="65" />

    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 1085, Column 134: required attribute "alt" not specified
    …l/okladki/e101b4e9aac789628e503dd2f914f5e1_thumb.jpg" width="50" height="65" />

    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 1101, Column 134: required attribute "alt" not specified
    …l/okladki/5165a636f9039eb904ab163888a65ff2_thumb.jpg" width="50" height="65" />

    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 1115, Column 134: required attribute "alt" not specified
    …l/okladki/fb496e8205587073fe31dcc1db49be6d_thumb.jpg" width="50" height="65" />

    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 1129, Column 60: document type does not allow element "div" here; assuming missing "li" start-tag
    		                					            <div style="clear:both;"></div>
  • Error Line 1131, Column 23: end tag for "li" omitted, but OMITTAG NO was specified
    		                </ul>

    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 1129, Column 36: start tag was here
    		                					            <div style="clear:both;"></div>
  • Error Line 1156, Column 243: required attribute "alt" not specified
    …e="ma-i-we-i" width="72" height="93" style="float:left;margin-right:7px" /></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 1166, Column 341: required attribute "alt" not specified
    …nderstanding" width="72" height="93" style="float:left;margin-right:7px" /></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 1176, Column 243: required attribute "alt" not specified
    …e="the-truth" width="72" height="93" style="float:left;margin-right:7px" /></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 1186, Column 270: required attribute "alt" not specified
    …d-life-of-pi" width="72" height="93" style="float:left;margin-right:7px" /></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 1196, Column 325: required attribute "alt" not specified
    …-retribution" width="72" height="93" style="float:left;margin-right:7px" /></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 1207, Column 287: required attribute "alt" not specified
    …re-la-raison" width="72" height="93" style="float:left;margin-right:7px" /></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 1217, Column 331: required attribute "alt" not specified
    …ngs-playbook" width="72" height="93" style="float:left;margin-right:7px" /></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 1227, Column 239: required attribute "alt" not specified
    …tle="skyfall" width="72" height="93" style="float:left;margin-right:7px" /></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 1237, Column 233: required attribute "alt" not specified
    …itle="obława" width="72" height="93" style="float:left;margin-right:7px" /></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 1247, Column 264: required attribute "alt" not specified
    …odowiec-léon" width="72" height="93" style="float:left;margin-right:7px" /></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 1257, Column 274: required attribute "alt" not specified
    …i-death-race" width="72" height="93" style="float:left;margin-right:7px" /></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 1267, Column 233: required attribute "alt" not specified
    …itle="obława" width="72" height="93" style="float:left;margin-right:7px" /></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 1277, Column 321: required attribute "alt" not specified
    …spre-dincolo" width="72" height="93" style="float:left;margin-right:7px" /></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 1287, Column 305: required attribute "alt" not specified
    …-to-die-hard" width="72" height="93" style="float:left;margin-right:7px" /></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 1297, Column 298: required attribute "alt" not specified
    …ci-desu-nôto" width="72" height="93" style="float:left;margin-right:7px" /></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 1310, Column 140: required attribute "alt" not specified
    …/static.kinolive.pl/images/prev.png" /></a>&nbsp;&nbsp;<a href="javascript:voi…

    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 1310, Column 325: required attribute "alt" not specified
    …/static.kinolive.pl/images/stop.png" /></a><a class="none" href="javascript:vo…

    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 1310, Column 511: required attribute "alt" not specified
    …/static.kinolive.pl/images/play.png" /></a>&nbsp;&nbsp;<a href="javascript:voi…

    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 1310, Column 644: required attribute "alt" not specified
    …"><img class="vam" src="http://static.kinolive.pl/images/next.png" /></a></div>

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

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

  • Warning Line 1321, Column 29: cannot generate system identifier for general entity "c"
    				<a href="#/videos?type=&c=2&t=a&o=mv" class="filmy_button">Filmy</a>

    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 1321, Column 29: general entity "c" not defined and no default entity
    				<a href="#/videos?type=&c=2&t=a&o=mv" class="filmy_button">Filmy</a>

    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 1321, Column 30: reference not terminated by REFC delimiter
    				<a href="#/videos?type=&c=2&t=a&o=mv" class="filmy_button">Filmy</a>

    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 1321, Column 30: reference to external entity in attribute value
    				<a href="#/videos?type=&c=2&t=a&o=mv" class="filmy_button">Filmy</a>

    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 1321, Column 30: reference to entity "c" for which no system identifier could be generated
    				<a href="#/videos?type=&c=2&t=a&o=mv" class="filmy_button">Filmy</a>

    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 1321, Column 28: entity was defined here
    				<a href="#/videos?type=&c=2&t=a&o=mv" class="filmy_button">Filmy</a>
  • Warning Line 1321, Column 33: cannot generate system identifier for general entity "t"
    				<a href="#/videos?type=&c=2&t=a&o=mv" class="filmy_button">Filmy</a>

    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 1321, Column 33: general entity "t" not defined and no default entity
    				<a href="#/videos?type=&c=2&t=a&o=mv" class="filmy_button">Filmy</a>

    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 1321, Column 34: reference not terminated by REFC delimiter
    				<a href="#/videos?type=&c=2&t=a&o=mv" class="filmy_button">Filmy</a>

    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 1321, Column 34: reference to external entity in attribute value
    				<a href="#/videos?type=&c=2&t=a&o=mv" class="filmy_button">Filmy</a>

    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 1321, Column 34: reference to entity "t" for which no system identifier could be generated
    				<a href="#/videos?type=&c=2&t=a&o=mv" class="filmy_button">Filmy</a>

    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 1321, Column 32: entity was defined here
    				<a href="#/videos?type=&c=2&t=a&o=mv" class="filmy_button">Filmy</a>
  • Warning Line 1321, Column 37: cannot generate system identifier for general entity "o"
    				<a href="#/videos?type=&c=2&t=a&o=mv" class="filmy_button">Filmy</a>

    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 1321, Column 37: general entity "o" not defined and no default entity
    				<a href="#/videos?type=&c=2&t=a&o=mv" class="filmy_button">Filmy</a>

    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 1321, Column 38: reference not terminated by REFC delimiter
    				<a href="#/videos?type=&c=2&t=a&o=mv" class="filmy_button">Filmy</a>

    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 1321, Column 38: reference to external entity in attribute value
    				<a href="#/videos?type=&c=2&t=a&o=mv" class="filmy_button">Filmy</a>

    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 1321, Column 38: reference to entity "o" for which no system identifier could be generated
    				<a href="#/videos?type=&c=2&t=a&o=mv" class="filmy_button">Filmy</a>

    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 1321, Column 36: entity was defined here
    				<a href="#/videos?type=&c=2&t=a&o=mv" class="filmy_button">Filmy</a>
  • Warning Line 1322, Column 30: reference not terminated by REFC delimiter
    				<a href="#/videos?type=&c=3&t=a&o=mv" class="seriale_button" style="margin-…

    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 1322, Column 30: reference to external entity in attribute value
    				<a href="#/videos?type=&c=3&t=a&o=mv" class="seriale_button" style="margin-…

    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 1322, Column 30: reference to entity "c" for which no system identifier could be generated
    				<a href="#/videos?type=&c=3&t=a&o=mv" class="seriale_button" style="margin-…

    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 1321, Column 28: entity was defined here
    				<a href="#/videos?type=&c=2&t=a&o=mv" class="filmy_button">Filmy</a>
  • Warning Line 1322, Column 34: reference not terminated by REFC delimiter
    				<a href="#/videos?type=&c=3&t=a&o=mv" class="seriale_button" style="margin-…

    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 1322, Column 34: reference to external entity in attribute value
    				<a href="#/videos?type=&c=3&t=a&o=mv" class="seriale_button" style="margin-…

    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 1322, Column 34: reference to entity "t" for which no system identifier could be generated
    				<a href="#/videos?type=&c=3&t=a&o=mv" class="seriale_button" style="margin-…

    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 1321, Column 32: entity was defined here
    				<a href="#/videos?type=&c=2&t=a&o=mv" class="filmy_button">Filmy</a>
  • Warning Line 1322, Column 38: reference not terminated by REFC delimiter
    				<a href="#/videos?type=&c=3&t=a&o=mv" class="seriale_button" style="margin-…

    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 1322, Column 38: reference to external entity in attribute value
    				<a href="#/videos?type=&c=3&t=a&o=mv" class="seriale_button" style="margin-…

    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 1322, Column 38: reference to entity "o" for which no system identifier could be generated
    				<a href="#/videos?type=&c=3&t=a&o=mv" class="seriale_button" style="margin-…

    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 1321, Column 36: entity was defined here
    				<a href="#/videos?type=&c=2&t=a&o=mv" class="filmy_button">Filmy</a>
  • Error Line 1340, Column 30: document type does not allow element "div" here; assuming missing "li" start-tag
    			<div style="display:none;">0</div>
  • Error Line 1358, Column 87: document type does not allow element "div" here
    …style="padding:5px;text-align:center;"><img src="http://static.kinolive.pl/ima…

    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 1366, Column 88: document type does not allow element "div" here
    …style="padding:5px;text-align:center;"><img src="http://static.kinolive.pl/ima…

    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 1386, Column 87: document type does not allow element "div" here
    …style="padding:5px;text-align:center;"><img src="http://static.kinolive.pl/ima…

    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 1394, Column 88: document type does not allow element "div" here
    …style="padding:5px;text-align:center;"><img src="http://static.kinolive.pl/ima…

    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 1414, Column 87: document type does not allow element "div" here
    …style="padding:5px;text-align:center;"><img src="http://static.kinolive.pl/ima…

    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 1422, Column 88: document type does not allow element "div" here
    …style="padding:5px;text-align:center;"><img src="http://static.kinolive.pl/ima…

    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 1442, Column 87: document type does not allow element "div" here
    …style="padding:5px;text-align:center;"><img src="http://static.kinolive.pl/ima…

    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 1450, Column 88: document type does not allow element "div" here
    …style="padding:5px;text-align:center;"><img src="http://static.kinolive.pl/ima…

    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 1463, Column 167: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    …: url(images/kinolive_34.png) no-repeat;width: 356px; height:55px !important;">

    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 1477, Column 167: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    …: url(images/kinolive_34.png) no-repeat;width: 356px; height:55px !important;">

    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 1491, Column 167: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    …: url(images/kinolive_34.png) no-repeat;width: 356px; height:55px !important;">

    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 1505, Column 167: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    …: url(images/kinolive_34.png) no-repeat;width: 356px; height:55px !important;">

    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 1519, Column 200: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    …: url(images/kinolive_34.png) no-repeat;width: 356px; height:55px !important;">

    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 1537, Column 156: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    …http://static.kinolive.pl/images/kinolive_34.png);width: 356px; height: 55px;">

    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 1552, Column 156: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    …http://static.kinolive.pl/images/kinolive_34.png);width: 356px; height: 55px;">

    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 1567, Column 156: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    …http://static.kinolive.pl/images/kinolive_34.png);width: 356px; height: 55px;">

    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 1582, Column 156: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    …http://static.kinolive.pl/images/kinolive_34.png);width: 356px; height: 55px;">

    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 1597, Column 189: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    …http://static.kinolive.pl/images/kinolive_34.png);width: 356px; height: 55px;">

    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 1615, Column 5: end tag for "li" omitted, but OMITTAG NO was specified
    </ul>

    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 1340, Column 4: start tag was here
    			<div style="display:none;">0</div>
  • Warning Line 1760, Column 94: character "<" is the first character of a delimiter but occurred as data
    …acebook.com/KinoLivePL" target="_blank<"><img src="http://static.kinolive.pl/i…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 1760, Column 94: character "<" is not allowed in the value of attribute "target"
    …acebook.com/KinoLivePL" target="_blank<"><img src="http://static.kinolive.pl/i…

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

  • Error Line 1763, Column 26: document type does not allow element "style" here
    			<style type="text/css">

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

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

  • Error Line 1797, Column 117: required attribute "alt" not specified
    … src="http://www.fust.pl/fust.jpg"  style="width:1020px;height:200px;"></a><br>

    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 1797, Column 121: end tag for "img" omitted, but OMITTAG NO was specified
    … src="http://www.fust.pl/fust.jpg"  style="width:1020px;height:200px;"></a><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 1797, Column 43: start tag was here
    …    				    	<a href="http://fust.pl"><img src="http://www.fust.pl/fust.jpg"  …
  • Error Line 1797, Column 126: end tag for "br" omitted, but OMITTAG NO was specified
    … src="http://www.fust.pl/fust.jpg"  style="width:1020px;height:200px;"></a><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 1797, Column 122: start tag was here
    … src="http://www.fust.pl/fust.jpg"  style="width:1020px;height:200px;"></a><br>
  • Error Line 1798, Column 118: required attribute "alt" not specified
    …src="http://www.hasia.pl/Untitled.gif"  style="width:1020px;height:200px;"></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 1798, Column 122: end tag for "img" omitted, but OMITTAG NO was specified
    …src="http://www.hasia.pl/Untitled.gif"  style="width:1020px;height:200px;"></a>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 1798, Column 39: start tag was here
    <a href="http://www.hasia.pl/shared/"><img src="http://www.hasia.pl/Untitled.gi…
  • Error Line 1845, Column 60: required attribute "alt" not specified
                    <img src="http://kinolive.pl/favicon.gif" />

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

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

  • Error Line 1856, Column 15: end tag for element "center" which is not open
    </div></center>

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

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

  • Warning Line 1860, Column 82: reference not terminated by REFC delimiter
    …e='text/javascript' src='http://liczniki.org/hit.php?l=kinolive2&o=1'></script>

    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 1860, Column 82: reference to external entity in attribute value
    …e='text/javascript' src='http://liczniki.org/hit.php?l=kinolive2&o=1'></script>

    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 1860, Column 82: reference to entity "o" for which no system identifier could be generated
    …e='text/javascript' src='http://liczniki.org/hit.php?l=kinolive2&o=1'></script>

    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 1321, Column 36: entity was defined here
    				<a href="#/videos?type=&c=2&t=a&o=mv" class="filmy_button">Filmy</a>

Visitor Analysis

Daily Visitor
  • 0 visits