Dapatkan Promo terbaik dan Diskon terbesar untuk member LivingSocial. Nikmati makanan terlezat dan pengalaman tak terlupakan dengan Promo LivingSocial yang pasti Murah ...

livingsocial.co.id
  • Domain Name
    livingsocial.co.id
  • Favicon
  • Google Page Rank
    3
  • Alexa Rank
    #19932
  • Page Size
    225.8 KB
  • Ip Address
    183.91.70.244
  • Heading
    H1: 0, H2: 0, H3: 4, H4: 0, H5: 0, H6: 0
  • Images
    0 GIF, 60 JPG, 1 PNG

Website Meta Analysis

  • Title
    Livingsocial Indonesia
  • Meta Keyword
    deal, kupon, vocer, diskon, promo, promosi
  • Meta Description
    Dapatkan Promo terbaik dan Diskon terbesar untuk member LivingSocial. Nikmati makanan terlezat dan pengalaman tak terlupakan dengan Promo LivingSocial yang pasti Murah

Technical Analysis

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

Hyper Text Transfer Protocol (HTTP) header show data header response from livingsocial.co.id.

HTML Analysis

  • server: nginx
  • date: Fri, 01 Mar 2013 09:35:14 GMT
  • content-type: text/html; charset=UTF-8
  • connection: keep-alive
  • x-varnish: 1577509142 1577508996
  • age: 63
  • via: 1.1 varnish
  • x-cache: HIT (5)
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
No data whois for livingsocial.co.id

DNS Analysis


DNS servers
ns10.zoneedit.com [131.203.126.171]
ns2.rackspace.com [65.61.188.4]
ns19.zoneedit.com [74.50.27.56]
ns.rackspace.com [69.20.95.4]


DNS Records

Answer records
livingsocial.co.id SOA
server: ns.rackspace.com
email: hostmaster@rackspace.com
serial: 1358416663
refresh: 3600
retry: 300
expire: 1814400
minimum ttl: 300
300s
livingsocial.co.id A 183.91.70.244 86400s
livingsocial.co.id MX
preference: 10
exchange: mx.eemms.net
86400s
livingsocial.co.id NS  ns2.rackspace.com 86400s
livingsocial.co.id NS  ns.rackspace.com 86400s
livingsocial.co.id TXT v=spf1 include:emarsys.net include:emsmtp.com ~all 86400s

Authority records

Additional records

IP 183.91.70.244 Analysis

  • Country Code
    ID
  • Country Code3
    IDN
  • Country Name
    Indonesia
  • City
    AS
  • Continent Code
    5° South
  • Latitude
    120.
  • Longitude
  • % [whois.apnic.net node-6]
    % Whois data copyright terms http://www.apnic.net/db/dbcopyright.html

    inetnum: 183.91.70.240 - 183.91.70.255
    netname: LA-ALK
    descr: APLIKANUSA LINTASARTA-DEAL KEREN
    descr: Jakarta Raya
    country: ID
    admin-c: LA60-AP
    tech-c: LA60-AP
    mnt-by: MAINT-LINTASARTA
    mnt-irt: IRT-LINTASARTA-ID
    changed: hostmaster@lintasarta.net 20110419
    status: ASSIGNED NON-PORTABLE
    remarks: spam and abuse report : abuse@idola.net.id
    source: APNIC

    route: 183.91.64.0/19
    descr: Route Object of PT Aplikanusa Lintasarta
    descr: ISP
    descr: MH Thamrin Kav 3
    descr: Menara Thamrin Bulding 12th Floor
    descr: Jakarta 10250
    country: ID
    origin: AS4800
    remarks: Email address for spam or abuse complaints
    remarks: abuse@idola.net.id
    mnt-by: MAINT-LINTASARTA
    changed: hostmaster@idnic.net 20100421
    source: APNIC

    role: LINTASARTA ADMINISTRATOR
    address: PT Aplikanusa Lintasarta
    address: MH Thamrin Kav 3
    address: Menara Thamrin Bulding 12th Floor
    address: Jakarta 10250
    country: ID
    phone: +62-21-2302345
    fax-no: +62-21-2303883
    e-mail: hostmaster@lintasarta.net
    remarks: spam and abuse report : abuse@idola.net.id
    remarks: technical and routing : support@idola.net.id
    remarks: hostmasters : hostmaster@idola.net.id
    admin-c: DS717-AP
    tech-c: ND121-AP
    nic-hdl: LA60-AP
    remarks: LINTASARTA administrators role object
    notify: hostmaster@lintasarta.net
    mnt-by: MAINT-LINTASARTA
    changed: hostmaster@idola.net.id 20030307
    changed: hostmaster@idnic.net 20090501
    changed: hm-changed@apnic.net 20110325
    source: APNIC


In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 110 Errors
  • 67 Warnings
Ratio Text/Html
  • 0.4943005405405405
Message Error
  • Error Line 44, Column 8: required attribute "type" not specified
    <script>function utmx_section(){}function utmx(){}(function(){var

    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 48, Column 56: character "<" is the first character of a delimiter but occurred as data
    indexOf(';',i);return escape(c.substring(i+n.length+1,j<0?c.

    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 50, Column 5: an attribute specification must start with a name or name token
    '<sc'+'ript src="'+'http'+(l.protocol=='https:'?'s://ssl':

    An attribute name (and some attribute values) must start with one of a restricted set of characters. This error usually indicates that you have failed to add a closing quotation mark on a previous attribute value (so the attribute value looks like the start of a new attribute) or have used an attribute that is not defined (usually a typo in a common attribute name).

  • Error Line 50, Column 5: element "sc" undefined
    '<sc'+'ript src="'+'http'+(l.protocol=='https:'?'s://ssl':

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 52, Column 3: cannot generate system identifier for general entity "utmx"
    '&utmx='+(x?x:'')+'&utmxx='+(xx?xx:'')+'&utmxtime='+new Date().

    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 52, Column 3: general entity "utmx" not defined and no default entity
    '&utmx='+(x?x:'')+'&utmxx='+(xx?xx:'')+'&utmxtime='+new Date().

    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 52, Column 7: reference not terminated by REFC delimiter
    '&utmx='+(x?x:'')+'&utmxx='+(xx?xx:'')+'&utmxtime='+new Date().

    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 52, Column 7: reference to entity "utmx" for which no system identifier could be generated
    '&utmx='+(x?x:'')+'&utmxx='+(xx?xx:'')+'&utmxtime='+new Date().

    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 52, Column 2: entity was defined here
    '&utmx='+(x?x:'')+'&utmxx='+(xx?xx:'')+'&utmxtime='+new Date().
  • Warning Line 52, Column 21: cannot generate system identifier for general entity "utmxx"
    '&utmx='+(x?x:'')+'&utmxx='+(xx?xx:'')+'&utmxtime='+new Date().

    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 52, Column 21: general entity "utmxx" not defined and no default entity
    '&utmx='+(x?x:'')+'&utmxx='+(xx?xx:'')+'&utmxtime='+new Date().

    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 52, Column 26: reference not terminated by REFC delimiter
    '&utmx='+(x?x:'')+'&utmxx='+(xx?xx:'')+'&utmxtime='+new Date().

    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 52, Column 26: reference to entity "utmxx" for which no system identifier could be generated
    '&utmx='+(x?x:'')+'&utmxx='+(xx?xx:'')+'&utmxtime='+new Date().

    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 52, Column 20: entity was defined here
    '&utmx='+(x?x:'')+'&utmxx='+(xx?xx:'')+'&utmxtime='+new Date().
  • Warning Line 52, Column 42: cannot generate system identifier for general entity "utmxtime"
    '&utmx='+(x?x:'')+'&utmxx='+(xx?xx:'')+'&utmxtime='+new Date().

    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 52, Column 42: general entity "utmxtime" not defined and no default entity
    '&utmx='+(x?x:'')+'&utmxx='+(xx?xx:'')+'&utmxtime='+new Date().

    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 52, Column 50: reference not terminated by REFC delimiter
    '&utmx='+(x?x:'')+'&utmxx='+(xx?xx:'')+'&utmxtime='+new Date().

    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 52, Column 50: reference to entity "utmxtime" for which no system identifier could be generated
    '&utmx='+(x?x:'')+'&utmxx='+(xx?xx:'')+'&utmxtime='+new Date().

    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 52, Column 41: entity was defined here
    '&utmx='+(x?x:'')+'&utmxx='+(xx?xx:'')+'&utmxtime='+new Date().
  • Warning Line 53, Column 16: cannot generate system identifier for general entity "utmxhash"
    valueOf()+(h?'&utmxhash='+escape(h.substr(1)):'')+

    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 53, Column 16: general entity "utmxhash" not defined and no default entity
    valueOf()+(h?'&utmxhash='+escape(h.substr(1)):'')+

    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 53, Column 24: reference not terminated by REFC delimiter
    valueOf()+(h?'&utmxhash='+escape(h.substr(1)):'')+

    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 53, Column 24: reference to entity "utmxhash" for which no system identifier could be generated
    valueOf()+(h?'&utmxhash='+escape(h.substr(1)):'')+

    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 53, Column 15: entity was defined here
    valueOf()+(h?'&utmxhash='+escape(h.substr(1)):'')+
  • Warning Line 54, Column 43: character "<" is the first character of a delimiter but occurred as data
    '" type="text/javascript" charset="utf-8"><\/sc'+'ript>')})();

    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 55, Column 9: end tag for "sc" omitted, but OMITTAG NO was specified
    </script><script>utmx('url','A/B');</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 50, Column 2: start tag was here
    '<sc'+'ript src="'+'http'+(l.protocol=='https:'?'s://ssl':
  • Error Line 55, Column 17: required attribute "type" not specified
    </script><script>utmx('url','A/B');</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 92, Column 9: multiple comments in comment declaration
    <!---------------  UTM Tracking  ------------------->
  • Warning Line 92, Column 13: multiple comments in comment declaration
    <!---------------  UTM Tracking  ------------------->
  • Warning Line 92, Column 34: multiple comments in comment declaration
    <!---------------  UTM Tracking  ------------------->
  • Warning Line 92, Column 38: multiple comments in comment declaration
    <!---------------  UTM Tracking  ------------------->
  • Warning Line 92, Column 42: multiple comments in comment declaration
    <!---------------  UTM Tracking  ------------------->
  • Warning Line 92, Column 46: multiple comments in comment declaration
    <!---------------  UTM Tracking  ------------------->
  • Warning Line 92, Column 50: multiple comments in comment declaration
    <!---------------  UTM Tracking  ------------------->
  • Error Line 92, Column 52: invalid comment declaration: found name character outside comment but inside comment declaration
    <!---------------  UTM Tracking  ------------------->
  • Info Line 92, Column 1: comment declaration started here
    <!---------------  UTM Tracking  ------------------->
  • Warning Line 120, Column 28: character "&" is the first character of a delimiter but occurred as data
    	  var vars = query.split("&"); 

    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 121, Column 30: character ";" not allowed in attribute specification list
    	  for (var i=0;i<vars.length;i++) { 
  • Error Line 121, Column 30: element "vars.length" undefined
    	  for (var i=0;i<vars.length;i++) { 

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 147, Column 87: cannot generate system identifier for general entity "utm_source"
    …ck/estrack/beta/t3.php?action=session&utm_source='+encodeURIComponent(utm_sour…

    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 147, Column 87: general entity "utm_source" not defined and no default entity
    …ck/estrack/beta/t3.php?action=session&utm_source='+encodeURIComponent(utm_sour…

    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 147, Column 97: reference not terminated by REFC delimiter
    …/beta/t3.php?action=session&utm_source='+encodeURIComponent(utm_source)+'&utm_…

    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 147, Column 97: reference to entity "utm_source" for which no system identifier could be generated
    …/beta/t3.php?action=session&utm_source='+encodeURIComponent(utm_source)+'&utm_…

    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 147, Column 86: entity was defined here
    …ack/estrack/beta/t3.php?action=session&utm_source='+encodeURIComponent(utm_sou…
  • Warning Line 147, Column 133: cannot generate system identifier for general entity "utm_medium"
    …ce='+encodeURIComponent(utm_source)+'&utm_medium='+encodeURIComponent(utm_medi…

    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 147, Column 133: general entity "utm_medium" not defined and no default entity
    …ce='+encodeURIComponent(utm_source)+'&utm_medium='+encodeURIComponent(utm_medi…

    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 147, Column 143: reference not terminated by REFC delimiter
    …eURIComponent(utm_source)+'&utm_medium='+encodeURIComponent(utm_medium)+'&utm_…

    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 147, Column 143: reference to entity "utm_medium" for which no system identifier could be generated
    …eURIComponent(utm_source)+'&utm_medium='+encodeURIComponent(utm_medium)+'&utm_…

    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 147, Column 132: entity was defined here
    …rce='+encodeURIComponent(utm_source)+'&utm_medium='+encodeURIComponent(utm_med…
  • Warning Line 147, Column 179: cannot generate system identifier for general entity "utm_campaign"
    …um='+encodeURIComponent(utm_medium)+'&utm_campaign='+encodeURIComponent(utm_ca…

    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 147, Column 179: general entity "utm_campaign" not defined and no default entity
    …um='+encodeURIComponent(utm_medium)+'&utm_campaign='+encodeURIComponent(utm_ca…

    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 147, Column 191: reference not terminated by REFC delimiter
    …RIComponent(utm_medium)+'&utm_campaign='+encodeURIComponent(utm_campaign)+'&ut…

    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 147, Column 191: reference to entity "utm_campaign" for which no system identifier could be generated
    …RIComponent(utm_medium)+'&utm_campaign='+encodeURIComponent(utm_campaign)+'&ut…

    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 147, Column 178: entity was defined here
    …ium='+encodeURIComponent(utm_medium)+'&utm_campaign='+encodeURIComponent(utm_c…
  • Warning Line 147, Column 229: cannot generate system identifier for general entity "utm_content"
    …='+encodeURIComponent(utm_campaign)+'&utm_content='+encodeURIComponent(utm_con…

    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 147, Column 229: general entity "utm_content" not defined and no default entity
    …='+encodeURIComponent(utm_campaign)+'&utm_content='+encodeURIComponent(utm_con…

    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 147, Column 240: reference not terminated by REFC delimiter
    …IComponent(utm_campaign)+'&utm_content='+encodeURIComponent(utm_content)+'&utm…

    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 147, Column 240: reference to entity "utm_content" for which no system identifier could be generated
    …IComponent(utm_campaign)+'&utm_content='+encodeURIComponent(utm_content)+'&utm…

    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 147, Column 228: entity was defined here
    …n='+encodeURIComponent(utm_campaign)+'&utm_content='+encodeURIComponent(utm_co…
  • Warning Line 147, Column 277: cannot generate system identifier for general entity "utm_keyword"
    …t='+encodeURIComponent(utm_content)+'&utm_keyword='+encodeURIComponent(utm_key…

    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 147, Column 277: general entity "utm_keyword" not defined and no default entity
    …t='+encodeURIComponent(utm_content)+'&utm_keyword='+encodeURIComponent(utm_key…

    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 147, Column 288: reference not terminated by REFC delimiter
    …RIComponent(utm_content)+'&utm_keyword='+encodeURIComponent(utm_keyword)+'&bus…

    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 147, Column 288: reference to entity "utm_keyword" for which no system identifier could be generated
    …RIComponent(utm_content)+'&utm_keyword='+encodeURIComponent(utm_keyword)+'&bus…

    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 147, Column 276: entity was defined here
    …nt='+encodeURIComponent(utm_content)+'&utm_keyword='+encodeURIComponent(utm_ke…
  • Warning Line 147, Column 325: cannot generate system identifier for general entity "bust"
    …ent(utm_content)+'&utm_keyword='+encodeURIComponent(utm_keyword)+'&bust='+bust;

    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 147, Column 325: general entity "bust" not defined and no default entity
    …ent(utm_content)+'&utm_keyword='+encodeURIComponent(utm_keyword)+'&bust='+bust;

    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 147, Column 329: reference not terminated by REFC delimiter
    …ent(utm_content)+'&utm_keyword='+encodeURIComponent(utm_keyword)+'&bust='+bust;

    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 147, Column 329: reference to entity "bust" for which no system identifier could be generated
    …ent(utm_content)+'&utm_keyword='+encodeURIComponent(utm_keyword)+'&bust='+bust;

    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 147, Column 324: entity was defined here
    …ent(utm_content)+'&utm_keyword='+encodeURIComponent(utm_keyword)+'&bust='+bust;
  • Error Line 158, Column 72: there is no attribute "border"
    …mg src="'+scriptURL+'" width="1" height="1" border="0" style="display:none">');

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

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

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

  • Error Line 158, Column 96: required attribute "alt" not specified
    …mg src="'+scriptURL+'" width="1" height="1" border="0" style="display:none">');

    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 158, Column 97: end tag for "img" omitted, but OMITTAG NO was specified
    …mg src="'+scriptURL+'" width="1" height="1" border="0" style="display:none">');

    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 158, Column 19: start tag was here
    		document.write('<img src="'+scriptURL+'" width="1" height="1" border="0" styl…
  • Error Line 166, Column 9: end tag for "vars.length" 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 121, Column 18: start tag was here
    	  for (var i=0;i<vars.length;i++) { 
  • Warning Line 171, Column 9: multiple comments in comment declaration
    <!---------------  Light Box newsletter  ------------------->
  • Warning Line 171, Column 13: multiple comments in comment declaration
    <!---------------  Light Box newsletter  ------------------->
  • Warning Line 171, Column 42: multiple comments in comment declaration
    <!---------------  Light Box newsletter  ------------------->
  • Warning Line 171, Column 46: multiple comments in comment declaration
    <!---------------  Light Box newsletter  ------------------->
  • Warning Line 171, Column 50: multiple comments in comment declaration
    <!---------------  Light Box newsletter  ------------------->
  • Warning Line 171, Column 54: multiple comments in comment declaration
    <!---------------  Light Box newsletter  ------------------->
  • Warning Line 171, Column 58: multiple comments in comment declaration
    <!---------------  Light Box newsletter  ------------------->
  • Error Line 171, Column 60: invalid comment declaration: found name character outside comment but inside comment declaration
    <!---------------  Light Box newsletter  ------------------->
  • Info Line 171, Column 1: comment declaration started here
    <!---------------  Light Box newsletter  ------------------->
  • Error Line 188, Column 29: character ";" not allowed in attribute specification list
    for (i=0;i<ARRcookies.length;i++)
  • Error Line 188, Column 29: element "ARRcookies.length" undefined
    for (i=0;i<ARRcookies.length;i++)

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 213, Column 113: cannot generate system identifier for general entity "exprie"
    …tp://') + cookie_url + '?action=write&exprie='+exprie+'&value='+value+'&ckname…

    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 213, Column 113: general entity "exprie" not defined and no default entity
    …tp://') + cookie_url + '?action=write&exprie='+exprie+'&value='+value+'&ckname…

    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 213, Column 119: reference not terminated by REFC delimiter
    …) + cookie_url + '?action=write&exprie='+exprie+'&value='+value+'&ckname=popup…

    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 213, Column 119: reference to entity "exprie" for which no system identifier could be generated
    …) + cookie_url + '?action=write&exprie='+exprie+'&value='+value+'&ckname=popup…

    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 213, Column 112: entity was defined here
    …ttp://') + cookie_url + '?action=write&exprie='+exprie+'&value='+value+'&cknam…
  • Warning Line 213, Column 131: cannot generate system identifier for general entity "value"
    … + cookie_url + '?action=write&exprie='+exprie+'&value='+value+'&ckname=popup';

    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 213, Column 131: general entity "value" not defined and no default entity
    … + cookie_url + '?action=write&exprie='+exprie+'&value='+value+'&ckname=popup';

    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 213, Column 136: reference not terminated by REFC delimiter
    … + cookie_url + '?action=write&exprie='+exprie+'&value='+value+'&ckname=popup';

    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 213, Column 136: reference to entity "value" for which no system identifier could be generated
    … + cookie_url + '?action=write&exprie='+exprie+'&value='+value+'&ckname=popup';

    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 213, Column 130: entity was defined here
    … + cookie_url + '?action=write&exprie='+exprie+'&value='+value+'&ckname=popup';
  • Warning Line 213, Column 147: cannot generate system identifier for general entity "ckname"
    … + cookie_url + '?action=write&exprie='+exprie+'&value='+value+'&ckname=popup';

    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 213, Column 147: general entity "ckname" not defined and no default entity
    … + cookie_url + '?action=write&exprie='+exprie+'&value='+value+'&ckname=popup';

    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 213, Column 153: reference not terminated by REFC delimiter
    … + cookie_url + '?action=write&exprie='+exprie+'&value='+value+'&ckname=popup';

    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 213, Column 153: reference to entity "ckname" for which no system identifier could be generated
    … + cookie_url + '?action=write&exprie='+exprie+'&value='+value+'&ckname=popup';

    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 213, Column 146: entity was defined here
    … + cookie_url + '?action=write&exprie='+exprie+'&value='+value+'&ckname=popup';
  • Warning Line 219, Column 117: reference not terminated by REFC delimiter
    …://' : 'http://') + cookie_url+ '?action=read&exprie=0&value=yes&ckname=popup';

    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 219, Column 117: reference to entity "exprie" for which no system identifier could be generated
    …://' : 'http://') + cookie_url+ '?action=read&exprie=0&value=yes&ckname=popup';

    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 213, Column 112: entity was defined here
    …ttp://') + cookie_url + '?action=write&exprie='+exprie+'&value='+value+'&cknam…
  • Warning Line 219, Column 125: reference not terminated by REFC delimiter
    …://' : 'http://') + cookie_url+ '?action=read&exprie=0&value=yes&ckname=popup';

    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 219, Column 125: reference to entity "value" for which no system identifier could be generated
    …://' : 'http://') + cookie_url+ '?action=read&exprie=0&value=yes&ckname=popup';

    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 213, Column 130: entity was defined here
    … + cookie_url + '?action=write&exprie='+exprie+'&value='+value+'&ckname=popup';
  • Warning Line 219, Column 136: reference not terminated by REFC delimiter
    …://' : 'http://') + cookie_url+ '?action=read&exprie=0&value=yes&ckname=popup';

    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 219, Column 136: reference to entity "ckname" for which no system identifier could be generated
    …://' : 'http://') + cookie_url+ '?action=read&exprie=0&value=yes&ckname=popup';

    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 213, Column 146: entity was defined here
    … + cookie_url + '?action=write&exprie='+exprie+'&value='+value+'&ckname=popup';
  • Error Line 226, Column 9: end tag for "ARRcookies.length" 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 188, Column 11: start tag was here
    for (i=0;i<ARRcookies.length;i++)
  • Error Line 230, 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 231, Column 17: character "&" is the first character of a delimiter but occurred as data
    	!window.jQuery && document.write('<script src="https://apps.livingsocial.co.id…

    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 231, Column 18: character "&" is the first character of a delimiter but occurred as data
    	!window.jQuery && document.write('<script src="https://apps.livingsocial.co.id…

    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 231, Column 123: required attribute "type" not specified
    …pps.livingsocial.co.id/marketing/lp/fancybox/jquery-1.4.3.min.js"><\/script>');

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

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

  • Error Line 231, Column 123: document type does not allow element "script" here
    …pps.livingsocial.co.id/marketing/lp/fancybox/jquery-1.4.3.min.js"><\/script>');

    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 231, Column 124: character "<" is the first character of a delimiter but occurred as data
    …pps.livingsocial.co.id/marketing/lp/fancybox/jquery-1.4.3.min.js"><\/script>');

    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 233, Column 123: document type does not allow element "script" here
    …ngsocial.co.id/marketing/lp/fancybox/jquery.mousewheel-3.0.4.pack.js"></script>

    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 234, Column 121: document type does not allow element "script" here
    …vingsocial.co.id/marketing/lp/fancybox/jquery.fancybox-1.3.4.pack.js"></script>

    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 235, Column 143: document type does not allow element "link" here
    …social.co.id/marketing/lp/fancybox/jquery.fancybox-1.3.4.css" media="screen" />

    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 236, Column 96: document type does not allow element "link" here
    …heet" href="https://apps.livingsocial.co.id/marketing/lp/fancybox/style.css" />

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

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

  • Error Line 239, Column 31: document type does not allow element "script" here
    <script type="text/javascript">

    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 246, Column 19: there is no attribute "src"
    					'<iframe src="'+url+'" style="width:580px;height:380px;" frameborder="0" 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 246, Column 35: there is no attribute "style"
    					'<iframe src="'+url+'" style="width:580px;height:380px;" frameborder="0" 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 246, Column 75: there is no attribute "frameborder"
    …width:580px;height:380px;" frameborder="0" allowtransparency="true"></iframe>',

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

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

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

  • Error Line 246, Column 97: there is no attribute "allowtransparency"
    …width:580px;height:380px;" frameborder="0" allowtransparency="true"></iframe>',

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

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

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

  • Error Line 246, Column 103: element "iframe" undefined
    …width:580px;height:380px;" frameborder="0" allowtransparency="true"></iframe>',

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 262, Column 58: document type does not allow element "div" here
    … style="width:550px;text-align:right;"><a href="javascript:;" onclick="fancybo…

    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 290, Column 31: character "&" is the first character of a delimiter but occurred as data
    						if (popup_cookie!='yes' && chorme_ck!='yes') {

    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 290, Column 32: character "&" is the first character of a delimiter but occurred as data
    						if (popup_cookie!='yes' && chorme_ck!='yes') {

    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 317, Column 14: character "&" is the first character of a delimiter but occurred as data
    if ((!isiPad)&&(!mobile)) {

    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 317, Column 15: character "&" is the first character of a delimiter but occurred as data
    if ((!isiPad)&&(!mobile)) {

    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 333, Column 9: multiple comments in comment declaration
    <!---------------  Light Box newsletter  ------------------->
  • Warning Line 333, Column 13: multiple comments in comment declaration
    <!---------------  Light Box newsletter  ------------------->
  • Warning Line 333, Column 42: multiple comments in comment declaration
    <!---------------  Light Box newsletter  ------------------->
  • Warning Line 333, Column 46: multiple comments in comment declaration
    <!---------------  Light Box newsletter  ------------------->
  • Warning Line 333, Column 50: multiple comments in comment declaration
    <!---------------  Light Box newsletter  ------------------->
  • Warning Line 333, Column 54: multiple comments in comment declaration
    <!---------------  Light Box newsletter  ------------------->
  • Warning Line 333, Column 58: multiple comments in comment declaration
    <!---------------  Light Box newsletter  ------------------->
  • Error Line 333, Column 60: invalid comment declaration: found name character outside comment but inside comment declaration
    <!---------------  Light Box newsletter  ------------------->
  • Info Line 333, Column 1: comment declaration started here
    <!---------------  Light Box newsletter  ------------------->
  • Error Line 335, 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>.

  • Error Line 335, Column 8: document type does not allow element "script" here
    <script>

    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 351, Column 23: character "<" is the first character of a delimiter but occurred as data
        for (var i = 0; i < ca.length; i++) {

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 378, Column 104: element "iframe" undefined
    …idth:400px;height:250px;" frameborder="0" allowtransparency="false"></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 454, Column 31: document type does not allow element "script" here
    <script type="text/javascript">

    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 461, Column 10: document type does not allow element "noscript" here
    <noscript>

    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 463, Column 94: 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 466, Column 42: document type does not allow element "div" here
    <div id="header" class="header-container">

    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 468, Column 64: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    		<a href="http://www.livingsocial.co.id/"><div class="ls-logo"></div></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 481, Column 32: ID "currentCityLabel" already defined
    				<a href="javascript:;" id="currentCityLabel" onclick="toggleMenu(); return …

    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 479, Column 20: ID "currentCityLabel" first defined here
    				<a href="" id="currentCityLabel">
  • Error Line 485, Column 34: document type does not allow element "script" here; assuming missing "li" start-tag
    			<script type="text/javascript">
  • Error Line 488, Column 45: end tag for "li" omitted, but OMITTAG NO was specified
    																																							 </ul>

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

  • Info Line 485, Column 4: start tag was here
    			<script type="text/javascript">
  • Warning Line 518, Column 26: character "&" is the first character of a delimiter but occurred as data
            if((document.all)&&(navigator.appVersion.indexOf("MSIE 7.")!=-1)){

    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 518, Column 27: character "&" is the first character of a delimiter but occurred as data
            if((document.all)&&(navigator.appVersion.indexOf("MSIE 7.")!=-1)){

    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 584, Column 70: an attribute value must be a literal unless it contains only name characters
    …             document.write("<a class=\"fb_button fb_button_medium\"><span cla…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 584, Column 98: "fb_button_medium" is not a member of a group specified for any attribute
    …"<a class=\"fb_button fb_button_medium\"><span class=\"fb_button_text\">Connec…
  • Error Line 584, Column 100: document type does not allow element "a" here
    …a class=\"fb_button fb_button_medium\"><span class=\"fb_button_text\">Connect<…

    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 584, Column 113: an attribute value must be a literal unless it contains only name characters
    …_button fb_button_medium\"><span class=\"fb_button_text\">Connect</span></a>");

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 587, Column 84: there is no attribute "class"
    …ocument.write("<fb:login-button class=\"fb-login-button\" onlogin=\"login()\" …

    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 587, Column 84: an attribute value must be a literal unless it contains only name characters
    …ocument.write("<fb:login-button class=\"fb-login-button\" onlogin=\"login()\" …

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 587, Column 112: there is no attribute "onlogin"
    …ton class=\"fb-login-button\" onlogin=\"login()\"  scope=\"email,publish_strea…

    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 587, Column 112: an attribute value must be a literal unless it contains only name characters
    …ton class=\"fb-login-button\" onlogin=\"login()\"  scope=\"email,publish_strea…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 587, Column 131: there is no attribute "scope"
    …n-button\" onlogin=\"login()\"  scope=\"email,publish_stream\">Connect</fb:log…

    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 587, Column 131: an attribute value must be a literal unless it contains only name characters
    …n-button\" onlogin=\"login()\"  scope=\"email,publish_stream\">Connect</fb:log…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 587, Column 155: element "fb:login-button" undefined
    …nlogin=\"login()\"  scope=\"email,publish_stream\">Connect</fb:login-button>");

    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 610, Column 64: there is no attribute "align"
    <div class="warpbody" style="display:block; width:100%;" align="center">

    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 610, Column 72: document type does not allow element "div" here
    <div class="warpbody" style="display:block; width:100%;" align="center">

    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 655, Column 31: document type does not allow element "script" here
    <script type="text/javascript">

    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 677, Column 40: character "&" is the first character of a delimiter but occurred as data
            } else if(link.href != baseUrl && link.href != baseUrl + '/') {

    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 677, Column 41: character "&" is the first character of a delimiter but occurred as data
            } else if(link.href != baseUrl && link.href != baseUrl + '/') {

    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 684, Column 81: document type does not allow element "div" here
    …script><div class="warpbody" style="display:block; width:100%;" align="center">

    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 695, Column 31: document type does not allow element "script" here
    <script type="text/javascript">

    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 731, Column 57: document type does not allow element "div" here
    </script>        <div class="main-container col1-layout">

    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 751, Column 86: there is no attribute "width"
    …d/marketing/diapo/example.html" width="625" height="424" scrolling="no" frameb…

    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 751, Column 99: there is no attribute "height"
    …iapo/example.html" width="625" height="424" scrolling="no" frameborder="0" all…

    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 751, Column 115: there is no attribute "scrolling"
    …l" width="625" height="424" scrolling="no" frameborder="0" allowTransparency="…

    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 751, Column 154: there is no attribute "allowTransparency"
    …t="424" scrolling="no" frameborder="0" allowTransparency="true"></iframe></div>

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

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

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

  • Error Line 751, Column 160: element "iframe" undefined
    …t="424" scrolling="no" frameborder="0" allowTransparency="true"></iframe></div>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 789, Column 265: there is no attribute "align"
    …Modern Hypnosis" width="360" height="245" align="left" hspace="0" vspace="0" />

    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 789, Column 279: there is no attribute "hspace"
    …Modern Hypnosis" width="360" height="245" align="left" hspace="0" vspace="0" />

    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 789, Column 290: there is no attribute "vspace"
    …Modern Hypnosis" width="360" height="245" align="left" hspace="0" vspace="0" />

    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 816, Column 71: there is no attribute "language"
    …                         <script type="text/javascript"  language="javascript">

    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 842, Column 54: there is no attribute "align"
    …          <button type="button" align="center" onclick = "window.location.href…

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

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

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

  • Error Line 989, Column 10: ID "deals_container" already defined
    <div id="deals_container">

    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 782, Column 10: ID "deals_container" first defined here
    <div id="deals_container">
  • Error Line 1129, Column 10: ID "deals_container" already defined
    <div id="deals_container">

    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 782, Column 10: ID "deals_container" first defined here
    <div id="deals_container">
  • Error Line 1204, Column 10: ID "deals_container" already defined
    <div id="deals_container">

    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 782, Column 10: ID "deals_container" first defined here
    <div id="deals_container">
  • Error Line 3199, Column 64: there is no attribute "target"
    …ivingsocial.co.id/how-to-buy2" target="_parent"><img src="http://www.livingsoc…

    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 3200, Column 73: there is no attribute "bgcolor"
    …ble border="0" cellspacing="0" cellpadding="0" width="980px" bgcolor="#FFFFFF">

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

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

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

  • Error Line 3231, Column 11: there is no attribute "width"
    <td width="225">

    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 3289, Column 35: 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 3289, Column 35: 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 3325, Column 76: 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" value="" id="language-input" name="___store" />

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

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

  • Warning Line 3354, Column 7: S separator in comment declaration
    <!----  CHARTBEAT  ------------>

    This may happen if you have consecutive comments but did not close one of them properly. The proper syntax for comments is <!-- my comment -->.

  • Warning Line 3354, Column 8: S separator in comment declaration
    <!----  CHARTBEAT  ------------>

    This may happen if you have consecutive comments but did not close one of them properly. The proper syntax for comments is <!-- my comment -->.

  • Error Line 3354, Column 9: invalid comment declaration: found name start character outside comment but inside comment declaration
    <!----  CHARTBEAT  ------------>
  • Info Line 3354, Column 1: comment declaration started here
    <!----  CHARTBEAT  ------------>
  • Error Line 3376, Column 47: document type does not allow element "script" here
                    <script type="text/javascript">

    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 3380, Column 19: end tag for "script" omitted, but OMITTAG NO was specified
    </script>    </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 230, Column 1: start tag was here
    <script>

Visitor Analysis

Daily Visitor
  • 8.050 visits
Daily Visitor