bagas31.com

Free Download Software Full Crack Keygen Patch Serial, Download Antivirus, Download Free Game, Tutorial Tips Blogger Komputer, Free Audio Video Converter Tool, Aplikasi Internet Gratis ...

Display Widget for this domain on your website. Click Here
Processing update domain...

Overview Info

  • Domain Name
    bagas31.com
  • Favicon
  • Alexa Rank
    #24529
  • Google Page Rank
    PR 2
  • Ip Address
    216.239.38.21
  • Page Size
    143.4 KB
  • Images
    4 GIF, 16 JPG, 13 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    4 3 0 0 0 0

Website Meta Analysis



  • Title
    BAGAS31 | Download Software Gratis
  • Meta Keyword
    free download software, download, antivirus, gratis, tutorial, free games, free, full, crack, patch, serial, keygen, key, tips, video converter, tool, aplikasi, pro, activator, idm, office, windows, nero, utility, winrar
  • Meta Description
    Free Download Software Full Crack Keygen Patch Serial, Download Antivirus, Download Free Game, Tutorial Tips Blogger Komputer, Free Audio Video Converter Tool, Aplikasi Internet Gratis

Technical Analysis



  • Webserver
    GSE
  • Ip Address
    216.239.38.21
  • Domain Age
    2 Years, 5 Months, 20 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • content-type: text/html; charset=UTF-8
  • expires: Thu, 01 Aug 2013 03:15:42 GMT
  • date: Thu, 01 Aug 2013 03:15:42 GMT
  • cache-control: private, max-age=0
  • last-modified: Thu, 01 Aug 2013 02:53:30 GMT
  • etag: "2a1699cc-cf90-40e9-bc71-acf3b52db9fb"
  • content-encoding: gzip
  • x-content-type-options: nosniff
  • x-xss-protection: 1; mode=block
  • content-length: 32577
  • server: GSE
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
IDwebhost.com
Best Service at Affordable Cost

Domain Name: BAGAS31.COM

Registrant:
PrivacyProtect.org
Domain Admin ( email )
ID#10760, PO Box 16
Note - All Postal Mails Rejected, visit Privacyprotect.org
Nobby Beach
null,QLD 4218
AU
Tel. +45.36946676

Creation Date: 22-Feb-2011
Expiration Date: 22-Feb-2013

Domain servers in listed order:
earth.idwebhost.com
mars.idwebhost.com
mercury.idwebhost.com
venus.idwebhost.com


Administrative Contact:
PrivacyProtect.org
Domain Admin ( email )
ID#10760, PO Box 16
Note - All Postal Mails Rejected, visit Privacyprotect.org
Nobby Beach
null,QLD 4218
AU
Tel. +45.36946676

Technical Contact:
PrivacyProtect.org
Domain Admin ( email )
ID#10760, PO Box 16
Note - All Postal Mails Rejected, visit Privacyprotect.org
Nobby Beach
null,QLD 4218
AU
Tel. +45.36946676

Billing Contact:
PrivacyProtect.org
Domain Admin ( email )
ID#10760, PO Box 16
Note - All Postal Mails Rejected, visit Privacyprotect.org
Nobby Beach
null,QLD 4218
AU
Tel. +45.36946676

Status:LOCKED
Note: This Domain Name is currently Locked. In this status the domain
name cannot be transferred, hijacked, or modified. The Owner of this
domain name can easily change this status from their control panel.
This feature is provided as a security measure against fraudulent domain name hijacking.

PRIVACYPROTECT.ORG is providing privacy protection services to this domain name to
protect the owner from spam and phishing attacks. PrivacyProtect.org is not
responsible for any of the activities associated with this domain name. If you wish
to report any abuse concerning the usage of this domain name, you may do so at
http://privacyprotect.org/contact. We have a stringent abuse policy and any
complaint will be actioned within a short period of time.

The data in this whois database is provided to you for information purposes only,
that is, to assist you in obtaining information about or related
to a domain name registration record. We make this information available "as is",
and do not guarantee its accuracy. By submitting a whois query, you agree that you will
use this data only for lawful purposes and that, under no circumstances will you use this data to:
(1) enable high volume, automated, electronic processes that stress
or load this whois database system providing you this information; or
(2) allow, enable, or otherwise support the transmission of mass unsolicited,
commercial advertising or solicitations via direct mail, electronic mail, or by telephone.
The compilation, repackaging, dissemination or other use of this data is expressly prohibited without
prior written consent from us. The Registrar of record is CV. Jogjacamp.
We reserve the right to modify these terms at any time.
By submitting this query, you agree to abide by these terms.






DNS Analysis


DNS servers
mercury.idwebhost.com [50.23.136.173]
venus.idwebhost.com [50.23.75.44]
earth.idwebhost.com [67.15.253.219]
mars.idwebhost.com [184.173.149.221]


DNS Records

Answer records
bagas31.com NS  venus.idwebhost.com 38400s
bagas31.com MX
preference: 30
exchange: aspmx2.googlemail.com
28800s
bagas31.com MX
preference: 20
exchange: alt2.aspmx.l.google.com
28800s
bagas31.com MX
preference: 30
exchange: aspmx4.googlemail.com
28800s
bagas31.com A 216.239.36.21 28800s
bagas31.com NS  mercury.idwebhost.com 38400s
bagas31.com MX
preference: 10
exchange: aspmx.l.google.com
28800s
bagas31.com A 216.239.34.21 28800s
bagas31.com MX
preference: 30
exchange: aspmx5.googlemail.com
28800s
bagas31.com MX
preference: 20
exchange: alt1.aspmx.l.google.com
28800s
bagas31.com NS  earth.idwebhost.com 38400s
bagas31.com NS  mars.idwebhost.com 38400s
bagas31.com A 216.239.32.21 28800s
bagas31.com MX
preference: 30
exchange: aspmx3.googlemail.com
28800s
bagas31.com SOA
server: mercury.idwebhost.com
email: bagaspramudita@gmail.com
serial: 2012031201
refresh: 7200
retry: 7200
expire: 172800
minimum ttl: 7200
38400s
bagas31.com A 216.239.38.21 28800s

Authority records

Additional records

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 140 Errors
  • 159 Warnings
Ratio Text/Html
  • 0.5402200255970373
Message Error
  • Error Line 15, Column 41: there is no attribute "property"
    <meta content='bagaspramudita' property='fb:admins'/>

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

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

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

  • Warning Line 29, Column 264: character "&" is the first character of a delimiter but occurred as data
    …ming={Timer:e,load:f};if(a.performance&&a.performance.timing){var g=a.performa…

    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 29, Column 266: cannot generate system identifier for general entity "a.performance.timing"
    …ng={Timer:e,load:f};if(a.performance&&a.performance.timing){var g=a.performanc…

    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 29, Column 266: general entity "a.performance.timing" not defined and no default entity
    …ng={Timer:e,load:f};if(a.performance&&a.performance.timing){var g=a.performanc…

    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 29, Column 286: reference not terminated by REFC delimiter
    …if(a.performance&&a.performance.timing){var g=a.performance.timing,j=a[b].load…

    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 29, Column 286: reference to entity "a.performance.timing" for which no system identifier could be generated
    …if(a.performance&&a.performance.timing){var g=a.performance.timing,j=a[b].load…

    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 29, Column 265: entity was defined here
    …ing={Timer:e,load:f};if(a.performance&&a.performance.timing){var g=a.performan…
  • Error Line 29, Column 368: character "&" not allowed in attribute specification list
    ….navigationStart,l=g.responseStart;0<k&&l>=k&&(j[d]("_wtsrt",void 0,k),j[d]("w…
  • Error Line 29, Column 368: element "k" undefined
    ….navigationStart,l=g.responseStart;0<k&&l>=k&&(j[d]("_wtsrt",void 0,k),j[d]("w…

    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 29, Column 370: cannot generate system identifier for general entity "l"
    …avigationStart,l=g.responseStart;0<k&&l>=k&&(j[d]("_wtsrt",void 0,k),j[d]("wts…

    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 29, Column 370: general entity "l" not defined and no default entity
    …avigationStart,l=g.responseStart;0<k&&l>=k&&(j[d]("_wtsrt",void 0,k),j[d]("wts…

    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 29, Column 371: reference not terminated by REFC delimiter
    …vigationStart,l=g.responseStart;0<k&&l>=k&&(j[d]("_wtsrt",void 0,k),j[d]("wtsr…

    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 29, Column 371: reference to entity "l" for which no system identifier could be generated
    …vigationStart,l=g.responseStart;0<k&&l>=k&&(j[d]("_wtsrt",void 0,k),j[d]("wtsr…

    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 29, Column 369: entity was defined here
    …navigationStart,l=g.responseStart;0<k&&l>=k&&(j[d]("_wtsrt",void 0,k),j[d]("wt…
  • Warning Line 29, Column 374: character "&" is the first character of a delimiter but occurred as data
    …ationStart,l=g.responseStart;0<k&&l>=k&&(j[d]("_wtsrt",void 0,k),j[d]("wtsrt_"…

    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 29, Column 375: character "&" is the first character of a delimiter but occurred as data
    …tionStart,l=g.responseStart;0<k&&l>=k&&(j[d]("_wtsrt",void 0,k),j[d]("wtsrt_",…

    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 30, Column 24: character "&" is the first character of a delimiter but occurred as data
    try{var m=null;a.chrome&&a.chrome.csi&&(m=Math.floor(a.chrome.csi().pageT),j&&0…

    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 30, Column 26: cannot generate system identifier for general entity "a.chrome.csi"
    try{var m=null;a.chrome&&a.chrome.csi&&(m=Math.floor(a.chrome.csi().pageT),j&&0…

    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 30, Column 26: general entity "a.chrome.csi" not defined and no default entity
    try{var m=null;a.chrome&&a.chrome.csi&&(m=Math.floor(a.chrome.csi().pageT),j&&0…

    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 30, Column 38: reference not terminated by REFC delimiter
    try{var m=null;a.chrome&&a.chrome.csi&&(m=Math.floor(a.chrome.csi().pageT),j&&0…

    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 30, Column 38: reference to entity "a.chrome.csi" for which no system identifier could be generated
    try{var m=null;a.chrome&&a.chrome.csi&&(m=Math.floor(a.chrome.csi().pageT),j&&0…

    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 30, Column 25: entity was defined here
    try{var m=null;a.chrome&&a.chrome.csi&&(m=Math.floor(a.chrome.csi().pageT),j&&0…
  • Warning Line 30, Column 38: character "&" is the first character of a delimiter but occurred as data
    try{var m=null;a.chrome&&a.chrome.csi&&(m=Math.floor(a.chrome.csi().pageT),j&&0…

    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 30, Column 39: character "&" is the first character of a delimiter but occurred as data
    try{var m=null;a.chrome&&a.chrome.csi&&(m=Math.floor(a.chrome.csi().pageT),j&&0…

    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 30, Column 77: character "&" is the first character of a delimiter but occurred as data
    …&(m=Math.floor(a.chrome.csi().pageT),j&&0<k&&(j[d]("_tbnd",void 0,a.chrome.csi…

    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 30, Column 78: character "&" is the first character of a delimiter but occurred as data
    …(m=Math.floor(a.chrome.csi().pageT),j&&0<k&&(j[d]("_tbnd",void 0,a.chrome.csi(…

    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 30, Column 82: character "&" not allowed in attribute specification list
    …ath.floor(a.chrome.csi().pageT),j&&0<k&&(j[d]("_tbnd",void 0,a.chrome.csi().st…
  • Error Line 30, Column 82: element "k" undefined
    …ath.floor(a.chrome.csi().pageT),j&&0<k&&(j[d]("_tbnd",void 0,a.chrome.csi().st…

    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 30, Column 83: character "&" is the first character of a delimiter but occurred as data
    …th.floor(a.chrome.csi().pageT),j&&0<k&&(j[d]("_tbnd",void 0,a.chrome.csi().sta…

    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 30, Column 161: character "&" is the first character of a delimiter but occurred as data
    …rtE),j[d]("tbnd_","_tbnd",k)));null==m&&a.gtbExternal&&(m=a.gtbExternal.pageT(…

    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 30, Column 163: cannot generate system identifier for general entity "a.gtbExternal"
    …E),j[d]("tbnd_","_tbnd",k)));null==m&&a.gtbExternal&&(m=a.gtbExternal.pageT())…

    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 30, Column 163: general entity "a.gtbExternal" not defined and no default entity
    …E),j[d]("tbnd_","_tbnd",k)));null==m&&a.gtbExternal&&(m=a.gtbExternal.pageT())…

    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 30, Column 176: reference not terminated by REFC delimiter
    …_","_tbnd",k)));null==m&&a.gtbExternal&&(m=a.gtbExternal.pageT());null==m&&a.e…

    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 30, Column 176: reference to entity "a.gtbExternal" for which no system identifier could be generated
    …_","_tbnd",k)));null==m&&a.gtbExternal&&(m=a.gtbExternal.pageT());null==m&&a.e…

    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 30, Column 162: entity was defined here
    …tE),j[d]("tbnd_","_tbnd",k)));null==m&&a.gtbExternal&&(m=a.gtbExternal.pageT()…
  • Warning Line 30, Column 176: character "&" is the first character of a delimiter but occurred as data
    …_","_tbnd",k)));null==m&&a.gtbExternal&&(m=a.gtbExternal.pageT());null==m&&a.e…

    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 30, Column 177: character "&" is the first character of a delimiter but occurred as data
    …","_tbnd",k)));null==m&&a.gtbExternal&&(m=a.gtbExternal.pageT());null==m&&a.ex…

    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 30, Column 211: character "&" is the first character of a delimiter but occurred as data
    …nal&&(m=a.gtbExternal.pageT());null==m&&a.external&&(m=a.external.pageT,j&&0<k…

    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 30, Column 213: cannot generate system identifier for general entity "a.external"
    …l&&(m=a.gtbExternal.pageT());null==m&&a.external&&(m=a.external.pageT,j&&0<k&&…

    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 30, Column 213: general entity "a.external" not defined and no default entity
    …l&&(m=a.gtbExternal.pageT());null==m&&a.external&&(m=a.external.pageT,j&&0<k&&…

    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 30, Column 223: reference not terminated by REFC delimiter
    …bExternal.pageT());null==m&&a.external&&(m=a.external.pageT,j&&0<k&&(j[d]("_tb…

    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 30, Column 223: reference to entity "a.external" for which no system identifier could be generated
    …bExternal.pageT());null==m&&a.external&&(m=a.external.pageT,j&&0<k&&(j[d]("_tb…

    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 30, Column 212: entity was defined here
    …al&&(m=a.gtbExternal.pageT());null==m&&a.external&&(m=a.external.pageT,j&&0<k&…
  • Warning Line 30, Column 223: character "&" is the first character of a delimiter but occurred as data
    …bExternal.pageT());null==m&&a.external&&(m=a.external.pageT,j&&0<k&&(j[d]("_tb…

    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 30, Column 224: character "&" is the first character of a delimiter but occurred as data
    …External.pageT());null==m&&a.external&&(m=a.external.pageT,j&&0<k&&(j[d]("_tbn…

    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 30, Column 246: character "&" is the first character of a delimiter but occurred as data
    …==m&&a.external&&(m=a.external.pageT,j&&0<k&&(j[d]("_tbnd",void 0,a.external.s…

    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 30, Column 247: character "&" is the first character of a delimiter but occurred as data
    …=m&&a.external&&(m=a.external.pageT,j&&0<k&&(j[d]("_tbnd",void 0,a.external.st…

    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 30, Column 251: character "&" not allowed in attribute specification list
    …a.external&&(m=a.external.pageT,j&&0<k&&(j[d]("_tbnd",void 0,a.external.startE…
  • Error Line 30, Column 251: element "k" undefined
    …a.external&&(m=a.external.pageT,j&&0<k&&(j[d]("_tbnd",void 0,a.external.startE…

    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 30, Column 252: character "&" is the first character of a delimiter but occurred as data
    ….external&&(m=a.external.pageT,j&&0<k&&(j[d]("_tbnd",void 0,a.external.startE)…

    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 30, Column 320: character "&" is the first character of a delimiter but occurred as data
    …al.startE),j[d]("tbnd_","_tbnd",k)));m&&(a[b].pt=m)}catch(n){};a.tickAboveFold…

    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 30, Column 321: character "&" is the first character of a delimiter but occurred as data
    …l.startE),j[d]("tbnd_","_tbnd",k)));m&&(a[b].pt=m)}catch(n){};a.tickAboveFold=…

    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 30, Column 452: character "&" is the first character of a delimiter but occurred as data
    …Top;while(c=c.offsetParent)}c=i;750>=c&&a[b].load[d]("aft")};var q=!1;function…

    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 30, Column 454: cannot generate system identifier for general entity "a"
    …p;while(c=c.offsetParent)}c=i;750>=c&&a[b].load[d]("aft")};var q=!1;function r…

    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 30, Column 454: general entity "a" not defined and no default entity
    …p;while(c=c.offsetParent)}c=i;750>=c&&a[b].load[d]("aft")};var q=!1;function r…

    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 30, Column 455: reference not terminated by REFC delimiter
    …;while(c=c.offsetParent)}c=i;750>=c&&a[b].load[d]("aft")};var q=!1;function r(…

    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 30, Column 455: reference to entity "a" for which no system identifier could be generated
    …;while(c=c.offsetParent)}c=i;750>=c&&a[b].load[d]("aft")};var q=!1;function r(…

    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 30, Column 453: entity was defined here
    …op;while(c=c.offsetParent)}c=i;750>=c&&a[b].load[d]("aft")};var q=!1;function …
  • Error Line 31, Column 15: end tag for "k" 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 30, Column 249: start tag was here
    …&&a.external&&(m=a.external.pageT,j&&0<k&&(j[d]("_tbnd",void 0,a.external.star…
  • Error Line 31, Column 15: end tag for "k" 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 30, Column 80: start tag was here
    …=Math.floor(a.chrome.csi().pageT),j&&0<k&&(j[d]("_tbnd",void 0,a.chrome.csi().…
  • Error Line 31, Column 15: end tag for "k" 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 29, Column 366: start tag was here
    …=g.navigationStart,l=g.responseStart;0<k&&l>=k&&(j[d]("_wtsrt",void 0,k),j[d](…
  • Warning Line 50, Column 123: cannot generate system identifier for general entity "zx"
    ….css?targetBlogID=5324470203034857638&zx=186c7998-33ed-4a82-a80d-615e2fc47310"…

    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 50, Column 123: general entity "zx" not defined and no default entity
    ….css?targetBlogID=5324470203034857638&zx=186c7998-33ed-4a82-a80d-615e2fc47310"…

    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 50, Column 125: reference not terminated by REFC delimiter
    …css?targetBlogID=5324470203034857638&zx=186c7998-33ed-4a82-a80d-615e2fc47310"/>

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

  • Warning Line 50, Column 125: reference to external entity in attribute value
    …css?targetBlogID=5324470203034857638&zx=186c7998-33ed-4a82-a80d-615e2fc47310"/>

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

  • Error Line 50, Column 125: reference to entity "zx" for which no system identifier could be generated
    …css?targetBlogID=5324470203034857638&zx=186c7998-33ed-4a82-a80d-615e2fc47310"/>

    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 50, Column 122: entity was defined here
    …n.css?targetBlogID=5324470203034857638&zx=186c7998-33ed-4a82-a80d-615e2fc47310…
  • Warning Line 121, Column 5: multiple comments in comment declaration
    ----------------------------------------------- */
  • Warning Line 121, Column 9: multiple comments in comment declaration
    ----------------------------------------------- */
  • Warning Line 121, Column 13: multiple comments in comment declaration
    ----------------------------------------------- */
  • Warning Line 121, Column 17: multiple comments in comment declaration
    ----------------------------------------------- */
  • Warning Line 121, Column 21: multiple comments in comment declaration
    ----------------------------------------------- */
  • Warning Line 121, Column 25: multiple comments in comment declaration
    ----------------------------------------------- */
  • Warning Line 121, Column 29: multiple comments in comment declaration
    ----------------------------------------------- */
  • Warning Line 121, Column 33: multiple comments in comment declaration
    ----------------------------------------------- */
  • Warning Line 121, Column 37: multiple comments in comment declaration
    ----------------------------------------------- */
  • Warning Line 121, Column 41: multiple comments in comment declaration
    ----------------------------------------------- */
  • Warning Line 121, Column 45: multiple comments in comment declaration
    ----------------------------------------------- */
  • Error Line 121, Column 47: invalid comment declaration: found name character outside comment but inside comment declaration
    ----------------------------------------------- */
  • Info Line 51, Column 41: comment declaration started here
    <style id='page-skin-1' type='text/css'><!--
  • Warning Line 442, Column 87: cannot generate system identifier for general entity "m"
    …vigator,b="userAgent",c="indexOf",f="&m=1",g="(^|&)m=",h="?",i="?m=1";function…

    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 442, Column 87: general entity "m" not defined and no default entity
    …vigator,b="userAgent",c="indexOf",f="&m=1",g="(^|&)m=",h="?",i="?m=1";function…

    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 442, Column 88: reference not terminated by REFC delimiter
    …igator,b="userAgent",c="indexOf",f="&m=1",g="(^|&)m=",h="?",i="?m=1";function …

    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 442, Column 88: reference to entity "m" for which no system identifier could be generated
    …igator,b="userAgent",c="indexOf",f="&m=1",g="(^|&)m=",h="?",i="?m=1";function …

    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 442, Column 86: entity was defined here
    …avigator,b="userAgent",c="indexOf",f="&m=1",g="(^|&)m=",h="?",i="?m=1";functio…
  • Warning Line 442, Column 98: character "&" is the first character of a delimiter but occurred as data
    …userAgent",c="indexOf",f="&m=1",g="(^|&)m=",h="?",i="?m=1";function j(){var d=…

    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 442, Column 222: character "<" is the first character of a delimiter but occurred as data
    …gth){case 1:return d+i;case 2:return 0<=e[1].search(g)?null:d+f;default:return…

    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 442, Column 293: character "&" is the first character of a delimiter but occurred as data
    …:return null}}if(-1!=a[b][c]("Mobile")&&-1!=a[b][c]("WebKit")&&-1==a[b][c]("iP…

    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 442, Column 294: character "&" is the first character of a delimiter but occurred as data
    …return null}}if(-1!=a[b][c]("Mobile")&&-1!=a[b][c]("WebKit")&&-1==a[b][c]("iPa…

    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 442, Column 316: character "&" is the first character of a delimiter but occurred as data
    …b][c]("Mobile")&&-1!=a[b][c]("WebKit")&&-1==a[b][c]("iPad")||-1!=a[b][c]("Oper…

    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 442, Column 317: character "&" is the first character of a delimiter but occurred as data
    …][c]("Mobile")&&-1!=a[b][c]("WebKit")&&-1==a[b][c]("iPad")||-1!=a[b][c]("Opera…

    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 442, Column 402: character "&" is the first character of a delimiter but occurred as data
    …pera Mini")||-1!=a[b][c]("IEMobile")){var k=j();k&&window.location.replace(k)};

    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 442, Column 404: cannot generate system identifier for general entity "window.location.replace"
    …pera Mini")||-1!=a[b][c]("IEMobile")){var k=j();k&&window.location.replace(k)};

    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 442, Column 404: general entity "window.location.replace" not defined and no default entity
    …pera Mini")||-1!=a[b][c]("IEMobile")){var k=j();k&&window.location.replace(k)};

    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 442, Column 427: reference not terminated by REFC delimiter
    …pera Mini")||-1!=a[b][c]("IEMobile")){var k=j();k&&window.location.replace(k)};

    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 442, Column 427: reference to entity "window.location.replace" for which no system identifier could be generated
    …pera Mini")||-1!=a[b][c]("IEMobile")){var k=j();k&&window.location.replace(k)};

    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 442, Column 403: entity was defined here
    …pera Mini")||-1!=a[b][c]("IEMobile")){var k=j();k&&window.location.replace(k)};
  • Error Line 447, Column 50: required attribute "type" not specified
    <script src='//connect.facebook.net/en_US/all.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>.

  • Warning Line 462, Column 30: character "&" is the first character of a delimiter but occurred as data
              if (window.iframes && iframes.open) {

    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 462, Column 31: character "&" is the first character of a delimiter but occurred as data
              if (window.iframes && iframes.open) {

    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 488, Column 449: there is no attribute "border"
    …le='Jadikan Halaman Awal'><img border='0' src='http://4.bp.blogspot.com/-t4LXs…

    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 488, Column 548: required attribute "alt" not specified
    …com/-t4LXslJIfoo/T79OAI8jYeI/AAAAAAAADB8/xjy1VVJvzow/s1600/home.png'/></a></li>

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

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

  • Error Line 490, Column 71: there is no attribute "target"
    …ww.bagas31.com/2011/05/pasang-iklan.html' target='_blank'>Pasang Iklan</a></li>

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

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

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

  • Warning Line 495, Column 140: reference not terminated by REFC delimiter
    …' border='0' src='http://opi.yahoo.com/online?u=bagas31chat&m=g&t=1'/></a></li>

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

  • Warning Line 495, Column 140: reference to external entity in attribute value
    …' border='0' src='http://opi.yahoo.com/online?u=bagas31chat&m=g&t=1'/></a></li>

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

  • Error Line 495, Column 140: reference to entity "m" for which no system identifier could be generated
    …' border='0' src='http://opi.yahoo.com/online?u=bagas31chat&m=g&t=1'/></a></li>

    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 442, Column 86: entity was defined here
    …avigator,b="userAgent",c="indexOf",f="&m=1",g="(^|&)m=",h="?",i="?m=1";functio…
  • Warning Line 495, Column 143: cannot generate system identifier for general entity "t"
    …' border='0' src='http://opi.yahoo.com/online?u=bagas31chat&m=g&t=1'/></a></li>

    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 495, Column 143: general entity "t" not defined and no default entity
    …' border='0' src='http://opi.yahoo.com/online?u=bagas31chat&m=g&t=1'/></a></li>

    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 495, Column 144: reference not terminated by REFC delimiter
    …' border='0' src='http://opi.yahoo.com/online?u=bagas31chat&m=g&t=1'/></a></li>

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

  • Warning Line 495, Column 144: reference to external entity in attribute value
    …' border='0' src='http://opi.yahoo.com/online?u=bagas31chat&m=g&t=1'/></a></li>

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

  • Error Line 495, Column 144: reference to entity "t" for which no system identifier could be generated
    …' border='0' src='http://opi.yahoo.com/online?u=bagas31chat&m=g&t=1'/></a></li>

    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 495, Column 142: entity was defined here
    …' border='0' src='http://opi.yahoo.com/online?u=bagas31chat&m=g&t=1'/></a></li>
  • Error Line 506, Column 233: required attribute "alt" not specified
    …AAAAAAAEJo/HRObR32uOPk/s1600/ads.jpg"/></a><div id='float-left'><center><a hre…

    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 506, Column 266: element "center" undefined
    …jpg"/></a><div id='float-left'><center><a href='https://safelinking.net/d/6cdd…

    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 507, Column 112: required attribute "alt" not specified
    …AAAAAADvg/bo76j1iuf10/s1600/ads1.jpg'/></a></center></div><div id='float-right…

    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 507, Column 161: element "center" undefined
    …er></div><div id='float-right'><center><a href='https://safelinking.net/d/6cdd…

    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 507, Column 359: required attribute "alt" not specified
    …CGuagU/UBS2iV2qFAI/AAAAAAAADvQ/cko2uRrzMtc/s1600/ads2.jpg'/></a></center></div>

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

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

  • Warning Line 512, Column 83: cannot generate system identifier for general entity "widgetType"
    …/rearrange?blogID=5324470203034857638&widgetType=HTML&widgetId=HTML12&action=e…

    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 512, Column 83: general entity "widgetType" not defined and no default entity
    …/rearrange?blogID=5324470203034857638&widgetType=HTML&widgetId=HTML12&action=e…

    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 512, Column 93: reference not terminated by REFC delimiter
    …?blogID=5324470203034857638&widgetType=HTML&widgetId=HTML12&action=editWidget&…

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

  • Warning Line 512, Column 93: reference to external entity in attribute value
    …?blogID=5324470203034857638&widgetType=HTML&widgetId=HTML12&action=editWidget&…

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

  • Error Line 512, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=5324470203034857638&widgetType=HTML&widgetId=HTML12&action=editWidget&…

    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 512, Column 82: entity was defined here
    …m/rearrange?blogID=5324470203034857638&widgetType=HTML&widgetId=HTML12&action=…
  • Warning Line 512, Column 99: cannot generate system identifier for general entity "widgetId"
    …D=5324470203034857638&widgetType=HTML&widgetId=HTML12&action=editWidget&sectio…

    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 512, Column 99: general entity "widgetId" not defined and no default entity
    …D=5324470203034857638&widgetType=HTML&widgetId=HTML12&action=editWidget&sectio…

    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 512, Column 107: reference not terminated by REFC delimiter
    …0203034857638&widgetType=HTML&widgetId=HTML12&action=editWidget&sectionId=head…

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

  • Warning Line 512, Column 107: reference to external entity in attribute value
    …0203034857638&widgetType=HTML&widgetId=HTML12&action=editWidget&sectionId=head…

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

  • Error Line 512, Column 107: reference to entity "widgetId" for which no system identifier could be generated
    …0203034857638&widgetType=HTML&widgetId=HTML12&action=editWidget&sectionId=head…

    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 512, Column 98: entity was defined here
    …ID=5324470203034857638&widgetType=HTML&widgetId=HTML12&action=editWidget&secti…
  • Warning Line 512, Column 115: cannot generate system identifier for general entity "action"
    …57638&widgetType=HTML&widgetId=HTML12&action=editWidget&sectionId=headerAds' o…

    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 512, Column 115: general entity "action" not defined and no default entity
    …57638&widgetType=HTML&widgetId=HTML12&action=editWidget&sectionId=headerAds' o…

    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 512, Column 121: reference not terminated by REFC delimiter
    …widgetType=HTML&widgetId=HTML12&action=editWidget&sectionId=headerAds' onclick…

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

  • Warning Line 512, Column 121: reference to external entity in attribute value
    …widgetType=HTML&widgetId=HTML12&action=editWidget&sectionId=headerAds' onclick…

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

  • Error Line 512, Column 121: reference to entity "action" for which no system identifier could be generated
    …widgetType=HTML&widgetId=HTML12&action=editWidget&sectionId=headerAds' onclick…

    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 512, Column 114: entity was defined here
    …857638&widgetType=HTML&widgetId=HTML12&action=editWidget&sectionId=headerAds' …
  • Warning Line 512, Column 133: cannot generate system identifier for general entity "sectionId"
    …TML&widgetId=HTML12&action=editWidget&sectionId=headerAds' onclick='return _Wi…

    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 512, Column 133: general entity "sectionId" not defined and no default entity
    …TML&widgetId=HTML12&action=editWidget&sectionId=headerAds' onclick='return _Wi…

    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 512, Column 142: reference not terminated by REFC delimiter
    …tId=HTML12&action=editWidget&sectionId=headerAds' onclick='return _WidgetManag…

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

  • Warning Line 512, Column 142: reference to external entity in attribute value
    …tId=HTML12&action=editWidget&sectionId=headerAds' onclick='return _WidgetManag…

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

  • Error Line 512, Column 142: reference to entity "sectionId" for which no system identifier could be generated
    …tId=HTML12&action=editWidget&sectionId=headerAds' onclick='return _WidgetManag…

    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 512, Column 132: entity was defined here
    …HTML&widgetId=HTML12&action=editWidget&sectionId=headerAds' onclick='return _W…
  • Error Line 541, Column 74: 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 name='cx' type='hidden' value='011202849595459924334:51xylm-uzxc'/>

    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 542, Column 242: 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
    …x; width:830px; text-indent:127px; padding: 5px; font-size: 16px' type='text'/>

    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 543, Column 43: 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 name='hl' type='hidden' value='en'/>

    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 544, Column 88: 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
    …orange' style='font-weight: bold' type='submit' value='Telusuri'/></form></div>

    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 555, Column 102: character "&" is the first character of a delimiter but occurred as data
    …iller-full-265.html'>Norton Utilities & Task Killer Full 2.6.5 for Android</a>…

    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 567, Column 131: there is no attribute "imageanchor"
    …ton+Mobile+Utilities.png" imageanchor="1" style="clear: left; float: left; mar…

    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 567, Column 339: required attribute "alt" not specified
    …QdybcwI/AAAAAAAAHWQ/GU-CIUMWlnE/s1600/Norton+Mobile+Utilities.png" /></a></div>

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

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

  • Error Line 572, Column 132: required attribute "alt" not specified
    …UQpgzlXw9gI/AAAAAAAAHVI/IZDtY4UNDso/s1600/Norton+Mobile+Utilities.jpg" /></div>

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

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

  • Error Line 577, Column 3: document type does not allow element "b" here; assuming missing "li" start-tag
    <b>Password : <input class="box-password" onclick="select()" type="text" value=…
  • Error Line 577, Column 191: end tag for "li" omitted, but OMITTAG NO was specified
    …span style="color: #38761d;">Tested</span></b> (Samsung Galaxy Y GT-S5360)</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 577, Column 1: start tag was here
    <b>Password : <input class="box-password" onclick="select()" type="text" value=…
  • Error Line 590, Column 24: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div class='labelbagas'>

    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 623, Column 86: there is no attribute "trbidi"
    …mmary4052145231290912400'><div dir="ltr" style="text-align: left;" trbidi="on">

    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 625, Column 405: required attribute "alt" not specified
    …1600/internet+download+manager+full+keygen+patch+crack+serial.png" /></a></div>

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

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

  • Error Line 636, Column 335: required attribute "alt" not specified
    …AAAAAALA/Y0xzVdgfHMA/s400/capture-20130130-133443.png" width="400" /></a></div>

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

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

  • Error Line 663, Column 24: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div class='labelbagas'>

    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 700, Column 378: required attribute "alt" not specified
    …k/HOtEBDon0h8/s320/box_ashampoo_snap_6_800x800_rgb.jpg" width="80" /></a></div>

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

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

  • Error Line 708, Column 347: required attribute "alt" not specified
    …s/WzvoforTg50/s1600/scr_ashampoo_snap_6_en_overview_functions.jpg" /></a></div>

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

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

  • Error Line 741, Column 24: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div class='labelbagas'>

    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 779, Column 309: required attribute "alt" not specified
    …1lQJGAa-BY/UQXafm6iFtI/AAAAAAAAAJE/Drjk3RhhYus/s1600/Ashampoo.png" /></a></div>

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

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

  • Error Line 792, Column 325: required attribute "alt" not specified
    …/AAAAAAAAAKQ/myItCD_sA38/s1600/Ashampoo+WinOptimizer+2013+(2).png" /></a></div>

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

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

  • Error Line 817, Column 24: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div class='labelbagas'>

    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 849, Column 214: required attribute "alt" not specified
    …com/-rHpziNY3IAg/UMQ6KQW7zEI/AAAAAAAAElc/9kLoImOY9F0/s1600/ads.jpg"/></a></div>

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

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

  • Warning Line 853, Column 93: reference not terminated by REFC delimiter
    …?blogID=5324470203034857638&widgetType=HTML&widgetId=HTML4&action=editWidget&s…

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

  • Warning Line 853, Column 93: reference to external entity in attribute value
    …?blogID=5324470203034857638&widgetType=HTML&widgetId=HTML4&action=editWidget&s…

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

  • Error Line 853, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=5324470203034857638&widgetType=HTML&widgetId=HTML4&action=editWidget&s…

    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 512, Column 82: entity was defined here
    …m/rearrange?blogID=5324470203034857638&widgetType=HTML&widgetId=HTML12&action=…
  • Warning Line 853, Column 107: reference not terminated by REFC delimiter
    …0203034857638&widgetType=HTML&widgetId=HTML4&action=editWidget&sectionId=s-sid…

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

  • Warning Line 853, Column 107: reference to external entity in attribute value
    …0203034857638&widgetType=HTML&widgetId=HTML4&action=editWidget&sectionId=s-sid…

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

  • Error Line 853, Column 107: reference to entity "widgetId" for which no system identifier could be generated
    …0203034857638&widgetType=HTML&widgetId=HTML4&action=editWidget&sectionId=s-sid…

    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 512, Column 98: entity was defined here
    …ID=5324470203034857638&widgetType=HTML&widgetId=HTML12&action=editWidget&secti…
  • Warning Line 853, Column 120: reference not terminated by REFC delimiter
    …&widgetType=HTML&widgetId=HTML4&action=editWidget&sectionId=s-sidebar' onclick…

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

  • Warning Line 853, Column 120: reference to external entity in attribute value
    …&widgetType=HTML&widgetId=HTML4&action=editWidget&sectionId=s-sidebar' onclick…

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

  • Error Line 853, Column 120: reference to entity "action" for which no system identifier could be generated
    …&widgetType=HTML&widgetId=HTML4&action=editWidget&sectionId=s-sidebar' onclick…

    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 512, Column 114: entity was defined here
    …857638&widgetType=HTML&widgetId=HTML12&action=editWidget&sectionId=headerAds' …
  • Warning Line 853, Column 141: reference not terminated by REFC delimiter
    …etId=HTML4&action=editWidget&sectionId=s-sidebar' onclick='return _WidgetManag…

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

  • Warning Line 853, Column 141: reference to external entity in attribute value
    …etId=HTML4&action=editWidget&sectionId=s-sidebar' onclick='return _WidgetManag…

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

  • Error Line 853, Column 141: reference to entity "sectionId" for which no system identifier could be generated
    …etId=HTML4&action=editWidget&sectionId=s-sidebar' onclick='return _WidgetManag…

    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 512, Column 132: entity was defined here
    …HTML&widgetId=HTML12&action=editWidget&sectionId=headerAds' onclick='return _W…
  • Error Line 867, Column 188: required attribute "alt" not specified
    …MM/UQYbyXjea4I/AAAAAAAAEuM/B1-8y6sJCA8/s1600/adspre.gif" border="0"/></a></div>

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

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

  • Warning Line 871, Column 93: reference not terminated by REFC delimiter
    …?blogID=5324470203034857638&widgetType=HTML&widgetId=HTML3&action=editWidget&s…

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

  • Warning Line 871, Column 93: reference to external entity in attribute value
    …?blogID=5324470203034857638&widgetType=HTML&widgetId=HTML3&action=editWidget&s…

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

  • Error Line 871, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=5324470203034857638&widgetType=HTML&widgetId=HTML3&action=editWidget&s…

    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 512, Column 82: entity was defined here
    …m/rearrange?blogID=5324470203034857638&widgetType=HTML&widgetId=HTML12&action=…
  • Warning Line 871, Column 107: reference not terminated by REFC delimiter
    …0203034857638&widgetType=HTML&widgetId=HTML3&action=editWidget&sectionId=sideb…

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

  • Warning Line 871, Column 107: reference to external entity in attribute value
    …0203034857638&widgetType=HTML&widgetId=HTML3&action=editWidget&sectionId=sideb…

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

  • Error Line 871, Column 107: reference to entity "widgetId" for which no system identifier could be generated
    …0203034857638&widgetType=HTML&widgetId=HTML3&action=editWidget&sectionId=sideb…

    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 512, Column 98: entity was defined here
    …ID=5324470203034857638&widgetType=HTML&widgetId=HTML12&action=editWidget&secti…
  • Warning Line 871, Column 120: reference not terminated by REFC delimiter
    …&widgetType=HTML&widgetId=HTML3&action=editWidget&sectionId=sidebar' onclick='…

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

  • Warning Line 871, Column 120: reference to external entity in attribute value
    …&widgetType=HTML&widgetId=HTML3&action=editWidget&sectionId=sidebar' onclick='…

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

  • Error Line 871, Column 120: reference to entity "action" for which no system identifier could be generated
    …&widgetType=HTML&widgetId=HTML3&action=editWidget&sectionId=sidebar' onclick='…

    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 512, Column 114: entity was defined here
    …857638&widgetType=HTML&widgetId=HTML12&action=editWidget&sectionId=headerAds' …
  • Warning Line 871, Column 141: reference not terminated by REFC delimiter
    …etId=HTML3&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

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

  • Warning Line 871, Column 141: reference to external entity in attribute value
    …etId=HTML3&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

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

  • Error Line 871, Column 141: reference to entity "sectionId" for which no system identifier could be generated
    …etId=HTML3&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

    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 512, Column 132: entity was defined here
    …HTML&widgetId=HTML12&action=editWidget&sectionId=headerAds' onclick='return _W…
  • Warning Line 1109, Column 117: character "&" is the first character of a delimiter but occurred as data
    …full.html" target="_blank">Xara Photo & Graphic Designer MX 8.1 Full Crack</a>…

    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 1186, Column 123: character "&" is the first character of a delimiter but occurred as data
    …html" target="_blank">Nero Burning ROM & Nero Express 11.2 Full Serial</a></li>

    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 1345, Column 123: character "&" is the first character of a delimiter but occurred as data
    …1-for-ntfs-fat.html" target="_blank">GetDataBack 4.21 for (NTFS & FAT)</a></li>

    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 1439, Column 13: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <li><a href=http://www.bagas31.com/2011/12/advanced-system-optimizer-32.html" t…
  • Error Line 1439, Column 19: NET-enabling start-tag not immediately followed by null end-tag
    <li><a href=http://www.bagas31.com/2011/12/advanced-system-optimizer-32.html" t…

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

  • Error Line 1439, Column 127: end tag for element "a" which is not open
    …ystem-optimizer-32.html" target="_blank">Advanced System Optimizer 3.2</a></li>

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

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

  • Warning Line 1492, Column 138: character "&" is the first character of a delimiter but occurred as data
    …-rip.html" target="_blank">Marine Sharpshooter 4 : Locked & Loaded Rip</a></li>

    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 1533, Column 104: character "&" is the first character of a delimiter but occurred as data
    …enegade-rip.html" target="_blank">Command & Conouer : Renegade ( Rip )</a></li>

    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 1537, Column 113: character "&" is the first character of a delimiter but occurred as data
    …ortable.html" target="_blank">Command & Conguare : Red Alert 2 Portable (190 M…

    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 1548, Column 104: character "&" is the first character of a delimiter but occurred as data
    …are-red-alert-3.html" target="_blank">Command & Conquare : Red Alert 3</a></li>

    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 1585, Column 143: character "&" is the first character of a delimiter but occurred as data
    …epat.html" target="_blank">Everything | Cari File dengan Mudah & Cepat</a></li>

    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 1603, Column 92: character "&" is the first character of a delimiter but occurred as data
    …10/tom-jerry-house-trap.html" target="_blank">Tom & Jerry : House Trap</a></li>

    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 1716, Column 118: character "&" is the first character of a delimiter but occurred as data
    …ne-download.html" target="_blank">Quiz Parampaa 1 & 2 Offline Download</a></li>

    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 1888, Column 116: character "&" is the first character of a delimiter but occurred as data
    …ble-edition.html" target="_blank">Monopoly Here & Now Portable Edition</a></li>

    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 1983, Column 93: reference not terminated by REFC delimiter
    …?blogID=5324470203034857638&widgetType=HTML&widgetId=HTML7&action=editWidget&s…

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

  • Warning Line 1983, Column 93: reference to external entity in attribute value
    …?blogID=5324470203034857638&widgetType=HTML&widgetId=HTML7&action=editWidget&s…

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

  • Error Line 1983, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=5324470203034857638&widgetType=HTML&widgetId=HTML7&action=editWidget&s…

    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 512, Column 82: entity was defined here
    …m/rearrange?blogID=5324470203034857638&widgetType=HTML&widgetId=HTML12&action=…
  • Warning Line 1983, Column 107: reference not terminated by REFC delimiter
    …0203034857638&widgetType=HTML&widgetId=HTML7&action=editWidget&sectionId=sideb…

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

  • Warning Line 1983, Column 107: reference to external entity in attribute value
    …0203034857638&widgetType=HTML&widgetId=HTML7&action=editWidget&sectionId=sideb…

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

  • Error Line 1983, Column 107: reference to entity "widgetId" for which no system identifier could be generated
    …0203034857638&widgetType=HTML&widgetId=HTML7&action=editWidget&sectionId=sideb…

    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 512, Column 98: entity was defined here
    …ID=5324470203034857638&widgetType=HTML&widgetId=HTML12&action=editWidget&secti…
  • Warning Line 1983, Column 120: reference not terminated by REFC delimiter
    …&widgetType=HTML&widgetId=HTML7&action=editWidget&sectionId=sidebar' onclick='…

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

  • Warning Line 1983, Column 120: reference to external entity in attribute value
    …&widgetType=HTML&widgetId=HTML7&action=editWidget&sectionId=sidebar' onclick='…

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

  • Error Line 1983, Column 120: reference to entity "action" for which no system identifier could be generated
    …&widgetType=HTML&widgetId=HTML7&action=editWidget&sectionId=sidebar' onclick='…

    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 512, Column 114: entity was defined here
    …857638&widgetType=HTML&widgetId=HTML12&action=editWidget&sectionId=headerAds' …
  • Warning Line 1983, Column 141: reference not terminated by REFC delimiter
    …etId=HTML7&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

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

  • Warning Line 1983, Column 141: reference to external entity in attribute value
    …etId=HTML7&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

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

  • Error Line 1983, Column 141: reference to entity "sectionId" for which no system identifier could be generated
    …etId=HTML7&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

    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 512, Column 132: entity was defined here
    …HTML&widgetId=HTML12&action=editWidget&sectionId=headerAds' onclick='return _W…
  • Error Line 1992, Column 195: required attribute "alt" not specified
    …-3_B088QDGwQ/UBSzvYyfXtI/AAAAAAAADtY/m4GMFO4kBjc/s1600/twitter.gif"/></a></div>

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

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

  • Error Line 1994, Column 81: element "center" undefined
    …in-top:-15px;padding-top:5px;"><center><a href="http://haidaralishare.blogspot…

    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 1994, Column 309: required attribute "alt" not specified
    …BAb77NI/AAAAAAAAEm8/fyq1HLs8cIk/s1600/ads.jpg" width="288"/></a></center></div>

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

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

  • Warning Line 1999, Column 93: reference not terminated by REFC delimiter
    …?blogID=5324470203034857638&widgetType=HTML&widgetId=HTML13&action=editWidget&…

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

  • Warning Line 1999, Column 93: reference to external entity in attribute value
    …?blogID=5324470203034857638&widgetType=HTML&widgetId=HTML13&action=editWidget&…

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

  • Error Line 1999, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=5324470203034857638&widgetType=HTML&widgetId=HTML13&action=editWidget&…

    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 512, Column 82: entity was defined here
    …m/rearrange?blogID=5324470203034857638&widgetType=HTML&widgetId=HTML12&action=…
  • Warning Line 1999, Column 107: reference not terminated by REFC delimiter
    …0203034857638&widgetType=HTML&widgetId=HTML13&action=editWidget&sectionId=side…

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

  • Warning Line 1999, Column 107: reference to external entity in attribute value
    …0203034857638&widgetType=HTML&widgetId=HTML13&action=editWidget&sectionId=side…

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

  • Error Line 1999, Column 107: reference to entity "widgetId" for which no system identifier could be generated
    …0203034857638&widgetType=HTML&widgetId=HTML13&action=editWidget&sectionId=side…

    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 512, Column 98: entity was defined here
    …ID=5324470203034857638&widgetType=HTML&widgetId=HTML12&action=editWidget&secti…
  • Warning Line 1999, Column 121: reference not terminated by REFC delimiter
    …widgetType=HTML&widgetId=HTML13&action=editWidget&sectionId=sidebar' onclick='…

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

  • Warning Line 1999, Column 121: reference to external entity in attribute value
    …widgetType=HTML&widgetId=HTML13&action=editWidget&sectionId=sidebar' onclick='…

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

  • Error Line 1999, Column 121: reference to entity "action" for which no system identifier could be generated
    …widgetType=HTML&widgetId=HTML13&action=editWidget&sectionId=sidebar' onclick='…

    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 512, Column 114: entity was defined here
    …857638&widgetType=HTML&widgetId=HTML12&action=editWidget&sectionId=headerAds' …
  • Warning Line 1999, Column 142: reference not terminated by REFC delimiter
    …tId=HTML13&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

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

  • Warning Line 1999, Column 142: reference to external entity in attribute value
    …tId=HTML13&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

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

  • Error Line 1999, Column 142: reference to entity "sectionId" for which no system identifier could be generated
    …tId=HTML13&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

    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 512, Column 132: entity was defined here
    …HTML&widgetId=HTML12&action=editWidget&sectionId=headerAds' onclick='return _W…
  • Warning Line 2013, Column 93: reference not terminated by REFC delimiter
    …?blogID=5324470203034857638&widgetType=HTML&widgetId=HTML8&action=editWidget&s…

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

  • Warning Line 2013, Column 93: reference to external entity in attribute value
    …?blogID=5324470203034857638&widgetType=HTML&widgetId=HTML8&action=editWidget&s…

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

  • Error Line 2013, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=5324470203034857638&widgetType=HTML&widgetId=HTML8&action=editWidget&s…

    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 512, Column 82: entity was defined here
    …m/rearrange?blogID=5324470203034857638&widgetType=HTML&widgetId=HTML12&action=…
  • Warning Line 2013, Column 107: reference not terminated by REFC delimiter
    …0203034857638&widgetType=HTML&widgetId=HTML8&action=editWidget&sectionId=sideb…

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

  • Warning Line 2013, Column 107: reference to external entity in attribute value
    …0203034857638&widgetType=HTML&widgetId=HTML8&action=editWidget&sectionId=sideb…

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

  • Error Line 2013, Column 107: reference to entity "widgetId" for which no system identifier could be generated
    …0203034857638&widgetType=HTML&widgetId=HTML8&action=editWidget&sectionId=sideb…

    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 512, Column 98: entity was defined here
    …ID=5324470203034857638&widgetType=HTML&widgetId=HTML12&action=editWidget&secti…
  • Warning Line 2013, Column 120: reference not terminated by REFC delimiter
    …&widgetType=HTML&widgetId=HTML8&action=editWidget&sectionId=sidebar' onclick='…

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

  • Warning Line 2013, Column 120: reference to external entity in attribute value
    …&widgetType=HTML&widgetId=HTML8&action=editWidget&sectionId=sidebar' onclick='…

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

  • Error Line 2013, Column 120: reference to entity "action" for which no system identifier could be generated
    …&widgetType=HTML&widgetId=HTML8&action=editWidget&sectionId=sidebar' onclick='…

    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 512, Column 114: entity was defined here
    …857638&widgetType=HTML&widgetId=HTML12&action=editWidget&sectionId=headerAds' …
  • Warning Line 2013, Column 141: reference not terminated by REFC delimiter
    …etId=HTML8&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

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

  • Warning Line 2013, Column 141: reference to external entity in attribute value
    …etId=HTML8&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

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

  • Error Line 2013, Column 141: reference to entity "sectionId" for which no system identifier could be generated
    …etId=HTML8&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

    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 512, Column 132: entity was defined here
    …HTML&widgetId=HTML12&action=editWidget&sectionId=headerAds' onclick='return _W…
  • Error Line 2020, Column 41: there is no attribute "src"
    …iv class='widget-content'><iframe src="//www.facebook.com/plugins/likebox.php?…

    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 2020, Column 295: there is no attribute "scrolling"
    …&amp;appId=241220852594687" scrolling="no" frameborder="0" style="border: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 2020, Column 312: there is no attribute "frameborder"
    …852594687" scrolling="no" frameborder="0" style="border:none; overflow:hidden;…

    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 2020, Column 322: there is no attribute "style"
    … scrolling="no" frameborder="0" style="border:none; overflow:hidden; width:288…

    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 2020, Column 399: there is no attribute "allowtransparency"
    …ow:hidden; width:288px; height:292px;" 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 2020, Column 405: element "iframe" undefined
    …ow:hidden; width:288px; height:292px;" 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).
  • Warning Line 2024, Column 93: reference not terminated by REFC delimiter
    …?blogID=5324470203034857638&widgetType=HTML&widgetId=HTML11&action=editWidget&…

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

  • Warning Line 2024, Column 93: reference to external entity in attribute value
    …?blogID=5324470203034857638&widgetType=HTML&widgetId=HTML11&action=editWidget&…

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

  • Error Line 2024, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=5324470203034857638&widgetType=HTML&widgetId=HTML11&action=editWidget&…

    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 512, Column 82: entity was defined here
    …m/rearrange?blogID=5324470203034857638&widgetType=HTML&widgetId=HTML12&action=…
  • Warning Line 2024, Column 107: reference not terminated by REFC delimiter
    …0203034857638&widgetType=HTML&widgetId=HTML11&action=editWidget&sectionId=side…

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

  • Warning Line 2024, Column 107: reference to external entity in attribute value
    …0203034857638&widgetType=HTML&widgetId=HTML11&action=editWidget&sectionId=side…

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

  • Error Line 2024, Column 107: reference to entity "widgetId" for which no system identifier could be generated
    …0203034857638&widgetType=HTML&widgetId=HTML11&action=editWidget&sectionId=side…

    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 512, Column 98: entity was defined here
    …ID=5324470203034857638&widgetType=HTML&widgetId=HTML12&action=editWidget&secti…
  • Warning Line 2024, Column 121: reference not terminated by REFC delimiter
    …widgetType=HTML&widgetId=HTML11&action=editWidget&sectionId=sidebar' onclick='…

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

  • Warning Line 2024, Column 121: reference to external entity in attribute value
    …widgetType=HTML&widgetId=HTML11&action=editWidget&sectionId=sidebar' onclick='…

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

  • Error Line 2024, Column 121: reference to entity "action" for which no system identifier could be generated
    …widgetType=HTML&widgetId=HTML11&action=editWidget&sectionId=sidebar' onclick='…

    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 512, Column 114: entity was defined here
    …857638&widgetType=HTML&widgetId=HTML12&action=editWidget&sectionId=headerAds' …
  • Warning Line 2024, Column 142: reference not terminated by REFC delimiter
    …tId=HTML11&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

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

  • Warning Line 2024, Column 142: reference to external entity in attribute value
    …tId=HTML11&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

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

  • Error Line 2024, Column 142: reference to entity "sectionId" for which no system identifier could be generated
    …tId=HTML11&action=editWidget&sectionId=sidebar' onclick='return _WidgetManager…

    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 512, Column 132: entity was defined here
    …HTML&widgetId=HTML12&action=editWidget&sectionId=headerAds' onclick='return _W…
  • Error Line 2042, Column 141: there is no attribute "target"
    …fb/a/mailverify" method="post" target="popupwindow" onsubmit="window.open('htt…

    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 2042, Column 316: there is no attribute "color"
    …height=520');return true"><font color="#000000">Kirim Update Software Terbaru …

    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 2042, Column 325: element "font" undefined
    …0');return true"><font color="#000000">Kirim Update Software Terbaru Untuk <br…

    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 2042, Column 425: document type does not allow element "br" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …aru Untuk <br /><b>Sobat BAGAS31</b> Langsung ke Email Sobat !</font><br/><br/>

    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 2042, Column 430: document type does not allow element "br" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …aru Untuk <br /><b>Sobat BAGAS31</b> Langsung ke Email Sobat !</font><br/><br/>

    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 2043, Column 82: there is no attribute "placeholder"
    …" class='input' size="30" placeholder="Masukan Email Anda..." name="email" /><…

    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 2044, Column 106: document type does not allow element "p" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …alue="GO" type="submit" /><br/><br/><p><a href="http://feeds.feedburner.com/Ba…

    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 2053, Column 93: reference not terminated by REFC delimiter
    …?blogID=5324470203034857638&widgetType=HTML&widgetId=HTML2&action=editWidget&s…

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

  • Warning Line 2053, Column 93: reference to external entity in attribute value
    …?blogID=5324470203034857638&widgetType=HTML&widgetId=HTML2&action=editWidget&s…

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

  • Error Line 2053, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=5324470203034857638&widgetType=HTML&widgetId=HTML2&action=editWidget&s…

    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 512, Column 82: entity was defined here
    …m/rearrange?blogID=5324470203034857638&widgetType=HTML&widgetId=HTML12&action=…
  • Warning Line 2053, Column 107: reference not terminated by REFC delimiter
    …0203034857638&widgetType=HTML&widgetId=HTML2&action=editWidget&sectionId=f-tag…

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

  • Warning Line 2053, Column 107: reference to external entity in attribute value
    …0203034857638&widgetType=HTML&widgetId=HTML2&action=editWidget&sectionId=f-tag…

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

  • Error Line 2053, Column 107: reference to entity "widgetId" for which no system identifier could be generated
    …0203034857638&widgetType=HTML&widgetId=HTML2&action=editWidget&sectionId=f-tag…

    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 512, Column 98: entity was defined here
    …ID=5324470203034857638&widgetType=HTML&widgetId=HTML12&action=editWidget&secti…
  • Warning Line 2053, Column 120: reference not terminated by REFC delimiter
    …&widgetType=HTML&widgetId=HTML2&action=editWidget&sectionId=f-tag' onclick='re…

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

  • Warning Line 2053, Column 120: reference to external entity in attribute value
    …&widgetType=HTML&widgetId=HTML2&action=editWidget&sectionId=f-tag' onclick='re…

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

  • Error Line 2053, Column 120: reference to entity "action" for which no system identifier could be generated
    …&widgetType=HTML&widgetId=HTML2&action=editWidget&sectionId=f-tag' onclick='re…

    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 512, Column 114: entity was defined here
    …857638&widgetType=HTML&widgetId=HTML12&action=editWidget&sectionId=headerAds' …
  • Warning Line 2053, Column 141: reference not terminated by REFC delimiter
    …etId=HTML2&action=editWidget&sectionId=f-tag' onclick='return _WidgetManager._…

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

  • Warning Line 2053, Column 141: reference to external entity in attribute value
    …etId=HTML2&action=editWidget&sectionId=f-tag' onclick='return _WidgetManager._…

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

  • Error Line 2053, Column 141: reference to entity "sectionId" for which no system identifier could be generated
    …etId=HTML2&action=editWidget&sectionId=f-tag' onclick='return _WidgetManager._…

    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 512, Column 132: entity was defined here
    …HTML&widgetId=HTML12&action=editWidget&sectionId=headerAds' onclick='return _W…
  • Warning Line 2091, Column 93: reference not terminated by REFC delimiter
    …?blogID=5324470203034857638&widgetType=HTML&widgetId=HTML5&action=editWidget&s…

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

  • Warning Line 2091, Column 93: reference to external entity in attribute value
    …?blogID=5324470203034857638&widgetType=HTML&widgetId=HTML5&action=editWidget&s…

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

  • Error Line 2091, Column 93: reference to entity "widgetType" for which no system identifier could be generated
    …?blogID=5324470203034857638&widgetType=HTML&widgetId=HTML5&action=editWidget&s…

    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 512, Column 82: entity was defined here
    …m/rearrange?blogID=5324470203034857638&widgetType=HTML&widgetId=HTML12&action=…
  • Warning Line 2091, Column 107: reference not terminated by REFC delimiter
    …0203034857638&widgetType=HTML&widgetId=HTML5&action=editWidget&sectionId=f-ad'…

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

  • Warning Line 2091, Column 107: reference to external entity in attribute value
    …0203034857638&widgetType=HTML&widgetId=HTML5&action=editWidget&sectionId=f-ad'…

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

  • Error Line 2091, Column 107: reference to entity "widgetId" for which no system identifier could be generated
    …0203034857638&widgetType=HTML&widgetId=HTML5&action=editWidget&sectionId=f-ad'…

    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 512, Column 98: entity was defined here
    …ID=5324470203034857638&widgetType=HTML&widgetId=HTML12&action=editWidget&secti…
  • Warning Line 2091, Column 120: reference not terminated by REFC delimiter
    …&widgetType=HTML&widgetId=HTML5&action=editWidget&sectionId=f-ad' onclick='ret…

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

  • Warning Line 2091, Column 120: reference to external entity in attribute value
    …&widgetType=HTML&widgetId=HTML5&action=editWidget&sectionId=f-ad' onclick='ret…

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

  • Error Line 2091, Column 120: reference to entity "action" for which no system identifier could be generated
    …&widgetType=HTML&widgetId=HTML5&action=editWidget&sectionId=f-ad' onclick='ret…

    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 512, Column 114: entity was defined here
    …857638&widgetType=HTML&widgetId=HTML12&action=editWidget&sectionId=headerAds' …
  • Warning Line 2091, Column 141: reference not terminated by REFC delimiter
    …etId=HTML5&action=editWidget&sectionId=f-ad' onclick='return _WidgetManager._P…

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

  • Warning Line 2091, Column 141: reference to external entity in attribute value
    …etId=HTML5&action=editWidget&sectionId=f-ad' onclick='return _WidgetManager._P…

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

  • Error Line 2091, Column 141: reference to entity "sectionId" for which no system identifier could be generated
    …etId=HTML5&action=editWidget&sectionId=f-ad' onclick='return _WidgetManager._P…

    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 512, Column 132: entity was defined here
    …HTML&widgetId=HTML12&action=editWidget&sectionId=headerAds' onclick='return _W…
  • Error Line 2105, Column 21: required attribute "type" not specified
    <script id='_waude1'>var _wau = _wau || []; _wau.push(["small", "8ejm4iynxnab",…

    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 2120, Column 28: element "center" undefined
    <div id='trik_atas'><center><a href='http://borneoadvertisements.com/' rel='nof…

    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 2120, Column 213: required attribute "alt" not specified
    …AAAAAAAEsw/ddPU3GUpLHI/s1600/ads.jpg'/></a></center></div><script src='http://…

    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 2122, 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 2148, Column 49: character "&" is the first character of a delimiter but occurred as data
    …(BLOG_attachCsiOnload) != 'undefined' && BLOG_attachCsiOnload != null) { windo…

    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 2148, Column 50: character "&" is the first character of a delimiter but occurred as data
    …BLOG_attachCsiOnload) != 'undefined' && BLOG_attachCsiOnload != null) { window…

    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.

Visitor Analysis

Daily Visitor
  • 11.200 visits

In Page Analysis