مجانا فيلم اباحي، الجنس، الثلاثون ...

pornxnxx.info
  • Domain Name
    pornxnxx.info
  • Favicon
  • Google Page Rank
    0
  • Alexa Rank
    #51820
  • Page Size
    23.1 KB
  • Ip Address
    198.154.240.125
  • Heading
    H1: 1, H2: 3, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    0 GIF, 18 JPG, 0 PNG

Website Meta Analysis

  • Title
    مجانا فيلم اباحي، الجنس، الثلاثون
  • Meta Keyword
    سكس فرنسي بنات صغار, مشاهدة افلام سكس مجانا, بورنوافلام سكس, سكس موفس, مواقع سكس لإيرانيات, فلم سكس نساء تخان, افلام برنو مدبلجه باللغه العربيه, عرب سكسي يتب مقطع لافلام, س
  • Meta Description
    مجانا فيلم اباحي، الجنس، الثلاثون

Technical Analysis

  • Webserver
    Apache
  • Ip Address
    198.154.240.125
  • Domain Age
    1 Years, 10 Months, 25 days.
  • Javascript Library
    yui
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from pornxnxx.info.

HTML Analysis

  • date: Wed, 11 Sep 2013 12:15:28 GMT
  • server: Apache
  • x-powered-by: PHP/5.3.21
  • expires: Thu, 19 Nov 1981 08:52:00 GMT
  • cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
  • pragma: no-cache
  • connection: close
  • content-type: text/html
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for pornxnxx.info

DNS Analysis


DNS servers
ns2.pornxnxx.info [198.154.241.41]
ns1.pornxnxx.info [198.154.240.125]


DNS Records

Answer records
pornxnxx.info TXT v=spf1 ip4:184.173.239.119 a mx include:websitewelcome.com ~all 14400s
pornxnxx.info MX
preference: 0
exchange: pornxnxx.info
14400s
pornxnxx.info SOA
server: ns1.pornxnxx.info
email: anamariatanasie@yahoo.com
serial: 2013020801
refresh: 86400
retry: 7200
expire: 3600000
minimum ttl: 86400
86400s
pornxnxx.info NS  ns2.pornxnxx.info 86400s
pornxnxx.info NS  ns1.pornxnxx.info 86400s
pornxnxx.info A 198.154.240.125 14400s

Authority records

Additional records
pornxnxx.info A 198.154.240.125 14400s
ns1.pornxnxx.info A 198.154.240.125 14400s
ns2.pornxnxx.info A 198.154.241.41 14400s

IP 198.154.240.125 Analysis

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 189 Errors
  • 236 Warnings
Ratio Text/Html
  • 0.756551928532114
Message Error
  • Error Line 10, Column 206: end tag for "meta" omitted, but OMITTAG NO was specified
    …سكس نساء تخان, افلام برنو مدبلجه باللغه العربيه, عرب سكسي يتب مقطع لافلام, س"> 

    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 10, Column 1: start tag was here
    <meta name="keywords" content="سكس فرنسي بنات صغار, مشاهدة افلام سكس مجانا, بور…
  • Error Line 12, Column 70: end tag for "meta" omitted, but OMITTAG NO was specified
    <meta name="description" content="مجانا فيلم اباحي، الجنس، الثلاثون"> 

    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 12, Column 1: start tag was here
    <meta name="description" content="مجانا فيلم اباحي، الجنس، الثلاثون"> 
  • Error Line 14, Column 41: end tag for "meta" omitted, but OMITTAG NO was specified
    <meta name="allow-search" content="yes"> 

    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 14, Column 1: start tag was here
    <meta name="allow-search" content="yes"> 
  • Error Line 16, Column 38: end tag for "meta" omitted, but OMITTAG NO was specified
    <meta name="robots" content="follow"> 

    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 16, Column 1: start tag was here
    <meta name="robots" content="follow"> 
  • Error Line 18, Column 45: end tag for "meta" omitted, but OMITTAG NO was specified
    <meta name="revisit-after" content="1 days"> 

    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 18, Column 1: start tag was here
    <meta name="revisit-after" content="1 days"> 
  • Error Line 46, Column 11: element "center" undefined
    		 <center>

    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 48, Column 15: there is no attribute "width"
    <iframe width="600" scrolling="no" height="450" frameborder="0" marginwidth="0"…

    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 48, Column 31: there is no attribute "scrolling"
    <iframe width="600" scrolling="no" height="450" frameborder="0" marginwidth="0"…

    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 48, Column 43: there is no attribute "height"
    …ame width="600" scrolling="no" height="450" frameborder="0" marginwidth="0" ma…

    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 48, Column 61: there is no attribute "frameborder"
    …rolling="no" height="450" frameborder="0" marginwidth="0" marginheight="0" src…

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

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

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

  • Error Line 48, Column 77: there is no attribute "marginwidth"
    …ght="450" frameborder="0" marginwidth="0" marginheight="0" src="http://alexwap…

    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 48, Column 94: there is no attribute "marginheight"
    …rder="0" marginwidth="0" marginheight="0" src="http://alexwap.net/andrei.html"…

    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 48, Column 102: there is no attribute "src"
    … marginwidth="0" marginheight="0" src="http://alexwap.net/andrei.html" style="…

    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 48, Column 141: there is no attribute "style"
    …"0" src="http://alexwap.net/andrei.html" style="margin-top:25px"></iframe><br/>

    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 48, Column 158: element "iframe" undefined
    …"0" src="http://alexwap.net/andrei.html" style="margin-top:25px"></iframe><br/>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 54, Column 7: end tag for "center" omitted, but OMITTAG NO was specified
    	</div>

    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 46, Column 4: start tag was here
    		 <center>
  • Warning Line 62, Column 63: cannot generate system identifier for general entity "category"
    …tegories</h2><ul><li><a href="/?id=11&category=%D8%A7%D9%84%D9%88%D8%AC%D9%87+…

    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 62, Column 63: general entity "category" not defined and no default entity
    …tegories</h2><ul><li><a href="/?id=11&category=%D8%A7%D9%84%D9%88%D8%AC%D9%87+…

    This is usually a cascading error caused by 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 62, Column 71: reference not terminated by REFC delimiter
    …</h2><ul><li><a href="/?id=11&category=%D8%A7%D9%84%D9%88%D8%AC%D9%87+%D9%81%D…

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

  • Warning Line 62, Column 71: reference to external entity in attribute value
    …</h2><ul><li><a href="/?id=11&category=%D8%A7%D9%84%D9%88%D8%AC%D9%87+%D9%81%D…

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

  • Error Line 62, Column 71: reference to entity "category" for which no system identifier could be generated
    …</h2><ul><li><a href="/?id=11&category=%D8%A7%D9%84%D9%88%D8%AC%D9%87+%D9%81%D…

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

  • Info Line 62, Column 62: entity was defined here
    …ategories</h2><ul><li><a href="/?id=11&category=%D8%A7%D9%84%D9%88%D8%AC%D9%87…
  • Warning Line 62, Column 159: cannot generate system identifier for general entity "option"
    …%D9%85+%D8%A7%D8%A8%D8%A7%D8%AD%D9%8A&option=category&p=1">الوجه فيلم اباحي</a…

    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 62, Column 159: general entity "option" not defined and no default entity
    …%D9%85+%D8%A7%D8%A8%D8%A7%D8%AD%D9%8A&option=category&p=1">الوجه فيلم اباحي</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.

  • Warning Line 62, Column 165: reference not terminated by REFC delimiter
    …+%D8%A7%D8%A8%D8%A7%D8%AD%D9%8A&option=category&p=1">الوجه فيلم اباحي</a></li>…

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

  • Warning Line 62, Column 165: reference to external entity in attribute value
    …+%D8%A7%D8%A8%D8%A7%D8%AD%D9%8A&option=category&p=1">الوجه فيلم اباحي</a></li>…

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

  • Error Line 62, Column 165: reference to entity "option" for which no system identifier could be generated
    …+%D8%A7%D8%A8%D8%A7%D8%AD%D9%8A&option=category&p=1">الوجه فيلم اباحي</a></li>…

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

  • Info Line 62, Column 158: entity was defined here
    …4%D9%85+%D8%A7%D8%A8%D8%A7%D8%AD%D9%8A&option=category&p=1">الوجه فيلم اباحي</…
  • Warning Line 62, Column 175: cannot generate system identifier for general entity "p"
    …%A8%D8%A7%D8%AD%D9%8A&option=category&p=1">الوجه فيلم اباحي</a></li><li><a hre…

    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 62, Column 175: general entity "p" not defined and no default entity
    …%A8%D8%A7%D8%AD%D9%8A&option=category&p=1">الوجه فيلم اباحي</a></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.

  • Warning Line 62, Column 176: reference not terminated by REFC delimiter
    …A8%D8%A7%D8%AD%D9%8A&option=category&p=1">الوجه فيلم اباحي</a></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 62, Column 176: reference to external entity in attribute value
    …A8%D8%A7%D8%AD%D9%8A&option=category&p=1">الوجه فيلم اباحي</a></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 62, Column 176: reference to entity "p" for which no system identifier could be generated
    …A8%D8%A7%D8%AD%D9%8A&option=category&p=1">الوجه فيلم اباحي</a></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 62, Column 174: entity was defined here
    …8%A8%D8%A7%D8%AD%D9%8A&option=category&p=1">الوجه فيلم اباحي</a></li><li><a hr…
  • Warning Line 62, Column 234: reference not terminated by REFC delimiter
    …</a></li><li><a href="/?id=19&category=%D9%81%D9%8A%D9%84%D9%85+%D8%A7%D8%A8%D…

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

  • Warning Line 62, Column 234: reference to external entity in attribute value
    …</a></li><li><a href="/?id=19&category=%D9%81%D9%8A%D9%84%D9%85+%D8%A7%D8%A8%D…

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

  • Error Line 62, Column 234: reference to entity "category" for which no system identifier could be generated
    …</a></li><li><a href="/?id=19&category=%D9%81%D9%8A%D9%84%D9%85+%D8%A7%D8%A8%D…

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

  • Info Line 62, Column 62: entity was defined here
    …ategories</h2><ul><li><a href="/?id=11&category=%D8%A7%D9%84%D9%88%D8%AC%D9%87…
  • Warning Line 62, Column 340: reference not terminated by REFC delimiter
    …3%D8%AA%D9%85%D9%86%D8%A7%D8%A1&option=category&p=1">فيلم اباحي استمناء</a></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 62, Column 340: reference to external entity in attribute value
    …3%D8%AA%D9%85%D9%86%D8%A7%D8%A1&option=category&p=1">فيلم اباحي استمناء</a></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 62, Column 340: reference to entity "option" for which no system identifier could be generated
    …3%D8%AA%D9%85%D9%86%D8%A7%D8%A1&option=category&p=1">فيلم اباحي استمناء</a></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 62, Column 158: entity was defined here
    …4%D9%85+%D8%A7%D8%A8%D8%A7%D8%AD%D9%8A&option=category&p=1">الوجه فيلم اباحي</…
  • Warning Line 62, Column 351: reference not terminated by REFC delimiter
    …85%D9%86%D8%A7%D8%A1&option=category&p=1">فيلم اباحي استمناء</a></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 62, Column 351: reference to external entity in attribute value
    …85%D9%86%D8%A7%D8%A1&option=category&p=1">فيلم اباحي استمناء</a></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 62, Column 351: reference to entity "p" for which no system identifier could be generated
    …85%D9%86%D8%A7%D8%A1&option=category&p=1">فيلم اباحي استمناء</a></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 62, Column 174: entity was defined here
    …8%A8%D8%A7%D8%AD%D9%8A&option=category&p=1">الوجه فيلم اباحي</a></li><li><a hr…
  • Warning Line 62, Column 410: reference not terminated by REFC delimiter
    …ء</a></li><li><a href="/?id=5&category=%D9%81%D9%8A%D9%84%D9%85+%D8%A7%D8%A8%D…

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

  • Warning Line 62, Column 410: reference to external entity in attribute value
    …ء</a></li><li><a href="/?id=5&category=%D9%81%D9%8A%D9%84%D9%85+%D8%A7%D8%A8%D…

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

  • Error Line 62, Column 410: reference to entity "category" for which no system identifier could be generated
    …ء</a></li><li><a href="/?id=5&category=%D9%81%D9%8A%D9%84%D9%85+%D8%A7%D8%A8%D…

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

  • Info Line 62, Column 62: entity was defined here
    …ategories</h2><ul><li><a href="/?id=11&category=%D8%A7%D9%84%D9%88%D8%AC%D9%87…
  • Warning Line 62, Column 522: reference not terminated by REFC delimiter
    …2%D8%B3%D9%8A%D9%88%D9%8A%D8%A9&option=category&p=1">فيلم اباحي الآسيوية</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 62, Column 522: reference to external entity in attribute value
    …2%D8%B3%D9%8A%D9%88%D9%8A%D8%A9&option=category&p=1">فيلم اباحي الآسيوية</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 62, Column 522: reference to entity "option" for which no system identifier could be generated
    …2%D8%B3%D9%8A%D9%88%D9%8A%D8%A9&option=category&p=1">فيلم اباحي الآسيوية</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 62, Column 158: entity was defined here
    …4%D9%85+%D8%A7%D8%A8%D8%A7%D8%AD%D9%8A&option=category&p=1">الوجه فيلم اباحي</…
  • Warning Line 62, Column 533: reference not terminated by REFC delimiter
    …8A%D9%88%D9%8A%D8%A9&option=category&p=1">فيلم اباحي الآسيوية</a></li><li><a h…

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

  • Warning Line 62, Column 533: reference to external entity in attribute value
    …8A%D9%88%D9%8A%D8%A9&option=category&p=1">فيلم اباحي الآسيوية</a></li><li><a h…

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

  • Error Line 62, Column 533: reference to entity "p" for which no system identifier could be generated
    …8A%D9%88%D9%8A%D8%A9&option=category&p=1">فيلم اباحي الآسيوية</a></li><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.

  • Info Line 62, Column 174: entity was defined here
    …8%A8%D8%A7%D8%AD%D9%8A&option=category&p=1">الوجه فيلم اباحي</a></li><li><a hr…
  • Warning Line 62, Column 594: reference not terminated by REFC delimiter
    …</a></li><li><a href="/?id=10&category=%D9%81%D9%8A%D9%84%D9%85+%D8%A7%D8%A8%D…

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

  • Warning Line 62, Column 594: reference to external entity in attribute value
    …</a></li><li><a href="/?id=10&category=%D9%81%D9%8A%D9%84%D9%85+%D8%A7%D8%A8%D…

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

  • Error Line 62, Column 594: reference to entity "category" for which no system identifier could be generated
    …</a></li><li><a href="/?id=10&category=%D9%81%D9%8A%D9%84%D9%85+%D8%A7%D8%A8%D…

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

  • Info Line 62, Column 62: entity was defined here
    …ategories</h2><ul><li><a href="/?id=11&category=%D8%A7%D9%84%D9%88%D8%AC%D9%87…
  • Warning Line 62, Column 700: reference not terminated by REFC delimiter
    …4%D8%A3%D8%A8%D9%86%D9%88%D8%B3&option=category&p=1">فيلم اباحي الأبنوس</a></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 62, Column 700: reference to external entity in attribute value
    …4%D8%A3%D8%A8%D9%86%D9%88%D8%B3&option=category&p=1">فيلم اباحي الأبنوس</a></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 62, Column 700: reference to entity "option" for which no system identifier could be generated
    …4%D8%A3%D8%A8%D9%86%D9%88%D8%B3&option=category&p=1">فيلم اباحي الأبنوس</a></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 62, Column 158: entity was defined here
    …4%D9%85+%D8%A7%D8%A8%D8%A7%D8%AD%D9%8A&option=category&p=1">الوجه فيلم اباحي</…
  • Warning Line 62, Column 711: reference not terminated by REFC delimiter
    …A8%D9%86%D9%88%D8%B3&option=category&p=1">فيلم اباحي الأبنوس</a></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 62, Column 711: reference to external entity in attribute value
    …A8%D9%86%D9%88%D8%B3&option=category&p=1">فيلم اباحي الأبنوس</a></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 62, Column 711: reference to entity "p" for which no system identifier could be generated
    …A8%D9%86%D9%88%D8%B3&option=category&p=1">فيلم اباحي الأبنوس</a></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 62, Column 174: entity was defined here
    …8%A8%D8%A7%D8%AD%D9%8A&option=category&p=1">الوجه فيلم اباحي</a></li><li><a hr…
  • Warning Line 62, Column 771: reference not terminated by REFC delimiter
    …</a></li><li><a href="/?id=22&category=%D9%81%D9%8A%D9%84%D9%85+%D8%A7%D8%A8%D…

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

  • Warning Line 62, Column 771: reference to external entity in attribute value
    …</a></li><li><a href="/?id=22&category=%D9%81%D9%8A%D9%84%D9%85+%D8%A7%D8%A8%D…

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

  • Error Line 62, Column 771: reference to entity "category" for which no system identifier could be generated
    …</a></li><li><a href="/?id=22&category=%D9%81%D9%8A%D9%84%D9%85+%D8%A7%D8%A8%D…

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

  • Info Line 62, Column 62: entity was defined here
    …ategories</h2><ul><li><a href="/?id=11&category=%D8%A7%D9%84%D9%88%D8%AC%D9%87…
  • Warning Line 62, Column 871: reference not terminated by REFC delimiter
    …7%D9%84%D8%AA%D8%AF%D9%81%D9%82&option=category&p=1">فيلم اباحي التدفق</a></li…

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

  • Warning Line 62, Column 871: reference to external entity in attribute value
    …7%D9%84%D8%AA%D8%AF%D9%81%D9%82&option=category&p=1">فيلم اباحي التدفق</a></li…

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

  • Error Line 62, Column 871: reference to entity "option" for which no system identifier could be generated
    …7%D9%84%D8%AA%D8%AF%D9%81%D9%82&option=category&p=1">فيلم اباحي التدفق</a></li…

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

  • Info Line 62, Column 158: entity was defined here
    …4%D9%85+%D8%A7%D8%A8%D8%A7%D8%AD%D9%8A&option=category&p=1">الوجه فيلم اباحي</…
  • Warning Line 62, Column 882: reference not terminated by REFC delimiter
    …AA%D8%AF%D9%81%D9%82&option=category&p=1">فيلم اباحي التدفق</a></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 62, Column 882: reference to external entity in attribute value
    …AA%D8%AF%D9%81%D9%82&option=category&p=1">فيلم اباحي التدفق</a></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 62, Column 882: reference to entity "p" for which no system identifier could be generated
    …AA%D8%AF%D9%81%D9%82&option=category&p=1">فيلم اباحي التدفق</a></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 62, Column 174: entity was defined here
    …8%A8%D8%A7%D8%AD%D9%8A&option=category&p=1">الوجه فيلم اباحي</a></li><li><a hr…
  • Warning Line 62, Column 941: reference not terminated by REFC delimiter
    …</a></li><li><a href="/?id=21&category=%D9%81%D9%8A%D9%84%D9%85+%D8%A7%D8%A8%D…

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

  • Warning Line 62, Column 941: reference to external entity in attribute value
    …</a></li><li><a href="/?id=21&category=%D9%81%D9%8A%D9%84%D9%85+%D8%A7%D8%A8%D…

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

  • Error Line 62, Column 941: reference to entity "category" for which no system identifier could be generated
    …</a></li><li><a href="/?id=21&category=%D9%81%D9%8A%D9%84%D9%85+%D8%A7%D8%A8%D…

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

  • Info Line 62, Column 62: entity was defined here
    …ategories</h2><ul><li><a href="/?id=11&category=%D8%A7%D9%84%D9%88%D8%AC%D9%87…
  • Warning Line 62, Column 1041: reference not terminated by REFC delimiter
    …7%D9%84%D8%B9%D8%A7%D9%85%D8%A9&option=category&p=1">فيلم اباحي العامة</a></li…

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

  • Warning Line 62, Column 1041: reference to external entity in attribute value
    …7%D9%84%D8%B9%D8%A7%D9%85%D8%A9&option=category&p=1">فيلم اباحي العامة</a></li…

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

  • Error Line 62, Column 1041: reference to entity "option" for which no system identifier could be generated
    …7%D9%84%D8%B9%D8%A7%D9%85%D8%A9&option=category&p=1">فيلم اباحي العامة</a></li…

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

  • Info Line 62, Column 158: entity was defined here
    …4%D9%85+%D8%A7%D8%A8%D8%A7%D8%AD%D9%8A&option=category&p=1">الوجه فيلم اباحي</…
  • Warning Line 62, Column 1052: reference not terminated by REFC delimiter
    …B9%D8%A7%D9%85%D8%A9&option=category&p=1">فيلم اباحي العامة</a></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 62, Column 1052: reference to external entity in attribute value
    …B9%D8%A7%D9%85%D8%A9&option=category&p=1">فيلم اباحي العامة</a></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 62, Column 1052: reference to entity "p" for which no system identifier could be generated
    …B9%D8%A7%D9%85%D8%A9&option=category&p=1">فيلم اباحي العامة</a></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 62, Column 174: entity was defined here
    …8%A8%D8%A7%D8%AD%D9%8A&option=category&p=1">الوجه فيلم اباحي</a></li><li><a hr…
  • Warning Line 62, Column 1110: reference not terminated by REFC delimiter
    …ة</a></li><li><a href="/?id=8&category=%D9%81%D9%8A%D9%84%D9%85+%D8%A7%D8%A8%D…

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

  • Warning Line 62, Column 1110: reference to external entity in attribute value
    …ة</a></li><li><a href="/?id=8&category=%D9%81%D9%8A%D9%84%D9%85+%D8%A7%D8%A8%D…

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

  • Error Line 62, Column 1110: reference to entity "category" for which no system identifier could be generated
    …ة</a></li><li><a href="/?id=8&category=%D9%81%D9%8A%D9%84%D9%85+%D8%A7%D8%A8%D…

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

  • Info Line 62, Column 62: entity was defined here
    …ategories</h2><ul><li><a href="/?id=11&category=%D8%A7%D9%84%D9%88%D8%AC%D9%87…
  • Warning Line 62, Column 1210: reference not terminated by REFC delimiter
    …7%D9%84%D9%84%D8%B3%D8%A7%D9%86&option=category&p=1">فيلم اباحي اللسان</a></li…

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

  • Warning Line 62, Column 1210: reference to external entity in attribute value
    …7%D9%84%D9%84%D8%B3%D8%A7%D9%86&option=category&p=1">فيلم اباحي اللسان</a></li…

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

  • Error Line 62, Column 1210: reference to entity "option" for which no system identifier could be generated
    …7%D9%84%D9%84%D8%B3%D8%A7%D9%86&option=category&p=1">فيلم اباحي اللسان</a></li…

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

  • Info Line 62, Column 158: entity was defined here
    …4%D9%85+%D8%A7%D8%A8%D8%A7%D8%AD%D9%8A&option=category&p=1">الوجه فيلم اباحي</…
  • Warning Line 62, Column 1221: reference not terminated by REFC delimiter
    …84%D8%B3%D8%A7%D9%86&option=category&p=1">فيلم اباحي اللسان</a></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 62, Column 1221: reference to external entity in attribute value
    …84%D8%B3%D8%A7%D9%86&option=category&p=1">فيلم اباحي اللسان</a></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 62, Column 1221: reference to entity "p" for which no system identifier could be generated
    …84%D8%B3%D8%A7%D9%86&option=category&p=1">فيلم اباحي اللسان</a></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 62, Column 174: entity was defined here
    …8%A8%D8%A7%D8%AD%D9%8A&option=category&p=1">الوجه فيلم اباحي</a></li><li><a hr…
  • Warning Line 62, Column 1280: reference not terminated by REFC delimiter
    …</a></li><li><a href="/?id=20&category=%D9%81%D9%8A%D9%84%D9%85+%D8%A7%D8%A8%D…

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

  • Warning Line 62, Column 1280: reference to external entity in attribute value
    …</a></li><li><a href="/?id=20&category=%D9%81%D9%8A%D9%84%D9%85+%D8%A7%D8%A8%D…

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

  • Error Line 62, Column 1280: reference to entity "category" for which no system identifier could be generated
    …</a></li><li><a href="/?id=20&category=%D9%81%D9%8A%D9%84%D9%85+%D8%A7%D8%A8%D…

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

  • Info Line 62, Column 62: entity was defined here
    …ategories</h2><ul><li><a href="/?id=11&category=%D8%A7%D9%84%D9%88%D8%AC%D9%87…
  • Warning Line 62, Column 1386: reference not terminated by REFC delimiter
    …4%D9%86%D8%A7%D8%B6%D8%AC%D8%A9&option=category&p=1">فيلم اباحي الناضجة</a></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 62, Column 1386: reference to external entity in attribute value
    …4%D9%86%D8%A7%D8%B6%D8%AC%D8%A9&option=category&p=1">فيلم اباحي الناضجة</a></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 62, Column 1386: reference to entity "option" for which no system identifier could be generated
    …4%D9%86%D8%A7%D8%B6%D8%AC%D8%A9&option=category&p=1">فيلم اباحي الناضجة</a></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 62, Column 158: entity was defined here
    …4%D9%85+%D8%A7%D8%A8%D8%A7%D8%AD%D9%8A&option=category&p=1">الوجه فيلم اباحي</…
  • Warning Line 62, Column 1397: reference not terminated by REFC delimiter
    …A7%D8%B6%D8%AC%D8%A9&option=category&p=1">فيلم اباحي الناضجة</a></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 62, Column 1397: reference to external entity in attribute value
    …A7%D8%B6%D8%AC%D8%A9&option=category&p=1">فيلم اباحي الناضجة</a></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 62, Column 1397: reference to entity "p" for which no system identifier could be generated
    …A7%D8%B6%D8%AC%D8%A9&option=category&p=1">فيلم اباحي الناضجة</a></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 62, Column 174: entity was defined here
    …8%A8%D8%A7%D8%AD%D9%8A&option=category&p=1">الوجه فيلم اباحي</a></li><li><a hr…
  • Warning Line 62, Column 1456: reference not terminated by REFC delimiter
    …ة</a></li><li><a href="/?id=3&category=%D9%81%D9%8A%D9%84%D9%85+%D8%A7%D8%A8%D…

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

  • Warning Line 62, Column 1456: reference to external entity in attribute value
    …ة</a></li><li><a href="/?id=3&category=%D9%81%D9%8A%D9%84%D9%85+%D8%A7%D8%A8%D…

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

  • Error Line 62, Column 1456: reference to entity "category" for which no system identifier could be generated
    …ة</a></li><li><a href="/?id=3&category=%D9%81%D9%8A%D9%84%D9%85+%D8%A7%D8%A8%D…

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

  • Info Line 62, Column 62: entity was defined here
    …ategories</h2><ul><li><a href="/?id=11&category=%D8%A7%D9%84%D9%88%D8%AC%D9%87…
  • Warning Line 62, Column 1556: reference not terminated by REFC delimiter
    …7%D9%84%D9%87%D9%88%D8%A7%D8%A9&option=category&p=1">فيلم اباحي الهواة</a></li…

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

  • Warning Line 62, Column 1556: reference to external entity in attribute value
    …7%D9%84%D9%87%D9%88%D8%A7%D8%A9&option=category&p=1">فيلم اباحي الهواة</a></li…

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

  • Error Line 62, Column 1556: reference to entity "option" for which no system identifier could be generated
    …7%D9%84%D9%87%D9%88%D8%A7%D8%A9&option=category&p=1">فيلم اباحي الهواة</a></li…

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

  • Info Line 62, Column 158: entity was defined here
    …4%D9%85+%D8%A7%D8%A8%D8%A7%D8%AD%D9%8A&option=category&p=1">الوجه فيلم اباحي</…
  • Warning Line 62, Column 1567: reference not terminated by REFC delimiter
    …87%D9%88%D8%A7%D8%A9&option=category&p=1">فيلم اباحي الهواة</a></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 62, Column 1567: reference to external entity in attribute value
    …87%D9%88%D8%A7%D8%A9&option=category&p=1">فيلم اباحي الهواة</a></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 62, Column 1567: reference to entity "p" for which no system identifier could be generated
    …87%D9%88%D8%A7%D8%A9&option=category&p=1">فيلم اباحي الهواة</a></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 62, Column 174: entity was defined here
    …8%A8%D8%A7%D8%AD%D9%8A&option=category&p=1">الوجه فيلم اباحي</a></li><li><a hr…
  • Warning Line 62, Column 1626: reference not terminated by REFC delimiter
    …</a></li><li><a href="/?id=12&category=%D9%81%D9%8A%D9%84%D9%85+%D8%A7%D8%A8%D…

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

  • Warning Line 62, Column 1626: reference to external entity in attribute value
    …</a></li><li><a href="/?id=12&category=%D9%81%D9%8A%D9%84%D9%85+%D8%A7%D8%A8%D…

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

  • Error Line 62, Column 1626: reference to entity "category" for which no system identifier could be generated
    …</a></li><li><a href="/?id=12&category=%D9%81%D9%8A%D9%84%D9%85+%D8%A7%D8%A8%D…

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

  • Info Line 62, Column 62: entity was defined here
    …ategories</h2><ul><li><a href="/?id=11&category=%D8%A7%D9%84%D9%88%D8%AC%D9%87…
  • Warning Line 62, Column 1720: reference not terminated by REFC delimiter
    …+%D8%A7%D9%84%D9%88%D8%AB%D9%86&option=category&p=1">فيلم اباحي الوثن</a></li>…

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

  • Warning Line 62, Column 1720: reference to external entity in attribute value
    …+%D8%A7%D9%84%D9%88%D8%AB%D9%86&option=category&p=1">فيلم اباحي الوثن</a></li>…

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

  • Error Line 62, Column 1720: reference to entity "option" for which no system identifier could be generated
    …+%D8%A7%D9%84%D9%88%D8%AB%D9%86&option=category&p=1">فيلم اباحي الوثن</a></li>…

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

  • Info Line 62, Column 158: entity was defined here
    …4%D9%85+%D8%A7%D8%A8%D8%A7%D8%AD%D9%8A&option=category&p=1">الوجه فيلم اباحي</…
  • Warning Line 62, Column 1731: reference not terminated by REFC delimiter
    …84%D9%88%D8%AB%D9%86&option=category&p=1">فيلم اباحي الوثن</a></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 62, Column 1731: reference to external entity in attribute value
    …84%D9%88%D8%AB%D9%86&option=category&p=1">فيلم اباحي الوثن</a></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 62, Column 1731: reference to entity "p" for which no system identifier could be generated
    …84%D9%88%D8%AB%D9%86&option=category&p=1">فيلم اباحي الوثن</a></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 62, Column 174: entity was defined here
    …8%A8%D8%A7%D8%AD%D9%8A&option=category&p=1">الوجه فيلم اباحي</a></li><li><a hr…
  • Warning Line 62, Column 1788: reference not terminated by REFC delimiter
    …ن</a></li><li><a href="/?id=4&category=%D9%81%D9%8A%D9%84%D9%85+%D8%A7%D8%A8%D…

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

  • Warning Line 62, Column 1788: reference to external entity in attribute value
    …ن</a></li><li><a href="/?id=4&category=%D9%81%D9%8A%D9%84%D9%85+%D8%A7%D8%A8%D…

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

  • Error Line 62, Column 1788: reference to entity "category" for which no system identifier could be generated
    …ن</a></li><li><a href="/?id=4&category=%D9%81%D9%8A%D9%84%D9%85+%D8%A7%D8%A8%D…

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

  • Info Line 62, Column 62: entity was defined here
    …ategories</h2><ul><li><a href="/?id=11&category=%D8%A7%D9%84%D9%88%D8%AC%D9%87…
  • Warning Line 62, Column 1876: reference not terminated by REFC delimiter
    …%D9%8A+%D8%B4%D8%B1%D8%AC%D9%8A&option=category&p=1">فيلم اباحي شرجي</a></li><…

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

  • Warning Line 62, Column 1876: reference to external entity in attribute value
    …%D9%8A+%D8%B4%D8%B1%D8%AC%D9%8A&option=category&p=1">فيلم اباحي شرجي</a></li><…

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

  • Error Line 62, Column 1876: reference to entity "option" for which no system identifier could be generated
    …%D9%8A+%D8%B4%D8%B1%D8%AC%D9%8A&option=category&p=1">فيلم اباحي شرجي</a></li><…

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

  • Info Line 62, Column 158: entity was defined here
    …4%D9%85+%D8%A7%D8%A8%D8%A7%D8%AD%D9%8A&option=category&p=1">الوجه فيلم اباحي</…
  • Warning Line 62, Column 1887: reference not terminated by REFC delimiter
    …B4%D8%B1%D8%AC%D9%8A&option=category&p=1">فيلم اباحي شرجي</a></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 62, Column 1887: reference to external entity in attribute value
    …B4%D8%B1%D8%AC%D9%8A&option=category&p=1">فيلم اباحي شرجي</a></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 62, Column 1887: reference to entity "p" for which no system identifier could be generated
    …B4%D8%B1%D8%AC%D9%8A&option=category&p=1">فيلم اباحي شرجي</a></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 62, Column 174: entity was defined here
    …8%A8%D8%A7%D8%AD%D9%8A&option=category&p=1">الوجه فيلم اباحي</a></li><li><a hr…
  • Warning Line 62, Column 1943: reference not terminated by REFC delimiter
    …ي</a></li><li><a href="/?id=6&category=%D9%81%D9%8A%D9%84%D9%85+%D8%A7%D8%A8%D…

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

  • Warning Line 62, Column 1943: reference to external entity in attribute value
    …ي</a></li><li><a href="/?id=6&category=%D9%81%D9%8A%D9%84%D9%85+%D8%A7%D8%A8%D…

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

  • Error Line 62, Column 1943: reference to entity "category" for which no system identifier could be generated
    …ي</a></li><li><a href="/?id=6&category=%D9%81%D9%8A%D9%84%D9%85+%D8%A7%D8%A8%D…

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

  • Info Line 62, Column 62: entity was defined here
    …ategories</h2><ul><li><a href="/?id=11&category=%D8%A7%D9%84%D9%88%D8%AC%D9%87…
  • Warning Line 62, Column 2037: reference not terminated by REFC delimiter
    …+%D9%81%D8%A7%D8%AA%D9%86%D8%A9&option=category&p=1">فيلم اباحي فاتنة</a></li>…

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

  • Warning Line 62, Column 2037: reference to external entity in attribute value
    …+%D9%81%D8%A7%D8%AA%D9%86%D8%A9&option=category&p=1">فيلم اباحي فاتنة</a></li>…

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

  • Error Line 62, Column 2037: reference to entity "option" for which no system identifier could be generated
    …+%D9%81%D8%A7%D8%AA%D9%86%D8%A9&option=category&p=1">فيلم اباحي فاتنة</a></li>…

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

  • Info Line 62, Column 158: entity was defined here
    …4%D9%85+%D8%A7%D8%A8%D8%A7%D8%AD%D9%8A&option=category&p=1">الوجه فيلم اباحي</…
  • Warning Line 62, Column 2048: reference not terminated by REFC delimiter
    …A7%D8%AA%D9%86%D8%A9&option=category&p=1">فيلم اباحي فاتنة</a></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 62, Column 2048: reference to external entity in attribute value
    …A7%D8%AA%D9%86%D8%A9&option=category&p=1">فيلم اباحي فاتنة</a></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 62, Column 2048: reference to entity "p" for which no system identifier could be generated
    …A7%D8%AA%D9%86%D8%A9&option=category&p=1">فيلم اباحي فاتنة</a></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 62, Column 174: entity was defined here
    …8%A8%D8%A7%D8%AD%D9%8A&option=category&p=1">الوجه فيلم اباحي</a></li><li><a hr…
  • Warning Line 62, Column 2105: reference not terminated by REFC delimiter
    …ة</a></li><li><a href="/?id=7&category=%D9%81%D9%8A%D9%84%D9%85+%D8%A7%D8%A8%D…

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

  • Warning Line 62, Column 2105: reference to external entity in attribute value
    …ة</a></li><li><a href="/?id=7&category=%D9%81%D9%8A%D9%84%D9%85+%D8%A7%D8%A8%D…

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

  • Error Line 62, Column 2105: reference to entity "category" for which no system identifier could be generated
    …ة</a></li><li><a href="/?id=7&category=%D9%81%D9%8A%D9%84%D9%85+%D8%A7%D8%A8%D…

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

  • Info Line 62, Column 62: entity was defined here
    …ategories</h2><ul><li><a href="/?id=11&category=%D8%A7%D9%84%D9%88%D8%AC%D9%87…
  • Warning Line 62, Column 2224: reference not terminated by REFC delimiter
    …+%D8%A7%D9%84%D8%AB%D8%AF%D9%8A&option=category&p=1">فيلم اباحي كبير الثدي</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 62, Column 2224: reference to external entity in attribute value
    …+%D8%A7%D9%84%D8%AB%D8%AF%D9%8A&option=category&p=1">فيلم اباحي كبير الثدي</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 62, Column 2224: reference to entity "option" for which no system identifier could be generated
    …+%D8%A7%D9%84%D8%AB%D8%AF%D9%8A&option=category&p=1">فيلم اباحي كبير الثدي</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 62, Column 158: entity was defined here
    …4%D9%85+%D8%A7%D8%A8%D8%A7%D8%AD%D9%8A&option=category&p=1">الوجه فيلم اباحي</…
  • Warning Line 62, Column 2235: reference not terminated by REFC delimiter
    …84%D8%AB%D8%AF%D9%8A&option=category&p=1">فيلم اباحي كبير الثدي</a></li><li><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 62, Column 2235: reference to external entity in attribute value
    …84%D8%AB%D8%AF%D9%8A&option=category&p=1">فيلم اباحي كبير الثدي</a></li><li><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 62, Column 2235: reference to entity "p" for which no system identifier could be generated
    …84%D8%AB%D8%AF%D9%8A&option=category&p=1">فيلم اباحي كبير الثدي</a></li><li><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 62, Column 174: entity was defined here
    …8%A8%D8%A7%D8%AD%D9%8A&option=category&p=1">الوجه فيلم اباحي</a></li><li><a hr…
  • Warning Line 62, Column 2298: reference not terminated by REFC delimiter
    …</a></li><li><a href="/?id=17&category=%D9%81%D9%8A%D9%84%D9%85+%D8%A7%D8%A8%D…

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

  • Warning Line 62, Column 2298: reference to external entity in attribute value
    …</a></li><li><a href="/?id=17&category=%D9%81%D9%8A%D9%84%D9%85+%D8%A7%D8%A8%D…

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

  • Error Line 62, Column 2298: reference to entity "category" for which no system identifier could be generated
    …</a></li><li><a href="/?id=17&category=%D9%81%D9%8A%D9%84%D9%85+%D8%A7%D8%A8%D…

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

  • Info Line 62, Column 62: entity was defined here
    …ategories</h2><ul><li><a href="/?id=11&category=%D8%A7%D9%84%D9%88%D8%AC%D9%87…
  • Warning Line 62, Column 2398: reference not terminated by REFC delimiter
    …4%D8%A7%D8%AA%D9%8A%D9%86%D8%A7&option=category&p=1">فيلم اباحي لاتينا</a></li…

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

  • Warning Line 62, Column 2398: reference to external entity in attribute value
    …4%D8%A7%D8%AA%D9%8A%D9%86%D8%A7&option=category&p=1">فيلم اباحي لاتينا</a></li…

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

  • Error Line 62, Column 2398: reference to entity "option" for which no system identifier could be generated
    …4%D8%A7%D8%AA%D9%8A%D9%86%D8%A7&option=category&p=1">فيلم اباحي لاتينا</a></li…

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

  • Info Line 62, Column 158: entity was defined here
    …4%D9%85+%D8%A7%D8%A8%D8%A7%D8%AD%D9%8A&option=category&p=1">الوجه فيلم اباحي</…
  • Warning Line 62, Column 2409: reference not terminated by REFC delimiter
    …AA%D9%8A%D9%86%D8%A7&option=category&p=1">فيلم اباحي لاتينا</a></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 62, Column 2409: reference to external entity in attribute value
    …AA%D9%8A%D9%86%D8%A7&option=category&p=1">فيلم اباحي لاتينا</a></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 62, Column 2409: reference to entity "p" for which no system identifier could be generated
    …AA%D9%8A%D9%86%D8%A7&option=category&p=1">فيلم اباحي لاتينا</a></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 62, Column 174: entity was defined here
    …8%A8%D8%A7%D8%AD%D9%8A&option=category&p=1">الوجه فيلم اباحي</a></li><li><a hr…
  • Warning Line 62, Column 2468: reference not terminated by REFC delimiter
    …</a></li><li><a href="/?id=18&category=%D9%81%D9%8A%D9%84%D9%85+%D8%A7%D8%A8%D…

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

  • Warning Line 62, Column 2468: reference to external entity in attribute value
    …</a></li><li><a href="/?id=18&category=%D9%81%D9%8A%D9%84%D9%85+%D8%A7%D8%A8%D…

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

  • Error Line 62, Column 2468: reference to entity "category" for which no system identifier could be generated
    …</a></li><li><a href="/?id=18&category=%D9%81%D9%8A%D9%84%D9%85+%D8%A7%D8%A8%D…

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

  • Info Line 62, Column 62: entity was defined here
    …ategories</h2><ul><li><a href="/?id=11&category=%D8%A7%D9%84%D9%88%D8%AC%D9%87…
  • Warning Line 62, Column 2562: reference not terminated by REFC delimiter
    …+%D9%85%D8%AB%D9%84%D9%8A%D9%87&option=category&p=1">فيلم اباحي مثليه</a></li>…

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

  • Warning Line 62, Column 2562: reference to external entity in attribute value
    …+%D9%85%D8%AB%D9%84%D9%8A%D9%87&option=category&p=1">فيلم اباحي مثليه</a></li>…

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

  • Error Line 62, Column 2562: reference to entity "option" for which no system identifier could be generated
    …+%D9%85%D8%AB%D9%84%D9%8A%D9%87&option=category&p=1">فيلم اباحي مثليه</a></li>…

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

  • Info Line 62, Column 158: entity was defined here
    …4%D9%85+%D8%A7%D8%A8%D8%A7%D8%AD%D9%8A&option=category&p=1">الوجه فيلم اباحي</…
  • Warning Line 62, Column 2573: reference not terminated by REFC delimiter
    …AB%D9%84%D9%8A%D9%87&option=category&p=1">فيلم اباحي مثليه</a></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 62, Column 2573: reference to external entity in attribute value
    …AB%D9%84%D9%8A%D9%87&option=category&p=1">فيلم اباحي مثليه</a></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 62, Column 2573: reference to entity "p" for which no system identifier could be generated
    …AB%D9%84%D9%8A%D9%87&option=category&p=1">فيلم اباحي مثليه</a></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 62, Column 174: entity was defined here
    …8%A8%D8%A7%D8%AD%D9%8A&option=category&p=1">الوجه فيلم اباحي</a></li><li><a hr…
  • Warning Line 62, Column 2631: reference not terminated by REFC delimiter
    …</a></li><li><a href="/?id=14&category=%D9%81%D9%8A%D9%84%D9%85+%D8%A7%D8%A8%D…

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

  • Warning Line 62, Column 2631: reference to external entity in attribute value
    …</a></li><li><a href="/?id=14&category=%D9%81%D9%8A%D9%84%D9%85+%D8%A7%D8%A8%D…

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

  • Error Line 62, Column 2631: reference to entity "category" for which no system identifier could be generated
    …</a></li><li><a href="/?id=14&category=%D9%81%D9%8A%D9%84%D9%85+%D8%A7%D8%A8%D…

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

  • Info Line 62, Column 62: entity was defined here
    …ategories</h2><ul><li><a href="/?id=11&category=%D8%A7%D9%84%D9%88%D8%AC%D9%87…
  • Warning Line 62, Column 2750: reference not terminated by REFC delimiter
    …+%D8%A7%D9%84%D8%AC%D9%86%D8%B3&option=category&p=1">فيلم اباحي مثلي الجنس</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 62, Column 2750: reference to external entity in attribute value
    …+%D8%A7%D9%84%D8%AC%D9%86%D8%B3&option=category&p=1">فيلم اباحي مثلي الجنس</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 62, Column 2750: reference to entity "option" for which no system identifier could be generated
    …+%D8%A7%D9%84%D8%AC%D9%86%D8%B3&option=category&p=1">فيلم اباحي مثلي الجنس</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 62, Column 158: entity was defined here
    …4%D9%85+%D8%A7%D8%A8%D8%A7%D8%AD%D9%8A&option=category&p=1">الوجه فيلم اباحي</…
  • Warning Line 62, Column 2761: reference not terminated by REFC delimiter
    …84%D8%AC%D9%86%D8%B3&option=category&p=1">فيلم اباحي مثلي الجنس</a></li><li><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 62, Column 2761: reference to external entity in attribute value
    …84%D8%AC%D9%86%D8%B3&option=category&p=1">فيلم اباحي مثلي الجنس</a></li><li><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 62, Column 2761: reference to entity "p" for which no system identifier could be generated
    …84%D8%AC%D9%86%D8%B3&option=category&p=1">فيلم اباحي مثلي الجنس</a></li><li><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 62, Column 174: entity was defined here
    …8%A8%D8%A7%D8%AD%D9%8A&option=category&p=1">الوجه فيلم اباحي</a></li><li><a hr…
  • Warning Line 62, Column 2824: reference not terminated by REFC delimiter
    …</a></li><li><a href="/?id=15&category=%D9%81%D9%8A%D9%84%D9%85+%D8%A7%D8%A8%D…

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

  • Warning Line 62, Column 2824: reference to external entity in attribute value
    …</a></li><li><a href="/?id=15&category=%D9%81%D9%8A%D9%84%D9%85+%D8%A7%D8%A8%D…

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

  • Error Line 62, Column 2824: reference to entity "category" for which no system identifier could be generated
    …</a></li><li><a href="/?id=15&category=%D9%81%D9%8A%D9%84%D9%85+%D8%A7%D8%A8%D…

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

  • Info Line 62, Column 62: entity was defined here
    …ategories</h2><ul><li><a href="/?id=11&category=%D8%A7%D9%84%D9%88%D8%AC%D9%87…
  • Warning Line 62, Column 2924: reference not terminated by REFC delimiter
    …5%D8%AC%D9%85%D9%88%D8%B9%D8%A9&option=category&p=1">فيلم اباحي مجموعة</a></li…

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

  • Warning Line 62, Column 2924: reference to external entity in attribute value
    …5%D8%AC%D9%85%D9%88%D8%B9%D8%A9&option=category&p=1">فيلم اباحي مجموعة</a></li…

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

  • Error Line 62, Column 2924: reference to entity "option" for which no system identifier could be generated
    …5%D8%AC%D9%85%D9%88%D8%B9%D8%A9&option=category&p=1">فيلم اباحي مجموعة</a></li…

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

  • Info Line 62, Column 158: entity was defined here
    …4%D9%85+%D8%A7%D8%A8%D8%A7%D8%AD%D9%8A&option=category&p=1">الوجه فيلم اباحي</…
  • Warning Line 62, Column 2935: reference not terminated by REFC delimiter
    …85%D9%88%D8%B9%D8%A9&option=category&p=1">فيلم اباحي مجموعة</a></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 62, Column 2935: reference to external entity in attribute value
    …85%D9%88%D8%B9%D8%A9&option=category&p=1">فيلم اباحي مجموعة</a></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 62, Column 2935: reference to entity "p" for which no system identifier could be generated
    …85%D9%88%D8%B9%D8%A9&option=category&p=1">فيلم اباحي مجموعة</a></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 62, Column 174: entity was defined here
    …8%A8%D8%A7%D8%AD%D9%8A&option=category&p=1">الوجه فيلم اباحي</a></li><li><a hr…
  • Warning Line 62, Column 2994: reference not terminated by REFC delimiter
    …</a></li><li><a href="/?id=16&category=%D9%81%D9%8A%D9%84%D9%85+%D8%A7%D8%A8%D…

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

  • Warning Line 62, Column 2994: reference to external entity in attribute value
    …</a></li><li><a href="/?id=16&category=%D9%81%D9%8A%D9%84%D9%85+%D8%A7%D8%A8%D…

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

  • Error Line 62, Column 2994: reference to entity "category" for which no system identifier could be generated
    …</a></li><li><a href="/?id=16&category=%D9%81%D9%8A%D9%84%D9%85+%D8%A7%D8%A8%D…

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

  • Info Line 62, Column 62: entity was defined here
    …ategories</h2><ul><li><a href="/?id=11&category=%D8%A7%D9%84%D9%88%D8%AC%D9%87…
  • Warning Line 62, Column 3088: reference not terminated by REFC delimiter
    …+%D9%87%D9%86%D8%AA%D8%A7%D9%8A&option=category&p=1">فيلم اباحي هنتاي</a></li>…

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

  • Warning Line 62, Column 3088: reference to external entity in attribute value
    …+%D9%87%D9%86%D8%AA%D8%A7%D9%8A&option=category&p=1">فيلم اباحي هنتاي</a></li>…

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

  • Error Line 62, Column 3088: reference to entity "option" for which no system identifier could be generated
    …+%D9%87%D9%86%D8%AA%D8%A7%D9%8A&option=category&p=1">فيلم اباحي هنتاي</a></li>…

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

  • Info Line 62, Column 158: entity was defined here
    …4%D9%85+%D8%A7%D8%A8%D8%A7%D8%AD%D9%8A&option=category&p=1">الوجه فيلم اباحي</…
  • Warning Line 62, Column 3099: reference not terminated by REFC delimiter
    …86%D8%AA%D8%A7%D9%8A&option=category&p=1">فيلم اباحي هنتاي</a></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 62, Column 3099: reference to external entity in attribute value
    …86%D8%AA%D8%A7%D9%8A&option=category&p=1">فيلم اباحي هنتاي</a></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 62, Column 3099: reference to entity "p" for which no system identifier could be generated
    …86%D8%AA%D8%A7%D9%8A&option=category&p=1">فيلم اباحي هنتاي</a></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 62, Column 174: entity was defined here
    …8%A8%D8%A7%D8%AD%D9%8A&option=category&p=1">الوجه فيلم اباحي</a></li><li><a hr…
  • Warning Line 62, Column 3156: reference not terminated by REFC delimiter
    …ي</a></li><li><a href="/?id=9&category=%D9%85%D8%B4%D8%A7%D9%87%D8%AF+%D8%A8%D…

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

  • Warning Line 62, Column 3156: reference to external entity in attribute value
    …ي</a></li><li><a href="/?id=9&category=%D9%85%D8%B4%D8%A7%D9%87%D8%AF+%D8%A8%D…

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

  • Error Line 62, Column 3156: reference to entity "category" for which no system identifier could be generated
    …ي</a></li><li><a href="/?id=9&category=%D9%85%D8%B4%D8%A7%D9%87%D8%AF+%D8%A8%D…

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

  • Info Line 62, Column 62: entity was defined here
    …ategories</h2><ul><li><a href="/?id=11&category=%D8%A7%D9%84%D9%88%D8%AC%D9%87…
  • Warning Line 62, Column 3306: reference not terminated by REFC delimiter
    …+%D8%A7%D8%A8%D8%A7%D8%AD%D9%8A&option=category&p=1">مشاهد بقذف المني فيلم ابا…

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

  • Warning Line 62, Column 3306: reference to external entity in attribute value
    …+%D8%A7%D8%A8%D8%A7%D8%AD%D9%8A&option=category&p=1">مشاهد بقذف المني فيلم ابا…

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

  • Error Line 62, Column 3306: reference to entity "option" for which no system identifier could be generated
    …+%D8%A7%D8%A8%D8%A7%D8%AD%D9%8A&option=category&p=1">مشاهد بقذف المني فيلم ابا…

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

  • Info Line 62, Column 158: entity was defined here
    …4%D9%85+%D8%A7%D8%A8%D8%A7%D8%AD%D9%8A&option=category&p=1">الوجه فيلم اباحي</…
  • Warning Line 62, Column 3317: reference not terminated by REFC delimiter
    …A8%D8%A7%D8%AD%D9%8A&option=category&p=1">مشاهد بقذف المني فيلم اباحي</a></li>…

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

  • Warning Line 62, Column 3317: reference to external entity in attribute value
    …A8%D8%A7%D8%AD%D9%8A&option=category&p=1">مشاهد بقذف المني فيلم اباحي</a></li>…

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

  • Error Line 62, Column 3317: reference to entity "p" for which no system identifier could be generated
    …A8%D8%A7%D8%AD%D9%8A&option=category&p=1">مشاهد بقذف المني فيلم اباحي</a></li>…

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

  • Info Line 62, Column 174: entity was defined here
    …8%A8%D8%A7%D8%AD%D9%8A&option=category&p=1">الوجه فيلم اباحي</a></li><li><a hr…
  • Error Line 62, Column 3367: character data is not allowed here
    …gory&p=1">مشاهد بقذف المني فيلم اباحي</a></li></ul></li>Left Two Free HTML Area

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 64, Column 31: document type does not allow element "script" here; assuming missing "li" start-tag
    <script type="text/javascript">
  • Error Line 119, Column 37: character ";" not allowed in attribute specification list
          for (var n=0; n<cookies.length; n++) {
  • Error Line 119, Column 37: element "cookies.length" undefined
          for (var n=0; n<cookies.length; n++) {

    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 157, Column 9: end tag for "cookies.length" omitted, but OMITTAG NO was specified
    </script><li><h2>Recent Comments</h2><ul></ul></li> 

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

  • Info Line 119, Column 22: start tag was here
          for (var n=0; n<cookies.length; n++) {
  • Error Line 157, Column 13: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    </script><li><h2>Recent Comments</h2><ul></ul></li> 

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

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

  • Error Line 157, Column 46: end tag for "ul" which is not finished
    </script><li><h2>Recent Comments</h2><ul></ul></li> 

    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 161, Column 8: end tag for "li" omitted, but OMITTAG NO was specified
    			</ul>

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

  • Info Line 64, Column 1: start tag was here
    <script type="text/javascript">
  • Error Line 170, Column 20: element "center" undefined
                <center>Content Up Free HTML Area</center>

    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 172, Column 22: element "center" undefined
                  <center><div class='paginator'><a class='secili' href='javascript…

    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 172, Column 249: cannot generate system identifier for general entity "id"
    …valign="top"><a  href="/?option=video&id=277032&title=%D9%87%D9%88+%D9%85%D8%A…

    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 172, Column 249: general entity "id" not defined and no default entity
    …valign="top"><a  href="/?option=video&id=277032&title=%D9%87%D9%88+%D9%85%D8%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.

  • Warning Line 172, Column 251: reference not terminated by REFC delimiter
    …lign="top"><a  href="/?option=video&id=277032&title=%D9%87%D9%88+%D9%85%D8%AA%…

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

  • Warning Line 172, Column 251: reference to external entity in attribute value
    …lign="top"><a  href="/?option=video&id=277032&title=%D9%87%D9%88+%D9%85%D8%AA%…

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

  • Error Line 172, Column 251: reference to entity "id" for which no system identifier could be generated
    …lign="top"><a  href="/?option=video&id=277032&title=%D9%87%D9%88+%D9%85%D8%AA%…

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

  • Info Line 172, Column 248: entity was defined here
    … valign="top"><a  href="/?option=video&id=277032&title=%D9%87%D9%88+%D9%85%D8%…
  • Warning Line 172, Column 259: cannot generate system identifier for general entity "title"
    …p"><a  href="/?option=video&id=277032&title=%D9%87%D9%88+%D9%85%D8%AA%D8%AD%D9…

    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 172, Column 259: general entity "title" not defined and no default entity
    …p"><a  href="/?option=video&id=277032&title=%D9%87%D9%88+%D9%85%D8%AA%D8%AD%D9…

    This is usually a cascading error caused by 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 172, Column 264: reference not terminated by REFC delimiter
    …  href="/?option=video&id=277032&title=%D9%87%D9%88+%D9%85%D8%AA%D8%AD%D9%85%D…

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

  • Warning Line 172, Column 264: reference to external entity in attribute value
    …  href="/?option=video&id=277032&title=%D9%87%D9%88+%D9%85%D8%AA%D8%AD%D9%85%D…

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

  • Error Line 172, Column 264: reference to entity "title" for which no system identifier could be generated
    …  href="/?option=video&id=277032&title=%D9%87%D9%88+%D9%85%D8%AA%D8%AD%D9%85%D…

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

  • Info Line 172, Column 258: entity was defined here
    …op"><a  href="/?option=video&id=277032&title=%D9%87%D9%88+%D9%85%D8%AA%D8%AD%D…
  • Error Line 172, Column 483: there is no attribute "align"
    …%D8%B1%D8%AC+%D8%AB%D9%85"><div align="center"><img multiple_thumbnail_url="g"…

    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 172, Column 491: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …8%AC+%D8%AB%D9%85"><div align="center"><img multiple_thumbnail_url="g" class="…

    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 172, Column 520: there is no attribute "multiple_thumbnail_url"
    …="center"><img multiple_thumbnail_url="g" class="video-thumb" border="0" src="…

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

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

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

  • Error Line 172, Column 551: there is no attribute "border"
    …il_url="g" class="video-thumb" border="0" src="/img/thumb/277032_0.jpg" num="8…

    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 172, Column 589: there is no attribute "num"
    …"0" src="/img/thumb/277032_0.jpg" num="8" id="thumb1" alt="هو متحمس مكنسة مع د…

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

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

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

  • Warning Line 172, Column 779: reference not terminated by REFC delimiter
    …lign="top"><a  href="/?option=video&id=277036&title=%D9%81%D9%8A+%D8%B3%D9%86+…

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

  • Warning Line 172, Column 779: reference to external entity in attribute value
    …lign="top"><a  href="/?option=video&id=277036&title=%D9%81%D9%8A+%D8%B3%D9%86+…

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

  • Error Line 172, Column 779: reference to entity "id" for which no system identifier could be generated
    …lign="top"><a  href="/?option=video&id=277036&title=%D9%81%D9%8A+%D8%B3%D9%86+…

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

  • Info Line 172, Column 248: entity was defined here
    … valign="top"><a  href="/?option=video&id=277032&title=%D9%87%D9%88+%D9%85%D8%…
  • Warning Line 172, Column 792: reference not terminated by REFC delimiter
    …  href="/?option=video&id=277036&title=%D9%81%D9%8A+%D8%B3%D9%86+%D8%A7%D9%84%…

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

  • Warning Line 172, Column 792: reference to external entity in attribute value
    …  href="/?option=video&id=277036&title=%D9%81%D9%8A+%D8%B3%D9%86+%D8%A7%D9%84%…

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

  • Error Line 172, Column 792: reference to entity "title" for which no system identifier could be generated
    …  href="/?option=video&id=277036&title=%D9%81%D9%8A+%D8%B3%D9%86+%D8%A7%D9%84%…

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

  • Info Line 172, Column 258: entity was defined here
    …op"><a  href="/?option=video&id=277032&title=%D9%87%D9%88+%D9%85%D8%AA%D8%AD%D…
  • Error Line 172, Column 963: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …D8%AC%D8%AF%D8%A7"><div align="center"><img multiple_thumbnail_url="g" class="…

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

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

  • Warning Line 172, Column 1229: reference not terminated by REFC delimiter
    …lign="top"><a  href="/?option=video&id=277038&title=%D9%87%D9%88%D8%A7%D8%A9+%…

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

  • Warning Line 172, Column 1229: reference to external entity in attribute value
    …lign="top"><a  href="/?option=video&id=277038&title=%D9%87%D9%88%D8%A7%D8%A9+%…

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

  • Error Line 172, Column 1229: reference to entity "id" for which no system identifier could be generated
    …lign="top"><a  href="/?option=video&id=277038&title=%D9%87%D9%88%D8%A7%D8%A9+%…

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

  • Info Line 172, Column 248: entity was defined here
    … valign="top"><a  href="/?option=video&id=277032&title=%D9%87%D9%88+%D9%85%D8%…
  • Warning Line 172, Column 1242: reference not terminated by REFC delimiter
    …  href="/?option=video&id=277038&title=%D9%87%D9%88%D8%A7%D8%A9+%D8%A7%D8%AA%D…

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

  • Warning Line 172, Column 1242: reference to external entity in attribute value
    …  href="/?option=video&id=277038&title=%D9%87%D9%88%D8%A7%D8%A9+%D8%A7%D8%AA%D…

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

  • Error Line 172, Column 1242: reference to entity "title" for which no system identifier could be generated
    …  href="/?option=video&id=277038&title=%D9%87%D9%88%D8%A7%D8%A9+%D8%A7%D8%AA%D…

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

  • Info Line 172, Column 258: entity was defined here
    …op"><a  href="/?option=video&id=277032&title=%D9%87%D9%88+%D9%85%D8%AA%D8%AD%D…
  • Error Line 172, Column 1407: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …D8%AF%D9%8A%D9%83"><div align="center"><img multiple_thumbnail_url="g" class="…

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

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

  • Warning Line 172, Column 1716: reference not terminated by REFC delimiter
    …lign="top"><a  href="/?option=video&id=277039&title=%D8%B1%D8%A7%D8%A6%D8%B9+%…

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

  • Warning Line 172, Column 1716: reference to external entity in attribute value
    …lign="top"><a  href="/?option=video&id=277039&title=%D8%B1%D8%A7%D8%A6%D8%B9+%…

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

  • Error Line 172, Column 1716: reference to entity "id" for which no system identifier could be generated
    …lign="top"><a  href="/?option=video&id=277039&title=%D8%B1%D8%A7%D8%A6%D8%B9+%…

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

  • Info Line 172, Column 248: entity was defined here
    … valign="top"><a  href="/?option=video&id=277032&title=%D9%87%D9%88+%D9%85%D8%…
  • Warning Line 172, Column 1729: reference not terminated by REFC delimiter
    …  href="/?option=video&id=277039&title=%D8%B1%D8%A7%D8%A6%D8%B9+%D9%85%D8%B5+%…

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

  • Warning Line 172, Column 1729: reference to external entity in attribute value
    …  href="/?option=video&id=277039&title=%D8%B1%D8%A7%D8%A6%D8%B9+%D9%85%D8%B5+%…

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

  • Error Line 172, Column 1729: reference to entity "title" for which no system identifier could be generated
    …  href="/?option=video&id=277039&title=%D8%B1%D8%A7%D8%A6%D8%B9+%D9%85%D8%B5+%…

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

  • Info Line 172, Column 258: entity was defined here
    …op"><a  href="/?option=video&id=277032&title=%D9%87%D9%88+%D9%85%D8%AA%D8%AD%D…
  • Error Line 172, Column 1975: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …D8%A8%D8%A7%D8%A8"><div align="center"><img multiple_thumbnail_url="g" class="…

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

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

  • Warning Line 172, Column 2271: reference not terminated by REFC delimiter
    …lign="top"><a  href="/?option=video&id=277040&title=%D8%A7%D9%84%D8%A2%D8%B3%D…

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

  • Warning Line 172, Column 2271: reference to external entity in attribute value
    …lign="top"><a  href="/?option=video&id=277040&title=%D8%A7%D9%84%D8%A2%D8%B3%D…

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

  • Error Line 172, Column 2271: reference to entity "id" for which no system identifier could be generated
    …lign="top"><a  href="/?option=video&id=277040&title=%D8%A7%D9%84%D8%A2%D8%B3%D…

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

  • Info Line 172, Column 248: entity was defined here
    … valign="top"><a  href="/?option=video&id=277032&title=%D9%87%D9%88+%D9%85%D8%…
  • Warning Line 172, Column 2284: reference not terminated by REFC delimiter
    …  href="/?option=video&id=277040&title=%D8%A7%D9%84%D8%A2%D8%B3%D9%8A%D9%88%D9…

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

  • Warning Line 172, Column 2284: reference to external entity in attribute value
    …  href="/?option=video&id=277040&title=%D8%A7%D9%84%D8%A2%D8%B3%D9%8A%D9%88%D9…

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

  • Error Line 172, Column 2284: reference to entity "title" for which no system identifier could be generated
    …  href="/?option=video&id=277040&title=%D8%A7%D9%84%D8%A2%D8%B3%D9%8A%D9%88%D9…

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

  • Info Line 172, Column 258: entity was defined here
    …op"><a  href="/?option=video&id=277032&title=%D9%87%D9%88+%D9%85%D8%AA%D8%AD%D…
  • Error Line 172, Column 2510: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …D8%AE%D9%8A%D9%81"><div align="center"><img multiple_thumbnail_url="g" class="…

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

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

  • Warning Line 172, Column 2796: reference not terminated by REFC delimiter
    …lign="top"><a  href="/?option=video&id=277041&title=%D9%85%D8%A7%D8%B1%D8%B3+%…

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

  • Warning Line 172, Column 2796: reference to external entity in attribute value
    …lign="top"><a  href="/?option=video&id=277041&title=%D9%85%D8%A7%D8%B1%D8%B3+%…

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

  • Error Line 172, Column 2796: reference to entity "id" for which no system identifier could be generated
    …lign="top"><a  href="/?option=video&id=277041&title=%D9%85%D8%A7%D8%B1%D8%B3+%…

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

  • Info Line 172, Column 248: entity was defined here
    … valign="top"><a  href="/?option=video&id=277032&title=%D9%87%D9%88+%D9%85%D8%…
  • Warning Line 172, Column 2809: reference not terminated by REFC delimiter
    …  href="/?option=video&id=277041&title=%D9%85%D8%A7%D8%B1%D8%B3+%D8%A7%D9%84%D…

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

  • Warning Line 172, Column 2809: reference to external entity in attribute value
    …  href="/?option=video&id=277041&title=%D9%85%D8%A7%D8%B1%D8%B3+%D8%A7%D9%84%D…

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

  • Error Line 172, Column 2809: reference to entity "title" for which no system identifier could be generated
    …  href="/?option=video&id=277041&title=%D9%85%D8%A7%D8%B1%D8%B3+%D8%A7%D9%84%D…

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

  • Info Line 172, Column 258: entity was defined here
    …op"><a  href="/?option=video&id=277032&title=%D9%87%D9%88+%D9%85%D8%AA%D8%AD%D…
  • Error Line 172, Column 3086: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …D8%B2%D9%85%D9%8A"><div align="center"><img multiple_thumbnail_url="g" class="…

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

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

  • Warning Line 172, Column 3439: reference not terminated by REFC delimiter
    …lign="top"><a  href="/?option=video&id=272886&title=%D8%B7%D9%8A%D9%81+%D8%A7%…

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

  • Warning Line 172, Column 3439: reference to external entity in attribute value
    …lign="top"><a  href="/?option=video&id=272886&title=%D8%B7%D9%8A%D9%81+%D8%A7%…

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

  • Error Line 172, Column 3439: reference to entity "id" for which no system identifier could be generated
    …lign="top"><a  href="/?option=video&id=272886&title=%D8%B7%D9%8A%D9%81+%D8%A7%…

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

  • Info Line 172, Column 248: entity was defined here
    … valign="top"><a  href="/?option=video&id=277032&title=%D9%87%D9%88+%D9%85%D8%…
  • Warning Line 172, Column 3452: reference not terminated by REFC delimiter
    …  href="/?option=video&id=272886&title=%D8%B7%D9%8A%D9%81+%D8%A7%D9%85%D8%B1%D…

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

  • Warning Line 172, Column 3452: reference to external entity in attribute value
    …  href="/?option=video&id=272886&title=%D8%B7%D9%8A%D9%81+%D8%A7%D9%85%D8%B1%D…

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

  • Error Line 172, Column 3452: reference to entity "title" for which no system identifier could be generated
    …  href="/?option=video&id=272886&title=%D8%B7%D9%8A%D9%81+%D8%A7%D9%85%D8%B1%D…

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

  • Info Line 172, Column 258: entity was defined here
    …op"><a  href="/?option=video&id=277032&title=%D9%87%D9%88+%D9%85%D8%AA%D8%AD%D…
  • Error Line 172, Column 3672: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …%D9%83%D8%B3+xxnx"><div align="center"><img multiple_thumbnail_url="g" class="…

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

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

  • Warning Line 172, Column 3966: reference not terminated by REFC delimiter
    …lign="top"><a  href="/?option=video&id=273050&title=%D8%B4%D9%82%D8%B1%D8%A7%D…

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

  • Warning Line 172, Column 3966: reference to external entity in attribute value
    …lign="top"><a  href="/?option=video&id=273050&title=%D8%B4%D9%82%D8%B1%D8%A7%D…

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

  • Error Line 172, Column 3966: reference to entity "id" for which no system identifier could be generated
    …lign="top"><a  href="/?option=video&id=273050&title=%D8%B4%D9%82%D8%B1%D8%A7%D…

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

  • Info Line 172, Column 248: entity was defined here
    … valign="top"><a  href="/?option=video&id=277032&title=%D9%87%D9%88+%D9%85%D8%…
  • Warning Line 172, Column 3979: reference not terminated by REFC delimiter
    …  href="/?option=video&id=273050&title=%D8%B4%D9%82%D8%B1%D8%A7%D8%A1+%D9%85%D…

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

  • Warning Line 172, Column 3979: reference to external entity in attribute value
    …  href="/?option=video&id=273050&title=%D8%B4%D9%82%D8%B1%D8%A7%D8%A1+%D9%85%D…

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

  • Error Line 172, Column 3979: reference to entity "title" for which no system identifier could be generated
    …  href="/?option=video&id=273050&title=%D8%B4%D9%82%D8%B1%D8%A7%D8%A1+%D9%85%D…

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

  • Info Line 172, Column 258: entity was defined here
    …op"><a  href="/?option=video&id=277032&title=%D9%87%D9%88+%D9%85%D8%AA%D8%AD%D…
  • Error Line 172, Column 4156: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …D9%82%D9%87%D8%A7"><div align="center"><img multiple_thumbnail_url="g" class="…

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

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

  • Warning Line 172, Column 4424: reference not terminated by REFC delimiter
    …lign="top"><a  href="/?option=video&id=273076&title=%D9%87%D8%B0%D9%87+%D8%A7%…

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

  • Warning Line 172, Column 4424: reference to external entity in attribute value
    …lign="top"><a  href="/?option=video&id=273076&title=%D9%87%D8%B0%D9%87+%D8%A7%…

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

  • Error Line 172, Column 4424: reference to entity "id" for which no system identifier could be generated
    …lign="top"><a  href="/?option=video&id=273076&title=%D9%87%D8%B0%D9%87+%D8%A7%…

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

  • Info Line 172, Column 248: entity was defined here
    … valign="top"><a  href="/?option=video&id=277032&title=%D9%87%D9%88+%D9%85%D8%…
  • Warning Line 172, Column 4437: reference not terminated by REFC delimiter
    …  href="/?option=video&id=273076&title=%D9%87%D8%B0%D9%87+%D8%A7%D9%84%D9%81%D…

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

  • Warning Line 172, Column 4437: reference to external entity in attribute value
    …  href="/?option=video&id=273076&title=%D9%87%D8%B0%D9%87+%D8%A7%D9%84%D9%81%D…

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

  • Error Line 172, Column 4437: reference to entity "title" for which no system identifier could be generated
    …  href="/?option=video&id=273076&title=%D9%87%D8%B0%D9%87+%D8%A7%D9%84%D9%81%D…

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

  • Info Line 172, Column 258: entity was defined here
    …op"><a  href="/?option=video&id=277032&title=%D9%87%D9%88+%D9%85%D8%AA%D8%AD%D…
  • Error Line 172, Column 4640: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …8%B5+%D8%A8%D9%83"><div align="center"><img multiple_thumbnail_url="g" class="…

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

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

  • Warning Line 172, Column 4965: reference not terminated by REFC delimiter
    …lign="top"><a  href="/?option=video&id=273039&title=%D8%AA%D8%AF%D9%84%D9%8A%D…

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

  • Warning Line 172, Column 4965: reference to external entity in attribute value
    …lign="top"><a  href="/?option=video&id=273039&title=%D8%AA%D8%AF%D9%84%D9%8A%D…

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

  • Error Line 172, Column 4965: reference to entity "id" for which no system identifier could be generated
    …lign="top"><a  href="/?option=video&id=273039&title=%D8%AA%D8%AF%D9%84%D9%8A%D…

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

  • Info Line 172, Column 248: entity was defined here
    … valign="top"><a  href="/?option=video&id=277032&title=%D9%87%D9%88+%D9%85%D8%…
  • Warning Line 172, Column 4978: reference not terminated by REFC delimiter
    …  href="/?option=video&id=273039&title=%D8%AA%D8%AF%D9%84%D9%8A%D9%83+%D8%A8%D…

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

  • Warning Line 172, Column 4978: reference to external entity in attribute value
    …  href="/?option=video&id=273039&title=%D8%AA%D8%AF%D9%84%D9%8A%D9%83+%D8%A8%D…

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

  • Error Line 172, Column 4978: reference to entity "title" for which no system identifier could be generated
    …  href="/?option=video&id=273039&title=%D8%AA%D8%AF%D9%84%D9%8A%D9%83+%D8%A8%D…

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

  • Info Line 172, Column 258: entity was defined here
    …op"><a  href="/?option=video&id=277032&title=%D9%87%D9%88+%D9%85%D8%AA%D8%AD%D…
  • Error Line 172, Column 5185: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …D8%B1%D8%A7%D8%A1"><div align="center"><img multiple_thumbnail_url="g" class="…

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

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

  • Warning Line 172, Column 5464: reference not terminated by REFC delimiter
    …lign="top"><a  href="/?option=video&id=273044&title=%D8%A7%D9%85%D8%B1%D8%A3%D…

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

  • Warning Line 172, Column 5464: reference to external entity in attribute value
    …lign="top"><a  href="/?option=video&id=273044&title=%D8%A7%D9%85%D8%B1%D8%A3%D…

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

  • Error Line 172, Column 5464: reference to entity "id" for which no system identifier could be generated
    …lign="top"><a  href="/?option=video&id=273044&title=%D8%A7%D9%85%D8%B1%D8%A3%D…

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

  • Info Line 172, Column 248: entity was defined here
    … valign="top"><a  href="/?option=video&id=277032&title=%D9%87%D9%88+%D9%85%D8%…
  • Warning Line 172, Column 5477: reference not terminated by REFC delimiter
    …  href="/?option=video&id=273044&title=%D8%A7%D9%85%D8%B1%D8%A3%D8%A9+%D8%B4%D…

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

  • Warning Line 172, Column 5477: reference to external entity in attribute value
    …  href="/?option=video&id=273044&title=%D8%A7%D9%85%D8%B1%D8%A3%D8%A9+%D8%B4%D…

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

  • Error Line 172, Column 5477: reference to entity "title" for which no system identifier could be generated
    …  href="/?option=video&id=273044&title=%D8%A7%D9%85%D8%B1%D8%A3%D8%A9+%D8%B4%D…

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

  • Info Line 172, Column 258: entity was defined here
    …op"><a  href="/?option=video&id=277032&title=%D9%87%D9%88+%D9%85%D8%AA%D8%AD%D…
  • Error Line 172, Column 5717: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …D9%85%D8%A7%D8%B1"><div align="center"><img multiple_thumbnail_url="g" class="…

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

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

  • Warning Line 172, Column 6012: reference not terminated by REFC delimiter
    …lign="top"><a  href="/?option=video&id=273040&title=%D9%86%D9%88%D8%B1%D8%A7+%…

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

  • Warning Line 172, Column 6012: reference to external entity in attribute value
    …lign="top"><a  href="/?option=video&id=273040&title=%D9%86%D9%88%D8%B1%D8%A7+%…

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

  • Error Line 172, Column 6012: reference to entity "id" for which no system identifier could be generated
    …lign="top"><a  href="/?option=video&id=273040&title=%D9%86%D9%88%D8%B1%D8%A7+%…

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

  • Info Line 172, Column 248: entity was defined here
    … valign="top"><a  href="/?option=video&id=277032&title=%D9%87%D9%88+%D9%85%D8%…
  • Warning Line 172, Column 6025: reference not terminated by REFC delimiter
    …  href="/?option=video&id=273040&title=%D9%86%D9%88%D8%B1%D8%A7+%D8%A7%D9%84%D…

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

  • Warning Line 172, Column 6025: reference to external entity in attribute value
    …  href="/?option=video&id=273040&title=%D9%86%D9%88%D8%B1%D8%A7+%D8%A7%D9%84%D…

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

  • Error Line 172, Column 6025: reference to entity "title" for which no system identifier could be generated
    …  href="/?option=video&id=273040&title=%D9%86%D9%88%D8%B1%D8%A7+%D8%A7%D9%84%D…

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

  • Info Line 172, Column 258: entity was defined here
    …op"><a  href="/?option=video&id=277032&title=%D9%87%D9%88+%D9%85%D8%AA%D8%AD%D…
  • Error Line 172, Column 6207: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …D9%86%D9%88%D9%86"><div align="center"><img multiple_thumbnail_url="g" class="…

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

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

  • Warning Line 172, Column 6521: reference not terminated by REFC delimiter
    …lign="top"><a  href="/?option=video&id=273047&title=%D8%A7%D9%84%D8%AC%D9%86%D…

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

  • Warning Line 172, Column 6521: reference to external entity in attribute value
    …lign="top"><a  href="/?option=video&id=273047&title=%D8%A7%D9%84%D8%AC%D9%86%D…

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

  • Error Line 172, Column 6521: reference to entity "id" for which no system identifier could be generated
    …lign="top"><a  href="/?option=video&id=273047&title=%D8%A7%D9%84%D8%AC%D9%86%D…

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

  • Info Line 172, Column 248: entity was defined here
    … valign="top"><a  href="/?option=video&id=277032&title=%D9%87%D9%88+%D9%85%D8%…
  • Warning Line 172, Column 6534: reference not terminated by REFC delimiter
    …  href="/?option=video&id=273047&title=%D8%A7%D9%84%D8%AC%D9%86%D8%B3+%D8%B9%D…

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

  • Warning Line 172, Column 6534: reference to external entity in attribute value
    …  href="/?option=video&id=273047&title=%D8%A7%D9%84%D8%AC%D9%86%D8%B3+%D8%B9%D…

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

  • Error Line 172, Column 6534: reference to entity "title" for which no system identifier could be generated
    …  href="/?option=video&id=273047&title=%D8%A7%D9%84%D8%AC%D9%86%D8%B3+%D8%B9%D…

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

  • Info Line 172, Column 258: entity was defined here
    …op"><a  href="/?option=video&id=277032&title=%D9%87%D9%88+%D9%85%D8%AA%D8%AD%D…
  • Error Line 172, Column 6669: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …%85%D8%B9+alm4sex"><div align="center"><img multiple_thumbnail_url="g" class="…

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

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

  • Warning Line 172, Column 6934: reference not terminated by REFC delimiter
    …lign="top"><a  href="/?option=video&id=273071&title=%D8%A7%D9%84%D9%84%D8%B9%D…

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

  • Warning Line 172, Column 6934: reference to external entity in attribute value
    …lign="top"><a  href="/?option=video&id=273071&title=%D8%A7%D9%84%D9%84%D8%B9%D…

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

  • Error Line 172, Column 6934: reference to entity "id" for which no system identifier could be generated
    …lign="top"><a  href="/?option=video&id=273071&title=%D8%A7%D9%84%D9%84%D8%B9%D…

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

  • Info Line 172, Column 248: entity was defined here
    … valign="top"><a  href="/?option=video&id=277032&title=%D9%87%D9%88+%D9%85%D8%…
  • Warning Line 172, Column 6947: reference not terminated by REFC delimiter
    …  href="/?option=video&id=273071&title=%D8%A7%D9%84%D9%84%D8%B9%D9%86%D8%A9+%D…

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

  • Warning Line 172, Column 6947: reference to external entity in attribute value
    …  href="/?option=video&id=273071&title=%D8%A7%D9%84%D9%84%D8%B9%D9%86%D8%A9+%D…

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

  • Error Line 172, Column 6947: reference to entity "title" for which no system identifier could be generated
    …  href="/?option=video&id=273071&title=%D8%A7%D9%84%D9%84%D8%B9%D9%86%D8%A9+%D…

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

  • Info Line 172, Column 258: entity was defined here
    …op"><a  href="/?option=video&id=277032&title=%D9%87%D9%88+%D9%85%D8%AA%D8%AD%D…
  • Error Line 172, Column 7153: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …D9%8A%D8%A9+XNXXX"><div align="center"><img multiple_thumbnail_url="g" class="…

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

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

  • Warning Line 172, Column 7440: reference not terminated by REFC delimiter
    …lign="top"><a  href="/?option=video&id=273070&title=%D9%87%D8%B0%D8%A7+%D8%B4%…

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

  • Warning Line 172, Column 7440: reference to external entity in attribute value
    …lign="top"><a  href="/?option=video&id=273070&title=%D9%87%D8%B0%D8%A7+%D8%B4%…

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

  • Error Line 172, Column 7440: reference to entity "id" for which no system identifier could be generated
    …lign="top"><a  href="/?option=video&id=273070&title=%D9%87%D8%B0%D8%A7+%D8%B4%…

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

  • Info Line 172, Column 248: entity was defined here
    … valign="top"><a  href="/?option=video&id=277032&title=%D9%87%D9%88+%D9%85%D8%…
  • Warning Line 172, Column 7453: reference not terminated by REFC delimiter
    …  href="/?option=video&id=273070&title=%D9%87%D8%B0%D8%A7+%D8%B4%D9%82%D8%B1%D…

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

  • Warning Line 172, Column 7453: reference to external entity in attribute value
    …  href="/?option=video&id=273070&title=%D9%87%D8%B0%D8%A7+%D8%B4%D9%82%D8%B1%D…

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

  • Error Line 172, Column 7453: reference to entity "title" for which no system identifier could be generated
    …  href="/?option=video&id=273070&title=%D9%87%D8%B0%D8%A7+%D8%B4%D9%82%D8%B1%D…

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

  • Info Line 172, Column 258: entity was defined here
    …op"><a  href="/?option=video&id=277032&title=%D9%87%D9%88+%D9%85%D8%AA%D8%AD%D…
  • Error Line 172, Column 7692: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …D8%AC%D9%84%D9%83"><div align="center"><img multiple_thumbnail_url="g" class="…

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

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

  • Warning Line 172, Column 8030: reference not terminated by REFC delimiter
    …lign="top"><a  href="/?option=video&id=273072&title=%D8%A3%D8%B1%D8%A8%D8%B9+%…

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

  • Warning Line 172, Column 8030: reference to external entity in attribute value
    …lign="top"><a  href="/?option=video&id=273072&title=%D8%A3%D8%B1%D8%A8%D8%B9+%…

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

  • Error Line 172, Column 8030: reference to entity "id" for which no system identifier could be generated
    …lign="top"><a  href="/?option=video&id=273072&title=%D8%A3%D8%B1%D8%A8%D8%B9+%…

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

  • Info Line 172, Column 248: entity was defined here
    … valign="top"><a  href="/?option=video&id=277032&title=%D9%87%D9%88+%D9%85%D8%…
  • Warning Line 172, Column 8043: reference not terminated by REFC delimiter
    …  href="/?option=video&id=273072&title=%D8%A3%D8%B1%D8%A8%D8%B9+%D8%AC%D9%85%D…

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

  • Warning Line 172, Column 8043: reference to external entity in attribute value
    …  href="/?option=video&id=273072&title=%D8%A3%D8%B1%D8%A8%D8%B9+%D8%AC%D9%85%D…

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

  • Error Line 172, Column 8043: reference to entity "title" for which no system identifier could be generated
    …  href="/?option=video&id=273072&title=%D8%A3%D8%B1%D8%A8%D8%B9+%D8%AC%D9%85%D…

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

  • Info Line 172, Column 258: entity was defined here
    …op"><a  href="/?option=video&id=277032&title=%D9%87%D9%88+%D9%85%D8%AA%D8%AD%D…
  • Error Line 172, Column 8189: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …D8%AC%D9%86%D8%B3"><div align="center"><img multiple_thumbnail_url="g" class="…

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

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

  • Warning Line 172, Column 8446: reference not terminated by REFC delimiter
    …lign="top"><a  href="/?option=video&id=273082&title=%D9%81%D9%8A+%D8%A7%D9%84%…

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

  • Warning Line 172, Column 8446: reference to external entity in attribute value
    …lign="top"><a  href="/?option=video&id=273082&title=%D9%81%D9%8A+%D8%A7%D9%84%…

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

  • Error Line 172, Column 8446: reference to entity "id" for which no system identifier could be generated
    …lign="top"><a  href="/?option=video&id=273082&title=%D9%81%D9%8A+%D8%A7%D9%84%…

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

  • Info Line 172, Column 248: entity was defined here
    … valign="top"><a  href="/?option=video&id=277032&title=%D9%87%D9%88+%D9%85%D8%…
  • Warning Line 172, Column 8459: reference not terminated by REFC delimiter
    …  href="/?option=video&id=273082&title=%D9%81%D9%8A+%D8%A7%D9%84%D9%84%D8%A7%D…

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

  • Warning Line 172, Column 8459: reference to external entity in attribute value
    …  href="/?option=video&id=273082&title=%D9%81%D9%8A+%D8%A7%D9%84%D9%84%D8%A7%D…

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

  • Error Line 172, Column 8459: reference to entity "title" for which no system identifier could be generated
    …  href="/?option=video&id=273082&title=%D9%81%D9%8A+%D8%A7%D9%84%D9%84%D8%A7%D…

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

  • Info Line 172, Column 258: entity was defined here
    …op"><a  href="/?option=video&id=277032&title=%D9%87%D9%88+%D9%85%D8%AA%D8%AD%D…
  • Error Line 172, Column 8635: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …D8%B1%D8%AC%D9%8A"><div align="center"><img multiple_thumbnail_url="g" class="…

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

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

  • Warning Line 172, Column 8902: reference not terminated by REFC delimiter
    …lign="top"><a  href="/?option=video&id=273081&title=%D9%81%D8%B1%D8%AE+%D8%A7%…

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

  • Warning Line 172, Column 8902: reference to external entity in attribute value
    …lign="top"><a  href="/?option=video&id=273081&title=%D9%81%D8%B1%D8%AE+%D8%A7%…

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

  • Error Line 172, Column 8902: reference to entity "id" for which no system identifier could be generated
    …lign="top"><a  href="/?option=video&id=273081&title=%D9%81%D8%B1%D8%AE+%D8%A7%…

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

  • Info Line 172, Column 248: entity was defined here
    … valign="top"><a  href="/?option=video&id=277032&title=%D9%87%D9%88+%D9%85%D8%…
  • Warning Line 172, Column 8915: reference not terminated by REFC delimiter
    …  href="/?option=video&id=273081&title=%D9%81%D8%B1%D8%AE+%D8%A7%D9%84%D8%B3%D…

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

  • Warning Line 172, Column 8915: reference to external entity in attribute value
    …  href="/?option=video&id=273081&title=%D9%81%D8%B1%D8%AE+%D8%A7%D9%84%D8%B3%D…

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

  • Error Line 172, Column 8915: reference to entity "title" for which no system identifier could be generated
    …  href="/?option=video&id=273081&title=%D9%81%D8%B1%D8%AE+%D8%A7%D9%84%D8%B3%D…

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

  • Info Line 172, Column 258: entity was defined here
    …op"><a  href="/?option=video&id=277032&title=%D9%87%D9%88+%D9%85%D8%AA%D8%AD%D…
  • Error Line 172, Column 9110: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …D9%85%D8%A7%D9%84"><div align="center"><img multiple_thumbnail_url="g" class="…

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

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

  • Warning Line 172, Column 9677: character "&" is the first character of a delimiter but occurred as data
    …ild/yahoo-dom-event/yahoo-dom-event.js&2.8.0r4/build/element/element-min.js&2.…

    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 172, Column 9714: character "&" is the first character of a delimiter but occurred as data
    …s&2.8.0r4/build/element/element-min.js&2.8.0r4/build/container/container-min.j…

    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 172, Column 9755: character "&" is the first character of a delimiter but occurred as data
    …8.0r4/build/container/container-min.js&2.8.0r4/build/connection/connection-min…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 181, Column 24: element "center" undefined
                    <center>

    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 186, Column 16: there is no attribute "border"
    <iframe border=0 frameborder=0 marginheight=0 marginwidth=0 width=308 height=29…

    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 186, Column 16: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <iframe border=0 frameborder=0 marginheight=0 marginwidth=0 width=308 height=29…
  • Error Line 186, Column 30: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <iframe border=0 frameborder=0 marginheight=0 marginwidth=0 width=308 height=29…
  • Error Line 186, Column 45: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …e border=0 frameborder=0 marginheight=0 marginwidth=0 width=308 height=299 scr…
  • Error Line 186, Column 59: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …meborder=0 marginheight=0 marginwidth=0 width=308 height=299 scrolling=no allo…
  • Error Line 186, Column 67: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …=0 marginheight=0 marginwidth=0 width=308 height=299 scrolling=no allowtranspa…
  • Error Line 186, Column 78: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ight=0 marginwidth=0 width=308 height=299 scrolling=no allowtransparency=true …
  • Error Line 186, Column 92: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …idth=0 width=308 height=299 scrolling=no allowtransparency=true src=http://ads…
  • Error Line 186, Column 113: there is no attribute "allowtransparency"
    …ht=299 scrolling=no allowtransparency=true src=http://adserver.juicyads.com/ad…

    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 186, Column 113: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ht=299 scrolling=no allowtransparency=true src=http://adserver.juicyads.com/ad…
  • Error Line 186, Column 122: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …rolling=no allowtransparency=true src=http://adserver.juicyads.com/adshow.php?…
  • Error Line 186, Column 128: NET-enabling start-tag not immediately followed by null end-tag
    …g=no allowtransparency=true src=http://adserver.juicyads.com/adshow.php?adzone…

    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 186, Column 128: element "iframe" undefined
    …g=no allowtransparency=true src=http://adserver.juicyads.com/adshow.php?adzone…

    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 186, Column 184: end tag for element "iframe" which is not open
    …arency=true src=http://adserver.juicyads.com/adshow.php?adzone=154571></iframe>

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

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

  • Error Line 192, Column 8: required attribute "type" not specified
    <script>var _wau = _wau || []; _wau.push(["tab", "rzk1a01dop2w", "8v6", "left-m…

    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 196, Column 10: end tag for "center" omitted, but OMITTAG NO was specified
    				</div>

    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 181, Column 17: start tag was here
                    <center>
  • Error Line 206, Column 78: document type does not allow element "script" here; assuming missing "li" start-tag
    …type="text/javascript" src="http://mobile.juicyads.com/js/jam_min.js"></script>
  • Error Line 210, Column 4: document type does not allow element "li" here; missing one of "ul", "ol" start-tag
    <li><h2>Tags</h2><ul><a href="/?option=tag&tag=VIDEO+SEX++%D8%AD%D9%8A%D9%88%D8…

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

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

  • Warning Line 210, Column 44: cannot generate system identifier for general entity "tag"
    …h2>Tags</h2><ul><a href="/?option=tag&tag=VIDEO+SEX++%D8%AD%D9%8A%D9%88%D8%A7%…

    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 210, Column 44: general entity "tag" not defined and no default entity
    …h2>Tags</h2><ul><a href="/?option=tag&tag=VIDEO+SEX++%D8%AD%D9%8A%D9%88%D8%A7%…

    This is usually a cascading error caused by 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 210, Column 47: reference not terminated by REFC delimiter
    …Tags</h2><ul><a href="/?option=tag&tag=VIDEO+SEX++%D8%AD%D9%8A%D9%88%D8%A7%D9%…

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

  • Warning Line 210, Column 47: reference to external entity in attribute value
    …Tags</h2><ul><a href="/?option=tag&tag=VIDEO+SEX++%D8%AD%D9%8A%D9%88%D8%A7%D9%…

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

  • Error Line 210, Column 47: reference to entity "tag" for which no system identifier could be generated
    …Tags</h2><ul><a href="/?option=tag&tag=VIDEO+SEX++%D8%AD%D9%8A%D9%88%D8%A7%D9%…

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

  • Info Line 210, Column 43: entity was defined here
    …<h2>Tags</h2><ul><a href="/?option=tag&tag=VIDEO+SEX++%D8%AD%D9%8A%D9%88%D8%A7…
  • Error Line 210, Column 134: document type does not allow element "a" here; assuming missing "li" start-tag
    …D8%AA+%D9%85%D8%B9+%D8%A8%D8%B4%D8%B1">VIDEO SEX  حيوانات مع بشر</a>, <a href=…
  • Warning Line 210, Column 191: reference not terminated by REFC delimiter
    … مع بشر</a>, <a href="/?option=tag&tag=%D9%85%D9%88%D8%A7%D9%82%D8%B9+%D8%B3%D…

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

  • Warning Line 210, Column 191: reference to external entity in attribute value
    … مع بشر</a>, <a href="/?option=tag&tag=%D9%85%D9%88%D8%A7%D9%82%D8%B9+%D8%B3%D…

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

  • Error Line 210, Column 191: reference to entity "tag" for which no system identifier could be generated
    … مع بشر</a>, <a href="/?option=tag&tag=%D9%85%D9%88%D8%A7%D9%82%D8%B9+%D8%B3%D…

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

  • Info Line 210, Column 43: entity was defined here
    …<h2>Tags</h2><ul><a href="/?option=tag&tag=VIDEO+SEX++%D8%AD%D9%8A%D9%88%D8%A7…
  • Warning Line 210, Column 380: reference not terminated by REFC delimiter
    …وحة فرى</a>, <a href="/?option=tag&tag=%D8%A8%D8%B1%D9%86%D9%88%D8%A7%D9%84%D9…

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

  • Warning Line 210, Column 380: reference to external entity in attribute value
    …وحة فرى</a>, <a href="/?option=tag&tag=%D8%A8%D8%B1%D9%86%D9%88%D8%A7%D9%84%D9…

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

  • Error Line 210, Column 380: reference to entity "tag" for which no system identifier could be generated
    …وحة فرى</a>, <a href="/?option=tag&tag=%D8%A8%D8%B1%D9%86%D9%88%D8%A7%D9%84%D9…

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

  • Info Line 210, Column 43: entity was defined here
    …<h2>Tags</h2><ul><a href="/?option=tag&tag=VIDEO+SEX++%D8%AD%D9%8A%D9%88%D8%A7…
  • Warning Line 210, Column 484: reference not terminated by REFC delimiter
    …والمانى</a>, <a href="/?option=tag&tag=%D9%83%D9%8A%D8%AA%D9%88+%D8%B3%D9%83%D…

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

  • Warning Line 210, Column 484: reference to external entity in attribute value
    …والمانى</a>, <a href="/?option=tag&tag=%D9%83%D9%8A%D8%AA%D9%88+%D8%B3%D9%83%D…

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

  • Error Line 210, Column 484: reference to entity "tag" for which no system identifier could be generated
    …والمانى</a>, <a href="/?option=tag&tag=%D9%83%D9%8A%D8%AA%D9%88+%D8%B3%D9%83%D…

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

  • Info Line 210, Column 43: entity was defined here
    …<h2>Tags</h2><ul><a href="/?option=tag&tag=VIDEO+SEX++%D8%AD%D9%8A%D9%88%D8%A7…
  • Warning Line 210, Column 606: reference not terminated by REFC delimiter
    …س فيديو</a>, <a href="/?option=tag&tag=%D9%86%D9%8A%D9%83+%D8%A8%D9%86%D8%A7%D…

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

  • Warning Line 210, Column 606: reference to external entity in attribute value
    …س فيديو</a>, <a href="/?option=tag&tag=%D9%86%D9%8A%D9%83+%D8%A8%D9%86%D8%A7%D…

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

  • Error Line 210, Column 606: reference to entity "tag" for which no system identifier could be generated
    …س فيديو</a>, <a href="/?option=tag&tag=%D9%86%D9%8A%D9%83+%D8%A8%D9%86%D8%A7%D…

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

  • Info Line 210, Column 43: entity was defined here
    …<h2>Tags</h2><ul><a href="/?option=tag&tag=VIDEO+SEX++%D8%AD%D9%8A%D9%88%D8%A7…
  • Warning Line 210, Column 742: reference not terminated by REFC delimiter
    …مراهقات</a>, <a href="/?option=tag&tag=%D8%A7%D9%81%D9%84%D8%A7%D9%85+%D9%88%D…

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

  • Warning Line 210, Column 742: reference to external entity in attribute value
    …مراهقات</a>, <a href="/?option=tag&tag=%D8%A7%D9%81%D9%84%D8%A7%D9%85+%D9%88%D…

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

  • Error Line 210, Column 742: reference to entity "tag" for which no system identifier could be generated
    …مراهقات</a>, <a href="/?option=tag&tag=%D8%A7%D9%81%D9%84%D8%A7%D9%85+%D9%88%D…

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

  • Info Line 210, Column 43: entity was defined here
    …<h2>Tags</h2><ul><a href="/?option=tag&tag=VIDEO+SEX++%D8%AD%D9%8A%D9%88%D8%A7…
  • Warning Line 210, Column 869: reference not terminated by REFC delimiter
    …رعاننيك</a>, <a href="/?option=tag&tag=%D8%A7%D9%81%D9%84%D8%A7%D9%85+%D9%86%D…

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

  • Warning Line 210, Column 869: reference to external entity in attribute value
    …رعاننيك</a>, <a href="/?option=tag&tag=%D8%A7%D9%81%D9%84%D8%A7%D9%85+%D9%86%D…

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

  • Error Line 210, Column 869: reference to entity "tag" for which no system identifier could be generated
    …رعاننيك</a>, <a href="/?option=tag&tag=%D8%A7%D9%81%D9%84%D8%A7%D9%85+%D9%86%D…

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

  • Info Line 210, Column 43: entity was defined here
    …<h2>Tags</h2><ul><a href="/?option=tag&tag=VIDEO+SEX++%D8%AD%D9%8A%D9%88%D8%A7…
  • Warning Line 210, Column 1066: reference not terminated by REFC delimiter
    …رهقات  </a>, <a href="/?option=tag&tag=%D8%B3%D9%83%D8%B3+%D8%B3%D9%85%D9%8A%D…

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

  • Warning Line 210, Column 1066: reference to external entity in attribute value
    …رهقات  </a>, <a href="/?option=tag&tag=%D8%B3%D9%83%D8%B3+%D8%B3%D9%85%D9%8A%D…

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

  • Error Line 210, Column 1066: reference to entity "tag" for which no system identifier could be generated
    …رهقات  </a>, <a href="/?option=tag&tag=%D8%B3%D9%83%D8%B3+%D8%B3%D9%85%D9%8A%D…

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

  • Info Line 210, Column 43: entity was defined here
    …<h2>Tags</h2><ul><a href="/?option=tag&tag=VIDEO+SEX++%D8%AD%D9%8A%D9%88%D8%A7…
  • Warning Line 210, Column 1181: reference not terminated by REFC delimiter
    …ين جميل</a>, <a href="/?option=tag&tag=%D8%A8%D9%88%D8%B1%D9%86%D9%88+%D8%A7%D…

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

  • Warning Line 210, Column 1181: reference to external entity in attribute value
    …ين جميل</a>, <a href="/?option=tag&tag=%D8%A8%D9%88%D8%B1%D9%86%D9%88+%D8%A7%D…

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

  • Error Line 210, Column 1181: reference to entity "tag" for which no system identifier could be generated
    …ين جميل</a>, <a href="/?option=tag&tag=%D8%A8%D9%88%D8%B1%D9%86%D9%88+%D8%A7%D…

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

  • Info Line 210, Column 43: entity was defined here
    …<h2>Tags</h2><ul><a href="/?option=tag&tag=VIDEO+SEX++%D8%AD%D9%8A%D9%88%D8%A7…
  • Warning Line 210, Column 1354: reference not terminated by REFC delimiter
    … العالم</a>, <a href="/?option=tag&tag=%D8%B3%D9%83%D8%B3%D9%8A+%D8%A7%D9%84%D…

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

  • Warning Line 210, Column 1354: reference to external entity in attribute value
    … العالم</a>, <a href="/?option=tag&tag=%D8%B3%D9%83%D8%B3%D9%8A+%D8%A7%D9%84%D…

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

  • Error Line 210, Column 1354: reference to entity "tag" for which no system identifier could be generated
    … العالم</a>, <a href="/?option=tag&tag=%D8%B3%D9%83%D8%B3%D9%8A+%D8%A7%D9%84%D…

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

  • Info Line 210, Column 43: entity was defined here
    …<h2>Tags</h2><ul><a href="/?option=tag&tag=VIDEO+SEX++%D8%AD%D9%8A%D9%88%D8%A7…
  • Warning Line 210, Column 1483: reference not terminated by REFC delimiter
    …فال نيج</a>, <a href="/?option=tag&tag=%D8%B3%D9%8A%D9%83%D8%B3+%D9%85%D8%AC%D…

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

  • Warning Line 210, Column 1483: reference to external entity in attribute value
    …فال نيج</a>, <a href="/?option=tag&tag=%D8%B3%D9%8A%D9%83%D8%B3+%D9%85%D8%AC%D…

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

  • Error Line 210, Column 1483: reference to entity "tag" for which no system identifier could be generated
    …فال نيج</a>, <a href="/?option=tag&tag=%D8%B3%D9%8A%D9%83%D8%B3+%D9%85%D8%AC%D…

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

  • Info Line 210, Column 43: entity was defined here
    …<h2>Tags</h2><ul><a href="/?option=tag&tag=VIDEO+SEX++%D8%AD%D9%8A%D9%88%D8%A7…
  • Warning Line 210, Column 1649: reference not terminated by REFC delimiter
    …ايطاليا</a>, <a href="/?option=tag&tag=%D9%82%D8%B5%D8%B5+%D8%A7%D8%B3%D8%AA%D…

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

  • Warning Line 210, Column 1649: reference to external entity in attribute value
    …ايطاليا</a>, <a href="/?option=tag&tag=%D9%82%D8%B5%D8%B5+%D8%A7%D8%B3%D8%AA%D…

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

  • Error Line 210, Column 1649: reference to entity "tag" for which no system identifier could be generated
    …ايطاليا</a>, <a href="/?option=tag&tag=%D9%82%D8%B5%D8%B5+%D8%A7%D8%B3%D8%AA%D…

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

  • Info Line 210, Column 43: entity was defined here
    …<h2>Tags</h2><ul><a href="/?option=tag&tag=VIDEO+SEX++%D8%AD%D9%8A%D9%88%D8%A7…
  • Warning Line 210, Column 1755: reference not terminated by REFC delimiter
    …استمناء</a>, <a href="/?option=tag&tag=%D8%B3%D9%83%D8%B3+%D8%A7%D8%B7%D8%A7%D…

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

  • Warning Line 210, Column 1755: reference to external entity in attribute value
    …استمناء</a>, <a href="/?option=tag&tag=%D8%B3%D9%83%D8%B3+%D8%A7%D8%B7%D8%A7%D…

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

  • Error Line 210, Column 1755: reference to entity "tag" for which no system identifier could be generated
    …استمناء</a>, <a href="/?option=tag&tag=%D8%B3%D9%83%D8%B3+%D8%A7%D8%B7%D8%A7%D…

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

  • Info Line 210, Column 43: entity was defined here
    …<h2>Tags</h2><ul><a href="/?option=tag&tag=VIDEO+SEX++%D8%AD%D9%8A%D9%88%D8%A7…
  • Warning Line 210, Column 2087: reference not terminated by REFC delimiter
    …رجال في</a>, <a href="/?option=tag&tag=htblxxx">htblxxx</a>, <a href="/?option…

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

  • Warning Line 210, Column 2087: reference to external entity in attribute value
    …رجال في</a>, <a href="/?option=tag&tag=htblxxx">htblxxx</a>, <a href="/?option…

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

  • Error Line 210, Column 2087: reference to entity "tag" for which no system identifier could be generated
    …رجال في</a>, <a href="/?option=tag&tag=htblxxx">htblxxx</a>, <a href="/?option…

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

  • Info Line 210, Column 43: entity was defined here
    …<h2>Tags</h2><ul><a href="/?option=tag&tag=VIDEO+SEX++%D8%AD%D9%8A%D9%88%D8%A7…
  • Warning Line 210, Column 2135: reference not terminated by REFC delimiter
    …htblxxx</a>, <a href="/?option=tag&tag=%D9%85%D8%AD%D8%B1%D9%85+%D8%A7%D8%A8%D…

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

  • Warning Line 210, Column 2135: reference to external entity in attribute value
    …htblxxx</a>, <a href="/?option=tag&tag=%D9%85%D8%AD%D8%B1%D9%85+%D8%A7%D8%A8%D…

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

  • Error Line 210, Column 2135: reference to entity "tag" for which no system identifier could be generated
    …htblxxx</a>, <a href="/?option=tag&tag=%D9%85%D8%AD%D8%B1%D9%85+%D8%A7%D8%A8%D…

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

  • Info Line 210, Column 43: entity was defined here
    …<h2>Tags</h2><ul><a href="/?option=tag&tag=VIDEO+SEX++%D8%AD%D9%8A%D9%88%D8%A7…
  • Warning Line 210, Column 2291: reference not terminated by REFC delimiter
    …ه صيني </a>, <a href="/?option=tag&tag=sex+porno+motarjam+arabi">sex porno mot…

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

  • Warning Line 210, Column 2291: reference to external entity in attribute value
    …ه صيني </a>, <a href="/?option=tag&tag=sex+porno+motarjam+arabi">sex porno mot…

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

  • Error Line 210, Column 2291: reference to entity "tag" for which no system identifier could be generated
    …ه صيني </a>, <a href="/?option=tag&tag=sex+porno+motarjam+arabi">sex porno mot…

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

  • Info Line 210, Column 43: entity was defined here
    …<h2>Tags</h2><ul><a href="/?option=tag&tag=VIDEO+SEX++%D8%AD%D9%8A%D9%88%D8%A7…
  • Warning Line 210, Column 2373: reference not terminated by REFC delimiter
    …m arabi</a>, <a href="/?option=tag&tag=%D8%B1%D8%AC%D9%84+%D9%8A%D9%86%D9%8A%D…

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

  • Warning Line 210, Column 2373: reference to external entity in attribute value
    …m arabi</a>, <a href="/?option=tag&tag=%D8%B1%D8%AC%D9%84+%D9%8A%D9%86%D9%8A%D…

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

  • Error Line 210, Column 2373: reference to entity "tag" for which no system identifier could be generated
    …m arabi</a>, <a href="/?option=tag&tag=%D8%B1%D8%AC%D9%84+%D9%8A%D9%86%D9%8A%D…

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

  • Info Line 210, Column 43: entity was defined here
    …<h2>Tags</h2><ul><a href="/?option=tag&tag=VIDEO+SEX++%D8%AD%D9%8A%D9%88%D8%A7…
  • Warning Line 210, Column 2488: reference not terminated by REFC delimiter
    …يك كلبة</a>, <a href="/?option=tag&tag=xxx+%D9%85%D9%85%D8%AB%D9%84%D9%8A%D9%8…

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

  • Warning Line 210, Column 2488: reference to external entity in attribute value
    …يك كلبة</a>, <a href="/?option=tag&tag=xxx+%D9%85%D9%85%D8%AB%D9%84%D9%8A%D9%8…

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

  • Error Line 210, Column 2488: reference to entity "tag" for which no system identifier could be generated
    …يك كلبة</a>, <a href="/?option=tag&tag=xxx+%D9%85%D9%85%D8%AB%D9%84%D9%8A%D9%8…

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

  • Info Line 210, Column 43: entity was defined here
    …<h2>Tags</h2><ul><a href="/?option=tag&tag=VIDEO+SEX++%D8%AD%D9%8A%D9%88%D8%A7…
  • Warning Line 210, Column 2572: reference not terminated by REFC delimiter
    … ممثلين</a>, <a href="/?option=tag&tag=%D9%81%D9%8A%D8%AF%D9%8A%D9%88+%D9%86%D…

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

  • Warning Line 210, Column 2572: reference to external entity in attribute value
    … ممثلين</a>, <a href="/?option=tag&tag=%D9%81%D9%8A%D8%AF%D9%8A%D9%88+%D9%86%D…

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

  • Error Line 210, Column 2572: reference to entity "tag" for which no system identifier could be generated
    … ممثلين</a>, <a href="/?option=tag&tag=%D9%81%D9%8A%D8%AF%D9%8A%D9%88+%D9%86%D…

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

  • Info Line 210, Column 43: entity was defined here
    …<h2>Tags</h2><ul><a href="/?option=tag&tag=VIDEO+SEX++%D8%AD%D9%8A%D9%88%D8%A7…
  • Warning Line 210, Column 2687: reference not terminated by REFC delimiter
    …نيك خار</a>, <a href="/?option=tag&tag=%D8%B3%D9%83%D8%B3+%D8%B3%D8%AA%D8%A7%D…

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

  • Warning Line 210, Column 2687: reference to external entity in attribute value
    …نيك خار</a>, <a href="/?option=tag&tag=%D8%B3%D9%83%D8%B3+%D8%B3%D8%AA%D8%A7%D…

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

  • Error Line 210, Column 2687: reference to entity "tag" for which no system identifier could be generated
    …نيك خار</a>, <a href="/?option=tag&tag=%D8%B3%D9%83%D8%B3+%D8%B3%D8%AA%D8%A7%D…

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

  • Info Line 210, Column 43: entity was defined here
    …<h2>Tags</h2><ul><a href="/?option=tag&tag=VIDEO+SEX++%D8%AD%D9%8A%D9%88%D8%A7…
  • Error Line 210, Column 2862: end tag for "li" omitted, but OMITTAG NO was specified
    …8%B4%D8%B1">سكس ستات كبيرة مجانى مباشر</a>, </ul></li> Right Two Free HTML Area

    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 210, Column 22: start tag was here
    <li><h2>Tags</h2><ul><a href="/?option=tag&tag=VIDEO+SEX++%D8%AD%D9%8A%D9%88%D8…
  • Error Line 217, Column 10: end tag for element "center" which is not open
     </center></font></div>

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

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

  • Error Line 217, Column 17: end tag for element "font" which is not open
     </center></font></div>

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

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

  • Error Line 217, Column 23: end tag for "li" omitted, but OMITTAG NO was specified
     </center></font></div>

    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 206, Column 1: start tag was here
    <script type="text/javascript" src="http://mobile.juicyads.com/js/jam_min.js"><…
  • Error Line 217, Column 23: end tag for "ul" omitted, but OMITTAG NO was specified
     </center></font></div>

    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 204, Column 4: start tag was here
    			<ul>
  • Error Line 218, Column 9: end tag for element "center" which is not open
    </center>

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

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

  • Error Line 221, Column 23: 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).

  • Warning Line 266, Column 21: character "&" is the first character of a delimiter but occurred as data
    var ie=document.all && !window.opera

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 266, Column 22: character "&" is the first character of a delimiter but occurred as data
    var ie=document.all && !window.opera

    This message may appear in several cases:

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

    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 281, Column 24: character "&" is the first character of a delimiter but occurred as data
    if (enablefade=="yes" && objref.filters){

    This message may appear in several cases:

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

    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 309, Column 21: character "&" is the first character of a delimiter but occurred as data
    var ie=document.all && !window.opera

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 309, Column 22: character "&" is the first character of a delimiter but occurred as data
    var ie=document.all && !window.opera

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 322, Column 33: character "&" is the first character of a delimiter but occurred as data
    var delayvar=(enablefade=="yes" && objref.filters)? (autohidebox[1]+objref.filt…

    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 322, Column 34: character "&" is the first character of a delimiter but occurred as data
    var delayvar=(enablefade=="yes" && objref.filters)? (autohidebox[1]+objref.filt…

    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 348, Column 35: character "&" is the first character of a delimiter but occurred as data
    if (displaymode=="oncepersession" && get_cookie("fadedin")=="" || displaymode==…

    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 348, Column 36: character "&" is the first character of a delimiter but occurred as data
    if (displaymode=="oncepersession" && get_cookie("fadedin")=="" || displaymode==…

    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 348, Column 119: character "&" is the first character of a delimiter but occurred as data
    …)=="" || displaymode=="always" || parseInt(displaymode)!=NaN && random_num==0){

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 348, Column 120: character "&" is the first character of a delimiter but occurred as data
    …)=="" || displaymode=="always" || parseInt(displaymode)!=NaN && random_num==0){

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 363, Column 50: there is no attribute "name"
    …="http://pornxnxx.info/ads.html" name="frame1" scrolling="no" frameborder="no"…

    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 363, Column 97: there is no attribute "align"
    …scrolling="no" frameborder="no" align="center" height = "286px" width = "308px…

    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 363, Column 138: element "iframe" undefined
    …crolling="no" frameborder="no" align="center" height = "286px" width = "308px">

    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 369, Column 16: there is no attribute "bgcolor"
    <table bgcolor="#B9D3EE" bordercolor="#80FF00" border="0">

    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 369, Column 38: there is no attribute "bordercolor"
    <table bgcolor="#B9D3EE" bordercolor="#80FF00" border="0">

    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 369, Column 58: document type does not allow element "table" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <table bgcolor="#B9D3EE" bordercolor="#80FF00" border="0">

    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 372, Column 14: there is no attribute "color"
     <font color="red" size="2"><right> CLOSE (X) </right></font>

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

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

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

  • Error Line 372, Column 25: there is no attribute "size"
     <font color="red" size="2"><right> CLOSE (X) </right></font>

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

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

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

  • Error Line 372, Column 28: element "font" undefined
     <font color="red" size="2"><right> CLOSE (X) </right></font>

    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 372, Column 35: element "right" undefined
     <font color="red" size="2"><right> CLOSE (X) </right></font>

    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 374, Column 4: end tag for "td" omitted, but OMITTAG NO was specified
    </a>

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

  • Info Line 371, Column 2: start tag was here
     <td align="right">
  • Error Line 374, Column 4: end tag for "tr" omitted, but OMITTAG NO was specified
    </a>

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

  • Info Line 370, Column 2: start tag was here
     <tr>
  • Error Line 374, Column 4: end tag for "table" omitted, but OMITTAG NO was specified
    </a>

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

  • Info Line 369, Column 1: start tag was here
    <table bgcolor="#B9D3EE" bordercolor="#80FF00" border="0">
  • Error Line 376, Column 5: end tag for element "td" which is not open
    </td>

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

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

  • Error Line 377, Column 5: end tag for element "tr" which is not open
    </tr>

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

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

  • Error Line 378, Column 8: end tag for element "table" which is not open
    </table>

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

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

  • Error Line 380, Column 8: end tag for element "ul" which is not open
    			</ul>

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

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

  • Error Line 392, Column 8: element "center" undefined
    <center>

    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 400, Column 41: there is no attribute "target"
    … href="http://www.histats.com" target="_blank" title="web stats" ><script  typ…

    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 404, Column 59: document type does not allow element "a" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …ttp://www.histats.com" target="_blank"><img  src="http://sstatic1.histats.com/…

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

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

  • Warning Line 404, Column 112: character "&" is the first character of a delimiter but occurred as data
    …p://sstatic1.histats.com/0.gif?2240815&101" alt="web stats" border="0"></a></n…

    This message may appear in several cases:

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

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

  • Info Line 404, Column 60: start tag was here
    …tp://www.histats.com" target="_blank"><img  src="http://sstatic1.histats.com/0…
  • Error Line 405, Column 191: end tag for "center" omitted, but OMITTAG NO was specified
    …ipted by <a href="http://freeadultscript.com/">Adult Script V 2</a>.</p> </div>

    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 392, Column 1: start tag was here
    <center>
  • Error Line 406, Column 7: end tag for "div" omitted, but OMITTAG NO was specified
    </body>

    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 56, Column 1: start tag was here
    <div id="page">

Visitor Analysis

Daily Visitor
  • 910 visits