21Cineplex Official Site - The Official Indonesia Cinema 21 Movies Site featuring complete showtimes of all theaters in Indonesia. ...

21cineplex.com
  • Domain Name
    21cineplex.com
  • Favicon
  • Google Page Rank
    4
  • Alexa Rank
    #7155
  • Page Size
    38.3 KB
  • Ip Address
    202.59.161.235
  • Heading
    H1: 0, H2: 11, H3: 10, H4: 0, H5: 0, H6: 0
  • Images
    0 GIF, 31 JPG, 6 PNG

Website Meta Analysis

  • Title
    Cinema 21 - Largest Indonesian Cinema Network - Cinema 21
  • Meta Keyword
    Cinema 21, 21cineplex, Now Playing, Coming Soon, Theater, Bioskop 21, The Stars, 21Exclusive, Slowmotion, Gallery, Video Trailer
  • Meta Description
    21Cineplex Official Site - The Official Indonesia Cinema 21 Movies Site featuring complete showtimes of all theaters in Indonesia.

Technical Analysis

  • Webserver
    nginx
  • Ip Address
    202.59.161.235
  • Domain Age
    13 Years, 10 Months, 7 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • server: nginx
  • date: Wed, 04 Sep 2013 18:19:44 GMT
  • content-type: text/html
  • connection: keep-alive
  • vary: Accept-Encoding
  • x-powered-by: PHP/5.4.17
  • 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
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Contact: email
Visit: http://www.semanggi.net

Domain Name: 21cineplex.com

Registrant:
NA
NA 21Cineplex ()

Fax:
Jl. K.H Wahid Hasyim No. 96 Bldg C
Jakarta, DKI Jakarta 10340
ID

Administrative Contact:
NA
Bambang Hartono ( email )
+62.2131901188
Fax: +62.2131907366
Jl. K.H Wahid Hasyim No. 96 Bldg C
Jakarta, DKI Jakarta 10340
ID

Technical Contact:
NA
Taufik Hidayat ( email )
+62.56966221
Fax: +62.56966254
Gedung IKM Honda Lt.3
Jl. Daan Mogot No.6
Jakarta Barat, DKI Jaya Jakarta 10160
ID

Domain Status: Locked

Name Servers:
dns1.name-services.com
dns2.name-services.com
dns3.name-services.com
dns4.name-services.com
dns5.name-services.com

Created: 10 Nov 1999 00:48:59
Expires: 10 Nov 2014 00:48:59

DNS Analysis


DNS servers
dns1.name-services.com [98.124.192.1]
dns2.name-services.com [98.124.197.1]
dns3.name-services.com [98.124.193.1]
dns4.name-services.com [98.124.194.1]
dns5.name-services.com [98.124.196.1]

DNS Records

Answer records
21cineplex.com NS  dns2.name-services.com 3600s
21cineplex.com NS  dns4.name-services.com 3600s
21cineplex.com NS  dns1.name-services.com 3600s
21cineplex.com SOA
server: dns1.name-services.com
email: info@name-services.com
serial: 2002050701
refresh: 10800
retry: 3600
expire: 604800
minimum ttl: 3600
1800s
21cineplex.com NS  dns5.name-services.com 3600s
21cineplex.com A 202.59.161.235 1800s
21cineplex.com NS  dns3.name-services.com 3600s
21cineplex.com MX
preference: 10
exchange: mail.21cineplex.com
1800s

Authority records

Additional records

IP 202.59.161.235 Analysis

  • Country Code
    ID
  • Country Code3
    IDN
  • Country Name
    Indonesia
  • City
    Jakarta
  • Continent Code
    AS
  • Latitude
    6.1744
  • Longitude
    106.8294
  • % [whois.apnic.net node-1]
    % Whois data copyright terms http://www.apnic.net/db/dbcopyright.html

    inetnum: 202.59.161.224 - 202.59.161.255
    netname: NAPINFO-Colo
    descr: PT. NAP Info Lintas Nusa
    descr: Suite 101 AB Annes Bldg., Plaza Kuningan
    descr: Jl. H.R Rasuna Said Kav. C11-14
    descr: Jakarta 12940
    country: ID
    admin-c: SH144-AP
    tech-c: GW8177-AP
    status: ASSIGNED NON-PORTABLE
    mnt-by: MAINT-ID-NAPINFO
    changed: noc@nap.net.id 20070712
    source: APNIC

    route: 202.59.160.0/20
    descr: Route Object of NAP.Net.id - Network Access Point
    origin: AS17727
    mnt-by: MAINT-ID-NAPINFO
    changed: hm-changed@apnic.net 20070319
    source: APNIC

    person: Sandi Gunawan Ho
    nic-hdl: SH144-AP
    e-mail: sandy@nap.net.id
    address: PT. NAP Info Lintas Nusa
    address: Suite 101 AB Annex Building, Plaza Kuningan
    address: H.R. Rasuna Said, Kav. C 11-14.
    address: Jakarta Selatan, DKI 12940
    phone: +62-(21)-252-8888
    fax-no: +62-(21)-252-5555
    country: ID
    changed: hostmaster@nap.net.id 20060124
    mnt-by: MAINT-ID-INTER
    source: APNIC

    person: Gunawan Wicaksono
    nic-hdl: GW8177-AP
    e-mail: gunawan@nap.net.id
    address: PT. NAP Info Lintas Nusa
    address: Suite 101 AB Annex Building, Plaza Kuningan.
    address: Jalan. H.R. Rasuna Said, Kav. C 11-14.
    address: Jakarta Selatan, DKI 12940
    phone: +62-(21)-252-8888
    fax-no: +62-(21)-252-5555
    country: ID
    changed: hostmaster@nap.net.id 20070321
    mnt-by: MAINT-ID-NAPINFO
    source: APNIC


In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 108 Errors
  • 11 Warnings
Ratio Text/Html
  • 0.6189347000178484
Message Error
  • Error Line 87, Column 97: document type does not allow element "img" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "address", "fieldset", "ins", "del" start-tag
    ….effectivemeasure.net/em_image" alt="" style="position:absolute; left:-5px;" />

    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 95, Column 95: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …<input type="hidden" name="cx" value="partner-pub-0638543342152890:2138330900">

    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 95, Column 96: end tag for "input" omitted, but OMITTAG NO was specified
    …<input type="hidden" name="cx" value="partner-pub-0638543342152890:2138330900">

    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 95, Column 17: start tag was here
                    <input type="hidden" name="cx" value="partner-pub-0638543342152…
  • Error Line 96, Column 65: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
                    <input type="hidden" name="cof" value="FORID:10">

    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 96, Column 66: end tag for "input" omitted, but OMITTAG NO was specified
                    <input type="hidden" name="cof" value="FORID:10">

    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 96, Column 17: start tag was here
                    <input type="hidden" name="cof" value="FORID:10">
  • Error Line 97, Column 61: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
                    <input type="hidden" name="ie" value="UTF-8">

    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 97, Column 62: end tag for "input" omitted, but OMITTAG NO was specified
                    <input type="hidden" name="ie" value="UTF-8">

    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 97, Column 17: start tag was here
                    <input type="hidden" name="ie" value="UTF-8">
  • Error Line 98, Column 59: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
                    <input type="text" name="q" class="srctxt">

    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 98, Column 60: end tag for "input" omitted, but OMITTAG NO was specified
                    <input type="text" name="q" class="srctxt">

    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 98, Column 17: start tag was here
                    <input type="text" name="q" class="srctxt">
  • Error Line 99, Column 67: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
                    <input type="submit" name="sa" value="" class="go">

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

    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 99, Column 17: start tag was here
                    <input type="submit" name="sa" value="" class="go">
  • Error Line 103, Column 78: there is no attribute "target"
    …21cineplex.com/feeds/news.xml" target="_blank" class="tw"><span>twitter</span>…

    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 108, Column 27: there is no attribute "frameBorder"
    						<iframe frameBorder="0" class="fblogin" src="http://www.21cineplex.com/ap…

    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 108, Column 37: there is no attribute "class"
    						<iframe frameBorder="0" class="fblogin" src="http://www.21cineplex.com/ap…

    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 108, Column 51: there is no attribute "src"
    …e frameBorder="0" class="fblogin" src="http://www.21cineplex.com/apis/fblogin/…

    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 108, Column 109: there is no attribute "scrolling"
    …n" src="http://www.21cineplex.com/apis/fblogin/?xs=71" scrolling="no"></iframe>

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

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

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

  • Error Line 108, Column 113: element "iframe" undefined
    …n" src="http://www.21cineplex.com/apis/fblogin/?xs=71" scrolling="no"></iframe>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 110, Column 7: document type does not allow element "p" here; missing one of "object", "ins", "del", "map", "button" start-tag
    				<p><a href="http://www.21cineplex.com/signup">Sign Up</a>&nbsp;&nbsp;&nbsp;…

    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 111, Column 43: document type does not allow element "form" here; missing one of "object", "ins", "del", "map" start-tag
    …<form method="post" action="login.php"><input type="text" id="email" class="lo…

    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 111, Column 119: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …login-txt" value="Email" name="email" ><input id="password" name="password" ty…

    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 111, Column 120: end tag for "input" omitted, but OMITTAG NO was specified
    …ogin-txt" value="Email" name="email" ><input id="password" name="password" typ…

    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 111, Column 44: start tag was here
    …form method="post" action="login.php"><input type="text" id="email" class="log…
  • Error Line 111, Column 207: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …rd" class="login-txt" value="password"> <input type="submit" class="btn-login"…

    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 111, Column 208: end tag for "input" omitted, but OMITTAG NO was specified
    …d" class="login-txt" value="password"> <input type="submit" class="btn-login" …

    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 111, Column 120: start tag was here
    …ogin-txt" value="Email" name="email" ><input id="password" name="password" typ…
  • Error Line 111, Column 256: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …-txt" value="password"> <input type="submit" class="btn-login" value=""></form>

    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 111, Column 263: end tag for "input" omitted, but OMITTAG NO was specified
    …-txt" value="password"> <input type="submit" class="btn-login" value=""></form>

    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 111, Column 209: start tag was here
    …" class="login-txt" value="password"> <input type="submit" class="btn-login" v…
  • Error Line 126, Column 25: there is no attribute "rel"
                    <li rel="1">

    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 170, Column 70: syntax of attribute value does not conform to declared value
    …="http://www.21cineplex.com/nowplaying" id=""><span>NOW PLAYING</span></a></li>

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 171, Column 70: syntax of attribute value does not conform to declared value
    …="http://www.21cineplex.com/comingsoon" id=""><span>COMING SOON</span></a></li>

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 172, Column 68: syntax of attribute value does not conform to declared value
    …href="http://www.21cineplex.com/theaters" id=""><span>THEATERS</span></a></li>	

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 173, Column 31: syntax of attribute value does not conform to declared value
    		<li class="mn6 drop"><a id="" href="http://www.21cineplex.com/news"><span>INF…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 174, Column 26: end tag for element "a" which is not open
    			<!--[if IE 7]><!--></a><!--<![endif]-->

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

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

  • Error Line 183, Column 67: syntax of attribute value does not conform to declared value
    …><a href="http://www.21cineplex.com/inframe" id=""><span>MOVIE NEWS</span></li>

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 183, Column 96: end tag for "a" omitted, but OMITTAG NO was specified
    …><a href="http://www.21cineplex.com/inframe" id=""><span>MOVIE NEWS</span></li>

    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 183, Column 19: start tag was here
    		<li class="mn5"><a href="http://www.21cineplex.com/inframe" id=""><span>MOVIE…
  • Error Line 184, Column 26: syntax of attribute value does not conform to declared value
    		<li class="mn7"><a id="" href="http://www.21cineplex.com/video"><span>VIDEO</…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 186, Column 132: required attribute "alt" not specified
    … src="http://www.21cineplex.com/imax_page/images/imaxmini.jpg"></span></a></li>

    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 186, Column 139: end tag for "img" omitted, but OMITTAG NO was specified
    … src="http://www.21cineplex.com/imax_page/images/imaxmini.jpg"></span></a></li>

    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 186, Column 66: start tag was here
    …http://www.21cineplex.com/imax"><span><img src="http://www.21cineplex.com/imax…
  • Error Line 214, Column 30: end tag for "ul" which is not finished
    		<ul id="twitterfeed-c"></ul>

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

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

  • Error Line 225, Column 33: document type does not allow element "h3" here; missing one of "object", "ins", "del", "map", "button" start-tag
    			<h3 style="padding:5px 30px;">Silver Linings Playbook</h3></a>

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

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

  • Error Line 231, Column 33: document type does not allow element "h3" here; missing one of "object", "ins", "del", "map", "button" start-tag
    			<h3 style="padding:5px 30px;">WARM BODIES</h3></a>

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

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

  • Error Line 237, Column 33: document type does not allow element "h3" here; missing one of "object", "ins", "del", "map", "button" start-tag
    			<h3 style="padding:5px 30px;">BELENGGU</h3></a>

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

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

  • Error Line 243, Column 33: document type does not allow element "h3" here; missing one of "object", "ins", "del", "map", "button" start-tag
    			<h3 style="padding:5px 30px;">SULE DETEKTIF TOKEK</h3></a>

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

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

  • Error Line 249, Column 33: document type does not allow element "h3" here; missing one of "object", "ins", "del", "map", "button" start-tag
    			<h3 style="padding:5px 30px;">Japan Anime + J-Pop Week Di Indonesia</h3></a>

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

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

  • Error Line 255, Column 33: document type does not allow element "h3" here; missing one of "object", "ins", "del", "map", "button" start-tag
    			<h3 style="padding:5px 30px;">IRON MAN 3</h3></a>

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

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

  • Error Line 286, Column 41: required attribute "action" not specified
    			<form id="frmMoviegator" method="get">

    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 287, Column 44: document type does not allow element "select" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    			<select name="moviesearch" id="mvsearch">

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

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

  • Error Line 290, Column 84: document type does not allow element "select" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …elect name="moviesearch2" id="mvsearch2" style="display:none;margin-top: 2px;">

    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 293, Column 54: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    			<input type="submit" name="go" value="" class="go">

    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 293, Column 55: end tag for "input" omitted, but OMITTAG NO was specified
    			<input type="submit" name="go" value="" class="go">

    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 293, Column 4: start tag was here
    			<input type="submit" name="go" value="" class="go">
  • Error Line 297, Column 42: required attribute "action" not specified
    			<form id="frmMoviegator2" method="get">

    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 298, Column 45: document type does not allow element "select" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    			<select name="teatersearch" id="thsearch">

    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 301, Column 86: document type does not allow element "select" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …ect name="theatersearch2" id="thsearch2" style="display:none;margin-top: 2px;">

    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 304, Column 60: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    			<input type="submit" name="go" value="" class="go right">

    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 304, Column 61: end tag for "input" omitted, but OMITTAG NO was specified
    			<input type="submit" name="go" value="" class="go right">

    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 304, Column 4: start tag was here
    			<input type="submit" name="go" value="" class="go right">
  • Warning Line 311, Column 18: character "&" is the first character of a delimiter but occurred as data
    						if((!inPrg)&&(cidy!="")){

    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 311, Column 19: character "&" is the first character of a delimiter but occurred as data
    						if((!inPrg)&&(cidy!="")){

    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 324, Column 19: character "&" is the first character of a delimiter but occurred as data
    						if((!inPrg2)&&(civy!="")){

    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 324, Column 20: character "&" is the first character of a delimiter but occurred as data
    						if((!inPrg2)&&(civy!="")){

    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 362, Column 95: required attribute "alt" not specified
    …x.21cineplex.com"><img src="images/img-content/mtix.jpg" class="ban145x60"></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 362, Column 99: end tag for "img" omitted, but OMITTAG NO was specified
    …x.21cineplex.com"><img src="images/img-content/mtix.jpg" class="ban145x60"></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 362, Column 39: start tag was here
    	<a href="http://mtix.21cineplex.com"><img src="images/img-content/mtix.jpg" cl…
  • Error Line 401, Column 24: there is no attribute "value"
    			var opts='<li value="77">AMBON</li><li value="12">BANDUNG</li><li value="26"…

    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 401, Column 28: document type does not allow element "li" here
    			var opts='<li value="77">AMBON</li><li value="12">BANDUNG</li><li value="26"…

    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 401, Column 53: document type does not allow element "li" here
    …li value="77">AMBON</li><li value="12">BANDUNG</li><li value="26">BOGOR</li><l…

    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 401, Column 80: document type does not allow element "li" here
    … value="12">BANDUNG</li><li value="26">BOGOR</li><li value="76">BANJARMASIN</l…

    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 401, Column 105: document type does not allow element "li" here
    …li value="26">BOGOR</li><li value="76">BANJARMASIN</li><li value="81">BENGKULU…

    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 401, Column 136: document type does not allow element "li" here
    …ue="76">BANJARMASIN</li><li value="81">BENGKULU</li><li value="36">BEKASI</li>…

    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 401, Column 164: document type does not allow element "li" here
    …value="81">BENGKULU</li><li value="36">BEKASI</li><li value="79">BALIKPAPAN</l…

    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 401, Column 190: document type does not allow element "li" here
    …i value="36">BEKASI</li><li value="79">BALIKPAPAN</li><li value="78">BINJAI</l…

    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 401, Column 220: document type does not allow element "li" here
    …lue="79">BALIKPAPAN</li><li value="78">BINJAI</li><li value="27">BATAM</li><li…

    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 401, Column 246: document type does not allow element "li" here
    …i value="78">BINJAI</li><li value="27">BATAM</li><li value="29">CIKARANG</li><…

    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 401, Column 271: document type does not allow element "li" here
    …li value="27">BATAM</li><li value="29">CIKARANG</li><li value="59">CILEGON</li…

    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 401, Column 299: document type does not allow element "li" here
    …value="29">CIKARANG</li><li value="59">CILEGON</li><li value="61">CIREBON</li>…

    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 401, Column 326: document type does not allow element "li" here
    … value="59">CILEGON</li><li value="61">CIREBON</li><li value="56">DENPASAR</li…

    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 401, Column 353: document type does not allow element "li" here
    … value="61">CIREBON</li><li value="56">DENPASAR</li><li value="3">JAKARTA</li>…

    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 401, Column 380: document type does not allow element "li" here
    … value="56">DENPASAR</li><li value="3">JAKARTA</li><li value="47">JAMBI</li><l…

    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 401, Column 407: document type does not allow element "li" here
    …i value="3">JAKARTA</li><li value="47">JAMBI</li><li value="48">LAMPUNG</li><l…

    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 401, Column 432: document type does not allow element "li" here
    …li value="47">JAMBI</li><li value="48">LAMPUNG</li><li value="25">MEDAN</li><l…

    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 401, Column 459: document type does not allow element "li" here
    … value="48">LAMPUNG</li><li value="25">MEDAN</li><li value="23">MALANG</li><li…

    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 401, Column 484: document type does not allow element "li" here
    …li value="25">MEDAN</li><li value="23">MALANG</li><li value="62">MENADO</li><l…

    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 401, Column 510: document type does not allow element "li" here
    …i value="23">MALANG</li><li value="62">MENADO</li><li value="73">PEKANBARU</li…

    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 401, Column 536: document type does not allow element "li" here
    …i value="62">MENADO</li><li value="73">PEKANBARU</li><li value="50">PALEMBANG<…

    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 401, Column 565: document type does not allow element "li" here
    …alue="73">PEKANBARU</li><li value="50">PALEMBANG</li><li value="80">PALANGKARA…

    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 401, Column 594: document type does not allow element "li" here
    …alue="50">PALEMBANG</li><li value="80">PALANGKARAYA</li><li value="69">PONTIAN…

    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 401, Column 626: document type does not allow element "li" here
    …e="80">PALANGKARAYA</li><li value="69">PONTIANAK</li><li value="55">SURABAYA</…

    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 401, Column 655: document type does not allow element "li" here
    …alue="69">PONTIANAK</li><li value="55">SURABAYA</li><li value="70">SURAKARTA</…

    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 401, Column 683: document type does not allow element "li" here
    …value="55">SURABAYA</li><li value="70">SURAKARTA</li><li value="52">SAMARINDA<…

    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 401, Column 712: document type does not allow element "li" here
    …alue="70">SURAKARTA</li><li value="52">SAMARINDA</li><li value="20">SEMARANG</…

    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 401, Column 741: document type does not allow element "li" here
    …alue="52">SAMARINDA</li><li value="20">SEMARANG</li><li value="35">TANGERANG</…

    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 401, Column 769: document type does not allow element "li" here
    …value="20">SEMARANG</li><li value="35">TANGERANG</li><li value="82">TASIK MALA…

    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 401, Column 798: document type does not allow element "li" here
    …alue="35">TANGERANG</li><li value="82">TASIK MALAYA</li><li value="54">UJUNG P…

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

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

  • Error Line 401, Column 830: document type does not allow element "li" here
    …e="82">TASIK MALAYA</li><li value="54">UJUNG PANDANG</li><li value="75">YOGYAK…

    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 401, Column 863: document type does not allow element "li" here
    …IK MALAYA</li><li value="54">UJUNG PANDANG</li><li value="75">YOGYAKARTA</li>';

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

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

  • Warning Line 448, Column 17: character "&" is the first character of a delimiter but occurred as data
    					if((!inPrg)&&(cid!="")){

    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 448, Column 18: character "&" is the first character of a delimiter but occurred as data
    					if((!inPrg)&&(cid!="")){

    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 460, Column 18: character "&" is the first character of a delimiter but occurred as data
    						if((!inPrg)&&(cid!="")){

    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 460, Column 19: character "&" is the first character of a delimiter but occurred as data
    						if((!inPrg)&&(cid!="")){

    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 531, Column 9: end tag for "p" omitted, but OMITTAG NO was specified
    			</div>

    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 529, Column 6: start tag was here
    					<p>Di saat Elang (Abimana Aryasatya) berusaha mencari pelaku pembunuhan di…
  • Error Line 537, Column 14: there is no attribute "name"
    		<form name="kuis" class="kuis" id="fkuis">

    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 537, Column 44: required attribute "action" not specified
    		<form name="kuis" class="kuis" id="fkuis">

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

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

  • Error Line 538, Column 60: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …" value="1" name="jawab" id="quiz-opt">&nbsp;NICHOLAS HOULT<br /><input type="…

    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 538, Column 61: end tag for "input" omitted, but OMITTAG NO was specified
    … value="1" name="jawab" id="quiz-opt">&nbsp;NICHOLAS HOULT<br /><input type="r…

    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 538, Column 4: start tag was here
    			<input type="radio" value="1" name="jawab" id="quiz-opt">&nbsp;NICHOLAS HOUL…
  • Error Line 538, Column 67: character data is not allowed here
    …="1" name="jawab" id="quiz-opt">&nbsp;NICHOLAS HOULT<br /><input type="radio" …

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

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 538, Column 86: document type does not allow element "br" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …d="quiz-opt">&nbsp;NICHOLAS HOULT<br /><input type="radio" value="2" name="jaw…

    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 538, Column 134: ID "quiz-opt" already defined
    …pe="radio" value="2" name="jawab" id="quiz-opt">&nbsp;EWAN MCGREGOR<br /><inpu…

    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 538, Column 51: ID "quiz-opt" first defined here
    …pe="radio" value="1" name="jawab" id="quiz-opt">&nbsp;NICHOLAS HOULT<br /><inp…
  • Error Line 538, Column 143: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …" value="2" name="jawab" id="quiz-opt">&nbsp;EWAN MCGREGOR<br /><input type="r…

    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 538, Column 144: end tag for "input" omitted, but OMITTAG NO was specified
    … value="2" name="jawab" id="quiz-opt">&nbsp;EWAN MCGREGOR<br /><input type="ra…

    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 538, Column 87: start tag was here
    …="quiz-opt">&nbsp;NICHOLAS HOULT<br /><input type="radio" value="2" name="jawa…
  • Error Line 538, Column 168: document type does not allow element "br" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …id="quiz-opt">&nbsp;EWAN MCGREGOR<br /><input type="radio" value="3" name="jaw…

    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 538, Column 216: ID "quiz-opt" already defined
    …pe="radio" value="3" name="jawab" id="quiz-opt">&nbsp;EDDIE MARSAN<br /><input…

    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 538, Column 51: ID "quiz-opt" first defined here
    …pe="radio" value="1" name="jawab" id="quiz-opt">&nbsp;NICHOLAS HOULT<br /><inp…
  • Error Line 538, Column 225: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …" value="3" name="jawab" id="quiz-opt">&nbsp;EDDIE MARSAN<br /><input type="ra…

    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 538, Column 226: end tag for "input" omitted, but OMITTAG NO was specified
    … value="3" name="jawab" id="quiz-opt">&nbsp;EDDIE MARSAN<br /><input type="rad…

    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 538, Column 169: start tag was here
    …d="quiz-opt">&nbsp;EWAN MCGREGOR<br /><input type="radio" value="3" name="jawa…
  • Error Line 538, Column 249: document type does not allow element "br" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    … id="quiz-opt">&nbsp;EDDIE MARSAN<br /><input type="radio" value="4" name="jaw…

    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 538, Column 297: ID "quiz-opt" already defined
    …pe="radio" value="4" name="jawab" id="quiz-opt">&nbsp;EWEN BREMNER<br /><input…

    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 538, Column 51: ID "quiz-opt" first defined here
    …pe="radio" value="1" name="jawab" id="quiz-opt">&nbsp;NICHOLAS HOULT<br /><inp…
  • Error Line 538, Column 306: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …" value="4" name="jawab" id="quiz-opt">&nbsp;EWEN BREMNER<br /><input type="ra…

    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 538, Column 307: end tag for "input" omitted, but OMITTAG NO was specified
    … value="4" name="jawab" id="quiz-opt">&nbsp;EWEN BREMNER<br /><input type="rad…

    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 538, Column 250: start tag was here
    …id="quiz-opt">&nbsp;EDDIE MARSAN<br /><input type="radio" value="4" name="jawa…
  • Error Line 538, Column 330: document type does not allow element "br" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    … id="quiz-opt">&nbsp;EWEN BREMNER<br /><input type="radio" value="5" name="jaw…

    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 538, Column 378: ID "quiz-opt" already defined
    …pe="radio" value="5" name="jawab" id="quiz-opt">&nbsp;STANLEY TUCCI<br />     …

    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 538, Column 51: ID "quiz-opt" first defined here
    …pe="radio" value="1" name="jawab" id="quiz-opt">&nbsp;NICHOLAS HOULT<br /><inp…
  • Error Line 538, Column 387: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …" value="5" name="jawab" id="quiz-opt">&nbsp;STANLEY TUCCI<br />            <d…

    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 538, Column 388: end tag for "input" omitted, but OMITTAG NO was specified
    … value="5" name="jawab" id="quiz-opt">&nbsp;STANLEY TUCCI<br />            <di…

    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 538, Column 331: start tag was here
    …id="quiz-opt">&nbsp;EWEN BREMNER<br /><input type="radio" value="5" name="jawa…
  • Error Line 538, Column 412: document type does not allow element "br" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …id="quiz-opt">&nbsp;STANLEY TUCCI<br />            <div class="pesan" id="kpes…

    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 539, Column 22: there is no attribute "align"
                <p align="center"><input type="submit" name="submit" value="" class…

    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 539, Column 97: end tag for "input" omitted, but OMITTAG NO was specified
    …r"><input type="submit" name="submit" value="" class="btn-submit"></p>		</form>

    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 539, Column 31: start tag was here
                <p align="center"><input type="submit" name="submit" value="" class…
  • Error Line 543, Column 7: 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 543, Column 7: document type does not allow element "style" here
    <style>

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

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

  • Error Line 595, Column 116: document type does not allow element "h3" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …s-a-good-day-to-die-hard,1802.htm"><h3>PEMENANG KUIS A GOOD DAY TO DIE HARD</h…

    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 595, Column 160: document type does not allow element "p" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …tm"><h3>PEMENANG KUIS A GOOD DAY TO DIE HARD</h3><p>Selamat untuk para pemenang

    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 598, Column 128: document type does not allow element "h3" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …eplex.com/news/mtix-news,1801.htm"><h3>M-TIX NEWS</h3><p>Pembelian tiket via M…

    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 598, Column 146: document type does not allow element "p" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …x-news,1801.htm"><h3>M-TIX NEWS</h3><p>Pembelian tiket via M-TIX hari Jumat, 2…

    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 598, Column 337: document type does not allow element "h3" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …h-dibuka-csb-xxi-cirebon,1800.htm"><h3>TELAH DIBUKA CSB XXI CIREBON</h3><p>TEL…

    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 598, Column 373: document type does not allow element "p" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …h3>TELAH DIBUKA CSB XXI CIREBON</h3><p>TELAH DIBUKA pada hari Jumat, 1 Februar…

    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 605, Column 114: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …murder-3,3069.htm"><div class="play_t"></div><img src="http://www.21cineplex.c…

    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 605, Column 224: required attribute "alt" not specified
    …88765857_130x100.png" class="thumb3" /></a><h3><a href="http://www.21cineplex.…

    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 605, Column 593: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …n-taylor,3068.htm"><div class="play_t"></div><img src="http://www.21cineplex.c…

    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 605, Column 703: required attribute "alt" not specified
    …11089670_130x100.png" class="thumb3" /></a><h3><a href="http://www.21cineplex.…

    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 644, Column 10: ID "wrapper" already defined
    <div id="wrapper">	

    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 90, Column 10: ID "wrapper" first defined here
    <div id="wrapper">
  • Error Line 654, Column 20: end tag for "br" omitted, but OMITTAG NO was specified
    	<br class="clear"><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 654, Column 2: start tag was here
    	<br class="clear"><br>
  • Error Line 654, Column 24: end tag for "br" omitted, but OMITTAG NO was specified
    	<br class="clear"><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 654, Column 20: start tag was here
    	<br class="clear"><br>
  • Error Line 656, Column 99: end tag for "br" omitted, but OMITTAG NO was specified
    … are © Lucasfilm Ltd. TM All rights are reserved. Used under authorization.<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 656, Column 95: start tag was here
    … are © Lucasfilm Ltd. TM All rights are reserved. Used under authorization.<br>
  • Error Line 657, Column 145: end tag for "br" omitted, but OMITTAG NO was specified
    …ny, Sony Dynamic Digital Sound and SDDS are trademarks of Sony Corporation.<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 657, Column 141: start tag was here
    …ny, Sony Dynamic Digital Sound and SDDS are trademarks of Sony Corporation.<br>
  • Error Line 658, Column 186: end tag for "br" omitted, but OMITTAG NO was specified
    …lex or 21Cineplex.com website are copyrights and trademarks of 21Cineplex. <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 658, Column 182: start tag was here
    …lex or 21Cineplex.com website are copyrights and trademarks of 21Cineplex. <br>
  • Error Line 666, Column 27: document type does not allow element "span" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    <span style="display:none">Process time: 0.006751 secs</span></body>

    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>").

Visitor Analysis

Daily Visitor
  • 28.000 visits