1cuk.com

1CAK.com - The new 1CUK For fun Only, The Largest Indonesian fun site with collection of funny pictures, funny quotes, funny videos, jokes and inspirational quotes with meme troll and comics. ...

Display Widget for this domain on your website. Click Here
This data was last updated from 02-08-2013 10:45:08  (update).

Overview Info

  • Domain Name
    1cuk.com
  • Favicon
  • Alexa Rank
    #25180678
  • Google Page Rank
    PR 3
  • Ip Address
    119.81.20.194
  • Page Size
    21.4 KB
  • Images
    0 GIF, 3 JPG, 0 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    0 0 3 0 0 0

Website Meta Analysis



  • Title
    1CAK - For Fun Only
  • Meta Keyword
    1cak,1cuk,just for fun,jokes,lucu, fun, entertainment, interesting, cool,fun collection, fun portfolio, admire,fun,humor,9gag,humour,just for fun, tertawa, kocak, ngakak, stress, koplak
  • Meta Description
    1CAK.com - The new 1CUK For fun Only, The Largest Indonesian fun site with collection of funny pictures, funny quotes, funny videos, jokes and inspirational quotes with meme troll and comics.

Technical Analysis



  • Webserver
    nginx/1.2.8
  • Ip Address
    119.81.20.194
  • Domain Age
    1 Years, 5 Months, 14 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • server: nginx/1.2.8
  • date: Fri, 02 Aug 2013 10:45:04 GMT
  • content-type: text/html
  • connection: keep-alive
  • x-powered-by: PHP/5.5.0beta3
  • cache-control: no-cache, must-revalidate
  • expires: Sat, 26 Jul 1997 05:00:00 GMT
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for 1cuk.com

DNS Analysis


DNS servers
manage1.rumahweb.com [50.23.136.173]
manage2.rumahweb.com [50.23.75.44]
manage3.rumahweb.com [67.15.253.219]


DNS Records

Answer records
1cuk.com NS  manage1.rumahweb.com 38400s
1cuk.com MX
preference: 10
exchange: aspmx2.googlemail.com
28800s
1cuk.com MX
preference: 5
exchange: alt1.aspmx.l.google.com
28800s
1cuk.com NS  manage3.rumahweb.com 38400s
1cuk.com NS  manage2.rumahweb.com 38400s
1cuk.com MX
preference: 10
exchange: aspmx3.googlemail.com
28800s
1cuk.com MX
preference: 1
exchange: aspmx.l.google.com
28800s
1cuk.com A 119.81.20.194 28800s
1cuk.com SOA
server: manage1.rumahweb.com
email: adjiexx@gmail.com
serial: 2012111702
refresh: 7200
retry: 7200
expire: 172800
minimum ttl: 7200
38400s
1cuk.com MX
preference: 5
exchange: alt2.aspmx.l.google.com
28800s
1cuk.com NS  manage4.rumahweb.com 38400s

Authority records

Additional records

IP 119.81.20.194 Analysis

  • Country Code
    CN
  • Country Code3
    CHN
  • Country Name
    China
  • City
    Langfang
  • Continent Code
    AS
  • Latitude
    39.5097
  • Longitude
    116.6947
  • % [whois.apnic.net node-4]
    % Whois data copyright terms http://www.apnic.net/db/dbcopyright.html

    inetnum: 119.81.0.0 - 119.81.255.255
    netname: SOFTLAYER-AP
    descr: SoftLayer Dutch Holdings B.V.
    descr: Keplerstaat 34
    country: SG
    admin-c: SDHB1-AP
    tech-c: SDHB1-AP
    mnt-by: APNIC-HM
    mnt-lower: MAINT-SOFTLAYER-AP
    mnt-routes: MAINT-SOFTLAYER-AP
    mnt-irt: IRT-SOFTLAYER-AP
    status: ALLOCATED PORTABLE
    changed: hm-changed@apnic.net 20120410
    source: APNIC

    role: SOFTLAYER DUTCH HOLDINGS BV - network administra
    address: Keplerstaat 34, 1171CD Badhoevedorp
    country: NL
    phone: +1-214-442-0600
    e-mail: networking@softlayer.com
    admin-c: SDHB1-AP
    tech-c: SDHB1-AP
    nic-hdl: SDHB1-AP
    mnt-by: MAINT-SOFTLAYER-AP
    changed: hm-changed@apnic.net 20110823
    source: APNIC


Site Same Ip

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 116 Errors
  • 15 Warnings
Ratio Text/Html
  • 0.6015353683056114
Message Error
  • Error Line 7, Column 12: there is no attribute "NAME"
    <META NAME="Keywords" content="1cak,1cuk,just for fun,jokes,lucu, fun, entertai…

    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 7, Column 31: there is no attribute "content"
    <META NAME="Keywords" content="1cak,1cuk,just for fun,jokes,lucu, fun, entertai…

    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 7, Column 219: element "META" undefined
    …,fun,humor,9gag,humour,just for fun, tertawa, kocak, ngakak, stress, koplak "> 

    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 8, Column 230: element "META" undefined
    … funny videos, jokes and inspirational quotes with meme troll and comics.  "/> 

    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 9, Column 45: element "META" undefined
    <META NAME="revisit-after" content="1 days"/> 

    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 10, Column 49: element "META" undefined
    <META NAME="author" content="1cak.com,1cuk.com"/> 

    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 11, Column 59: element "META" undefined
    <META NAME="owner" content="1cak,1cak.com,1cuk, 1cuk.com"/> 

    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 12, Column 44: element "META" undefined
    <META NAME="distribution" content="global"/> 

    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 17, Column 16: there is no attribute "property"
    <meta property="fb:app_id" content="342379812518937"/>

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

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

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

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

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

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

  • Error Line 94, Column 7: end tag for "META" omitted, but OMITTAG NO was specified
    </head>

    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 7, Column 1: start tag was here
    <META NAME="Keywords" content="1cak,1cuk,just for fun,jokes,lucu, fun, entertai…
  • Error Line 94, Column 7: end tag for "head" which is not finished
    </head>

    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 102, Column 8: required attribute "type" not specified
    <script>

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

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

  • Warning Line 107, Column 71: cannot generate system identifier for general entity "appId"
    …"//connect.facebook.net/en_US/all.js?t=20120910#xfbml=1&appId=342379812518937";

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

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

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

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

  • Error Line 107, Column 71: general entity "appId" not defined and no default entity
    …"//connect.facebook.net/en_US/all.js?t=20120910#xfbml=1&appId=342379812518937";

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

  • Warning Line 107, Column 76: reference not terminated by REFC delimiter
    …"//connect.facebook.net/en_US/all.js?t=20120910#xfbml=1&appId=342379812518937";

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Error Line 107, Column 76: reference to entity "appId" for which no system identifier could be generated
    …"//connect.facebook.net/en_US/all.js?t=20120910#xfbml=1&appId=342379812518937";

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

  • Info Line 107, Column 70: entity was defined here
    …"//connect.facebook.net/en_US/all.js?t=20120910#xfbml=1&appId=342379812518937";
  • Error Line 129, Column 296: end tag for "input" omitted, but OMITTAG NO was specified
    …ch_icon.gif);background-repeat:no-repeat;background-position:178px 4px;"></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 129, Column 84: start tag was here
    …ne;text-align:left;padding-left:5px" ><input id="searchText" onclick="return f…
  • Error Line 141, Column 12: ID "sddm" already defined
       <ul id="sddm">

    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 120, Column 12: ID "sddm" first defined here
       <ul id="sddm">
  • Error Line 189, Column 10: required attribute "type" not specified
      <script>

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

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

  • Warning Line 194, Column 20: cannot generate system identifier for general entity "setSave"
    	   $.get("/recent&setSave="+saveNum,function(data){

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

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

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

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

  • Error Line 194, Column 20: general entity "setSave" not defined and no default entity
    	   $.get("/recent&setSave="+saveNum,function(data){

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

  • Warning Line 194, Column 27: reference not terminated by REFC delimiter
    	   $.get("/recent&setSave="+saveNum,function(data){

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Error Line 194, Column 27: reference to entity "setSave" for which no system identifier could be generated
    	   $.get("/recent&setSave="+saveNum,function(data){

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

  • Info Line 194, Column 19: entity was defined here
    	   $.get("/recent&setSave="+saveNum,function(data){
  • Error Line 203, Column 178: there is no attribute "width"
    …r><td style='overflow-x:hidden' width='472' align='center'><div rel='161713' c…

    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 203, Column 208: there is no attribute "rel"
    …' width='472' align='center'><div rel='161713' class='upperSpan' id='upper_spa…

    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 203, Column 328: end tag for "input" omitted, but OMITTAG NO was specified
    …ray' type='hidden' value='1361020175'><a href='/161713' target='_blank'><img t…

    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 203, Column 264: start tag was here
    …perSpan' id='upper_span_161713'></div><input class='post_time_array' type='hid…
  • Error Line 203, Column 353: there is no attribute "target"
    …'1361020175'><a href='/161713' target='_blank'><img title='Mas Bagus Setiawan …

    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 203, Column 423: there is no attribute "onload"
    …etiawan diajakin dinner Pacar' onload="if(this.width > 453) {this.width=453}" …

    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 203, Column 515: required attribute "alt" not specified
    …1a44e61b9df7cdf473224cec654341_t.jpg' ></a><div  style='background:#fff;height…

    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 203, Column 519: end tag for "img" omitted, but OMITTAG NO was specified
    …e61b9df7cdf473224cec654341_t.jpg' ></a><div  style='background:#fff;height:23p…

    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 203, Column 362: start tag was here
    …75'><a href='/161713' target='_blank'><img title='Mas Bagus Setiawan diajakin …
  • Error Line 203, Column 840: document type does not allow element "h3" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …t='_blank'><h3 style='margin-top:-4px'>Mas Bagus Setiawan Diajakin Dinner Paca…

    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 205, Column 56: end tag for "br" omitted, but OMITTAG NO was specified
    							<div class='blur'>from kisah mas bagus <br></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 205, Column 47: start tag was here
    							<div class='blur'>from kisah mas bagus <br></div> 
  • Error Line 207, Column 103: end tag for "br" omitted, but OMITTAG NO was specified
    …Button_161713'  onclick="nope('161713','/')" class='nopeStyle'>Nuf</button><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 207, Column 99: start tag was here
    …Button_161713'  onclick="nope('161713','/')" class='nopeStyle'>Nuf</button><br>
  • Warning Line 209, Column 92: cannot generate system identifier for general entity "post_id"
    …ass='blur' onclick="$.get('votedetail&post_id=161713',function(data){ $('#vote…

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

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

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

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

  • Error Line 209, Column 92: general entity "post_id" not defined and no default entity
    …ass='blur' onclick="$.get('votedetail&post_id=161713',function(data){ $('#vote…

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

  • Warning Line 209, Column 99: reference not terminated by REFC delimiter
    …ur' onclick="$.get('votedetail&post_id=161713',function(data){ $('#votedtl_161…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 209, Column 99: reference to external entity in attribute value
    …ur' onclick="$.get('votedetail&post_id=161713',function(data){ $('#votedtl_161…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 209, Column 99: reference to entity "post_id" for which no system identifier could be generated
    …ur' onclick="$.get('votedetail&post_id=161713',function(data){ $('#votedtl_161…

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

  • Info Line 209, Column 91: entity was defined here
    …lass='blur' onclick="$.get('votedetail&post_id=161713',function(data){ $('#vot…
  • Error Line 209, Column 232: there is no attribute "href"
    …</span> funs, <fb:comments-count href=http://1cak.com/161713></fb:comments-cou…

    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 209, Column 232: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …</span> funs, <fb:comments-count href=http://1cak.com/161713></fb:comments-cou…
  • Error Line 209, Column 238: NET-enabling start-tag not immediately followed by null end-tag
    …> funs, <fb:comments-count href=http://1cak.com/161713></fb:comments-count> co…

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

  • Error Line 209, Column 238: element "fb:comments-count" undefined
    …> funs, <fb:comments-count href=http://1cak.com/161713></fb:comments-count> co…

    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 209, Column 274: end tag for element "fb:comments-count" which is not open
    …comments-count href=http://1cak.com/161713></fb:comments-count> comments</div>	

    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 212, Column 65: there is no attribute "data-href"
    …" style="margin-bottom:5px" data-href="http://1cak.com/161713" data-send="fals…

    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 212, Column 100: there is no attribute "data-send"
    …ef="http://1cak.com/161713" data-send="false" data-layout="button_count" data-…

    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 212, Column 120: there is no attribute "data-layout"
    …161713" data-send="false" data-layout="button_count" data-width="100" data-sho…

    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 212, Column 146: there is no attribute "data-width"
    …data-layout="button_count" data-width="100" data-show-faces="true" data-action…

    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 212, Column 168: there is no attribute "data-show-faces"
    …n_count" data-width="100" data-show-faces="true" data-action="recommend"></div>

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

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

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

  • Error Line 212, Column 187: there is no attribute "data-action"
    …n_count" data-width="100" data-show-faces="true" data-action="recommend"></div>

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

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

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

  • Error Line 215, Column 83: there is no attribute "data-url"
    …class="twitter-share-button" data-url="http://1cak.com/161713" data-text="Mas …

    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 215, Column 118: there is no attribute "data-text"
    …rl="http://1cak.com/161713" data-text="Mas Bagus Setiawan diajakin dinner Paca…

    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 215, Column 169: there is no attribute "related"
    …data-text="Mas Bagus Setiawan diajakin dinner Pacar" related="onecak">Tweet</a>

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

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

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

  • Error Line 226, Column 349: end tag for "input" omitted, but OMITTAG NO was specified
    …ray' type='hidden' value='1361018655'><a href='/161674' target='_blank'><img t…

    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 226, Column 285: start tag was here
    …perSpan' id='upper_span_161674'></div><input class='post_time_array' type='hid…
  • Error Line 226, Column 528: required attribute "alt" not specified
    …adfac1457e53598d5f89a41082ac76_t.jpg' ></a><div  style='background:#fff;height…

    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 226, Column 532: end tag for "img" omitted, but OMITTAG NO was specified
    …c1457e53598d5f89a41082ac76_t.jpg' ></a><div  style='background:#fff;height:23p…

    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 226, Column 383: start tag was here
    …55'><a href='/161674' target='_blank'><img title='Just farhat abbas business m…
  • Error Line 226, Column 865: document type does not allow element "h3" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …t='_blank'><h3 style='margin-top:-4px'>Just Farhat Abbas Business Model</h3></…

    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 230, Column 103: end tag for "br" omitted, but OMITTAG NO was specified
    …Button_161674'  onclick="nope('161674','/')" class='nopeStyle'>Nuf</button><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 230, Column 99: start tag was here
    …Button_161674'  onclick="nope('161674','/')" class='nopeStyle'>Nuf</button><br>
  • Warning Line 232, Column 99: reference not terminated by REFC delimiter
    …ur' onclick="$.get('votedetail&post_id=161674',function(data){ $('#votedtl_161…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 232, Column 99: reference to external entity in attribute value
    …ur' onclick="$.get('votedetail&post_id=161674',function(data){ $('#votedtl_161…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 232, Column 99: reference to entity "post_id" for which no system identifier could be generated
    …ur' onclick="$.get('votedetail&post_id=161674',function(data){ $('#votedtl_161…

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

  • Info Line 209, Column 91: entity was defined here
    …lass='blur' onclick="$.get('votedetail&post_id=161713',function(data){ $('#vot…
  • Error Line 232, Column 232: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …</span> funs, <fb:comments-count href=http://1cak.com/161674></fb:comments-cou…
  • Error Line 232, Column 238: NET-enabling start-tag not immediately followed by null end-tag
    …> funs, <fb:comments-count href=http://1cak.com/161674></fb:comments-count> co…

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

  • Error Line 232, Column 238: element "fb:comments-count" undefined
    …> funs, <fb:comments-count href=http://1cak.com/161674></fb:comments-count> co…

    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 232, Column 274: end tag for element "fb:comments-count" which is not open
    …comments-count href=http://1cak.com/161674></fb:comments-count> comments</div>	

    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 249, Column 349: end tag for "input" omitted, but OMITTAG NO was specified
    …ray' type='hidden' value='1361018104'><a href='/161652' target='_blank'><img t…

    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 249, Column 285: start tag was here
    …perSpan' id='upper_span_161652'></div><input class='post_time_array' type='hid…
  • Error Line 249, Column 532: required attribute "alt" not specified
    …8e3f9055bd3e1bd48719f789946fc4_t.jpg' ></a><div  style='background:#fff;height…

    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 249, Column 536: end tag for "img" omitted, but OMITTAG NO was specified
    …9055bd3e1bd48719f789946fc4_t.jpg' ></a><div  style='background:#fff;height:23p…

    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 249, Column 383: start tag was here
    …04'><a href='/161652' target='_blank'><img title='Mengenang Peristiwa 10 Novem…
  • Error Line 249, Column 865: document type does not allow element "h3" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …t='_blank'><h3 style='margin-top:-4px'>Mengenang Peristiwa 10 November 1945</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 253, Column 103: end tag for "br" omitted, but OMITTAG NO was specified
    …Button_161652'  onclick="nope('161652','/')" class='nopeStyle'>Nuf</button><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 253, Column 99: start tag was here
    …Button_161652'  onclick="nope('161652','/')" class='nopeStyle'>Nuf</button><br>
  • Warning Line 255, Column 99: reference not terminated by REFC delimiter
    …ur' onclick="$.get('votedetail&post_id=161652',function(data){ $('#votedtl_161…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 255, Column 99: reference to external entity in attribute value
    …ur' onclick="$.get('votedetail&post_id=161652',function(data){ $('#votedtl_161…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 255, Column 99: reference to entity "post_id" for which no system identifier could be generated
    …ur' onclick="$.get('votedetail&post_id=161652',function(data){ $('#votedtl_161…

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

  • Info Line 209, Column 91: entity was defined here
    …lass='blur' onclick="$.get('votedetail&post_id=161713',function(data){ $('#vot…
  • Error Line 255, Column 231: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …</span> funs, <fb:comments-count href=http://1cak.com/161652></fb:comments-cou…
  • Error Line 255, Column 237: NET-enabling start-tag not immediately followed by null end-tag
    …> funs, <fb:comments-count href=http://1cak.com/161652></fb:comments-count> co…

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

  • Error Line 255, Column 237: element "fb:comments-count" undefined
    …> funs, <fb:comments-count href=http://1cak.com/161652></fb:comments-count> co…

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 255, Column 273: end tag for element "fb:comments-count" which is not open
    …comments-count href=http://1cak.com/161652></fb:comments-count> comments</div>	

    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 275, Column 10: required attribute "type" not specified
      <script>

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

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

  • Error Line 297, Column 53: there is no attribute "href"
    …nt_div_'+pid).html("<fb:comments href='http://"+domain+"/"+pid+"' num-posts='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 297, Column 91: there is no attribute "num-posts"
    …s href='http://"+domain+"/"+pid+"' num-posts='15' width='470'></fb:comments>");

    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 297, Column 102: there is no attribute "width"
    …s href='http://"+domain+"/"+pid+"' num-posts='15' width='470'></fb:comments>");

    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 297, Column 107: element "fb:comments" undefined
    …s href='http://"+domain+"/"+pid+"' num-posts='15' width='470'></fb:comments>");

    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 327, Column 37: character ")" not allowed in attribute specification list
    	  if(curPostArrayIdx<postArrayIdx-1){
  • Error Line 327, Column 37: element "postArrayIdx-1" undefined
    	  if(curPostArrayIdx<postArrayIdx-1){

    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 391, Column 11: end tag for "postArrayIdx-1" omitted, but OMITTAG NO was specified
      </script>

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

  • Info Line 327, Column 22: start tag was here
    	  if(curPostArrayIdx<postArrayIdx-1){
  • Error Line 407, Column 5: end tag for "hr" omitted, but OMITTAG NO was specified
    <hr><center><input type='button' onclick="window.location='/register';" class='…

    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 407, Column 1: start tag was here
    <hr><center><input type='button' onclick="window.location='/register';" class='…
  • Error Line 407, Column 12: element "center" undefined
    <hr><center><input type='button' onclick="window.location='/register';" class='…

    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 407, Column 160: end tag for "input" omitted, but OMITTAG NO was specified
    …ickable' style='background-color:#3B5998' value='Login with Facebook'></center>

    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 407, Column 13: start tag was here
    <hr><center><input type='button' onclick="window.location='/register';" class='…
  • Error Line 409, Column 5: end tag for "hr" omitted, but OMITTAG NO was specified
    <hr>Tertawa adalah tanda bahagia, tapi akan lebih bahagia jika anda bisa membua…

    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 409, Column 1: start tag was here
    <hr>Tertawa adalah tanda bahagia, tapi akan lebih bahagia jika anda bisa membua…
  • Error Line 409, Column 107: end tag for "br" omitted, but OMITTAG NO was specified
    …bisa membuat orang lain tertawa.. <br> -Einstein- <br>So, mari berbagi tawa de…

    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 409, Column 103: start tag was here
    …nda bisa membuat orang lain tertawa.. <br> -Einstein- <br>So, mari berbagi taw…
  • Error Line 409, Column 123: end tag for "br" omitted, but OMITTAG NO was specified
    …ng lain tertawa.. <br> -Einstein- <br>So, mari berbagi tawa dengan <a href='/u…

    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 409, Column 119: start tag was here
    … orang lain tertawa.. <br> -Einstein- <br>So, mari berbagi tawa dengan <a href…
  • Error Line 409, Column 172: element "u" undefined
    …rbagi tawa dengan <a href='/upload'><u>mensubmit</u></a> something fun.. <br>T…

    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 409, Column 211: end tag for "br" omitted, but OMITTAG NO was specified
    …mensubmit</u></a> something fun.. <br>This is Just for fun only. The Largest I…

    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 409, Column 207: start tag was here
    …><u>mensubmit</u></a> something fun.. <br>This is Just for fun only. The Large…
  • Error Line 413, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <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 413, Column 1: start tag was here
    <br>
  • Error Line 420, Column 84: there is no attribute "data-show-count"
    …twitter-follow-button" data-show-count="true" data-lang="en">Follow @onecak</a>

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

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

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

  • Error Line 420, Column 101: there is no attribute "data-lang"
    …twitter-follow-button" data-show-count="true" data-lang="en">Follow @onecak</a>

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

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

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

  • Error Line 423, Column 23: there is no attribute "annotation"
    <g:plusone annotation="inline"  href="http://1cuk.com"></g:plusone>

    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 423, Column 38: there is no attribute "href"
    <g:plusone annotation="inline"  href="http://1cuk.com"></g:plusone>

    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 423, Column 55: element "g:plusone" undefined
    <g:plusone annotation="inline"  href="http://1cuk.com"></g:plusone>

    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 433, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <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 433, Column 1: start tag was here
    <br>
  • Error Line 453, Column 5: end tag for "hr" omitted, but OMITTAG NO was specified
    <hr>

    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 453, Column 1: start tag was here
    <hr>
  • Error Line 468, Column 5: end tag for "hr" omitted, but OMITTAG NO was specified
    <hr>

    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 468, Column 1: start tag was here
    <hr>
  • Error Line 495, Column 8: required attribute "type" not specified
    <script>

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

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

  • Warning Line 506, Column 20: character "&" is the first character of a delimiter but occurred as data
    	if(scrolT>likeTop && !rightPositioned){

    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 506, Column 21: character "&" is the first character of a delimiter but occurred as data
    	if(scrolT>likeTop && !rightPositioned){

    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 514, Column 19: character ")" not allowed in attribute specification list
    	if(scrolT<likeTop){ 
  • Error Line 514, Column 19: element "likeTop" undefined
    	if(scrolT<likeTop){ 

    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 526, Column 9: end tag for "likeTop" omitted, but OMITTAG NO was specified
    </script>

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

  • Info Line 514, Column 11: start tag was here
    	if(scrolT<likeTop){ 

Visitor Analysis

Daily Visitor
  • 2 visits

In Page Analysis