صحيفة يومية الكترونية اردنية عربية سياسية اقتصادية رياضية فنية جرائم وحوادث تهتم بالاخبار الاردنية والعربية والعالمية ...

watnnews.net
  • Domain Name
    watnnews.net
  • Favicon
  • Google Page Rank
    4
  • Alexa Rank
    #50219
  • Page Size
    88.3 KB
  • Ip Address
    74.208.133.56
  • Heading
    H1: 0, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    17 GIF, 23 JPG, 0 PNG

Website Meta Analysis

  • Title
    وطن نيوز | صحيفة الوطن الأردنية
  • Meta Keyword
    صحيفة,وطن,الاخبارية,الاردن,انتخابات,نيابية,2012,news,jordan
  • Meta Description
    صحيفة يومية الكترونية اردنية عربية سياسية اقتصادية رياضية فنية جرائم وحوادث تهتم بالاخبار الاردنية والعربية والعالمية

Technical Analysis

  • Webserver
    Microsoft-IIS/7.5
  • Ip Address
    74.208.133.56
  • Domain Age
    3 Years, 8 Months, 7 days.
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • cache-control: private
  • content-type: text/html; charset=windows-1256
  • server: Microsoft-IIS/7.5
  • x-aspnet-version: 2.0.50727
  • x-powered-by: ASP.NET
  • x-powered-by-plesk: PleskWin
  • date: Fri, 28 Jun 2013 08:32:48 GMT
  • content-length: 88140
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Domain Name: WATNNEWS.NET

Registration Date: 10-Oct-2009
Expiration Date: 10-Oct-2013

Status:ACTIVE


Name Servers:
ns51.1and1.com
ns52.1and1.com


Registrant Contact Details:
PrivacyProtect.org
Domain Admin ( email )
ID#10760, PO Box 16
Note - Visit PrivacyProtect.org to contact the domain owner/operator
Nobby Beach
Queensland,QLD 4218
AU
Tel. +45.36946676

Administrative Contact Details:
PrivacyProtect.org
Domain Admin ( email )
ID#10760, PO Box 16
Note - Visit PrivacyProtect.org to contact the domain owner/operator
Nobby Beach
Queensland,QLD 4218
AU
Tel. +45.36946676

Technical Contact Details:
PrivacyProtect.org
Domain Admin ( email )
ID#10760, PO Box 16
Note - Visit PrivacyProtect.org to contact the domain owner/operator
Nobby Beach
Queensland,QLD 4218
AU
Tel. +45.36946676

Billing Contact Details:
PrivacyProtect.org
Domain Admin ( email )
ID#10760, PO Box 16
Note - Visit PrivacyProtect.org to contact the domain owner/operator
Nobby Beach
Queensland,QLD 4218
AU
Tel. +45.36946676

DNS Analysis


DNS servers
ns51.1and1.com [217.160.80.164]
ns52.1and1.com [217.160.81.164]


DNS Records

Answer records
watnnews.net NS  ns52.1and1.com 86400s
watnnews.net MX
preference: 10
exchange: mx01.1and1.com
86400s
watnnews.net NS  ns51.1and1.com 86400s
watnnews.net MX
preference: 10
exchange: mx00.1and1.com
86400s
watnnews.net A 74.208.133.56 86400s
watnnews.net SOA
server: ns51.1and1.com
email: hostmaster@1and1.com
serial: 2012012402
refresh: 28800
retry: 7200
expire: 604800
minimum ttl: 86400
86400s

Authority records

Additional records

IP 74.208.133.56 Analysis

  • Country Code
    US
  • Country Code3
    USA
  • Country Name
    United States
  • City
    Wayne
  • Continent Code
    19087
  • Latitude
    610
  • Longitude
    504
  • #
    # Query terms are ambiguous. The query is assumed to be:
    # "n 74.208.133.56"
    #
    # Use "?" to get help.
    #

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

    NetRange: 74.208.0.0 - 74.208.255.255
    CIDR: 74.208.0.0/16
    OriginAS: AS8560
    NetName: 1AN1-NETWORK
    NetHandle: NET-74-208-0-0-1
    Parent: NET-74-0-0-0-0
    NetType: Direct Allocation
    Comment: For abuse issues, please use only abuse@1and1.com
    RegDate: 2006-11-22
    Updated: 2012-02-02
    Ref: http://whois.arin.net/rest/net/NET-74-208-0-0-1

    OrgName: 1&1 Internet Inc.
    OrgId: 11INT
    Address: 701 Lee Rd
    Address: Suite 300
    City: Chesterbrook
    StateProv: PA
    PostalCode: 19087
    Country: US
    RegDate: 2006-09-05
    Updated: 2011-10-12
    Comment: http://www.1and1.com
    Comment: For abuse issues, please use only abuse@schlund.de
    Ref: http://whois.arin.net/rest/org/11INT

    OrgAbuseHandle: 1AD-ARIN
    OrgAbuseName: 1and1 Abuse Department
    OrgAbusePhone: +1-877-206-4253
    OrgAbuseEmail: abuse@1and1.com
    OrgAbuseRef: http://whois.arin.net/rest/poc/1AD-ARIN

    OrgTechHandle: 1NO-ARIN
    OrgTechName: 1and1 ARIN Role
    OrgTechPhone: +1-610-560-1617
    OrgTechEmail: arin-role@oneandone.net
    OrgTechRef: http://whois.arin.net/rest/poc/1NO-ARIN

    RTechHandle: 1NO-ARIN
    RTechName: 1and1 ARIN Role
    RTechPhone: +1-610-560-1617
    RTechEmail: arin-role@oneandone.net
    RTechRef: http://whois.arin.net/rest/poc/1NO-ARIN

    RNOCHandle: 1NO-ARIN
    RNOCName: 1and1 ARIN Role
    RNOCPhone: +1-610-560-1617
    RNOCEmail: arin-role@oneandone.net
    RNOCRef: http://whois.arin.net/rest/poc/1NO-ARIN

    RAbuseHandle: 1AD-ARIN
    RAbuseName: 1and1 Abuse Department
    RAbusePhone: +1-877-206-4253
    RAbuseEmail: abuse@1and1.com
    RAbuseRef: http://whois.arin.net/rest/poc/1AD-ARIN

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 168 Errors
  • 116 Warnings
Ratio Text/Html
  • 0.7749894978885228
Message Error
  • Error Line 47, Column 218: document type does not allow element "noscript" here; assuming missing "object" start-tag
    …news.net"}; atrk ();</script><noscript><img src="https://d5nxst8fruw4z.cloudfr…
  • Error Line 49, Column 75: document type does not allow element "link" here
    …nk href="Theme/ArIE.css" rel="stylesheet" type="text/css" media="all" /></head>

    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 49, Column 82: end tag for "object" omitted, but OMITTAG NO was specified
    …nk href="Theme/ArIE.css" rel="stylesheet" type="text/css" media="all" /></head>

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

  • Info Line 47, Column 209: start tag was here
    …ain:"watnnews.net"}; atrk ();</script><noscript><img src="https://d5nxst8fruw4…
  • Error Line 74, Column 175: there is no attribute "valign"
    …><img src="Images/Space.gif" alt="Expand القرآن الكريم" valign="middle" /></td>

    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 316, Column 70: document type does not allow element "link" here
        <link href="Theme/all.min.css" rel="stylesheet" type="text/css" />

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

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

  • Error Line 320, Column 73: document type does not allow element "link" here
        <link href="Theme/TabControl.css" rel="stylesheet" type="text/css" />

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

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

  • Error Line 406, Column 74: document type does not allow element "center" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …tentPlaceHolder1_lblTopScript"><center><a id='TopImageLink' href='NewsDetails.…

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

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

  • Warning Line 406, Column 129: cannot generate system identifier for general entity "NewsID"
    …ink' href='NewsDetails.aspx?PageID=54&NewsID=74424'><img id='TopImage' src='Up…

    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 406, Column 129: general entity "NewsID" not defined and no default entity
    …ink' href='NewsDetails.aspx?PageID=54&NewsID=74424'><img id='TopImage' src='Up…

    This is usually a cascading error caused by 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 406, Column 135: reference not terminated by REFC delimiter
    …ref='NewsDetails.aspx?PageID=54&NewsID=74424'><img id='TopImage' src='Upload/I…

    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 406, Column 135: reference to external entity in attribute value
    …ref='NewsDetails.aspx?PageID=54&NewsID=74424'><img id='TopImage' src='Upload/I…

    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 406, Column 135: reference to entity "NewsID" for which no system identifier could be generated
    …ref='NewsDetails.aspx?PageID=54&NewsID=74424'><img id='TopImage' src='Upload/I…

    This is usually a cascading error caused by 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 406, Column 128: entity was defined here
    …Link' href='NewsDetails.aspx?PageID=54&NewsID=74424'><img id='TopImage' src='U…
  • Error Line 406, Column 366: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …ter><div id='TopTitle' class='WebPart'><a href=NewsDetails.aspx?PageID=54&News…

    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 406, Column 375: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …id='TopTitle' class='WebPart'><a href=NewsDetails.aspx?PageID=54&NewsID=74424 …
  • Error Line 406, Column 391: an attribute value must be a literal unless it contains only name characters
    …ass='WebPart'><a href=NewsDetails.aspx?PageID=54&NewsID=74424 class=News>مفاوض…

    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 406, Column 421: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ils.aspx?PageID=54&NewsID=74424 class=News>مفاوضات معقدة لاختيار رئيس الحكومة …
  • Error Line 406, Column 522: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    … المرشحين</a></div><div id='TopDetail'>وطـــــن نــيــوز ... <a class=MoreLink…

    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 406, Column 554: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …etail'>وطـــــن نــيــوز ... <a class=MoreLinkNavigation href=NewsDetails.aspx…
  • Error Line 406, Column 578: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    … ... <a class=MoreLinkNavigation href=NewsDetails.aspx?PageID=54&NewsID=74424 …
  • Error Line 406, Column 594: an attribute value must be a literal unless it contains only name characters
    …reLinkNavigation href=NewsDetails.aspx?PageID=54&NewsID=74424 >المزيد</a></div…

    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 406, Column 675: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …=74424 >المزيد</a></div><div id='MainNews' style='display: none'>0</div></span>

    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 411, Column 29: there is no attribute "id"
                    <marquee id="Marq" scrolldelay="30" scrollamount="1" truespeed …

    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 411, Column 48: there is no attribute "scrolldelay"
    …       <marquee id="Marq" scrolldelay="30" scrollamount="1" truespeed directio…

    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 411, Column 66: there is no attribute "scrollamount"
    …marquee id="Marq" scrolldelay="30" scrollamount="1" truespeed direction="right"

    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 411, Column 80: "truespeed" is not a member of a group specified for any attribute
    …marquee id="Marq" scrolldelay="30" scrollamount="1" truespeed direction="right"
  • Error Line 411, Column 90: there is no attribute "direction"
    …marquee id="Marq" scrolldelay="30" scrollamount="1" truespeed direction="right"

    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 412, Column 33: there is no attribute "onmouseover"
                        onmouseover="stop()" onmouseout="start()">

    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 412, Column 53: there is no attribute "onmouseout"
                        onmouseover="stop()" onmouseout="start()">

    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 412, Column 62: element "marquee" undefined
                        onmouseover="stop()" onmouseout="start()">

    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 414, Column 162: there is no attribute "runat"
    …ize="3"><img id="imgBannerNews" runat="server" src="Images/Flag.gif" alt="" st…

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

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

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

  • Warning Line 415, Column 90: reference not terminated by REFC delimiter
    …          <a class="BannerNews" href="NewsDetails.aspx?PageID=29&NewsID=74433">

    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 415, Column 90: reference to external entity in attribute value
    …          <a class="BannerNews" href="NewsDetails.aspx?PageID=29&NewsID=74433">

    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 415, Column 90: reference to entity "NewsID" for which no system identifier could be generated
    …          <a class="BannerNews" href="NewsDetails.aspx?PageID=29&NewsID=74433">

    This is usually a cascading error caused by 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 406, Column 128: entity was defined here
    …Link' href='NewsDetails.aspx?PageID=54&NewsID=74424'><img id='TopImage' src='U…
  • Error Line 418, Column 141: ID "imgBannerNews" already defined
    …ont color="#033858" size="3"><img id="imgBannerNews" runat="server" src="Image…

    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 414, Column 141: ID "imgBannerNews" first defined here
    …ont color="#033858" size="3"><img id="imgBannerNews" runat="server" src="Image…
  • Warning Line 419, Column 89: reference not terminated by REFC delimiter
    …           <a class="BannerNews" href="NewsDetails.aspx?PageID=5&NewsID=74432">

    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 419, Column 89: reference to external entity in attribute value
    …           <a class="BannerNews" href="NewsDetails.aspx?PageID=5&NewsID=74432">

    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 419, Column 89: reference to entity "NewsID" for which no system identifier could be generated
    …           <a class="BannerNews" href="NewsDetails.aspx?PageID=5&NewsID=74432">

    This is usually a cascading error caused by 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 406, Column 128: entity was defined here
    …Link' href='NewsDetails.aspx?PageID=54&NewsID=74424'><img id='TopImage' src='U…
  • Error Line 422, Column 141: ID "imgBannerNews" already defined
    …ont color="#033858" size="3"><img id="imgBannerNews" runat="server" src="Image…

    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 414, Column 141: ID "imgBannerNews" first defined here
    …ont color="#033858" size="3"><img id="imgBannerNews" runat="server" src="Image…
  • Warning Line 423, Column 89: reference not terminated by REFC delimiter
    …           <a class="BannerNews" href="NewsDetails.aspx?PageID=3&NewsID=74431">

    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 423, Column 89: reference to external entity in attribute value
    …           <a class="BannerNews" href="NewsDetails.aspx?PageID=3&NewsID=74431">

    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 423, Column 89: reference to entity "NewsID" for which no system identifier could be generated
    …           <a class="BannerNews" href="NewsDetails.aspx?PageID=3&NewsID=74431">

    This is usually a cascading error caused by 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 406, Column 128: entity was defined here
    …Link' href='NewsDetails.aspx?PageID=54&NewsID=74424'><img id='TopImage' src='U…
  • Error Line 426, Column 141: ID "imgBannerNews" already defined
    …ont color="#033858" size="3"><img id="imgBannerNews" runat="server" src="Image…

    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 414, Column 141: ID "imgBannerNews" first defined here
    …ont color="#033858" size="3"><img id="imgBannerNews" runat="server" src="Image…
  • Warning Line 427, Column 90: reference not terminated by REFC delimiter
    …          <a class="BannerNews" href="NewsDetails.aspx?PageID=54&NewsID=74429">

    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 427, Column 90: reference to external entity in attribute value
    …          <a class="BannerNews" href="NewsDetails.aspx?PageID=54&NewsID=74429">

    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 427, Column 90: reference to entity "NewsID" for which no system identifier could be generated
    …          <a class="BannerNews" href="NewsDetails.aspx?PageID=54&NewsID=74429">

    This is usually a cascading error caused by 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 406, Column 128: entity was defined here
    …Link' href='NewsDetails.aspx?PageID=54&NewsID=74424'><img id='TopImage' src='U…
  • Error Line 430, Column 141: ID "imgBannerNews" already defined
    …ont color="#033858" size="3"><img id="imgBannerNews" runat="server" src="Image…

    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 414, Column 141: ID "imgBannerNews" first defined here
    …ont color="#033858" size="3"><img id="imgBannerNews" runat="server" src="Image…
  • Warning Line 431, Column 89: reference not terminated by REFC delimiter
    …           <a class="BannerNews" href="NewsDetails.aspx?PageID=3&NewsID=74428">

    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 89: reference to external entity in attribute value
    …           <a class="BannerNews" href="NewsDetails.aspx?PageID=3&NewsID=74428">

    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 89: reference to entity "NewsID" for which no system identifier could be generated
    …           <a class="BannerNews" href="NewsDetails.aspx?PageID=3&NewsID=74428">

    This is usually a cascading error caused by 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 406, Column 128: entity was defined here
    …Link' href='NewsDetails.aspx?PageID=54&NewsID=74424'><img id='TopImage' src='U…
  • Error Line 434, Column 141: ID "imgBannerNews" already defined
    …ont color="#033858" size="3"><img id="imgBannerNews" runat="server" src="Image…

    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 414, Column 141: ID "imgBannerNews" first defined here
    …ont color="#033858" size="3"><img id="imgBannerNews" runat="server" src="Image…
  • Warning Line 435, Column 89: reference not terminated by REFC delimiter
    …           <a class="BannerNews" href="NewsDetails.aspx?PageID=3&NewsID=74426">

    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 89: reference to external entity in attribute value
    …           <a class="BannerNews" href="NewsDetails.aspx?PageID=3&NewsID=74426">

    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 89: reference to entity "NewsID" for which no system identifier could be generated
    …           <a class="BannerNews" href="NewsDetails.aspx?PageID=3&NewsID=74426">

    This is usually a cascading error caused by 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 406, Column 128: entity was defined here
    …Link' href='NewsDetails.aspx?PageID=54&NewsID=74424'><img id='TopImage' src='U…
  • Error Line 438, Column 141: ID "imgBannerNews" already defined
    …ont color="#033858" size="3"><img id="imgBannerNews" runat="server" src="Image…

    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 414, Column 141: ID "imgBannerNews" first defined here
    …ont color="#033858" size="3"><img id="imgBannerNews" runat="server" src="Image…
  • Warning Line 439, Column 89: reference not terminated by REFC delimiter
    …           <a class="BannerNews" href="NewsDetails.aspx?PageID=3&NewsID=74425">

    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 439, Column 89: reference to external entity in attribute value
    …           <a class="BannerNews" href="NewsDetails.aspx?PageID=3&NewsID=74425">

    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 439, Column 89: reference to entity "NewsID" for which no system identifier could be generated
    …           <a class="BannerNews" href="NewsDetails.aspx?PageID=3&NewsID=74425">

    This is usually a cascading error caused by 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 406, Column 128: entity was defined here
    …Link' href='NewsDetails.aspx?PageID=54&NewsID=74424'><img id='TopImage' src='U…
  • Error Line 442, Column 141: ID "imgBannerNews" already defined
    …ont color="#033858" size="3"><img id="imgBannerNews" runat="server" src="Image…

    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 414, Column 141: ID "imgBannerNews" first defined here
    …ont color="#033858" size="3"><img id="imgBannerNews" runat="server" src="Image…
  • Warning Line 443, Column 90: reference not terminated by REFC delimiter
    …          <a class="BannerNews" href="NewsDetails.aspx?PageID=54&NewsID=74424">

    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 443, Column 90: reference to external entity in attribute value
    …          <a class="BannerNews" href="NewsDetails.aspx?PageID=54&NewsID=74424">

    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 443, Column 90: reference to entity "NewsID" for which no system identifier could be generated
    …          <a class="BannerNews" href="NewsDetails.aspx?PageID=54&NewsID=74424">

    This is usually a cascading error caused by 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 406, Column 128: entity was defined here
    …Link' href='NewsDetails.aspx?PageID=54&NewsID=74424'><img id='TopImage' src='U…
  • Error Line 446, Column 141: ID "imgBannerNews" already defined
    …ont color="#033858" size="3"><img id="imgBannerNews" runat="server" src="Image…

    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 414, Column 141: ID "imgBannerNews" first defined here
    …ont color="#033858" size="3"><img id="imgBannerNews" runat="server" src="Image…
  • Warning Line 447, Column 90: reference not terminated by REFC delimiter
    …          <a class="BannerNews" href="NewsDetails.aspx?PageID=56&NewsID=74423">

    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 447, Column 90: reference to external entity in attribute value
    …          <a class="BannerNews" href="NewsDetails.aspx?PageID=56&NewsID=74423">

    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 447, Column 90: reference to entity "NewsID" for which no system identifier could be generated
    …          <a class="BannerNews" href="NewsDetails.aspx?PageID=56&NewsID=74423">

    This is usually a cascading error caused by 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 406, Column 128: entity was defined here
    …Link' href='NewsDetails.aspx?PageID=54&NewsID=74424'><img id='TopImage' src='U…
  • Error Line 450, Column 141: ID "imgBannerNews" already defined
    …ont color="#033858" size="3"><img id="imgBannerNews" runat="server" src="Image…

    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 414, Column 141: ID "imgBannerNews" first defined here
    …ont color="#033858" size="3"><img id="imgBannerNews" runat="server" src="Image…
  • Warning Line 451, Column 90: reference not terminated by REFC delimiter
    …          <a class="BannerNews" href="NewsDetails.aspx?PageID=54&NewsID=74422">

    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 451, Column 90: reference to external entity in attribute value
    …          <a class="BannerNews" href="NewsDetails.aspx?PageID=54&NewsID=74422">

    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 451, Column 90: reference to entity "NewsID" for which no system identifier could be generated
    …          <a class="BannerNews" href="NewsDetails.aspx?PageID=54&NewsID=74422">

    This is usually a cascading error caused by 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 406, Column 128: entity was defined here
    …Link' href='NewsDetails.aspx?PageID=54&NewsID=74424'><img id='TopImage' src='U…
  • Error Line 457, Column 253: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …#ffffff'; ContinueLoop('0');" onclick=window.location='NewsDetails.aspx?PageID…
  • Error Line 457, Column 268: an attribute specification must start with a name or name token
    …nueLoop('0');" onclick=window.location='NewsDetails.aspx?PageID=54&NewsID=7442…

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

  • Error Line 457, Column 268: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …nueLoop('0');" onclick=window.location='NewsDetails.aspx?PageID=54&NewsID=7442…

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

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

  • Warning Line 457, Column 303: reference not terminated by REFC delimiter
    …ion='NewsDetails.aspx?PageID=54&NewsID=74424' onmouseover="this.style.backgrou…

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

  • Error Line 457, Column 303: reference to entity "NewsID" for which no system identifier could be generated
    …ion='NewsDetails.aspx?PageID=54&NewsID=74424' onmouseover="this.style.backgrou…

    This is usually a cascading error caused by 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 406, Column 128: entity was defined here
    …Link' href='NewsDetails.aspx?PageID=54&NewsID=74424'><img id='TopImage' src='U…
  • Warning Line 457, Column 410: reference not terminated by REFC delimiter
    …age('NewsDetails.aspx?PageID=54&NewsID=74424','Upload/Images/250x300/News-1-74…

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

  • Error Line 457, Column 410: reference to entity "NewsID" for which no system identifier could be generated
    …age('NewsDetails.aspx?PageID=54&NewsID=74424','Upload/Images/250x300/News-1-74…

    This is usually a cascading error caused by 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 406, Column 128: entity was defined here
    …Link' href='NewsDetails.aspx?PageID=54&NewsID=74424'><img id='TopImage' src='U…
  • Warning Line 457, Column 587: reference not terminated by REFC delimiter
    …ref='NewsDetails.aspx?PageID=54&NewsID=74424'><img id='Image-0' src='Upload/Im…

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

  • Warning Line 457, Column 587: reference to external entity in attribute value
    …ref='NewsDetails.aspx?PageID=54&NewsID=74424'><img id='Image-0' src='Upload/Im…

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

  • Error Line 457, Column 587: reference to entity "NewsID" for which no system identifier could be generated
    …ref='NewsDetails.aspx?PageID=54&NewsID=74424'><img id='Image-0' src='Upload/Im…

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

  • Info Line 406, Column 128: entity was defined here
    …Link' href='NewsDetails.aspx?PageID=54&NewsID=74424'><img id='TopImage' src='U…
  • Error Line 457, Column 773: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …le-0' style='margin-top: 5px'><a href=NewsDetails.aspx?PageID=54&NewsID=74424 …
  • Error Line 457, Column 789: an attribute value must be a literal unless it contains only name characters
    …gin-top: 5px'><a href=NewsDetails.aspx?PageID=54&NewsID=74424 class='News'><a …

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

  • Error Line 457, Column 834: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …=54&NewsID=74424 class='News'><a href=NewsDetails.aspx?PageID=54&NewsID=74424 …
  • Error Line 457, Column 850: an attribute value must be a literal unless it contains only name characters
    … class='News'><a href=NewsDetails.aspx?PageID=54&NewsID=74424 class=News>مفاوض…

    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 457, Column 880: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ils.aspx?PageID=54&NewsID=74424 class=News>مفاوضات معقدة لاختيار رئيس الحكومة …
  • Error Line 457, Column 884: document type does not allow element "a" here; missing one of "object", "span", "bdo", "applet", "iframe", "tt", "i", "b", "u", "s", "strike", "big", "small", "font", "em", "strong", "dfn", "code", "q", "samp", "kbd", "var", "cite", "abbr", "acronym", "sub", "sup", "label", "ins", "del" start-tag
    …aspx?PageID=54&NewsID=74424 class=News>مفاوضات معقدة لاختيار رئيس الحكومة .. و…

    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 457, Column 1044: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …il-0' >وطـــــن نــيــوز ... <a class=MoreLinkNavigation href=NewsDetails.aspx…
  • Error Line 457, Column 1068: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    … ... <a class=MoreLinkNavigation href=NewsDetails.aspx?PageID=54&NewsID=74424 …
  • Error Line 457, Column 1084: an attribute value must be a literal unless it contains only name characters
    …reLinkNavigation href=NewsDetails.aspx?PageID=54&NewsID=74424 >المزيد</a></div…

    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 457, Column 1140: ID "divHighLight" already defined
    …74424 >المزيد</a></div></div><div id='divHighLight' style='margin-Bottom: 4px;…

    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 457, Column 73: ID "divHighLight" first defined here
    …ntentPlaceHolder1_lblScript"><div id='divHighLight' style='margin-Bottom: 4px;…
  • Error Line 457, Column 1320: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …#ffffff'; ContinueLoop('1');" onclick=window.location='NewsDetails.aspx?PageID…
  • Error Line 457, Column 1335: an attribute specification must start with a name or name token
    …nueLoop('1');" onclick=window.location='NewsDetails.aspx?PageID=54&NewsID=7442…

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

  • Error Line 457, Column 1335: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …nueLoop('1');" onclick=window.location='NewsDetails.aspx?PageID=54&NewsID=7442…

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

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

  • Warning Line 457, Column 1370: reference not terminated by REFC delimiter
    …ion='NewsDetails.aspx?PageID=54&NewsID=74422' onmouseover="this.style.backgrou…

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

  • Error Line 457, Column 1370: reference to entity "NewsID" for which no system identifier could be generated
    …ion='NewsDetails.aspx?PageID=54&NewsID=74422' onmouseover="this.style.backgrou…

    This is usually a cascading error caused by 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 406, Column 128: entity was defined here
    …Link' href='NewsDetails.aspx?PageID=54&NewsID=74424'><img id='TopImage' src='U…
  • Warning Line 457, Column 1477: reference not terminated by REFC delimiter
    …age('NewsDetails.aspx?PageID=54&NewsID=74422','Upload/Images/250x300/News-1-74…

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

  • Error Line 457, Column 1477: reference to entity "NewsID" for which no system identifier could be generated
    …age('NewsDetails.aspx?PageID=54&NewsID=74422','Upload/Images/250x300/News-1-74…

    This is usually a cascading error caused by 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 406, Column 128: entity was defined here
    …Link' href='NewsDetails.aspx?PageID=54&NewsID=74424'><img id='TopImage' src='U…
  • Warning Line 457, Column 1654: reference not terminated by REFC delimiter
    …ref='NewsDetails.aspx?PageID=54&NewsID=74422'><img id='Image-1' src='Upload/Im…

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

  • Warning Line 457, Column 1654: reference to external entity in attribute value
    …ref='NewsDetails.aspx?PageID=54&NewsID=74422'><img id='Image-1' src='Upload/Im…

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

  • Error Line 457, Column 1654: reference to entity "NewsID" for which no system identifier could be generated
    …ref='NewsDetails.aspx?PageID=54&NewsID=74422'><img id='Image-1' src='Upload/Im…

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

  • Info Line 406, Column 128: entity was defined here
    …Link' href='NewsDetails.aspx?PageID=54&NewsID=74424'><img id='TopImage' src='U…
  • Error Line 457, Column 1840: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …le-1' style='margin-top: 5px'><a href=NewsDetails.aspx?PageID=54&NewsID=74422 …
  • Error Line 457, Column 1856: an attribute value must be a literal unless it contains only name characters
    …gin-top: 5px'><a href=NewsDetails.aspx?PageID=54&NewsID=74422 class='News'><a …

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

  • Error Line 457, Column 1901: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …=54&NewsID=74422 class='News'><a href=NewsDetails.aspx?PageID=54&NewsID=74422 …
  • Error Line 457, Column 1917: an attribute value must be a literal unless it contains only name characters
    … class='News'><a href=NewsDetails.aspx?PageID=54&NewsID=74422 class=News>بوتين…

    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 457, Column 1947: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ils.aspx?PageID=54&NewsID=74422 class=News>بوتين والملك عبدلله الثاني: مقابلة …
  • Error Line 457, Column 1951: document type does not allow element "a" here; missing one of "object", "span", "bdo", "applet", "iframe", "tt", "i", "b", "u", "s", "strike", "big", "small", "font", "em", "strong", "dfn", "code", "q", "samp", "kbd", "var", "cite", "abbr", "acronym", "sub", "sup", "label", "ins", "del" start-tag
    …aspx?PageID=54&NewsID=74422 class=News>بوتين والملك عبدلله الثاني: مقابلة خاصة…

    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 457, Column 2127: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …il-1' >وطـــــن نــيــوز ... <a class=MoreLinkNavigation href=NewsDetails.aspx…
  • Error Line 457, Column 2151: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    … ... <a class=MoreLinkNavigation href=NewsDetails.aspx?PageID=54&NewsID=74422 …
  • Error Line 457, Column 2167: an attribute value must be a literal unless it contains only name characters
    …reLinkNavigation href=NewsDetails.aspx?PageID=54&NewsID=74422 >المزيد</a></div…

    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 457, Column 2223: ID "divHighLight" already defined
    …74422 >المزيد</a></div></div><div id='divHighLight' style='margin-Bottom: 4px;…

    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 457, Column 73: ID "divHighLight" first defined here
    …ntentPlaceHolder1_lblScript"><div id='divHighLight' style='margin-Bottom: 4px;…
  • Error Line 457, Column 2403: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …#ffffff'; ContinueLoop('2');" onclick=window.location='NewsDetails.aspx?PageID…
  • Error Line 457, Column 2418: an attribute specification must start with a name or name token
    …nueLoop('2');" onclick=window.location='NewsDetails.aspx?PageID=56&NewsID=7442…

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

  • Error Line 457, Column 2418: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …nueLoop('2');" onclick=window.location='NewsDetails.aspx?PageID=56&NewsID=7442…

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

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

  • Warning Line 457, Column 2453: reference not terminated by REFC delimiter
    …ion='NewsDetails.aspx?PageID=56&NewsID=74421' onmouseover="this.style.backgrou…

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

  • Error Line 457, Column 2453: reference to entity "NewsID" for which no system identifier could be generated
    …ion='NewsDetails.aspx?PageID=56&NewsID=74421' onmouseover="this.style.backgrou…

    This is usually a cascading error caused by 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 406, Column 128: entity was defined here
    …Link' href='NewsDetails.aspx?PageID=54&NewsID=74424'><img id='TopImage' src='U…
  • Warning Line 457, Column 2560: reference not terminated by REFC delimiter
    …age('NewsDetails.aspx?PageID=56&NewsID=74421','Upload/Images/250x300/News-1-74…

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

  • Error Line 457, Column 2560: reference to entity "NewsID" for which no system identifier could be generated
    …age('NewsDetails.aspx?PageID=56&NewsID=74421','Upload/Images/250x300/News-1-74…

    This is usually a cascading error caused by 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 406, Column 128: entity was defined here
    …Link' href='NewsDetails.aspx?PageID=54&NewsID=74424'><img id='TopImage' src='U…
  • Warning Line 457, Column 2737: reference not terminated by REFC delimiter
    …ref='NewsDetails.aspx?PageID=56&NewsID=74421'><img id='Image-2' src='Upload/Im…

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

  • Warning Line 457, Column 2737: reference to external entity in attribute value
    …ref='NewsDetails.aspx?PageID=56&NewsID=74421'><img id='Image-2' src='Upload/Im…

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

  • Error Line 457, Column 2737: reference to entity "NewsID" for which no system identifier could be generated
    …ref='NewsDetails.aspx?PageID=56&NewsID=74421'><img id='Image-2' src='Upload/Im…

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

  • Info Line 406, Column 128: entity was defined here
    …Link' href='NewsDetails.aspx?PageID=54&NewsID=74424'><img id='TopImage' src='U…
  • Error Line 457, Column 2923: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …le-2' style='margin-top: 5px'><a href=NewsDetails.aspx?PageID=56&NewsID=74421 …
  • Error Line 457, Column 2939: an attribute value must be a literal unless it contains only name characters
    …gin-top: 5px'><a href=NewsDetails.aspx?PageID=56&NewsID=74421 class='News'><a …

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

  • Error Line 457, Column 2984: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …=56&NewsID=74421 class='News'><a href=NewsDetails.aspx?PageID=56&NewsID=74421 …
  • Error Line 457, Column 3000: an attribute value must be a literal unless it contains only name characters
    … class='News'><a href=NewsDetails.aspx?PageID=56&NewsID=74421 class=News>كيف إ…

    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 457, Column 3030: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ils.aspx?PageID=56&NewsID=74421 class=News>كيف إستقبل بشار الأسد ضيوفه الأردني…
  • Error Line 457, Column 3034: document type does not allow element "a" here; missing one of "object", "span", "bdo", "applet", "iframe", "tt", "i", "b", "u", "s", "strike", "big", "small", "font", "em", "strong", "dfn", "code", "q", "samp", "kbd", "var", "cite", "abbr", "acronym", "sub", "sup", "label", "ins", "del" start-tag
    …aspx?PageID=56&NewsID=74421 class=News>كيف إستقبل بشار الأسد ضيوفه الأردنيين؟.…

    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 457, Column 3203: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …il-2' >وطـــــن نــيــوز ... <a class=MoreLinkNavigation href=NewsDetails.aspx…
  • Error Line 457, Column 3227: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    … ... <a class=MoreLinkNavigation href=NewsDetails.aspx?PageID=56&NewsID=74421 …
  • Error Line 457, Column 3243: an attribute value must be a literal unless it contains only name characters
    …reLinkNavigation href=NewsDetails.aspx?PageID=56&NewsID=74421 >المزيد</a></div…

    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 457, Column 3299: ID "divHighLight" already defined
    …74421 >المزيد</a></div></div><div id='divHighLight' style='margin-Bottom: 4px;…

    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 457, Column 73: ID "divHighLight" first defined here
    …ntentPlaceHolder1_lblScript"><div id='divHighLight' style='margin-Bottom: 4px;…
  • Error Line 457, Column 3479: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …#ffffff'; ContinueLoop('3');" onclick=window.location='NewsDetails.aspx?PageID…
  • Error Line 457, Column 3494: an attribute specification must start with a name or name token
    …nueLoop('3');" onclick=window.location='NewsDetails.aspx?PageID=56&NewsID=7441…

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

  • Error Line 457, Column 3494: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …nueLoop('3');" onclick=window.location='NewsDetails.aspx?PageID=56&NewsID=7441…

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

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

  • Warning Line 457, Column 3529: reference not terminated by REFC delimiter
    …ion='NewsDetails.aspx?PageID=56&NewsID=74412' onmouseover="this.style.backgrou…

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

  • Error Line 457, Column 3529: reference to entity "NewsID" for which no system identifier could be generated
    …ion='NewsDetails.aspx?PageID=56&NewsID=74412' onmouseover="this.style.backgrou…

    This is usually a cascading error caused by 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 406, Column 128: entity was defined here
    …Link' href='NewsDetails.aspx?PageID=54&NewsID=74424'><img id='TopImage' src='U…
  • Warning Line 457, Column 3636: reference not terminated by REFC delimiter
    …age('NewsDetails.aspx?PageID=56&NewsID=74412','Upload/Images/250x300/News-1-74…

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

  • Error Line 457, Column 3636: reference to entity "NewsID" for which no system identifier could be generated
    …age('NewsDetails.aspx?PageID=56&NewsID=74412','Upload/Images/250x300/News-1-74…

    This is usually a cascading error caused by 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 406, Column 128: entity was defined here
    …Link' href='NewsDetails.aspx?PageID=54&NewsID=74424'><img id='TopImage' src='U…
  • Warning Line 457, Column 3813: reference not terminated by REFC delimiter
    …ref='NewsDetails.aspx?PageID=56&NewsID=74412'><img id='Image-3' src='Upload/Im…

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

  • Warning Line 457, Column 3813: reference to external entity in attribute value
    …ref='NewsDetails.aspx?PageID=56&NewsID=74412'><img id='Image-3' src='Upload/Im…

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

  • Error Line 457, Column 3813: reference to entity "NewsID" for which no system identifier could be generated
    …ref='NewsDetails.aspx?PageID=56&NewsID=74412'><img id='Image-3' src='Upload/Im…

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

  • Info Line 406, Column 128: entity was defined here
    …Link' href='NewsDetails.aspx?PageID=54&NewsID=74424'><img id='TopImage' src='U…
  • Error Line 457, Column 3999: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …le-3' style='margin-top: 5px'><a href=NewsDetails.aspx?PageID=56&NewsID=74412 …
  • Error Line 457, Column 4015: an attribute value must be a literal unless it contains only name characters
    …gin-top: 5px'><a href=NewsDetails.aspx?PageID=56&NewsID=74412 class='News'><a …

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

  • Error Line 457, Column 4060: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …=56&NewsID=74412 class='News'><a href=NewsDetails.aspx?PageID=56&NewsID=74412 …
  • Error Line 457, Column 4076: an attribute value must be a literal unless it contains only name characters
    … class='News'><a href=NewsDetails.aspx?PageID=56&NewsID=74412 class=News>البطا…

    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 457, Column 4106: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ils.aspx?PageID=56&NewsID=74412 class=News>البطاينة : رفع اسعار الكهرباء قريبا…
  • Error Line 457, Column 4110: document type does not allow element "a" here; missing one of "object", "span", "bdo", "applet", "iframe", "tt", "i", "b", "u", "s", "strike", "big", "small", "font", "em", "strong", "dfn", "code", "q", "samp", "kbd", "var", "cite", "abbr", "acronym", "sub", "sup", "label", "ins", "del" start-tag
    …aspx?PageID=56&NewsID=74412 class=News>البطاينة : رفع اسعار الكهرباء قريبا</a>…

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

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

  • Error Line 457, Column 4221: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    … 8px' id='TopDetail-3' > ... <a class=MoreLinkNavigation href=NewsDetails.aspx…
  • Error Line 457, Column 4245: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    … ... <a class=MoreLinkNavigation href=NewsDetails.aspx?PageID=56&NewsID=74412 …
  • Error Line 457, Column 4261: an attribute value must be a literal unless it contains only name characters
    …reLinkNavigation href=NewsDetails.aspx?PageID=56&NewsID=74412 >المزيد</a></div…

    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.

  • Warning Line 485, Column 63: reference not terminated by REFC delimiter
    …            <a href="NewsDetails.aspx?PageID=29&NewsID=74433" target="_parent">

    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 485, Column 63: reference to external entity in attribute value
    …            <a href="NewsDetails.aspx?PageID=29&NewsID=74433" target="_parent">

    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 485, Column 63: reference to entity "NewsID" for which no system identifier could be generated
    …            <a href="NewsDetails.aspx?PageID=29&NewsID=74433" target="_parent">

    This is usually a cascading error caused by 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 406, Column 128: entity was defined here
    …Link' href='NewsDetails.aspx?PageID=54&NewsID=74424'><img id='TopImage' src='U…
  • Warning Line 488, Column 63: reference not terminated by REFC delimiter
    …            <a href="NewsDetails.aspx?PageID=29&NewsID=74433" target="_parent">

    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 488, Column 63: reference to external entity in attribute value
    …            <a href="NewsDetails.aspx?PageID=29&NewsID=74433" target="_parent">

    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 488, Column 63: reference to entity "NewsID" for which no system identifier could be generated
    …            <a href="NewsDetails.aspx?PageID=29&NewsID=74433" target="_parent">

    This is usually a cascading error caused by 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 406, Column 128: entity was defined here
    …Link' href='NewsDetails.aspx?PageID=54&NewsID=74424'><img id='TopImage' src='U…
  • Warning Line 493, Column 62: reference not terminated by REFC delimiter
    …             <a href="NewsDetails.aspx?PageID=3&NewsID=74431" target="_parent">

    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 493, Column 62: reference to external entity in attribute value
    …             <a href="NewsDetails.aspx?PageID=3&NewsID=74431" target="_parent">

    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 493, Column 62: reference to entity "NewsID" for which no system identifier could be generated
    …             <a href="NewsDetails.aspx?PageID=3&NewsID=74431" target="_parent">

    This is usually a cascading error caused by 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 406, Column 128: entity was defined here
    …Link' href='NewsDetails.aspx?PageID=54&NewsID=74424'><img id='TopImage' src='U…
  • Warning Line 496, Column 62: reference not terminated by REFC delimiter
    …             <a href="NewsDetails.aspx?PageID=3&NewsID=74431" target="_parent">

    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 496, Column 62: reference to external entity in attribute value
    …             <a href="NewsDetails.aspx?PageID=3&NewsID=74431" target="_parent">

    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 496, Column 62: reference to entity "NewsID" for which no system identifier could be generated
    …             <a href="NewsDetails.aspx?PageID=3&NewsID=74431" target="_parent">

    This is usually a cascading error caused by 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 406, Column 128: entity was defined here
    …Link' href='NewsDetails.aspx?PageID=54&NewsID=74424'><img id='TopImage' src='U…
  • Warning Line 501, Column 63: reference not terminated by REFC delimiter
    …            <a href="NewsDetails.aspx?PageID=54&NewsID=74429" target="_parent">

    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 501, Column 63: reference to external entity in attribute value
    …            <a href="NewsDetails.aspx?PageID=54&NewsID=74429" target="_parent">

    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 501, Column 63: reference to entity "NewsID" for which no system identifier could be generated
    …            <a href="NewsDetails.aspx?PageID=54&NewsID=74429" target="_parent">

    This is usually a cascading error caused by 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 406, Column 128: entity was defined here
    …Link' href='NewsDetails.aspx?PageID=54&NewsID=74424'><img id='TopImage' src='U…
  • Warning Line 504, Column 63: reference not terminated by REFC delimiter
    …            <a href="NewsDetails.aspx?PageID=54&NewsID=74429" target="_parent">

    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 504, Column 63: reference to external entity in attribute value
    …            <a href="NewsDetails.aspx?PageID=54&NewsID=74429" target="_parent">

    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 504, Column 63: reference to entity "NewsID" for which no system identifier could be generated
    …            <a href="NewsDetails.aspx?PageID=54&NewsID=74429" target="_parent">

    This is usually a cascading error caused by 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 406, Column 128: entity was defined here
    …Link' href='NewsDetails.aspx?PageID=54&NewsID=74424'><img id='TopImage' src='U…
  • Warning Line 509, Column 62: reference not terminated by REFC delimiter
    …             <a href="NewsDetails.aspx?PageID=3&NewsID=74426" target="_parent">

    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 509, Column 62: reference to external entity in attribute value
    …             <a href="NewsDetails.aspx?PageID=3&NewsID=74426" target="_parent">

    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 509, Column 62: reference to entity "NewsID" for which no system identifier could be generated
    …             <a href="NewsDetails.aspx?PageID=3&NewsID=74426" target="_parent">

    This is usually a cascading error caused by 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 406, Column 128: entity was defined here
    …Link' href='NewsDetails.aspx?PageID=54&NewsID=74424'><img id='TopImage' src='U…
  • Warning Line 512, Column 62: reference not terminated by REFC delimiter
    …             <a href="NewsDetails.aspx?PageID=3&NewsID=74426" target="_parent">

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

  • Warning Line 512, Column 62: reference to external entity in attribute value
    …             <a href="NewsDetails.aspx?PageID=3&NewsID=74426" target="_parent">

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

  • Error Line 512, Column 62: reference to entity "NewsID" for which no system identifier could be generated
    …             <a href="NewsDetails.aspx?PageID=3&NewsID=74426" target="_parent">

    This is usually a cascading error caused by 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 406, Column 128: entity was defined here
    …Link' href='NewsDetails.aspx?PageID=54&NewsID=74424'><img id='TopImage' src='U…
  • Warning Line 517, Column 62: reference not terminated by REFC delimiter
    …             <a href="NewsDetails.aspx?PageID=3&NewsID=74425" target="_parent">

    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 517, Column 62: reference to external entity in attribute value
    …             <a href="NewsDetails.aspx?PageID=3&NewsID=74425" target="_parent">

    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 517, Column 62: reference to entity "NewsID" for which no system identifier could be generated
    …             <a href="NewsDetails.aspx?PageID=3&NewsID=74425" target="_parent">

    This is usually a cascading error caused by 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 406, Column 128: entity was defined here
    …Link' href='NewsDetails.aspx?PageID=54&NewsID=74424'><img id='TopImage' src='U…
  • Warning Line 520, Column 62: reference not terminated by REFC delimiter
    …             <a href="NewsDetails.aspx?PageID=3&NewsID=74425" target="_parent">

    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 520, Column 62: reference to external entity in attribute value
    …             <a href="NewsDetails.aspx?PageID=3&NewsID=74425" target="_parent">

    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 520, Column 62: reference to entity "NewsID" for which no system identifier could be generated
    …             <a href="NewsDetails.aspx?PageID=3&NewsID=74425" target="_parent">

    This is usually a cascading error caused by 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 406, Column 128: entity was defined here
    …Link' href='NewsDetails.aspx?PageID=54&NewsID=74424'><img id='TopImage' src='U…
  • Warning Line 525, Column 63: reference not terminated by REFC delimiter
    …            <a href="NewsDetails.aspx?PageID=56&NewsID=74423" target="_parent">

    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 525, Column 63: reference to external entity in attribute value
    …            <a href="NewsDetails.aspx?PageID=56&NewsID=74423" target="_parent">

    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 525, Column 63: reference to entity "NewsID" for which no system identifier could be generated
    …            <a href="NewsDetails.aspx?PageID=56&NewsID=74423" target="_parent">

    This is usually a cascading error caused by 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 406, Column 128: entity was defined here
    …Link' href='NewsDetails.aspx?PageID=54&NewsID=74424'><img id='TopImage' src='U…
  • Warning Line 528, Column 63: reference not terminated by REFC delimiter
    …            <a href="NewsDetails.aspx?PageID=56&NewsID=74423" target="_parent">

    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 528, Column 63: reference to external entity in attribute value
    …            <a href="NewsDetails.aspx?PageID=56&NewsID=74423" target="_parent">

    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 528, Column 63: reference to entity "NewsID" for which no system identifier could be generated
    …            <a href="NewsDetails.aspx?PageID=56&NewsID=74423" target="_parent">

    This is usually a cascading error caused by 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 406, Column 128: entity was defined here
    …Link' href='NewsDetails.aspx?PageID=54&NewsID=74424'><img id='TopImage' src='U…
  • Warning Line 533, Column 63: reference not terminated by REFC delimiter
    …            <a href="NewsDetails.aspx?PageID=56&NewsID=74413" target="_parent">

    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 533, Column 63: reference to external entity in attribute value
    …            <a href="NewsDetails.aspx?PageID=56&NewsID=74413" target="_parent">

    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 533, Column 63: reference to entity "NewsID" for which no system identifier could be generated
    …            <a href="NewsDetails.aspx?PageID=56&NewsID=74413" target="_parent">

    This is usually a cascading error caused by 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 406, Column 128: entity was defined here
    …Link' href='NewsDetails.aspx?PageID=54&NewsID=74424'><img id='TopImage' src='U…
  • Warning Line 536, Column 63: reference not terminated by REFC delimiter
    …            <a href="NewsDetails.aspx?PageID=56&NewsID=74413" target="_parent">

    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 536, Column 63: reference to external entity in attribute value
    …            <a href="NewsDetails.aspx?PageID=56&NewsID=74413" target="_parent">

    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 536, Column 63: reference to entity "NewsID" for which no system identifier could be generated
    …            <a href="NewsDetails.aspx?PageID=56&NewsID=74413" target="_parent">

    This is usually a cascading error caused by 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 406, Column 128: entity was defined here
    …Link' href='NewsDetails.aspx?PageID=54&NewsID=74424'><img id='TopImage' src='U…
  • Warning Line 543, Column 62: reference not terminated by REFC delimiter
    …             <a href="NewsDetails.aspx?PageID=4&NewsID=74419" target="_parent">

    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 543, Column 62: reference to external entity in attribute value
    …             <a href="NewsDetails.aspx?PageID=4&NewsID=74419" target="_parent">

    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 543, Column 62: reference to entity "NewsID" for which no system identifier could be generated
    …             <a href="NewsDetails.aspx?PageID=4&NewsID=74419" target="_parent">

    This is usually a cascading error caused by 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 406, Column 128: entity was defined here
    …Link' href='NewsDetails.aspx?PageID=54&NewsID=74424'><img id='TopImage' src='U…
  • Warning Line 546, Column 62: reference not terminated by REFC delimiter
    …             <a href="NewsDetails.aspx?PageID=4&NewsID=74419" target="_parent">

    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 546, Column 62: reference to external entity in attribute value
    …             <a href="NewsDetails.aspx?PageID=4&NewsID=74419" target="_parent">

    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 546, Column 62: reference to entity "NewsID" for which no system identifier could be generated
    …             <a href="NewsDetails.aspx?PageID=4&NewsID=74419" target="_parent">

    This is usually a cascading error caused by 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 406, Column 128: entity was defined here
    …Link' href='NewsDetails.aspx?PageID=54&NewsID=74424'><img id='TopImage' src='U…
  • Warning Line 551, Column 63: reference not terminated by REFC delimiter
    …            <a href="NewsDetails.aspx?PageID=54&NewsID=74399" target="_parent">

    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 551, Column 63: reference to external entity in attribute value
    …            <a href="NewsDetails.aspx?PageID=54&NewsID=74399" target="_parent">

    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 551, Column 63: reference to entity "NewsID" for which no system identifier could be generated
    …            <a href="NewsDetails.aspx?PageID=54&NewsID=74399" target="_parent">

    This is usually a cascading error caused by 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 406, Column 128: entity was defined here
    …Link' href='NewsDetails.aspx?PageID=54&NewsID=74424'><img id='TopImage' src='U…
  • Warning Line 554, Column 63: reference not terminated by REFC delimiter
    …            <a href="NewsDetails.aspx?PageID=54&NewsID=74399" target="_parent">

    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 554, Column 63: reference to external entity in attribute value
    …            <a href="NewsDetails.aspx?PageID=54&NewsID=74399" target="_parent">

    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 554, Column 63: reference to entity "NewsID" for which no system identifier could be generated
    …            <a href="NewsDetails.aspx?PageID=54&NewsID=74399" target="_parent">

    This is usually a cascading error caused by 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 406, Column 128: entity was defined here
    …Link' href='NewsDetails.aspx?PageID=54&NewsID=74424'><img id='TopImage' src='U…
  • Warning Line 559, Column 63: reference not terminated by REFC delimiter
    …            <a href="NewsDetails.aspx?PageID=29&NewsID=74405" target="_parent">

    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 559, Column 63: reference to external entity in attribute value
    …            <a href="NewsDetails.aspx?PageID=29&NewsID=74405" target="_parent">

    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 559, Column 63: reference to entity "NewsID" for which no system identifier could be generated
    …            <a href="NewsDetails.aspx?PageID=29&NewsID=74405" target="_parent">

    This is usually a cascading error caused by 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 406, Column 128: entity was defined here
    …Link' href='NewsDetails.aspx?PageID=54&NewsID=74424'><img id='TopImage' src='U…
  • Warning Line 562, Column 63: reference not terminated by REFC delimiter
    …            <a href="NewsDetails.aspx?PageID=29&NewsID=74405" target="_parent">

    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 562, Column 63: reference to external entity in attribute value
    …            <a href="NewsDetails.aspx?PageID=29&NewsID=74405" target="_parent">

    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 562, Column 63: reference to entity "NewsID" for which no system identifier could be generated
    …            <a href="NewsDetails.aspx?PageID=29&NewsID=74405" target="_parent">

    This is usually a cascading error caused by 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 406, Column 128: entity was defined here
    …Link' href='NewsDetails.aspx?PageID=54&NewsID=74424'><img id='TopImage' src='U…
  • Warning Line 567, Column 63: reference not terminated by REFC delimiter
    …            <a href="NewsDetails.aspx?PageID=54&NewsID=74394" target="_parent">

    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 567, Column 63: reference to external entity in attribute value
    …            <a href="NewsDetails.aspx?PageID=54&NewsID=74394" target="_parent">

    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 567, Column 63: reference to entity "NewsID" for which no system identifier could be generated
    …            <a href="NewsDetails.aspx?PageID=54&NewsID=74394" target="_parent">

    This is usually a cascading error caused by 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 406, Column 128: entity was defined here
    …Link' href='NewsDetails.aspx?PageID=54&NewsID=74424'><img id='TopImage' src='U…
  • Warning Line 570, Column 63: reference not terminated by REFC delimiter
    …            <a href="NewsDetails.aspx?PageID=54&NewsID=74394" target="_parent">

    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 570, Column 63: reference to external entity in attribute value
    …            <a href="NewsDetails.aspx?PageID=54&NewsID=74394" target="_parent">

    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 570, Column 63: reference to entity "NewsID" for which no system identifier could be generated
    …            <a href="NewsDetails.aspx?PageID=54&NewsID=74394" target="_parent">

    This is usually a cascading error caused by 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 406, Column 128: entity was defined here
    …Link' href='NewsDetails.aspx?PageID=54&NewsID=74424'><img id='TopImage' src='U…
  • Warning Line 575, Column 63: reference not terminated by REFC delimiter
    …            <a href="NewsDetails.aspx?PageID=27&NewsID=74401" target="_parent">

    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 575, Column 63: reference to external entity in attribute value
    …            <a href="NewsDetails.aspx?PageID=27&NewsID=74401" target="_parent">

    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 575, Column 63: reference to entity "NewsID" for which no system identifier could be generated
    …            <a href="NewsDetails.aspx?PageID=27&NewsID=74401" target="_parent">

    This is usually a cascading error caused by 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 406, Column 128: entity was defined here
    …Link' href='NewsDetails.aspx?PageID=54&NewsID=74424'><img id='TopImage' src='U…
  • Warning Line 578, Column 63: reference not terminated by REFC delimiter
    …            <a href="NewsDetails.aspx?PageID=27&NewsID=74401" target="_parent">

    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 578, Column 63: reference to external entity in attribute value
    …            <a href="NewsDetails.aspx?PageID=27&NewsID=74401" target="_parent">

    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 578, Column 63: reference to entity "NewsID" for which no system identifier could be generated
    …            <a href="NewsDetails.aspx?PageID=27&NewsID=74401" target="_parent">

    This is usually a cascading error caused by 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 406, Column 128: entity was defined here
    …Link' href='NewsDetails.aspx?PageID=54&NewsID=74424'><img id='TopImage' src='U…
  • Warning Line 583, Column 63: reference not terminated by REFC delimiter
    …            <a href="NewsDetails.aspx?PageID=16&NewsID=74384" target="_parent">

    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 583, Column 63: reference to external entity in attribute value
    …            <a href="NewsDetails.aspx?PageID=16&NewsID=74384" target="_parent">

    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 583, Column 63: reference to entity "NewsID" for which no system identifier could be generated
    …            <a href="NewsDetails.aspx?PageID=16&NewsID=74384" target="_parent">

    This is usually a cascading error caused by 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 406, Column 128: entity was defined here
    …Link' href='NewsDetails.aspx?PageID=54&NewsID=74424'><img id='TopImage' src='U…
  • Warning Line 586, Column 63: reference not terminated by REFC delimiter
    …            <a href="NewsDetails.aspx?PageID=16&NewsID=74384" target="_parent">

    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 586, Column 63: reference to external entity in attribute value
    …            <a href="NewsDetails.aspx?PageID=16&NewsID=74384" target="_parent">

    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 586, Column 63: reference to entity "NewsID" for which no system identifier could be generated
    …            <a href="NewsDetails.aspx?PageID=16&NewsID=74384" target="_parent">

    This is usually a cascading error caused by 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 406, Column 128: entity was defined here
    …Link' href='NewsDetails.aspx?PageID=54&NewsID=74424'><img id='TopImage' src='U…
  • Warning Line 591, Column 62: reference not terminated by REFC delimiter
    …             <a href="NewsDetails.aspx?PageID=3&NewsID=74398" target="_parent">

    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 591, Column 62: reference to external entity in attribute value
    …             <a href="NewsDetails.aspx?PageID=3&NewsID=74398" target="_parent">

    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 591, Column 62: reference to entity "NewsID" for which no system identifier could be generated
    …             <a href="NewsDetails.aspx?PageID=3&NewsID=74398" target="_parent">

    This is usually a cascading error caused by 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 406, Column 128: entity was defined here
    …Link' href='NewsDetails.aspx?PageID=54&NewsID=74424'><img id='TopImage' src='U…
  • Warning Line 594, Column 62: reference not terminated by REFC delimiter
    …             <a href="NewsDetails.aspx?PageID=3&NewsID=74398" target="_parent">

    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 594, Column 62: reference to external entity in attribute value
    …             <a href="NewsDetails.aspx?PageID=3&NewsID=74398" target="_parent">

    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 594, Column 62: reference to entity "NewsID" for which no system identifier could be generated
    …             <a href="NewsDetails.aspx?PageID=3&NewsID=74398" target="_parent">

    This is usually a cascading error caused by 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 406, Column 128: entity was defined here
    …Link' href='NewsDetails.aspx?PageID=54&NewsID=74424'><img id='TopImage' src='U…
  • Warning Line 613, Column 79: reference not terminated by REFC delimiter
    …            <a href="NewsDetails.aspx?PageID=56&NewsID=74378" target="_parent">

    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 613, Column 79: reference to external entity in attribute value
    …            <a href="NewsDetails.aspx?PageID=56&NewsID=74378" target="_parent">

    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 613, Column 79: reference to entity "NewsID" for which no system identifier could be generated
    …            <a href="NewsDetails.aspx?PageID=56&NewsID=74378" target="_parent">

    This is usually a cascading error caused by 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 406, Column 128: entity was defined here
    …Link' href='NewsDetails.aspx?PageID=54&NewsID=74424'><img id='TopImage' src='U…
  • Warning Line 616, Column 79: reference not terminated by REFC delimiter
    …            <a href="NewsDetails.aspx?PageID=56&NewsID=74378" target="_parent">

    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 616, Column 79: reference to external entity in attribute value
    …            <a href="NewsDetails.aspx?PageID=56&NewsID=74378" target="_parent">

    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 616, Column 79: reference to entity "NewsID" for which no system identifier could be generated
    …            <a href="NewsDetails.aspx?PageID=56&NewsID=74378" target="_parent">

    This is usually a cascading error caused by 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 406, Column 128: entity was defined here
    …Link' href='NewsDetails.aspx?PageID=54&NewsID=74424'><img id='TopImage' src='U…
  • Warning Line 621, Column 79: reference not terminated by REFC delimiter
    …            <a href="NewsDetails.aspx?PageID=56&NewsID=74332" target="_parent">

    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 621, Column 79: reference to external entity in attribute value
    …            <a href="NewsDetails.aspx?PageID=56&NewsID=74332" target="_parent">

    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 621, Column 79: reference to entity "NewsID" for which no system identifier could be generated
    …            <a href="NewsDetails.aspx?PageID=56&NewsID=74332" target="_parent">

    This is usually a cascading error caused by 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 406, Column 128: entity was defined here
    …Link' href='NewsDetails.aspx?PageID=54&NewsID=74424'><img id='TopImage' src='U…
  • Warning Line 624, Column 79: reference not terminated by REFC delimiter
    …            <a href="NewsDetails.aspx?PageID=56&NewsID=74332" target="_parent">

    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 624, Column 79: reference to external entity in attribute value
    …            <a href="NewsDetails.aspx?PageID=56&NewsID=74332" target="_parent">

    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 624, Column 79: reference to entity "NewsID" for which no system identifier could be generated
    …            <a href="NewsDetails.aspx?PageID=56&NewsID=74332" target="_parent">

    This is usually a cascading error caused by 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 406, Column 128: entity was defined here
    …Link' href='NewsDetails.aspx?PageID=54&NewsID=74424'><img id='TopImage' src='U…
  • Warning Line 629, Column 79: reference not terminated by REFC delimiter
    …            <a href="NewsDetails.aspx?PageID=56&NewsID=74274" target="_parent">

    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 629, Column 79: reference to external entity in attribute value
    …            <a href="NewsDetails.aspx?PageID=56&NewsID=74274" target="_parent">

    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 629, Column 79: reference to entity "NewsID" for which no system identifier could be generated
    …            <a href="NewsDetails.aspx?PageID=56&NewsID=74274" target="_parent">

    This is usually a cascading error caused by 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 406, Column 128: entity was defined here
    …Link' href='NewsDetails.aspx?PageID=54&NewsID=74424'><img id='TopImage' src='U…
  • Warning Line 632, Column 79: reference not terminated by REFC delimiter
    …            <a href="NewsDetails.aspx?PageID=56&NewsID=74274" target="_parent">

    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 632, Column 79: reference to external entity in attribute value
    …            <a href="NewsDetails.aspx?PageID=56&NewsID=74274" target="_parent">

    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 632, Column 79: reference to entity "NewsID" for which no system identifier could be generated
    …            <a href="NewsDetails.aspx?PageID=56&NewsID=74274" target="_parent">

    This is usually a cascading error caused by 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 406, Column 128: entity was defined here
    …Link' href='NewsDetails.aspx?PageID=54&NewsID=74424'><img id='TopImage' src='U…
  • Warning Line 637, Column 79: reference not terminated by REFC delimiter
    …            <a href="NewsDetails.aspx?PageID=56&NewsID=74261" target="_parent">

    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 637, Column 79: reference to external entity in attribute value
    …            <a href="NewsDetails.aspx?PageID=56&NewsID=74261" target="_parent">

    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 637, Column 79: reference to entity "NewsID" for which no system identifier could be generated
    …            <a href="NewsDetails.aspx?PageID=56&NewsID=74261" target="_parent">

    This is usually a cascading error caused by 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 406, Column 128: entity was defined here
    …Link' href='NewsDetails.aspx?PageID=54&NewsID=74424'><img id='TopImage' src='U…
  • Warning Line 640, Column 79: reference not terminated by REFC delimiter
    …            <a href="NewsDetails.aspx?PageID=56&NewsID=74261" target="_parent">

    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 640, Column 79: reference to external entity in attribute value
    …            <a href="NewsDetails.aspx?PageID=56&NewsID=74261" target="_parent">

    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 640, Column 79: reference to entity "NewsID" for which no system identifier could be generated
    …            <a href="NewsDetails.aspx?PageID=56&NewsID=74261" target="_parent">

    This is usually a cascading error caused by 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 406, Column 128: entity was defined here
    …Link' href='NewsDetails.aspx?PageID=54&NewsID=74424'><img id='TopImage' src='U…
  • Warning Line 645, Column 79: reference not terminated by REFC delimiter
    …            <a href="NewsDetails.aspx?PageID=56&NewsID=74252" target="_parent">

    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 645, Column 79: reference to external entity in attribute value
    …            <a href="NewsDetails.aspx?PageID=56&NewsID=74252" target="_parent">

    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 645, Column 79: reference to entity "NewsID" for which no system identifier could be generated
    …            <a href="NewsDetails.aspx?PageID=56&NewsID=74252" target="_parent">

    This is usually a cascading error caused by 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 406, Column 128: entity was defined here
    …Link' href='NewsDetails.aspx?PageID=54&NewsID=74424'><img id='TopImage' src='U…
  • Warning Line 648, Column 79: reference not terminated by REFC delimiter
    …            <a href="NewsDetails.aspx?PageID=56&NewsID=74252" target="_parent">

    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 648, Column 79: reference to external entity in attribute value
    …            <a href="NewsDetails.aspx?PageID=56&NewsID=74252" target="_parent">

    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 648, Column 79: reference to entity "NewsID" for which no system identifier could be generated
    …            <a href="NewsDetails.aspx?PageID=56&NewsID=74252" target="_parent">

    This is usually a cascading error caused by 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 406, Column 128: entity was defined here
    …Link' href='NewsDetails.aspx?PageID=54&NewsID=74424'><img id='TopImage' src='U…
  • Warning Line 653, Column 79: reference not terminated by REFC delimiter
    …            <a href="NewsDetails.aspx?PageID=56&NewsID=74216" target="_parent">

    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 653, Column 79: reference to external entity in attribute value
    …            <a href="NewsDetails.aspx?PageID=56&NewsID=74216" target="_parent">

    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 653, Column 79: reference to entity "NewsID" for which no system identifier could be generated
    …            <a href="NewsDetails.aspx?PageID=56&NewsID=74216" target="_parent">

    This is usually a cascading error caused by 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 406, Column 128: entity was defined here
    …Link' href='NewsDetails.aspx?PageID=54&NewsID=74424'><img id='TopImage' src='U…
  • Warning Line 656, Column 79: reference not terminated by REFC delimiter
    …            <a href="NewsDetails.aspx?PageID=56&NewsID=74216" target="_parent">

    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 656, Column 79: reference to external entity in attribute value
    …            <a href="NewsDetails.aspx?PageID=56&NewsID=74216" target="_parent">

    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 656, Column 79: reference to entity "NewsID" for which no system identifier could be generated
    …            <a href="NewsDetails.aspx?PageID=56&NewsID=74216" target="_parent">

    This is usually a cascading error caused by 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 406, Column 128: entity was defined here
    …Link' href='NewsDetails.aspx?PageID=54&NewsID=74424'><img id='TopImage' src='U…
  • Warning Line 668, Column 79: reference not terminated by REFC delimiter
    …            <a href="NewsDetails.aspx?PageID=56&NewsID=74213" target="_parent">

    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 668, Column 79: reference to external entity in attribute value
    …            <a href="NewsDetails.aspx?PageID=56&NewsID=74213" target="_parent">

    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 668, Column 79: reference to entity "NewsID" for which no system identifier could be generated
    …            <a href="NewsDetails.aspx?PageID=56&NewsID=74213" target="_parent">

    This is usually a cascading error caused by 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 406, Column 128: entity was defined here
    …Link' href='NewsDetails.aspx?PageID=54&NewsID=74424'><img id='TopImage' src='U…
  • Warning Line 671, Column 79: reference not terminated by REFC delimiter
    …            <a href="NewsDetails.aspx?PageID=56&NewsID=74213" target="_parent">

    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 671, Column 79: reference to external entity in attribute value
    …            <a href="NewsDetails.aspx?PageID=56&NewsID=74213" target="_parent">

    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 671, Column 79: reference to entity "NewsID" for which no system identifier could be generated
    …            <a href="NewsDetails.aspx?PageID=56&NewsID=74213" target="_parent">

    This is usually a cascading error caused by 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 406, Column 128: entity was defined here
    …Link' href='NewsDetails.aspx?PageID=54&NewsID=74424'><img id='TopImage' src='U…
  • Warning Line 676, Column 79: reference not terminated by REFC delimiter
    …            <a href="NewsDetails.aspx?PageID=56&NewsID=74204" target="_parent">

    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 676, Column 79: reference to external entity in attribute value
    …            <a href="NewsDetails.aspx?PageID=56&NewsID=74204" target="_parent">

    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 676, Column 79: reference to entity "NewsID" for which no system identifier could be generated
    …            <a href="NewsDetails.aspx?PageID=56&NewsID=74204" target="_parent">

    This is usually a cascading error caused by 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 406, Column 128: entity was defined here
    …Link' href='NewsDetails.aspx?PageID=54&NewsID=74424'><img id='TopImage' src='U…
  • Warning Line 679, Column 79: reference not terminated by REFC delimiter
    …            <a href="NewsDetails.aspx?PageID=56&NewsID=74204" target="_parent">

    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 679, Column 79: reference to external entity in attribute value
    …            <a href="NewsDetails.aspx?PageID=56&NewsID=74204" target="_parent">

    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 679, Column 79: reference to entity "NewsID" for which no system identifier could be generated
    …            <a href="NewsDetails.aspx?PageID=56&NewsID=74204" target="_parent">

    This is usually a cascading error caused by 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 406, Column 128: entity was defined here
    …Link' href='NewsDetails.aspx?PageID=54&NewsID=74424'><img id='TopImage' src='U…
  • Warning Line 684, Column 79: reference not terminated by REFC delimiter
    …            <a href="NewsDetails.aspx?PageID=56&NewsID=74138" target="_parent">

    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 684, Column 79: reference to external entity in attribute value
    …            <a href="NewsDetails.aspx?PageID=56&NewsID=74138" target="_parent">

    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 684, Column 79: reference to entity "NewsID" for which no system identifier could be generated
    …            <a href="NewsDetails.aspx?PageID=56&NewsID=74138" target="_parent">

    This is usually a cascading error caused by 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 406, Column 128: entity was defined here
    …Link' href='NewsDetails.aspx?PageID=54&NewsID=74424'><img id='TopImage' src='U…
  • Warning Line 687, Column 79: reference not terminated by REFC delimiter
    …            <a href="NewsDetails.aspx?PageID=56&NewsID=74138" target="_parent">

    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 687, Column 79: reference to external entity in attribute value
    …            <a href="NewsDetails.aspx?PageID=56&NewsID=74138" target="_parent">

    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 687, Column 79: reference to entity "NewsID" for which no system identifier could be generated
    …            <a href="NewsDetails.aspx?PageID=56&NewsID=74138" target="_parent">

    This is usually a cascading error caused by 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 406, Column 128: entity was defined here
    …Link' href='NewsDetails.aspx?PageID=54&NewsID=74424'><img id='TopImage' src='U…
  • Warning Line 692, Column 79: reference not terminated by REFC delimiter
    …            <a href="NewsDetails.aspx?PageID=56&NewsID=73910" target="_parent">

    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 692, Column 79: reference to external entity in attribute value
    …            <a href="NewsDetails.aspx?PageID=56&NewsID=73910" target="_parent">

    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 692, Column 79: reference to entity "NewsID" for which no system identifier could be generated
    …            <a href="NewsDetails.aspx?PageID=56&NewsID=73910" target="_parent">

    This is usually a cascading error caused by 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 406, Column 128: entity was defined here
    …Link' href='NewsDetails.aspx?PageID=54&NewsID=74424'><img id='TopImage' src='U…
  • Warning Line 695, Column 79: reference not terminated by REFC delimiter
    …            <a href="NewsDetails.aspx?PageID=56&NewsID=73910" target="_parent">

    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 695, Column 79: reference to external entity in attribute value
    …            <a href="NewsDetails.aspx?PageID=56&NewsID=73910" target="_parent">

    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 695, Column 79: reference to entity "NewsID" for which no system identifier could be generated
    …            <a href="NewsDetails.aspx?PageID=56&NewsID=73910" target="_parent">

    This is usually a cascading error caused by 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 406, Column 128: entity was defined here
    …Link' href='NewsDetails.aspx?PageID=54&NewsID=74424'><img id='TopImage' src='U…
  • Warning Line 700, Column 79: reference not terminated by REFC delimiter
    …            <a href="NewsDetails.aspx?PageID=56&NewsID=74109" target="_parent">

    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 700, Column 79: reference to external entity in attribute value
    …            <a href="NewsDetails.aspx?PageID=56&NewsID=74109" target="_parent">

    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 700, Column 79: reference to entity "NewsID" for which no system identifier could be generated
    …            <a href="NewsDetails.aspx?PageID=56&NewsID=74109" target="_parent">

    This is usually a cascading error caused by 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 406, Column 128: entity was defined here
    …Link' href='NewsDetails.aspx?PageID=54&NewsID=74424'><img id='TopImage' src='U…
  • Warning Line 703, Column 79: reference not terminated by REFC delimiter
    …            <a href="NewsDetails.aspx?PageID=56&NewsID=74109" target="_parent">

    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 703, Column 79: reference to external entity in attribute value
    …            <a href="NewsDetails.aspx?PageID=56&NewsID=74109" target="_parent">

    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 703, Column 79: reference to entity "NewsID" for which no system identifier could be generated
    …            <a href="NewsDetails.aspx?PageID=56&NewsID=74109" target="_parent">

    This is usually a cascading error caused by 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 406, Column 128: entity was defined here
    …Link' href='NewsDetails.aspx?PageID=54&NewsID=74424'><img id='TopImage' src='U…
  • Warning Line 708, Column 79: reference not terminated by REFC delimiter
    …            <a href="NewsDetails.aspx?PageID=56&NewsID=74136" target="_parent">

    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 708, Column 79: reference to external entity in attribute value
    …            <a href="NewsDetails.aspx?PageID=56&NewsID=74136" target="_parent">

    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 708, Column 79: reference to entity "NewsID" for which no system identifier could be generated
    …            <a href="NewsDetails.aspx?PageID=56&NewsID=74136" target="_parent">

    This is usually a cascading error caused by 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 406, Column 128: entity was defined here
    …Link' href='NewsDetails.aspx?PageID=54&NewsID=74424'><img id='TopImage' src='U…
  • Warning Line 711, Column 79: reference not terminated by REFC delimiter
    …            <a href="NewsDetails.aspx?PageID=56&NewsID=74136" target="_parent">

    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 711, Column 79: reference to external entity in attribute value
    …            <a href="NewsDetails.aspx?PageID=56&NewsID=74136" target="_parent">

    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 711, Column 79: reference to entity "NewsID" for which no system identifier could be generated
    …            <a href="NewsDetails.aspx?PageID=56&NewsID=74136" target="_parent">

    This is usually a cascading error caused by 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 406, Column 128: entity was defined here
    …Link' href='NewsDetails.aspx?PageID=54&NewsID=74424'><img id='TopImage' src='U…
  • Warning Line 736, Column 64: character "&" is the first character of a delimiter but occurred as data
    …p://sstatic1.histats.com/0.gif?1245407&101" alt="counter code" border="0"></a>…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 736, Column 103: end tag for "img" omitted, but OMITTAG NO was specified
    …c1.histats.com/0.gif?1245407&101" alt="counter code" border="0"></a></noscript>

    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 736, Column 13: start tag was here
                <img src="http://sstatic1.histats.com/0.gif?1245407&101" alt="count…
  • Error Line 760, Column 175: required attribute "alt" not specified
    …mg src="http://www.designtechno.net/statistics/poweredby.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 777, Column 71: there is no attribute "allowtransparency"
    …                             height: 240px;" 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 808, Column 7: end tag for "div" omitted, but OMITTAG NO was specified
    </form>

    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 65, Column 5: start tag was here
        <div id="Wrapper" class="Wrapper">

Visitor Analysis

Daily Visitor
  • 1.517 visits
Daily Visitor