fagalicious.com

Daily updated Gay Porn Blog featuring free porn pics, videos and previews. ...

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

Overview Info

  • Domain Name
    fagalicious.com
  • Favicon
  • Alexa Rank
    #180241
  • Google Page Rank
    PR 3
  • Ip Address
    198.57.198.220
  • Page Size
    106.3 KB
  • Images
    2 GIF, 64 JPG, 3 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    7 10 0 0 0 0

Website Meta Analysis

  • Title
    Fagalicious - Gay Porn Blog
  • Meta Keyword
    gay, blog, fagalicious, gday, guycandy, feelslikegay, feels like gay, sex, NSFW, men, sites, free, gay porn, porn sites, pornsites, porno, paysite, free videos, videos, muscle, hunk, hunks, jock, jocks, links, homosexual, homo, fratmen, sean cody, seancody, randyblue, randy blue, corbin fisher, corbinfisher, nextdoorbuddies, next door buddies, chaosmen
  • Meta Description
    Daily updated Gay Porn Blog featuring free porn pics, videos and previews.

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.198.220
  • Domain Age
    4 Years, 5 Months, 2 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Tue, 09 Jul 2013 08:54:29 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
  • vary: Accept-Encoding,Cookie
  • last-modified: Tue, 09 Jul 2013 08:40:40 GMT
  • etag: "58037b-51fa-4e1101daec351"
  • accept-ranges: bytes
  • content-length: 20986
  • x-powered-by: W3 Total Cache/0.9.2.10
  • content-type: text/html; charset=UTF-8
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Domain name: fagalicious.com

Registrant Contact:
HostGator
Brent Oxley ()

Fax:
11251 nw freeway suite 400
Houston, 77065
US

Administrative Contact:
HostGator
Adam Farrar ( email )
+1.7135745287
Fax: +1.11
11251 Northwest Fwy suite 400
Houston, TX 77092
US

Technical Contact:
HostGator
Adam Farrar ( email )
+1.7135745287
Fax: +1.11
11251 Northwest Fwy suite 400
Houston, TX 77092
US

Status: Locked

Name Servers:
ns1399.hostgator.com
ns1400.hostgator.com

Creation date: 29 Jan 2009 15:42:12
Expiration date: 29 Jan 2013 15:42:12

DNS Analysis


DNS servers
ns1399.hostgator.com [174.132.166.34]
ns1400.hostgator.com [174.132.166.35]

DNS Records

Answer records
fagalicious.com MX
preference: 0
exchange: fagalicious.com
14400s
fagalicious.com SOA
server: ns1399.hostgator.com
email: dnsadmin@gator700.hostgator.com
serial: 2012113003
refresh: 86400
retry: 7200
expire: 3600000
minimum ttl: 86400
86400s
fagalicious.com NS  ns1399.hostgator.com 86400s
fagalicious.com NS  ns1400.hostgator.com 86400s
fagalicious.com A 174.132.166.58 14400s

Authority records

Additional records
fagalicious.com A 174.132.166.58 14400s
ns1399.hostgator.com A 174.132.166.34 14400s
ns1400.hostgator.com A 174.132.166.35 14400s

IP 198.57.198.220 Analysis

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

Site Same Ip

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 282 Errors
  • 23 Warnings
Ratio Text/Html
  • 0.7620582913095796
Message Error
  • Error Line 29, Column 12: an attribute value must be a literal unless it contains only name characters
    <meta name=RATING” content="Mature, Adult" />

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

  • Error Line 32, Column 100: end tag for "link" omitted, but OMITTAG NO was specified
    …onts.googleapis.com/css?family=Chivo:400,900' rel='stylesheet' type='text/css'>

    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 32, Column 1: start tag was here
    <link href='http://fonts.googleapis.com/css?family=Chivo:400,900' rel='styleshe…
  • Error Line 52, Column 202: end tag for "link" omitted, but OMITTAG NO was specified
    …/video-js.css" type="text/css" media="screen" title="Video JS" charset="utf-8">

    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 52, Column 3: start tag was here
      <link rel="stylesheet" href="http://fagalicious.com/wp-content/plugins/videoj…
  • Error Line 65, Column 294: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …4Ljg0LjEwNi4xMDYuMC4wLjAuMC4w" target=_blank><img src="http://fagalicious.com/…
  • Error Line 95, Column 10: ID "blurb" already defined
    <div id="blurb">

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 68, Column 11: ID "blurb" first defined here
    	<div id="blurb">
  • Error Line 120, Column 20: there is no attribute "class"
          <video class="video-js" width="590" height="332" poster="http://beefandba…

    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 120, Column 37: there is no attribute "width"
          <video class="video-js" width="590" height="332" poster="http://beefandba…

    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 120, Column 50: there is no attribute "height"
    …o class="video-js" width="590" height="332" poster="http://beefandbananas.com/…

    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 120, Column 63: there is no attribute "poster"
    …o-js" width="590" height="332" poster="http://beefandbananas.com/wp-content/up…

    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 120, Column 142: "controls" is not a member of a group specified for any attribute
    …ananas.com/wp-content/uploads/undercover-part2-v.jpg" controls preload="none" >
  • Error Line 120, Column 150: there is no attribute "preload"
    …ananas.com/wp-content/uploads/undercover-part2-v.jpg" controls preload="none" >

    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 120, Column 157: element "video" undefined
    …ananas.com/wp-content/uploads/undercover-part2-v.jpg" controls preload="none" >

    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 121, Column 19: there is no attribute "src"
          <source src="http://manspotting.net/clips/UndercoverPart2_scene1_trailer_…

    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 121, Column 97: there is no attribute "type"
    …Part2_scene1_trailer_mobile.mp4" type='video/mp4; codecs="avc1.42E01E, mp4a.40…

    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 121, Column 143: element "source" undefined
    …scene1_trailer_mobile.mp4" type='video/mp4; codecs="avc1.42E01E, mp4a.40.2"' />

    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 139, Column 11: 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 139, Column 7: start tag was here
          <br>
  • Error Line 141, Column 8: 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 135, Column 5: start tag was here
        <p class="vjs-no-video"><strong>Download Video:</strong>
  • Error Line 144, Column 181: end tag for element "A" which is not open
    …target="_blank">Undercover, Part 21</A>&#8221; in full length at <a href="http…

    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 144, Column 313: document type does not allow element "a" here; missing one of "object", "span", "bdo", "applet", "iframe", "tt", "i", "b", "u", "s", "strike", "big", "small", "font", "em", "strong", "dfn", "code", "q", "samp", "kbd", "var", "cite", "abbr", "acronym", "sub", "sup", "label", "ins", "del" start-tag
    …LjEuMS4wLjAuMC4wLjA" title="Men.com $1 Trial" target="_blank">Men.com</a><br />

    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 145, Column 139: document type does not allow element "a" here; missing one of "object", "span", "bdo", "applet", "iframe", "tt", "i", "b", "u", "s", "strike", "big", "small", "font", "em", "strong", "dfn", "code", "q", "samp", "kbd", "var", "cite", "abbr", "acronym", "sub", "sup", "label", "ins", "del" start-tag
    …QuMzEuMC4wLjAuMC4w" title="Str8ToGay.com" target="_blank">Str8ToGay.com</a></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 145, Column 160: end tag for "a" omitted, but OMITTAG NO was specified
    …QuMzEuMC4wLjAuMC4w" title="Str8ToGay.com" target="_blank">Str8ToGay.com</a></p>

    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 144, Column 22: start tag was here
    <p>- Download &#8220;<a href="http://enter.men.com/track/MTMzMS4xLjEuMS4wLjAuMC…
  • Error Line 147, 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 147, Column 1: start tag was here
    <br>
  • Error Line 149, Column 407: end tag for "br" omitted, but OMITTAG NO was specified
    …/category/porn/" title="View all posts in Porn" rel="category tag">Porn</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 149, Column 403: start tag was here
    …/category/porn/" title="View all posts in Porn" rel="category tag">Porn</a><br>
  • Error Line 170, Column 169: "controls" is not a member of a group specified for any attribute
    …c12955/ccefa33d0b/12955_02/01/12955_02_120sec_00.jpg" controls preload="none" >
  • Error Line 170, Column 184: element "video" undefined
    …c12955/ccefa33d0b/12955_02/01/12955_02_120sec_00.jpg" controls preload="none" >

    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 171, Column 176: element "source" undefined
    …01/12955_02_120sec_00.mp4" type='video/mp4; codecs="avc1.42E01E, mp4a.40.2"' />

    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 189, Column 11: 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 189, Column 7: start tag was here
          <br>
  • Error Line 191, Column 8: 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 185, Column 5: start tag was here
        <p class="vjs-no-video"><strong>Download Video:</strong>
  • Error Line 198, Column 169: "controls" is not a member of a group specified for any attribute
    …c11547/b601c7775c/11547_01/01/11547_01_120sec_00.jpg" controls preload="none" >
  • Error Line 198, Column 184: element "video" undefined
    …c11547/b601c7775c/11547_01/01/11547_01_120sec_00.jpg" controls preload="none" >

    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 199, Column 176: element "source" undefined
    …01/11547_01_120sec_00.mp4" type='video/mp4; codecs="avc1.42E01E, mp4a.40.2"' />

    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 217, Column 11: 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 217, Column 7: start tag was here
          <br>
  • Error Line 219, Column 8: 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 213, Column 5: start tag was here
        <p class="vjs-no-video"><strong>Download Video:</strong>
  • Error Line 226, Column 169: "controls" is not a member of a group specified for any attribute
    …c11940/e7abebc17c/11940_02/01/11940_02_120sec_00.jpg" controls preload="none" >
  • Error Line 226, Column 184: element "video" undefined
    …c11940/e7abebc17c/11940_02/01/11940_02_120sec_00.jpg" controls preload="none" >

    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 227, Column 176: element "source" undefined
    …01/11940_02_120sec_00.mp4" type='video/mp4; codecs="avc1.42E01E, mp4a.40.2"' />

    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 245, Column 11: 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 245, Column 7: start tag was here
          <br>
  • Error Line 247, Column 8: 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 241, Column 5: start tag was here
        <p class="vjs-no-video"><strong>Download Video:</strong>
  • Error Line 254, Column 169: "controls" is not a member of a group specified for any attribute
    …c11204/234c744dbb/11204_01/01/11204_01_120sec_00.jpg" controls preload="none" >
  • Error Line 254, Column 184: element "video" undefined
    …c11204/234c744dbb/11204_01/01/11204_01_120sec_00.jpg" controls preload="none" >

    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 255, Column 176: element "source" undefined
    …01/11204_01_120sec_00.mp4" type='video/mp4; codecs="avc1.42E01E, mp4a.40.2"' />

    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 273, Column 11: 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 273, Column 7: start tag was here
          <br>
  • Error Line 275, Column 8: 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 269, Column 5: start tag was here
        <p class="vjs-no-video"><strong>Download Video:</strong>
  • Error Line 282, Column 162: "controls" is not a member of a group specified for any attribute
    …/99/9937/2e0c6a5e47/9937_06/01/9937_06_120sec_00.jpg" controls preload="none" >
  • Error Line 282, Column 177: element "video" undefined
    …/99/9937/2e0c6a5e47/9937_06/01/9937_06_120sec_00.jpg" controls preload="none" >

    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 283, Column 169: element "source" undefined
    …/01/9937_06_120sec_00.mp4" type='video/mp4; codecs="avc1.42E01E, mp4a.40.2"' />

    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 301, Column 11: 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 301, Column 7: start tag was here
          <br>
  • Error Line 303, Column 8: 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 297, Column 5: start tag was here
        <p class="vjs-no-video"><strong>Download Video:</strong>
  • Error Line 310, Column 162: "controls" is not a member of a group specified for any attribute
    …/42/4223/4caa6b9d99/4223_02/01/4223_02_120sec_00.jpg" controls preload="none" >
  • Error Line 310, Column 177: element "video" undefined
    …/42/4223/4caa6b9d99/4223_02/01/4223_02_120sec_00.jpg" controls preload="none" >

    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 311, Column 169: element "source" undefined
    …/01/4223_02_120sec_00.mp4" type='video/mp4; codecs="avc1.42E01E, mp4a.40.2"' />

    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 329, Column 11: 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 329, Column 7: start tag was here
          <br>
  • Error Line 331, Column 8: 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 325, Column 5: start tag was here
        <p class="vjs-no-video"><strong>Download Video:</strong>
  • Error Line 335, 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 335, Column 1: start tag was here
    <br>
  • Error Line 337, Column 333: end tag for "br" omitted, but OMITTAG NO was specified
    …/category/porn/" title="View all posts in Porn" rel="category tag">Porn</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 337, Column 329: start tag was here
    …/category/porn/" title="View all posts in Porn" rel="category tag">Porn</a><br>
  • Error Line 349, Column 122: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …A=917967-0000&#038;PA=1315109" target=_blank><img src="http://beefandbananas.c…
  • Error Line 350, Column 95: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …cks.cgi?CA=917967-0000&#038;PA=1315109" target=_blank>Sean Cody</a> writes:</p>
  • Error Line 351, Column 131: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …gi?CA=917967-0000&#038;PA=1315109" target=_blank>redheads with muscles</a>!</p>
  • Error Line 355, Column 96: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …A=917967-0000&#038;PA=1315109" target=_blank>I’m going to shoot a lot today!</…
  • Error Line 356, Column 131: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …A=917967-0000&#038;PA=1315109" target=_blank>he shot not one but two huge load…
  • Error Line 357, Column 116: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …i-bin/clicks.cgi?CA=917967-0000&#038;PA=1315109" target=_blank>SeanCody.com</p>
  • Error Line 357, Column 138: end tag for "a" omitted, but OMITTAG NO was specified
    …i-bin/clicks.cgi?CA=917967-0000&#038;PA=1315109" target=_blank>SeanCody.com</p>

    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 25: start tag was here
    <p>- See more of Lee at <a href="http://refer.ccbill.com/cgi-bin/clicks.cgi?CA=…
  • Error Line 358, Column 112: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …A=917967-0000&#038;PA=1315109" target=_blank><img src="http://beefandbananas.c…
  • Error Line 359, 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 359, Column 1: start tag was here
    <br>
  • Error Line 361, Column 300: end tag for "br" omitted, but OMITTAG NO was specified
    …/category/porn/" title="View all posts in Porn" rel="category tag">Porn</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 361, Column 296: start tag was here
    …/category/porn/" title="View all posts in Porn" rel="category tag">Porn</a><br>
  • Error Line 380, Column 132: "controls" is not a member of a group specified for any attribute
    …//manspotting.net/blog/wp-content/uploads/abel-v.jpg" controls preload="none" >
  • Error Line 380, Column 147: element "video" undefined
    …//manspotting.net/blog/wp-content/uploads/abel-v.jpg" controls preload="none" >

    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 381, Column 125: element "source" undefined
    …bel4_teaser.universal.mp4" type='video/mp4; codecs="avc1.42E01E, mp4a.40.2"' />

    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 399, Column 11: 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 399, Column 7: start tag was here
          <br>
  • Error Line 401, Column 8: 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 395, Column 5: start tag was here
        <p class="vjs-no-video"><strong>Download Video:</strong>
  • Error Line 406, 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 406, Column 1: start tag was here
    <br>
  • Error Line 408, Column 336: end tag for "br" omitted, but OMITTAG NO was specified
    …/category/porn/" title="View all posts in Porn" rel="category tag">Porn</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 408, Column 332: start tag was here
    …/category/porn/" title="View all posts in Porn" rel="category tag">Porn</a><br>
  • Error Line 431, Column 160: "controls" is not a member of a group specified for any attribute
    …loads/kyle-king-charlie-harding-trenton-ducati-v.jpg" controls preload="none" >
  • Error Line 431, Column 175: element "video" undefined
    …loads/kyle-king-charlie-harding-trenton-ducati-v.jpg" controls preload="none" >

    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 432, Column 122: element "source" undefined
    …clips/tr_16033_04_big.mp4" type='video/mp4; codecs="avc1.42E01E, mp4a.40.2"' />

    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 450, Column 11: 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 450, Column 7: start tag was here
          <br>
  • Error Line 452, Column 8: 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 446, Column 5: start tag was here
        <p class="vjs-no-video"><strong>Download Video:</strong>
  • Error Line 455, Column 232: end tag for element "A" which is not open
    …038;buffer=" title="Raging Stallion" target="_blank">RagingStallion.com</A></p>

    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 455, Column 236: end tag for "a" omitted, but OMITTAG NO was specified
    …038;buffer=" title="Raging Stallion" target="_blank">RagingStallion.com</A></p>

    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 455, Column 37: start tag was here
    <p>- Watch the full-length scene at <a href="http://www.buddylead.com/ragingsta…
  • Error Line 457, 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 457, Column 1: start tag was here
    <br>
  • Error Line 459, Column 414: end tag for "br" omitted, but OMITTAG NO was specified
    …/category/porn/" title="View all posts in Porn" rel="category tag">Porn</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 459, Column 410: start tag was here
    …/category/porn/" title="View all posts in Porn" rel="category tag">Porn</a><br>
  • Error Line 471, Column 408: end tag for element "A" which is not open
    …dth="585" height="3616" class="alignnone size-full wp-image-59767" /></A></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 471, Column 414: end tag for "a" omitted, but OMITTAG NO was specified
    …dth="585" height="3616" class="alignnone size-full wp-image-59767" /></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 471, Column 31: start tag was here
    			<div class="mypicsgallery"><a href="http://enter.men.com/track/MTMzMS4xLjEuM…
  • Error Line 472, Column 405: end tag for element "A" which is not open
    …dth="585" height="3542" class="alignnone size-full wp-image-59768" /></A></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 472, Column 411: end tag for "a" omitted, but OMITTAG NO was specified
    …dth="585" height="3542" class="alignnone size-full wp-image-59768" /></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 472, Column 28: start tag was here
    <div class="mypicsgallery"><a href="http://enter.men.com/track/MTMzMS4xLjEuMS4w…
  • Error Line 480, Column 155: "controls" is not a member of a group specified for any attribute
    …ontent/uploads/thestrippersJOscreencapsz-590x331.jpg" controls preload="none" >
  • Error Line 480, Column 170: element "video" undefined
    …ontent/uploads/thestrippersJOscreencapsz-590x331.jpg" controls preload="none" >

    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 481, Column 143: element "source" undefined
    …scene1_trailer_mobile.mp4" type='video/mp4; codecs="avc1.42E01E, mp4a.40.2"' />

    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 499, Column 11: 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 499, Column 7: start tag was here
          <br>
  • Error Line 501, Column 8: 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 495, Column 5: start tag was here
        <p class="vjs-no-video"><strong>Download Video:</strong>
  • Error Line 507, 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 507, Column 1: start tag was here
    <br>
  • Error Line 509, Column 455: end tag for "br" omitted, but OMITTAG NO was specified
    …/category/porn/" title="View all posts in Porn" rel="category tag">Porn</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 509, Column 451: start tag was here
    …/category/porn/" title="View all posts in Porn" rel="category tag">Porn</a><br>
  • Error Line 531, Column 159: "controls" is not a member of a group specified for any attribute
    …s/wp-content/uploads/Hooker-Stories-2-Episode2-v.jpg" controls preload="none" >
  • Error Line 531, Column 174: element "video" undefined
    …s/wp-content/uploads/Hooker-Stories-2-Episode2-v.jpg" controls preload="none" >

    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 532, Column 129: element "source" undefined
    …ookerStories2Episode2.mp4" type='video/mp4; codecs="avc1.42E01E, mp4a.40.2"' />

    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 550, Column 11: 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 550, Column 7: start tag was here
          <br>
  • Error Line 552, Column 8: 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 546, Column 5: start tag was here
        <p class="vjs-no-video"><strong>Download Video:</strong>
  • Error Line 555, Column 372: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …om/track/MTAwODc3LjEuMS4xLjAuMC4wLjAuMA" target=_blank>NakedSword.com</a><br />
  • Error Line 558, 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 558, Column 1: start tag was here
    <br>
  • Error Line 560, Column 473: end tag for "br" omitted, but OMITTAG NO was specified
    …/category/porn/" title="View all posts in Porn" rel="category tag">Porn</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 560, Column 469: start tag was here
    …/category/porn/" title="View all posts in Porn" rel="category tag">Porn</a><br>
  • Error Line 571, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br><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 571, Column 1: start tag was here
    <br><br><br>
  • Error Line 571, Column 9: end tag for "br" omitted, but OMITTAG NO was specified
    <br><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 571, Column 5: start tag was here
    <br><br><br>
  • Error Line 571, Column 13: end tag for "br" omitted, but OMITTAG NO was specified
    <br><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 571, Column 9: start tag was here
    <br><br><br>
  • Error Line 589, Column 84: end tag for "br" omitted, but OMITTAG NO was specified
    …rm></div><div class="block text-24 widget_text">			<div class="textwidget"><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 589, Column 80: start tag was here
    …rm></div><div class="block text-24 widget_text">			<div class="textwidget"><br>
  • Error Line 687, Column 77: end tag for "br" omitted, but OMITTAG NO was specified
    </div><div class="block text-26 widget_text">			<div class="textwidget"><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 687, Column 73: start tag was here
    </div><div class="block text-26 widget_text">			<div class="textwidget"><br>
  • Error Line 689, 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 689, Column 1: start tag was here
    <br><br>
  • Error Line 689, 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 689, Column 5: start tag was here
    <br><br>
  • Warning Line 690, Column 61: cannot generate system identifier for general entity "su"
    …ddylead.com/menofmontreal/go.php?pr=9&su=2&si=62&pa=index&ar=&ad=177532&buffer…

    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 690, Column 61: general entity "su" not defined and no default entity
    …ddylead.com/menofmontreal/go.php?pr=9&su=2&si=62&pa=index&ar=&ad=177532&buffer…

    This is usually a cascading error caused by 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 690, Column 63: reference not terminated by REFC delimiter
    …ylead.com/menofmontreal/go.php?pr=9&su=2&si=62&pa=index&ar=&ad=177532&buffer="…

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

  • Warning Line 690, Column 63: reference to external entity in attribute value
    …ylead.com/menofmontreal/go.php?pr=9&su=2&si=62&pa=index&ar=&ad=177532&buffer="…

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

  • Error Line 690, Column 63: reference to entity "su" for which no system identifier could be generated
    …ylead.com/menofmontreal/go.php?pr=9&su=2&si=62&pa=index&ar=&ad=177532&buffer="…

    This is usually a cascading error caused by 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 690, Column 60: entity was defined here
    …uddylead.com/menofmontreal/go.php?pr=9&su=2&si=62&pa=index&ar=&ad=177532&buffe…
  • Warning Line 690, Column 66: cannot generate system identifier for general entity "si"
    …ad.com/menofmontreal/go.php?pr=9&su=2&si=62&pa=index&ar=&ad=177532&buffer=" ti…

    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 690, Column 66: general entity "si" not defined and no default entity
    …ad.com/menofmontreal/go.php?pr=9&su=2&si=62&pa=index&ar=&ad=177532&buffer=" ti…

    This is usually a cascading error caused by 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 690, Column 68: reference not terminated by REFC delimiter
    ….com/menofmontreal/go.php?pr=9&su=2&si=62&pa=index&ar=&ad=177532&buffer=" titl…

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

  • Warning Line 690, Column 68: reference to external entity in attribute value
    ….com/menofmontreal/go.php?pr=9&su=2&si=62&pa=index&ar=&ad=177532&buffer=" titl…

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

  • Error Line 690, Column 68: reference to entity "si" for which no system identifier could be generated
    ….com/menofmontreal/go.php?pr=9&su=2&si=62&pa=index&ar=&ad=177532&buffer=" titl…

    This is usually a cascading error caused by 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 690, Column 65: entity was defined here
    …ead.com/menofmontreal/go.php?pr=9&su=2&si=62&pa=index&ar=&ad=177532&buffer=" t…
  • Warning Line 690, Column 72: cannot generate system identifier for general entity "pa"
    …/menofmontreal/go.php?pr=9&su=2&si=62&pa=index&ar=&ad=177532&buffer=" title="M…

    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 690, Column 72: general entity "pa" not defined and no default entity
    …/menofmontreal/go.php?pr=9&su=2&si=62&pa=index&ar=&ad=177532&buffer=" title="M…

    This is usually a cascading error caused by 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 690, Column 74: reference not terminated by REFC delimiter
    …enofmontreal/go.php?pr=9&su=2&si=62&pa=index&ar=&ad=177532&buffer=" title="Men…

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

  • Warning Line 690, Column 74: reference to external entity in attribute value
    …enofmontreal/go.php?pr=9&su=2&si=62&pa=index&ar=&ad=177532&buffer=" title="Men…

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

  • Error Line 690, Column 74: reference to entity "pa" for which no system identifier could be generated
    …enofmontreal/go.php?pr=9&su=2&si=62&pa=index&ar=&ad=177532&buffer=" title="Men…

    This is usually a cascading error caused by 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 690, Column 71: entity was defined here
    …m/menofmontreal/go.php?pr=9&su=2&si=62&pa=index&ar=&ad=177532&buffer=" title="…
  • Warning Line 690, Column 81: cannot generate system identifier for general entity "ar"
    …treal/go.php?pr=9&su=2&si=62&pa=index&ar=&ad=177532&buffer=" title="MenOfMontr…

    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 690, Column 81: general entity "ar" not defined and no default entity
    …treal/go.php?pr=9&su=2&si=62&pa=index&ar=&ad=177532&buffer=" title="MenOfMontr…

    This is usually a cascading error caused by 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 690, Column 83: reference not terminated by REFC delimiter
    …eal/go.php?pr=9&su=2&si=62&pa=index&ar=&ad=177532&buffer=" title="MenOfMontrea…

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

  • Warning Line 690, Column 83: reference to external entity in attribute value
    …eal/go.php?pr=9&su=2&si=62&pa=index&ar=&ad=177532&buffer=" title="MenOfMontrea…

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

  • Error Line 690, Column 83: reference to entity "ar" for which no system identifier could be generated
    …eal/go.php?pr=9&su=2&si=62&pa=index&ar=&ad=177532&buffer=" title="MenOfMontrea…

    This is usually a cascading error caused by 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 690, Column 80: entity was defined here
    …ntreal/go.php?pr=9&su=2&si=62&pa=index&ar=&ad=177532&buffer=" title="MenOfMont…
  • Warning Line 690, Column 85: cannot generate system identifier for general entity "ad"
    …l/go.php?pr=9&su=2&si=62&pa=index&ar=&ad=177532&buffer=" title="MenOfMontreal.…

    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 690, Column 85: general entity "ad" not defined and no default entity
    …l/go.php?pr=9&su=2&si=62&pa=index&ar=&ad=177532&buffer=" title="MenOfMontreal.…

    This is usually a cascading error caused by 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 690, Column 87: reference not terminated by REFC delimiter
    …go.php?pr=9&su=2&si=62&pa=index&ar=&ad=177532&buffer=" title="MenOfMontreal.co…

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

  • Warning Line 690, Column 87: reference to external entity in attribute value
    …go.php?pr=9&su=2&si=62&pa=index&ar=&ad=177532&buffer=" title="MenOfMontreal.co…

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

  • Error Line 690, Column 87: reference to entity "ad" for which no system identifier could be generated
    …go.php?pr=9&su=2&si=62&pa=index&ar=&ad=177532&buffer=" title="MenOfMontreal.co…

    This is usually a cascading error caused by 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 690, Column 84: entity was defined here
    …al/go.php?pr=9&su=2&si=62&pa=index&ar=&ad=177532&buffer=" title="MenOfMontreal…
  • Warning Line 690, Column 95: cannot generate system identifier for general entity "buffer"
    …r=9&su=2&si=62&pa=index&ar=&ad=177532&buffer=" title="MenOfMontreal.com" targe…

    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 690, Column 95: general entity "buffer" not defined and no default entity
    …r=9&su=2&si=62&pa=index&ar=&ad=177532&buffer=" title="MenOfMontreal.com" targe…

    This is usually a cascading error caused by 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 690, Column 101: reference not terminated by REFC delimiter
    …=2&si=62&pa=index&ar=&ad=177532&buffer=" title="MenOfMontreal.com" target="_bl…

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

  • Warning Line 690, Column 101: reference to external entity in attribute value
    …=2&si=62&pa=index&ar=&ad=177532&buffer=" title="MenOfMontreal.com" target="_bl…

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

  • Error Line 690, Column 101: reference to entity "buffer" for which no system identifier could be generated
    …=2&si=62&pa=index&ar=&ad=177532&buffer=" title="MenOfMontreal.com" target="_bl…

    This is usually a cascading error caused by 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 690, Column 94: entity was defined here
    …pr=9&su=2&si=62&pa=index&ar=&ad=177532&buffer=" title="MenOfMontreal.com" targ…
  • Error Line 695, Column 248: end tag for "br" omitted, but OMITTAG NO was specified
    …e size-full wp-image-46568" /></a><br><a href="http://fagalicious.com/tag/john…

    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 695, Column 244: start tag was here
    …nnone size-full wp-image-46568" /></a><br><a href="http://fagalicious.com/tag/…
  • Error Line 695, Column 340: end tag for "br" omitted, but OMITTAG NO was specified
    …agalicious.com/tag/johnny-forza/" title="Johnny Forza">Johnny Forza</a><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 695, Column 336: start tag was here
    …agalicious.com/tag/johnny-forza/" title="Johnny Forza">Johnny Forza</a><br><br>
  • Error Line 695, Column 344: end tag for "br" omitted, but OMITTAG NO was specified
    …agalicious.com/tag/johnny-forza/" title="Johnny Forza">Johnny Forza</a><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 695, Column 340: start tag was here
    …agalicious.com/tag/johnny-forza/" title="Johnny Forza">Johnny Forza</a><br><br>
  • Error Line 698, Column 244: end tag for "br" omitted, but OMITTAG NO was specified
    …e size-full wp-image-46568" /></a><br><a href="http://fagalicious.com/tag/mick…

    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 698, Column 240: start tag was here
    …nnone size-full wp-image-46568" /></a><br><a href="http://fagalicious.com/tag/…
  • Error Line 698, Column 333: end tag for "br" omitted, but OMITTAG NO was specified
    …//fagalicious.com/tag/mick-lovell/" title="Mick Lovell">Mick Lovell</a><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 698, Column 329: start tag was here
    …//fagalicious.com/tag/mick-lovell/" title="Mick Lovell">Mick Lovell</a><br><br>
  • Error Line 698, Column 337: end tag for "br" omitted, but OMITTAG NO was specified
    …//fagalicious.com/tag/mick-lovell/" title="Mick Lovell">Mick Lovell</a><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 698, Column 333: start tag was here
    …//fagalicious.com/tag/mick-lovell/" title="Mick Lovell">Mick Lovell</a><br><br>
  • Error Line 701, Column 256: end tag for "br" omitted, but OMITTAG NO was specified
    …e size-full wp-image-46568" /></a><br><a href="http://fagalicious.com/tag/anth…

    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 701, Column 252: start tag was here
    …nnone size-full wp-image-46568" /></a><br><a href="http://fagalicious.com/tag/…
  • Error Line 701, Column 354: end tag for "br" omitted, but OMITTAG NO was specified
    …ious.com/tag/anthony-romero/" title="Anthony Romero">Anthony Romero</a><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 701, Column 350: start tag was here
    …ious.com/tag/anthony-romero/" title="Anthony Romero">Anthony Romero</a><br><br>
  • Error Line 701, Column 358: end tag for "br" omitted, but OMITTAG NO was specified
    …ious.com/tag/anthony-romero/" title="Anthony Romero">Anthony Romero</a><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 701, Column 354: start tag was here
    …ious.com/tag/anthony-romero/" title="Anthony Romero">Anthony Romero</a><br><br>
  • Error Line 704, Column 260: end tag for "br" omitted, but OMITTAG NO was specified
    …e size-full wp-image-46568" /></a><br><a href="http://fagalicious.com/tag/tyle…

    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 704, Column 256: start tag was here
    …nnone size-full wp-image-46568" /></a><br><a href="http://fagalicious.com/tag/…
  • Error Line 704, Column 361: end tag for "br" omitted, but OMITTAG NO was specified
    …s.com/tag/tyler-alexander/" title="Tyler Alexander">Tyler Alexander</a><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 704, Column 357: start tag was here
    …s.com/tag/tyler-alexander/" title="Tyler Alexander">Tyler Alexander</a><br><br>
  • Error Line 704, Column 365: end tag for "br" omitted, but OMITTAG NO was specified
    …s.com/tag/tyler-alexander/" title="Tyler Alexander">Tyler Alexander</a><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 704, Column 361: start tag was here
    …s.com/tag/tyler-alexander/" title="Tyler Alexander">Tyler Alexander</a><br><br>
  • Error Line 707, Column 248: end tag for "br" omitted, but OMITTAG NO was specified
    …e size-full wp-image-47019" /></a><br><a href="http://fagalicious.com/tag/jake…

    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 707, Column 244: start tag was here
    …nnone size-full wp-image-47019" /></a><br><a href="http://fagalicious.com/tag/…
  • Error Line 707, Column 340: end tag for "br" omitted, but OMITTAG NO was specified
    …agalicious.com/tag/jake-genesis/" title="Jake Genesis">Jake Genesis</a><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 707, Column 336: start tag was here
    …agalicious.com/tag/jake-genesis/" title="Jake Genesis">Jake Genesis</a><br><br>
  • Error Line 707, Column 344: end tag for "br" omitted, but OMITTAG NO was specified
    …agalicious.com/tag/jake-genesis/" title="Jake Genesis">Jake Genesis</a><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 707, Column 340: start tag was here
    …agalicious.com/tag/jake-genesis/" title="Jake Genesis">Jake Genesis</a><br><br>
  • Error Line 710, Column 248: end tag for "br" omitted, but OMITTAG NO was specified
    …e size-full wp-image-46640" /></a><br><a href="http://fagalicious.com/tag/andr…

    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 710, Column 244: start tag was here
    …nnone size-full wp-image-46640" /></a><br><a href="http://fagalicious.com/tag/…
  • Error Line 710, Column 340: end tag for "br" omitted, but OMITTAG NO was specified
    …agalicious.com/tag/andrew-stark/" title="Andrew Stark">Andrew Stark</a><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 710, Column 336: start tag was here
    …agalicious.com/tag/andrew-stark/" title="Andrew Stark">Andrew Stark</a><br><br>
  • Error Line 710, Column 344: end tag for "br" omitted, but OMITTAG NO was specified
    …agalicious.com/tag/andrew-stark/" title="Andrew Stark">Andrew Stark</a><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 710, Column 340: start tag was here
    …agalicious.com/tag/andrew-stark/" title="Andrew Stark">Andrew Stark</a><br><br>
  • Error Line 714, Column 248: end tag for "br" omitted, but OMITTAG NO was specified
    …e size-full wp-image-46568" /></a><br><a href="http://fagalicious.com/tag/dunc…

    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 714, Column 244: start tag was here
    …nnone size-full wp-image-46568" /></a><br><a href="http://fagalicious.com/tag/…
  • Error Line 714, Column 340: end tag for "br" omitted, but OMITTAG NO was specified
    …agalicious.com/tag/duncan-black/" title="Duncan Black">Duncan Black</a><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 714, Column 336: start tag was here
    …agalicious.com/tag/duncan-black/" title="Duncan Black">Duncan Black</a><br><br>
  • Error Line 714, Column 344: end tag for "br" omitted, but OMITTAG NO was specified
    …agalicious.com/tag/duncan-black/" title="Duncan Black">Duncan Black</a><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 714, Column 340: start tag was here
    …agalicious.com/tag/duncan-black/" title="Duncan Black">Duncan Black</a><br><br>
  • Error Line 717, Column 255: end tag for "br" omitted, but OMITTAG NO was specified
    …e size-full wp-image-46568" /></a><br><a href="http://fagalicious.com/tag/padd…

    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 717, Column 251: start tag was here
    …nnone size-full wp-image-46568" /></a><br><a href="http://fagalicious.com/tag/…
  • Error Line 717, Column 349: end tag for "br" omitted, but OMITTAG NO was specified
    …alicious.com/tag/paddy-obrian/" title="Paddy O'Brian">Paddy O'Brian</a><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 717, Column 345: start tag was here
    …alicious.com/tag/paddy-obrian/" title="Paddy O'Brian">Paddy O'Brian</a><br><br>
  • Error Line 717, Column 353: end tag for "br" omitted, but OMITTAG NO was specified
    …alicious.com/tag/paddy-obrian/" title="Paddy O'Brian">Paddy O'Brian</a><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 717, Column 349: start tag was here
    …alicious.com/tag/paddy-obrian/" title="Paddy O'Brian">Paddy O'Brian</a><br><br>
  • Error Line 722, Column 240: end tag for "br" omitted, but OMITTAG NO was specified
    …e size-full wp-image-47019" /></a><br><a href="http://fagalicious.com/tag/tate…

    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 722, Column 236: start tag was here
    …nnone size-full wp-image-47019" /></a><br><a href="http://fagalicious.com/tag/…
  • Error Line 722, Column 326: end tag for "br" omitted, but OMITTAG NO was specified
    …tp://fagalicious.com/tag/tate-ryder/" title="Tate Ryder">Tate Ryder</a><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 722, Column 322: start tag was here
    …tp://fagalicious.com/tag/tate-ryder/" title="Tate Ryder">Tate Ryder</a><br><br>
  • Error Line 722, Column 330: end tag for "br" omitted, but OMITTAG NO was specified
    …tp://fagalicious.com/tag/tate-ryder/" title="Tate Ryder">Tate Ryder</a><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 722, Column 326: start tag was here
    …tp://fagalicious.com/tag/tate-ryder/" title="Tate Ryder">Tate Ryder</a><br><br>
  • Error Line 725, Column 256: end tag for "br" omitted, but OMITTAG NO was specified
    …e size-full wp-image-46640" /></a><br><a href="http://fagalicious.com/tag/tren…

    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 725, Column 252: start tag was here
    …nnone size-full wp-image-46640" /></a><br><a href="http://fagalicious.com/tag/…
  • Error Line 725, Column 354: end tag for "br" omitted, but OMITTAG NO was specified
    …ious.com/tag/trenton-ducati/" title="Trenton Ducati">Trenton Ducati</a><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 725, Column 350: start tag was here
    …ious.com/tag/trenton-ducati/" title="Trenton Ducati">Trenton Ducati</a><br><br>
  • Error Line 725, Column 358: end tag for "br" omitted, but OMITTAG NO was specified
    …ious.com/tag/trenton-ducati/" title="Trenton Ducati">Trenton Ducati</a><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 725, Column 354: start tag was here
    …ious.com/tag/trenton-ducati/" title="Trenton Ducati">Trenton Ducati</a><br><br>
  • Error Line 730, Column 252: end tag for "br" omitted, but OMITTAG NO was specified
    …e size-full wp-image-46568" /></a><br><a href="http://fagalicious.com/tag/tomm…

    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 248: start tag was here
    …nnone size-full wp-image-46568" /></a><br><a href="http://fagalicious.com/tag/…
  • Error Line 730, Column 346: end tag for "br" omitted, but OMITTAG NO was specified
    …alicious.com/tag/tommy-defendi" title="Tommy Defendi">Tommy Defendi</a><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 730, Column 342: start tag was here
    …alicious.com/tag/tommy-defendi" title="Tommy Defendi">Tommy Defendi</a><br><br>
  • Error Line 730, Column 350: end tag for "br" omitted, but OMITTAG NO was specified
    …alicious.com/tag/tommy-defendi" title="Tommy Defendi">Tommy Defendi</a><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 730, Column 346: start tag was here
    …alicious.com/tag/tommy-defendi" title="Tommy Defendi">Tommy Defendi</a><br><br>
  • Error Line 733, Column 240: end tag for "br" omitted, but OMITTAG NO was specified
    …e size-full wp-image-46568" /></a><br><a href="http://fagalicious.com/tag/jess…

    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 733, Column 236: start tag was here
    …nnone size-full wp-image-46568" /></a><br><a href="http://fagalicious.com/tag/…
  • Error Line 733, Column 326: end tag for "br" omitted, but OMITTAG NO was specified
    …tp://fagalicious.com/tag/jessy-ares/" title="Jessy Ares">Jessy Ared</a><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 733, Column 322: start tag was here
    …tp://fagalicious.com/tag/jessy-ares/" title="Jessy Ares">Jessy Ared</a><br><br>
  • Error Line 733, Column 330: end tag for "br" omitted, but OMITTAG NO was specified
    …tp://fagalicious.com/tag/jessy-ares/" title="Jessy Ares">Jessy Ared</a><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 733, Column 326: start tag was here
    …tp://fagalicious.com/tag/jessy-ares/" title="Jessy Ares">Jessy Ared</a><br><br>
  • Error Line 738, Column 257: end tag for "br" omitted, but OMITTAG NO was specified
    …e size-full wp-image-47019" /></a><br><a href="http://fagalicious.com/tag/calv…

    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 738, Column 253: start tag was here
    …nnone size-full wp-image-47019" /></a><br><a href="http://fagalicious.com/tag/…
  • Error Line 738, Column 356: end tag for "br" omitted, but OMITTAG NO was specified
    …ous.com/tag/calvin-sean-cody/" title="Calvin Sean Cody">Calvin (SC)</a><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 738, Column 352: start tag was here
    …ous.com/tag/calvin-sean-cody/" title="Calvin Sean Cody">Calvin (SC)</a><br><br>
  • Error Line 738, Column 360: end tag for "br" omitted, but OMITTAG NO was specified
    …ous.com/tag/calvin-sean-cody/" title="Calvin Sean Cody">Calvin (SC)</a><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 738, Column 356: start tag was here
    …ous.com/tag/calvin-sean-cody/" title="Calvin Sean Cody">Calvin (SC)</a><br><br>
  • Error Line 741, Column 261: end tag for "br" omitted, but OMITTAG NO was specified
    …e size-full wp-image-46640" /></a><br><a href="http://fagalicious.com/tag/chri…

    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 257: start tag was here
    …nnone size-full wp-image-46640" /></a><br><a href="http://fagalicious.com/tag/…
  • Error Line 741, Column 362: end tag for "br" omitted, but OMITTAG NO was specified
    …s.com/tag/christian-wilde/" title="Christian Wilde">Christian Wilde</a><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 741, Column 358: start tag was here
    …s.com/tag/christian-wilde/" title="Christian Wilde">Christian Wilde</a><br><br>
  • Error Line 741, Column 366: end tag for "br" omitted, but OMITTAG NO was specified
    …s.com/tag/christian-wilde/" title="Christian Wilde">Christian Wilde</a><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 741, Column 362: start tag was here
    …s.com/tag/christian-wilde/" title="Christian Wilde">Christian Wilde</a><br><br>
  • Error Line 746, Column 248: end tag for "br" omitted, but OMITTAG NO was specified
    …e size-full wp-image-50171" /></a><br><a href="http://fagalicious.com/tag/john…

    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 746, Column 244: start tag was here
    …nnone size-full wp-image-50171" /></a><br><a href="http://fagalicious.com/tag/…
  • Error Line 746, Column 335: end tag for element "A" which is not open
    …agalicious.com/tag/johnny-rapid/" title="Johnny Rapid">Johnny Rapid</A><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 746, Column 340: end tag for "br" omitted, but OMITTAG NO was specified
    …agalicious.com/tag/johnny-rapid/" title="Johnny Rapid">Johnny Rapid</A><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 746, Column 336: start tag was here
    …agalicious.com/tag/johnny-rapid/" title="Johnny Rapid">Johnny Rapid</A><br><br>
  • Error Line 746, Column 344: end tag for "br" omitted, but OMITTAG NO was specified
    …agalicious.com/tag/johnny-rapid/" title="Johnny Rapid">Johnny Rapid</A><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 746, Column 340: start tag was here
    …agalicious.com/tag/johnny-rapid/" title="Johnny Rapid">Johnny Rapid</A><br><br>
  • Error Line 749, Column 75: document type does not allow element "a" here; missing one of "object", "span", "bdo", "applet", "iframe", "tt", "i", "b", "u", "s", "strike", "big", "small", "font", "em", "strong", "dfn", "code", "q", "samp", "kbd", "var", "cite", "abbr", "acronym", "sub", "sup", "label", "ins", "del" start-tag
    …brandon-sc/" title="Brandon Sean Cody"><img src="http://fleshandskin.com/wp-co…

    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 749, Column 254: end tag for "br" omitted, but OMITTAG NO was specified
    …e size-full wp-image-47019" /></a><br><a href="http://fagalicious.com/tag/bran…

    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 749, Column 250: start tag was here
    …nnone size-full wp-image-47019" /></a><br><a href="http://fagalicious.com/tag/…
  • Error Line 749, Column 328: document type does not allow element "a" here; missing one of "object", "span", "bdo", "applet", "iframe", "tt", "i", "b", "u", "s", "strike", "big", "small", "font", "em", "strong", "dfn", "code", "q", "samp", "kbd", "var", "cite", "abbr", "acronym", "sub", "sup", "label", "ins", "del" start-tag
    …licious.com/tag/brandon-sc/" title="Brandon Sean Cody">Brandon (SC)</a><br><br>

    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 749, Column 349: end tag for "br" omitted, but OMITTAG NO was specified
    …licious.com/tag/brandon-sc/" title="Brandon Sean Cody">Brandon (SC)</a><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 749, Column 345: start tag was here
    …licious.com/tag/brandon-sc/" title="Brandon Sean Cody">Brandon (SC)</a><br><br>
  • Error Line 749, Column 353: end tag for "br" omitted, but OMITTAG NO was specified
    …licious.com/tag/brandon-sc/" title="Brandon Sean Cody">Brandon (SC)</a><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 749, Column 349: start tag was here
    …licious.com/tag/brandon-sc/" title="Brandon Sean Cody">Brandon (SC)</a><br><br>
  • Error Line 754, Column 76: document type does not allow element "a" here; missing one of "object", "span", "bdo", "applet", "iframe", "tt", "i", "b", "u", "s", "strike", "big", "small", "font", "em", "strong", "dfn", "code", "q", "samp", "kbd", "var", "cite", "abbr", "acronym", "sub", "sup", "label", "ins", "del" start-tag
    …hillip-aubrey/" title="Phillip Aubrey"><img src="http://fleshandskin.com/wp-co…

    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 754, Column 258: end tag for "br" omitted, but OMITTAG NO was specified
    …e size-full wp-image-46641" /></a><br><a href="http://fagalicious.com/tag/phil…

    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 754, Column 254: start tag was here
    …nnone size-full wp-image-46641" /></a><br><a href="http://fagalicious.com/tag/…
  • Error Line 754, Column 333: document type does not allow element "a" here; missing one of "object", "span", "bdo", "applet", "iframe", "tt", "i", "b", "u", "s", "strike", "big", "small", "font", "em", "strong", "dfn", "code", "q", "samp", "kbd", "var", "cite", "abbr", "acronym", "sub", "sup", "label", "ins", "del" start-tag
    …ious.com/tag/phillip-aubrey/" title="Phillip Aubrey">Phillip Aubrey</a><br><br>

    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 754, Column 356: end tag for "br" omitted, but OMITTAG NO was specified
    …ious.com/tag/phillip-aubrey/" title="Phillip Aubrey">Phillip Aubrey</a><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 754, Column 352: start tag was here
    …ious.com/tag/phillip-aubrey/" title="Phillip Aubrey">Phillip Aubrey</a><br><br>
  • Error Line 754, Column 360: end tag for "br" omitted, but OMITTAG NO was specified
    …ious.com/tag/phillip-aubrey/" title="Phillip Aubrey">Phillip Aubrey</a><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 754, Column 356: start tag was here
    …ious.com/tag/phillip-aubrey/" title="Phillip Aubrey">Phillip Aubrey</a><br><br>
  • Error Line 757, Column 104: document type does not allow element "a" here; missing one of "object", "span", "bdo", "applet", "iframe", "tt", "i", "b", "u", "s", "strike", "big", "small", "font", "em", "strong", "dfn", "code", "q", "samp", "kbd", "var", "cite", "abbr", "acronym", "sub", "sup", "label", "ins", "del" start-tag
    …" title="Marc Dylan aka Chris Gabriel"><img src="http://fleshandskin.com/wp-co…

    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 757, Column 296: end tag for "br" omitted, but OMITTAG NO was specified
    …e size-full wp-image-37953" /></a><br><a href="http://fagalicious.com/tag/marc…

    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 757, Column 292: start tag was here
    …nnone size-full wp-image-37953" /></a><br><a href="http://fagalicious.com/tag/…
  • Error Line 757, Column 399: document type does not allow element "a" here; missing one of "object", "span", "bdo", "applet", "iframe", "tt", "i", "b", "u", "s", "strike", "big", "small", "font", "em", "strong", "dfn", "code", "q", "samp", "kbd", "var", "cite", "abbr", "acronym", "sub", "sup", "label", "ins", "del" start-tag
    …aka-chris-gabriel/" title="Marc Dylan aka Chris Gabriel">Marc Dylan</a><br><br>

    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 757, Column 418: end tag for "br" omitted, but OMITTAG NO was specified
    …aka-chris-gabriel/" title="Marc Dylan aka Chris Gabriel">Marc Dylan</a><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 757, Column 414: start tag was here
    …aka-chris-gabriel/" title="Marc Dylan aka Chris Gabriel">Marc Dylan</a><br><br>
  • Error Line 757, Column 422: end tag for "br" omitted, but OMITTAG NO was specified
    …aka-chris-gabriel/" title="Marc Dylan aka Chris Gabriel">Marc Dylan</a><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 757, Column 418: start tag was here
    …aka-chris-gabriel/" title="Marc Dylan aka Chris Gabriel">Marc Dylan</a><br><br>
  • Error Line 762, Column 65: document type does not allow element "a" here; missing one of "object", "span", "bdo", "applet", "iframe", "tt", "i", "b", "u", "s", "strike", "big", "small", "font", "em", "strong", "dfn", "code", "q", "samp", "kbd", "var", "cite", "abbr", "acronym", "sub", "sup", "label", "ins", "del" start-tag
    …s.com/tag/jimmy-coxxx-aka-jimmy-clay/"><img src="http://fleshandskin.com/wp-co…

    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 762, Column 253: end tag for "br" omitted, but OMITTAG NO was specified
    …e size-full wp-image-41741" /></a><br><a href="http://fagalicious.com/tag/jimm…

    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 762, Column 249: start tag was here
    …nnone size-full wp-image-41741" /></a><br><a href="http://fagalicious.com/tag/…
  • Error Line 762, Column 317: document type does not allow element "a" here; missing one of "object", "span", "bdo", "applet", "iframe", "tt", "i", "b", "u", "s", "strike", "big", "small", "font", "em", "strong", "dfn", "code", "q", "samp", "kbd", "var", "cite", "abbr", "acronym", "sub", "sup", "label", "ins", "del" start-tag
    …http://fagalicious.com/tag/jimmy-coxxx-aka-jimmy-clay/">Jimmy Coxxx</A><br><br>

    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 762, Column 332: end tag for element "A" which is not open
    …http://fagalicious.com/tag/jimmy-coxxx-aka-jimmy-clay/">Jimmy Coxxx</A><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 762, Column 337: end tag for "br" omitted, but OMITTAG NO was specified
    …http://fagalicious.com/tag/jimmy-coxxx-aka-jimmy-clay/">Jimmy Coxxx</A><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 762, Column 333: start tag was here
    …http://fagalicious.com/tag/jimmy-coxxx-aka-jimmy-clay/">Jimmy Coxxx</A><br><br>
  • Error Line 762, Column 341: end tag for "br" omitted, but OMITTAG NO was specified
    …http://fagalicious.com/tag/jimmy-coxxx-aka-jimmy-clay/">Jimmy Coxxx</A><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 762, Column 337: start tag was here
    …http://fagalicious.com/tag/jimmy-coxxx-aka-jimmy-clay/">Jimmy Coxxx</A><br><br>
  • Error Line 765, Column 51: document type does not allow element "a" here; missing one of "object", "span", "bdo", "applet", "iframe", "tt", "i", "b", "u", "s", "strike", "big", "small", "font", "em", "strong", "dfn", "code", "q", "samp", "kbd", "var", "cite", "abbr", "acronym", "sub", "sup", "label", "ins", "del" start-tag
    …p://fagalicious.com/tag/spencer-reed/"><img src="http://fleshandskin.com/wp-co…

    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 765, Column 229: end tag for "br" omitted, but OMITTAG NO was specified
    …e size-full wp-image-41749" /></a><br><a href="http://fagalicious.com/tag/spen…

    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 765, Column 225: start tag was here
    …nnone size-full wp-image-41749" /></a><br><a href="http://fagalicious.com/tag/…
  • Error Line 765, Column 279: document type does not allow element "a" here; missing one of "object", "span", "bdo", "applet", "iframe", "tt", "i", "b", "u", "s", "strike", "big", "small", "font", "em", "strong", "dfn", "code", "q", "samp", "kbd", "var", "cite", "abbr", "acronym", "sub", "sup", "label", "ins", "del" start-tag
    …<br><a href="http://fagalicious.com/tag/spencer-reed/">Spencer Reed</a><br><br>

    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 765, Column 300: end tag for "br" omitted, but OMITTAG NO was specified
    …<br><a href="http://fagalicious.com/tag/spencer-reed/">Spencer Reed</a><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 765, Column 296: start tag was here
    …<br><a href="http://fagalicious.com/tag/spencer-reed/">Spencer Reed</a><br><br>
  • Error Line 765, Column 304: end tag for "br" omitted, but OMITTAG NO was specified
    …<br><a href="http://fagalicious.com/tag/spencer-reed/">Spencer Reed</a><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 765, Column 300: start tag was here
    …<br><a href="http://fagalicious.com/tag/spencer-reed/">Spencer Reed</a><br><br>
  • Error Line 770, Column 50: document type does not allow element "a" here; missing one of "object", "span", "bdo", "applet", "iframe", "tt", "i", "b", "u", "s", "strike", "big", "small", "font", "em", "strong", "dfn", "code", "q", "samp", "kbd", "var", "cite", "abbr", "acronym", "sub", "sup", "label", "ins", "del" start-tag
    …tp://fagalicious.com/tag/spencer-fox/"><img src="http://fleshandskin.com/wp-co…

    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 770, Column 226: end tag for "br" omitted, but OMITTAG NO was specified
    …e size-full wp-image-41742" /></a><br><a href="http://fagalicious.com/tag/spen…

    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 770, Column 222: start tag was here
    …nnone size-full wp-image-41742" /></a><br><a href="http://fagalicious.com/tag/…
  • Error Line 770, Column 275: document type does not allow element "a" here; missing one of "object", "span", "bdo", "applet", "iframe", "tt", "i", "b", "u", "s", "strike", "big", "small", "font", "em", "strong", "dfn", "code", "q", "samp", "kbd", "var", "cite", "abbr", "acronym", "sub", "sup", "label", "ins", "del" start-tag
    …a><br><a href="http://fagalicious.com/tag/spencer-fox/">Spencer Fox</a><br><br>

    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 770, Column 295: end tag for "br" omitted, but OMITTAG NO was specified
    …a><br><a href="http://fagalicious.com/tag/spencer-fox/">Spencer Fox</a><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 770, Column 291: start tag was here
    …a><br><a href="http://fagalicious.com/tag/spencer-fox/">Spencer Fox</a><br><br>
  • Error Line 770, Column 299: end tag for "br" omitted, but OMITTAG NO was specified
    …a><br><a href="http://fagalicious.com/tag/spencer-fox/">Spencer Fox</a><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 770, Column 295: start tag was here
    …a><br><a href="http://fagalicious.com/tag/spencer-fox/">Spencer Fox</a><br><br>
  • Error Line 773, Column 51: document type does not allow element "a" here; missing one of "object", "span", "bdo", "applet", "iframe", "tt", "i", "b", "u", "s", "strike", "big", "small", "font", "em", "strong", "dfn", "code", "q", "samp", "kbd", "var", "cite", "abbr", "acronym", "sub", "sup", "label", "ins", "del" start-tag
    …p://fagalicious.com/tag/austin-wilde/"><img src="http://fleshandskin.com/wp-co…

    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 773, Column 227: end tag for "br" omitted, but OMITTAG NO was specified
    …e size-full wp-image-27885" /></a><br><a href="http://fagalicious.com/tag/aust…

    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 773, Column 223: start tag was here
    …nnone size-full wp-image-27885" /></a><br><a href="http://fagalicious.com/tag/…
  • Error Line 773, Column 277: document type does not allow element "a" here; missing one of "object", "span", "bdo", "applet", "iframe", "tt", "i", "b", "u", "s", "strike", "big", "small", "font", "em", "strong", "dfn", "code", "q", "samp", "kbd", "var", "cite", "abbr", "acronym", "sub", "sup", "label", "ins", "del" start-tag
    …<br><a href="http://fagalicious.com/tag/austin-wilde/">Austin Wilde</a><br><br>

    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 773, Column 298: end tag for "br" omitted, but OMITTAG NO was specified
    …<br><a href="http://fagalicious.com/tag/austin-wilde/">Austin Wilde</a><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 773, Column 294: start tag was here
    …<br><a href="http://fagalicious.com/tag/austin-wilde/">Austin Wilde</a><br><br>
  • Error Line 773, Column 302: end tag for "br" omitted, but OMITTAG NO was specified
    …<br><a href="http://fagalicious.com/tag/austin-wilde/">Austin Wilde</a><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 773, Column 298: start tag was here
    …<br><a href="http://fagalicious.com/tag/austin-wilde/">Austin Wilde</a><br><br>
  • Error Line 778, Column 47: document type does not allow element "a" here; missing one of "object", "span", "bdo", "applet", "iframe", "tt", "i", "b", "u", "s", "strike", "big", "small", "font", "em", "strong", "dfn", "code", "q", "samp", "kbd", "var", "cite", "abbr", "acronym", "sub", "sup", "label", "ins", "del" start-tag
    …"http://fagalicious.com/tag/aiden-cf/"><img src="http://fleshandskin.com/wp-co…

    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 778, Column 216: end tag for "br" omitted, but OMITTAG NO was specified
    …e size-full wp-image-28235" /></a><br><a href="http://fagalicious.com/tag/aide…

    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 778, Column 212: start tag was here
    …nnone size-full wp-image-28235" /></a><br><a href="http://fagalicious.com/tag/…
  • Error Line 778, Column 262: document type does not allow element "a" here; missing one of "object", "span", "bdo", "applet", "iframe", "tt", "i", "b", "u", "s", "strike", "big", "small", "font", "em", "strong", "dfn", "code", "q", "samp", "kbd", "var", "cite", "abbr", "acronym", "sub", "sup", "label", "ins", "del" start-tag
    …/></a><br><a href="http://fagalicious.com/tag/aiden-cf/">Aiden (CF)</a><br><br>

    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 778, Column 281: end tag for "br" omitted, but OMITTAG NO was specified
    …/></a><br><a href="http://fagalicious.com/tag/aiden-cf/">Aiden (CF)</a><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 778, Column 277: start tag was here
    …/></a><br><a href="http://fagalicious.com/tag/aiden-cf/">Aiden (CF)</a><br><br>
  • Error Line 778, Column 285: end tag for "br" omitted, but OMITTAG NO was specified
    …/></a><br><a href="http://fagalicious.com/tag/aiden-cf/">Aiden (CF)</a><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 778, Column 281: start tag was here
    …/></a><br><a href="http://fagalicious.com/tag/aiden-cf/">Aiden (CF)</a><br><br>
  • Error Line 781, Column 54: document type does not allow element "a" here; missing one of "object", "span", "bdo", "applet", "iframe", "tt", "i", "b", "u", "s", "strike", "big", "small", "font", "em", "strong", "dfn", "code", "q", "samp", "kbd", "var", "cite", "abbr", "acronym", "sub", "sup", "label", "ins", "del" start-tag
    …/fagalicious.com/tag/topher-dimaggio/"><img src="http://fleshandskin.com/wp-co…

    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 781, Column 238: end tag for "br" omitted, but OMITTAG NO was specified
    …e size-full wp-image-27886" /></a><br><a href="http://fagalicious.com/tag/toph…

    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 781, Column 234: start tag was here
    …nnone size-full wp-image-27886" /></a><br><a href="http://fagalicious.com/tag/…
  • Error Line 781, Column 291: document type does not allow element "a" here; missing one of "object", "span", "bdo", "applet", "iframe", "tt", "i", "b", "u", "s", "strike", "big", "small", "font", "em", "strong", "dfn", "code", "q", "samp", "kbd", "var", "cite", "abbr", "acronym", "sub", "sup", "label", "ins", "del" start-tag
    … href="http://fagalicious.com/tag/topher-dimaggio/">Topher DiMaggio</a><br><br>

    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 781, Column 315: end tag for "br" omitted, but OMITTAG NO was specified
    … href="http://fagalicious.com/tag/topher-dimaggio/">Topher DiMaggio</a><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 781, Column 311: start tag was here
    … href="http://fagalicious.com/tag/topher-dimaggio/">Topher DiMaggio</a><br><br>
  • Error Line 781, Column 319: end tag for "br" omitted, but OMITTAG NO was specified
    … href="http://fagalicious.com/tag/topher-dimaggio/">Topher DiMaggio</a><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 781, Column 315: start tag was here
    … href="http://fagalicious.com/tag/topher-dimaggio/">Topher DiMaggio</a><br><br>
  • Error Line 786, Column 51: document type does not allow element "a" here; missing one of "object", "span", "bdo", "applet", "iframe", "tt", "i", "b", "u", "s", "strike", "big", "small", "font", "em", "strong", "dfn", "code", "q", "samp", "kbd", "var", "cite", "abbr", "acronym", "sub", "sup", "label", "ins", "del" start-tag
    …p://fagalicious.com/tag/adam-killian/"><img src="http://fleshandskin.com/wp-co…

    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 786, Column 225: end tag for "br" omitted, but OMITTAG NO was specified
    …nnone size-full wp-image-41747" /><br><a href="http://fagalicious.com/tag/adam…

    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 786, Column 221: start tag was here
    …alignnone size-full wp-image-41747" /><br><a href="http://fagalicious.com/tag/…
  • Error Line 786, Column 275: document type does not allow element "a" here; missing one of "object", "span", "bdo", "applet", "iframe", "tt", "i", "b", "u", "s", "strike", "big", "small", "font", "em", "strong", "dfn", "code", "q", "samp", "kbd", "var", "cite", "abbr", "acronym", "sub", "sup", "label", "ins", "del" start-tag
    …<br><a href="http://fagalicious.com/tag/adam-killian/">Adam Killian</a><br><br>

    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 786, Column 296: end tag for "br" omitted, but OMITTAG NO was specified
    …<br><a href="http://fagalicious.com/tag/adam-killian/">Adam Killian</a><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 786, Column 292: start tag was here
    …<br><a href="http://fagalicious.com/tag/adam-killian/">Adam Killian</a><br><br>
  • Error Line 786, Column 300: end tag for "br" omitted, but OMITTAG NO was specified
    …<br><a href="http://fagalicious.com/tag/adam-killian/">Adam Killian</a><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 786, Column 296: start tag was here
    …<br><a href="http://fagalicious.com/tag/adam-killian/">Adam Killian</a><br><br>
  • Error Line 789, Column 67: document type does not allow element "a" here; missing one of "object", "span", "bdo", "applet", "iframe", "tt", "i", "b", "u", "s", "strike", "big", "small", "font", "em", "strong", "dfn", "code", "q", "samp", "kbd", "var", "cite", "abbr", "acronym", "sub", "sup", "label", "ins", "del" start-tag
    …com/tag/brady-jensen-jonah-sean-cody/"><img src="http://fleshandskin.com/wp-co…

    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 789, Column 245: end tag for "br" omitted, but OMITTAG NO was specified
    …e size-full wp-image-22159" /></a><br><a href="http://fagalicious.com/tag/brad…

    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 789, Column 241: start tag was here
    …nnone size-full wp-image-22159" /></a><br><a href="http://fagalicious.com/tag/…
  • Error Line 789, Column 311: document type does not allow element "a" here; missing one of "object", "span", "bdo", "applet", "iframe", "tt", "i", "b", "u", "s", "strike", "big", "small", "font", "em", "strong", "dfn", "code", "q", "samp", "kbd", "var", "cite", "abbr", "acronym", "sub", "sup", "label", "ins", "del" start-tag
    …p://fagalicious.com/tag/brady-jensen-jonah-sean-cody/">Brady Jensen</a><br><br>

    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 789, Column 332: end tag for "br" omitted, but OMITTAG NO was specified
    …p://fagalicious.com/tag/brady-jensen-jonah-sean-cody/">Brady Jensen</a><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 789, Column 328: start tag was here
    …p://fagalicious.com/tag/brady-jensen-jonah-sean-cody/">Brady Jensen</a><br><br>
  • Error Line 789, Column 336: end tag for "br" omitted, but OMITTAG NO was specified
    …p://fagalicious.com/tag/brady-jensen-jonah-sean-cody/">Brady Jensen</a><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 789, Column 332: start tag was here
    …p://fagalicious.com/tag/brady-jensen-jonah-sean-cody/">Brady Jensen</a><br><br>
  • Error Line 794, Column 52: document type does not allow element "a" here; missing one of "object", "span", "bdo", "applet", "iframe", "tt", "i", "b", "u", "s", "strike", "big", "small", "font", "em", "strong", "dfn", "code", "q", "samp", "kbd", "var", "cite", "abbr", "acronym", "sub", "sup", "label", "ins", "del" start-tag
    …://fagalicious.com/tag/jessie-colter/"><img src="http://fleshandskin.com/wp-co…

    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 794, Column 175: literal is missing closing delimiter
    …le="Jessie Colter" width="150" class="alignnone size-full border="0" wp-image-…

    Did you forget to close a (double) quote mark?

  • Error Line 794, Column 204: end tag for "img" omitted, but OMITTAG NO was specified
    …" class="alignnone size-full border="0" wp-image-41743" /></a><br><a href="htt…

    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 794, Column 53: start tag was here
    …//fagalicious.com/tag/jessie-colter/"><img src="http://fleshandskin.com/wp-con…
  • Error Line 794, Column 232: end tag for "br" omitted, but OMITTAG NO was specified
    … border="0" wp-image-41743" /></a><br><a href="http://fagalicious.com/tag/jess…

    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 794, Column 228: start tag was here
    …full border="0" wp-image-41743" /></a><br><a href="http://fagalicious.com/tag/…
  • Error Line 794, Column 283: document type does not allow element "a" here; missing one of "object", "span", "bdo", "applet", "iframe", "tt", "i", "b", "u", "s", "strike", "big", "small", "font", "em", "strong", "dfn", "code", "q", "samp", "kbd", "var", "cite", "abbr", "acronym", "sub", "sup", "label", "ins", "del" start-tag
    …r><a href="http://fagalicious.com/tag/jessie-colter/">Jessie Colter</a><br><br>

    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 794, Column 305: end tag for "br" omitted, but OMITTAG NO was specified
    …r><a href="http://fagalicious.com/tag/jessie-colter/">Jessie Colter</a><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 794, Column 301: start tag was here
    …r><a href="http://fagalicious.com/tag/jessie-colter/">Jessie Colter</a><br><br>
  • Error Line 794, Column 309: end tag for "br" omitted, but OMITTAG NO was specified
    …r><a href="http://fagalicious.com/tag/jessie-colter/">Jessie Colter</a><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 794, Column 305: start tag was here
    …r><a href="http://fagalicious.com/tag/jessie-colter/">Jessie Colter</a><br><br>
  • Error Line 797, Column 52: document type does not allow element "a" here; missing one of "object", "span", "bdo", "applet", "iframe", "tt", "i", "b", "u", "s", "strike", "big", "small", "font", "em", "strong", "dfn", "code", "q", "samp", "kbd", "var", "cite", "abbr", "acronym", "sub", "sup", "label", "ins", "del" start-tag
    …://fagalicious.com/tag/samuel-otoole/"><img src="http://fleshandskin.com/wp-co…

    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 797, Column 232: end tag for "br" omitted, but OMITTAG NO was specified
    …e size-full wp-image-22159" /></a><br><a href="http://fagalicious.com/tag/samu…

    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 797, Column 228: start tag was here
    …nnone size-full wp-image-22159" /></a><br><a href="http://fagalicious.com/tag/…
  • Error Line 797, Column 283: document type does not allow element "a" here; missing one of "object", "span", "bdo", "applet", "iframe", "tt", "i", "b", "u", "s", "strike", "big", "small", "font", "em", "strong", "dfn", "code", "q", "samp", "kbd", "var", "cite", "abbr", "acronym", "sub", "sup", "label", "ins", "del" start-tag
    …><a href="http://fagalicious.com/tag/samuel-otoole/">Samuel O'Toole</a><br><br>

    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 797, Column 306: end tag for "br" omitted, but OMITTAG NO was specified
    …><a href="http://fagalicious.com/tag/samuel-otoole/">Samuel O'Toole</a><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 797, Column 302: start tag was here
    …><a href="http://fagalicious.com/tag/samuel-otoole/">Samuel O'Toole</a><br><br>
  • Error Line 797, Column 310: end tag for "br" omitted, but OMITTAG NO was specified
    …><a href="http://fagalicious.com/tag/samuel-otoole/">Samuel O'Toole</a><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 797, Column 306: start tag was here
    …><a href="http://fagalicious.com/tag/samuel-otoole/">Samuel O'Toole</a><br><br>
  • Error Line 802, Column 51: document type does not allow element "a" here; missing one of "object", "span", "bdo", "applet", "iframe", "tt", "i", "b", "u", "s", "strike", "big", "small", "font", "em", "strong", "dfn", "code", "q", "samp", "kbd", "var", "cite", "abbr", "acronym", "sub", "sup", "label", "ins", "del" start-tag
    …p://fagalicious.com/tag/gavin-waters/"><img src="http://fleshandskin.com/wp-co…

    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 802, Column 240: end tag for "br" omitted, but OMITTAG NO was specified
    …ne size-full wp-image-3674" /></a><br><a href="http://fagalicious.com/tag/gavi…

    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 802, Column 236: start tag was here
    …gnnone size-full wp-image-3674" /></a><br><a href="http://fagalicious.com/tag/…
  • Error Line 802, Column 290: document type does not allow element "a" here; missing one of "object", "span", "bdo", "applet", "iframe", "tt", "i", "b", "u", "s", "strike", "big", "small", "font", "em", "strong", "dfn", "code", "q", "samp", "kbd", "var", "cite", "abbr", "acronym", "sub", "sup", "label", "ins", "del" start-tag
    …<br><a href="http://fagalicious.com/tag/gavin-waters/">Gavin Waters</a><br><br>

    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 802, Column 311: end tag for "br" omitted, but OMITTAG NO was specified
    …<br><a href="http://fagalicious.com/tag/gavin-waters/">Gavin Waters</a><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 802, Column 307: start tag was here
    …<br><a href="http://fagalicious.com/tag/gavin-waters/">Gavin Waters</a><br><br>
  • Error Line 802, Column 315: end tag for "br" omitted, but OMITTAG NO was specified
    …<br><a href="http://fagalicious.com/tag/gavin-waters/">Gavin Waters</a><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 802, Column 311: start tag was here
    …<br><a href="http://fagalicious.com/tag/gavin-waters/">Gavin Waters</a><br><br>
  • Error Line 805, Column 50: document type does not allow element "a" here; missing one of "object", "span", "bdo", "applet", "iframe", "tt", "i", "b", "u", "s", "strike", "big", "small", "font", "em", "strong", "dfn", "code", "q", "samp", "kbd", "var", "cite", "abbr", "acronym", "sub", "sup", "label", "ins", "del" start-tag
    …tp://fagalicious.com/tag/marcus-mojo/"><img src="http://fleshandskin.com/wp-co…

    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 805, Column 284: end tag for "br" omitted, but OMITTAG NO was specified
    …ne size-full wp-image-3674" /></a><br><a href="http://fagalicious.com/tag/marc…

    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 805, Column 280: start tag was here
    …gnnone size-full wp-image-3674" /></a><br><a href="http://fagalicious.com/tag/…
  • Error Line 805, Column 333: document type does not allow element "a" here; missing one of "object", "span", "bdo", "applet", "iframe", "tt", "i", "b", "u", "s", "strike", "big", "small", "font", "em", "strong", "dfn", "code", "q", "samp", "kbd", "var", "cite", "abbr", "acronym", "sub", "sup", "label", "ins", "del" start-tag
    …a><br><a href="http://fagalicious.com/tag/marcus-mojo/">Marcus Mojo</a><br><br>

    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 805, Column 353: end tag for "br" omitted, but OMITTAG NO was specified
    …a><br><a href="http://fagalicious.com/tag/marcus-mojo/">Marcus Mojo</a><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 805, Column 349: start tag was here
    …a><br><a href="http://fagalicious.com/tag/marcus-mojo/">Marcus Mojo</a><br><br>
  • Error Line 805, Column 357: end tag for "br" omitted, but OMITTAG NO was specified
    …a><br><a href="http://fagalicious.com/tag/marcus-mojo/">Marcus Mojo</a><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 805, Column 353: start tag was here
    …a><br><a href="http://fagalicious.com/tag/marcus-mojo/">Marcus Mojo</a><br><br>
  • Error Line 810, Column 52: document type does not allow element "a" here; missing one of "object", "span", "bdo", "applet", "iframe", "tt", "i", "b", "u", "s", "strike", "big", "small", "font", "em", "strong", "dfn", "code", "q", "samp", "kbd", "var", "cite", "abbr", "acronym", "sub", "sup", "label", "ins", "del" start-tag
    …://fagalicious.com/tag/damien-crosse/"><img src="http://fleshandskin.com/wp-co…

    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 810, Column 243: end tag for "br" omitted, but OMITTAG NO was specified
    …ne size-full wp-image-3450" /></a><br><a href="http://fagalicious.com/tag/dami…

    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 810, Column 239: start tag was here
    …gnnone size-full wp-image-3450" /></a><br><a href="http://fagalicious.com/tag/…
  • Error Line 810, Column 294: document type does not allow element "a" here; missing one of "object", "span", "bdo", "applet", "iframe", "tt", "i", "b", "u", "s", "strike", "big", "small", "font", "em", "strong", "dfn", "code", "q", "samp", "kbd", "var", "cite", "abbr", "acronym", "sub", "sup", "label", "ins", "del" start-tag
    …r><a href="http://fagalicious.com/tag/damien-crosse/">Damien Crosse</a><br><br>

    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 810, Column 316: end tag for "br" omitted, but OMITTAG NO was specified
    …r><a href="http://fagalicious.com/tag/damien-crosse/">Damien Crosse</a><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 810, Column 312: start tag was here
    …r><a href="http://fagalicious.com/tag/damien-crosse/">Damien Crosse</a><br><br>
  • Error Line 810, Column 320: end tag for "br" omitted, but OMITTAG NO was specified
    …r><a href="http://fagalicious.com/tag/damien-crosse/">Damien Crosse</a><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 810, Column 316: start tag was here
    …r><a href="http://fagalicious.com/tag/damien-crosse/">Damien Crosse</a><br><br>
  • Error Line 813, Column 48: document type does not allow element "a" here; missing one of "object", "span", "bdo", "applet", "iframe", "tt", "i", "b", "u", "s", "strike", "big", "small", "font", "em", "strong", "dfn", "code", "q", "samp", "kbd", "var", "cite", "abbr", "acronym", "sub", "sup", "label", "ins", "del" start-tag
    …http://fagalicious.com/tag/rod-daily/"><img src="http://fleshandskin.com/wp-co…

    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 813, Column 226: end tag for "br" omitted, but OMITTAG NO was specified
    …ne size-full wp-image-3454" /></a><br><a href="http://fagalicious.com/tag/rod-…

    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 813, Column 222: start tag was here
    …gnnone size-full wp-image-3454" /></a><br><a href="http://fagalicious.com/tag/…
  • Error Line 813, Column 273: document type does not allow element "a" here; missing one of "object", "span", "bdo", "applet", "iframe", "tt", "i", "b", "u", "s", "strike", "big", "small", "font", "em", "strong", "dfn", "code", "q", "samp", "kbd", "var", "cite", "abbr", "acronym", "sub", "sup", "label", "ins", "del" start-tag
    …/></a><br><a href="http://fagalicious.com/tag/rod-daily/">Rod Daily</a><br><br>

    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 813, Column 291: end tag for "br" omitted, but OMITTAG NO was specified
    …/></a><br><a href="http://fagalicious.com/tag/rod-daily/">Rod Daily</a><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 813, Column 287: start tag was here
    …/></a><br><a href="http://fagalicious.com/tag/rod-daily/">Rod Daily</a><br><br>
  • Error Line 813, Column 295: end tag for "br" omitted, but OMITTAG NO was specified
    …/></a><br><a href="http://fagalicious.com/tag/rod-daily/">Rod Daily</a><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 813, Column 291: start tag was here
    …/></a><br><a href="http://fagalicious.com/tag/rod-daily/">Rod Daily</a><br><br>
  • Error Line 816, Column 6: end tag for "a" omitted, but OMITTAG NO was specified
    </div></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 786, Column 1: start tag was here
    <a href="http://fagalicious.com/tag/adam-killian/"><img src="http://fleshandski…
  • Error Line 816, Column 6: end tag for "a" omitted, but OMITTAG NO was specified
    </div></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 762, Column 253: start tag was here
    …e size-full wp-image-41741" /></a><br><a href="http://fagalicious.com/tag/jimm…
  • Error Line 816, Column 6: end tag for "a" omitted, but OMITTAG NO was specified
    </div></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 746, Column 248: start tag was here
    …e size-full wp-image-50171" /></a><br><a href="http://fagalicious.com/tag/john…
  • Error Line 817, Column 79: end tag for "br" omitted, but OMITTAG NO was specified
    		</div><div class="block text-18 widget_text">			<div class="textwidget"><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 817, Column 75: start tag was here
    		</div><div class="block text-18 widget_text">			<div class="textwidget"><br>
  • Warning Line 818, Column 63: reference not terminated by REFC delimiter
    …ylead.com/nextdoorebony/go.php?pr=9&su=2&si=51&pa=index&ar=&ad=177532&buffer="…

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

  • Warning Line 818, Column 63: reference to external entity in attribute value
    …ylead.com/nextdoorebony/go.php?pr=9&su=2&si=51&pa=index&ar=&ad=177532&buffer="…

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

  • Error Line 818, Column 63: reference to entity "su" for which no system identifier could be generated
    …ylead.com/nextdoorebony/go.php?pr=9&su=2&si=51&pa=index&ar=&ad=177532&buffer="…

    This is usually a cascading error caused by 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 690, Column 60: entity was defined here
    …uddylead.com/menofmontreal/go.php?pr=9&su=2&si=62&pa=index&ar=&ad=177532&buffe…
  • Warning Line 818, Column 68: reference not terminated by REFC delimiter
    ….com/nextdoorebony/go.php?pr=9&su=2&si=51&pa=index&ar=&ad=177532&buffer=" titl…

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

  • Warning Line 818, Column 68: reference to external entity in attribute value
    ….com/nextdoorebony/go.php?pr=9&su=2&si=51&pa=index&ar=&ad=177532&buffer=" titl…

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

  • Error Line 818, Column 68: reference to entity "si" for which no system identifier could be generated
    ….com/nextdoorebony/go.php?pr=9&su=2&si=51&pa=index&ar=&ad=177532&buffer=" titl…

    This is usually a cascading error caused by 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 690, Column 65: entity was defined here
    …ead.com/menofmontreal/go.php?pr=9&su=2&si=62&pa=index&ar=&ad=177532&buffer=" t…
  • Warning Line 818, Column 74: reference not terminated by REFC delimiter
    …extdoorebony/go.php?pr=9&su=2&si=51&pa=index&ar=&ad=177532&buffer=" title="Nex…

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

  • Warning Line 818, Column 74: reference to external entity in attribute value
    …extdoorebony/go.php?pr=9&su=2&si=51&pa=index&ar=&ad=177532&buffer=" title="Nex…

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

  • Error Line 818, Column 74: reference to entity "pa" for which no system identifier could be generated
    …extdoorebony/go.php?pr=9&su=2&si=51&pa=index&ar=&ad=177532&buffer=" title="Nex…

    This is usually a cascading error caused by 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 690, Column 71: entity was defined here
    …m/menofmontreal/go.php?pr=9&su=2&si=62&pa=index&ar=&ad=177532&buffer=" title="…
  • Warning Line 818, Column 83: reference not terminated by REFC delimiter
    …ony/go.php?pr=9&su=2&si=51&pa=index&ar=&ad=177532&buffer=" title="NextDoorEbon…

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

  • Warning Line 818, Column 83: reference to external entity in attribute value
    …ony/go.php?pr=9&su=2&si=51&pa=index&ar=&ad=177532&buffer=" title="NextDoorEbon…

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

  • Error Line 818, Column 83: reference to entity "ar" for which no system identifier could be generated
    …ony/go.php?pr=9&su=2&si=51&pa=index&ar=&ad=177532&buffer=" title="NextDoorEbon…

    This is usually a cascading error caused by 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 690, Column 80: entity was defined here
    …ntreal/go.php?pr=9&su=2&si=62&pa=index&ar=&ad=177532&buffer=" title="MenOfMont…
  • Warning Line 818, Column 87: reference not terminated by REFC delimiter
    …go.php?pr=9&su=2&si=51&pa=index&ar=&ad=177532&buffer=" title="NextDoorEbony" t…

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

  • Warning Line 818, Column 87: reference to external entity in attribute value
    …go.php?pr=9&su=2&si=51&pa=index&ar=&ad=177532&buffer=" title="NextDoorEbony" t…

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

  • Error Line 818, Column 87: reference to entity "ad" for which no system identifier could be generated
    …go.php?pr=9&su=2&si=51&pa=index&ar=&ad=177532&buffer=" title="NextDoorEbony" t…

    This is usually a cascading error caused by 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 690, Column 84: entity was defined here
    …al/go.php?pr=9&su=2&si=62&pa=index&ar=&ad=177532&buffer=" title="MenOfMontreal…
  • Warning Line 818, Column 101: reference not terminated by REFC delimiter
    …=2&si=51&pa=index&ar=&ad=177532&buffer=" title="NextDoorEbony" target="_blank"…

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

  • Warning Line 818, Column 101: reference to external entity in attribute value
    …=2&si=51&pa=index&ar=&ad=177532&buffer=" title="NextDoorEbony" target="_blank"…

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

  • Error Line 818, Column 101: reference to entity "buffer" for which no system identifier could be generated
    …=2&si=51&pa=index&ar=&ad=177532&buffer=" title="NextDoorEbony" target="_blank"…

    This is usually a cascading error caused by 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 690, Column 94: entity was defined here
    …pr=9&su=2&si=62&pa=index&ar=&ad=177532&buffer=" title="MenOfMontreal.com" targ…
  • Error Line 818, Column 324: end tag for element "A" which is not open
    …="0" width="160" height="505" class="alignnone size-full wp-image-48084" /></A>

    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 819, 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 819, Column 1: start tag was here
    <br><br>
  • Error Line 819, 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 819, Column 5: start tag was here
    <br><br>
  • Error Line 820, Column 77: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ree/TourVerified/?WMID=207048" target=_blank><img src="http://fleshandskin.com…
  • Error Line 820, Column 83: document type does not allow element "a" here; missing one of "object", "span", "bdo", "applet", "iframe", "tt", "i", "b", "u", "s", "strike", "big", "small", "font", "em", "strong", "dfn", "code", "q", "samp", "kbd", "var", "cite", "abbr", "acronym", "sub", "sup", "label", "ins", "del" start-tag
    …urVerified/?WMID=207048" target=_blank><img src="http://fleshandskin.com/wp-co…

    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 821, 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 821, Column 1: start tag was here
    <br><br>
  • Error Line 821, 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 821, Column 5: start tag was here
    <br><br>
  • Error Line 822, Column 111: document type does not allow element "a" here; missing one of "object", "span", "bdo", "applet", "iframe", "tt", "i", "b", "u", "s", "strike", "big", "small", "font", "em", "strong", "dfn", "code", "q", "samp", "kbd", "var", "cite", "abbr", "acronym", "sub", "sup", "label", "ins", "del" start-tag
    …A" title="FraternityX" target="_blank"><img src="http://bonermag.com/wp-conten…

    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 823, Column 6: end tag for "a" 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 818, Column 1: start tag was here
    <a href="http://www.buddylead.com/nextdoorebony/go.php?pr=9&su=2&si=51&pa=index…
  • Error Line 1016, Column 81: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …xblogs.com/cgi-bin/links/in.cgi?id=2532" target=_blank>Planet Sexblogs</a></li>
  • Error Line 1028, Column 48: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <li><a href="http://nakedmenlinks.com/" target=_blank>Naked Men Links</a></li>
  • Error Line 1030, Column 44: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <li><a href="http://hunkhunter.com" target=_blank>Hunk Hunter</a></li>
  • Error Line 1035, Column 43: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <li><a href="http://www.arucci.nl" target=_blank>Arucci</a></li>
  • Error Line 1040, Column 46: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <li><a href="http://manpics2000.com/" target=_blank>ManPics</a></li>
  • Error Line 1073, Column 39: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <li><a href="http://smaq.com/" target=_blank>SMaQ</a></li>
  • Error Line 1126, 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 1126, Column 1: start tag was here
    <br>
  • Error Line 1127, Column 90: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …e="Gay Blogs - People Like Us" target=_blank><img src="http://www.plublogs.com…
  • Error Line 1128, 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 1128, Column 1: start tag was here
    <br>
  • Error Line 1130, 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 1130, Column 1: start tag was here
    <br>
  • Error Line 1131, Column 22: there is no attribute "title"
    &nbsp;&nbsp;<A title="gay porn at Gaydemon" href="http://www.gaydemon.com/" 

    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 1131, Column 50: there is no attribute "href"
    &nbsp;&nbsp;<A title="gay porn at Gaydemon" href="http://www.gaydemon.com/" 

    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 1132, Column 10: there is no attribute "target"
      target=_blank><IMG border=0 alt="Gaydemon's Guide to Gay Porn" 

    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 1132, Column 10: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
      target=_blank><IMG border=0 alt="Gaydemon's Guide to Gay Porn" 
  • Error Line 1132, Column 16: element "A" undefined
      target=_blank><IMG border=0 alt="Gaydemon's Guide to Gay Porn" 

    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 1132, Column 29: there is no attribute "border"
      target=_blank><IMG border=0 alt="Gaydemon's Guide to Gay Porn" 

    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 1132, Column 29: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
      target=_blank><IMG border=0 alt="Gaydemon's Guide to Gay Porn" 
  • Error Line 1132, Column 35: there is no attribute "alt"
      target=_blank><IMG border=0 alt="Gaydemon's Guide to Gay Porn" 

    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 1133, Column 7: there is no attribute "src"
      src="http://www.gaydemon.com/banners/gaydemon.jpg" width=120 height=60></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 1133, Column 60: there is no attribute "width"
      src="http://www.gaydemon.com/banners/gaydemon.jpg" width=120 height=60></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 1133, Column 60: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
      src="http://www.gaydemon.com/banners/gaydemon.jpg" width=120 height=60></A> 
  • Error Line 1133, Column 71: there is no attribute "height"
      src="http://www.gaydemon.com/banners/gaydemon.jpg" width=120 height=60></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 1133, Column 71: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
      src="http://www.gaydemon.com/banners/gaydemon.jpg" width=120 height=60></A> 
  • Error Line 1133, Column 73: element "IMG" undefined
      src="http://www.gaydemon.com/banners/gaydemon.jpg" width=120 height=60></A> 

    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 1133, Column 77: end tag for "IMG" omitted, but OMITTAG NO was specified
      src="http://www.gaydemon.com/banners/gaydemon.jpg" width=120 height=60></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 1132, Column 17: start tag was here
      target=_blank><IMG border=0 alt="Gaydemon's Guide to Gay Porn" 
  • Error Line 1134, 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 1134, Column 1: start tag was here
    <br>
  • Error Line 1137, Column 514: end tag for "br" omitted, but OMITTAG NO was specified
    … condoms and other safe practices.<br>More information about <a href="http://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 1137, Column 510: start tag was here
    …e of condoms and other safe practices.<br>More information about <a href="http…
  • Error Line 1137, Column 596: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …nyurl.com/barebacksexwarninginfo" target=_blank>barebacking and safe sex...</a>
  • Error Line 1138, 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 1138, Column 1: start tag was here
    <br><br>
  • Error Line 1138, 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 1138, Column 5: start tag was here
    <br><br>
  • Warning Line 1139, Column 38: character "&" is the first character of a delimiter but occurred as data
    Some videos or pictures contain BDSM & Fetish themes. These scenes are scripted…

    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 1141, Column 79: end tag for "br" omitted, but OMITTAG NO was specified
    		</div><div class="block text-27 widget_text">			<div class="textwidget"><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 1141, Column 75: start tag was here
    		</div><div class="block text-27 widget_text">			<div class="textwidget"><br>
  • Error Line 1142, Column 263: end tag for element "A" which is not open
    …com" width="160" height="649" class="alignnone size-full wp-image-48030" /></A>

    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 1143, 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 1143, Column 1: start tag was here
    <br><br>
  • Error Line 1143, 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 1143, Column 5: start tag was here
    <br><br>
  • Error Line 1144, Column 121: document type does not allow element "a" here; missing one of "object", "span", "bdo", "applet", "iframe", "tt", "i", "b", "u", "s", "strike", "big", "small", "font", "em", "strong", "dfn", "code", "q", "samp", "kbd", "var", "cite", "abbr", "acronym", "sub", "sup", "label", "ins", "del" start-tag
    …" title="CollegeDudes" target="_blank"><img src="http://fleshandskin.com/wp-co…

    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 1145, 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 1145, Column 1: start tag was here
    <br><br>
  • Error Line 1145, 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 1145, Column 5: start tag was here
    <br><br>
  • Warning Line 1146, Column 68: cannot generate system identifier for general entity "PA"
    …com/cgi-bin/clicks.cgi?CA=917967-0000&PA=1315109" target=_blank><img src="http…

    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 1146, Column 68: general entity "PA" not defined and no default entity
    …com/cgi-bin/clicks.cgi?CA=917967-0000&PA=1315109" target=_blank><img src="http…

    This is usually a cascading error caused by 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 1146, Column 70: reference not terminated by REFC delimiter
    …m/cgi-bin/clicks.cgi?CA=917967-0000&PA=1315109" target=_blank><img src="http:/…

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

  • Warning Line 1146, Column 70: reference to external entity in attribute value
    …m/cgi-bin/clicks.cgi?CA=917967-0000&PA=1315109" target=_blank><img src="http:/…

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

  • Error Line 1146, Column 70: reference to entity "PA" for which no system identifier could be generated
    …m/cgi-bin/clicks.cgi?CA=917967-0000&PA=1315109" target=_blank><img src="http:/…

    This is usually a cascading error caused by 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 1146, Column 67: entity was defined here
    ….com/cgi-bin/clicks.cgi?CA=917967-0000&PA=1315109" target=_blank><img src="htt…
  • Error Line 1146, Column 87: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …cgi?CA=917967-0000&PA=1315109" target=_blank><img src="http://fleshandskin.com…
  • Error Line 1146, Column 93: document type does not allow element "a" here; missing one of "object", "span", "bdo", "applet", "iframe", "tt", "i", "b", "u", "s", "strike", "big", "small", "font", "em", "strong", "dfn", "code", "q", "samp", "kbd", "var", "cite", "abbr", "acronym", "sub", "sup", "label", "ins", "del" start-tag
    …=917967-0000&PA=1315109" target=_blank><img src="http://fleshandskin.com/wp-co…

    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 1146, Column 266: end tag for "a" omitted, but OMITTAG NO was specified
    …idth="160" height="463" class="alignnone size-full wp-image-48032" /></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 1142, Column 1: start tag was here
    <a href="http://enter.men.com/track/MTMzMS4xLjEuMS4wLjAuMC4wLjA" title="Men.com…
  • Error Line 1151, 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 1151, Column 1: start tag was here
    <br><br>
  • Error Line 1151, 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 1151, Column 5: start tag was here
    <br><br>
  • Error Line 1155, Column 135: there is no attribute "allowtransparency"
    …ads?spot_id=175382" allowtransparency="true" marginheight="0" marginwidth="0" …

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

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

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

  • Error Line 1160, 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 1160, Column 1: start tag was here
    <br><br>
  • Error Line 1160, 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 1160, Column 5: start tag was here
    <br><br>
  • Error Line 1163, 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 1163, Column 1: start tag was here
    <br><br>
  • Error Line 1163, 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 1163, Column 5: start tag was here
    <br><br>
  • Error Line 1164, Column 173: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …label.org/" style="text-decoration: none;color:#cccccc;" target=_blank>RTA</a>.
  • Error Line 1165, 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 1165, Column 1: start tag was here
    <br><br>
  • Error Line 1165, 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 1165, Column 5: start tag was here
    <br><br>
  • Error Line 1166, Column 98: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …coration: none;color:#cccccc;" target=_blank>Click here to block this website<…
  • Error Line 1166, Column 147: end tag for element "font" which is not open
    …_blank>Click here to block this website</a></font> with free parental controls.

    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 1167, 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 1167, Column 1: start tag was here
    <br><br>
  • Error Line 1167, 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 1167, Column 5: start tag was here
    <br><br>
  • Error Line 1169, Column 26: end tag for element "p" which is not open
    	| All Rights Reserved</p></div></font>

    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 1169, Column 39: end tag for element "font" which is not open
    	| All Rights Reserved</p></div></font>

    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 1176, 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 1179, Column 50: required attribute "type" not specified
    <script src="http://www.linkwithin.com/widget.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>.

Visitor Analysis

Daily Visitor
  • 887 visits

In Page Analysis