inyarwanda.com

Entertainment and people ...

Display Widget for this domain on your website. Click Here
This data was last updated from 09-07-2013 04:17:01  (update).

Overview Info

  • Domain Name
    inyarwanda.com
  • Favicon
  • Alexa Rank
    #56506
  • Google Page Rank
    PR 2
  • Ip Address
    198.57.188.174
  • Page Size
    79.6 KB
  • Images
    12 GIF, 53 JPG, 11 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    5 0 17 3 18 2

Website Meta Analysis



  • Title
    InyaRWANDA-Entertainment and People
  • Meta Keyword
    HTML,CSS,XML,JavaScript
  • Meta Description
    Entertainment and people

Technical Analysis



  • Webserver
    Apache/2.2.24 (Unix) mod_ssl/2.2.24 OpenSSL/1.0.0-fips mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635
  • Ip Address
    198.57.188.174
  • Domain Age
    5 Years, 0 Months, 23 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Tue, 09 Jul 2013 04:16:59 GMT
  • server: Apache/2.2.24 (Unix) mod_ssl/2.2.24 OpenSSL/1.0.0-fips mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635
  • x-powered-by: PHP/5.3.25
  • 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
  • content-type: text/html
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for inyarwanda.com

IP 198.57.188.174 Analysis

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

Site Same Ip

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 209 Errors
  • 29 Warnings
Ratio Text/Html
  • 0.6578543638081913
Message Error
  • Error Line 5, Column 61: end tag for "meta" omitted, but OMITTAG NO was specified
    <meta name="description" content="Entertainment and people">

    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 5, Column 1: start tag was here
    <meta name="description" content="Entertainment and people">
  • Error Line 6, Column 57: end tag for "meta" omitted, but OMITTAG NO was specified
    <meta name="keywords" content="HTML,CSS,XML,JavaScript">

    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 6, Column 1: start tag was here
    <meta name="keywords" content="HTML,CSS,XML,JavaScript">
  • Error Line 7, Column 48: end tag for "meta" omitted, but OMITTAG NO was specified
    <meta name="author" content="Emmauel Baziyaka">

    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 7, Column 1: start tag was here
    <meta name="author" content="Emmauel Baziyaka">
  • Error Line 20, Column 8: required attribute "type" not specified
    	<style>

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

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

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

  • Error Line 73, Column 64: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …		<a href="http://inyarwanda.com/signin"><div  class="signin">Sign In</div></a>

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

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

  • Error Line 74, Column 24: there is no attribute "data-toggle"
    		&nbsp;<a data-toggle="modal" href="#register" onclick="hideModal('newsletter'…

    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 74, Column 103: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …ter" onclick="hideModal('newsletter');"><div class="signup"> Register</div></a>

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

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

  • Error Line 78, Column 88: required attribute "alt" not specified
    …tp://inyarwanda.com/"><img src="http://inyarwanda.com/images/logo_top.png"></a>

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

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

  • Error Line 78, Column 92: end tag for "img" omitted, but OMITTAG NO was specified
    …tp://inyarwanda.com/"><img src="http://inyarwanda.com/images/logo_top.png"></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 78, Column 36: start tag was here
    		<a href="http://inyarwanda.com/"><img src="http://inyarwanda.com/images/logo_…
  • Error Line 82, Column 53: there is no attribute "placeholder"
    …ss="sb_input" type="text" placeholder="Type and Search" id="txt_search" name="…

    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 85, Column 38: the name and VI delimiter can be omitted from an attribute specification only if SHORTTAG YES is specified
    					  <option value="music" selected>Songs</option>

    "VI delimiter" is a technical term for the equal sign. This error message means that the name of an attribute and the equal sign cannot be omitted when specifying an attribute. A common cause for this error message is the use of "Attribute Minimization" in document types where it is not allowed, in XHTML for instance.

    How to fix: For attributes such as compact, checked or selected, do not write e.g <option selected ... but rather <option selected="selected" ...

  • Error Line 113, Column 84: document type does not allow element "link" here
    … type='text/css' rel='stylesheet' href='http://inyarwanda.com/css/alert.css' />

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

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

  • Error Line 114, Column 84: document type does not allow element "link" here
    … type='text/css' rel='stylesheet' href='http://inyarwanda.com/css/modal.css' />

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

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

  • Error Line 118, Column 33: there is no attribute "data-dismiss"
    		<a class="close" data-dismiss="modal">×</a>  

    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 127, Column 30: value of attribute "id" invalid: "6" cannot start a name
    				<input type="hidden" id="6_letters_code_one" name="6_letters_code"/>

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

  • Error Line 172, Column 30: value of attribute "id" invalid: "6" cannot start a name
    				<input type="hidden" id="6_letters_code_two" name="6_letters_code"/>

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

  • Error Line 178, Column 79: end tag for "input" omitted, but OMITTAG NO was specified
    							<input id="name" name="name" type="text" placeholder="Enter your name">

    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 178, Column 8: start tag was here
    							<input id="name" name="name" type="text" placeholder="Enter your name">
  • Error Line 184, Column 103: end tag for "input" omitted, but OMITTAG NO was specified
    …etter_id" name="newsletter_id" type="text" placeholder="Enter your email here">

    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 184, Column 8: start tag was here
    							<input id="newsletter_id" name="newsletter_id" type="text" placeholder="…
  • Error Line 198, Column 8: required attribute "type" not specified
    <script>

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

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

  • Warning Line 207, Column 46: cannot generate system identifier for general entity "view"
    …=$("#registration-frm").serialize()+"&view=authors&action=new&save=1&fileFromR…

    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 207, Column 46: general entity "view" not defined and no default entity
    …=$("#registration-frm").serialize()+"&view=authors&action=new&save=1&fileFromR…

    This is usually a cascading error caused by 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 207, Column 50: reference not terminated by REFC delimiter
    …#registration-frm").serialize()+"&view=authors&action=new&save=1&fileFromRegis…

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

  • Error Line 207, Column 50: reference to entity "view" for which no system identifier could be generated
    …#registration-frm").serialize()+"&view=authors&action=new&save=1&fileFromRegis…

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

  • Info Line 207, Column 45: entity was defined here
    …d=$("#registration-frm").serialize()+"&view=authors&action=new&save=1&fileFrom…
  • Warning Line 207, Column 59: cannot generate system identifier for general entity "action"
    …tion-frm").serialize()+"&view=authors&action=new&save=1&fileFromRegistration=1…

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

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

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

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

  • Error Line 207, Column 59: general entity "action" not defined and no default entity
    …tion-frm").serialize()+"&view=authors&action=new&save=1&fileFromRegistration=1…

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

  • Warning Line 207, Column 65: reference not terminated by REFC delimiter
    …rm").serialize()+"&view=authors&action=new&save=1&fileFromRegistration=1&webma…

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

  • Error Line 207, Column 65: reference to entity "action" for which no system identifier could be generated
    …rm").serialize()+"&view=authors&action=new&save=1&fileFromRegistration=1&webma…

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

  • Info Line 207, Column 58: entity was defined here
    …ation-frm").serialize()+"&view=authors&action=new&save=1&fileFromRegistration=…
  • Warning Line 207, Column 70: cannot generate system identifier for general entity "save"
    …serialize()+"&view=authors&action=new&save=1&fileFromRegistration=1&webmaster_…

    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 207, Column 70: general entity "save" not defined and no default entity
    …serialize()+"&view=authors&action=new&save=1&fileFromRegistration=1&webmaster_…

    This is usually a cascading error caused by 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 207, Column 74: reference not terminated by REFC delimiter
    …alize()+"&view=authors&action=new&save=1&fileFromRegistration=1&webmaster_emai…

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

  • Error Line 207, Column 74: reference to entity "save" for which no system identifier could be generated
    …alize()+"&view=authors&action=new&save=1&fileFromRegistration=1&webmaster_emai…

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

  • Info Line 207, Column 69: entity was defined here
    ….serialize()+"&view=authors&action=new&save=1&fileFromRegistration=1&webmaster…
  • Warning Line 207, Column 77: cannot generate system identifier for general entity "fileFromRegistration"
    …ze()+"&view=authors&action=new&save=1&fileFromRegistration=1&webmaster_email=b…

    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 207, Column 77: general entity "fileFromRegistration" not defined and no default entity
    …ze()+"&view=authors&action=new&save=1&fileFromRegistration=1&webmaster_email=b…

    This is usually a cascading error caused by 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 207, Column 97: reference not terminated by REFC delimiter
    …action=new&save=1&fileFromRegistration=1&webmaster_email=baziyaka@gmail.com&st…

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

  • Error Line 207, Column 97: reference to entity "fileFromRegistration" for which no system identifier could be generated
    …action=new&save=1&fileFromRegistration=1&webmaster_email=baziyaka@gmail.com&st…

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

  • Info Line 207, Column 76: entity was defined here
    …ize()+"&view=authors&action=new&save=1&fileFromRegistration=1&webmaster_email=…
  • Warning Line 207, Column 100: cannot generate system identifier for general entity "webmaster_email"
    …ion=new&save=1&fileFromRegistration=1&webmaster_email=baziyaka@gmail.com&statu…

    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 207, Column 100: general entity "webmaster_email" not defined and no default entity
    …ion=new&save=1&fileFromRegistration=1&webmaster_email=baziyaka@gmail.com&statu…

    This is usually a cascading error caused by 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 207, Column 115: reference not terminated by REFC delimiter
    …fileFromRegistration=1&webmaster_email=baziyaka@gmail.com&status=1&category=ar…

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

  • Error Line 207, Column 115: reference to entity "webmaster_email" for which no system identifier could be generated
    …fileFromRegistration=1&webmaster_email=baziyaka@gmail.com&status=1&category=ar…

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

  • Info Line 207, Column 99: entity was defined here
    …tion=new&save=1&fileFromRegistration=1&webmaster_email=baziyaka@gmail.com&stat…
  • Warning Line 207, Column 135: cannot generate system identifier for general entity "status"
    …romRegistration=1&webmaster_email=baziyaka@gmail.com&status=1&category=artist";

    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 207, Column 135: general entity "status" not defined and no default entity
    …romRegistration=1&webmaster_email=baziyaka@gmail.com&status=1&category=artist";

    This is usually a cascading error caused by 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 207, Column 141: reference not terminated by REFC delimiter
    …romRegistration=1&webmaster_email=baziyaka@gmail.com&status=1&category=artist";

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

  • Error Line 207, Column 141: reference to entity "status" for which no system identifier could be generated
    …romRegistration=1&webmaster_email=baziyaka@gmail.com&status=1&category=artist";

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

  • Info Line 207, Column 134: entity was defined here
    …romRegistration=1&webmaster_email=baziyaka@gmail.com&status=1&category=artist";
  • Warning Line 207, Column 144: cannot generate system identifier for general entity "category"
    …romRegistration=1&webmaster_email=baziyaka@gmail.com&status=1&category=artist";

    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 207, Column 144: general entity "category" not defined and no default entity
    …romRegistration=1&webmaster_email=baziyaka@gmail.com&status=1&category=artist";

    This is usually a cascading error caused by 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 207, Column 152: reference not terminated by REFC delimiter
    …romRegistration=1&webmaster_email=baziyaka@gmail.com&status=1&category=artist";

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

  • Error Line 207, Column 152: reference to entity "category" for which no system identifier could be generated
    …romRegistration=1&webmaster_email=baziyaka@gmail.com&status=1&category=artist";

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

  • Info Line 207, Column 143: entity was defined here
    …romRegistration=1&webmaster_email=baziyaka@gmail.com&status=1&category=artist";
  • Error Line 217, Column 56: document type does not allow element "h4" here
    …-msg").html("<h4 class='alert_success'>Your account has been created successfu…

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

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

  • Error Line 217, Column 165: document type does not allow element "br" here
    …ully. Check you email for your account information. Thank you</h4><br/><br/>");

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

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

  • Error Line 217, Column 170: document type does not allow element "br" here
    …ully. Check you email for your account information. Thank you</h4><br/><br/>");

    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 242, Column 48: reference not terminated by REFC delimiter
    …("#newsletter_frm").serialize()+"&view=newsletter&action=new&save=1&fileFromNe…

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

  • Error Line 242, Column 48: reference to entity "view" for which no system identifier could be generated
    …("#newsletter_frm").serialize()+"&view=newsletter&action=new&save=1&fileFromNe…

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

  • Info Line 207, Column 45: entity was defined here
    …d=$("#registration-frm").serialize()+"&view=authors&action=new&save=1&fileFrom…
  • Warning Line 242, Column 66: reference not terminated by REFC delimiter
    …).serialize()+"&view=newsletter&action=new&save=1&fileFromNewsletter=1&webmast…

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

  • Error Line 242, Column 66: reference to entity "action" for which no system identifier could be generated
    …).serialize()+"&view=newsletter&action=new&save=1&fileFromNewsletter=1&webmast…

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

  • Info Line 207, Column 58: entity was defined here
    …ation-frm").serialize()+"&view=authors&action=new&save=1&fileFromRegistration=…
  • Warning Line 242, Column 75: reference not terminated by REFC delimiter
    …ze()+"&view=newsletter&action=new&save=1&fileFromNewsletter=1&webmaster_email=…

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

  • Error Line 242, Column 75: reference to entity "save" for which no system identifier could be generated
    …ze()+"&view=newsletter&action=new&save=1&fileFromNewsletter=1&webmaster_email=…

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

  • Info Line 207, Column 69: entity was defined here
    ….serialize()+"&view=authors&action=new&save=1&fileFromRegistration=1&webmaster…
  • Warning Line 242, Column 78: cannot generate system identifier for general entity "fileFromNewsletter"
    …)+"&view=newsletter&action=new&save=1&fileFromNewsletter=1&webmaster_email=baz…

    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 242, Column 78: general entity "fileFromNewsletter" not defined and no default entity
    …)+"&view=newsletter&action=new&save=1&fileFromNewsletter=1&webmaster_email=baz…

    This is usually a cascading error caused by 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 242, Column 96: reference not terminated by REFC delimiter
    …r&action=new&save=1&fileFromNewsletter=1&webmaster_email=baziyaka@gmail.com&ro…

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

  • Error Line 242, Column 96: reference to entity "fileFromNewsletter" for which no system identifier could be generated
    …r&action=new&save=1&fileFromNewsletter=1&webmaster_email=baziyaka@gmail.com&ro…

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

  • Info Line 242, Column 77: entity was defined here
    …()+"&view=newsletter&action=new&save=1&fileFromNewsletter=1&webmaster_email=ba…
  • Warning Line 242, Column 114: reference not terminated by REFC delimiter
    …1&fileFromNewsletter=1&webmaster_email=baziyaka@gmail.com&root_folder=http://i…

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

  • Error Line 242, Column 114: reference to entity "webmaster_email" for which no system identifier could be generated
    …1&fileFromNewsletter=1&webmaster_email=baziyaka@gmail.com&root_folder=http://i…

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

  • Info Line 207, Column 99: entity was defined here
    …tion=new&save=1&fileFromRegistration=1&webmaster_email=baziyaka@gmail.com&stat…
  • Warning Line 242, Column 134: cannot generate system identifier for general entity "root_folder"
    …letter=1&webmaster_email=baziyaka@gmail.com&root_folder=http://inyarwanda.com";

    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 242, Column 134: general entity "root_folder" not defined and no default entity
    …letter=1&webmaster_email=baziyaka@gmail.com&root_folder=http://inyarwanda.com";

    This is usually a cascading error caused by 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 242, Column 145: reference not terminated by REFC delimiter
    …letter=1&webmaster_email=baziyaka@gmail.com&root_folder=http://inyarwanda.com";

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

  • Error Line 242, Column 145: reference to entity "root_folder" for which no system identifier could be generated
    …letter=1&webmaster_email=baziyaka@gmail.com&root_folder=http://inyarwanda.com";

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

  • Info Line 242, Column 133: entity was defined here
    …letter=1&webmaster_email=baziyaka@gmail.com&root_folder=http://inyarwanda.com";
  • Error Line 254, Column 67: document type does not allow element "h4" here
    …-msg").html("<h4 class='alert_success'>Your registration terminated with succe…

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

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

  • Error Line 254, Column 129: document type does not allow element "br" here
    …success'>Your registration terminated with success. Thank you</h4><br/><br/>");

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

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

  • Error Line 254, Column 134: document type does not allow element "br" here
    …success'>Your registration terminated with success. Thank you</h4><br/><br/>");

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

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

  • Error Line 284, Column 116: required attribute "alt" not specified
    …a.com/"><img src="http://inyarwanda.com/images/InyarwandaLogo3.png" ></a></div>

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

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

  • Error Line 284, Column 120: end tag for "img" omitted, but OMITTAG NO was specified
    …a.com/"><img src="http://inyarwanda.com/images/InyarwandaLogo3.png" ></a></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 284, Column 56: start tag was here
    …ogo"><a href="http://inyarwanda.com/"><img src="http://inyarwanda.com/images/I…
  • Error Line 285, Column 160: required attribute "alt" not specified
    …tp://inyarwanda.com/adverts/tigo-SIM-AQ.gif" width="683" height="75"></a></div>

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

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

  • Error Line 285, Column 164: end tag for "img" omitted, but OMITTAG NO was specified
    …tp://inyarwanda.com/adverts/tigo-SIM-AQ.gif" width="683" height="75"></a></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 285, Column 80: start tag was here
    …ttp://www.tigo.co.rw" target="_blank"><img src="http://inyarwanda.com/adverts/…
  • Error Line 403, Column 115: required attribute "alt" not specified
    …ttp://inyarwanda.com/adverts/MTN Zone - inyarwanda web banner - rwandese.jpg" >

    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 403, Column 116: end tag for "img" omitted, but OMITTAG NO was specified
    …ttp://inyarwanda.com/adverts/MTN Zone - inyarwanda web banner - rwandese.jpg" >

    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 403, Column 6: start tag was here
    					<img style="width:900px;"src="http://inyarwanda.com/adverts/MTN Zone - iny…
  • Error Line 413, Column 9: required attribute "type" not specified
    		<style>

    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 413, Column 9: document type does not allow element "style" here
    		<style>

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

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

  • Error Line 421, Column 87: document type does not allow element "link" here
    …ef="http://inyarwanda.com/css/homepage.css" rel="stylesheet" type="text/css" />

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

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

  • Error Line 422, Column 95: document type does not allow element "link" here
    …://inyarwanda.com/css/Selectyze.jquery.css" rel="stylesheet" type="text/css" />

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

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

  • Error Line 423, Column 96: document type does not allow element "link" here
    …//inyarwanda.com/pub/fespad/CSS/global.css" rel="stylesheet" type="text/css" />

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

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

  • Error Line 426, Column 8: required attribute "type" not specified
    <script>

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

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

  • Warning Line 431, Column 9: character "<" is the first character of a delimiter but occurred as data
    while(k < i)

    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 450, Column 63: document type does not allow element "a" here
    …='http://inyarwanda.com/article/50517'>Umuhanzi w’icyamamare Ice Prince ubu ar…

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

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

  • Error Line 450, Column 186: document type does not allow element "a" here
    …='http://inyarwanda.com/article/50512'>Brad Pitt na Angelina Jolie bagiye kwam…

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

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

  • Error Line 450, Column 292: document type does not allow element "a" here
    …='http://inyarwanda.com/article/50509'>Abakobwa 9 nibo bahatanira Miss East Af…

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

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

  • Error Line 450, Column 417: document type does not allow element "a" here
    …='http://inyarwanda.com/article/50507'>Jaguar mu myaka ishize yari umukene non…

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

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

  • Error Line 450, Column 533: document type does not allow element "a" here
    …='http://inyarwanda.com/article/50506'>Umutekano wa Rick Ross ukomeje kumuhang…

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

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

  • Error Line 450, Column 634: document type does not allow element "a" here
    …='http://inyarwanda.com/article/50505'>Abatsinze amarushanwa yo kubyina mu nta…

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

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

  • Error Line 461, Column 54: document type does not allow element "span" here
    …pan style='float:right;color:#18699D;'><a href='http://inyarwanda.com/article/…

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

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

  • Error Line 461, Column 194: document type does not allow element "span" here
    …pan style='float:right;color:#18699D;'><a href='http://inyarwanda.com/article/…

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

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

  • Error Line 461, Column 334: document type does not allow element "span" here
    …pan style='float:right;color:#18699D;'><a href='http://inyarwanda.com/article/…

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

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

  • Error Line 461, Column 474: document type does not allow element "span" here
    …pan style='float:right;color:#18699D;'><a href='http://inyarwanda.com/article/…

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

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

  • Error Line 461, Column 614: document type does not allow element "span" here
    …pan style='float:right;color:#18699D;'><a href='http://inyarwanda.com/article/…

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

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

  • Error Line 461, Column 754: document type does not allow element "span" here
    …pan style='float:right;color:#18699D;'><a href='http://inyarwanda.com/article/…

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

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

  • Error Line 474, Column 19: there is no attribute "loop"
    				<marquee loop="infinity"  onmouseover="this.stop();" onmouseout="this.start…

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

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

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

  • Error Line 474, Column 43: there is no attribute "onmouseover"
    …<marquee loop="infinity"  onmouseover="this.stop();" onmouseout="this.start();…

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

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

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

  • Error Line 474, Column 69: there is no attribute "onmouseout"
    …onmouseover="this.stop();" onmouseout="this.start();" SCROLLAMOUNT=2 SCROLLDEL…

    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 474, Column 98: there is no attribute "SCROLLAMOUNT"
    …mouseout="this.start();" SCROLLAMOUNT=2 SCROLLDELAY=10 BEHAVIOR="SCROLL" DIREC…

    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 474, Column 98: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …mouseout="this.start();" SCROLLAMOUNT=2 SCROLLDELAY=10 BEHAVIOR="SCROLL" DIREC…
  • Error Line 474, Column 112: there is no attribute "SCROLLDELAY"
    …is.start();" SCROLLAMOUNT=2 SCROLLDELAY=10 BEHAVIOR="SCROLL" DIRECTION="left" >

    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 474, Column 112: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …is.start();" SCROLLAMOUNT=2 SCROLLDELAY=10 BEHAVIOR="SCROLL" DIRECTION="left" >
  • Error Line 474, Column 124: there is no attribute "BEHAVIOR"
    …is.start();" SCROLLAMOUNT=2 SCROLLDELAY=10 BEHAVIOR="SCROLL" DIRECTION="left" >

    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 474, Column 143: there is no attribute "DIRECTION"
    …is.start();" SCROLLAMOUNT=2 SCROLLDELAY=10 BEHAVIOR="SCROLL" DIRECTION="left" >

    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 474, Column 150: element "marquee" undefined
    …is.start();" SCROLLAMOUNT=2 SCROLLDELAY=10 BEHAVIOR="SCROLL" DIRECTION="left" >

    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 483, Column 19: end tag for "span" omitted, but OMITTAG NO was specified
    									</marquee>

    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 482, Column 130: start tag was here
    …0244">95% by’bakobwa bajya mu tubyiniro i Kampala ntibikoza amakariso</a><span>
  • Error Line 483, Column 19: end tag for "span" omitted, but OMITTAG NO was specified
    									</marquee>

    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 482, Column 11: start tag was here
    										<span><a href="http://inyarwanda.com/article/50244">95% by’bakobwa ba…
  • Error Line 483, Column 19: end tag for "span" omitted, but OMITTAG NO was specified
    									</marquee>

    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 481, Column 116: start tag was here
    ….com/article/50436">LIVE: Ni ibicika mu gitaramo cyo gufungura FESPAD</a><span>
  • Error Line 483, Column 19: end tag for "span" omitted, but OMITTAG NO was specified
    									</marquee>

    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 481, Column 11: start tag was here
    										<span><a href="http://inyarwanda.com/article/50436">LIVE: Ni ibicika …
  • Error Line 483, Column 19: end tag for "span" omitted, but OMITTAG NO was specified
    									</marquee>

    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 480, Column 158: start tag was here
    …yo kubyina mu ntara y'Uburengerazuba muri FESPAD bamenyekanye-AMAFOTO</a><span>
  • Error Line 483, Column 19: end tag for "span" omitted, but OMITTAG NO was specified
    									</marquee>

    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 480, Column 11: start tag was here
    										<span><a href="http://inyarwanda.com/article/50505">Abatsinze amarush…
  • Error Line 483, Column 19: end tag for "span" omitted, but OMITTAG NO was specified
    									</marquee>

    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 479, Column 114: start tag was here
    …da.com/article/50506">Umutekano wa Rick Ross ukomeje kumuhangayikisha</a><span>
  • Error Line 483, Column 19: end tag for "span" omitted, but OMITTAG NO was specified
    									</marquee>

    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 479, Column 11: start tag was here
    										<span><a href="http://inyarwanda.com/article/50506">Umutekano wa Rick…
  • Error Line 483, Column 19: end tag for "span" omitted, but OMITTAG NO was specified
    									</marquee>

    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 478, Column 129: start tag was here
    …50507">Jaguar mu myaka ishize yari umukene none ubuzima bwarahindutse</a><span>
  • Error Line 483, Column 19: end tag for "span" omitted, but OMITTAG NO was specified
    									</marquee>

    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 478, Column 11: start tag was here
    										<span><a href="http://inyarwanda.com/article/50507">Jaguar mu myaka i…
  • Error Line 483, Column 19: end tag for "span" omitted, but OMITTAG NO was specified
    									</marquee>

    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 477, Column 138: start tag was here
    …akobwa 9 nibo bahatanira Miss East Africa muri Afurika y’epfo-AMAFOTO</a><span>
  • Error Line 483, Column 19: end tag for "span" omitted, but OMITTAG NO was specified
    									</marquee>

    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 477, Column 11: start tag was here
    										<span><a href="http://inyarwanda.com/article/50509">Abakobwa 9 nibo b…
  • Error Line 483, Column 19: end tag for "span" omitted, but OMITTAG NO was specified
    									</marquee>

    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 476, Column 119: start tag was here
    …m/article/50512">Brad Pitt na Angelina Jolie bagiye kwambikana impeta</a><span>
  • Error Line 483, Column 19: end tag for "span" omitted, but OMITTAG NO was specified
    									</marquee>

    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 476, Column 11: start tag was here
    										<span><a href="http://inyarwanda.com/article/50512">Brad Pitt na Ange…
  • Error Line 483, Column 19: end tag for "span" omitted, but OMITTAG NO was specified
    									</marquee>

    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 475, Column 136: start tag was here
    …Umuhanzi w’icyamamare Ice Prince ubu ari mundege aza mu Rwanda-VIDEO.</a><span>
  • Error Line 483, Column 19: end tag for "span" omitted, but OMITTAG NO was specified
    									</marquee>

    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 475, Column 11: start tag was here
    										<span><a href="http://inyarwanda.com/article/50517">Umuhanzi w’icyama…
  • Error Line 536, Column 13: required attribute "type" not specified
    						<style>

    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 536, Column 13: document type does not allow element "style" here
    						<style>

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

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

  • Error Line 541, Column 65: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ight="310" align="middle" frameborder=0 scrolling="no" src="http://inyarwanda.…
  • Error Line 548, Column 84: required attribute "alt" not specified
    …<a href="http://inyarwanda.com/billboard"><img src="images/billboard.gif" ></a>

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

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

  • Error Line 548, Column 88: end tag for "img" omitted, but OMITTAG NO was specified
    …<a href="http://inyarwanda.com/billboard"><img src="images/billboard.gif" ></a>

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

  • Info Line 548, Column 52: start tag was here
    …<a href="http://inyarwanda.com/billboard"><img src="images/billboard.gif" ></a>
  • Error Line 551, Column 82: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …wanda.com/webradio-karahanyuze"><div class="webradiomenu">Karahanyuze</div></a>

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

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

  • Error Line 552, Column 77: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …tp://inyarwanda.com/webradio-gospel"><div class="webradiomenu">Gospel</div></a>

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

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

  • Error Line 553, Column 77: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …p://inyarwanda.com/webradio-hiphop"><div class="webradiomenu">Hip Hop</div></a>

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

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

  • Error Line 554, Column 80: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …nyarwanda.com/webradio-igitaramo"><div class="webradiomenu">Igitaramo</div></a>

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

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

  • Error Line 555, Column 77: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …tp://inyarwanda.com/webradio-inanga"><div class="webradiomenu">Inanga</div></a>

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

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

  • Error Line 556, Column 75: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …="http://inyarwanda.com/webradio-zouk"><div class="webradiomenu">Zouk</div></a>

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

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

  • Error Line 557, Column 74: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …="http://inyarwanda.com/webradio-rnb"><div class="webradiomenu">R'n'b</div></a>

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

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

  • Error Line 558, Column 76: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …http://inyarwanda.com/webradio-slows"><div class="webradiomenu">Shows</div></a>

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

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

  • Error Line 559, Column 65: required attribute "alt" not specified
    			<div class="switched-banner2"><img src="images/webradio.png" ></div>

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

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

  • Error Line 559, Column 71: end tag for "img" omitted, but OMITTAG NO was specified
    			<div class="switched-banner2"><img src="images/webradio.png" ></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 559, Column 34: start tag was here
    			<div class="switched-banner2"><img src="images/webradio.png" ></div>
  • Error Line 587, Column 60: document type does not allow element "h4" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …tp://inyarwanda.com/article/50516"><h4>Senderi Interantional Hit, Lil G, Maven…

    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 601, Column 116: required attribute "alt" not specified
    …"http://inyarwanda.com/media/images/news/thumbs/1362057824355477575.jpg"></div>

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

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

  • Error Line 601, Column 122: end tag for "img" omitted, but OMITTAG NO was specified
    …"http://inyarwanda.com/media/images/news/thumbs/1362057824355477575.jpg"></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 601, Column 35: start tag was here
    									<div class="logoarticle"><img src="http://inyarwanda.com/media/images/…
  • Error Line 614, Column 116: required attribute "alt" not specified
    …"http://inyarwanda.com/media/images/news/thumbs/1362039152331652811.jpg"></div>

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

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

  • Error Line 614, Column 122: end tag for "img" omitted, but OMITTAG NO was specified
    …"http://inyarwanda.com/media/images/news/thumbs/1362039152331652811.jpg"></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 614, Column 35: start tag was here
    									<div class="logoarticle"><img src="http://inyarwanda.com/media/images/…
  • Error Line 627, Column 117: required attribute "alt" not specified
    …http://inyarwanda.com/media/images/news/thumbs/13620374341109527258.jpg"></div>

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

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

  • Error Line 627, Column 123: end tag for "img" omitted, but OMITTAG NO was specified
    …http://inyarwanda.com/media/images/news/thumbs/13620374341109527258.jpg"></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 627, Column 35: start tag was here
    									<div class="logoarticle"><img src="http://inyarwanda.com/media/images/…
  • Error Line 640, Column 117: required attribute "alt" not specified
    …http://inyarwanda.com/media/images/news/thumbs/13619817521992439852.jpg"></div>

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

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

  • Error Line 640, Column 123: end tag for "img" omitted, but OMITTAG NO was specified
    …http://inyarwanda.com/media/images/news/thumbs/13619817521992439852.jpg"></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 640, Column 35: start tag was here
    									<div class="logoarticle"><img src="http://inyarwanda.com/media/images/…
  • Error Line 653, Column 117: required attribute "alt" not specified
    …http://inyarwanda.com/media/images/news/thumbs/13619713451040231437.JPG"></div>

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

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

  • Error Line 653, Column 123: end tag for "img" omitted, but OMITTAG NO was specified
    …http://inyarwanda.com/media/images/news/thumbs/13619713451040231437.JPG"></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 653, Column 35: start tag was here
    									<div class="logoarticle"><img src="http://inyarwanda.com/media/images/…
  • Error Line 666, Column 117: required attribute "alt" not specified
    …http://inyarwanda.com/media/images/news/thumbs/13619651311394279485.jpg"></div>

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

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

  • Error Line 666, Column 123: end tag for "img" omitted, but OMITTAG NO was specified
    …http://inyarwanda.com/media/images/news/thumbs/13619651311394279485.jpg"></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 666, Column 35: start tag was here
    									<div class="logoarticle"><img src="http://inyarwanda.com/media/images/…
  • Error Line 679, Column 117: required attribute "alt" not specified
    …http://inyarwanda.com/media/images/news/thumbs/13619479982025076770.jpg"></div>

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

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

  • Error Line 679, Column 123: end tag for "img" omitted, but OMITTAG NO was specified
    …http://inyarwanda.com/media/images/news/thumbs/13619479982025076770.jpg"></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 679, Column 35: start tag was here
    									<div class="logoarticle"><img src="http://inyarwanda.com/media/images/…
  • Error Line 705, Column 61: document type does not allow element "h4" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …tp://inyarwanda.com/article/50515"><h4>Indoneziya: Umugore yishe umwana we amu…

    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 719, Column 118: required attribute "alt" not specified
    …http://inyarwanda.com/media/images/news/thumbs/13619806131347325611.jpg"></div>

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

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

  • Error Line 719, Column 124: end tag for "img" omitted, but OMITTAG NO was specified
    …http://inyarwanda.com/media/images/news/thumbs/13619806131347325611.jpg"></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 719, Column 36: start tag was here
    										<div class="logoarticle"><img src="http://inyarwanda.com/media/images…
  • Error Line 730, Column 117: required attribute "alt" not specified
    …"http://inyarwanda.com/media/images/news/thumbs/1361975601399411347.jpg"></div>

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

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

  • Error Line 730, Column 123: end tag for "img" omitted, but OMITTAG NO was specified
    …"http://inyarwanda.com/media/images/news/thumbs/1361975601399411347.jpg"></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 730, Column 36: start tag was here
    										<div class="logoarticle"><img src="http://inyarwanda.com/media/images…
  • Error Line 741, Column 118: required attribute "alt" not specified
    …http://inyarwanda.com/media/images/news/thumbs/13619745091553010413.jpg"></div>

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

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

  • Error Line 741, Column 124: end tag for "img" omitted, but OMITTAG NO was specified
    …http://inyarwanda.com/media/images/news/thumbs/13619745091553010413.jpg"></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 741, Column 36: start tag was here
    										<div class="logoarticle"><img src="http://inyarwanda.com/media/images…
  • Error Line 752, Column 117: required attribute "alt" not specified
    …"http://inyarwanda.com/media/images/news/thumbs/1361950783629498985.jpg"></div>

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

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

  • Error Line 752, Column 123: end tag for "img" omitted, but OMITTAG NO was specified
    …"http://inyarwanda.com/media/images/news/thumbs/1361950783629498985.jpg"></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 752, Column 36: start tag was here
    										<div class="logoarticle"><img src="http://inyarwanda.com/media/images…
  • Error Line 763, Column 116: required attribute "alt" not specified
    …="http://inyarwanda.com/media/images/news/thumbs/136189549325494105.jpg"></div>

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

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

  • Error Line 763, Column 122: end tag for "img" omitted, but OMITTAG NO was specified
    …="http://inyarwanda.com/media/images/news/thumbs/136189549325494105.jpg"></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 763, Column 36: start tag was here
    										<div class="logoarticle"><img src="http://inyarwanda.com/media/images…
  • Error Line 774, Column 118: required attribute "alt" not specified
    …http://inyarwanda.com/media/images/news/thumbs/1361888067275606764.jpeg"></div>

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

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

  • Error Line 774, Column 124: end tag for "img" omitted, but OMITTAG NO was specified
    …http://inyarwanda.com/media/images/news/thumbs/1361888067275606764.jpeg"></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 774, Column 36: start tag was here
    										<div class="logoarticle"><img src="http://inyarwanda.com/media/images…
  • Error Line 785, Column 118: required attribute "alt" not specified
    …http://inyarwanda.com/media/images/news/thumbs/13618863331252391309.JPG"></div>

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

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

  • Error Line 785, Column 124: end tag for "img" omitted, but OMITTAG NO was specified
    …http://inyarwanda.com/media/images/news/thumbs/13618863331252391309.JPG"></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 785, Column 36: start tag was here
    										<div class="logoarticle"><img src="http://inyarwanda.com/media/images…
  • Error Line 916, Column 71: required attribute "alt" not specified
    			<img src="http://inyarwanda.com/pub/fespad/images/fespad_kg_bg.png">

    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 916, Column 72: end tag for "img" omitted, but OMITTAG NO was specified
    			<img src="http://inyarwanda.com/pub/fespad/images/fespad_kg_bg.png">

    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 916, Column 4: start tag was here
    			<img src="http://inyarwanda.com/pub/fespad/images/fespad_kg_bg.png">
  • Error Line 920, Column 133: required attribute "alt" not specified
    …="http://inyarwanda.com/media/images/news/thumbs/13620536791470137673.jpg"></a>

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

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

  • Error Line 920, Column 137: end tag for "img" omitted, but OMITTAG NO was specified
    …="http://inyarwanda.com/media/images/news/thumbs/13620536791470137673.jpg"></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 920, Column 51: start tag was here
    …"http://inyarwanda.com/article/50511"><img src="http://inyarwanda.com/media/im…
  • Error Line 927, Column 133: required attribute "alt" not specified
    …="http://inyarwanda.com/media/images/news/thumbs/13619702031804684489.jpg"></a>

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

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

  • Error Line 927, Column 137: end tag for "img" omitted, but OMITTAG NO was specified
    …="http://inyarwanda.com/media/images/news/thumbs/13619702031804684489.jpg"></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 927, Column 51: start tag was here
    …"http://inyarwanda.com/article/50497"><img src="http://inyarwanda.com/media/im…
  • Error Line 934, Column 132: required attribute "alt" not specified
    …c="http://inyarwanda.com/media/images/news/thumbs/1361965663482211793.jpg"></a>

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

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

  • Error Line 934, Column 136: end tag for "img" omitted, but OMITTAG NO was specified
    …c="http://inyarwanda.com/media/images/news/thumbs/1361965663482211793.jpg"></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 934, Column 51: start tag was here
    …"http://inyarwanda.com/article/50492"><img src="http://inyarwanda.com/media/im…
  • Error Line 941, Column 133: required attribute "alt" not specified
    …="http://inyarwanda.com/media/images/news/thumbs/13619504781361587011.jpg"></a>

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

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

  • Error Line 941, Column 137: end tag for "img" omitted, but OMITTAG NO was specified
    …="http://inyarwanda.com/media/images/news/thumbs/13619504781361587011.jpg"></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 941, Column 51: start tag was here
    …"http://inyarwanda.com/article/50489"><img src="http://inyarwanda.com/media/im…
  • Error Line 948, Column 132: required attribute "alt" not specified
    …c="http://inyarwanda.com/media/images/news/thumbs/1361909500189280733.jpg"></a>

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

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

  • Error Line 948, Column 136: end tag for "img" omitted, but OMITTAG NO was specified
    …c="http://inyarwanda.com/media/images/news/thumbs/1361909500189280733.jpg"></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 948, Column 51: start tag was here
    …"http://inyarwanda.com/article/50485"><img src="http://inyarwanda.com/media/im…
  • Error Line 960, Column 8: required attribute "type" not specified
    <script>

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

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

  • Error Line 968, Column 133: document type does not allow element "link" here
    …com/pub/vertical-slider/style-newsticker.css" type="text/css" media="screen" />

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

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

  • Error Line 990, Column 133: required attribute "alt" not specified
    …ews-arrow-previous.png" class="previous" style="width:auto;margin-left:50%;" />

    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 995, Column 30: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    				<div style="margin:auto;"><img src="http://inyarwanda.com/media/images/news…

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

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

  • Error Line 995, Column 125: required attribute "alt" not specified
    …wanda.com/media/images/news/1362057382633646289.jpg" style="width:336px"></div>

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

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

  • Error Line 995, Column 131: end tag for "img" omitted, but OMITTAG NO was specified
    …wanda.com/media/images/news/1362057382633646289.jpg" style="width:336px"></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 995, Column 31: start tag was here
    				<div style="margin:auto;"><img src="http://inyarwanda.com/media/images/news…
  • Error Line 1000, Column 30: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    				<div style="margin:auto;"><img src="http://inyarwanda.com/media/images/news…

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

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

  • Error Line 1000, Column 126: required attribute "alt" not specified
    …anda.com/media/images/news/13619060391656301155.jpg" style="width:336px"></div>

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

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

  • Error Line 1000, Column 132: end tag for "img" omitted, but OMITTAG NO was specified
    …anda.com/media/images/news/13619060391656301155.jpg" style="width:336px"></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 1000, Column 31: start tag was here
    				<div style="margin:auto;"><img src="http://inyarwanda.com/media/images/news…
  • Error Line 1005, Column 30: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    				<div style="margin:auto;"><img src="http://inyarwanda.com/media/images/news…

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

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

  • Error Line 1005, Column 125: required attribute "alt" not specified
    …wanda.com/media/images/news/1361431682623180240.jpg" style="width:336px"></div>

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

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

  • Error Line 1005, Column 131: end tag for "img" omitted, but OMITTAG NO was specified
    …wanda.com/media/images/news/1361431682623180240.jpg" style="width:336px"></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 1005, Column 31: start tag was here
    				<div style="margin:auto;"><img src="http://inyarwanda.com/media/images/news…
  • Error Line 1010, Column 30: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    				<div style="margin:auto;"><img src="http://inyarwanda.com/media/images/news…

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

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

  • Error Line 1010, Column 125: required attribute "alt" not specified
    …wanda.com/media/images/news/1358833527111554925.gif" style="width:336px"></div>

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

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

  • Error Line 1010, Column 131: end tag for "img" omitted, but OMITTAG NO was specified
    …wanda.com/media/images/news/1358833527111554925.gif" style="width:336px"></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 1010, Column 31: start tag was here
    				<div style="margin:auto;"><img src="http://inyarwanda.com/media/images/news…
  • Error Line 1015, Column 120: required attribute "alt" not specified
    …ical-slider/news-arrow.png" class="next" style="width:auto;margin-left:50%;" />

    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 1057, Column 40: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …						<p class="sng"><div class="sgnm"><a href="http://inyarwanda.com/music/89…

    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 1058, Column 24: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    							<div class="sga"><span class="snga"><a href="http://inyarwanda.com/artis…

    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 1065, Column 40: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …						<p class="sng"><div class="sgnm"><a href="http://inyarwanda.com/music/89…

    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 1066, Column 24: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    							<div class="sga"><span class="snga"><a href="http://inyarwanda.com/artis…

    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 1073, Column 40: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …						<p class="sng"><div class="sgnm"><a href="http://inyarwanda.com/music/89…

    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 1074, Column 24: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    							<div class="sga"><span class="snga"><a href="http://inyarwanda.com/artis…

    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 1081, Column 40: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …						<p class="sng"><div class="sgnm"><a href="http://inyarwanda.com/music/89…

    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 1082, Column 24: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    							<div class="sga"><span class="snga"><a href="http://inyarwanda.com/artis…

    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 1089, Column 40: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …						<p class="sng"><div class="sgnm"><a href="http://inyarwanda.com/music/88…

    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 1090, Column 24: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    							<div class="sga"><span class="snga"><a href="http://inyarwanda.com/artis…

    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 1100, Column 52: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    							<div class="newsletter" style="height:auto;">

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

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

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

  • Error Line 1216, Column 144: "allowfullscreen" is not a member of a group specified for any attribute
    …feature=player_detailpage" frameborder="0" allowfullscreen></iframe>					</div>
  • Error Line 1301, Column 124: required attribute "alt" not specified
    …mg src='http://inyarwanda.com/adverts/1361439552FamilyTV001.gif'></a>				</div>

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

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

  • Error Line 1301, Column 128: end tag for "img" omitted, but OMITTAG NO was specified
    …mg src='http://inyarwanda.com/adverts/1361439552FamilyTV001.gif'></a>				</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 1301, Column 58: start tag was here
    …nk' href='http://www.rwandafamily.tv'><img src='http://inyarwanda.com/adverts/…
  • Error Line 1492, Column 39: there is no attribute "data-href"
    			<div class="fb-like-box" data-href="http://www.facebook.com/inyarwandadotcom…

    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 1492, Column 93: there is no attribute "data-width"
    …book.com/inyarwandadotcom" data-width="240" data-height="300" data-show-faces=…

    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 1492, Column 111: there is no attribute "data-height"
    …adotcom" data-width="240" data-height="300" data-show-faces="true" data-stream…

    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 1492, Column 133: there is no attribute "data-show-faces"
    …40" data-height="300" data-show-faces="true" data-stream="false" data-border-c…

    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 1492, Column 152: there is no attribute "data-stream"
    …0" data-show-faces="true" data-stream="false" data-border-color="#ffffff" data…

    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 1492, Column 178: there is no attribute "data-border-color"
    …rue" data-stream="false" data-border-color="#ffffff" data-header="false"></div>

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

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

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

  • Error Line 1492, Column 200: there is no attribute "data-header"
    …rue" data-stream="false" data-border-color="#ffffff" data-header="false"></div>

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

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

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

  • Error Line 1498, Column 8: required attribute "type" not specified
    <script>(function(d, s, id) {

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

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

  • Warning Line 1502, Column 57: cannot generate system identifier for general entity "appId"
      js.src = "//connect.facebook.net/en_US/all.js#xfbml=1&appId=272873242740031";

    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 1502, Column 57: general entity "appId" not defined and no default entity
      js.src = "//connect.facebook.net/en_US/all.js#xfbml=1&appId=272873242740031";

    This is usually a cascading error caused by 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 1502, Column 62: reference not terminated by REFC delimiter
      js.src = "//connect.facebook.net/en_US/all.js#xfbml=1&appId=272873242740031";

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

  • Error Line 1502, Column 62: reference to entity "appId" for which no system identifier could be generated
      js.src = "//connect.facebook.net/en_US/all.js#xfbml=1&appId=272873242740031";

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

  • Info Line 1502, Column 56: entity was defined here
      js.src = "//connect.facebook.net/en_US/all.js#xfbml=1&appId=272873242740031";
  • Error Line 1621, Column 63: required attribute "type" not specified
    <script src="http://inyarwanda.com/scripts/bootstrap-modal.js"></script>

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

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

  • Error Line 1621, Column 63: document type does not allow element "script" here
    <script src="http://inyarwanda.com/scripts/bootstrap-modal.js"></script>

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

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

  • Error Line 1623, Column 74: document type does not allow element "script" here
    …ipt type="text/javascript" src="scripts/combobox/Selectyze.jquery.js"></script>

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

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

  • Error Line 1624, Column 78: document type does not allow element "script" here
    …type="text/javascript" src="scripts/combobox/Selectyze.jquery.min.js"></script>

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

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

  • Error Line 1626, Column 31: document type does not allow element "script" here
    <script type="text/javascript">

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

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

  • Error Line 1638, Column 8: required attribute "type" not specified
    <script>

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

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

  • Error Line 1638, Column 8: document type does not allow element "script" here
    <script>

    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 1644, Column 31: cannot generate system identifier for general entity "start"
    	var d="category="+category+"&start=0&limit=10";

    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 1644, Column 31: general entity "start" not defined and no default entity
    	var d="category="+category+"&start=0&limit=10";

    This is usually a cascading error caused by 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 1644, Column 36: reference not terminated by REFC delimiter
    	var d="category="+category+"&start=0&limit=10";

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

  • Error Line 1644, Column 36: reference to entity "start" for which no system identifier could be generated
    	var d="category="+category+"&start=0&limit=10";

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

  • Info Line 1644, Column 30: entity was defined here
    	var d="category="+category+"&start=0&limit=10";
  • Warning Line 1644, Column 39: cannot generate system identifier for general entity "limit"
    	var d="category="+category+"&start=0&limit=10";

    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 1644, Column 39: general entity "limit" not defined and no default entity
    	var d="category="+category+"&start=0&limit=10";

    This is usually a cascading error caused by 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 1644, Column 44: reference not terminated by REFC delimiter
    	var d="category="+category+"&start=0&limit=10";

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

  • Error Line 1644, Column 44: reference to entity "limit" for which no system identifier could be generated
    	var d="category="+category+"&start=0&limit=10";

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

  • Info Line 1644, Column 38: entity was defined here
    	var d="category="+category+"&start=0&limit=10";
  • Error Line 1656, Column 8: required attribute "type" not specified
    <script>

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

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

  • Error Line 1656, Column 8: document type does not allow element "script" here
    <script>

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

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

Visitor Analysis

Daily Visitor
  • 4.433 visits

In Page Analysis