pinoy-ako.info

Pinoy Ako Online Community for Filipinos all over the world. Miss mo ba Pinas? Watch Pinoy Live TV ABS-CBN 2, GMA 7, TV5, CS9 and more.. Listen to pinoy radio, watch pinoy movies ...

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

Overview Info

  • Domain Name
    pinoy-ako.info
  • Favicon
  • Alexa Rank
    #2671
  • Google Page Rank
    PR 1
  • Ip Address
    109.201.133.185
  • Page Size
    95.7 KB
  • Images
    3 GIF, 64 JPG, 7 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    0 0 3 0 0 0

Website Meta Analysis



  • Title
    Pinoy Ako Online Tambayan - Pinoy Live TV, Movies, Radio, News and more
  • Meta Keyword
    'watch filipino channel', 'pinoy channel', 'philippine basketball association, 'watch nba', 'radio philippines', 'pinoy radio', 'listen radio philippines', 'watch pinoy movies', 'watch gma 7', 'watch kapuso', 'watch kapamilya', 'watch abscbn 2', 'pinoy tv', 'pinoy movies', 'chat pinoy', 'chat pinay', 'news philippines', 'tv station philippines', 'pinoy news', 'watch wowowee', 'watch eat bulaga', 'eat bulaga', 'wowowee', 'watch tv patrol', 'live news philippines', 'live pinoy tv', 'pinoy tambayan', 'pinoy showbiz', 'smart gilas', 'watch pba', 'watch pacquaio fight','pacquiao fight', 'pacquaio cotto', 'pinoy', 'pinay', 'filipina', 'filipino', 'noypi', 'news philippines', 'pinoy community', 'filipino community', 'pinoy worker', 'caregiver', 'filipino worker', 'ofw', 'ocw', 'seaman', 'nurse', 'dh', 'domestic helper', 'japayuki', 'philippines', 'work abroad', 'work overseas', 'japan', 'dubai', 'filam', 'filipino american', 'filipino in america', 'pinoy in america', 'pinoy in USA', 'canada', 'pinoy in canada', 'skilled worker', 'waiter', 'saudi', 'pinoy in saudi', 'riyadh', 'europe', 'italy', 'singapore', 'hong kong', 'uk', 'pinoy in uk', 'cebuano', 'ilocano', 'bisaya', 'ilonggo', 'muslim', 'manila', 'kapampangan', 'probinsya', 'local tv', 'live steaming', 'pacquiao', 'abscbn', 'gma7', 'gma', 'abscbn 2', 'pinoy movies', 'movies', 'chat', 'teleserye', 'kababayan', 'pacquiao mayweather', 'pinoy big brother', 'pbb double up', '24 oras'
  • Meta Description
    Pinoy Ako Online Community for Filipinos all over the world. Miss mo ba Pinas? Watch Pinoy Live TV ABS-CBN 2, GMA 7, TV5, CS9 and more.. Listen to pinoy radio, watch pinoy movies or chat with our kababayans. Pasok na!

Technical Analysis



  • Webserver
    nginx
  • Ip Address
    109.201.133.185
  • Domain Age
    3 Years, 12 Months, 17 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from pinoy-ako.info.

HTML Analysis

  • server: nginx
  • date: Thu, 19 Sep 2013 12:34:40 GMT
  • content-type: text/html; charset=utf-8
  • connection: keep-alive
  • vary: Accept-Encoding
  • x-powered-by: PHP/5.3.3
  • p3p: CP="NOI ADM DEV PSAi COM NAV OUR OTRo STP IND DEM"
  • expires: Thu, 19 Sep 2013 12:47:29 GMT
  • cache-control: public
  • x-cache-status: HIT
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Access to INFO WHOIS information is provided to assist persons in
determining the contents of a domain name registration record in the
Afilias registry database. The data in this record is provided by
Afilias Limited for informational purposes only, and Afilias does not
guarantee its accuracy. This service is intended only for query-based
access. You agree that you will use this data only for lawful purposes
and that, under no circumstances will you use this data to: (a) allow,
enable, or otherwise support the transmission by e-mail, telephone, or
facsimile of mass unsolicited, commercial advertising or solicitations
to entities other than the data recipient's own existing customers; or
(b) enable high volume, automated, electronic processes that send
queries or data to the systems of Registry Operator, a Registrar, or
Afilias except as reasonably necessary to register domain names or
modify existing registrations. All rights reserved. Afilias reserves
the right to modify these terms at any time. By submitting this query,
you agree to abide by this policy.

Domain ID:D29781239-LRMS
Domain Name:PINOY-AKO.INFO
Created On:23-Sep-2009 03:14:25 UTC
Last Updated On:23-Sep-2012 06:15:29 UTC
Expiration Date:23-Sep-2013 03:14:25 UTC
Sponsoring Registrar:Click Registrar, Inc. dba publicdomainregistry.com (R673-LRMS)
Status:CLIENT TRANSFER PROHIBITED
Status:TRANSFER PROHIBITED
Registrant ID:PP-SP-001
Registrant Name:Domain Admin
Registrant Organization:PrivacyProtect.org
Registrant Street1:ID#10760, PO Box 16
Registrant Street2:Note - All Postal Mails Rejected, visit Privacyprotect.org
Registrant Street3:
Registrant City:Nobby Beach
Registrant State/Province:
Registrant Postal Code:QLD 4218
Registrant Country:AU
Registrant Phone:+45.36946676
Registrant Phone Ext.:
Registrant FAX:
Registrant FAX Ext.:
Registrant Email: email
Admin ID:PP-SP-001
Admin Name:Domain Admin
Admin Organization:PrivacyProtect.org
Admin Street1:ID#10760, PO Box 16
Admin Street2:Note - All Postal Mails Rejected, visit Privacyprotect.org
Admin Street3:
Admin City:Nobby Beach
Admin State/Province:
Admin Postal Code:QLD 4218
Admin Country:AU
Admin Phone:+45.36946676
Admin Phone Ext.:
Admin FAX:
Admin FAX Ext.:
Admin Email: email
Billing ID:PP-SP-001
Billing Name:Domain Admin
Billing Organization:PrivacyProtect.org
Billing Street1:ID#10760, PO Box 16
Billing Street2:Note - All Postal Mails Rejected, visit Privacyprotect.org
Billing Street3:
Billing City:Nobby Beach
Billing State/Province:
Billing Postal Code:QLD 4218
Billing Country:AU
Billing Phone:+45.36946676
Billing Phone Ext.:
Billing FAX:
Billing FAX Ext.:
Billing Email: email
Tech ID:PP-SP-001
Tech Name:Domain Admin
Tech Organization:PrivacyProtect.org
Tech Street1:ID#10760, PO Box 16
Tech Street2:Note - All Postal Mails Rejected, visit Privacyprotect.org
Tech Street3:
Tech City:Nobby Beach
Tech State/Province:
Tech Postal Code:QLD 4218
Tech Country:AU
Tech Phone:+45.36946676
Tech Phone Ext.:
Tech FAX:
Tech FAX Ext.:
Tech Email: email
Name Server:NS1.PINOY-AKO.INFO
Name Server:NS2.PINOY-AKO.INFO
Name Server:
Name Server:
Name Server:
Name Server:
Name Server:
Name Server:
Name Server:
Name Server:
Name Server:
Name Server:
Name Server:

DNS Analysis


DNS servers
ns1.pinoy-ako.info [67.228.254.4]
ns2.pinoy-ako.info [67.228.255.5]


DNS Records

Answer records
pinoy-ako.info SOA
server: ns1.pinoy-ako.info
email: [email protected]
serial: 2012120500
refresh: 3600
retry: 300
expire: 604800
minimum ttl: 3600
900s
pinoy-ako.info NS  ns1.pinoy-ako.info 900s
pinoy-ako.info NS  ns2.pinoy-ako.info 900s
pinoy-ako.info A 199.193.116.231 900s
pinoy-ako.info MX
preference: 0
exchange: pinoy-ako.info
900s

Authority records

Additional records
ns1.pinoy-ako.info A 67.228.254.4 900s
ns2.pinoy-ako.info A 67.228.255.5 900s

IP 109.201.133.185 Analysis

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

Site Same Ip

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 84 Errors
  • 67 Warnings
Ratio Text/Html
  • 0.6563156927975182
Message Error
  • Error Line 89, Column 48: there is no attribute "TYPE"
    <link rel="stylesheet" href="/tabber.css" TYPE="text/css" MEDIA="screen">

    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 89, Column 65: there is no attribute "MEDIA"
    <link rel="stylesheet" href="/tabber.css" TYPE="text/css" MEDIA="screen">

    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 89, Column 74: end tag for "link" omitted, but OMITTAG NO was specified
    <link rel="stylesheet" href="/tabber.css" TYPE="text/css" MEDIA="screen">

    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 89, Column 1: start tag was here
    <link rel="stylesheet" href="/tabber.css" TYPE="text/css" MEDIA="screen">
  • Error Line 90, Column 79: end tag for "link" omitted, but OMITTAG NO was specified
    <link rel="stylesheet" href="/tabber-print.css" TYPE="text/css" MEDIA="print">

    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 90, Column 1: start tag was here
    <link rel="stylesheet" href="/tabber-print.css" TYPE="text/css" MEDIA="print">
  • Warning Line 178, Column 15: character "&" is the first character of a delimiter but occurred as data
    					Regional & Other Stations									</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 300, Column 13: character "&" is the first character of a delimiter but occurred as data
    					Movies & Videos										<span class="ux-menu-arrow"></span>

    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 306, Column 13: character "&" is the first character of a delimiter but occurred as data
    					Sports & Other Videos									</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 372, Column 21: there is no attribute "FRAMEBORDER"
    <IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=300 HEIGH…

    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 372, Column 21: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=300 HEIGH…
  • Error Line 372, Column 35: there is no attribute "MARGINWIDTH"
    <IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=300 HEIGH…

    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 372, Column 35: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=300 HEIGH…
  • Error Line 372, Column 50: there is no attribute "MARGINHEIGHT"
    …MEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=300 HEIGHT=250 SRC=…

    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 372, Column 50: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …MEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=300 HEIGHT=250 SRC=…
  • Error Line 372, Column 62: there is no attribute "SCROLLING"
    …ARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=300 HEIGHT=250 SRC="http://adse…

    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 372, Column 62: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=300 HEIGHT=250 SRC="http://adse…
  • Error Line 372, Column 71: there is no attribute "WIDTH"
    …H=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=300 HEIGHT=250 SRC="http://adserving.cpx…

    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 372, Column 71: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …H=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=300 HEIGHT=250 SRC="http://adserving.cpx…
  • Error Line 372, Column 82: there is no attribute "HEIGHT"
    …EIGHT=0 SCROLLING=NO WIDTH=300 HEIGHT=250 SRC="http://adserving.cpxinteractive…

    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 372, Column 82: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …EIGHT=0 SCROLLING=NO WIDTH=300 HEIGHT=250 SRC="http://adserving.cpxinteractive…
  • Error Line 372, Column 90: there is no attribute "SRC"
    …SCROLLING=NO WIDTH=300 HEIGHT=250 SRC="http://adserving.cpxinteractive.com/st?…

    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 372, Column 145: cannot generate system identifier for general entity "ad_size"
    ….cpxinteractive.com/st?ad_type=iframe&ad_size=300x250&section=3539354&pub_url=…

    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 372, Column 145: general entity "ad_size" not defined and no default entity
    ….cpxinteractive.com/st?ad_type=iframe&ad_size=300x250&section=3539354&pub_url=…

    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 372, Column 152: reference not terminated by REFC delimiter
    …eractive.com/st?ad_type=iframe&ad_size=300x250&section=3539354&pub_url=${PUB_U…

    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 372, Column 152: reference to external entity in attribute value
    …eractive.com/st?ad_type=iframe&ad_size=300x250&section=3539354&pub_url=${PUB_U…

    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 372, Column 152: reference to entity "ad_size" for which no system identifier could be generated
    …eractive.com/st?ad_type=iframe&ad_size=300x250&section=3539354&pub_url=${PUB_U…

    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 372, Column 144: entity was defined here
    …g.cpxinteractive.com/st?ad_type=iframe&ad_size=300x250&section=3539354&pub_url…
  • Warning Line 372, Column 161: cannot generate system identifier for general entity "section"
    …com/st?ad_type=iframe&ad_size=300x250&section=3539354&pub_url=${PUB_URL}"></IF…

    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 372, Column 161: general entity "section" not defined and no default entity
    …com/st?ad_type=iframe&ad_size=300x250&section=3539354&pub_url=${PUB_URL}"></IF…

    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 372, Column 168: reference not terminated by REFC delimiter
    …st?ad_type=iframe&ad_size=300x250&section=3539354&pub_url=${PUB_URL}"></IFRAME>

    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 372, Column 168: reference to external entity in attribute value
    …st?ad_type=iframe&ad_size=300x250&section=3539354&pub_url=${PUB_URL}"></IFRAME>

    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 372, Column 168: reference to entity "section" for which no system identifier could be generated
    …st?ad_type=iframe&ad_size=300x250&section=3539354&pub_url=${PUB_URL}"></IFRAME>

    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 372, Column 160: entity was defined here
    ….com/st?ad_type=iframe&ad_size=300x250&section=3539354&pub_url=${PUB_URL}"></I…
  • Warning Line 372, Column 177: cannot generate system identifier for general entity "pub_url"
    …st?ad_type=iframe&ad_size=300x250&section=3539354&pub_url=${PUB_URL}"></IFRAME>

    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 372, Column 177: general entity "pub_url" not defined and no default entity
    …st?ad_type=iframe&ad_size=300x250&section=3539354&pub_url=${PUB_URL}"></IFRAME>

    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 372, Column 184: reference not terminated by REFC delimiter
    …st?ad_type=iframe&ad_size=300x250&section=3539354&pub_url=${PUB_URL}"></IFRAME>

    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 372, Column 184: reference to external entity in attribute value
    …st?ad_type=iframe&ad_size=300x250&section=3539354&pub_url=${PUB_URL}"></IFRAME>

    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 372, Column 184: reference to entity "pub_url" for which no system identifier could be generated
    …st?ad_type=iframe&ad_size=300x250&section=3539354&pub_url=${PUB_URL}"></IFRAME>

    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 372, Column 176: entity was defined here
    …st?ad_type=iframe&ad_size=300x250&section=3539354&pub_url=${PUB_URL}"></IFRAME>
  • Error Line 372, Column 196: element "IFRAME" undefined
    …st?ad_type=iframe&ad_size=300x250&section=3539354&pub_url=${PUB_URL}"></IFRAME>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 379, Column 66: required attribute "type" not specified
    …	<script id="matomytm8id" src="http://tm.tagcontroller.com/8"></script>		</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 384, Column 86: ID "top" already defined
    …                                                  <table width="100%" id="top">

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 367, Column 70: ID "top" first defined here
                                    	         			<table width="100%" id="top">
  • Error Line 388, Column 24: there is no attribute "behavior"
    					<marquee behavior="alternate" style="color: #fdff69; font-weight:bold; fon…

    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 388, Column 42: there is no attribute "style"
    …		<marquee behavior="alternate" style="color: #fdff69; font-weight:bold; font-…

    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 388, Column 102: there is no attribute "bgcolor"
    …weight:bold; font-size:14px;" bgcolor="#050d60">&gt;&gt;&gt; WATCH PINOY LIVE …

    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 388, Column 111: element "marquee" undefined
    …ld; font-size:14px;" bgcolor="#050d60">&gt;&gt;&gt; WATCH PINOY LIVE TV &lt;&l…

    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 389, Column 600: cannot generate system identifier for general entity "view"
    …ako.info/index.php?option=com_content&view=article&id=48:tv-channel-5&catid=36…

    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 389, Column 600: general entity "view" not defined and no default entity
    …ako.info/index.php?option=com_content&view=article&id=48:tv-channel-5&catid=36…

    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 389, Column 604: reference not terminated by REFC delimiter
    …info/index.php?option=com_content&view=article&id=48:tv-channel-5&catid=36&Ite…

    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 389, Column 604: reference to external entity in attribute value
    …info/index.php?option=com_content&view=article&id=48:tv-channel-5&catid=36&Ite…

    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 389, Column 604: reference to entity "view" for which no system identifier could be generated
    …info/index.php?option=com_content&view=article&id=48:tv-channel-5&catid=36&Ite…

    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 389, Column 599: entity was defined here
    …-ako.info/index.php?option=com_content&view=article&id=48:tv-channel-5&catid=3…
  • Warning Line 389, Column 613: cannot generate system identifier for general entity "id"
    …x.php?option=com_content&view=article&id=48:tv-channel-5&catid=36&Itemid=55"><…

    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 389, Column 613: general entity "id" not defined and no default entity
    …x.php?option=com_content&view=article&id=48:tv-channel-5&catid=36&Itemid=55"><…

    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 389, Column 615: reference not terminated by REFC delimiter
    …php?option=com_content&view=article&id=48:tv-channel-5&catid=36&Itemid=55"><im…

    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 389, Column 615: reference to external entity in attribute value
    …php?option=com_content&view=article&id=48:tv-channel-5&catid=36&Itemid=55"><im…

    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 389, Column 615: reference to entity "id" for which no system identifier could be generated
    …php?option=com_content&view=article&id=48:tv-channel-5&catid=36&Itemid=55"><im…

    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 389, Column 612: entity was defined here
    …ex.php?option=com_content&view=article&id=48:tv-channel-5&catid=36&Itemid=55">…
  • Warning Line 389, Column 632: cannot generate system identifier for general entity "catid"
    …ntent&view=article&id=48:tv-channel-5&catid=36&Itemid=55"><img alt="Watch Pino…

    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 389, Column 632: general entity "catid" not defined and no default entity
    …ntent&view=article&id=48:tv-channel-5&catid=36&Itemid=55"><img alt="Watch Pino…

    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 389, Column 637: reference not terminated by REFC delimiter
    …&view=article&id=48:tv-channel-5&catid=36&Itemid=55"><img alt="Watch Pinoy TV …

    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 389, Column 637: reference to external entity in attribute value
    …&view=article&id=48:tv-channel-5&catid=36&Itemid=55"><img alt="Watch Pinoy TV …

    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 389, Column 637: reference to entity "catid" for which no system identifier could be generated
    …&view=article&id=48:tv-channel-5&catid=36&Itemid=55"><img alt="Watch Pinoy TV …

    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 389, Column 631: entity was defined here
    …ontent&view=article&id=48:tv-channel-5&catid=36&Itemid=55"><img alt="Watch Pin…
  • Warning Line 389, Column 641: cannot generate system identifier for general entity "Itemid"
    …w=article&id=48:tv-channel-5&catid=36&Itemid=55"><img alt="Watch Pinoy TV - TV…

    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 389, Column 641: general entity "Itemid" not defined and no default entity
    …w=article&id=48:tv-channel-5&catid=36&Itemid=55"><img alt="Watch Pinoy TV - TV…

    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 389, Column 647: reference not terminated by REFC delimiter
    …cle&id=48:tv-channel-5&catid=36&Itemid=55"><img alt="Watch Pinoy TV - TV5 Chan…

    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 389, Column 647: reference to external entity in attribute value
    …cle&id=48:tv-channel-5&catid=36&Itemid=55"><img alt="Watch Pinoy TV - TV5 Chan…

    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 389, Column 647: reference to entity "Itemid" for which no system identifier could be generated
    …cle&id=48:tv-channel-5&catid=36&Itemid=55"><img alt="Watch Pinoy TV - TV5 Chan…

    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 389, Column 640: entity was defined here
    …ew=article&id=48:tv-channel-5&catid=36&Itemid=55"><img alt="Watch Pinoy TV - T…
  • Error Line 390, Column 106: element "marquee" undefined
    …ld; font-size:14px;" bgcolor="#aa0000">&gt;&gt;&gt; LISTEN TO PINOY RADIO &lt;…

    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 395, Column 21: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=468 HEIGH…
  • Error Line 395, Column 35: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=468 HEIGH…
  • Error Line 395, Column 50: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …MEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=468 HEIGHT=60 SRC="…
  • Error Line 395, Column 62: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=468 HEIGHT=60 SRC="http://adser…
  • Error Line 395, Column 71: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …H=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=468 HEIGHT=60 SRC="http://adserving.cpxi…
  • Error Line 395, Column 82: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …EIGHT=0 SCROLLING=NO WIDTH=468 HEIGHT=60 SRC="http://adserving.cpxinteractive.…
  • Warning Line 395, Column 151: reference not terminated by REFC delimiter
    …eractive.com/st?ad_type=iframe&ad_size=468x60&section=3539354&pub_url=${PUB_UR…

    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 395, Column 151: reference to external entity in attribute value
    …eractive.com/st?ad_type=iframe&ad_size=468x60&section=3539354&pub_url=${PUB_UR…

    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 395, Column 151: reference to entity "ad_size" for which no system identifier could be generated
    …eractive.com/st?ad_type=iframe&ad_size=468x60&section=3539354&pub_url=${PUB_UR…

    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 372, Column 144: entity was defined here
    …g.cpxinteractive.com/st?ad_type=iframe&ad_size=300x250&section=3539354&pub_url…
  • Warning Line 395, Column 166: reference not terminated by REFC delimiter
    …/st?ad_type=iframe&ad_size=468x60&section=3539354&pub_url=${PUB_URL}"></IFRAME>

    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 395, Column 166: reference to external entity in attribute value
    …/st?ad_type=iframe&ad_size=468x60&section=3539354&pub_url=${PUB_URL}"></IFRAME>

    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 395, Column 166: reference to entity "section" for which no system identifier could be generated
    …/st?ad_type=iframe&ad_size=468x60&section=3539354&pub_url=${PUB_URL}"></IFRAME>

    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 372, Column 160: entity was defined here
    ….com/st?ad_type=iframe&ad_size=300x250&section=3539354&pub_url=${PUB_URL}"></I…
  • Warning Line 395, Column 182: reference not terminated by REFC delimiter
    …/st?ad_type=iframe&ad_size=468x60&section=3539354&pub_url=${PUB_URL}"></IFRAME>

    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 395, Column 182: reference to external entity in attribute value
    …/st?ad_type=iframe&ad_size=468x60&section=3539354&pub_url=${PUB_URL}"></IFRAME>

    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 395, Column 182: reference to entity "pub_url" for which no system identifier could be generated
    …/st?ad_type=iframe&ad_size=468x60&section=3539354&pub_url=${PUB_URL}"></IFRAME>

    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 372, Column 176: entity was defined here
    …st?ad_type=iframe&ad_size=300x250&section=3539354&pub_url=${PUB_URL}"></IFRAME>
  • Error Line 395, Column 194: element "IFRAME" undefined
    …/st?ad_type=iframe&ad_size=468x60&section=3539354&pub_url=${PUB_URL}"></IFRAME>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 399, Column 21: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=468 HEIGH…
  • Error Line 399, Column 35: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=468 HEIGH…
  • Error Line 399, Column 50: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …MEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=468 HEIGHT=60 SRC="…
  • Error Line 399, Column 62: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=468 HEIGHT=60 SRC="http://adser…
  • Error Line 399, Column 71: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …H=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=468 HEIGHT=60 SRC="http://adserving.cpxi…
  • Error Line 399, Column 82: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …EIGHT=0 SCROLLING=NO WIDTH=468 HEIGHT=60 SRC="http://adserving.cpxinteractive.…
  • Warning Line 399, Column 151: reference not terminated by REFC delimiter
    …eractive.com/st?ad_type=iframe&ad_size=468x60&section=3539354&pub_url=${PUB_UR…

    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 399, Column 151: reference to external entity in attribute value
    …eractive.com/st?ad_type=iframe&ad_size=468x60&section=3539354&pub_url=${PUB_UR…

    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 399, Column 151: reference to entity "ad_size" for which no system identifier could be generated
    …eractive.com/st?ad_type=iframe&ad_size=468x60&section=3539354&pub_url=${PUB_UR…

    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 372, Column 144: entity was defined here
    …g.cpxinteractive.com/st?ad_type=iframe&ad_size=300x250&section=3539354&pub_url…
  • Warning Line 399, Column 166: reference not terminated by REFC delimiter
    …/st?ad_type=iframe&ad_size=468x60&section=3539354&pub_url=${PUB_URL}"></IFRAME>

    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 399, Column 166: reference to external entity in attribute value
    …/st?ad_type=iframe&ad_size=468x60&section=3539354&pub_url=${PUB_URL}"></IFRAME>

    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 399, Column 166: reference to entity "section" for which no system identifier could be generated
    …/st?ad_type=iframe&ad_size=468x60&section=3539354&pub_url=${PUB_URL}"></IFRAME>

    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 372, Column 160: entity was defined here
    ….com/st?ad_type=iframe&ad_size=300x250&section=3539354&pub_url=${PUB_URL}"></I…
  • Warning Line 399, Column 182: reference not terminated by REFC delimiter
    …/st?ad_type=iframe&ad_size=468x60&section=3539354&pub_url=${PUB_URL}"></IFRAME>

    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 399, Column 182: reference to external entity in attribute value
    …/st?ad_type=iframe&ad_size=468x60&section=3539354&pub_url=${PUB_URL}"></IFRAME>

    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 399, Column 182: reference to entity "pub_url" for which no system identifier could be generated
    …/st?ad_type=iframe&ad_size=468x60&section=3539354&pub_url=${PUB_URL}"></IFRAME>

    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 372, Column 176: entity was defined here
    …st?ad_type=iframe&ad_size=300x250&section=3539354&pub_url=${PUB_URL}"></IFRAME>
  • Error Line 399, Column 194: element "IFRAME" undefined
    …/st?ad_type=iframe&ad_size=468x60&section=3539354&pub_url=${PUB_URL}"></IFRAME>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 421, Column 139: required attribute "alt" not specified
    …ck.us/img849/4074/balitangpinoy.jpg" /></a>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp…

    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 421, Column 295: required attribute "alt" not specified
    …hack.us/img94/6271/sportsbalita.jpg" /></a>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp…

    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 421, Column 453: required attribute "alt" not specified
    …src="http://img26.imageshack.us/img26/9827/showbizchikka.jpg" /></a></div></td>

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

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

  • Error Line 965, Column 66: ID "top" already defined
    										                            			<table width="100%" id="top">

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 367, Column 70: ID "top" first defined here
                                    	         			<table width="100%" id="top">
  • Error Line 1228, Column 9: "DOCTYPE" declaration not allowed in instance
    					<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://ww…
  • Error Line 1230, Column 43: document type does not allow element "html" here
    <html xmlns="http://www.w3.org/1999/xhtml">

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

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

  • Error Line 1259, Column 16: end tag for "head" which is not finished
    </script></head>

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

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

  • Error Line 1262, Column 107: element "marquee" undefined
    …9; font-weight:bold; font-size:14px;" >&gt;&gt;&gt; PUMILI NG TV SHOW &lt;&lt;…

    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 1263, Column 32: required attribute "action" not specified
      <form name="form1" id="form1">

    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 1265, Column 49: character "<" is the first character of a delimiter but occurred as data
    <option value="">--- >>> PUMILI NG TV SHOW DITO <<< ---</option>

    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 1265, Column 50: character "<" is the first character of a delimiter but occurred as data
    <option value="">--- >>> PUMILI NG TV SHOW DITO <<< ---</option>

    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 1265, Column 51: character "<" is the first character of a delimiter but occurred as data
    <option value="">--- >>> PUMILI NG TV SHOW DITO <<< ---</option>

    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 1404, Column 82: character "&" is the first character of a delimiter but occurred as data
    …tp://pinoy-ako.info/tv-show-replay/514-pare-a-pare.html">- Pare & Pare</option>

    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 1487, Column 80: character "&" is the first character of a delimiter but occurred as data
    …="http://pinoy-ako.info/tv-shows/235-moomoo-and-me.html">- Moomoo & Me</option>

    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 1520, Column 115: character "&" is the first character of a delimiter but occurred as data
    …ow-starring-vic-sotto.html">- The Jose & Wally Show Starring Vic Sotto</option>

    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 1552, Column 203: end tag for "img" omitted, but OMITTAG NO was specified
    …ck.us/img809/7782/pbalogobago.jpg"></a> <a title="Watch Sports and Other video…

    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 1552, Column 112: start tag was here
    …pba-live/watch-pba-live-video-1.html"><img alt="Watch PBA Live" src="http://im…
  • Warning Line 1552, Column 307: reference not terminated by REFC delimiter
    …info/index.php?option=com_content&view=category&id=191&Itemid=147"><img alt="W…

    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 1552, Column 307: reference to external entity in attribute value
    …info/index.php?option=com_content&view=category&id=191&Itemid=147"><img alt="W…

    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 1552, Column 307: reference to entity "view" for which no system identifier could be generated
    …info/index.php?option=com_content&view=category&id=191&Itemid=147"><img alt="W…

    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 389, Column 599: entity was defined here
    …-ako.info/index.php?option=com_content&view=article&id=48:tv-channel-5&catid=3…
  • Warning Line 1552, Column 319: reference not terminated by REFC delimiter
    …hp?option=com_content&view=category&id=191&Itemid=147"><img alt="Watch Sports …

    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 1552, Column 319: reference to external entity in attribute value
    …hp?option=com_content&view=category&id=191&Itemid=147"><img alt="Watch Sports …

    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 1552, Column 319: reference to entity "id" for which no system identifier could be generated
    …hp?option=com_content&view=category&id=191&Itemid=147"><img alt="Watch Sports …

    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 389, Column 612: entity was defined here
    …ex.php?option=com_content&view=article&id=48:tv-channel-5&catid=36&Itemid=55">…
  • Warning Line 1552, Column 330: reference not terminated by REFC delimiter
    …om_content&view=category&id=191&Itemid=147"><img alt="Watch Sports and Other v…

    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 1552, Column 330: reference to external entity in attribute value
    …om_content&view=category&id=191&Itemid=147"><img alt="Watch Sports and Other v…

    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 1552, Column 330: reference to entity "Itemid" for which no system identifier could be generated
    …om_content&view=category&id=191&Itemid=147"><img alt="Watch Sports and Other v…

    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 389, Column 640: entity was defined here
    …ew=article&id=48:tv-channel-5&catid=36&Itemid=55"><img alt="Watch Pinoy TV - T…
  • Error Line 1558, Column 8: required attribute "type" not specified
    <script>(function(d, s, id) {

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

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

  • Error Line 1565, Column 36: there is no attribute "data-href"
    <div class="fb-like-box" data-href="https://www.facebook.com/pages/wwwpinoy-ako…

    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 1565, Column 110: there is no attribute "data-width"
    …inoy-akoinfo/344344099936" data-width="300" data-show-faces="false" data-strea…

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

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

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

  • Error Line 1565, Column 132: there is no attribute "data-show-faces"
    …936" data-width="300" data-show-faces="false" data-stream="false" data-header=…

    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 1565, Column 152: there is no attribute "data-stream"
    …th="300" data-show-faces="false" data-stream="false" data-header="false"></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 1565, Column 172: there is no attribute "data-header"
    …th="300" data-show-faces="false" data-stream="false" data-header="false"></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.

  • Warning Line 1567, Column 77: cannot generate system identifier for general entity "cwrun"
    …m/TagPublish/getjs.aspx?action=VIEWAD&cwrun=200&cwadformat=120X600&cwpid=53517…

    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 1567, Column 77: general entity "cwrun" not defined and no default entity
    …m/TagPublish/getjs.aspx?action=VIEWAD&cwrun=200&cwadformat=120X600&cwpid=53517…

    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 1567, Column 82: reference not terminated by REFC delimiter
    …Publish/getjs.aspx?action=VIEWAD&cwrun=200&cwadformat=120X600&cwpid=535170&cww…

    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 1567, Column 82: reference to external entity in attribute value
    …Publish/getjs.aspx?action=VIEWAD&cwrun=200&cwadformat=120X600&cwpid=535170&cww…

    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 1567, Column 82: reference to entity "cwrun" for which no system identifier could be generated
    …Publish/getjs.aspx?action=VIEWAD&cwrun=200&cwadformat=120X600&cwpid=535170&cww…

    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 1567, Column 76: entity was defined here
    …om/TagPublish/getjs.aspx?action=VIEWAD&cwrun=200&cwadformat=120X600&cwpid=5351…
  • Warning Line 1567, Column 87: cannot generate system identifier for general entity "cwadformat"
    …sh/getjs.aspx?action=VIEWAD&cwrun=200&cwadformat=120X600&cwpid=535170&cwwidth=…

    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 1567, Column 87: general entity "cwadformat" not defined and no default entity
    …sh/getjs.aspx?action=VIEWAD&cwrun=200&cwadformat=120X600&cwpid=535170&cwwidth=…

    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 1567, Column 97: reference not terminated by REFC delimiter
    …spx?action=VIEWAD&cwrun=200&cwadformat=120X600&cwpid=535170&cwwidth=120&cwheig…

    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 1567, Column 97: reference to external entity in attribute value
    …spx?action=VIEWAD&cwrun=200&cwadformat=120X600&cwpid=535170&cwwidth=120&cwheig…

    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 1567, Column 97: reference to entity "cwadformat" for which no system identifier could be generated
    …spx?action=VIEWAD&cwrun=200&cwadformat=120X600&cwpid=535170&cwwidth=120&cwheig…

    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 1567, Column 86: entity was defined here
    …ish/getjs.aspx?action=VIEWAD&cwrun=200&cwadformat=120X600&cwpid=535170&cwwidth…
  • Warning Line 1567, Column 106: cannot generate system identifier for general entity "cwpid"
    …n=VIEWAD&cwrun=200&cwadformat=120X600&cwpid=535170&cwwidth=120&cwheight=600&cw…

    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 1567, Column 106: general entity "cwpid" not defined and no default entity
    …n=VIEWAD&cwrun=200&cwadformat=120X600&cwpid=535170&cwwidth=120&cwheight=600&cw…

    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 1567, Column 111: reference not terminated by REFC delimiter
    …WAD&cwrun=200&cwadformat=120X600&cwpid=535170&cwwidth=120&cwheight=600&cwpnet=…

    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 1567, Column 111: reference to external entity in attribute value
    …WAD&cwrun=200&cwadformat=120X600&cwpid=535170&cwwidth=120&cwheight=600&cwpnet=…

    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 1567, Column 111: reference to entity "cwpid" for which no system identifier could be generated
    …WAD&cwrun=200&cwadformat=120X600&cwpid=535170&cwwidth=120&cwheight=600&cwpnet=…

    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 1567, Column 105: entity was defined here
    …on=VIEWAD&cwrun=200&cwadformat=120X600&cwpid=535170&cwwidth=120&cwheight=600&c…
  • Warning Line 1567, Column 119: cannot generate system identifier for general entity "cwwidth"
    …n=200&cwadformat=120X600&cwpid=535170&cwwidth=120&cwheight=600&cwpnet=1&cwtagi…

    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 1567, Column 119: general entity "cwwidth" not defined and no default entity
    …n=200&cwadformat=120X600&cwpid=535170&cwwidth=120&cwheight=600&cwpnet=1&cwtagi…

    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 1567, Column 126: reference not terminated by REFC delimiter
    …wadformat=120X600&cwpid=535170&cwwidth=120&cwheight=600&cwpnet=1&cwtagid=11969…

    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 1567, Column 126: reference to external entity in attribute value
    …wadformat=120X600&cwpid=535170&cwwidth=120&cwheight=600&cwpnet=1&cwtagid=11969…

    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 1567, Column 126: reference to entity "cwwidth" for which no system identifier could be generated
    …wadformat=120X600&cwpid=535170&cwwidth=120&cwheight=600&cwpnet=1&cwtagid=11969…

    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 1567, Column 118: entity was defined here
    …un=200&cwadformat=120X600&cwpid=535170&cwwidth=120&cwheight=600&cwpnet=1&cwtag…
  • Warning Line 1567, Column 131: cannot generate system identifier for general entity "cwheight"
    …rmat=120X600&cwpid=535170&cwwidth=120&cwheight=600&cwpnet=1&cwtagid=119695"></…

    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 1567, Column 131: general entity "cwheight" not defined and no default entity
    …rmat=120X600&cwpid=535170&cwwidth=120&cwheight=600&cwpnet=1&cwtagid=119695"></…

    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 1567, Column 139: reference not terminated by REFC delimiter
    …20X600&cwpid=535170&cwwidth=120&cwheight=600&cwpnet=1&cwtagid=119695"></script>

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

  • Warning Line 1567, Column 139: reference to external entity in attribute value
    …20X600&cwpid=535170&cwwidth=120&cwheight=600&cwpnet=1&cwtagid=119695"></script>

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

  • Error Line 1567, Column 139: reference to entity "cwheight" for which no system identifier could be generated
    …20X600&cwpid=535170&cwwidth=120&cwheight=600&cwpnet=1&cwtagid=119695"></script>

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

  • Info Line 1567, Column 130: entity was defined here
    …ormat=120X600&cwpid=535170&cwwidth=120&cwheight=600&cwpnet=1&cwtagid=119695"><…
  • Warning Line 1567, Column 144: cannot generate system identifier for general entity "cwpnet"
    …20X600&cwpid=535170&cwwidth=120&cwheight=600&cwpnet=1&cwtagid=119695"></script>

    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 1567, Column 144: general entity "cwpnet" not defined and no default entity
    …20X600&cwpid=535170&cwwidth=120&cwheight=600&cwpnet=1&cwtagid=119695"></script>

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

  • Warning Line 1567, Column 150: reference not terminated by REFC delimiter
    …20X600&cwpid=535170&cwwidth=120&cwheight=600&cwpnet=1&cwtagid=119695"></script>

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

  • Warning Line 1567, Column 150: reference to external entity in attribute value
    …20X600&cwpid=535170&cwwidth=120&cwheight=600&cwpnet=1&cwtagid=119695"></script>

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

  • Error Line 1567, Column 150: reference to entity "cwpnet" for which no system identifier could be generated
    …20X600&cwpid=535170&cwwidth=120&cwheight=600&cwpnet=1&cwtagid=119695"></script>

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

  • Info Line 1567, Column 143: entity was defined here
    …20X600&cwpid=535170&cwwidth=120&cwheight=600&cwpnet=1&cwtagid=119695"></script>
  • Warning Line 1567, Column 153: cannot generate system identifier for general entity "cwtagid"
    …20X600&cwpid=535170&cwwidth=120&cwheight=600&cwpnet=1&cwtagid=119695"></script>

    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 1567, Column 153: general entity "cwtagid" not defined and no default entity
    …20X600&cwpid=535170&cwwidth=120&cwheight=600&cwpnet=1&cwtagid=119695"></script>

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

  • Warning Line 1567, Column 160: reference not terminated by REFC delimiter
    …20X600&cwpid=535170&cwwidth=120&cwheight=600&cwpnet=1&cwtagid=119695"></script>

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

  • Warning Line 1567, Column 160: reference to external entity in attribute value
    …20X600&cwpid=535170&cwwidth=120&cwheight=600&cwpnet=1&cwtagid=119695"></script>

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

  • Error Line 1567, Column 160: reference to entity "cwtagid" for which no system identifier could be generated
    …20X600&cwpid=535170&cwwidth=120&cwheight=600&cwpnet=1&cwtagid=119695"></script>

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

  • Info Line 1567, Column 152: entity was defined here
    …20X600&cwpid=535170&cwwidth=120&cwheight=600&cwpnet=1&cwtagid=119695"></script>
  • Error Line 1567, Column 168: required attribute "type" not specified
    …20X600&cwpid=535170&cwwidth=120&cwheight=600&cwpnet=1&cwtagid=119695"></script>

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

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

  • Error Line 1569, Column 21: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=160 HEIGH…
  • Error Line 1569, Column 35: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=160 HEIGH…
  • Error Line 1569, Column 50: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …MEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=160 HEIGHT=600 SRC=…
  • Error Line 1569, Column 62: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=160 HEIGHT=600 SRC="http://adse…
  • Error Line 1569, Column 71: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …H=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=160 HEIGHT=600 SRC="http://adserving.cpx…
  • Error Line 1569, Column 82: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …EIGHT=0 SCROLLING=NO WIDTH=160 HEIGHT=600 SRC="http://adserving.cpxinteractive…
  • Warning Line 1569, Column 152: reference not terminated by REFC delimiter
    …eractive.com/st?ad_type=iframe&ad_size=160x600&section=3539354&pub_url=${PUB_U…

    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 1569, Column 152: reference to external entity in attribute value
    …eractive.com/st?ad_type=iframe&ad_size=160x600&section=3539354&pub_url=${PUB_U…

    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 1569, Column 152: reference to entity "ad_size" for which no system identifier could be generated
    …eractive.com/st?ad_type=iframe&ad_size=160x600&section=3539354&pub_url=${PUB_U…

    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 372, Column 144: entity was defined here
    …g.cpxinteractive.com/st?ad_type=iframe&ad_size=300x250&section=3539354&pub_url…
  • Warning Line 1569, Column 168: reference not terminated by REFC delimiter
    …st?ad_type=iframe&ad_size=160x600&section=3539354&pub_url=${PUB_URL}"></IFRAME>

    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 1569, Column 168: reference to external entity in attribute value
    …st?ad_type=iframe&ad_size=160x600&section=3539354&pub_url=${PUB_URL}"></IFRAME>

    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 1569, Column 168: reference to entity "section" for which no system identifier could be generated
    …st?ad_type=iframe&ad_size=160x600&section=3539354&pub_url=${PUB_URL}"></IFRAME>

    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 372, Column 160: entity was defined here
    ….com/st?ad_type=iframe&ad_size=300x250&section=3539354&pub_url=${PUB_URL}"></I…
  • Warning Line 1569, Column 184: reference not terminated by REFC delimiter
    …st?ad_type=iframe&ad_size=160x600&section=3539354&pub_url=${PUB_URL}"></IFRAME>

    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 1569, Column 184: reference to external entity in attribute value
    …st?ad_type=iframe&ad_size=160x600&section=3539354&pub_url=${PUB_URL}"></IFRAME>

    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 1569, Column 184: reference to entity "pub_url" for which no system identifier could be generated
    …st?ad_type=iframe&ad_size=160x600&section=3539354&pub_url=${PUB_URL}"></IFRAME>

    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 372, Column 176: entity was defined here
    …st?ad_type=iframe&ad_size=300x250&section=3539354&pub_url=${PUB_URL}"></IFRAME>
  • Error Line 1569, Column 196: element "IFRAME" undefined
    …st?ad_type=iframe&ad_size=160x600&section=3539354&pub_url=${PUB_URL}"></IFRAME>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1572, Column 21: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=300 HEIGH…
  • Error Line 1572, Column 35: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=300 HEIGH…
  • Error Line 1572, Column 50: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …MEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=300 HEIGHT=250 SRC=…
  • Error Line 1572, Column 62: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=300 HEIGHT=250 SRC="http://adse…
  • Error Line 1572, Column 71: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …H=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=300 HEIGHT=250 SRC="http://adserving.cpx…
  • Error Line 1572, Column 82: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …EIGHT=0 SCROLLING=NO WIDTH=300 HEIGHT=250 SRC="http://adserving.cpxinteractive…
  • Warning Line 1572, Column 152: reference not terminated by REFC delimiter
    …eractive.com/st?ad_type=iframe&ad_size=300x250&section=3539354&pub_url=${PUB_U…

    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 1572, Column 152: reference to external entity in attribute value
    …eractive.com/st?ad_type=iframe&ad_size=300x250&section=3539354&pub_url=${PUB_U…

    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 1572, Column 152: reference to entity "ad_size" for which no system identifier could be generated
    …eractive.com/st?ad_type=iframe&ad_size=300x250&section=3539354&pub_url=${PUB_U…

    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 372, Column 144: entity was defined here
    …g.cpxinteractive.com/st?ad_type=iframe&ad_size=300x250&section=3539354&pub_url…
  • Warning Line 1572, Column 168: reference not terminated by REFC delimiter
    …st?ad_type=iframe&ad_size=300x250&section=3539354&pub_url=${PUB_URL}"></IFRAME>

    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 1572, Column 168: reference to external entity in attribute value
    …st?ad_type=iframe&ad_size=300x250&section=3539354&pub_url=${PUB_URL}"></IFRAME>

    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 1572, Column 168: reference to entity "section" for which no system identifier could be generated
    …st?ad_type=iframe&ad_size=300x250&section=3539354&pub_url=${PUB_URL}"></IFRAME>

    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 372, Column 160: entity was defined here
    ….com/st?ad_type=iframe&ad_size=300x250&section=3539354&pub_url=${PUB_URL}"></I…
  • Warning Line 1572, Column 184: reference not terminated by REFC delimiter
    …st?ad_type=iframe&ad_size=300x250&section=3539354&pub_url=${PUB_URL}"></IFRAME>

    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 1572, Column 184: reference to external entity in attribute value
    …st?ad_type=iframe&ad_size=300x250&section=3539354&pub_url=${PUB_URL}"></IFRAME>

    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 1572, Column 184: reference to entity "pub_url" for which no system identifier could be generated
    …st?ad_type=iframe&ad_size=300x250&section=3539354&pub_url=${PUB_URL}"></IFRAME>

    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 372, Column 176: entity was defined here
    …st?ad_type=iframe&ad_size=300x250&section=3539354&pub_url=${PUB_URL}"></IFRAME>
  • Error Line 1572, Column 196: element "IFRAME" undefined
    …st?ad_type=iframe&ad_size=300x250&section=3539354&pub_url=${PUB_URL}"></IFRAME>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1575, Column 7: invalid comment declaration: found name start character outside comment but inside comment declaration
    <!----Tlvmedia----www.pinoy-ako.info (143031)--banner--300x250---->
  • Info Line 1575, Column 1: comment declaration started here
    <!----Tlvmedia----www.pinoy-ako.info (143031)--banner--300x250---->
  • Warning Line 1576, Column 86: cannot generate system identifier for general entity "ad_type"
    …tlvmedia.com/tags.js?id=102847_143031&ad_type=banner&ad_size=300x250"></script…

    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 1576, Column 86: general entity "ad_type" not defined and no default entity
    …tlvmedia.com/tags.js?id=102847_143031&ad_type=banner&ad_size=300x250"></script…

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

  • Warning Line 1576, Column 93: reference not terminated by REFC delimiter
    …tlvmedia.com/tags.js?id=102847_143031&ad_type=banner&ad_size=300x250"></script>

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

  • Warning Line 1576, Column 93: reference to external entity in attribute value
    …tlvmedia.com/tags.js?id=102847_143031&ad_type=banner&ad_size=300x250"></script>

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

  • Error Line 1576, Column 93: reference to entity "ad_type" for which no system identifier could be generated
    …tlvmedia.com/tags.js?id=102847_143031&ad_type=banner&ad_size=300x250"></script>

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

  • Info Line 1576, Column 85: entity was defined here
    ….tlvmedia.com/tags.js?id=102847_143031&ad_type=banner&ad_size=300x250"></scrip…
  • Warning Line 1576, Column 108: reference not terminated by REFC delimiter
    …tlvmedia.com/tags.js?id=102847_143031&ad_type=banner&ad_size=300x250"></script>

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

  • Warning Line 1576, Column 108: reference to external entity in attribute value
    …tlvmedia.com/tags.js?id=102847_143031&ad_type=banner&ad_size=300x250"></script>

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

  • Error Line 1576, Column 108: reference to entity "ad_size" for which no system identifier could be generated
    …tlvmedia.com/tags.js?id=102847_143031&ad_type=banner&ad_size=300x250"></script>

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

  • Info Line 372, Column 144: entity was defined here
    …g.cpxinteractive.com/st?ad_type=iframe&ad_size=300x250&section=3539354&pub_url…
  • Error Line 1577, Column 7: invalid comment declaration: found name start character outside comment but inside comment declaration
    <!----Tlvmedia-------------------------------------------------->
  • Info Line 1577, Column 1: comment declaration started here
    <!----Tlvmedia-------------------------------------------------->
  • Error Line 1584, Column 230: required attribute "alt" not specified
    …feed-icon32x32.png" style="border:0" /></a><a href="http://feeds.feedburner.co…

    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 1585, Column 8: there is no attribute "alt"
    <a alt="Subscribe using any feed reader!" href="http://www.addthis.com/feed.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 1586, Column 205: end tag for "img" omitted, but OMITTAG NO was specified
    …riconj.png" width="35" height="35"></a> <a href="ymsgr:sendIM?apinoyako"><img …

    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 1586, Column 84: start tag was here
    …r" href="http://twitter.com/pin0yako"><img alt="Follow us on Twitter" src="htt…
  • Error Line 1586, Column 319: required attribute "alt" not specified
    …rc="http://opi.yahoo.com/online?u=apinoyako&amp;m=g&amp;t=2" border="0" /> </a>

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

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

  • Error Line 1588, Column 10: ID "fb-root" already defined
    <div id="fb-root"></div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 1557, Column 10: ID "fb-root" first defined here
    <div id="fb-root"></div>
  • Error Line 1589, Column 8: required attribute "type" not specified
    <script>(function(d, s, id) {

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

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

  • Error Line 1601, Column 21: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=300 HEIGH…
  • Error Line 1601, Column 35: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=300 HEIGH…
  • Error Line 1601, Column 50: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …MEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=300 HEIGHT=250 SRC=…
  • Error Line 1601, Column 62: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=300 HEIGHT=250 SRC="http://adse…
  • Error Line 1601, Column 71: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …H=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=300 HEIGHT=250 SRC="http://adserving.cpx…
  • Error Line 1601, Column 82: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …EIGHT=0 SCROLLING=NO WIDTH=300 HEIGHT=250 SRC="http://adserving.cpxinteractive…
  • Warning Line 1601, Column 152: reference not terminated by REFC delimiter
    …eractive.com/st?ad_type=iframe&ad_size=300x250&section=3539354&pub_url=${PUB_U…

    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 1601, Column 152: reference to external entity in attribute value
    …eractive.com/st?ad_type=iframe&ad_size=300x250&section=3539354&pub_url=${PUB_U…

    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 1601, Column 152: reference to entity "ad_size" for which no system identifier could be generated
    …eractive.com/st?ad_type=iframe&ad_size=300x250&section=3539354&pub_url=${PUB_U…

    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 372, Column 144: entity was defined here
    …g.cpxinteractive.com/st?ad_type=iframe&ad_size=300x250&section=3539354&pub_url…
  • Warning Line 1601, Column 168: reference not terminated by REFC delimiter
    …st?ad_type=iframe&ad_size=300x250&section=3539354&pub_url=${PUB_URL}"></IFRAME>

    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 1601, Column 168: reference to external entity in attribute value
    …st?ad_type=iframe&ad_size=300x250&section=3539354&pub_url=${PUB_URL}"></IFRAME>

    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 1601, Column 168: reference to entity "section" for which no system identifier could be generated
    …st?ad_type=iframe&ad_size=300x250&section=3539354&pub_url=${PUB_URL}"></IFRAME>

    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 372, Column 160: entity was defined here
    ….com/st?ad_type=iframe&ad_size=300x250&section=3539354&pub_url=${PUB_URL}"></I…
  • Warning Line 1601, Column 184: reference not terminated by REFC delimiter
    …st?ad_type=iframe&ad_size=300x250&section=3539354&pub_url=${PUB_URL}"></IFRAME>

    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 1601, Column 184: reference to external entity in attribute value
    …st?ad_type=iframe&ad_size=300x250&section=3539354&pub_url=${PUB_URL}"></IFRAME>

    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 1601, Column 184: reference to entity "pub_url" for which no system identifier could be generated
    …st?ad_type=iframe&ad_size=300x250&section=3539354&pub_url=${PUB_URL}"></IFRAME>

    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 372, Column 176: entity was defined here
    …st?ad_type=iframe&ad_size=300x250&section=3539354&pub_url=${PUB_URL}"></IFRAME>
  • Error Line 1601, Column 196: element "IFRAME" undefined
    …st?ad_type=iframe&ad_size=300x250&section=3539354&pub_url=${PUB_URL}"></IFRAME>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 1605, Column 1086: character "&" is the first character of a delimiter but occurred as data
    …alejo.html" title="Watch shake rattle & roll 12 - Pinoy Movies"><img alt="Watc…

    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 1605, Column 1141: character "&" is the first character of a delimiter but occurred as data
    … Movies"><img alt="Watch shake rattle & roll 12 - Pinoy Movies" src="http://im…

    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 1644, Column 14: there is no attribute "TYPE"
    <SCRIPT TYPE="text/javascript" SRC="http://ad.xtendmedia.com/st?ad_type=ad&ad_s…

    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 1644, Column 36: there is no attribute "SRC"
    <SCRIPT TYPE="text/javascript" SRC="http://ad.xtendmedia.com/st?ad_type=ad&ad_s…

    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 1644, Column 83: reference not terminated by REFC delimiter
    …tp://ad.xtendmedia.com/st?ad_type=ad&ad_size=300x250&section=2951831"></SCRIPT>

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

  • Warning Line 1644, Column 83: reference to external entity in attribute value
    …tp://ad.xtendmedia.com/st?ad_type=ad&ad_size=300x250&section=2951831"></SCRIPT>

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

  • Error Line 1644, Column 83: reference to entity "ad_size" for which no system identifier could be generated
    …tp://ad.xtendmedia.com/st?ad_type=ad&ad_size=300x250&section=2951831"></SCRIPT>

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

  • Info Line 372, Column 144: entity was defined here
    …g.cpxinteractive.com/st?ad_type=iframe&ad_size=300x250&section=3539354&pub_url…
  • Warning Line 1644, Column 99: reference not terminated by REFC delimiter
    …tp://ad.xtendmedia.com/st?ad_type=ad&ad_size=300x250&section=2951831"></SCRIPT>

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

  • Warning Line 1644, Column 99: reference to external entity in attribute value
    …tp://ad.xtendmedia.com/st?ad_type=ad&ad_size=300x250&section=2951831"></SCRIPT>

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

  • Error Line 1644, Column 99: reference to entity "section" for which no system identifier could be generated
    …tp://ad.xtendmedia.com/st?ad_type=ad&ad_size=300x250&section=2951831"></SCRIPT>

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

  • Info Line 372, Column 160: entity was defined here
    ….com/st?ad_type=iframe&ad_size=300x250&section=3539354&pub_url=${PUB_URL}"></I…
  • Error Line 1644, Column 108: element "SCRIPT" undefined
    …tp://ad.xtendmedia.com/st?ad_type=ad&ad_size=300x250&section=2951831"></SCRIPT>

    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 1684, Column 101: reference not terminated by REFC delimiter
    …info/index.php?option=com_content&view=category&id=191&Itemid=147" title="More…

    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 1684, Column 101: reference to external entity in attribute value
    …info/index.php?option=com_content&view=category&id=191&Itemid=147" title="More…

    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 1684, Column 101: reference to entity "view" for which no system identifier could be generated
    …info/index.php?option=com_content&view=category&id=191&Itemid=147" title="More…

    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 389, Column 599: entity was defined here
    …-ako.info/index.php?option=com_content&view=article&id=48:tv-channel-5&catid=3…
  • Warning Line 1684, Column 113: reference not terminated by REFC delimiter
    …hp?option=com_content&view=category&id=191&Itemid=147" title="More Sports and …

    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 1684, Column 113: reference to external entity in attribute value
    …hp?option=com_content&view=category&id=191&Itemid=147" title="More Sports and …

    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 1684, Column 113: reference to entity "id" for which no system identifier could be generated
    …hp?option=com_content&view=category&id=191&Itemid=147" title="More Sports and …

    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 389, Column 612: entity was defined here
    …ex.php?option=com_content&view=article&id=48:tv-channel-5&catid=36&Itemid=55">…
  • Warning Line 1684, Column 124: reference not terminated by REFC delimiter
    …om_content&view=category&id=191&Itemid=147" title="More Sports and Other Video…

    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 1684, Column 124: reference to external entity in attribute value
    …om_content&view=category&id=191&Itemid=147" title="More Sports and Other Video…

    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 1684, Column 124: reference to entity "Itemid" for which no system identifier could be generated
    …om_content&view=category&id=191&Itemid=147" title="More Sports and Other Video…

    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 389, Column 640: entity was defined here
    …ew=article&id=48:tv-channel-5&catid=36&Itemid=55"><img alt="Watch Pinoy TV - T…
  • Error Line 1684, Column 324: end tag for "img" omitted, but OMITTAG NO was specified
    …d Other Videos" style="margin: 0px 0px 4px; vertical-align: bottom;"></a><br />

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

  • Info Line 1684, Column 167: start tag was here
    … title="More Sports and Other Videos"><img src="http://img194.imageshack.us/im…
  • Error Line 1686, Column 21: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=300 HEIGH…
  • Error Line 1686, Column 35: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=300 HEIGH…
  • Error Line 1686, Column 50: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …MEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=300 HEIGHT=250 SRC=…
  • Error Line 1686, Column 62: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=300 HEIGHT=250 SRC="http://adse…
  • Error Line 1686, Column 71: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …H=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=300 HEIGHT=250 SRC="http://adserving.cpx…
  • Error Line 1686, Column 82: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …EIGHT=0 SCROLLING=NO WIDTH=300 HEIGHT=250 SRC="http://adserving.cpxinteractive…
  • Warning Line 1686, Column 152: reference not terminated by REFC delimiter
    …eractive.com/st?ad_type=iframe&ad_size=300x250&section=3539354&pub_url=${PUB_U…

    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 1686, Column 152: reference to external entity in attribute value
    …eractive.com/st?ad_type=iframe&ad_size=300x250&section=3539354&pub_url=${PUB_U…

    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 1686, Column 152: reference to entity "ad_size" for which no system identifier could be generated
    …eractive.com/st?ad_type=iframe&ad_size=300x250&section=3539354&pub_url=${PUB_U…

    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 372, Column 144: entity was defined here
    …g.cpxinteractive.com/st?ad_type=iframe&ad_size=300x250&section=3539354&pub_url…
  • Warning Line 1686, Column 168: reference not terminated by REFC delimiter
    …st?ad_type=iframe&ad_size=300x250&section=3539354&pub_url=${PUB_URL}"></IFRAME>

    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 1686, Column 168: reference to external entity in attribute value
    …st?ad_type=iframe&ad_size=300x250&section=3539354&pub_url=${PUB_URL}"></IFRAME>

    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 1686, Column 168: reference to entity "section" for which no system identifier could be generated
    …st?ad_type=iframe&ad_size=300x250&section=3539354&pub_url=${PUB_URL}"></IFRAME>

    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 372, Column 160: entity was defined here
    ….com/st?ad_type=iframe&ad_size=300x250&section=3539354&pub_url=${PUB_URL}"></I…
  • Warning Line 1686, Column 184: reference not terminated by REFC delimiter
    …st?ad_type=iframe&ad_size=300x250&section=3539354&pub_url=${PUB_URL}"></IFRAME>

    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 1686, Column 184: reference to external entity in attribute value
    …st?ad_type=iframe&ad_size=300x250&section=3539354&pub_url=${PUB_URL}"></IFRAME>

    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 1686, Column 184: reference to entity "pub_url" for which no system identifier could be generated
    …st?ad_type=iframe&ad_size=300x250&section=3539354&pub_url=${PUB_URL}"></IFRAME>

    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 372, Column 176: entity was defined here
    …st?ad_type=iframe&ad_size=300x250&section=3539354&pub_url=${PUB_URL}"></IFRAME>
  • Error Line 1686, Column 196: element "IFRAME" undefined
    …st?ad_type=iframe&ad_size=300x250&section=3539354&pub_url=${PUB_URL}"></IFRAME>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 1727, Column 81: reference not terminated by REFC delimiter
    …Publish/getjs.aspx?action=VIEWAD&cwrun=200&cwadformat=300X250&cwpid=535170&cww…

    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 1727, Column 81: reference to external entity in attribute value
    …Publish/getjs.aspx?action=VIEWAD&cwrun=200&cwadformat=300X250&cwpid=535170&cww…

    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 1727, Column 81: reference to entity "cwrun" for which no system identifier could be generated
    …Publish/getjs.aspx?action=VIEWAD&cwrun=200&cwadformat=300X250&cwpid=535170&cww…

    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 1567, Column 76: entity was defined here
    …om/TagPublish/getjs.aspx?action=VIEWAD&cwrun=200&cwadformat=120X600&cwpid=5351…
  • Warning Line 1727, Column 96: reference not terminated by REFC delimiter
    …spx?action=VIEWAD&cwrun=200&cwadformat=300X250&cwpid=535170&cwwidth=300&cwheig…

    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 1727, Column 96: reference to external entity in attribute value
    …spx?action=VIEWAD&cwrun=200&cwadformat=300X250&cwpid=535170&cwwidth=300&cwheig…

    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 1727, Column 96: reference to entity "cwadformat" for which no system identifier could be generated
    …spx?action=VIEWAD&cwrun=200&cwadformat=300X250&cwpid=535170&cwwidth=300&cwheig…

    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 1567, Column 86: entity was defined here
    …ish/getjs.aspx?action=VIEWAD&cwrun=200&cwadformat=120X600&cwpid=535170&cwwidth…
  • Warning Line 1727, Column 110: reference not terminated by REFC delimiter
    …WAD&cwrun=200&cwadformat=300X250&cwpid=535170&cwwidth=300&cwheight=250&cwpnet=…

    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 1727, Column 110: reference to external entity in attribute value
    …WAD&cwrun=200&cwadformat=300X250&cwpid=535170&cwwidth=300&cwheight=250&cwpnet=…

    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 1727, Column 110: reference to entity "cwpid" for which no system identifier could be generated
    …WAD&cwrun=200&cwadformat=300X250&cwpid=535170&cwwidth=300&cwheight=250&cwpnet=…

    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 1567, Column 105: entity was defined here
    …on=VIEWAD&cwrun=200&cwadformat=120X600&cwpid=535170&cwwidth=120&cwheight=600&c…
  • Warning Line 1727, Column 125: reference not terminated by REFC delimiter
    …wadformat=300X250&cwpid=535170&cwwidth=300&cwheight=250&cwpnet=1&cwtagid=11969…

    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 1727, Column 125: reference to external entity in attribute value
    …wadformat=300X250&cwpid=535170&cwwidth=300&cwheight=250&cwpnet=1&cwtagid=11969…

    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 1727, Column 125: reference to entity "cwwidth" for which no system identifier could be generated
    …wadformat=300X250&cwpid=535170&cwwidth=300&cwheight=250&cwpnet=1&cwtagid=11969…

    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 1567, Column 118: entity was defined here
    …un=200&cwadformat=120X600&cwpid=535170&cwwidth=120&cwheight=600&cwpnet=1&cwtag…
  • Warning Line 1727, Column 138: reference not terminated by REFC delimiter
    …X250&cwpid=535170&cwwidth=300&cwheight=250&cwpnet=1&cwtagid=119696"></script><…

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

  • Warning Line 1727, Column 138: reference to external entity in attribute value
    …X250&cwpid=535170&cwwidth=300&cwheight=250&cwpnet=1&cwtagid=119696"></script><…

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

  • Error Line 1727, Column 138: reference to entity "cwheight" for which no system identifier could be generated
    …X250&cwpid=535170&cwwidth=300&cwheight=250&cwpnet=1&cwtagid=119696"></script><…

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

  • Info Line 1567, Column 130: entity was defined here
    …ormat=120X600&cwpid=535170&cwwidth=120&cwheight=600&cwpnet=1&cwtagid=119695"><…
  • Warning Line 1727, Column 149: reference not terminated by REFC delimiter
    …&cwpid=535170&cwwidth=300&cwheight=250&cwpnet=1&cwtagid=119696"></script><br />

    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 1727, Column 149: reference to external entity in attribute value
    …&cwpid=535170&cwwidth=300&cwheight=250&cwpnet=1&cwtagid=119696"></script><br />

    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 1727, Column 149: reference to entity "cwpnet" for which no system identifier could be generated
    …&cwpid=535170&cwwidth=300&cwheight=250&cwpnet=1&cwtagid=119696"></script><br />

    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 1567, Column 143: entity was defined here
    …20X600&cwpid=535170&cwwidth=120&cwheight=600&cwpnet=1&cwtagid=119695"></script>
  • Warning Line 1727, Column 159: reference not terminated by REFC delimiter
    …&cwpid=535170&cwwidth=300&cwheight=250&cwpnet=1&cwtagid=119696"></script><br />

    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 1727, Column 159: reference to external entity in attribute value
    …&cwpid=535170&cwwidth=300&cwheight=250&cwpnet=1&cwtagid=119696"></script><br />

    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 1727, Column 159: reference to entity "cwtagid" for which no system identifier could be generated
    …&cwpid=535170&cwwidth=300&cwheight=250&cwpnet=1&cwtagid=119696"></script><br />

    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 1567, Column 152: entity was defined here
    …20X600&cwpid=535170&cwwidth=120&cwheight=600&cwpnet=1&cwtagid=119695"></script>
  • Error Line 1727, Column 167: required attribute "type" not specified
    …&cwpid=535170&cwwidth=300&cwheight=250&cwpnet=1&cwtagid=119696"></script><br />

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

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

  • Error Line 1739, Column 30: required attribute "type" not specified
    <script language="JavaScript">

    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 1742, Column 68: required attribute "type" not specified
    <script language="JavaScript" src="http://c4.zedo.com/jsc/c4/fo.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 1746, Column 84: reference not terminated by REFC delimiter
    ….xtendmedia.com/st?ad_type=pop&ad_size=0x0&section=2951830&banned_pop_types=28…

    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 1746, Column 84: reference to external entity in attribute value
    ….xtendmedia.com/st?ad_type=pop&ad_size=0x0&section=2951830&banned_pop_types=28…

    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 1746, Column 84: reference to entity "ad_size" for which no system identifier could be generated
    ….xtendmedia.com/st?ad_type=pop&ad_size=0x0&section=2951830&banned_pop_types=28…

    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 372, Column 144: entity was defined here
    …g.cpxinteractive.com/st?ad_type=iframe&ad_size=300x250&section=3539354&pub_url…
  • Warning Line 1746, Column 96: reference not terminated by REFC delimiter
    …com/st?ad_type=pop&ad_size=0x0&section=2951830&banned_pop_types=28&pop_times=3…

    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 1746, Column 96: reference to external entity in attribute value
    …com/st?ad_type=pop&ad_size=0x0&section=2951830&banned_pop_types=28&pop_times=3…

    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 1746, Column 96: reference to entity "section" for which no system identifier could be generated
    …com/st?ad_type=pop&ad_size=0x0&section=2951830&banned_pop_types=28&pop_times=3…

    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 372, Column 160: entity was defined here
    ….com/st?ad_type=iframe&ad_size=300x250&section=3539354&pub_url=${PUB_URL}"></I…
  • Warning Line 1746, Column 105: cannot generate system identifier for general entity "banned_pop_types"
    …_type=pop&ad_size=0x0&section=2951830&banned_pop_types=28&pop_times=3&pop_freq…

    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 1746, Column 105: general entity "banned_pop_types" not defined and no default entity
    …_type=pop&ad_size=0x0&section=2951830&banned_pop_types=28&pop_times=3&pop_freq…

    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 1746, Column 121: reference not terminated by REFC delimiter
    …e=0x0&section=2951830&banned_pop_types=28&pop_times=3&pop_frequency=86400&pub_…

    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 1746, Column 121: reference to external entity in attribute value
    …e=0x0&section=2951830&banned_pop_types=28&pop_times=3&pop_frequency=86400&pub_…

    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 1746, Column 121: reference to entity "banned_pop_types" for which no system identifier could be generated
    …e=0x0&section=2951830&banned_pop_types=28&pop_times=3&pop_frequency=86400&pub_…

    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 1746, Column 104: entity was defined here
    …d_type=pop&ad_size=0x0&section=2951830&banned_pop_types=28&pop_times=3&pop_fre…
  • Warning Line 1746, Column 125: cannot generate system identifier for general entity "pop_times"
    …0&section=2951830&banned_pop_types=28&pop_times=3&pop_frequency=86400&pub_url=…

    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 1746, Column 125: general entity "pop_times" not defined and no default entity
    …0&section=2951830&banned_pop_types=28&pop_times=3&pop_frequency=86400&pub_url=…

    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 1746, Column 134: reference not terminated by REFC delimiter
    …=2951830&banned_pop_types=28&pop_times=3&pop_frequency=86400&pub_url=${PUB_URL…

    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 1746, Column 134: reference to external entity in attribute value
    …=2951830&banned_pop_types=28&pop_times=3&pop_frequency=86400&pub_url=${PUB_URL…

    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 1746, Column 134: reference to entity "pop_times" for which no system identifier could be generated
    …=2951830&banned_pop_types=28&pop_times=3&pop_frequency=86400&pub_url=${PUB_URL…

    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 1746, Column 124: entity was defined here
    …x0&section=2951830&banned_pop_types=28&pop_times=3&pop_frequency=86400&pub_url…
  • Warning Line 1746, Column 137: cannot generate system identifier for general entity "pop_frequency"
    …51830&banned_pop_types=28&pop_times=3&pop_frequency=86400&pub_url=${PUB_URL}">…

    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 1746, Column 137: general entity "pop_frequency" not defined and no default entity
    …51830&banned_pop_types=28&pop_times=3&pop_frequency=86400&pub_url=${PUB_URL}">…

    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 1746, Column 150: reference not terminated by REFC delimiter
    …nned_pop_types=28&pop_times=3&pop_frequency=86400&pub_url=${PUB_URL}"></SCRIPT>

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

  • Warning Line 1746, Column 150: reference to external entity in attribute value
    …nned_pop_types=28&pop_times=3&pop_frequency=86400&pub_url=${PUB_URL}"></SCRIPT>

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

  • Error Line 1746, Column 150: reference to entity "pop_frequency" for which no system identifier could be generated
    …nned_pop_types=28&pop_times=3&pop_frequency=86400&pub_url=${PUB_URL}"></SCRIPT>

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

  • Info Line 1746, Column 136: entity was defined here
    …951830&banned_pop_types=28&pop_times=3&pop_frequency=86400&pub_url=${PUB_URL}"…
  • Warning Line 1746, Column 164: reference not terminated by REFC delimiter
    …nned_pop_types=28&pop_times=3&pop_frequency=86400&pub_url=${PUB_URL}"></SCRIPT>

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

  • Warning Line 1746, Column 164: reference to external entity in attribute value
    …nned_pop_types=28&pop_times=3&pop_frequency=86400&pub_url=${PUB_URL}"></SCRIPT>

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

  • Error Line 1746, Column 164: reference to entity "pub_url" for which no system identifier could be generated
    …nned_pop_types=28&pop_times=3&pop_frequency=86400&pub_url=${PUB_URL}"></SCRIPT>

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

  • Info Line 372, Column 176: entity was defined here
    …st?ad_type=iframe&ad_size=300x250&section=3539354&pub_url=${PUB_URL}"></IFRAME>
  • Error Line 1746, Column 176: element "SCRIPT" undefined
    …nned_pop_types=28&pop_times=3&pop_frequency=86400&pub_url=${PUB_URL}"></SCRIPT>

    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 1749, Column 95: reference not terminated by REFC delimiter
    …interactive.com/st?ad_type=pop&ad_size=0x0&section=3539354&banned_pop_types=29…

    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 1749, Column 95: reference to external entity in attribute value
    …interactive.com/st?ad_type=pop&ad_size=0x0&section=3539354&banned_pop_types=29…

    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 1749, Column 95: reference to entity "ad_size" for which no system identifier could be generated
    …interactive.com/st?ad_type=pop&ad_size=0x0&section=3539354&banned_pop_types=29…

    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 372, Column 144: entity was defined here
    …g.cpxinteractive.com/st?ad_type=iframe&ad_size=300x250&section=3539354&pub_url…
  • Warning Line 1749, Column 107: reference not terminated by REFC delimiter
    …com/st?ad_type=pop&ad_size=0x0&section=3539354&banned_pop_types=29&pop_times=1…

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

  • Warning Line 1749, Column 107: reference to external entity in attribute value
    …com/st?ad_type=pop&ad_size=0x0&section=3539354&banned_pop_types=29&pop_times=1…

    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 1749, Column 107: reference to entity "section" for which no system identifier could be generated
    …com/st?ad_type=pop&ad_size=0x0&section=3539354&banned_pop_types=29&pop_times=1…

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

  • Info Line 372, Column 160: entity was defined here
    ….com/st?ad_type=iframe&ad_size=300x250&section=3539354&pub_url=${PUB_URL}"></I…
  • Warning Line 1749, Column 132: reference not terminated by REFC delimiter
    …e=0x0&section=3539354&banned_pop_types=29&pop_times=1&pop_frequency=86400&pub_…

    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 1749, Column 132: reference to external entity in attribute value
    …e=0x0&section=3539354&banned_pop_types=29&pop_times=1&pop_frequency=86400&pub_…

    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 1749, Column 132: reference to entity "banned_pop_types" for which no system identifier could be generated
    …e=0x0&section=3539354&banned_pop_types=29&pop_times=1&pop_frequency=86400&pub_…

    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 1746, Column 104: entity was defined here
    …d_type=pop&ad_size=0x0&section=2951830&banned_pop_types=28&pop_times=3&pop_fre…
  • Warning Line 1749, Column 145: reference not terminated by REFC delimiter
    …=3539354&banned_pop_types=29&pop_times=1&pop_frequency=86400&pub_url=${PUB_URL…

    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 1749, Column 145: reference to external entity in attribute value
    …=3539354&banned_pop_types=29&pop_times=1&pop_frequency=86400&pub_url=${PUB_URL…

    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 1749, Column 145: reference to entity "pop_times" for which no system identifier could be generated
    …=3539354&banned_pop_types=29&pop_times=1&pop_frequency=86400&pub_url=${PUB_URL…

    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 1746, Column 124: entity was defined here
    …x0&section=2951830&banned_pop_types=28&pop_times=3&pop_frequency=86400&pub_url…
  • Warning Line 1749, Column 161: reference not terminated by REFC delimiter
    …nned_pop_types=29&pop_times=1&pop_frequency=86400&pub_url=${PUB_URL}"></SCRIPT>

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

  • Warning Line 1749, Column 161: reference to external entity in attribute value
    …nned_pop_types=29&pop_times=1&pop_frequency=86400&pub_url=${PUB_URL}"></SCRIPT>

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

  • Error Line 1749, Column 161: reference to entity "pop_frequency" for which no system identifier could be generated
    …nned_pop_types=29&pop_times=1&pop_frequency=86400&pub_url=${PUB_URL}"></SCRIPT>

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

  • Info Line 1746, Column 136: entity was defined here
    …951830&banned_pop_types=28&pop_times=3&pop_frequency=86400&pub_url=${PUB_URL}"…
  • Warning Line 1749, Column 175: reference not terminated by REFC delimiter
    …nned_pop_types=29&pop_times=1&pop_frequency=86400&pub_url=${PUB_URL}"></SCRIPT>

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

  • Warning Line 1749, Column 175: reference to external entity in attribute value
    …nned_pop_types=29&pop_times=1&pop_frequency=86400&pub_url=${PUB_URL}"></SCRIPT>

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

  • Error Line 1749, Column 175: reference to entity "pub_url" for which no system identifier could be generated
    …nned_pop_types=29&pop_times=1&pop_frequency=86400&pub_url=${PUB_URL}"></SCRIPT>

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

  • Info Line 372, Column 176: entity was defined here
    …st?ad_type=iframe&ad_size=300x250&section=3539354&pub_url=${PUB_URL}"></IFRAME>
  • Error Line 1749, Column 187: element "SCRIPT" undefined
    …nned_pop_types=29&pop_times=1&pop_frequency=86400&pub_url=${PUB_URL}"></SCRIPT>

    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 1754, Column 30: required attribute "type" not specified
    <script language="JavaScript">

    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 1757, Column 68: required attribute "type" not specified
    <script language="JavaScript" src="http://c4.zedo.com/jsc/c4/fo.js"></script>

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

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

  • Error Line 1779, Column 6: end tag for element "div" which is not open
    </div>

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

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

Visitor Analysis

Daily Visitor
  • 39.667 visits

In Page Analysis