eenadu.net

EENADU Online Edition ...

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

Overview Info

  • Domain Name
    eenadu.net
  • Favicon
  • Alexa Rank
    #1378
  • Google Page Rank
    PR 6
  • Ip Address
    8.25.218.11
  • Page Size
    166.2 KB
  • Images
    43 GIF, 49 JPG, 16 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    2 13 1 0 2 0

Website Meta Analysis



  • Title
    EENADU Online Edition - Telugu news paper
  • Meta Keyword
    Eenadu, Eenadu Archives, Eenadu e Paper,breaking news,weather forecasting,telugu news paper,andhrapradesh news, ap news,political news,telugu cinema,telugu actors,movie actors,latest movies,online magazines,online jobs,health tips online,cricket, ipl t20,sachin tendulkar,mumbai indians,chennai super kings,business news,food recipes,share market,spot fixing
  • Meta Description
    EENADU Online Edition

Technical Analysis



  • Webserver
    Microsoft-IIS/7.5
  • Ip Address
    8.25.218.11
  • Domain Age
    16 Years, 7 Months, 10 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from eenadu.net.

HTML Analysis

  • cache-control: private
  • content-type: text/html; charset=utf-8
  • content-encoding: gzip
  • vary: Accept-Encoding
  • server: Microsoft-IIS/7.5
  • x-aspnet-version: 2.0.50727
  • x-powered-by: ASP.NET
  • date: Tue, 17 Sep 2013 17:44:38 GMT
  • content-length: 49044
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Registrant:
Ushodaya Enterprises Limited
Eenadu Complex, Somajiguda
Hyderabad, Andhra Pradesh 500082
IN
Domain Domain Name: EENADU.NET
-

-
Administrative Contact:
Cherukuri, email
Margardarsi Chit Fund Ltd.,
Margadarsi House, 5-10-195, Fatehmaidan
Road Hyderabad, Andhra Pradesh 500004
IN
91-40-3212678 fax: 91-40-3212678
Technical Contact:
Sankarlingam, email
689 LEGENDS DR
CAROL STREAM, IL 60188-3400
US
408/732-7180 fax: 408/732-8910

Expires: 04-Feb-2014.
Created: 03-Feb-1997.
Database Updated: 30-Jan-2012 10:50:30 EST.
Name Servers:
NS1.WEBINDIA.COM 216.129.98.241
NS2.WEBINDIA.COM 216.129.98.181

DNS Analysis


DNS servers
ns1.webindia.com [216.129.98.241]
ns2.webindia.com [216.129.98.181]

DNS Records

Answer records
eenadu.net SOA
server: ns1.webindia.com
email: www@webindia.com
serial: 2012120602
refresh: 10800
retry: 3600
expire: 604800
minimum ttl: 60
60s
eenadu.net NS  ns2.webindia.com 60s
eenadu.net NS  ns1.webindia.com 60s
eenadu.net A 8.25.218.11 60s
eenadu.net MX
preference: 10
exchange: spamtitan.webindia.com
60s
eenadu.net TXT v=spf1 ip4:216.129.98.206 ~all 60s

Authority records

Additional records
ns1.webindia.com A 216.129.98.241 1800s
ns2.webindia.com A 216.129.98.181 1800s
spamtitan.webindia.com A 216.129.98.200 1800s

IP 8.25.218.11 Analysis

  • Country Code
    US
  • Country Code3
    USA
  • Country Name
    United States
  • City
    NA
  • Continent Code
    38° North
  • Latitude
    97.
  • Longitude
  • #
    # Query terms are ambiguous. The query is assumed to be:
    # "n 8.25.218.11"
    #
    # Use "?" to get help.
    #

    #
    # The following results may also be obtained via:
    # http://whois.arin.net/rest/nets;q=8.25.218.11?showDetails=true&showARIN=false&ext=netref2
    #

    NetRange: 8.0.0.0 - 8.255.255.255
    CIDR: 8.0.0.0/8
    OriginAS:
    NetName: LVLT-ORG-8-8
    NetHandle: NET-8-0-0-0-1
    Parent:
    NetType: Direct Allocation
    RegDate: 1992-12-01
    Updated: 2012-02-24
    Ref: http://whois.arin.net/rest/net/NET-8-0-0-0-1

    OrgName: Level 3 Communications, Inc.
    OrgId: LVLT
    Address: 1025 Eldorado Blvd.
    City: Broomfield
    StateProv: CO
    PostalCode: 80021
    Country: US
    RegDate: 1998-05-22
    Updated: 2012-01-30
    Comment: ADDRESSES WITHIN THIS BLOCK ARE NON-PORTABLE
    Ref: http://whois.arin.net/rest/org/LVLT

    OrgNOCHandle: NOCSU27-ARIN
    OrgNOCName: NOC Support
    OrgNOCPhone: +1-877-453-8353
    OrgNOCEmail: noc.coreip@level3.com
    OrgNOCRef: http://whois.arin.net/rest/poc/NOCSU27-ARIN

    OrgTechHandle: IPADD5-ARIN
    OrgTechName: ipaddressing
    OrgTechPhone: +1-877-453-8353
    OrgTechEmail: ipaddressing@level3.com
    OrgTechRef: http://whois.arin.net/rest/poc/IPADD5-ARIN

    OrgAbuseHandle: APL8-ARIN
    OrgAbuseName: Abuse POC LVLT
    OrgAbusePhone: +1-877-453-8353
    OrgAbuseEmail: security@level3.com
    OrgAbuseRef: http://whois.arin.net/rest/poc/APL8-ARIN

    #
    # ARIN WHOIS data and services are subject to the Terms of Use
    # available at: https://www.arin.net/whois_tou.html
    #

Site Same Ip

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 334 Errors
  • 167 Warnings
Ratio Text/Html
  • 0.3654983988953847
Message Error
  • Warning Line 70, Column 52: character "<" is the first character of a delimiter but occurred as data
                        } else if ($(this).scrollTop() <= 134) {

    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 76, Column 44: character "<" is the first character of a delimiter but occurred as data
                    else if ($(window).width() < 1000) {

    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 113, Column 27: character "<" is the first character of a delimiter but occurred as data
                if (ffversion < 5)

    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 114, Column 45: an attribute value must be a literal unless it contains only name characters
    …          document.write("<span style=\"text-decoration: underline overline; f…

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

  • Error Line 114, Column 74: "underline" is not a member of a group specified for any attribute
    …an style=\"text-decoration: underline overline; font-size: x-large; color: #FF…
  • Error Line 114, Column 82: "overline" is not a member of a group specified for any attribute
    …=\"text-decoration: underline overline; font-size: x-large; color: #FF0000; te…
  • Error Line 114, Column 95: "font-size:" is not a member of a group specified for any attribute
    …ation: underline overline; font-size: x-large; color: #FF0000; text-transform:…
  • Error Line 114, Column 102: "x-large" is not a member of a group specified for any attribute
    …underline overline; font-size: x-large; color: #FF0000; text-transform: upperc…
  • Error Line 114, Column 111: "color:" is not a member of a group specified for any attribute
    … overline; font-size: x-large; color: #FF0000; text-transform: uppercase\"><ce…
  • Error Line 114, Column 136: "text-transform:" is not a member of a group specified for any attribute
    …arge; color: #FF0000; text-transform: uppercase\"><center>You're using older v…
  • Error Line 114, Column 145: "uppercase" is not a member of a group specified for any attribute
    …or: #FF0000; text-transform: uppercase\"><center>You're using older version of…
  • Error Line 114, Column 147: document type does not allow element "span" here
    …: #FF0000; text-transform: uppercase\"><center>You're using older version of F…

    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 114, Column 155: document type does not allow element "center" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …0; text-transform: uppercase\"><center>You're using older version of Firefox, …

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

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

  • Error Line 114, Column 225: an attribute value must be a literal unless it contains only name characters
    …irefox, For new version click <a href=\"http://www.mozilla.org/en-US/firefox/f…

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

  • Error Line 114, Column 283: an attribute value must be a literal unless it contains only name characters
    …illa.org/en-US/firefox/features/\" target=\"_blank\">HERE</a></center></span>")

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

  • Error Line 114, Column 283: character "\" is not allowed in the value of attribute "target"
    …illa.org/en-US/firefox/features/\" target=\"_blank\">HERE</a></center></span>")

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Warning Line 118, Column 27: character "<" is the first character of a delimiter but occurred as data
                if (ieversion < 8)

    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 119, Column 45: an attribute value must be a literal unless it contains only name characters
    …          document.write("<span style=\"text-decoration: underline overline; f…

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

  • Error Line 119, Column 74: "underline" is not a member of a group specified for any attribute
    …an style=\"text-decoration: underline overline; font-size: x-large; color: #FF…
  • Error Line 119, Column 82: "overline" is not a member of a group specified for any attribute
    …=\"text-decoration: underline overline; font-size: x-large; color: #FF0000; te…
  • Error Line 119, Column 95: "font-size:" is not a member of a group specified for any attribute
    …ation: underline overline; font-size: x-large; color: #FF0000; text-transform:…
  • Error Line 119, Column 102: "x-large" is not a member of a group specified for any attribute
    …underline overline; font-size: x-large; color: #FF0000; text-transform: upperc…
  • Error Line 119, Column 111: "color:" is not a member of a group specified for any attribute
    … overline; font-size: x-large; color: #FF0000; text-transform: uppercase\"><ce…
  • Error Line 119, Column 136: "text-transform:" is not a member of a group specified for any attribute
    …arge; color: #FF0000; text-transform: uppercase\"><center>You're using older v…
  • Error Line 119, Column 145: "uppercase" is not a member of a group specified for any attribute
    …or: #FF0000; text-transform: uppercase\"><center>You're using older version of…
  • Error Line 119, Column 147: document type does not allow element "span" here
    …: #FF0000; text-transform: uppercase\"><center>You're using older version of I…

    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 119, Column 155: document type does not allow element "center" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …0; text-transform: uppercase\"><center>You're using older version of Internet …

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

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

  • Error Line 119, Column 229: an attribute value must be a literal unless it contains only name characters
    …net Explorer, For new version <a href=\"http://windows.microsoft.com/en-US/int…

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

  • Error Line 119, Column 306: an attribute value must be a literal unless it contains only name characters
    …ternet-explorer/downloads/ie\" target=\"_blank\">CLICK HERE</a></center></span…

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

  • Error Line 119, Column 306: character "\" is not allowed in the value of attribute "target"
    …ternet-explorer/downloads/ie\" target=\"_blank\">CLICK HERE</a></center></span…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 134, Column 72: required attribute "type" not specified
        <script language="JavaScript" src="http://d8.zedo.com/jsc/d8/fo.js">

    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 140, Column 72: cannot generate system identifier for general entity "zoneid"
    …' src='http://n.admagnet.net/d/po/?n=&zoneid=6445&target=_blank&cb=INSERT_RAND…

    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 140, Column 72: general entity "zoneid" not defined and no default entity
    …' src='http://n.admagnet.net/d/po/?n=&zoneid=6445&target=_blank&cb=INSERT_RAND…

    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 140, Column 78: reference not terminated by REFC delimiter
    …'http://n.admagnet.net/d/po/?n=&zoneid=6445&target=_blank&cb=INSERT_RANDOM_NUM…

    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 140, Column 78: reference to external entity in attribute value
    …'http://n.admagnet.net/d/po/?n=&zoneid=6445&target=_blank&cb=INSERT_RANDOM_NUM…

    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 140, Column 78: reference to entity "zoneid" for which no system identifier could be generated
    …'http://n.admagnet.net/d/po/?n=&zoneid=6445&target=_blank&cb=INSERT_RANDOM_NUM…

    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 140, Column 71: entity was defined here
    …t' src='http://n.admagnet.net/d/po/?n=&zoneid=6445&target=_blank&cb=INSERT_RAN…
  • Warning Line 140, Column 84: cannot generate system identifier for general entity "target"
    …//n.admagnet.net/d/po/?n=&zoneid=6445&target=_blank&cb=INSERT_RANDOM_NUMBER_HE…

    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 140, Column 84: general entity "target" not defined and no default entity
    …//n.admagnet.net/d/po/?n=&zoneid=6445&target=_blank&cb=INSERT_RANDOM_NUMBER_HE…

    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 140, Column 90: reference not terminated by REFC delimiter
    …magnet.net/d/po/?n=&zoneid=6445&target=_blank&cb=INSERT_RANDOM_NUMBER_HERE&pop…

    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 140, Column 90: reference to external entity in attribute value
    …magnet.net/d/po/?n=&zoneid=6445&target=_blank&cb=INSERT_RANDOM_NUMBER_HERE&pop…

    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 140, Column 90: reference to entity "target" for which no system identifier could be generated
    …magnet.net/d/po/?n=&zoneid=6445&target=_blank&cb=INSERT_RANDOM_NUMBER_HERE&pop…

    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 140, Column 83: entity was defined here
    …://n.admagnet.net/d/po/?n=&zoneid=6445&target=_blank&cb=INSERT_RANDOM_NUMBER_H…
  • Warning Line 140, Column 98: cannot generate system identifier for general entity "cb"
    …et/d/po/?n=&zoneid=6445&target=_blank&cb=INSERT_RANDOM_NUMBER_HERE&popunder=1&…

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

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

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

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

  • Error Line 140, Column 98: general entity "cb" not defined and no default entity
    …et/d/po/?n=&zoneid=6445&target=_blank&cb=INSERT_RANDOM_NUMBER_HERE&popunder=1&…

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

  • Warning Line 140, Column 100: reference not terminated by REFC delimiter
    …/d/po/?n=&zoneid=6445&target=_blank&cb=INSERT_RANDOM_NUMBER_HERE&popunder=1&le…

    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 140, Column 100: reference to external entity in attribute value
    …/d/po/?n=&zoneid=6445&target=_blank&cb=INSERT_RANDOM_NUMBER_HERE&popunder=1&le…

    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 140, Column 100: reference to entity "cb" for which no system identifier could be generated
    …/d/po/?n=&zoneid=6445&target=_blank&cb=INSERT_RANDOM_NUMBER_HERE&popunder=1&le…

    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 140, Column 97: entity was defined here
    …net/d/po/?n=&zoneid=6445&target=_blank&cb=INSERT_RANDOM_NUMBER_HERE&popunder=1…
  • Warning Line 140, Column 127: cannot generate system identifier for general entity "popunder"
    …t=_blank&cb=INSERT_RANDOM_NUMBER_HERE&popunder=1&left=200&top=200&z=MzIzPQ%3D%…

    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 140, Column 127: general entity "popunder" not defined and no default entity
    …t=_blank&cb=INSERT_RANDOM_NUMBER_HERE&popunder=1&left=200&top=200&z=MzIzPQ%3D%…

    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 140, Column 135: reference not terminated by REFC delimiter
    …&cb=INSERT_RANDOM_NUMBER_HERE&popunder=1&left=200&top=200&z=MzIzPQ%3D%3D'></sc…

    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 140, Column 135: reference to external entity in attribute value
    …&cb=INSERT_RANDOM_NUMBER_HERE&popunder=1&left=200&top=200&z=MzIzPQ%3D%3D'></sc…

    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 140, Column 135: reference to entity "popunder" for which no system identifier could be generated
    …&cb=INSERT_RANDOM_NUMBER_HERE&popunder=1&left=200&top=200&z=MzIzPQ%3D%3D'></sc…

    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 140, Column 126: entity was defined here
    …et=_blank&cb=INSERT_RANDOM_NUMBER_HERE&popunder=1&left=200&top=200&z=MzIzPQ%3D…
  • Warning Line 140, Column 138: cannot generate system identifier for general entity "left"
    …=INSERT_RANDOM_NUMBER_HERE&popunder=1&left=200&top=200&z=MzIzPQ%3D%3D'></scrip…

    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 140, Column 138: general entity "left" not defined and no default entity
    …=INSERT_RANDOM_NUMBER_HERE&popunder=1&left=200&top=200&z=MzIzPQ%3D%3D'></scrip…

    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 140, Column 142: reference not terminated by REFC delimiter
    …INSERT_RANDOM_NUMBER_HERE&popunder=1&left=200&top=200&z=MzIzPQ%3D%3D'></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 140, Column 142: reference to external entity in attribute value
    …INSERT_RANDOM_NUMBER_HERE&popunder=1&left=200&top=200&z=MzIzPQ%3D%3D'></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 140, Column 142: reference to entity "left" for which no system identifier could be generated
    …INSERT_RANDOM_NUMBER_HERE&popunder=1&left=200&top=200&z=MzIzPQ%3D%3D'></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 140, Column 137: entity was defined here
    …b=INSERT_RANDOM_NUMBER_HERE&popunder=1&left=200&top=200&z=MzIzPQ%3D%3D'></scri…
  • Warning Line 140, Column 147: cannot generate system identifier for general entity "top"
    …INSERT_RANDOM_NUMBER_HERE&popunder=1&left=200&top=200&z=MzIzPQ%3D%3D'></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 140, Column 147: general entity "top" not defined and no default entity
    …INSERT_RANDOM_NUMBER_HERE&popunder=1&left=200&top=200&z=MzIzPQ%3D%3D'></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 140, Column 150: reference not terminated by REFC delimiter
    …INSERT_RANDOM_NUMBER_HERE&popunder=1&left=200&top=200&z=MzIzPQ%3D%3D'></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 140, Column 150: reference to external entity in attribute value
    …INSERT_RANDOM_NUMBER_HERE&popunder=1&left=200&top=200&z=MzIzPQ%3D%3D'></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 140, Column 150: reference to entity "top" for which no system identifier could be generated
    …INSERT_RANDOM_NUMBER_HERE&popunder=1&left=200&top=200&z=MzIzPQ%3D%3D'></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 140, Column 146: entity was defined here
    …INSERT_RANDOM_NUMBER_HERE&popunder=1&left=200&top=200&z=MzIzPQ%3D%3D'></script>
  • Warning Line 140, Column 155: cannot generate system identifier for general entity "z"
    …INSERT_RANDOM_NUMBER_HERE&popunder=1&left=200&top=200&z=MzIzPQ%3D%3D'></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 140, Column 155: general entity "z" not defined and no default entity
    …INSERT_RANDOM_NUMBER_HERE&popunder=1&left=200&top=200&z=MzIzPQ%3D%3D'></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 140, Column 156: reference not terminated by REFC delimiter
    …INSERT_RANDOM_NUMBER_HERE&popunder=1&left=200&top=200&z=MzIzPQ%3D%3D'></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 140, Column 156: reference to external entity in attribute value
    …INSERT_RANDOM_NUMBER_HERE&popunder=1&left=200&top=200&z=MzIzPQ%3D%3D'></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 140, Column 156: reference to entity "z" for which no system identifier could be generated
    …INSERT_RANDOM_NUMBER_HERE&popunder=1&left=200&top=200&z=MzIzPQ%3D%3D'></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 140, Column 154: entity was defined here
    …INSERT_RANDOM_NUMBER_HERE&popunder=1&left=200&top=200&z=MzIzPQ%3D%3D'></script>
  • Warning Line 193, Column 85: cannot generate system identifier for general entity "sid"
    …cks.com/clicks.php?url=http://www.RitePros.com&sid=Eenadu.net" target="_blank">

    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 193, Column 85: general entity "sid" not defined and no default entity
    …cks.com/clicks.php?url=http://www.RitePros.com&sid=Eenadu.net" target="_blank">

    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 193, Column 88: reference not terminated by REFC delimiter
    …cks.com/clicks.php?url=http://www.RitePros.com&sid=Eenadu.net" target="_blank">

    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 193, Column 88: reference to external entity in attribute value
    …cks.com/clicks.php?url=http://www.RitePros.com&sid=Eenadu.net" target="_blank">

    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 193, Column 88: reference to entity "sid" for which no system identifier could be generated
    …cks.com/clicks.php?url=http://www.RitePros.com&sid=Eenadu.net" target="_blank">

    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 193, Column 84: entity was defined here
    …cks.com/clicks.php?url=http://www.RitePros.com&sid=Eenadu.net" target="_blank">
  • Error Line 194, Column 63: required attribute "alt" not specified
        <img border="0" src="adimages/Ritepros_Ee_Blue_250x90.gif"></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 194, Column 67: end tag for "img" omitted, but OMITTAG NO was specified
        <img border="0" src="adimages/Ritepros_Ee_Blue_250x90.gif"></a> 

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

  • Info Line 194, Column 5: start tag was here
        <img border="0" src="adimages/Ritepros_Ee_Blue_250x90.gif"></a> 
  • Error Line 197, Column 49: there is no attribute "onClick"
    … href="http://www.eenadu.net" onClick="_gaq.push(['_trackEvent', 'ExternalLink…

    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 198, Column 81: required attribute "alt" not specified
    …<img src="siteimages/logo.gif" width="315" height="100" border="0" /></a></div>

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

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

  • Error Line 200, Column 155: required attribute "alt" not specified
    …"><img src="adimages/HCL 250x90.gif"  width="250" height="90" 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 226, Column 21: ID "dropdown" already defined
                <li id="dropdown"><a href="#" class="edit"></a>

    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 208, Column 17: ID "dropdown" first defined here
            <ul id="dropdown">
  • Error Line 316, Column 67: required attribute "alt" not specified
                <img src="adimages/tdp-vasthunna200-50.gif" border="0"></a></li>

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

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

  • Error Line 316, Column 71: end tag for "img" omitted, but OMITTAG NO was specified
                <img src="adimages/tdp-vasthunna200-50.gif" border="0"></a></li>

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

  • Info Line 316, Column 13: start tag was here
                <img src="adimages/tdp-vasthunna200-50.gif" border="0"></a></li>
  • Error Line 326, Column 106: required attribute "alt" not specified
    …img src="images/slidepic1.jpg" width="197" height="240" border="0" /></a></div>

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

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

  • Error Line 329, Column 106: required attribute "alt" not specified
    …img src="images/slidepic2.jpg" width="197" height="240" border="0" /></a></div>

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

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

  • Error Line 332, Column 106: required attribute "alt" not specified
    …img src="images/slidepic3.jpg" width="197" height="240" border="0" /></a></div>

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

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

  • Error Line 335, Column 106: required attribute "alt" not specified
    …img src="images/slidepic4.jpg" width="197" height="240" border="0" /></a></div>

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

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

  • Error Line 338, Column 106: required attribute "alt" not specified
    …img src="images/slidepic5.jpg" width="197" height="240" border="0" /></a></div>

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

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

  • Error Line 341, Column 106: required attribute "alt" not specified
    …img src="images/slidepic6.jpg" width="197" height="240" border="0" /></a></div>

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

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

  • Error Line 344, Column 106: required attribute "alt" not specified
    …img src="images/slidepic7.jpg" width="197" height="240" border="0" /></a></div>

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

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

  • Error Line 347, Column 106: required attribute "alt" not specified
    …img src="images/slidepic8.jpg" width="197" height="240" border="0" /></a></div>

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

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

  • Warning Line 361, Column 45: character "<" is the first character of a delimiter but occurred as data
    …                          nextprev: ["<<", ">>"],  //labels for "prev" and "ne…

    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 361, Column 46: character "<" is the first character of a delimiter but occurred as data
    …                         nextprev: ["<<", ">>"],  //labels for "prev" and "nex…

    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 379, Column 30: ID "leftadcontainer20050" already defined
                        <div id="leftadcontainer20050">

    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 312, Column 30: ID "leftadcontainer20050" first defined here
                        <div id="leftadcontainer20050">
  • Error Line 380, Column 13: ID "hm-l-ad20050" already defined
        <ul id="hm-l-ad20050">

    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 313, Column 13: ID "hm-l-ad20050" first defined here
        <ul id="hm-l-ad20050">
  • Error Line 382, Column 56: required attribute "alt" not specified
                <img src="adimages/Radiance.gif" border="0"></a></li> 

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

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

  • Error Line 382, Column 60: end tag for "img" omitted, but OMITTAG NO was specified
                <img src="adimages/Radiance.gif" border="0"></a></li> 

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

  • Info Line 382, Column 13: start tag was here
                <img src="adimages/Radiance.gif" border="0"></a></li> 
  • Error Line 393, Column 12: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
            <li><a href="http://www.stopiles.com/" target="_blank">

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

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

  • Error Line 394, Column 76: required attribute "alt" not specified
    …  <img src="adimages/stopiles.gif" border="0" width="200" height="50"></a></li>

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

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

  • Error Line 394, Column 80: end tag for "img" omitted, but OMITTAG NO was specified
    …  <img src="adimages/stopiles.gif" border="0" width="200" height="50"></a></li>

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

  • Info Line 394, Column 9: start tag was here
            <img src="adimages/stopiles.gif" border="0" width="200" height="50"></a…
  • Error Line 396, Column 12: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
            <li><a href="http://www.veindoctor.in/veinbeta/" target="_blank">

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

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

  • Error Line 397, Column 86: required attribute "alt" not specified
    …="adimages/varicoseveinclinic.gif" border="0" width="200" height="50"></a></li>

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

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

  • Error Line 397, Column 90: end tag for "img" omitted, but OMITTAG NO was specified
    …="adimages/varicoseveinclinic.gif" border="0" width="200" height="50"></a></li>

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

  • Info Line 397, Column 9: start tag was here
            <img src="adimages/varicoseveinclinic.gif" border="0" width="200" heigh…
  • Error Line 404, Column 30: ID "leftadcontainer20050" already defined
                        <div id="leftadcontainer20050">

    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 312, Column 30: ID "leftadcontainer20050" first defined here
                        <div id="leftadcontainer20050">
  • Error Line 405, Column 13: ID "hm-l-ad20050" already defined
        <ul id="hm-l-ad20050">        

    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 313, Column 13: ID "hm-l-ad20050" first defined here
        <ul id="hm-l-ad20050">
  • Error Line 416, Column 60: required attribute "alt" not specified
                <img src="adimages/Country Oven.gif" 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 416, Column 64: end tag for "img" omitted, but OMITTAG NO was specified
                <img src="adimages/Country Oven.gif" border="0"></a>

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

  • Info Line 416, Column 13: start tag was here
                <img src="adimages/Country Oven.gif" border="0"></a>
  • Error Line 426, Column 75: required attribute "alt" not specified
        <img src="siteimages/politics-lpann-img.gif" width="201" height="30" />

    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 428, Column 55: cannot generate system identifier for general entity "no"
    …ref="news/newsitem.aspx?item=politics&no=1">&#194;&#195;&#162;“&#233;’&#174;&#…

    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 428, Column 55: general entity "no" not defined and no default entity
    …ref="news/newsitem.aspx?item=politics&no=1">&#194;&#195;&#162;“&#233;’&#174;&#…

    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 428, Column 57: reference not terminated by REFC delimiter
    …f="news/newsitem.aspx?item=politics&no=1">&#194;&#195;&#162;“&#233;’&#174;&#25…

    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 428, Column 57: reference to external entity in attribute value
    …f="news/newsitem.aspx?item=politics&no=1">&#194;&#195;&#162;“&#233;’&#174;&#25…

    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 428, Column 57: reference to entity "no" for which no system identifier could be generated
    …f="news/newsitem.aspx?item=politics&no=1">&#194;&#195;&#162;“&#233;’&#174;&#25…

    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 428, Column 54: entity was defined here
    …href="news/newsitem.aspx?item=politics&no=1">&#194;&#195;&#162;“&#233;’&#174;&…
  • Warning Line 429, Column 57: reference not terminated by REFC delimiter
    …f="news/newsitem.aspx?item=politics&no=2">-&#171;&#162;-Ÿ&#191; ’&#185;&#162;-…

    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 429, Column 57: reference to external entity in attribute value
    …f="news/newsitem.aspx?item=politics&no=2">-&#171;&#162;-Ÿ&#191; ’&#185;&#162;-…

    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 429, Column 57: reference to entity "no" for which no system identifier could be generated
    …f="news/newsitem.aspx?item=politics&no=2">-&#171;&#162;-Ÿ&#191; ’&#185;&#162;-…

    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 428, Column 54: entity was defined here
    …href="news/newsitem.aspx?item=politics&no=1">&#194;&#195;&#162;“&#233;’&#174;&…
  • Warning Line 430, Column 57: reference not terminated by REFC delimiter
    …f="news/newsitem.aspx?item=politics&no=3">‡&#174;&#253;&#168; &#194;&#195;&#17…

    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 430, Column 57: reference to external entity in attribute value
    …f="news/newsitem.aspx?item=politics&no=3">‡&#174;&#253;&#168; &#194;&#195;&#17…

    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 430, Column 57: reference to entity "no" for which no system identifier could be generated
    …f="news/newsitem.aspx?item=politics&no=3">‡&#174;&#253;&#168; &#194;&#195;&#17…

    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 428, Column 54: entity was defined here
    …href="news/newsitem.aspx?item=politics&no=1">&#194;&#195;&#162;“&#233;’&#174;&…
  • Warning Line 431, Column 57: reference not terminated by REFC delimiter
    …f="news/newsitem.aspx?item=politics&no=4">&#171;&#213;&gt;x&#174;&#253;&#202;&…

    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 431, Column 57: reference to external entity in attribute value
    …f="news/newsitem.aspx?item=politics&no=4">&#171;&#213;&gt;x&#174;&#253;&#202;&…

    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 431, Column 57: reference to entity "no" for which no system identifier could be generated
    …f="news/newsitem.aspx?item=politics&no=4">&#171;&#213;&gt;x&#174;&#253;&#202;&…

    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 428, Column 54: entity was defined here
    …href="news/newsitem.aspx?item=politics&no=1">&#194;&#195;&#162;“&#233;’&#174;&…
  • Warning Line 432, Column 57: reference not terminated by REFC delimiter
    …f="news/newsitem.aspx?item=politics&no=5">&#169;&#162;œ&#191;&#175;&#254; &#20…

    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 432, Column 57: reference to external entity in attribute value
    …f="news/newsitem.aspx?item=politics&no=5">&#169;&#162;œ&#191;&#175;&#254; &#20…

    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 432, Column 57: reference to entity "no" for which no system identifier could be generated
    …f="news/newsitem.aspx?item=politics&no=5">&#169;&#162;œ&#191;&#175;&#254; &#20…

    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 428, Column 54: entity was defined here
    …href="news/newsitem.aspx?item=politics&no=1">&#194;&#195;&#162;“&#233;’&#174;&…
  • Warning Line 433, Column 57: reference not terminated by REFC delimiter
    …f="news/newsitem.aspx?item=politics&no=6">&#197;&#231;&#169;&#162;’&#195;&#186…

    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 433, Column 57: reference to external entity in attribute value
    …f="news/newsitem.aspx?item=politics&no=6">&#197;&#231;&#169;&#162;’&#195;&#186…

    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 433, Column 57: reference to entity "no" for which no system identifier could be generated
    …f="news/newsitem.aspx?item=politics&no=6">&#197;&#231;&#169;&#162;’&#195;&#186…

    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 428, Column 54: entity was defined here
    …href="news/newsitem.aspx?item=politics&no=1">&#194;&#195;&#162;“&#233;’&#174;&…
  • Warning Line 434, Column 57: reference not terminated by REFC delimiter
    …f="news/newsitem.aspx?item=politics&no=7">“X&#190;&#197;&#228;u&#194;&#185; &#…

    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 434, Column 57: reference to external entity in attribute value
    …f="news/newsitem.aspx?item=politics&no=7">“X&#190;&#197;&#228;u&#194;&#185; &#…

    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 434, Column 57: reference to entity "no" for which no system identifier could be generated
    …f="news/newsitem.aspx?item=politics&no=7">“X&#190;&#197;&#228;u&#194;&#185; &#…

    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 428, Column 54: entity was defined here
    …href="news/newsitem.aspx?item=politics&no=1">&#194;&#195;&#162;“&#233;’&#174;&…
  • Warning Line 435, Column 57: reference not terminated by REFC delimiter
    …f="news/newsitem.aspx?item=politics&no=8">&#197;&#231;&#169;&#162;’&#195;&#186…

    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 435, Column 57: reference to external entity in attribute value
    …f="news/newsitem.aspx?item=politics&no=8">&#197;&#231;&#169;&#162;’&#195;&#186…

    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 435, Column 57: reference to entity "no" for which no system identifier could be generated
    …f="news/newsitem.aspx?item=politics&no=8">&#197;&#231;&#169;&#162;’&#195;&#186…

    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 428, Column 54: entity was defined here
    …href="news/newsitem.aspx?item=politics&no=1">&#194;&#195;&#162;“&#233;’&#174;&…
  • Warning Line 436, Column 57: reference not terminated by REFC delimiter
    …f="news/newsitem.aspx?item=politics&no=9">&#202;’&#185;Ÿ&#191;&#213; &#166;CM …

    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 436, Column 57: reference to external entity in attribute value
    …f="news/newsitem.aspx?item=politics&no=9">&#202;’&#185;Ÿ&#191;&#213; &#166;CM …

    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 436, Column 57: reference to entity "no" for which no system identifier could be generated
    …f="news/newsitem.aspx?item=politics&no=9">&#202;’&#185;Ÿ&#191;&#213; &#166;CM …

    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 428, Column 54: entity was defined here
    …href="news/newsitem.aspx?item=politics&no=1">&#194;&#195;&#162;“&#233;’&#174;&…
  • Error Line 448, Column 78: required attribute "alt" not specified
    …    <img src="adimages/us2gtr.gif" border="0" height="30" width="200"></a></li>

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

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

  • Error Line 448, Column 82: end tag for "img" omitted, but OMITTAG NO was specified
    …    <img src="adimages/us2gtr.gif" border="0" height="30" width="200"></a></li>

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

  • Info Line 448, Column 13: start tag was here
                <img src="adimages/us2gtr.gif" border="0" height="30" width="200"><…
  • Error Line 464, Column 21: ID "txt-e" already defined
                <li id="txt-e"><a href="http://www.mobikwik.com" target="_blank" st…

    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 459, Column 17: ID "txt-e" first defined here
            <li id="txt-e"><a href="http://www.kaakateeya.com/" target="_blank">kaa…
  • Error Line 465, Column 17: ID "txt-e" already defined
            <li id="txt-e"><a href="http://www.AbhiBus.com" target="_blank">BookBus…

    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 459, Column 17: ID "txt-e" first defined here
            <li id="txt-e"><a href="http://www.kaakateeya.com/" target="_blank">kaa…
  • Warning Line 468, Column 75: cannot generate system identifier for general entity "utm_source"
    …://www.telugushaadi.com?ptnr=eentxthp&utm_source=Partner&utm_medium=Eenadu&utm…

    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 468, Column 75: general entity "utm_source" not defined and no default entity
    …://www.telugushaadi.com?ptnr=eentxthp&utm_source=Partner&utm_medium=Eenadu&utm…

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

  • Warning Line 468, Column 85: reference not terminated by REFC delimiter
    …ugushaadi.com?ptnr=eentxthp&utm_source=Partner&utm_medium=Eenadu&utm_content=t…

    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 468, Column 85: reference to external entity in attribute value
    …ugushaadi.com?ptnr=eentxthp&utm_source=Partner&utm_medium=Eenadu&utm_content=t…

    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 468, Column 85: reference to entity "utm_source" for which no system identifier could be generated
    …ugushaadi.com?ptnr=eentxthp&utm_source=Partner&utm_medium=Eenadu&utm_content=t…

    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 468, Column 74: entity was defined here
    …p://www.telugushaadi.com?ptnr=eentxthp&utm_source=Partner&utm_medium=Eenadu&ut…
  • Warning Line 468, Column 94: cannot generate system identifier for general entity "utm_medium"
    ….com?ptnr=eentxthp&utm_source=Partner&utm_medium=Eenadu&utm_content=txtlink&ut…

    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 468, Column 94: general entity "utm_medium" not defined and no default entity
    ….com?ptnr=eentxthp&utm_source=Partner&utm_medium=Eenadu&utm_content=txtlink&ut…

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

  • Warning Line 468, Column 104: reference not terminated by REFC delimiter
    …eentxthp&utm_source=Partner&utm_medium=Eenadu&utm_content=txtlink&utm_campaign…

    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 468, Column 104: reference to external entity in attribute value
    …eentxthp&utm_source=Partner&utm_medium=Eenadu&utm_content=txtlink&utm_campaign…

    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 468, Column 104: reference to entity "utm_medium" for which no system identifier could be generated
    …eentxthp&utm_source=Partner&utm_medium=Eenadu&utm_content=txtlink&utm_campaign…

    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 468, Column 93: entity was defined here
    …i.com?ptnr=eentxthp&utm_source=Partner&utm_medium=Eenadu&utm_content=txtlink&u…
  • Warning Line 468, Column 112: cannot generate system identifier for general entity "utm_content"
    …hp&utm_source=Partner&utm_medium=Eenadu&utm_content=txtlink&utm_campaign=G310C"

    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 468, Column 112: general entity "utm_content" not defined and no default entity
    …hp&utm_source=Partner&utm_medium=Eenadu&utm_content=txtlink&utm_campaign=G310C"

    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 468, Column 123: reference not terminated by REFC delimiter
    …hp&utm_source=Partner&utm_medium=Eenadu&utm_content=txtlink&utm_campaign=G310C"

    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 468, Column 123: reference to external entity in attribute value
    …hp&utm_source=Partner&utm_medium=Eenadu&utm_content=txtlink&utm_campaign=G310C"

    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 468, Column 123: reference to entity "utm_content" for which no system identifier could be generated
    …hp&utm_source=Partner&utm_medium=Eenadu&utm_content=txtlink&utm_campaign=G310C"

    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 468, Column 111: entity was defined here
    …hp&utm_source=Partner&utm_medium=Eenadu&utm_content=txtlink&utm_campaign=G310C"
  • Warning Line 468, Column 132: cannot generate system identifier for general entity "utm_campaign"
    …hp&utm_source=Partner&utm_medium=Eenadu&utm_content=txtlink&utm_campaign=G310C"

    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 468, Column 132: general entity "utm_campaign" not defined and no default entity
    …hp&utm_source=Partner&utm_medium=Eenadu&utm_content=txtlink&utm_campaign=G310C"

    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 468, Column 144: reference not terminated by REFC delimiter
    …hp&utm_source=Partner&utm_medium=Eenadu&utm_content=txtlink&utm_campaign=G310C"

    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 468, Column 144: reference to external entity in attribute value
    …hp&utm_source=Partner&utm_medium=Eenadu&utm_content=txtlink&utm_campaign=G310C"

    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 468, Column 144: reference to entity "utm_campaign" for which no system identifier could be generated
    …hp&utm_source=Partner&utm_medium=Eenadu&utm_content=txtlink&utm_campaign=G310C"

    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 468, Column 131: entity was defined here
    …hp&utm_source=Partner&utm_medium=Eenadu&utm_content=txtlink&utm_campaign=G310C"
  • Error Line 481, Column 60: required attribute "alt" not specified
                    <img src="cartsmall080113.jpg" 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 492, Column 30: ID "lcol-pannel1" already defined
                        <div id="lcol-pannel1">

    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 425, Column 30: ID "lcol-pannel1" first defined here
                        <div id="lcol-pannel1">
  • Error Line 493, Column 71: required attribute "alt" not specified
        <img src="siteimages/exclusives-img.gif" width="201" height="30" />

    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 494, Column 13: ID "lcol-pannel1data" already defined
        <ul id="lcol-pannel1data">

    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 427, Column 13: ID "lcol-pannel1data" first defined here
        <ul id="lcol-pannel1data">
  • Error Line 500, Column 14: ID "lcol-pannel1bottom" already defined
        <div id="lcol-pannel1bottom">

    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 438, Column 15: ID "lcol-pannel1bottom" first defined here
         <div id="lcol-pannel1bottom">
  • Error Line 506, Column 23: "DOCTYPE" declaration not allowed in instance
                        <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//…
  • Error Line 507, 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 567, Column 30: ID "lcol-pannel1" already defined
                        <div id="lcol-pannel1">

    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 425, Column 30: ID "lcol-pannel1" first defined here
                        <div id="lcol-pannel1">
  • Error Line 568, Column 74: required attribute "alt" not specified
        <img src="siteimages/sahitisampada-img.gif" width="201" height="30" />

    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 569, Column 13: ID "lcol-pannel1data" already defined
        <ul id="lcol-pannel1data">

    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 427, Column 13: ID "lcol-pannel1data" first defined here
        <ul id="lcol-pannel1data">
  • Error Line 573, Column 14: ID "lcol-pannel1bottom" already defined
        <div id="lcol-pannel1bottom">

    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 438, Column 15: ID "lcol-pannel1bottom" first defined here
         <div id="lcol-pannel1bottom">
  • Error Line 581, Column 70: required attribute "alt" not specified
    <img src="siteimages/ruchulu-lpann-img.gif" width="201" height="30" />

    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 612, Column 4: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    <li>

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

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

  • Error Line 613, Column 125: required attribute "alt" not specified
    …arget="_blank"><img src="adimages/appsc-responce.gif" border="0" width="468" />

    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 623, Column 66: required attribute "alt" not specified
        <img src="siteimages/taja-img1.gif" width="468" height="32" />

    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 628, Column 14: ID "verytaja" already defined
        <div id="verytaja">

    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 625, Column 14: ID "verytaja" first defined here
        <div id="verytaja">
  • Error Line 631, Column 14: ID "verytaja" already defined
        <div id="verytaja">

    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 625, Column 14: ID "verytaja" first defined here
        <div id="verytaja">
  • Error Line 634, Column 14: ID "verytaja" already defined
        <div id="verytaja">

    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 625, Column 14: ID "verytaja" first defined here
        <div id="verytaja">
  • Error Line 644, Column 21: ID "hmb1" already defined
                <li id="hmb1">

    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 638, Column 21: ID "hmb1" first defined here
                <li id="hmb1">
  • Error Line 647, Column 21: ID "hmb2" already defined
                <li id="hmb2">

    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 641, Column 21: ID "hmb2" first defined here
                <li id="hmb2">
  • Error Line 650, Column 21: ID "hmb1" already defined
                <li id="hmb1">

    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 638, Column 21: ID "hmb1" first defined here
                <li id="hmb1">
  • Error Line 653, Column 21: ID "hmb2" already defined
                <li id="hmb2">

    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 641, Column 21: ID "hmb2" first defined here
                <li id="hmb2">
  • Error Line 656, Column 21: ID "hmb1" already defined
                <li id="hmb1">

    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 638, Column 21: ID "hmb1" first defined here
                <li id="hmb1">
  • Error Line 670, Column 10: ID "adcontainer468" already defined
    <div id="adcontainer468">

    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 611, Column 30: ID "adcontainer468" first defined here
                        <div id="adcontainer468">
  • Error Line 697, Column 9: end tag for "ul" which is not finished
        </ul>

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

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

  • Error Line 714, Column 76: required attribute "alt" not specified
                <img src="news/8panel1.jpg" width="95" height="85" border="0" />

    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 717, Column 54: reference not terminated by REFC delimiter
                <a href="news/newsitem.aspx?item=panel&no=1">Full Story...</a></div>

    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 717, Column 54: reference to external entity in attribute value
                <a href="news/newsitem.aspx?item=panel&no=1">Full Story...</a></div>

    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 717, Column 54: reference to entity "no" for which no system identifier could be generated
                <a href="news/newsitem.aspx?item=panel&no=1">Full Story...</a></div>

    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 428, Column 54: entity was defined here
    …href="news/newsitem.aspx?item=politics&no=1">&#194;&#195;&#162;“&#233;’&#174;&…
  • Error Line 719, Column 14: ID "pann" already defined
        <div id="pann">

    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 712, Column 14: ID "pann" first defined here
        <div id="pann">
  • Error Line 721, Column 76: required attribute "alt" not specified
                <img src="news/8panel2.jpg" width="95" height="85" border="0" />

    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 723, Column 18: ID "pannmore" already defined
            <div id="pannmore">

    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 716, Column 18: ID "pannmore" first defined here
            <div id="pannmore">
  • Warning Line 724, Column 54: reference not terminated by REFC delimiter
                <a href="news/newsitem.aspx?item=panel&no=2">Full Story...</a></div>

    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 724, Column 54: reference to external entity in attribute value
                <a href="news/newsitem.aspx?item=panel&no=2">Full Story...</a></div>

    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 724, Column 54: reference to entity "no" for which no system identifier could be generated
                <a href="news/newsitem.aspx?item=panel&no=2">Full Story...</a></div>

    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 428, Column 54: entity was defined here
    …href="news/newsitem.aspx?item=politics&no=1">&#194;&#195;&#162;“&#233;’&#174;&…
  • Error Line 726, Column 14: ID "pann" already defined
        <div id="pann">

    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 712, Column 14: ID "pann" first defined here
        <div id="pann">
  • Error Line 728, Column 76: required attribute "alt" not specified
                <img src="news/8panel3.jpg" width="95" height="85" border="0" />

    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 730, Column 18: ID "pannmore" already defined
            <div id="pannmore">

    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 716, Column 18: ID "pannmore" first defined here
            <div id="pannmore">
  • Warning Line 731, Column 54: reference not terminated by REFC delimiter
                <a href="news/newsitem.aspx?item=panel&no=3">Full Story...</a></div>

    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 731, Column 54: reference to external entity in attribute value
                <a href="news/newsitem.aspx?item=panel&no=3">Full Story...</a></div>

    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 731, Column 54: reference to entity "no" for which no system identifier could be generated
                <a href="news/newsitem.aspx?item=panel&no=3">Full Story...</a></div>

    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 428, Column 54: entity was defined here
    …href="news/newsitem.aspx?item=politics&no=1">&#194;&#195;&#162;“&#233;’&#174;&…
  • Error Line 737, Column 76: required attribute "alt" not specified
                <img src="news/8panel4.jpg" width="95" height="85" border="0" />

    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 740, Column 62: reference not terminated by REFC delimiter
    …           <a href="news/newsitem.aspx?item=panel&no=4">Full Story...</a></div>

    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 740, Column 62: reference to external entity in attribute value
    …           <a href="news/newsitem.aspx?item=panel&no=4">Full Story...</a></div>

    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 740, Column 62: reference to entity "no" for which no system identifier could be generated
    …           <a href="news/newsitem.aspx?item=panel&no=4">Full Story...</a></div>

    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 428, Column 54: entity was defined here
    …href="news/newsitem.aspx?item=politics&no=1">&#194;&#195;&#162;“&#233;’&#174;&…
  • Error Line 744, Column 76: required attribute "alt" not specified
                <img src="news/8panel5.jpg" width="95" height="85" border="0" />

    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 747, Column 62: reference not terminated by REFC delimiter
    …           <a href="news/newsitem.aspx?item=panel&no=5">Full Story...</a></div>

    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 747, Column 62: reference to external entity in attribute value
    …           <a href="news/newsitem.aspx?item=panel&no=5">Full Story...</a></div>

    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 747, Column 62: reference to entity "no" for which no system identifier could be generated
    …           <a href="news/newsitem.aspx?item=panel&no=5">Full Story...</a></div>

    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 428, Column 54: entity was defined here
    …href="news/newsitem.aspx?item=politics&no=1">&#194;&#195;&#162;“&#233;’&#174;&…
  • Error Line 751, Column 76: required attribute "alt" not specified
                <img src="news/8panel6.jpg" width="95" height="85" border="0" />

    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 754, Column 62: reference not terminated by REFC delimiter
    …           <a href="news/newsitem.aspx?item=panel&no=6">Full Story...</a></div>

    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 754, Column 62: reference to external entity in attribute value
    …           <a href="news/newsitem.aspx?item=panel&no=6">Full Story...</a></div>

    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 754, Column 62: reference to entity "no" for which no system identifier could be generated
    …           <a href="news/newsitem.aspx?item=panel&no=6">Full Story...</a></div>

    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 428, Column 54: entity was defined here
    …href="news/newsitem.aspx?item=politics&no=1">&#194;&#195;&#162;“&#233;’&#174;&…
  • Warning Line 760, Column 62: reference not terminated by REFC delimiter
    …           <a href="news/newsitem.aspx?item=panel&no=7">Full Story...</a></div>

    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 760, Column 62: reference to external entity in attribute value
    …           <a href="news/newsitem.aspx?item=panel&no=7">Full Story...</a></div>

    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 760, Column 62: reference to entity "no" for which no system identifier could be generated
    …           <a href="news/newsitem.aspx?item=panel&no=7">Full Story...</a></div>

    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 428, Column 54: entity was defined here
    …href="news/newsitem.aspx?item=politics&no=1">&#194;&#195;&#162;“&#233;’&#174;&…
  • Error Line 764, Column 76: required attribute "alt" not specified
                <img src="news/8panel8.jpg" width="95" height="85" border="0" />

    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 767, Column 62: reference not terminated by REFC delimiter
    …           <a href="news/newsitem.aspx?item=panel&no=8">Full Story...</a></div>

    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 767, Column 62: reference to external entity in attribute value
    …           <a href="news/newsitem.aspx?item=panel&no=8">Full Story...</a></div>

    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 767, Column 62: reference to entity "no" for which no system identifier could be generated
    …           <a href="news/newsitem.aspx?item=panel&no=8">Full Story...</a></div>

    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 428, Column 54: entity was defined here
    …href="news/newsitem.aspx?item=politics&no=1">&#194;&#195;&#162;“&#233;’&#174;&…
  • Warning Line 774, Column 62: reference not terminated by REFC delimiter
    …           <a href="news/newsitem.aspx?item=panel&no=9">Full Story...</a></div>

    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 774, Column 62: reference to external entity in attribute value
    …           <a href="news/newsitem.aspx?item=panel&no=9">Full Story...</a></div>

    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 774, Column 62: reference to entity "no" for which no system identifier could be generated
    …           <a href="news/newsitem.aspx?item=panel&no=9">Full Story...</a></div>

    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 428, Column 54: entity was defined here
    …href="news/newsitem.aspx?item=politics&no=1">&#194;&#195;&#162;“&#233;’&#174;&…
  • Error Line 778, Column 77: required attribute "alt" not specified
                <img src="news/8panel10.jpg" width="95" height="85" border="0" />

    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 781, Column 62: reference not terminated by REFC delimiter
    …          <a href="news/newsitem.aspx?item=panel&no=10">Full Story...</a></div>

    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 781, Column 62: reference to external entity in attribute value
    …          <a href="news/newsitem.aspx?item=panel&no=10">Full Story...</a></div>

    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 781, Column 62: reference to entity "no" for which no system identifier could be generated
    …          <a href="news/newsitem.aspx?item=panel&no=10">Full Story...</a></div>

    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 428, Column 54: entity was defined here
    …href="news/newsitem.aspx?item=politics&no=1">&#194;&#195;&#162;“&#233;’&#174;&…
  • Error Line 785, Column 77: required attribute "alt" not specified
                <img src="news/8panel11.jpg" width="95" height="85" border="0" />

    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 788, Column 62: reference not terminated by REFC delimiter
    …          <a href="news/newsitem.aspx?item=panel&no=11">Full Story...</a></div>

    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 788, Column 62: reference to external entity in attribute value
    …          <a href="news/newsitem.aspx?item=panel&no=11">Full Story...</a></div>

    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 788, Column 62: reference to entity "no" for which no system identifier could be generated
    …          <a href="news/newsitem.aspx?item=panel&no=11">Full Story...</a></div>

    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 428, Column 54: entity was defined here
    …href="news/newsitem.aspx?item=politics&no=1">&#194;&#195;&#162;“&#233;’&#174;&…
  • Error Line 792, Column 77: required attribute "alt" not specified
                <img src="news/8panel12.jpg" width="95" height="85" border="0" />

    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 795, Column 62: reference not terminated by REFC delimiter
    …          <a href="news/newsitem.aspx?item=panel&no=12">Full Story...</a></div>

    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 795, Column 62: reference to external entity in attribute value
    …          <a href="news/newsitem.aspx?item=panel&no=12">Full Story...</a></div>

    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 795, Column 62: reference to entity "no" for which no system identifier could be generated
    …          <a href="news/newsitem.aspx?item=panel&no=12">Full Story...</a></div>

    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 428, Column 54: entity was defined here
    …href="news/newsitem.aspx?item=politics&no=1">&#194;&#195;&#162;“&#233;’&#174;&…
  • Error Line 799, Column 77: required attribute "alt" not specified
                <img src="news/8panel13.jpg" width="95" height="85" border="0" />

    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 802, Column 62: reference not terminated by REFC delimiter
    …          <a href="news/newsitem.aspx?item=panel&no=13">Full Story...</a></div>

    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 802, Column 62: reference to external entity in attribute value
    …          <a href="news/newsitem.aspx?item=panel&no=13">Full Story...</a></div>

    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 802, Column 62: reference to entity "no" for which no system identifier could be generated
    …          <a href="news/newsitem.aspx?item=panel&no=13">Full Story...</a></div>

    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 428, Column 54: entity was defined here
    …href="news/newsitem.aspx?item=politics&no=1">&#194;&#195;&#162;“&#233;’&#174;&…
  • Error Line 806, Column 77: required attribute "alt" not specified
                <img src="news/8panel14.jpg" width="95" height="85" border="0" />

    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 810, Column 62: reference not terminated by REFC delimiter
    …          <a href="news/newsitem.aspx?item=panel&no=14">Full Story...</a></div>

    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 810, Column 62: reference to external entity in attribute value
    …          <a href="news/newsitem.aspx?item=panel&no=14">Full Story...</a></div>

    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 810, Column 62: reference to entity "no" for which no system identifier could be generated
    …          <a href="news/newsitem.aspx?item=panel&no=14">Full Story...</a></div>

    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 428, Column 54: entity was defined here
    …href="news/newsitem.aspx?item=politics&no=1">&#194;&#195;&#162;“&#233;’&#174;&…
  • Error Line 820, Column 42: ID "datapannel" already defined
                                    <div id="datapannel">

    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 711, Column 42: ID "datapannel" first defined here
                                    <div id="datapannel">
  • Error Line 821, Column 14: ID "pann" already defined
        <div id="pann">

    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 712, Column 14: ID "pann" first defined here
        <div id="pann">
  • Error Line 825, Column 18: ID "pannmore" already defined
            <div id="pannmore">

    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 716, Column 18: ID "pannmore" first defined here
            <div id="pannmore">
  • Warning Line 826, Column 54: reference not terminated by REFC delimiter
                <a href="news/newsitem.aspx?item=state&no=1">Full Story...</a></div>

    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 826, Column 54: reference to external entity in attribute value
                <a href="news/newsitem.aspx?item=state&no=1">Full Story...</a></div>

    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 826, Column 54: reference to entity "no" for which no system identifier could be generated
                <a href="news/newsitem.aspx?item=state&no=1">Full Story...</a></div>

    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 428, Column 54: entity was defined here
    …href="news/newsitem.aspx?item=politics&no=1">&#194;&#195;&#162;“&#233;’&#174;&…
  • Error Line 828, Column 14: ID "pann" already defined
        <div id="pann">

    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 712, Column 14: ID "pann" first defined here
        <div id="pann">
  • Error Line 832, Column 18: ID "pannmore" already defined
            <div id="pannmore">

    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 716, Column 18: ID "pannmore" first defined here
            <div id="pannmore">
  • Warning Line 833, Column 54: reference not terminated by REFC delimiter
                <a href="news/newsitem.aspx?item=state&no=2">Full Story...</a></div>

    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 833, Column 54: reference to external entity in attribute value
                <a href="news/newsitem.aspx?item=state&no=2">Full Story...</a></div>

    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 833, Column 54: reference to entity "no" for which no system identifier could be generated
                <a href="news/newsitem.aspx?item=state&no=2">Full Story...</a></div>

    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 428, Column 54: entity was defined here
    …href="news/newsitem.aspx?item=politics&no=1">&#194;&#195;&#162;“&#233;’&#174;&…
  • Error Line 835, Column 14: ID "pann" already defined
        <div id="pann">

    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 712, Column 14: ID "pann" first defined here
        <div id="pann">
  • Error Line 839, Column 18: ID "pannmore" already defined
            <div id="pannmore">

    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 716, Column 18: ID "pannmore" first defined here
            <div id="pannmore">
  • Warning Line 840, Column 54: reference not terminated by REFC delimiter
                <a href="news/newsitem.aspx?item=state&no=3">Full Story...</a></div>

    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 840, Column 54: reference to external entity in attribute value
                <a href="news/newsitem.aspx?item=state&no=3">Full Story...</a></div>

    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 840, Column 54: reference to entity "no" for which no system identifier could be generated
                <a href="news/newsitem.aspx?item=state&no=3">Full Story...</a></div>

    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 428, Column 54: entity was defined here
    …href="news/newsitem.aspx?item=politics&no=1">&#194;&#195;&#162;“&#233;’&#174;&…
  • Error Line 842, Column 14: ID "subpann" already defined
        <div id="subpann">

    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 733, Column 14: ID "subpann" first defined here
        <div id="subpann">
  • Error Line 846, Column 76: required attribute "alt" not specified
                <img src="news/8state4.jpg" width="95" height="85" border="0" />

    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 849, Column 62: reference not terminated by REFC delimiter
    …           <a href="news/newsitem.aspx?item=state&no=4">Full Story...</a></div>

    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 849, Column 62: reference to external entity in attribute value
    …           <a href="news/newsitem.aspx?item=state&no=4">Full Story...</a></div>

    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 849, Column 62: reference to entity "no" for which no system identifier could be generated
    …           <a href="news/newsitem.aspx?item=state&no=4">Full Story...</a></div>

    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 428, Column 54: entity was defined here
    …href="news/newsitem.aspx?item=politics&no=1">&#194;&#195;&#162;“&#233;’&#174;&…
  • Warning Line 856, Column 62: reference not terminated by REFC delimiter
    …           <a href="news/newsitem.aspx?item=state&no=5">Full Story...</a></div>

    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 856, Column 62: reference to external entity in attribute value
    …           <a href="news/newsitem.aspx?item=state&no=5">Full Story...</a></div>

    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 856, Column 62: reference to entity "no" for which no system identifier could be generated
    …           <a href="news/newsitem.aspx?item=state&no=5">Full Story...</a></div>

    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 428, Column 54: entity was defined here
    …href="news/newsitem.aspx?item=politics&no=1">&#194;&#195;&#162;“&#233;’&#174;&…
  • Error Line 860, Column 76: required attribute "alt" not specified
                <img src="news/8state6.jpg" width="95" height="85" border="0" />

    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 863, Column 62: reference not terminated by REFC delimiter
    …           <a href="news/newsitem.aspx?item=state&no=6">Full Story...</a></div>

    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 863, Column 62: reference to external entity in attribute value
    …           <a href="news/newsitem.aspx?item=state&no=6">Full Story...</a></div>

    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 863, Column 62: reference to entity "no" for which no system identifier could be generated
    …           <a href="news/newsitem.aspx?item=state&no=6">Full Story...</a></div>

    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 428, Column 54: entity was defined here
    …href="news/newsitem.aspx?item=politics&no=1">&#194;&#195;&#162;“&#233;’&#174;&…
  • Error Line 867, Column 76: required attribute "alt" not specified
                <img src="news/8state7.jpg" width="95" height="85" border="0" />

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

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

  • Warning Line 871, Column 62: reference not terminated by REFC delimiter
    …           <a href="news/newsitem.aspx?item=state&no=7">Full Story...</a></div>

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

  • Warning Line 871, Column 62: reference to external entity in attribute value
    …           <a href="news/newsitem.aspx?item=state&no=7">Full Story...</a></div>

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

  • Error Line 871, Column 62: reference to entity "no" for which no system identifier could be generated
    …           <a href="news/newsitem.aspx?item=state&no=7">Full Story...</a></div>

    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 428, Column 54: entity was defined here
    …href="news/newsitem.aspx?item=politics&no=1">&#194;&#195;&#162;“&#233;’&#174;&…
  • Warning Line 878, Column 62: reference not terminated by REFC delimiter
    …           <a href="news/newsitem.aspx?item=state&no=8">Full Story...</a></div>

    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 878, Column 62: reference to external entity in attribute value
    …           <a href="news/newsitem.aspx?item=state&no=8">Full Story...</a></div>

    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 878, Column 62: reference to entity "no" for which no system identifier could be generated
    …           <a href="news/newsitem.aspx?item=state&no=8">Full Story...</a></div>

    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 428, Column 54: entity was defined here
    …href="news/newsitem.aspx?item=politics&no=1">&#194;&#195;&#162;“&#233;’&#174;&…
  • Error Line 882, Column 76: required attribute "alt" not specified
                <img src="news/8state9.jpg" width="95" height="85" border="0" />

    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 886, Column 62: reference not terminated by REFC delimiter
    …           <a href="news/newsitem.aspx?item=state&no=9">Full Story...</a></div>

    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 886, Column 62: reference to external entity in attribute value
    …           <a href="news/newsitem.aspx?item=state&no=9">Full Story...</a></div>

    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 886, Column 62: reference to entity "no" for which no system identifier could be generated
    …           <a href="news/newsitem.aspx?item=state&no=9">Full Story...</a></div>

    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 428, Column 54: entity was defined here
    …href="news/newsitem.aspx?item=politics&no=1">&#194;&#195;&#162;“&#233;’&#174;&…
  • Warning Line 893, Column 62: reference not terminated by REFC delimiter
    …          <a href="news/newsitem.aspx?item=state&no=10">Full Story...</a></div>

    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 893, Column 62: reference to external entity in attribute value
    …          <a href="news/newsitem.aspx?item=state&no=10">Full Story...</a></div>

    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 893, Column 62: reference to entity "no" for which no system identifier could be generated
    …          <a href="news/newsitem.aspx?item=state&no=10">Full Story...</a></div>

    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 428, Column 54: entity was defined here
    …href="news/newsitem.aspx?item=politics&no=1">&#194;&#195;&#162;“&#233;’&#174;&…
  • Warning Line 900, Column 62: reference not terminated by REFC delimiter
    …          <a href="news/newsitem.aspx?item=state&no=11">Full Story...</a></div>

    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 900, Column 62: reference to external entity in attribute value
    …          <a href="news/newsitem.aspx?item=state&no=11">Full Story...</a></div>

    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 900, Column 62: reference to entity "no" for which no system identifier could be generated
    …          <a href="news/newsitem.aspx?item=state&no=11">Full Story...</a></div>

    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 428, Column 54: entity was defined here
    …href="news/newsitem.aspx?item=politics&no=1">&#194;&#195;&#162;“&#233;’&#174;&…
  • Warning Line 907, Column 62: reference not terminated by REFC delimiter
    …          <a href="news/newsitem.aspx?item=state&no=12">Full Story...</a></div>

    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 907, Column 62: reference to external entity in attribute value
    …          <a href="news/newsitem.aspx?item=state&no=12">Full Story...</a></div>

    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 907, Column 62: reference to entity "no" for which no system identifier could be generated
    …          <a href="news/newsitem.aspx?item=state&no=12">Full Story...</a></div>

    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 428, Column 54: entity was defined here
    …href="news/newsitem.aspx?item=politics&no=1">&#194;&#195;&#162;“&#233;’&#174;&…
  • Warning Line 914, Column 62: reference not terminated by REFC delimiter
    …          <a href="news/newsitem.aspx?item=state&no=13">Full Story...</a></div>

    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 914, Column 62: reference to external entity in attribute value
    …          <a href="news/newsitem.aspx?item=state&no=13">Full Story...</a></div>

    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 914, Column 62: reference to entity "no" for which no system identifier could be generated
    …          <a href="news/newsitem.aspx?item=state&no=13">Full Story...</a></div>

    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 428, Column 54: entity was defined here
    …href="news/newsitem.aspx?item=politics&no=1">&#194;&#195;&#162;“&#233;’&#174;&…
  • Warning Line 921, Column 62: reference not terminated by REFC delimiter
    …          <a href="news/newsitem.aspx?item=state&no=14">Full Story...</a></div>

    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 921, Column 62: reference to external entity in attribute value
    …          <a href="news/newsitem.aspx?item=state&no=14">Full Story...</a></div>

    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 921, Column 62: reference to entity "no" for which no system identifier could be generated
    …          <a href="news/newsitem.aspx?item=state&no=14">Full Story...</a></div>

    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 428, Column 54: entity was defined here
    …href="news/newsitem.aspx?item=politics&no=1">&#194;&#195;&#162;“&#233;’&#174;&…
  • Error Line 925, Column 77: required attribute "alt" not specified
                <img src="news/8state15.jpg" width="95" height="85" border="0" />

    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 928, Column 62: reference not terminated by REFC delimiter
    …          <a href="news/newsitem.aspx?item=state&no=15">Full Story...</a></div>

    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 928, Column 62: reference to external entity in attribute value
    …          <a href="news/newsitem.aspx?item=state&no=15">Full Story...</a></div>

    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 928, Column 62: reference to entity "no" for which no system identifier could be generated
    …          <a href="news/newsitem.aspx?item=state&no=15">Full Story...</a></div>

    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 428, Column 54: entity was defined here
    …href="news/newsitem.aspx?item=politics&no=1">&#194;&#195;&#162;“&#233;’&#174;&…
  • Warning Line 935, Column 62: reference not terminated by REFC delimiter
    …          <a href="news/newsitem.aspx?item=state&no=16">Full Story...</a></div>

    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 935, Column 62: reference to external entity in attribute value
    …          <a href="news/newsitem.aspx?item=state&no=16">Full Story...</a></div>

    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 935, Column 62: reference to entity "no" for which no system identifier could be generated
    …          <a href="news/newsitem.aspx?item=state&no=16">Full Story...</a></div>

    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 428, Column 54: entity was defined here
    …href="news/newsitem.aspx?item=politics&no=1">&#194;&#195;&#162;“&#233;’&#174;&…
  • Warning Line 942, Column 62: reference not terminated by REFC delimiter
    …          <a href="news/newsitem.aspx?item=state&no=17">Full Story...</a></div>

    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 942, Column 62: reference to external entity in attribute value
    …          <a href="news/newsitem.aspx?item=state&no=17">Full Story...</a></div>

    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 942, Column 62: reference to entity "no" for which no system identifier could be generated
    …          <a href="news/newsitem.aspx?item=state&no=17">Full Story...</a></div>

    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 428, Column 54: entity was defined here
    …href="news/newsitem.aspx?item=politics&no=1">&#194;&#195;&#162;“&#233;’&#174;&…
  • Error Line 946, Column 77: required attribute "alt" not specified
                <img src="news/8state18.jpg" width="95" height="85" border="0" />

    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 950, Column 62: reference not terminated by REFC delimiter
    …          <a href="news/newsitem.aspx?item=state&no=18">Full Story...</a></div>

    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 950, Column 62: reference to external entity in attribute value
    …          <a href="news/newsitem.aspx?item=state&no=18">Full Story...</a></div>

    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 950, Column 62: reference to entity "no" for which no system identifier could be generated
    …          <a href="news/newsitem.aspx?item=state&no=18">Full Story...</a></div>

    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 428, Column 54: entity was defined here
    …href="news/newsitem.aspx?item=politics&no=1">&#194;&#195;&#162;“&#233;’&#174;&…
  • Warning Line 957, Column 62: reference not terminated by REFC delimiter
    …          <a href="news/newsitem.aspx?item=state&no=19">Full Story...</a></div>

    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 957, Column 62: reference to external entity in attribute value
    …          <a href="news/newsitem.aspx?item=state&no=19">Full Story...</a></div>

    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 957, Column 62: reference to entity "no" for which no system identifier could be generated
    …          <a href="news/newsitem.aspx?item=state&no=19">Full Story...</a></div>

    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 428, Column 54: entity was defined here
    …href="news/newsitem.aspx?item=politics&no=1">&#194;&#195;&#162;“&#233;’&#174;&…
  • Warning Line 964, Column 62: reference not terminated by REFC delimiter
    …          <a href="news/newsitem.aspx?item=state&no=20">Full Story...</a></div>

    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 964, Column 62: reference to external entity in attribute value
    …          <a href="news/newsitem.aspx?item=state&no=20">Full Story...</a></div>

    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 964, Column 62: reference to entity "no" for which no system identifier could be generated
    …          <a href="news/newsitem.aspx?item=state&no=20">Full Story...</a></div>

    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 428, Column 54: entity was defined here
    …href="news/newsitem.aspx?item=politics&no=1">&#194;&#195;&#162;“&#233;’&#174;&…
  • Warning Line 971, Column 62: reference not terminated by REFC delimiter
    …          <a href="news/newsitem.aspx?item=state&no=21">Full Story...</a></div>

    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 971, Column 62: reference to external entity in attribute value
    …          <a href="news/newsitem.aspx?item=state&no=21">Full Story...</a></div>

    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 971, Column 62: reference to entity "no" for which no system identifier could be generated
    …          <a href="news/newsitem.aspx?item=state&no=21">Full Story...</a></div>

    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 428, Column 54: entity was defined here
    …href="news/newsitem.aspx?item=politics&no=1">&#194;&#195;&#162;“&#233;’&#174;&…
  • Error Line 975, Column 77: required attribute "alt" not specified
                <img src="news/8state22.jpg" width="95" height="85" border="0" />

    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 979, Column 62: reference not terminated by REFC delimiter
    …          <a href="news/newsitem.aspx?item=state&no=22">Full Story...</a></div>

    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 979, Column 62: reference to external entity in attribute value
    …          <a href="news/newsitem.aspx?item=state&no=22">Full Story...</a></div>

    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 979, Column 62: reference to entity "no" for which no system identifier could be generated
    …          <a href="news/newsitem.aspx?item=state&no=22">Full Story...</a></div>

    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 428, Column 54: entity was defined here
    …href="news/newsitem.aspx?item=politics&no=1">&#194;&#195;&#162;“&#233;’&#174;&…
  • Error Line 983, Column 77: required attribute "alt" not specified
                <img src="news/8state23.jpg" width="95" height="85" border="0" />

    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 986, Column 62: reference not terminated by REFC delimiter
    …          <a href="news/newsitem.aspx?item=state&no=23">Full Story...</a></div>

    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 986, Column 62: reference to external entity in attribute value
    …          <a href="news/newsitem.aspx?item=state&no=23">Full Story...</a></div>

    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 986, Column 62: reference to entity "no" for which no system identifier could be generated
    …          <a href="news/newsitem.aspx?item=state&no=23">Full Story...</a></div>

    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 428, Column 54: entity was defined here
    …href="news/newsitem.aspx?item=politics&no=1">&#194;&#195;&#162;“&#233;’&#174;&…
  • Warning Line 993, Column 62: reference not terminated by REFC delimiter
    …          <a href="news/newsitem.aspx?item=state&no=24">Full Story...</a></div>

    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 993, Column 62: reference to external entity in attribute value
    …          <a href="news/newsitem.aspx?item=state&no=24">Full Story...</a></div>

    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 993, Column 62: reference to entity "no" for which no system identifier could be generated
    …          <a href="news/newsitem.aspx?item=state&no=24">Full Story...</a></div>

    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 428, Column 54: entity was defined here
    …href="news/newsitem.aspx?item=politics&no=1">&#194;&#195;&#162;“&#233;’&#174;&…
  • Warning Line 1000, Column 62: reference not terminated by REFC delimiter
    …          <a href="news/newsitem.aspx?item=state&no=25">Full Story...</a></div>

    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 1000, Column 62: reference to external entity in attribute value
    …          <a href="news/newsitem.aspx?item=state&no=25">Full Story...</a></div>

    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 1000, Column 62: reference to entity "no" for which no system identifier could be generated
    …          <a href="news/newsitem.aspx?item=state&no=25">Full Story...</a></div>

    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 428, Column 54: entity was defined here
    …href="news/newsitem.aspx?item=politics&no=1">&#194;&#195;&#162;“&#233;’&#174;&…
  • Warning Line 1007, Column 62: reference not terminated by REFC delimiter
    …          <a href="news/newsitem.aspx?item=state&no=26">Full Story...</a></div>

    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 1007, Column 62: reference to external entity in attribute value
    …          <a href="news/newsitem.aspx?item=state&no=26">Full Story...</a></div>

    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 1007, Column 62: reference to entity "no" for which no system identifier could be generated
    …          <a href="news/newsitem.aspx?item=state&no=26">Full Story...</a></div>

    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 428, Column 54: entity was defined here
    …href="news/newsitem.aspx?item=politics&no=1">&#194;&#195;&#162;“&#233;’&#174;&…
  • Error Line 1011, Column 77: required attribute "alt" not specified
                <img src="news/8state27.jpg" width="95" height="85" border="0" />

    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 1014, Column 62: reference not terminated by REFC delimiter
    …          <a href="news/newsitem.aspx?item=state&no=27">Full Story...</a></div>

    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 1014, Column 62: reference to external entity in attribute value
    …          <a href="news/newsitem.aspx?item=state&no=27">Full Story...</a></div>

    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 1014, Column 62: reference to entity "no" for which no system identifier could be generated
    …          <a href="news/newsitem.aspx?item=state&no=27">Full Story...</a></div>

    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 428, Column 54: entity was defined here
    …href="news/newsitem.aspx?item=politics&no=1">&#194;&#195;&#162;“&#233;’&#174;&…
  • Error Line 1024, Column 42: ID "datapannel" already defined
                                    <div id="datapannel">

    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 711, Column 42: ID "datapannel" first defined here
                                    <div id="datapannel">
  • Error Line 1025, Column 14: ID "pann" already defined
        <div id="pann">

    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 712, Column 14: ID "pann" first defined here
        <div id="pann">
  • Error Line 1027, Column 76: required attribute "alt" not specified
                <img src="news/8story1.jpg" width="95" height="85" border="0" />

    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 1029, Column 18: ID "pannmore" already defined
            <div id="pannmore">

    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 716, Column 18: ID "pannmore" first defined here
            <div id="pannmore">
  • Warning Line 1030, Column 54: reference not terminated by REFC delimiter
                <a href="news/newsitem.aspx?item=story&no=1">Full Story...</a></div>

    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 1030, Column 54: reference to external entity in attribute value
                <a href="news/newsitem.aspx?item=story&no=1">Full Story...</a></div>

    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 1030, Column 54: reference to entity "no" for which no system identifier could be generated
                <a href="news/newsitem.aspx?item=story&no=1">Full Story...</a></div>

    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 428, Column 54: entity was defined here
    …href="news/newsitem.aspx?item=politics&no=1">&#194;&#195;&#162;“&#233;’&#174;&…
  • Error Line 1032, Column 14: ID "pann" already defined
        <div id="pann">

    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 712, Column 14: ID "pann" first defined here
        <div id="pann">
  • Error Line 1034, Column 76: required attribute "alt" not specified
                <img src="news/8story2.jpg" width="95" height="85" border="0" />

    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 1036, Column 18: ID "pannmore" already defined
            <div id="pannmore">

    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 716, Column 18: ID "pannmore" first defined here
            <div id="pannmore">
  • Warning Line 1037, Column 54: reference not terminated by REFC delimiter
                <a href="news/newsitem.aspx?item=story&no=2">Full Story...</a></div>

    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 1037, Column 54: reference to external entity in attribute value
                <a href="news/newsitem.aspx?item=story&no=2">Full Story...</a></div>

    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 1037, Column 54: reference to entity "no" for which no system identifier could be generated
                <a href="news/newsitem.aspx?item=story&no=2">Full Story...</a></div>

    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 428, Column 54: entity was defined here
    …href="news/newsitem.aspx?item=politics&no=1">&#194;&#195;&#162;“&#233;’&#174;&…
  • Error Line 1039, Column 14: ID "pann" already defined
        <div id="pann">

    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 712, Column 14: ID "pann" first defined here
        <div id="pann">
  • Error Line 1043, Column 18: ID "pannmore" already defined
            <div id="pannmore">

    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 716, Column 18: ID "pannmore" first defined here
            <div id="pannmore">
  • Warning Line 1044, Column 54: reference not terminated by REFC delimiter
                <a href="news/newsitem.aspx?item=story&no=3">Full Story...</a></div>

    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 1044, Column 54: reference to external entity in attribute value
                <a href="news/newsitem.aspx?item=story&no=3">Full Story...</a></div>

    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 1044, Column 54: reference to entity "no" for which no system identifier could be generated
                <a href="news/newsitem.aspx?item=story&no=3">Full Story...</a></div>

    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 428, Column 54: entity was defined here
    …href="news/newsitem.aspx?item=politics&no=1">&#194;&#195;&#162;“&#233;’&#174;&…
  • Error Line 1046, Column 14: ID "subpann" already defined
        <div id="subpann">

    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 733, Column 14: ID "subpann" first defined here
        <div id="subpann">
  • Error Line 1050, Column 76: required attribute "alt" not specified
                <img src="news/8story4.jpg" width="95" height="85" border="0" />

    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 1053, Column 62: reference not terminated by REFC delimiter
    …           <a href="news/newsitem.aspx?item=story&no=4">Full Story...</a></div>

    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 1053, Column 62: reference to external entity in attribute value
    …           <a href="news/newsitem.aspx?item=story&no=4">Full Story...</a></div>

    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 1053, Column 62: reference to entity "no" for which no system identifier could be generated
    …           <a href="news/newsitem.aspx?item=story&no=4">Full Story...</a></div>

    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 428, Column 54: entity was defined here
    …href="news/newsitem.aspx?item=politics&no=1">&#194;&#195;&#162;“&#233;’&#174;&…
  • Warning Line 1060, Column 62: reference not terminated by REFC delimiter
    …           <a href="news/newsitem.aspx?item=story&no=5">Full Story...</a></div>

    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 1060, Column 62: reference to external entity in attribute value
    …           <a href="news/newsitem.aspx?item=story&no=5">Full Story...</a></div>

    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 1060, Column 62: reference to entity "no" for which no system identifier could be generated
    …           <a href="news/newsitem.aspx?item=story&no=5">Full Story...</a></div>

    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 428, Column 54: entity was defined here
    …href="news/newsitem.aspx?item=politics&no=1">&#194;&#195;&#162;“&#233;’&#174;&…
  • Error Line 1084, Column 30: ID "adcontainer468" already defined
                        <div id="adcontainer468">

    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 611, Column 30: ID "adcontainer468" first defined here
                        <div id="adcontainer468">
  • Error Line 1085, Column 13: ID "ad468" already defined
        <ul id="ad468">

    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 671, Column 13: ID "ad468" first defined here
        <ul id="ad468">
  • Error Line 1089, Column 70: end tag for "param" omitted, but OMITTAG NO was specified
                    <param name='Movie' value="adimages/468x60_raft.swf">

    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 1089, Column 17: start tag was here
                    <param name='Movie' value="adimages/468x60_raft.swf">
  • Error Line 1090, Column 68: end tag for "param" omitted, but OMITTAG NO was specified
                    <param name='Src' value="adimages/468x60_raft.swf">

    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 1090, Column 17: start tag was here
                    <param name='Src' value="adimages/468x60_raft.swf">
  • Error Line 1092, Column 28: there is no attribute "src"
                    <embed src="adimages/468x60_raft.swf" menu="false" quality="hig…

    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 1092, Column 60: there is no attribute "menu"
    …d src="adimages/468x60_raft.swf" menu="false" quality="high" width="468" 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 1092, Column 76: there is no attribute "quality"
    …468x60_raft.swf" menu="false" quality="high" width="468" height="60" wmode="tr…

    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 1092, Column 89: there is no attribute "width"
    …ft.swf" menu="false" quality="high" width="468" height="60" wmode="transparent"

    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 1092, Column 102: there is no attribute "height"
    …ft.swf" menu="false" quality="high" width="468" height="60" wmode="transparent"

    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 1092, Column 113: there is no attribute "wmode"
    …ft.swf" menu="false" quality="high" width="468" height="60" wmode="transparent"

    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 1093, Column 26: there is no attribute "type"
                        type="application/x-shockwave-flash" pluginspage="http://ww…

    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 1093, Column 70: there is no attribute "pluginspage"
    …cation/x-shockwave-flash" pluginspage="http://www.macromedia.com/shockwave/dow…

    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 1093, Column 157: element "embed" undefined
    …media.com/shockwave/download/index.cgi?P1_Prod_Version=ShockwaveFlash"></embed>

    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 1126, Column 50: required attribute "alt" not specified
            <img src="siteimages/cinema-hm-img.gif" /></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 1131, Column 83: required attribute "alt" not specified
    …        <img src="news/hm-cinema-pic.jpg" width="190" height="90" border="0" />

    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 1137, Column 14: ID "cenhmpannl-more" already defined
        <div id="cenhmpannl-more">

    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 1135, Column 14: ID "cenhmpannl-more" first defined here
        <div id="cenhmpannl-more">
  • Error Line 1140, Column 53: required attribute "alt" not specified
            <img src="siteimages/cinema-hm-bottom.gif" /></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 1147, Column 48: required attribute "alt" not specified
            <img src="siteimages/vasu-hm-img.gif" /></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 1152, Column 87: required attribute "alt" not specified
    …    <img src="news/hm-vasundhara-pic.jpg" width="190" height="90" border="0" />

    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 1158, Column 14: ID "cenhmpannr-more" already defined
        <div id="cenhmpannr-more">

    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 1156, Column 14: ID "cenhmpannr-more" first defined here
        <div id="cenhmpannr-more">
  • Error Line 1161, Column 51: required attribute "alt" not specified
            <img src="siteimages/vasu-hm-bottom.gif" /></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 1166, Column 30: ID "cenhmpannl" already defined
                        <div id="cenhmpannl">

    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 1124, Column 30: ID "cenhmpannl" first defined here
                        <div id="cenhmpannl">
  • Error Line 1168, Column 49: required attribute "alt" not specified
            <img src="siteimages/champ-hm-img.gif" /></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 1173, Column 83: required attribute "alt" not specified
    …        <img src="news/hm-sports-pic.jpg" width="190" height="90" border="0" />

    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 1177, Column 14: ID "cenhmpannl-more" already defined
        <div id="cenhmpannl-more">

    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 1135, Column 14: ID "cenhmpannl-more" first defined here
        <div id="cenhmpannl-more">
  • Error Line 1179, Column 14: ID "cenhmpannl-more" already defined
        <div id="cenhmpannl-more">

    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 1135, Column 14: ID "cenhmpannl-more" first defined here
        <div id="cenhmpannl-more">
  • Error Line 1181, Column 14: ID "cenhmpannl-bottom" already defined
        <div id="cenhmpannl-bottom">

    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 1139, Column 14: ID "cenhmpannl-bottom" first defined here
        <div id="cenhmpannl-bottom">
  • Error Line 1182, Column 52: required attribute "alt" not specified
            <img src="siteimages/champ-hm-bottom.gif" /></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 1187, Column 30: ID "cenhmpannr" already defined
                        <div id="cenhmpannr">

    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 1145, Column 30: ID "cenhmpannr" first defined here
                        <div id="cenhmpannr">
  • Error Line 1189, Column 50: required attribute "alt" not specified
            <img src="siteimages/busine-hm-img.gif" /></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 1194, Column 85: required attribute "alt" not specified
    …      <img src="news/hm-business-pic.jpg" width="190" height="90" border="0" />

    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 1198, Column 14: ID "cenhmpannr-more" already defined
        <div id="cenhmpannr-more">

    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 1156, Column 14: ID "cenhmpannr-more" first defined here
        <div id="cenhmpannr-more">
  • Warning Line 1199, Column 54: reference not terminated by REFC delimiter
            <a href="news/bnewsitem.aspx?item=business&no=1">Full Story...</a></div>

    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 1199, Column 54: reference to external entity in attribute value
            <a href="news/bnewsitem.aspx?item=business&no=1">Full Story...</a></div>

    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 1199, Column 54: reference to entity "no" for which no system identifier could be generated
            <a href="news/bnewsitem.aspx?item=business&no=1">Full Story...</a></div>

    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 428, Column 54: entity was defined here
    …href="news/newsitem.aspx?item=politics&no=1">&#194;&#195;&#162;“&#233;’&#174;&…
  • Error Line 1200, Column 14: ID "cenhmpannr-more" already defined
        <div id="cenhmpannr-more">

    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 1156, Column 14: ID "cenhmpannr-more" first defined here
        <div id="cenhmpannr-more">
  • Error Line 1202, Column 14: ID "cenhmpannr-bottom" already defined
        <div id="cenhmpannr-bottom">

    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 1160, Column 14: ID "cenhmpannr-bottom" first defined here
        <div id="cenhmpannr-bottom">
  • Error Line 1203, Column 53: required attribute "alt" not specified
            <img src="siteimages/busine-hm-bottom.gif" /></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 1213, Column 82: required attribute "alt" not specified
    …     <img src="news/hm-spclpg-pic.jpg" width="85" height="95" 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 1221, Column 77: required attribute "alt" not specified
                    <img src="siteimages/hm-spclpages-haibujji.png" border="0" />

    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 1223, Column 76: required attribute "alt" not specified
                    <img src="siteimages/hm-spclpages-chaduvu.png" border="0" />

    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 1225, Column 78: required attribute "alt" not specified
                    <img src="siteimages/hm-spclpages-sukhibava.png" border="0" />

    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 1227, Column 73: required attribute "alt" not specified
                    <img src="siteimages/hm-spclpages-siri.png" border="0" />

    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 1229, Column 78: required attribute "alt" not specified
                    <img src="siteimages/hm-spclpages-sthirasti.png" border="0" />

    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 1231, Column 74: required attribute "alt" not specified
                    <img src="siteimages/hm-spclpages-enadu.png" border="0" />

    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 1233, Column 75: required attribute "alt" not specified
                    <img src="siteimages/hm-spclpages-etaram.png" border="0" />

    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 1235, Column 76: required attribute "alt" not specified
                    <img src="siteimages/hm-spclpages-ruchulu.png" border="0" />

    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 1245, Column 30: ID "adcontainer468" already defined
                        <div id="adcontainer468">

    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 611, Column 30: ID "adcontainer468" first defined here
                        <div id="adcontainer468">
  • Error Line 1246, Column 9: ID "ad468" already defined
    <ul id="ad468">

    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 671, Column 13: ID "ad468" first defined here
        <ul id="ad468">
  • Error Line 1255, Column 85: required attribute "alt" not specified
    …      <img src="images/hm-mag-sunday.gif" width="89" height="108" border="0" />

    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 1257, Column 87: required attribute "alt" not specified
    …    <img src="images/hm-mag-annadata.gif" width="89" height="108" border="0" />

    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 1259, Column 85: required attribute "alt" not specified
    …      <img src="images/hm-mag-vipula.gif" width="89" height="108" border="0" />

    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 1261, Column 86: required attribute "alt" not specified
    …     <img src="images/hm-mag-chatura.gif" width="89" height="108" border="0" />

    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 1275, Column 19: "DOCTYPE" declaration not allowed in instance
                    <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" …
  • Error Line 1276, 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 1301, Column 21: ID "hddlDistricts" already defined
            <select id="hddlDistricts" onchange="return hddlDistricts_onchange(this…

    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 542, Column 29: ID "hddlDistricts" first defined here
                    <select id="hddlDistricts" onchange="return hddlDistricts_oncha…
  • Error Line 1345, Column 66: required attribute "alt" not specified
                <img src="adimages/teluguvelugu300x50.gif" border="0"></a> </li>

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

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

  • Error Line 1345, Column 70: end tag for "img" omitted, but OMITTAG NO was specified
                <img src="adimages/teluguvelugu300x50.gif" border="0"></a> </li>

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

  • Info Line 1345, Column 13: start tag was here
                <img src="adimages/teluguvelugu300x50.gif" border="0"></a> </li>
  • Error Line 1353, Column 50: required attribute "alt" not specified
            <img src="siteimages/hm-editorials.gif" /></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 1367, Column 57: required attribute "alt" not specified
            <img src="siteimages/hm-editorials-bottom.gif" /></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 1372, Column 26: ID "adcontainer30050" already defined
                    <div id="adcontainer30050">

    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 1342, Column 26: ID "adcontainer30050" first defined here
                    <div id="adcontainer30050">
  • Error Line 1373, Column 13: ID "ad30050" already defined
        <ul id="ad30050">

    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 1343, Column 13: ID "ad30050" first defined here
        <ul id="ad30050">
  • Error Line 1377, Column 73: end tag for "param" omitted, but OMITTAG NO was specified
                    <param name='Movie' value="adimages/hairtransplant.swf">

    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 1377, Column 17: start tag was here
                    <param name='Movie' value="adimages/hairtransplant.swf">
  • Error Line 1378, Column 71: end tag for "param" omitted, but OMITTAG NO was specified
                    <param name='Src' value="adimages/hairtransplant.swf">

    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 1378, Column 17: start tag was here
                    <param name='Src' value="adimages/hairtransplant.swf">
  • Error Line 1381, Column 189: element "embed" undefined
    …media.com/shockwave/download/index.cgi?P1_Prod_Version=ShockwaveFlash"></embed>

    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 1385, Column 88: required attribute "alt" not specified
    …"adimages/Chilukuri_Real.gif" width="300" height="50" border="0" /></a></li>   

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

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

  • Error Line 1410, Column 49: ID "cmtb1" already defined
                                            <li id="cmtb1">

    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 1400, Column 49: ID "cmtb1" first defined here
                                            <li id="cmtb1">
  • Error Line 1415, Column 49: ID "cmtb2" already defined
                                            <li id="cmtb2">

    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 1405, Column 49: ID "cmtb2" first defined here
                                            <li id="cmtb2">
  • Error Line 1420, Column 49: ID "cmtb1" already defined
                                            <li id="cmtb1">

    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 1400, Column 49: ID "cmtb1" first defined here
                                            <li id="cmtb1">
  • Error Line 1425, Column 49: ID "cmtb2" already defined
                                            <li id="cmtb2">

    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 1405, Column 49: ID "cmtb2" first defined here
                                            <li id="cmtb2">
  • Error Line 1430, Column 49: ID "cmtb1" already defined
                                            <li id="cmtb1">

    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 1400, Column 49: ID "cmtb1" first defined here
                                            <li id="cmtb1">
  • Error Line 1435, Column 49: ID "cmtb2" already defined
                                            <li id="cmtb2">

    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 1405, Column 49: ID "cmtb2" first defined here
                                            <li id="cmtb2">
  • Error Line 1444, Column 37: ID "commtabnews" already defined
                                <ul id="commtabnews">

    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 1398, Column 37: ID "commtabnews" first defined here
                                <ul id="commtabnews">
  • Error Line 1446, Column 49: ID "cmtb1" already defined
                                            <li id="cmtb1">

    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 1400, Column 49: ID "cmtb1" first defined here
                                            <li id="cmtb1">
  • Error Line 1451, Column 49: ID "cmtb2" already defined
                                            <li id="cmtb2">

    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 1405, Column 49: ID "cmtb2" first defined here
                                            <li id="cmtb2">
  • Error Line 1456, Column 49: ID "cmtb1" already defined
                                            <li id="cmtb1">

    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 1400, Column 49: ID "cmtb1" first defined here
                                            <li id="cmtb1">
  • Error Line 1461, Column 49: ID "cmtb2" already defined
                                            <li id="cmtb2">

    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 1405, Column 49: ID "cmtb2" first defined here
                                            <li id="cmtb2">
  • Error Line 1466, Column 49: ID "cmtb1" already defined
                                            <li id="cmtb1">

    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 1400, Column 49: ID "cmtb1" first defined here
                                            <li id="cmtb1">
  • Error Line 1471, Column 49: ID "cmtb2" already defined
                                            <li id="cmtb2">

    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 1405, Column 49: ID "cmtb2" first defined here
                                            <li id="cmtb2">
  • Error Line 1476, Column 49: ID "cmtb1" already defined
                                            <li id="cmtb1">

    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 1400, Column 49: ID "cmtb1" first defined here
                                            <li id="cmtb1">
  • Error Line 1481, Column 49: ID "cmtb2" already defined
                                            <li id="cmtb2">

    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 1405, Column 49: ID "cmtb2" first defined here
                                            <li id="cmtb2">
  • Error Line 1513, Column 49: required attribute "alt" not specified
            <img src="siteimages/hm-photo-gal.gif" /></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 1515, Column 78: required attribute "alt" not specified
            <img src="images/hm-gal1.jpg" name="slide" width="177" height="169" />

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

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

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

  • Error Line 1539, Column 68: required attribute "alt" not specified
                    <img src="siteimages/hm-gal-actor.png" border="0" />

    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 1541, Column 70: required attribute "alt" not specified
                    <img src="siteimages/hm-gal-actress.png" border="0" />

    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 1543, Column 69: required attribute "alt" not specified
                    <img src="siteimages/hm-gal-movies.png" border="0" />

    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 1545, Column 69: required attribute "alt" not specified
                    <img src="siteimages/hm-gal-events.png" 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>.

  • Warning Line 1569, Column 76: cannot generate system identifier for general entity "id"
    …h="300" height="250" src="http://wb-a.foreca.com/?page=get&id=v1in&language=te"

    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 1569, Column 76: general entity "id" not defined and no default entity
    …h="300" height="250" src="http://wb-a.foreca.com/?page=get&id=v1in&language=te"

    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 1569, Column 78: reference not terminated by REFC delimiter
    …h="300" height="250" src="http://wb-a.foreca.com/?page=get&id=v1in&language=te"

    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 78: reference to external entity in attribute value
    …h="300" height="250" src="http://wb-a.foreca.com/?page=get&id=v1in&language=te"

    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 78: reference to entity "id" for which no system identifier could be generated
    …h="300" height="250" src="http://wb-a.foreca.com/?page=get&id=v1in&language=te"

    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 1569, Column 75: entity was defined here
    …h="300" height="250" src="http://wb-a.foreca.com/?page=get&id=v1in&language=te"
  • Warning Line 1569, Column 84: cannot generate system identifier for general entity "language"
    …h="300" height="250" src="http://wb-a.foreca.com/?page=get&id=v1in&language=te"

    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 1569, Column 84: general entity "language" not defined and no default entity
    …h="300" height="250" src="http://wb-a.foreca.com/?page=get&id=v1in&language=te"

    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 1569, Column 92: reference not terminated by REFC delimiter
    …h="300" height="250" src="http://wb-a.foreca.com/?page=get&id=v1in&language=te"

    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 92: reference to external entity in attribute value
    …h="300" height="250" src="http://wb-a.foreca.com/?page=get&id=v1in&language=te"

    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 92: reference to entity "language" for which no system identifier could be generated
    …h="300" height="250" src="http://wb-a.foreca.com/?page=get&id=v1in&language=te"

    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 1569, Column 83: entity was defined here
    …h="300" height="250" src="http://wb-a.foreca.com/?page=get&id=v1in&language=te"
  • Error Line 1570, Column 15: duplicate specification of attribute "width"
            width="300" height="250" marginwidth="0" marginheight="0" frameborder="…

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 1570, Column 28: duplicate specification of attribute "height"
            width="300" height="250" marginwidth="0" marginheight="0" frameborder="…

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 1571, Column 27: there is no attribute "allowtransparency"
            allowtransparency="true"></iframe>

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

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

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

  • Error Line 1576, Column 26: ID "adcontainer30050" already defined
                    <div id="adcontainer30050">

    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 1342, Column 26: ID "adcontainer30050" first defined here
                    <div id="adcontainer30050">
  • Error Line 1577, Column 13: ID "ad30050" already defined
        <ul id="ad30050">

    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 1343, Column 13: ID "ad30050" first defined here
        <ul id="ad30050">
  • Error Line 1581, Column 61: required attribute "alt" not specified
                <img src="adimages/alaya300-50.gif" border="0" /></a></li>

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

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

  • Error Line 1583, Column 62: required attribute "alt" not specified
                <img src="adimages/youth-300-60.gif" border="0" /></a></li>

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

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

  • Error Line 1587, Column 72: end tag for "param" omitted, but OMITTAG NO was specified
                    <param name='Movie' value="adimages/ruchulubanner.swf">

    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 1587, Column 17: start tag was here
                    <param name='Movie' value="adimages/ruchulubanner.swf">
  • Error Line 1588, Column 70: end tag for "param" omitted, but OMITTAG NO was specified
                    <param name='Src' value="adimages/ruchulubanner.swf">

    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 1588, Column 17: start tag was here
                    <param name='Src' value="adimages/ruchulubanner.swf">
  • Error Line 1591, Column 189: element "embed" undefined
    …media.com/shockwave/download/index.cgi?P1_Prod_Version=ShockwaveFlash"></embed>

    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 1596, Column 68: required attribute "alt" not specified
                <img src="adimages/pellipandiri300-50.gif" border="0" /></a></li>

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

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

  • Error Line 1628, Column 51: required attribute "alt" not specified
            <img src="siteimages/hm-usefullinks.gif" /></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 1655, Column 118: required attribute "alt" not specified
    …="adimages/eenadumobile1000-50.gif" width="968" height="50"/></td></tr></table>

    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 1668, Column 16: character "&" is the first character of a delimiter but occurred as data
    <span>Designed & Developed by <b>Eenadu Internet Division.</b></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.

Visitor Analysis

Daily Visitor
  • 93.333 visits

In Page Analysis