caroline-dhavernas.net

Caroline Dhavernas - Caroline Dhavernas Fan is a fan site dedicated to the gorgeously talented actress Caroline Dhavernas. This site is online to keep you up to date with everything Caroline Dhavernas. ...

This data was last updated from 22-12-2014 04:15:37  (update).

Overview Info



  • Domain Name
    caroline-dhavernas.net
  • Favicon
  • Alexa Rank
    #0
  • Google Page Rank
    1
  • Ip Address
    192.111.139.120
  • Page Size
    31.1 KB
  • Images
    0 GIF, 50 JPG, 0 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    2 0 0 0 0 0

Website Meta Analysis



  • Title
    Caroline Dhavernas @ Caroline-Dhavernas.net - Your Ultimate Resource
  • Meta Keyword
    Caroline Dhavernas, Wonderfalls, Jaye Tyler, Hannibal, Off the Map, Mars et Avril
  • Meta Description
    Caroline Dhavernas - Caroline Dhavernas Fan is a fan site dedicated to the gorgeously talented actress Caroline Dhavernas. This site is online to keep you up to date with everything Caroline Dhavernas. Caroline has starred in the tv series

Technical Analysis



  • Webserver
    Apache
  • Ip Address
    192.111.139.120
  • Domain Age
    3 Years, 2 Months, 6 days.
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from caroline-dhavernas.net.

HTML Analysis

  • date: Mon, 22 Dec 2014 16:15:34 GMT
  • server: Apache
  • x-powered-by: PHP/5.4.35
  • x-pingback: http://caroline-dhavernas.net/xmlrpc.php
  • content-type: text/html; charset=UTF-8
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for caroline-dhavernas.net

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 160 Errors
  • 6 Warnings
Ratio Text/Html
  • 0.6747173366834172
Message Error
  • Error Line 4, Column 83: end tag for element "TITLE" which is not open
    …le>Caroline Dhavernas @ Caroline-Dhavernas.net - Your Ultimate Resource</TITLE>

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

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

  • Error Line 5, Column 12: there is no attribute "NAME"
    <META NAME="description" content="Caroline Dhavernas - Caroline Dhavernas Fan i…

    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 5, Column 34: there is no attribute "content"
    <META NAME="description" content="Caroline Dhavernas - Caroline Dhavernas Fan i…

    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 5, Column 288: an attribute value literal can occur in an attribute specification list only after a VI delimiter
    … starred in the tv series "Wonderfalls" and "Off the Map".  Caroline Dhavernas…

    Have you forgotten the "equal" sign marking the separation between the attribute and its declared value? Typical syntax is attribute="value".

  • Error Line 5, Column 288: element "META" undefined
    … starred in the tv series "Wonderfalls" and "Off the Map".  Caroline Dhavernas…

    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 6, Column 114: element "META" undefined
    …line Dhavernas, Wonderfalls, Jaye Tyler, Hannibal, Off the Map, Mars et Avril">

    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 9, Column 73: end tag for "meta" omitted, but OMITTAG NO was specified
    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">

    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 9, Column 1: start tag was here
    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
  • Error Line 11, Column 41: end tag for "meta" omitted, but OMITTAG NO was specified
    <meta name="Language" content="English">

    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 11, Column 1: start tag was here
    <meta name="Language" content="English">
  • Error Line 12, Column 18: there is no attribute "HTTP-EQUIV"
    <META HTTP-EQUIV="imagetoolbar" CONTENT="no">

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

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

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

  • Error Line 12, Column 41: there is no attribute "CONTENT"
    <META HTTP-EQUIV="imagetoolbar" CONTENT="no">

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

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

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

  • Error Line 12, Column 45: element "META" undefined
    <META HTTP-EQUIV="imagetoolbar" CONTENT="no">

    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 13, Column 34: element "META" undefined
    <META NAME="ROBOTS" CONTENT="ALL">

    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 14, Column 73: end tag for "meta" omitted, but OMITTAG NO was specified
    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">

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

  • Info Line 14, Column 1: start tag was here
    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
  • Error Line 18, Column 83: required attribute "type" not specified
    …http://cdn-media.hollywood.com/static/fstoolbar/white-top-toolbar.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 19, Column 7: end tag for "META" omitted, but OMITTAG NO was specified
    </head>

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

  • Info Line 13, Column 1: start tag was here
    <META NAME="ROBOTS" CONTENT="ALL">
  • Error Line 19, Column 7: end tag for "META" omitted, but OMITTAG NO was specified
    </head>

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

  • Info Line 12, Column 1: start tag was here
    <META HTTP-EQUIV="imagetoolbar" CONTENT="no">
  • Error Line 19, Column 7: end tag for "META" omitted, but OMITTAG NO was specified
    </head>

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

  • Info Line 6, Column 1: start tag was here
    <META NAME="keywords" content="Caroline Dhavernas, Wonderfalls, Jaye Tyler, Han…
  • Error Line 19, Column 7: end tag for "META" omitted, but OMITTAG NO was specified
    </head>

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

  • Info Line 5, Column 1: start tag was here
    <META NAME="description" content="Caroline Dhavernas - Caroline Dhavernas Fan i…
  • Error Line 19, Column 7: end tag for "title" omitted, but OMITTAG NO was specified
    </head>

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

  • Info Line 4, Column 1: start tag was here
    <title>Caroline Dhavernas @ Caroline-Dhavernas.net - Your Ultimate Resource</TI…
  • Warning Line 43, Column 55: character "&" is the first character of a delimiter but occurred as data
    …caroline-dhavernas.net/site-web">Site & Web</a>&nbsp;&nbsp;&nbsp; &bull; &nbsp…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 45, Column 47: character "&" is the first character of a delimiter but occurred as data
    <a href="http://caroline-dhavernas.net/">News & Updates</a>

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 53, Column 89: character "&" is the first character of a delimiter but occurred as data
    …a fan site dedicated to the beautiful & talented Canadian actress <b>Caroline …

    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 82, Column 63: document type does not allow element "table" here
    <table border="0" cellpadding="0" cellspacing="0" width="100%">

    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 84, Column 20: document type does not allow element "div" here
    <div class="bottom">Posted by Kayla on December 07, 2014 &bull; <a href="http:/…

    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 85, Column 11: end tag for element "td" which is not open
    </div></td>

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

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

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

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

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

  • Error Line 87, Column 9: end tag for "table" which is not finished
    	</table>

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

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

  • Error Line 89, Column 6: end tag for "table" omitted, but OMITTAG NO was specified
    </div>

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

  • Info Line 71, Column 1: start tag was here
    <table border="0" cellpadding="0" cellspacing="0" width="100%">
  • Error Line 94, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br>

    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 94, Column 1: start tag was here
    <br>
  • Error Line 107, Column 8: document type does not allow element "center" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <center><a href="http://caroline-dhavernas.net/gallery/thumbnails.php?album=144…

    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 129, Column 63: document type does not allow element "table" here
    <table border="0" cellpadding="0" cellspacing="0" width="100%">

    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 131, Column 20: document type does not allow element "div" here
    <div class="bottom">Posted by Kayla on May 16, 2014 &bull; <a href="http://caro…

    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 132, Column 11: end tag for element "td" which is not open
    </div></td>

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

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

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

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

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

  • Error Line 134, Column 9: end tag for "table" which is not finished
    	</table>

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

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

  • Error Line 136, Column 6: end tag for "table" omitted, but OMITTAG NO was specified
    </div>

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

  • Info Line 103, Column 1: start tag was here
    <table border="0" cellpadding="0" cellspacing="0" width="100%">
  • Error Line 141, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br>

    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 141, Column 1: start tag was here
    <br>
  • Error Line 161, Column 63: document type does not allow element "table" here
    <table border="0" cellpadding="0" cellspacing="0" width="100%">

    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 163, Column 20: document type does not allow element "div" here
    <div class="bottom">Posted by Kayla on May 09, 2014 &bull; <a href="http://caro…

    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 164, Column 11: end tag for element "td" which is not open
    </div></td>

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

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

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

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

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

  • Error Line 166, Column 9: end tag for "table" which is not finished
    	</table>

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

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

  • Error Line 168, Column 6: end tag for "table" omitted, but OMITTAG NO was specified
    </div>

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

  • Info Line 150, Column 1: start tag was here
    <table border="0" cellpadding="0" cellspacing="0" width="100%">
  • Error Line 173, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br>

    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 173, Column 1: start tag was here
    <br>
  • Error Line 186, Column 8: document type does not allow element "center" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <center><a href="http://caroline-dhavernas.net/gallery/thumbnails.php?album=147…

    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 195, Column 63: document type does not allow element "table" here
    <table border="0" cellpadding="0" cellspacing="0" width="100%">

    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 197, Column 20: document type does not allow element "div" here
    <div class="bottom">Posted by Kayla on February 13, 2014 &bull; <a href="http:/…

    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 198, Column 11: end tag for element "td" which is not open
    </div></td>

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

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

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

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

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

  • Error Line 200, Column 9: end tag for "table" which is not finished
    	</table>

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

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

  • Error Line 202, Column 6: end tag for "table" omitted, but OMITTAG NO was specified
    </div>

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

  • Info Line 182, Column 1: start tag was here
    <table border="0" cellpadding="0" cellspacing="0" width="100%">
  • Error Line 207, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br>

    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 207, Column 1: start tag was here
    <br>
  • Error Line 220, Column 8: document type does not allow element "center" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <center><iframe width="560" height="315" src="//www.youtube.com/embed/Y1LzcS7Db…

    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 220, Column 115: "allowfullscreen" is not a member of a group specified for any attribute
    …e.com/embed/Y1LzcS7Db68" frameborder="0" allowfullscreen></iframe></center></p>
  • Error Line 227, Column 63: document type does not allow element "table" here
    <table border="0" cellpadding="0" cellspacing="0" width="100%">

    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 229, Column 20: document type does not allow element "div" here
    <div class="bottom">Posted by Kayla on January 21, 2014 &bull; <a href="http://…

    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 230, Column 11: end tag for element "td" which is not open
    </div></td>

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

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

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

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

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

  • Error Line 232, Column 9: end tag for "table" which is not finished
    	</table>

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

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

  • Error Line 234, Column 6: end tag for "table" omitted, but OMITTAG NO was specified
    </div>

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

  • Info Line 216, Column 1: start tag was here
    <table border="0" cellpadding="0" cellspacing="0" width="100%">
  • Error Line 239, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br>

    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 239, Column 1: start tag was here
    <br>
  • Error Line 253, Column 8: document type does not allow element "center" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <center><img src="http://caroline-dhavernas.net/gallery/albums/Television%20Sho…

    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 253, Column 184: end tag for "center" omitted, but OMITTAG NO was specified
    …ls/Promos/thumb_001.jpg" alt="" /> </a> <a href="http://caroline-dhavernas.net…

    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 253, Column 1: start tag was here
    <center><img src="http://caroline-dhavernas.net/gallery/albums/Television%20Sho…
  • Error Line 253, Column 1252: end tag for element "center" which is not open
    …0Savoureux/thumb_Hannibal_1x13__Savoureux_147.JPG" alt="" /></a></center><br />

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

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

  • Error Line 265, Column 63: document type does not allow element "table" here
    <table border="0" cellpadding="0" cellspacing="0" width="100%">

    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 267, Column 20: document type does not allow element "div" here
    <div class="bottom">Posted by Kayla on January 07, 2014 &bull; <a href="http://…

    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 268, Column 11: end tag for element "td" which is not open
    </div></td>

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

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

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

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

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

  • Error Line 270, Column 9: end tag for "table" which is not finished
    	</table>

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

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

  • Error Line 272, Column 6: end tag for "table" omitted, but OMITTAG NO was specified
    </div>

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

  • Info Line 248, Column 1: start tag was here
    <table border="0" cellpadding="0" cellspacing="0" width="100%">
  • Error Line 277, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br>

    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 277, Column 1: start tag was here
    <br>
  • Error Line 285, Column 5: end tag for "td" omitted, but OMITTAG NO was specified
    </tr></td></table><br></br>

    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 280, Column 5: start tag was here
    <tr><td class="bottom"> 
  • Error Line 285, Column 10: end tag for element "td" which is not open
    </tr></td></table><br></br>

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

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

  • Error Line 312, Column 30: required attribute "type" not specified
    <script src="/ad/squaread.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 320, Column 4: end tag for element "p" which is not open
    </p></div>

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

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

  • Error Line 321, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br>

    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 321, Column 1: start tag was here
    <br>
  • Error Line 325, Column 8: document type does not allow element "center" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <center>

    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 351, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br>

    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 351, Column 1: start tag was here
    <br>
  • Error Line 357, Column 8: document type does not allow element "center" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <center><a href=""><img src="http://caroline-dhavernas.net/wp-content/themes/La…

    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 357, Column 125: required attribute "alt" not specified
    ….net/wp-content/themes/Layout01/images/hannibal2.jpg" title="Hannibal"></a><br>

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

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

  • Error Line 357, Column 129: end tag for "img" omitted, but OMITTAG NO was specified
    ….net/wp-content/themes/Layout01/images/hannibal2.jpg" title="Hannibal"></a><br>

    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 357, Column 20: start tag was here
    <center><a href=""><img src="http://caroline-dhavernas.net/wp-content/themes/La…
  • Error Line 357, Column 134: end tag for "br" omitted, but OMITTAG NO was specified
    ….net/wp-content/themes/Layout01/images/hannibal2.jpg" title="Hannibal"></a><br>

    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 357, Column 130: start tag was here
    ….net/wp-content/themes/Layout01/images/hannibal2.jpg" title="Hannibal"></a><br>
  • Error Line 361, Column 4: end tag for "center" omitted, but OMITTAG NO was specified
    </p></div>

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

  • Info Line 357, Column 1: start tag was here
    <center><a href=""><img src="http://caroline-dhavernas.net/wp-content/themes/La…
  • Error Line 364, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br>

    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 364, Column 1: start tag was here
    <br>
  • Warning Line 368, Column 44: character "&" is the first character of a delimiter but occurred as data
            <div class="sidebar-title">Current & Upcoming Projects</div><p>

    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 370, Column 131: required attribute "alt" not specified
    …ntent/themes/Layout01/images/mars.jpg" align="right" title="Mars et Avril"></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 370, Column 135: end tag for "img" omitted, but OMITTAG NO was specified
    …ntent/themes/Layout01/images/mars.jpg" align="right" title="Mars et Avril"></a>

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

  • Info Line 370, Column 12: start tag was here
    <a href=""><img src="http://caroline-dhavernas.net/wp-content/themes/Layout01/i…
  • Error Line 371, Column 25: end tag for "br" omitted, but OMITTAG NO was specified
    <b>Mars et Avril</b><br>

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

  • Info Line 371, Column 21: start tag was here
    <b>Mars et Avril</b><br>
  • Error Line 372, Column 29: end tag for "br" omitted, but OMITTAG NO was specified
    Caroline as <i>Avril</i><br>

    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 372, Column 25: start tag was here
    Caroline as <i>Avril</i><br>
  • Error Line 373, Column 14: end tag for "br" omitted, but OMITTAG NO was specified
    Completed<br>

    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 373, Column 10: start tag was here
    Completed<br>
  • Error Line 374, Column 36: end tag for "br" omitted, but OMITTAG NO was specified
    Currently in Theaters in Canada<br>

    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 374, Column 32: start tag was here
    Currently in Theaters in Canada<br>
  • Error Line 376, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br><br>

    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 376, Column 1: start tag was here
    <br><br>
  • Error Line 376, Column 9: end tag for "br" omitted, but OMITTAG NO was specified
    <br><br>

    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 376, Column 5: start tag was here
    <br><br>
  • Error Line 379, Column 150: required attribute "alt" not specified
    …nt/themes/Layout01/images/goodbye.jpg" align="right" title="Goodbye World"></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 379, Column 154: end tag for "img" omitted, but OMITTAG NO was specified
    …nt/themes/Layout01/images/goodbye.jpg" align="right" title="Goodbye World"></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 379, Column 28: start tag was here
    <a href="" target="_blank"><img src="http://caroline-dhavernas.net/wp-content/t…
  • Error Line 380, Column 25: end tag for "br" omitted, but OMITTAG NO was specified
    <b>Goodbye World</b><br>

    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 380, Column 21: start tag was here
    <b>Goodbye World</b><br>
  • Error Line 381, Column 29: end tag for "br" omitted, but OMITTAG NO was specified
    Caroline as <i>Becky</i><br>

    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 381, Column 25: start tag was here
    Caroline as <i>Becky</i><br>
  • Error Line 382, Column 20: end tag for "br" omitted, but OMITTAG NO was specified
    Post-Production<br>

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

  • Info Line 382, Column 16: start tag was here
    Post-Production<br>
  • Error Line 383, Column 27: end tag for "br" omitted, but OMITTAG NO was specified
    Release Date: TBA 2013<br>

    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 383, Column 23: start tag was here
    Release Date: TBA 2013<br>
  • Error Line 385, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br><br>

    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 385, Column 1: start tag was here
    <br><br>
  • Error Line 385, Column 9: end tag for "br" omitted, but OMITTAG NO was specified
    <br><br>

    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 385, Column 5: start tag was here
    <br><br>
  • Error Line 391, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br>

    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 391, Column 1: start tag was here
    <br>
  • Error Line 398, Column 8: document type does not allow element "center" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <center>

    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 400, Column 175: required attribute "alt" not specified
    …hemes/Layout01/images/family/aly.jpg" border="0" title="Aly Michalka Fan"></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 400, Column 179: end tag for "img" omitted, but OMITTAG NO was specified
    …hemes/Layout01/images/family/aly.jpg" border="0" title="Aly Michalka Fan"></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 400, Column 54: start tag was here
    …/alyson-michalka.org" target="_blank"><img src="http://iheartjennifer.org/wp-c…
  • Error Line 401, Column 171: required attribute "alt" not specified
    …mes/Layout01/images/family/emma.jpg" border="0" title="Emma Stone Source"></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 401, Column 175: end tag for "img" omitted, but OMITTAG NO was specified
    …mes/Layout01/images/family/emma.jpg" border="0" title="Emma Stone Source"></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 401, Column 48: start tag was here
    …http://emma-stone.us" target="_blank"><img src="http://iheartjennifer.org/wp-c…
  • Error Line 402, Column 191: required attribute "alt" not specified
    …ages/family/christina.jpg" border="0" title="Captivating Christina Ricci"></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 402, Column 195: end tag for "img" omitted, but OMITTAG NO was specified
    …ages/family/christina.jpg" border="0" title="Captivating Christina Ricci"></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 402, Column 53: start tag was here
    …//christina-ricci.us" target="_blank"><img src="http://iheartjennifer.org/wp-c…
  • Error Line 403, Column 176: required attribute "alt" not specified
    …yout01/images/family/ashley.jpg" border="0" title="Ashley Benson Central"></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 403, Column 180: end tag for "img" omitted, but OMITTAG NO was specified
    …yout01/images/family/ashley.jpg" border="0" title="Ashley Benson Central"></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 403, Column 47: start tag was here
    …"http://ashley-b.org" target="_blank"><img src="http://iheartjennifer.org/wp-c…
  • Error Line 404, Column 174: required attribute "alt" not specified
    …es/Layout01/images/family/julie.jpg" border="0" title="Julie Benz Online"></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 404, Column 178: end tag for "img" omitted, but OMITTAG NO was specified
    …es/Layout01/images/family/julie.jpg" border="0" title="Julie Benz Online"></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 404, Column 50: start tag was here
    …tp://julie-benz.info" target="_blank"><img src="http://iheartjennifer.org/wp-c…
  • Error Line 405, Column 177: required attribute "alt" not specified
    …s/Layout01/images/family/alexis.jpg" border="0" title="Alexis Dziena Web"></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 405, Column 181: end tag for "img" omitted, but OMITTAG NO was specified
    …s/Layout01/images/family/alexis.jpg" border="0" title="Alexis Dziena Web"></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 405, Column 52: start tag was here
    …://alexis-dziena.net" target="_blank"><img src="http://iheartjennifer.org/wp-c…
  • Error Line 406, Column 184: required attribute "alt" not specified
    …01/images/family/troian.jpg" border="0" title="Troian Bellisario Central"></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 406, Column 188: end tag for "img" omitted, but OMITTAG NO was specified
    …01/images/family/troian.jpg" border="0" title="Troian Bellisario Central"></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 406, Column 51: start tag was here
    …p://t-bellisario.net" target="_blank"><img src="http://iheartjennifer.org/wp-c…
  • Error Line 407, Column 177: required attribute "alt" not specified
    …mes/Layout01/images/family/anne.jpg" border="0" title="Anne Hathaway Fan"></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 407, Column 181: end tag for "img" omitted, but OMITTAG NO was specified
    …mes/Layout01/images/family/anne.jpg" border="0" title="Anne Hathaway Fan"></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 407, Column 54: start tag was here
    …/annehathawayfan.com" target="_blank"><img src="http://iheartjennifer.org/wp-c…
  • Error Line 408, Column 174: required attribute "alt" not specified
    …es/Layout01/images/family/isla.jpg" border="0" title="Isla Fisher Online"></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 408, Column 178: end tag for "img" omitted, but OMITTAG NO was specified
    …es/Layout01/images/family/isla.jpg" border="0" title="Isla Fisher Online"></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 408, Column 50: start tag was here
    …tp://isla-fisher.org" target="_blank"><img src="http://iheartjennifer.org/wp-c…
  • Error Line 415, Column 4: document type does not allow element "h1" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <h1></h1>

    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 416, Column 62: document type does not allow element "table" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <table border="0" width="350" cellpadding="0" cellspacing="3">

    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 419, Column 89: end tag for "br" omitted, but OMITTAG NO was specified
    …sp; <a href="http://krysten-ritter.org" target="_blank">Krysten Ritter</a> <br>

    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 419, Column 85: start tag was here
    …sp; <a href="http://krysten-ritter.org" target="_blank">Krysten Ritter</a> <br>
  • Error Line 420, Column 78: end tag for "br" omitted, but OMITTAG NO was specified
    &bull;&nbsp; <a href="http://amyacker.org" target="_blank">Amy Acker</a> <br>

    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 420, Column 74: start tag was here
    &bull;&nbsp; <a href="http://amyacker.org" target="_blank">Amy Acker</a> <br>
  • Error Line 421, Column 87: end tag for "br" omitted, but OMITTAG NO was specified
    …nbsp; <a href="http://brittany-snow.org" target="_blank">Brittany Snow</a> <br>

    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 421, Column 83: start tag was here
    …nbsp; <a href="http://brittany-snow.org" target="_blank">Brittany Snow</a> <br>
  • Error Line 422, Column 93: end tag for "br" omitted, but OMITTAG NO was specified
    …<a href="http://deborah-ann-woll.net" target="_blank">Deborah Ann Woll</a> <br>

    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 422, Column 89: start tag was here
    …<a href="http://deborah-ann-woll.net" target="_blank">Deborah Ann Woll</a> <br>
  • Error Line 428, Column 91: end tag for "br" omitted, but OMITTAG NO was specified
    …; <a href="http://katherine-heigl.net" target="_blank">Katherine Heigl</a> <br>

    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 428, Column 87: start tag was here
    …; <a href="http://katherine-heigl.net" target="_blank">Katherine Heigl</a> <br>
  • Error Line 429, Column 95: end tag for "br" omitted, but OMITTAG NO was specified
    … href="http://hollymariecombsfan.com" target="_blank">Holly Marie Combs</a><br>

    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 429, Column 91: start tag was here
    … href="http://hollymariecombsfan.com" target="_blank">Holly Marie Combs</a><br>
  • Error Line 430, Column 102: end tag for "br" omitted, but OMITTAG NO was specified
    …http://jessicaparkerkennedy.us" target="_blank">Jessica Parker Kennedy</a> <br>

    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 430, Column 98: start tag was here
    …http://jessicaparkerkennedy.us" target="_blank">Jessica Parker Kennedy</a> <br>
  • Error Line 432, Column 90: end tag for "br" omitted, but OMITTAG NO was specified
    …p; <a href="http://vanessa-lengies.net" target="_blank">Vanessa Lengies</a><br>

    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 432, Column 86: start tag was here
    …p; <a href="http://vanessa-lengies.net" target="_blank">Vanessa Lengies</a><br>
  • Error Line 437, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br>

    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 437, Column 1: start tag was here
    <br>
  • Warning Line 442, Column 42: character "&" is the first character of a delimiter but occurred as data
            <div class="sidebar-title">Elite & Top Affiliates</div><p>

    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 444, Column 8: document type does not allow element "center" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <center>

    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 445, Column 148: required attribute "alt" not specified
    …es/Layout01/images/elite/rachelle.jpg"></a> <a href="http://hugh-dancy.net/" t…

    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 445, Column 152: end tag for "img" omitted, but OMITTAG NO was specified
    …ayout01/images/elite/rachelle.jpg"></a> <a href="http://hugh-dancy.net/" targe…

    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 445, Column 55: start tag was here
    …rachelle-lefevre.net" target="_blank"><img src="http://caroline-dhavernas.net/…
  • Error Line 445, Column 292: required attribute "alt" not specified
    …themes/Layout01/images/elite/hugh.jpg"></a> <a href="http://mads-mikkelsen.net…

    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 445, Column 296: end tag for "img" omitted, but OMITTAG NO was specified
    …es/Layout01/images/elite/hugh.jpg"></a> <a href="http://mads-mikkelsen.net/" t…

    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 445, Column 203: start tag was here
    …tp://hugh-dancy.net/" target="_blank"><img src="http://caroline-dhavernas.net/…
  • Error Line 445, Column 440: required attribute "alt" not specified
    …themes/Layout01/images/elite/mads.jpg"></a> <a href="#/" target="_blank"><img …

    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 445, Column 444: end tag for "img" omitted, but OMITTAG NO was specified
    …es/Layout01/images/elite/mads.jpg"></a> <a href="#/" target="_blank"><img src=…

    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 445, Column 351: start tag was here
    …/mads-mikkelsen.net/" target="_blank"><img src="http://caroline-dhavernas.net/…
  • Error Line 445, Column 565: required attribute "alt" not specified
    …hemes/Layout01/images/elite/elite.jpg"></a> <a href="#/" target="_blank"><img …

    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 445, Column 569: end tag for "img" omitted, but OMITTAG NO was specified
    …s/Layout01/images/elite/elite.jpg"></a> <a href="#/" target="_blank"><img src=…

    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 445, Column 475: start tag was here
    …pg"></a> <a href="#/" target="_blank"><img src="http://caroline-dhavernas.net/…
  • Error Line 445, Column 690: required attribute "alt" not specified
    …/caroline-dhavernas.net/wp-content/themes/Layout01/images/elite/elite.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 445, Column 694: end tag for "img" omitted, but OMITTAG NO was specified
    …/caroline-dhavernas.net/wp-content/themes/Layout01/images/elite/elite.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 445, Column 600: start tag was here
    …pg"></a> <a href="#/" target="_blank"><img src="http://caroline-dhavernas.net/…
  • Error Line 447, Column 4: document type does not allow element "h1" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <h1></h1>

    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 448, Column 62: document type does not allow element "table" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <table border="0" width="350" cellpadding="0" cellspacing="3">

    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 453, Column 29: document type does not allow element "td" here
    <td valign="top" width="175">

    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 456, Column 10: end tag for "td" omitted, but OMITTAG NO was specified
    </td></tr></table>

    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 450, Column 1: start tag was here
    <td valign="top" width="175">
  • Error Line 463, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br>

    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 463, Column 1: start tag was here
    <br>
  • Error Line 471, Column 17: end tag for "br" omitted, but OMITTAG NO was specified
    Owner: Kayla<br>

    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 471, Column 13: start tag was here
    Owner: Kayla<br>
  • Error Line 472, Column 75: end tag for "br" omitted, but OMITTAG NO was specified
    Host: <a href="http://fan-sites.org" target="_blank">Fan-Sites.Org</a><br>

    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 472, Column 71: start tag was here
    Host: <a href="http://fan-sites.org" target="_blank">Fan-Sites.Org</a><br>
  • Error Line 473, Column 29: end tag for "br" omitted, but OMITTAG NO was specified
    Opened: October 22, 2012<br>

    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 473, Column 25: start tag was here
    Opened: October 22, 2012<br>
  • Error Line 474, Column 99: required attribute "type" not specified
    …="JavaScript" src="/cgi-bin/online/online.cgi?output=javascript"></script> Fans

    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 477, Column 3: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <p>

    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 484, Column 3: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <p>

    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 486, Column 8: document type does not allow element "center" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <center>

    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 495, Column 6: end tag for "p" omitted, but OMITTAG NO was specified
    </div>

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

  • Info Line 477, Column 1: start tag was here
    <p>
  • Error Line 495, Column 6: end tag for "p" omitted, but OMITTAG NO was specified
    </div>

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

  • Info Line 469, Column 58: start tag was here
            <div class="sidebar-title">Site Information</div><p>
  • Error Line 497, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br>

    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 497, Column 1: start tag was here
    <br>
  • Error Line 507, Column 6: end tag for element "div" which is not open
    </div>

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

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

  • Error Line 518, Column 6: document type does not allow element "html" here
    <html>

    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 518, Column 1: Missing xmlns attribute for element html. The value should be: http://www.w3.org/1999/xhtml
    <html>

    Many Document Types based on XML need a mandatory xmlns attribute on the root element. For example, the root element for XHTML might look like:
    <html xmlns="http://www.w3.org/1999/xhtml">

  • Error Line 518, Column 7: "html" not finished but document ended
    <html>
  • Error Line 518, Column 7: end tag for "html" omitted, but OMITTAG NO was specified
    <html>

    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 518, Column 1: start tag was here
    <html>
  • Error Line 518, Column 7: end tag for "html" omitted, but OMITTAG NO was specified
    <html>

    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 2, Column 1: start tag was here
    <html xmlns="http://www.w3.org/1999/xhtml">

Visitor Analysis

Daily Visitor
  • 0 visits

In Page Analysis