rastmanesh.com

دفتر مشاوره تغذیه و رژیم درمانی و رژیم لاغری،لاغری موضعی دکتر رضا راست منش ...

This data was last updated from 04-02-2014 09:41:11  (update).

Overview Info



  • Domain Name
    rastmanesh.com
  • Favicon
  • Alexa Rank
    #0
  • Google Page Rank
    3
  • Ip Address
    185.10.72.8
  • Page Size
    72.6 KB
  • Images
    1 GIF, 5 JPG, 3 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    0 0 0 0 0 0

Website Meta Analysis



  • Title
    رژیم، رژیم لاغری،لاغری موضعی، رژیم چاقی، رژیم درمانی، برنامه رژیم:دفتر مشاوره تغذیه و رژیم درمانی دکتر رضا راست منش
  • Meta Keyword
    رژیم، رژیم لاغری، لاغری موضعی، رژیم چاقی، رژیم درمانی، برنامه رژیم
  • Meta Description
    دفتر مشاوره تغذیه و رژیم درمانی و رژیم لاغری،لاغری موضعی دکتر رضا راست منش

Technical Analysis



  • Webserver
    Microsoft-IIS/7.5
  • Ip Address
    185.10.72.8
  • Domain Age
    1 Years, 5 Months, 20 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • cache-control: private
  • content-length: 19221
  • content-type: text/html; charset=utf-8
  • content-encoding: gzip
  • server: Microsoft-IIS/7.5
  • x-aspnet-version: 2.0.50727
  • x-powered-by: ASP.NET
  • date: Tue, 04 Feb 2014 21:41:06 GMT
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for rastmanesh.com

IP 185.10.72.8 Analysis

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

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 95 Errors
  • 93 Warnings
Ratio Text/Html
  • 0.5212063329791098
Message Error
  • Warning Line 32, Column 37: character "<" is the first character of a delimiter but occurred as data
                else if (parseFloat(aa) <= 18.5) {

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 35, Column 37: character "<" is the first character of a delimiter but occurred as data
                else if (parseFloat(aa) <= 24.9 && parseFloat(aa) > 18.5) {

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 35, Column 45: character "&" is the first character of a delimiter but occurred as data
                else if (parseFloat(aa) <= 24.9 && parseFloat(aa) > 18.5) {

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 35, Column 46: character "&" is the first character of a delimiter but occurred as data
                else if (parseFloat(aa) <= 24.9 && parseFloat(aa) > 18.5) {

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 38, Column 37: character "<" is the first character of a delimiter but occurred as data
                else if (parseFloat(aa) <= 29.9 && parseFloat(aa) > 24.9) {

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 38, Column 45: character "&" is the first character of a delimiter but occurred as data
                else if (parseFloat(aa) <= 29.9 && parseFloat(aa) > 24.9) {

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 38, Column 46: character "&" is the first character of a delimiter but occurred as data
                else if (parseFloat(aa) <= 29.9 && parseFloat(aa) > 24.9) {

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 81, Column 13164: cannot generate system identifier for general entity "CatID"
    …><a href='ShowContent.aspx?PageID=637&CatID=281'>مقالات فارسی </a><ul><li><a h…

    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 81, Column 13164: general entity "CatID" not defined and no default entity
    …><a href='ShowContent.aspx?PageID=637&CatID=281'>مقالات فارسی </a><ul><li><a h…

    This is usually a cascading error caused by 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 81, Column 13169: reference not terminated by REFC delimiter
    …ref='ShowContent.aspx?PageID=637&CatID=281'>مقالات فارسی </a><ul><li><a href='…

    If you meant to include an entity that starts with "&", then you should terminate it 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 81, Column 13169: reference to external entity in attribute value
    …ref='ShowContent.aspx?PageID=637&CatID=281'>مقالات فارسی </a><ul><li><a href='…

    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 81, Column 13169: reference to entity "CatID" for which no system identifier could be generated
    …ref='ShowContent.aspx?PageID=637&CatID=281'>مقالات فارسی </a><ul><li><a href='…

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

  • Info Line 81, Column 13163: entity was defined here
    …i><a href='ShowContent.aspx?PageID=637&CatID=281'>مقالات فارسی </a><ul><li><a …
  • Warning Line 81, Column 13242: reference not terminated by REFC delimiter
    …ref='ShowContent.aspx?PageID=642&CatID=283'>چاقی </a><ul></ul></li><li><a href…

    If you meant to include an entity that starts with "&", then you should terminate it 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 81, Column 13242: reference to external entity in attribute value
    …ref='ShowContent.aspx?PageID=642&CatID=283'>چاقی </a><ul></ul></li><li><a href…

    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 81, Column 13242: reference to entity "CatID" for which no system identifier could be generated
    …ref='ShowContent.aspx?PageID=642&CatID=283'>چاقی </a><ul></ul></li><li><a href…

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

  • Info Line 81, Column 13163: entity was defined here
    …i><a href='ShowContent.aspx?PageID=637&CatID=281'>مقالات فارسی </a><ul><li><a …
  • Error Line 81, Column 13265: end tag for "ul" which is not finished
    …ageID=642&CatID=283'>چاقی </a><ul></ul></li><li><a href='ShowContent.aspx?Page…

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

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

  • Warning Line 81, Column 13317: reference not terminated by REFC delimiter
    …ref='ShowContent.aspx?PageID=642&CatID=284'>لاغری </a><ul></ul></li><li><a hre…

    If you meant to include an entity that starts with "&", then you should terminate it 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 81, Column 13317: reference to external entity in attribute value
    …ref='ShowContent.aspx?PageID=642&CatID=284'>لاغری </a><ul></ul></li><li><a hre…

    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 81, Column 13317: reference to entity "CatID" for which no system identifier could be generated
    …ref='ShowContent.aspx?PageID=642&CatID=284'>لاغری </a><ul></ul></li><li><a hre…

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

  • Info Line 81, Column 13163: entity was defined here
    …i><a href='ShowContent.aspx?PageID=637&CatID=281'>مقالات فارسی </a><ul><li><a …
  • Error Line 81, Column 13341: end tag for "ul" which is not finished
    …geID=642&CatID=284'>لاغری </a><ul></ul></li><li><a href='ShowContent.aspx?Page…

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

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

  • Warning Line 81, Column 13393: reference not terminated by REFC delimiter
    …ref='ShowContent.aspx?PageID=642&CatID=285'>زنان باردار </a><ul></ul></li><li>…

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

  • Warning Line 81, Column 13393: reference to external entity in attribute value
    …ref='ShowContent.aspx?PageID=642&CatID=285'>زنان باردار </a><ul></ul></li><li>…

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

  • Error Line 81, Column 13393: reference to entity "CatID" for which no system identifier could be generated
    …ref='ShowContent.aspx?PageID=642&CatID=285'>زنان باردار </a><ul></ul></li><li>…

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

  • Info Line 81, Column 13163: entity was defined here
    …i><a href='ShowContent.aspx?PageID=637&CatID=281'>مقالات فارسی </a><ul><li><a …
  • Error Line 81, Column 13423: end tag for "ul" which is not finished
    …42&CatID=285'>زنان باردار </a><ul></ul></li><li><a href='ShowContent.aspx?Page…

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

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

  • Warning Line 81, Column 13475: reference not terminated by REFC delimiter
    …ref='ShowContent.aspx?PageID=642&CatID=286'>کودکان </a><ul></ul></li><li><a hr…

    If you meant to include an entity that starts with "&", then you should terminate it 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 81, Column 13475: reference to external entity in attribute value
    …ref='ShowContent.aspx?PageID=642&CatID=286'>کودکان </a><ul></ul></li><li><a hr…

    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 81, Column 13475: reference to entity "CatID" for which no system identifier could be generated
    …ref='ShowContent.aspx?PageID=642&CatID=286'>کودکان </a><ul></ul></li><li><a hr…

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

  • Info Line 81, Column 13163: entity was defined here
    …i><a href='ShowContent.aspx?PageID=637&CatID=281'>مقالات فارسی </a><ul><li><a …
  • Error Line 81, Column 13500: end tag for "ul" which is not finished
    …eID=642&CatID=286'>کودکان </a><ul></ul></li><li><a href='ShowContent.aspx?Page…

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

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

  • Warning Line 81, Column 13552: reference not terminated by REFC delimiter
    …ref='ShowContent.aspx?PageID=642&CatID=287'>دیابتی </a><ul></ul></li><li><a hr…

    If you meant to include an entity that starts with "&", then you should terminate it 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 81, Column 13552: reference to external entity in attribute value
    …ref='ShowContent.aspx?PageID=642&CatID=287'>دیابتی </a><ul></ul></li><li><a hr…

    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 81, Column 13552: reference to entity "CatID" for which no system identifier could be generated
    …ref='ShowContent.aspx?PageID=642&CatID=287'>دیابتی </a><ul></ul></li><li><a hr…

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

  • Info Line 81, Column 13163: entity was defined here
    …i><a href='ShowContent.aspx?PageID=637&CatID=281'>مقالات فارسی </a><ul><li><a …
  • Error Line 81, Column 13577: end tag for "ul" which is not finished
    …eID=642&CatID=287'>دیابتی </a><ul></ul></li><li><a href='ShowContent.aspx?Page…

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

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

  • Warning Line 81, Column 13629: reference not terminated by REFC delimiter
    …ref='ShowContent.aspx?PageID=642&CatID=288'>بیماران قلبی </a><ul></ul></li><li…

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

  • Warning Line 81, Column 13629: reference to external entity in attribute value
    …ref='ShowContent.aspx?PageID=642&CatID=288'>بیماران قلبی </a><ul></ul></li><li…

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

  • Error Line 81, Column 13629: reference to entity "CatID" for which no system identifier could be generated
    …ref='ShowContent.aspx?PageID=642&CatID=288'>بیماران قلبی </a><ul></ul></li><li…

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

  • Info Line 81, Column 13163: entity was defined here
    …i><a href='ShowContent.aspx?PageID=637&CatID=281'>مقالات فارسی </a><ul><li><a …
  • Error Line 81, Column 13660: end tag for "ul" which is not finished
    …2&CatID=288'>بیماران قلبی </a><ul></ul></li><li><a href='ShowContent.aspx?Page…

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

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

  • Warning Line 81, Column 13712: reference not terminated by REFC delimiter
    …ref='ShowContent.aspx?PageID=642&CatID=289'>بیماران مفصلی </a><ul></ul></li><l…

    If you meant to include an entity that starts with "&", then you should terminate it 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 81, Column 13712: reference to external entity in attribute value
    …ref='ShowContent.aspx?PageID=642&CatID=289'>بیماران مفصلی </a><ul></ul></li><l…

    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 81, Column 13712: reference to entity "CatID" for which no system identifier could be generated
    …ref='ShowContent.aspx?PageID=642&CatID=289'>بیماران مفصلی </a><ul></ul></li><l…

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

  • Info Line 81, Column 13163: entity was defined here
    …i><a href='ShowContent.aspx?PageID=637&CatID=281'>مقالات فارسی </a><ul><li><a …
  • Error Line 81, Column 13744: end tag for "ul" which is not finished
    …&CatID=289'>بیماران مفصلی </a><ul></ul></li><li><a href='ShowContent.aspx?Page…

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

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

  • Warning Line 81, Column 13796: reference not terminated by REFC delimiter
    …ref='ShowContent.aspx?PageID=642&CatID=290'>سایر </a><ul></ul></li><li><a href…

    If you meant to include an entity that starts with "&", then you should terminate it 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 81, Column 13796: reference to external entity in attribute value
    …ref='ShowContent.aspx?PageID=642&CatID=290'>سایر </a><ul></ul></li><li><a href…

    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 81, Column 13796: reference to entity "CatID" for which no system identifier could be generated
    …ref='ShowContent.aspx?PageID=642&CatID=290'>سایر </a><ul></ul></li><li><a href…

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

  • Info Line 81, Column 13163: entity was defined here
    …i><a href='ShowContent.aspx?PageID=637&CatID=281'>مقالات فارسی </a><ul><li><a …
  • Error Line 81, Column 13819: end tag for "ul" which is not finished
    …ageID=642&CatID=290'>سایر </a><ul></ul></li><li><a href='ShowContent.aspx?Page…

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

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

  • Warning Line 81, Column 13871: reference not terminated by REFC delimiter
    …ref='ShowContent.aspx?PageID=642&CatID=305'>A pilot study of potassium supplem…

    If you meant to include an entity that starts with "&", then you should terminate it 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 81, Column 13871: reference to external entity in attribute value
    …ref='ShowContent.aspx?PageID=642&CatID=305'>A pilot study of potassium supplem…

    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 81, Column 13871: reference to entity "CatID" for which no system identifier could be generated
    …ref='ShowContent.aspx?PageID=642&CatID=305'>A pilot study of potassium supplem…

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

  • Info Line 81, Column 13163: entity was defined here
    …i><a href='ShowContent.aspx?PageID=637&CatID=281'>مقالات فارسی </a><ul><li><a …
  • Error Line 81, Column 14056: end tag for "ul" which is not finished
    …placebo-controlled trial. </a><ul></ul></li><li><a href='ShowContent.aspx?Page…

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

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

  • Warning Line 81, Column 14108: reference not terminated by REFC delimiter
    …ref='ShowContent.aspx?PageID=642&CatID=310'>Hypothetical hormonal mechanism by…

    If you meant to include an entity that starts with "&", then you should terminate it 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 81, Column 14108: reference to external entity in attribute value
    …ref='ShowContent.aspx?PageID=642&CatID=310'>Hypothetical hormonal mechanism by…

    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 81, Column 14108: reference to entity "CatID" for which no system identifier could be generated
    …ref='ShowContent.aspx?PageID=642&CatID=310'>Hypothetical hormonal mechanism by…

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

  • Info Line 81, Column 13163: entity was defined here
    …i><a href='ShowContent.aspx?PageID=637&CatID=281'>مقالات فارسی </a><ul><li><a …
  • Error Line 81, Column 14232: end tag for "ul" which is not finished
    …ith rheumatoid arthritis. </a><ul></ul></li></ul></li><li><a href='ShowContent…

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

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

  • Warning Line 81, Column 14294: reference not terminated by REFC delimiter
    …ref='ShowContent.aspx?PageID=637&CatID=282'>مقالات خارجی </a><ul><li><a href='…

    If you meant to include an entity that starts with "&", then you should terminate it 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 81, Column 14294: reference to external entity in attribute value
    …ref='ShowContent.aspx?PageID=637&CatID=282'>مقالات خارجی </a><ul><li><a href='…

    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 81, Column 14294: reference to entity "CatID" for which no system identifier could be generated
    …ref='ShowContent.aspx?PageID=637&CatID=282'>مقالات خارجی </a><ul><li><a href='…

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

  • Info Line 81, Column 13163: entity was defined here
    …i><a href='ShowContent.aspx?PageID=637&CatID=281'>مقالات فارسی </a><ul><li><a …
  • Warning Line 81, Column 14367: reference not terminated by REFC delimiter
    …ref='ShowContent.aspx?PageID=642&CatID=304'>A pilot study of potassium supplem…

    If you meant to include an entity that starts with "&", then you should terminate it 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 81, Column 14367: reference to external entity in attribute value
    …ref='ShowContent.aspx?PageID=642&CatID=304'>A pilot study of potassium supplem…

    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 81, Column 14367: reference to entity "CatID" for which no system identifier could be generated
    …ref='ShowContent.aspx?PageID=642&CatID=304'>A pilot study of potassium supplem…

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

  • Info Line 81, Column 13163: entity was defined here
    …i><a href='ShowContent.aspx?PageID=637&CatID=281'>مقالات فارسی </a><ul><li><a …
  • Error Line 81, Column 14552: end tag for "ul" which is not finished
    …placebo-controlled trial. </a><ul></ul></li><li><a href='ShowContent.aspx?Page…

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

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

  • Warning Line 81, Column 14604: reference not terminated by REFC delimiter
    …ref='ShowContent.aspx?PageID=642&CatID=309'>Hypothetical hormonal mechanism by…

    If you meant to include an entity that starts with "&", then you should terminate it 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 81, Column 14604: reference to external entity in attribute value
    …ref='ShowContent.aspx?PageID=642&CatID=309'>Hypothetical hormonal mechanism by…

    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 81, Column 14604: reference to entity "CatID" for which no system identifier could be generated
    …ref='ShowContent.aspx?PageID=642&CatID=309'>Hypothetical hormonal mechanism by…

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

  • Info Line 81, Column 13163: entity was defined here
    …i><a href='ShowContent.aspx?PageID=637&CatID=281'>مقالات فارسی </a><ul><li><a …
  • Error Line 81, Column 14728: end tag for "ul" which is not finished
    …ith rheumatoid arthritis. </a><ul></ul></li><li><a href='ShowContent.aspx?Page…

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

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

  • Warning Line 81, Column 14780: reference not terminated by REFC delimiter
    …ref='ShowContent.aspx?PageID=642&CatID=315'>Alopecia and ocular alterations: a…

    If you meant to include an entity that starts with "&", then you should terminate it 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 81, Column 14780: reference to external entity in attribute value
    …ref='ShowContent.aspx?PageID=642&CatID=315'>Alopecia and ocular alterations: a…

    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 81, Column 14780: reference to entity "CatID" for which no system identifier could be generated
    …ref='ShowContent.aspx?PageID=642&CatID=315'>Alopecia and ocular alterations: a…

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

  • Info Line 81, Column 13163: entity was defined here
    …i><a href='ShowContent.aspx?PageID=637&CatID=281'>مقالات فارسی </a><ul><li><a …
  • Error Line 81, Column 14853: end tag for "ul" which is not finished
    …ns: a role for Minoxidil? </a><ul></ul></li><li><a href='ShowContent.aspx?Page…

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

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

  • Warning Line 81, Column 14905: reference not terminated by REFC delimiter
    …ref='ShowContent.aspx?PageID=642&CatID=316'>An urgent need to include risk-ben…

    If you meant to include an entity that starts with "&", then you should terminate it 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 81, Column 14905: reference to external entity in attribute value
    …ref='ShowContent.aspx?PageID=642&CatID=316'>An urgent need to include risk-ben…

    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 81, Column 14905: reference to entity "CatID" for which no system identifier could be generated
    …ref='ShowContent.aspx?PageID=642&CatID=316'>An urgent need to include risk-ben…

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

  • Info Line 81, Column 13163: entity was defined here
    …i><a href='ShowContent.aspx?PageID=637&CatID=281'>مقالات فارسی </a><ul><li><a …
  • Error Line 81, Column 15061: end tag for "ul" which is not finished
    …ments in cancer patients. </a><ul></ul></li><li><a href='ShowContent.aspx?Page…

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

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

  • Warning Line 81, Column 15113: reference not terminated by REFC delimiter
    …ref='ShowContent.aspx?PageID=642&CatID=317'>Potential of melatonin to treat or…

    If you meant to include an entity that starts with "&", then you should terminate it 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 81, Column 15113: reference to external entity in attribute value
    …ref='ShowContent.aspx?PageID=642&CatID=317'>Potential of melatonin to treat or…

    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 81, Column 15113: reference to entity "CatID" for which no system identifier could be generated
    …ref='ShowContent.aspx?PageID=642&CatID=317'>Potential of melatonin to treat or…

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

  • Info Line 81, Column 13163: entity was defined here
    …i><a href='ShowContent.aspx?PageID=637&CatID=281'>مقالات فارسی </a><ul><li><a …
  • Error Line 81, Column 15251: end tag for "ul" which is not finished
    …n of telomerase activity. </a><ul></ul></li><li><a href='ShowContent.aspx?Page…

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

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

  • Warning Line 81, Column 15303: reference not terminated by REFC delimiter
    …ref='ShowContent.aspx?PageID=642&CatID=318'>High polyphenol, low probiotic die…

    If you meant to include an entity that starts with "&", then you should terminate it 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 81, Column 15303: reference to external entity in attribute value
    …ref='ShowContent.aspx?PageID=642&CatID=318'>High polyphenol, low probiotic die…

    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 81, Column 15303: reference to entity "CatID" for which no system identifier could be generated
    …ref='ShowContent.aspx?PageID=642&CatID=318'>High polyphenol, low probiotic die…

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

  • Info Line 81, Column 13163: entity was defined here
    …i><a href='ShowContent.aspx?PageID=637&CatID=281'>مقالات فارسی </a><ul><li><a …
  • Error Line 81, Column 15419: end tag for "ul" which is not finished
    …l microbiota interaction. </a><ul></ul></li><li><a href='ShowContent.aspx?Page…

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

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

  • Warning Line 81, Column 15471: reference not terminated by REFC delimiter
    …ref='ShowContent.aspx?PageID=642&CatID=319'>Drug policy and treatment bias due…

    If you meant to include an entity that starts with "&", then you should terminate it 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 81, Column 15471: reference to external entity in attribute value
    …ref='ShowContent.aspx?PageID=642&CatID=319'>Drug policy and treatment bias due…

    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 81, Column 15471: reference to entity "CatID" for which no system identifier could be generated
    …ref='ShowContent.aspx?PageID=642&CatID=319'>Drug policy and treatment bias due…

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

  • Info Line 81, Column 13163: entity was defined here
    …i><a href='ShowContent.aspx?PageID=637&CatID=281'>مقالات فارسی </a><ul><li><a …
  • Error Line 81, Column 15606: end tag for "ul" which is not finished
    …t hyperactivity disorder. </a><ul></ul></li><li><a href='ShowContent.aspx?Page…

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

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

  • Warning Line 81, Column 15658: reference not terminated by REFC delimiter
    …ref='ShowContent.aspx?PageID=642&CatID=320'>Drug policy and treatment bias due…

    If you meant to include an entity that starts with "&", then you should terminate it 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 81, Column 15658: reference to external entity in attribute value
    …ref='ShowContent.aspx?PageID=642&CatID=320'>Drug policy and treatment bias due…

    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 81, Column 15658: reference to entity "CatID" for which no system identifier could be generated
    …ref='ShowContent.aspx?PageID=642&CatID=320'>Drug policy and treatment bias due…

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

  • Info Line 81, Column 13163: entity was defined here
    …i><a href='ShowContent.aspx?PageID=637&CatID=281'>مقالات فارسی </a><ul><li><a …
  • Error Line 81, Column 15793: end tag for "ul" which is not finished
    …t hyperactivity disorder. </a><ul></ul></li><li><a href='ShowContent.aspx?Page…

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

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

  • Warning Line 81, Column 15845: reference not terminated by REFC delimiter
    …ref='ShowContent.aspx?PageID=642&CatID=321'>Possible augmentation of photosens…

    If you meant to include an entity that starts with "&", then you should terminate it 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 81, Column 15845: reference to external entity in attribute value
    …ref='ShowContent.aspx?PageID=642&CatID=321'>Possible augmentation of photosens…

    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 81, Column 15845: reference to entity "CatID" for which no system identifier could be generated
    …ref='ShowContent.aspx?PageID=642&CatID=321'>Possible augmentation of photosens…

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

  • Info Line 81, Column 13163: entity was defined here
    …i><a href='ShowContent.aspx?PageID=637&CatID=281'>مقالات فارسی </a><ul><li><a …
  • Error Line 81, Column 15979: end tag for "ul" which is not finished
    …emic lupus erythematosus. </a><ul></ul></li><li><a href='ShowContent.aspx?Page…

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

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

  • Warning Line 81, Column 16031: reference not terminated by REFC delimiter
    …ref='ShowContent.aspx?PageID=642&CatID=322'>Possibility of enhanced risk of re…

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

  • Warning Line 81, Column 16031: reference to external entity in attribute value
    …ref='ShowContent.aspx?PageID=642&CatID=322'>Possibility of enhanced risk of re…

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

  • Error Line 81, Column 16031: reference to entity "CatID" for which no system identifier could be generated
    …ref='ShowContent.aspx?PageID=642&CatID=322'>Possibility of enhanced risk of re…

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

  • Info Line 81, Column 13163: entity was defined here
    …i><a href='ShowContent.aspx?PageID=637&CatID=281'>مقالات فارسی </a><ul><li><a …
  • Error Line 81, Column 16173: end tag for "ul" which is not finished
    …n and retinal alteration. </a><ul></ul></li><li><a href='ShowContent.aspx?Page…

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

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

  • Warning Line 81, Column 16225: reference not terminated by REFC delimiter
    …ref='ShowContent.aspx?PageID=642&CatID=323'>Possibility of enhanced risk of re…

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

  • Warning Line 81, Column 16225: reference to external entity in attribute value
    …ref='ShowContent.aspx?PageID=642&CatID=323'>Possibility of enhanced risk of re…

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

  • Error Line 81, Column 16225: reference to entity "CatID" for which no system identifier could be generated
    …ref='ShowContent.aspx?PageID=642&CatID=323'>Possibility of enhanced risk of re…

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

  • Info Line 81, Column 13163: entity was defined here
    …i><a href='ShowContent.aspx?PageID=637&CatID=281'>مقالات فارسی </a><ul><li><a …
  • Error Line 81, Column 16367: end tag for "ul" which is not finished
    …n and retinal alteration. </a><ul></ul></li><li><a href='ShowContent.aspx?Page…

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

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

  • Warning Line 81, Column 16419: reference not terminated by REFC delimiter
    …ref='ShowContent.aspx?PageID=642&CatID=324'>Potential of melatonin for the tre…

    If you meant to include an entity that starts with "&", then you should terminate it 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 81, Column 16419: reference to external entity in attribute value
    …ref='ShowContent.aspx?PageID=642&CatID=324'>Potential of melatonin for the tre…

    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 81, Column 16419: reference to entity "CatID" for which no system identifier could be generated
    …ref='ShowContent.aspx?PageID=642&CatID=324'>Potential of melatonin for the tre…

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

  • Info Line 81, Column 13163: entity was defined here
    …i><a href='ShowContent.aspx?PageID=637&CatID=281'>مقالات فارسی </a><ul><li><a …
  • Error Line 81, Column 16638: end tag for "ul" which is not finished
    …atients with sleep disord </a><ul></ul></li><li><a href='ShowContent.aspx?Page…

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

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

  • Warning Line 81, Column 16690: reference not terminated by REFC delimiter
    …ref='ShowContent.aspx?PageID=642&CatID=325'>POLI-mix functional food enhances …

    If you meant to include an entity that starts with "&", then you should terminate it 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 81, Column 16690: reference to external entity in attribute value
    …ref='ShowContent.aspx?PageID=642&CatID=325'>POLI-mix functional food enhances …

    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 81, Column 16690: reference to entity "CatID" for which no system identifier could be generated
    …ref='ShowContent.aspx?PageID=642&CatID=325'>POLI-mix functional food enhances …

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

  • Info Line 81, Column 13163: entity was defined here
    …i><a href='ShowContent.aspx?PageID=637&CatID=281'>مقالات فارسی </a><ul><li><a …
  • Error Line 81, Column 16820: end tag for "ul" which is not finished
    …e: an experimental study. </a><ul></ul></li><li><a href='ShowContent.aspx?Page…

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

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

  • Warning Line 81, Column 16872: reference not terminated by REFC delimiter
    …ref='ShowContent.aspx?PageID=642&CatID=326'>Beneficial modulation from a high-…

    If you meant to include an entity that starts with "&", then you should terminate it 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 81, Column 16872: reference to external entity in attribute value
    …ref='ShowContent.aspx?PageID=642&CatID=326'>Beneficial modulation from a high-…

    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 81, Column 16872: reference to entity "CatID" for which no system identifier could be generated
    …ref='ShowContent.aspx?PageID=642&CatID=326'>Beneficial modulation from a high-…

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

  • Info Line 81, Column 13163: entity was defined here
    …i><a href='ShowContent.aspx?PageID=637&CatID=281'>مقالات فارسی </a><ul><li><a …
  • Error Line 81, Column 16986: end tag for "ul" which is not finished
    …chronological skin aging. </a><ul></ul></li><li><a href='ShowContent.aspx?Page…

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

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

  • Warning Line 81, Column 17038: reference not terminated by REFC delimiter
    …ref='ShowContent.aspx?PageID=642&CatID=327'>Vitamin D deficiency and depressio…

    If you meant to include an entity that starts with "&", then you should terminate it 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 81, Column 17038: reference to external entity in attribute value
    …ref='ShowContent.aspx?PageID=642&CatID=327'>Vitamin D deficiency and depressio…

    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 81, Column 17038: reference to entity "CatID" for which no system identifier could be generated
    …ref='ShowContent.aspx?PageID=642&CatID=327'>Vitamin D deficiency and depressio…

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

  • Info Line 81, Column 13163: entity was defined here
    …i><a href='ShowContent.aspx?PageID=637&CatID=281'>مقالات فارسی </a><ul><li><a …
  • Error Line 81, Column 17126: end tag for "ul" which is not finished
    …relationship or artifact? </a><ul></ul></li><li><a href='ShowContent.aspx?Page…

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

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

  • Warning Line 81, Column 17178: reference not terminated by REFC delimiter
    …ref='ShowContent.aspx?PageID=642&CatID=328'>Association between tamoxifen trea…

    If you meant to include an entity that starts with "&", then you should terminate it 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 81, Column 17178: reference to external entity in attribute value
    …ref='ShowContent.aspx?PageID=642&CatID=328'>Association between tamoxifen trea…

    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 81, Column 17178: reference to entity "CatID" for which no system identifier could be generated
    …ref='ShowContent.aspx?PageID=642&CatID=328'>Association between tamoxifen trea…

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

  • Info Line 81, Column 13163: entity was defined here
    …i><a href='ShowContent.aspx?PageID=637&CatID=281'>مقالات فارسی </a><ul><li><a …
  • Error Line 81, Column 17277: end tag for "ul" which is not finished
    …A population-based study. </a><ul></ul></li><li><a href='ShowContent.aspx?Page…

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

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

  • Warning Line 81, Column 17329: reference not terminated by REFC delimiter
    …ref='ShowContent.aspx?PageID=642&CatID=329'>Common pathologic pathways: a sing…

    If you meant to include an entity that starts with "&", then you should terminate it 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 81, Column 17329: reference to external entity in attribute value
    …ref='ShowContent.aspx?PageID=642&CatID=329'>Common pathologic pathways: a sing…

    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 81, Column 17329: reference to entity "CatID" for which no system identifier could be generated
    …ref='ShowContent.aspx?PageID=642&CatID=329'>Common pathologic pathways: a sing…

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

  • Info Line 81, Column 13163: entity was defined here
    …i><a href='ShowContent.aspx?PageID=637&CatID=281'>مقالات فارسی </a><ul><li><a …
  • Error Line 81, Column 17404: end tag for "ul" which is not finished
    …ingle prescription dream? </a><ul></ul></li><li><a href='ShowContent.aspx?Page…

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

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

  • Warning Line 81, Column 17456: reference not terminated by REFC delimiter
    …ref='ShowContent.aspx?PageID=642&CatID=330'>Possibility of enhanced risk of re…

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

  • Warning Line 81, Column 17456: reference to external entity in attribute value
    …ref='ShowContent.aspx?PageID=642&CatID=330'>Possibility of enhanced risk of re…

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

  • Error Line 81, Column 17456: reference to entity "CatID" for which no system identifier could be generated
    …ref='ShowContent.aspx?PageID=642&CatID=330'>Possibility of enhanced risk of re…

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

  • Info Line 81, Column 13163: entity was defined here
    …i><a href='ShowContent.aspx?PageID=637&CatID=281'>مقالات فارسی </a><ul><li><a …
  • Error Line 81, Column 17621: end tag for "ul" which is not finished
    …tin doping: a hypothesis. </a><ul></ul></li><li><a href='ShowContent.aspx?Page…

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

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

  • Warning Line 81, Column 17673: reference not terminated by REFC delimiter
    …ref='ShowContent.aspx?PageID=642&CatID=331'>Beneficial effect of a sturgeon-ba…

    If you meant to include an entity that starts with "&", then you should terminate it 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 81, Column 17673: reference to external entity in attribute value
    …ref='ShowContent.aspx?PageID=642&CatID=331'>Beneficial effect of a sturgeon-ba…

    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 81, Column 17673: reference to entity "CatID" for which no system identifier could be generated
    …ref='ShowContent.aspx?PageID=642&CatID=331'>Beneficial effect of a sturgeon-ba…

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

  • Info Line 81, Column 13163: entity was defined here
    …i><a href='ShowContent.aspx?PageID=637&CatID=281'>مقالات فارسی </a><ul><li><a …
  • Error Line 81, Column 17869: end tag for "ul" which is not finished
    …en in human chondrocytes. </a><ul></ul></li><li><a href='ShowContent.aspx?Page…

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

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

  • Warning Line 81, Column 17921: reference not terminated by REFC delimiter
    …ref='ShowContent.aspx?PageID=642&CatID=332'>Short-term and Mid-term Effects of…

    If you meant to include an entity that starts with "&", then you should terminate it 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 81, Column 17921: reference to external entity in attribute value
    …ref='ShowContent.aspx?PageID=642&CatID=332'>Short-term and Mid-term Effects of…

    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 81, Column 17921: reference to entity "CatID" for which no system identifier could be generated
    …ref='ShowContent.aspx?PageID=642&CatID=332'>Short-term and Mid-term Effects of…

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

  • Info Line 81, Column 13163: entity was defined here
    …i><a href='ShowContent.aspx?PageID=637&CatID=281'>مقالات فارسی </a><ul><li><a …
  • Error Line 81, Column 18049: end tag for "ul" which is not finished
    … in Iranian Fasted Women. </a><ul></ul></li></ul></li></ul></li><li><div class…

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

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

  • Error Line 112, Column 170: required attribute "alt" not specified
    …itorUpload/Images/Banner/banner1.png'/><img style='display:none;margin:10px' w…

    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 112, Column 297: required attribute "alt" not specified
    …ight='275px'  src='UploadImages/EditorUpload/Images/Banner/banner2.png'/></div>

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

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

  • Error Line 117, Column 39: there is no attribute "scrollamount"
                    <marquee scrollamount="2" direction="right" onmouseover="this.s…

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

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

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

  • Error Line 117, Column 53: there is no attribute "direction"
    …  <marquee scrollamount="2" direction="right" onmouseover="this.stop()" onmous…

    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 117, Column 73: there is no attribute "onmouseover"
    …ount="2" direction="right" onmouseover="this.stop()" onmouseout="this.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 117, Column 98: there is no attribute "onmouseout"
    …ount="2" direction="right" onmouseover="this.stop()" onmouseout="this.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 117, Column 112: element "marquee" undefined
    …ount="2" direction="right" onmouseover="this.stop()" onmouseout="this.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 119, Column 76: value of attribute "dir" cannot be "RTL"; must be one of "ltr", "rtl"
    …n: rtl; unicode-bidi: embed;" dir="RTL"> <span> منعطف ترين رژيم های لاغری و لا…

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Error Line 134, Column 76: value of attribute "dir" cannot be "RTL"; must be one of "ltr", "rtl"
    …n: rtl; unicode-bidi: embed;" dir="RTL"> <span lang="AR-SA" style="font-size: …

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Error Line 138, Column 310: value of attribute "dir" cannot be "LTR"; must be one of "ltr", "rtl"
    …d: none repeat scroll 0% 0% white;"> ....</span> <span dir="LTR"> </span> </p> 

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Error Line 538, Column 80: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …Des"><div style="text-align: justify;">      <img   style="float: left;" src="…

    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 538, Column 190: NET-enabling start-tag not immediately followed by null end-tag
    …es/EditorUpload/Images/boshghab.jpg" / alt='رژیم، رژیم لاغری،لاغری موضعی، رژیم…

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

  • Error Line 538, Column 190: required attribute "alt" not specified
    …es/EditorUpload/Images/boshghab.jpg" / alt='رژیم، رژیم لاغری،لاغری موضعی، رژیم…

    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 538, Column 190: end tag for "img" omitted, but OMITTAG NO was specified
    …es/EditorUpload/Images/boshghab.jpg" / alt='رژیم، رژیم لاغری،لاغری موضعی، رژیم…

    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 538, Column 87: start tag was here
    …iv style="text-align: justify;">      <img   style="float: left;" src="http://…
  • Error Line 557, Column 105: required attribute "alt" not specified
    …ages/article.jpg" style="vertical-align: middle" /><span class="3boxspan">آخرین

    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 560, Column 49: there is no attribute "height"
    …                      <marquee height="159px" direction="up" scrollamount="2" …

    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 561, Column 62: element "marquee" undefined
                                        onmouseout="this.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).
  • Warning Line 562, Column 72: cannot generate system identifier for general entity "ArticleID"
    … <a href='ShowContent.aspx?PageID=643&ArticleID=180'>The role of vitamin D in …

    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 562, Column 72: general entity "ArticleID" not defined and no default entity
    … <a href='ShowContent.aspx?PageID=643&ArticleID=180'>The role of vitamin D in …

    This is usually a cascading error caused by 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 562, Column 81: reference not terminated by REFC delimiter
    …'ShowContent.aspx?PageID=643&ArticleID=180'>The role of vitamin D in depressio…

    If you meant to include an entity that starts with "&", then you should terminate it 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 81: reference to external entity in attribute value
    …'ShowContent.aspx?PageID=643&ArticleID=180'>The role of vitamin D in depressio…

    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 81: reference to entity "ArticleID" for which no system identifier could be generated
    …'ShowContent.aspx?PageID=643&ArticleID=180'>The role of vitamin D in depressio…

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

  • Info Line 562, Column 71: entity was defined here
    …  <a href='ShowContent.aspx?PageID=643&ArticleID=180'>The role of vitamin D in…
  • Warning Line 562, Column 224: reference not terminated by REFC delimiter
    …'ShowContent.aspx?PageID=643&ArticleID=179'>Type 2 Diabetes: A Protective Fact…

    If you meant to include an entity that starts with "&", then you should terminate it 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 224: reference to external entity in attribute value
    …'ShowContent.aspx?PageID=643&ArticleID=179'>Type 2 Diabetes: A Protective Fact…

    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 224: reference to entity "ArticleID" for which no system identifier could be generated
    …'ShowContent.aspx?PageID=643&ArticleID=179'>Type 2 Diabetes: A Protective Fact…

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

  • Info Line 562, Column 71: entity was defined here
    …  <a href='ShowContent.aspx?PageID=643&ArticleID=180'>The role of vitamin D in…
  • Warning Line 562, Column 378: reference not terminated by REFC delimiter
    …'ShowContent.aspx?PageID=643&ArticleID=178'>NAFLD: a sign of "early aging"?</a…

    If you meant to include an entity that starts with "&", then you should terminate it 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 378: reference to external entity in attribute value
    …'ShowContent.aspx?PageID=643&ArticleID=178'>NAFLD: a sign of "early aging"?</a…

    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 378: reference to entity "ArticleID" for which no system identifier could be generated
    …'ShowContent.aspx?PageID=643&ArticleID=178'>NAFLD: a sign of "early aging"?</a…

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

  • Info Line 562, Column 71: entity was defined here
    …  <a href='ShowContent.aspx?PageID=643&ArticleID=180'>The role of vitamin D in…
  • Warning Line 562, Column 471: reference not terminated by REFC delimiter
    …'ShowContent.aspx?PageID=643&ArticleID=173'>Excess body weight during pregnanc…

    If you meant to include an entity that starts with "&", then you should terminate it 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 471: reference to external entity in attribute value
    …'ShowContent.aspx?PageID=643&ArticleID=173'>Excess body weight during pregnanc…

    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 471: reference to entity "ArticleID" for which no system identifier could be generated
    …'ShowContent.aspx?PageID=643&ArticleID=173'>Excess body weight during pregnanc…

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

  • Info Line 562, Column 71: entity was defined here
    …  <a href='ShowContent.aspx?PageID=643&ArticleID=180'>The role of vitamin D in…
  • Warning Line 562, Column 612: reference not terminated by REFC delimiter
    …'ShowContent.aspx?PageID=643&ArticleID=172'>Correlates of Snacking with Stress…

    If you meant to include an entity that starts with "&", then you should terminate it 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 612: reference to external entity in attribute value
    …'ShowContent.aspx?PageID=643&ArticleID=172'>Correlates of Snacking with Stress…

    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 612: reference to entity "ArticleID" for which no system identifier could be generated
    …'ShowContent.aspx?PageID=643&ArticleID=172'>Correlates of Snacking with Stress…

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

  • Info Line 562, Column 71: entity was defined here
    …  <a href='ShowContent.aspx?PageID=643&ArticleID=180'>The role of vitamin D in…
  • Warning Line 562, Column 752: reference not terminated by REFC delimiter
    …'ShowContent.aspx?PageID=643&ArticleID=171'>Microbial Metabolism of Polyphenol…

    If you meant to include an entity that starts with "&", then you should terminate it 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 752: reference to external entity in attribute value
    …'ShowContent.aspx?PageID=643&ArticleID=171'>Microbial Metabolism of Polyphenol…

    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 752: reference to entity "ArticleID" for which no system identifier could be generated
    …'ShowContent.aspx?PageID=643&ArticleID=171'>Microbial Metabolism of Polyphenol…

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

  • Info Line 562, Column 71: entity was defined here
    …  <a href='ShowContent.aspx?PageID=643&ArticleID=180'>The role of vitamin D in…
  • Warning Line 562, Column 860: reference not terminated by REFC delimiter
    …'ShowContent.aspx?PageID=643&ArticleID=150'>Understanding the role of gut micr…

    If you meant to include an entity that starts with "&", then you should terminate it 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 860: reference to external entity in attribute value
    …'ShowContent.aspx?PageID=643&ArticleID=150'>Understanding the role of gut micr…

    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 860: reference to entity "ArticleID" for which no system identifier could be generated
    …'ShowContent.aspx?PageID=643&ArticleID=150'>Understanding the role of gut micr…

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

  • Info Line 562, Column 71: entity was defined here
    …  <a href='ShowContent.aspx?PageID=643&ArticleID=180'>The role of vitamin D in…
  • Warning Line 562, Column 1003: reference not terminated by REFC delimiter
    …'ShowContent.aspx?PageID=643&ArticleID=143'>Polyphenol Consumption and Metabol…

    If you meant to include an entity that starts with "&", then you should terminate it 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 1003: reference to external entity in attribute value
    …'ShowContent.aspx?PageID=643&ArticleID=143'>Polyphenol Consumption and Metabol…

    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 1003: reference to entity "ArticleID" for which no system identifier could be generated
    …'ShowContent.aspx?PageID=643&ArticleID=143'>Polyphenol Consumption and Metabol…

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

  • Info Line 562, Column 71: entity was defined here
    …  <a href='ShowContent.aspx?PageID=643&ArticleID=180'>The role of vitamin D in…
  • Warning Line 562, Column 1110: reference not terminated by REFC delimiter
    …'ShowContent.aspx?PageID=643&ArticleID=142'>Food Offerings: A Major Factor Imp…

    If you meant to include an entity that starts with "&", then you should terminate it 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 1110: reference to external entity in attribute value
    …'ShowContent.aspx?PageID=643&ArticleID=142'>Food Offerings: A Major Factor Imp…

    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 1110: reference to entity "ArticleID" for which no system identifier could be generated
    …'ShowContent.aspx?PageID=643&ArticleID=142'>Food Offerings: A Major Factor Imp…

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

  • Info Line 562, Column 71: entity was defined here
    …  <a href='ShowContent.aspx?PageID=643&ArticleID=180'>The role of vitamin D in…
  • Warning Line 562, Column 1239: reference not terminated by REFC delimiter
    …'ShowContent.aspx?PageID=643&ArticleID=117'>Potassium and Arthritis</a><br /><…

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

  • Warning Line 562, Column 1239: reference to external entity in attribute value
    …'ShowContent.aspx?PageID=643&ArticleID=117'>Potassium and Arthritis</a><br /><…

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

  • Error Line 562, Column 1239: reference to entity "ArticleID" for which no system identifier could be generated
    …'ShowContent.aspx?PageID=643&ArticleID=117'>Potassium and Arthritis</a><br /><…

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

  • Info Line 562, Column 71: entity was defined here
    …  <a href='ShowContent.aspx?PageID=643&ArticleID=180'>The role of vitamin D in…
  • Error Line 573, Column 102: required attribute "alt" not specified
    …/images/best.jpg" style="vertical-align: middle" /><span class="3boxspan">افراد

    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 578, Column 122: required attribute "alt" not specified
    …s/UC/Users/4.jpg' style='float:left' />فرشاد حیدری<br /><br />ایشان موفق شدند …

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

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

  • Error Line 578, Column 311: required attribute "alt" not specified
    …ges/no_image.gif' style='float:left' />فرشید حیدری<br /><br />ایشان موفق شدن د…

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

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

  • Error Line 634, Column 24: document type does not allow element "style" here
     <style 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).

Visitor Analysis

Daily Visitor
  • 76 visits

In Page Analysis