ATENCION: Este sitio web contiene material explicito que solo puede ser visto por personas adultas! Si este tipo de material es ofensivo para ti o si te encuentras en un pais donde este ...

solovenezolanas.com
  • Domain Name
    solovenezolanas.com
  • Favicon
  • Google Page Rank
    2
  • Alexa Rank
    #47410
  • Page Size
    7.2 KB
  • Ip Address
    108.162.199.80
  • Heading
    H1: 0, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    0 GIF, 4 JPG, 0 PNG

Website Meta Analysis

  • Title
    Warning - Adults Only - 18 and Up
  • Meta Keyword
  • Meta Description
    ATENCION: Este sitio web contiene material explicito que solo puede ser visto por personas adultas! Si este tipo de material es ofensivo para ti o si te encuentras en un pais donde este material no puede ser visto ABANDONA EL SITIO! 1. 2. 3. ...

Technical Analysis

  • Webserver
    cloudflare-nginx
  • Ip Address
    108.162.199.80
  • Domain Age
    4 Years, 11 Months, 2 days.
  • Javascript Library
    jquery, dojo
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • server: cloudflare-nginx
  • date: Fri, 04 Oct 2013 22:56:01 GMT
  • content-type: text/html; charset=UTF-8
  • connection: keep-alive
  • last-modified: Sun, 16 Jun 2013 03:17:23 GMT
  • x-powered-by: PleskLin
  • cf-ray: b857685c52d02ba
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for solovenezolanas.com

DNS Analysis


DNS servers
jack.ns.cloudflare.com [173.245.59.121]
kay.ns.cloudflare.com [173.245.58.125]


DNS Records

Answer records
solovenezolanas.com MX
preference: 0
exchange: smtp.secureserver.net
300s
solovenezolanas.com A 108.162.198.80 300s
solovenezolanas.com A 108.162.199.80 300s
solovenezolanas.com MX
preference: 10
exchange: mailstore1.secureserver.net
300s
solovenezolanas.com NS  kay.ns.cloudflare.com 86400s
solovenezolanas.com NS  jack.ns.cloudflare.com 86400s
solovenezolanas.com SOA
server: jack.ns.cloudflare.com
email: dns@cloudflare.com
serial: 2012101919
refresh: 10000
retry: 2400
expire: 604800
minimum ttl: 3600
86400s

Authority records

Additional records

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 37 Errors
  • 167 Warnings
Ratio Text/Html
  • 0.46458304899686087
Message Error
  • Error Line 186, Column 30: required attribute "type" not specified
    <script language="JavaScript">

    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 219, Column 70: required attribute "type" not specified
    <script language="JavaScript" src="http://x6.xclicks.net/js/x7174.js"></script>

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

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

  • Error Line 220, Column 30: required attribute "type" not specified
    <script language="JavaScript">

    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 227, Column 9: end tag for element "SCRIPT" which is not open
    </SCRIPT>

    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 228, Column 80: document type does not allow element "meta" here
    <meta name="verify-v1" content="1FbHlKKeyCB8kmj2DHvPGyY7oXUgrI5DMnG7T0nQIOk=" />

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

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

  • Error Line 230, Column 7: end tag for "script" omitted, but OMITTAG NO was specified
    </head>

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

  • Info Line 220, Column 1: start tag was here
    <script language="JavaScript">
  • Error Line 241, Column 10: there is no attribute "ALIGN"
    <P ALIGN=left>

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

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

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

  • Error Line 241, Column 10: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <P ALIGN=left>
  • Error Line 241, Column 14: element "P" undefined
    <P ALIGN=left>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 244, Column 76: there is no attribute "data-count"
    …ass="twitter-share-button" data-count="vertical">Tweet</a><script type="text/j…

    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 248, Column 17: there is no attribute "size"
    <g:plusone size="tall"></g:plusone>

    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 248, Column 23: element "g:plusone" undefined
    <g:plusone size="tall"></g:plusone>

    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 264, Column 16: there is no attribute "hspace"
    <iframe hspace=0 vspace=0 border=0 frameborder=0 marginheight=0 marginwidth=0 w…

    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 264, Column 16: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <iframe hspace=0 vspace=0 border=0 frameborder=0 marginheight=0 marginwidth=0 w…
  • Error Line 264, Column 25: there is no attribute "vspace"
    <iframe hspace=0 vspace=0 border=0 frameborder=0 marginheight=0 marginwidth=0 w…

    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 264, Column 25: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <iframe hspace=0 vspace=0 border=0 frameborder=0 marginheight=0 marginwidth=0 w…
  • Error Line 264, Column 34: there is no attribute "border"
    <iframe hspace=0 vspace=0 border=0 frameborder=0 marginheight=0 marginwidth=0 w…

    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 264, Column 34: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <iframe hspace=0 vspace=0 border=0 frameborder=0 marginheight=0 marginwidth=0 w…
  • Error Line 264, Column 48: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …space=0 vspace=0 border=0 frameborder=0 marginheight=0 marginwidth=0 width=736…
  • Error Line 264, Column 63: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …0 border=0 frameborder=0 marginheight=0 marginwidth=0 width=736 height=110 scr…
  • Error Line 264, Column 77: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …meborder=0 marginheight=0 marginwidth=0 width=736 height=110 scrolling=no allo…
  • Error Line 264, Column 85: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …=0 marginheight=0 marginwidth=0 width=736 height=110 scrolling=no allowtranspa…
  • Error Line 264, Column 96: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ight=0 marginwidth=0 width=736 height=110 scrolling=no allowtransparency=true …
  • Error Line 264, Column 110: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …idth=0 width=736 height=110 scrolling=no allowtransparency=true src=http://ads…
  • Error Line 264, Column 131: there is no attribute "allowtransparency"
    …ht=110 scrolling=no allowtransparency=true src=http://adserver.juicyads.com/ad…

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

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

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

  • Error Line 264, Column 131: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ht=110 scrolling=no allowtransparency=true src=http://adserver.juicyads.com/ad…
  • Error Line 264, Column 140: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …rolling=no allowtransparency=true src=http://adserver.juicyads.com/adshow.php?…
  • Error Line 264, Column 146: NET-enabling start-tag not immediately followed by null end-tag
    …g=no allowtransparency=true src=http://adserver.juicyads.com/adshow.php?adzone…

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

  • Error Line 264, Column 201: end tag for element "iframe" which is not open
    …parency=true src=http://adserver.juicyads.com/adshow.php?adzone=11315></iframe>

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

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

  • Error Line 300, Column 56: duplicate specification of attribute "value"
    …" value="Search the archive..." value="" name="s" id="s" onfocus="this.value='…

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Warning Line 355, Column 160: cannot generate system identifier for general entity "w"
    …ent/uploads/2012/06/vlcsnap-2012-06-11-13h47m20s104.png&w=125&h=125&zc=1&q=100"

    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 355, Column 160: general entity "w" not defined and no default entity
    …ent/uploads/2012/06/vlcsnap-2012-06-11-13h47m20s104.png&w=125&h=125&zc=1&q=100"

    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 355, Column 161: reference not terminated by REFC delimiter
    …ent/uploads/2012/06/vlcsnap-2012-06-11-13h47m20s104.png&w=125&h=125&zc=1&q=100"

    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 355, Column 161: reference to external entity in attribute value
    …ent/uploads/2012/06/vlcsnap-2012-06-11-13h47m20s104.png&w=125&h=125&zc=1&q=100"

    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 355, Column 161: reference to entity "w" for which no system identifier could be generated
    …ent/uploads/2012/06/vlcsnap-2012-06-11-13h47m20s104.png&w=125&h=125&zc=1&q=100"

    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 355, Column 159: entity was defined here
    …ent/uploads/2012/06/vlcsnap-2012-06-11-13h47m20s104.png&w=125&h=125&zc=1&q=100"
  • Warning Line 355, Column 166: cannot generate system identifier for general entity "h"
    …ent/uploads/2012/06/vlcsnap-2012-06-11-13h47m20s104.png&w=125&h=125&zc=1&q=100"

    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 355, Column 166: general entity "h" not defined and no default entity
    …ent/uploads/2012/06/vlcsnap-2012-06-11-13h47m20s104.png&w=125&h=125&zc=1&q=100"

    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 355, Column 167: reference not terminated by REFC delimiter
    …ent/uploads/2012/06/vlcsnap-2012-06-11-13h47m20s104.png&w=125&h=125&zc=1&q=100"

    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 355, Column 167: reference to external entity in attribute value
    …ent/uploads/2012/06/vlcsnap-2012-06-11-13h47m20s104.png&w=125&h=125&zc=1&q=100"

    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 355, Column 167: reference to entity "h" for which no system identifier could be generated
    …ent/uploads/2012/06/vlcsnap-2012-06-11-13h47m20s104.png&w=125&h=125&zc=1&q=100"

    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 355, Column 165: entity was defined here
    …ent/uploads/2012/06/vlcsnap-2012-06-11-13h47m20s104.png&w=125&h=125&zc=1&q=100"
  • Warning Line 355, Column 172: cannot generate system identifier for general entity "zc"
    …ent/uploads/2012/06/vlcsnap-2012-06-11-13h47m20s104.png&w=125&h=125&zc=1&q=100"

    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 355, Column 172: general entity "zc" not defined and no default entity
    …ent/uploads/2012/06/vlcsnap-2012-06-11-13h47m20s104.png&w=125&h=125&zc=1&q=100"

    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 355, Column 174: reference not terminated by REFC delimiter
    …ent/uploads/2012/06/vlcsnap-2012-06-11-13h47m20s104.png&w=125&h=125&zc=1&q=100"

    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 355, Column 174: reference to external entity in attribute value
    …ent/uploads/2012/06/vlcsnap-2012-06-11-13h47m20s104.png&w=125&h=125&zc=1&q=100"

    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 355, Column 174: reference to entity "zc" for which no system identifier could be generated
    …ent/uploads/2012/06/vlcsnap-2012-06-11-13h47m20s104.png&w=125&h=125&zc=1&q=100"

    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 355, Column 171: entity was defined here
    …ent/uploads/2012/06/vlcsnap-2012-06-11-13h47m20s104.png&w=125&h=125&zc=1&q=100"
  • Warning Line 355, Column 177: cannot generate system identifier for general entity "q"
    …ent/uploads/2012/06/vlcsnap-2012-06-11-13h47m20s104.png&w=125&h=125&zc=1&q=100"

    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 355, Column 177: general entity "q" not defined and no default entity
    …ent/uploads/2012/06/vlcsnap-2012-06-11-13h47m20s104.png&w=125&h=125&zc=1&q=100"

    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 355, Column 178: reference not terminated by REFC delimiter
    …ent/uploads/2012/06/vlcsnap-2012-06-11-13h47m20s104.png&w=125&h=125&zc=1&q=100"

    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 355, Column 178: reference to external entity in attribute value
    …ent/uploads/2012/06/vlcsnap-2012-06-11-13h47m20s104.png&w=125&h=125&zc=1&q=100"

    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 355, Column 178: reference to entity "q" for which no system identifier could be generated
    …ent/uploads/2012/06/vlcsnap-2012-06-11-13h47m20s104.png&w=125&h=125&zc=1&q=100"

    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 355, Column 176: entity was defined here
    …ent/uploads/2012/06/vlcsnap-2012-06-11-13h47m20s104.png&w=125&h=125&zc=1&q=100"
  • Warning Line 365, Column 161: reference not terminated by REFC delimiter
    …ent/uploads/2009/09/vlcsnap-2009-09-01-13h47m16s227.jpg&w=125&h=125&zc=1&q=100"

    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 365, Column 161: reference to external entity in attribute value
    …ent/uploads/2009/09/vlcsnap-2009-09-01-13h47m16s227.jpg&w=125&h=125&zc=1&q=100"

    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 365, Column 161: reference to entity "w" for which no system identifier could be generated
    …ent/uploads/2009/09/vlcsnap-2009-09-01-13h47m16s227.jpg&w=125&h=125&zc=1&q=100"

    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 355, Column 159: entity was defined here
    …ent/uploads/2012/06/vlcsnap-2012-06-11-13h47m20s104.png&w=125&h=125&zc=1&q=100"
  • Warning Line 365, Column 167: reference not terminated by REFC delimiter
    …ent/uploads/2009/09/vlcsnap-2009-09-01-13h47m16s227.jpg&w=125&h=125&zc=1&q=100"

    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 365, Column 167: reference to external entity in attribute value
    …ent/uploads/2009/09/vlcsnap-2009-09-01-13h47m16s227.jpg&w=125&h=125&zc=1&q=100"

    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 365, Column 167: reference to entity "h" for which no system identifier could be generated
    …ent/uploads/2009/09/vlcsnap-2009-09-01-13h47m16s227.jpg&w=125&h=125&zc=1&q=100"

    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 355, Column 165: entity was defined here
    …ent/uploads/2012/06/vlcsnap-2012-06-11-13h47m20s104.png&w=125&h=125&zc=1&q=100"
  • Warning Line 365, Column 174: reference not terminated by REFC delimiter
    …ent/uploads/2009/09/vlcsnap-2009-09-01-13h47m16s227.jpg&w=125&h=125&zc=1&q=100"

    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 365, Column 174: reference to external entity in attribute value
    …ent/uploads/2009/09/vlcsnap-2009-09-01-13h47m16s227.jpg&w=125&h=125&zc=1&q=100"

    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 365, Column 174: reference to entity "zc" for which no system identifier could be generated
    …ent/uploads/2009/09/vlcsnap-2009-09-01-13h47m16s227.jpg&w=125&h=125&zc=1&q=100"

    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 355, Column 171: entity was defined here
    …ent/uploads/2012/06/vlcsnap-2012-06-11-13h47m20s104.png&w=125&h=125&zc=1&q=100"
  • Warning Line 365, Column 178: reference not terminated by REFC delimiter
    …ent/uploads/2009/09/vlcsnap-2009-09-01-13h47m16s227.jpg&w=125&h=125&zc=1&q=100"

    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 365, Column 178: reference to external entity in attribute value
    …ent/uploads/2009/09/vlcsnap-2009-09-01-13h47m16s227.jpg&w=125&h=125&zc=1&q=100"

    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 365, Column 178: reference to entity "q" for which no system identifier could be generated
    …ent/uploads/2009/09/vlcsnap-2009-09-01-13h47m16s227.jpg&w=125&h=125&zc=1&q=100"

    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 355, Column 176: entity was defined here
    …ent/uploads/2012/06/vlcsnap-2012-06-11-13h47m20s104.png&w=125&h=125&zc=1&q=100"
  • Warning Line 375, Column 134: reference not terminated by REFC delimiter
    …/timthumb.php?src=//wp-content/uploads/2009/03/1-28.jpg&w=125&h=125&zc=1&q=100"

    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 375, Column 134: reference to external entity in attribute value
    …/timthumb.php?src=//wp-content/uploads/2009/03/1-28.jpg&w=125&h=125&zc=1&q=100"

    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 375, Column 134: reference to entity "w" for which no system identifier could be generated
    …/timthumb.php?src=//wp-content/uploads/2009/03/1-28.jpg&w=125&h=125&zc=1&q=100"

    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 355, Column 159: entity was defined here
    …ent/uploads/2012/06/vlcsnap-2012-06-11-13h47m20s104.png&w=125&h=125&zc=1&q=100"
  • Warning Line 375, Column 140: reference not terminated by REFC delimiter
    …/timthumb.php?src=//wp-content/uploads/2009/03/1-28.jpg&w=125&h=125&zc=1&q=100"

    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 375, Column 140: reference to external entity in attribute value
    …/timthumb.php?src=//wp-content/uploads/2009/03/1-28.jpg&w=125&h=125&zc=1&q=100"

    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 375, Column 140: reference to entity "h" for which no system identifier could be generated
    …/timthumb.php?src=//wp-content/uploads/2009/03/1-28.jpg&w=125&h=125&zc=1&q=100"

    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 355, Column 165: entity was defined here
    …ent/uploads/2012/06/vlcsnap-2012-06-11-13h47m20s104.png&w=125&h=125&zc=1&q=100"
  • Warning Line 375, Column 147: reference not terminated by REFC delimiter
    …/timthumb.php?src=//wp-content/uploads/2009/03/1-28.jpg&w=125&h=125&zc=1&q=100"

    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 375, Column 147: reference to external entity in attribute value
    …/timthumb.php?src=//wp-content/uploads/2009/03/1-28.jpg&w=125&h=125&zc=1&q=100"

    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 375, Column 147: reference to entity "zc" for which no system identifier could be generated
    …/timthumb.php?src=//wp-content/uploads/2009/03/1-28.jpg&w=125&h=125&zc=1&q=100"

    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 355, Column 171: entity was defined here
    …ent/uploads/2012/06/vlcsnap-2012-06-11-13h47m20s104.png&w=125&h=125&zc=1&q=100"
  • Warning Line 375, Column 151: reference not terminated by REFC delimiter
    …/timthumb.php?src=//wp-content/uploads/2009/03/1-28.jpg&w=125&h=125&zc=1&q=100"

    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 375, Column 151: reference to external entity in attribute value
    …/timthumb.php?src=//wp-content/uploads/2009/03/1-28.jpg&w=125&h=125&zc=1&q=100"

    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 375, Column 151: reference to entity "q" for which no system identifier could be generated
    …/timthumb.php?src=//wp-content/uploads/2009/03/1-28.jpg&w=125&h=125&zc=1&q=100"

    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 355, Column 176: entity was defined here
    …ent/uploads/2012/06/vlcsnap-2012-06-11-13h47m20s104.png&w=125&h=125&zc=1&q=100"
  • Warning Line 385, Column 160: reference not terminated by REFC delimiter
    …tent/uploads/2012/01/vlcsnap-2012-01-09-16h46m45s68.png&w=125&h=125&zc=1&q=100"

    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 385, Column 160: reference to external entity in attribute value
    …tent/uploads/2012/01/vlcsnap-2012-01-09-16h46m45s68.png&w=125&h=125&zc=1&q=100"

    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 385, Column 160: reference to entity "w" for which no system identifier could be generated
    …tent/uploads/2012/01/vlcsnap-2012-01-09-16h46m45s68.png&w=125&h=125&zc=1&q=100"

    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 355, Column 159: entity was defined here
    …ent/uploads/2012/06/vlcsnap-2012-06-11-13h47m20s104.png&w=125&h=125&zc=1&q=100"
  • Warning Line 385, Column 166: reference not terminated by REFC delimiter
    …tent/uploads/2012/01/vlcsnap-2012-01-09-16h46m45s68.png&w=125&h=125&zc=1&q=100"

    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 385, Column 166: reference to external entity in attribute value
    …tent/uploads/2012/01/vlcsnap-2012-01-09-16h46m45s68.png&w=125&h=125&zc=1&q=100"

    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 385, Column 166: reference to entity "h" for which no system identifier could be generated
    …tent/uploads/2012/01/vlcsnap-2012-01-09-16h46m45s68.png&w=125&h=125&zc=1&q=100"

    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 355, Column 165: entity was defined here
    …ent/uploads/2012/06/vlcsnap-2012-06-11-13h47m20s104.png&w=125&h=125&zc=1&q=100"
  • Warning Line 385, Column 173: reference not terminated by REFC delimiter
    …tent/uploads/2012/01/vlcsnap-2012-01-09-16h46m45s68.png&w=125&h=125&zc=1&q=100"

    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 385, Column 173: reference to external entity in attribute value
    …tent/uploads/2012/01/vlcsnap-2012-01-09-16h46m45s68.png&w=125&h=125&zc=1&q=100"

    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 385, Column 173: reference to entity "zc" for which no system identifier could be generated
    …tent/uploads/2012/01/vlcsnap-2012-01-09-16h46m45s68.png&w=125&h=125&zc=1&q=100"

    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 355, Column 171: entity was defined here
    …ent/uploads/2012/06/vlcsnap-2012-06-11-13h47m20s104.png&w=125&h=125&zc=1&q=100"
  • Warning Line 385, Column 177: reference not terminated by REFC delimiter
    …tent/uploads/2012/01/vlcsnap-2012-01-09-16h46m45s68.png&w=125&h=125&zc=1&q=100"

    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 385, Column 177: reference to external entity in attribute value
    …tent/uploads/2012/01/vlcsnap-2012-01-09-16h46m45s68.png&w=125&h=125&zc=1&q=100"

    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 385, Column 177: reference to entity "q" for which no system identifier could be generated
    …tent/uploads/2012/01/vlcsnap-2012-01-09-16h46m45s68.png&w=125&h=125&zc=1&q=100"

    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 355, Column 176: entity was defined here
    …ent/uploads/2012/06/vlcsnap-2012-06-11-13h47m20s104.png&w=125&h=125&zc=1&q=100"
  • Warning Line 414, Column 161: reference not terminated by REFC delimiter
    …ent/uploads/2012/10/vlcsnap-2012-10-04-17h36m06s242.png&w=150&h=150&zc=1&q=100"

    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 414, Column 161: reference to external entity in attribute value
    …ent/uploads/2012/10/vlcsnap-2012-10-04-17h36m06s242.png&w=150&h=150&zc=1&q=100"

    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 414, Column 161: reference to entity "w" for which no system identifier could be generated
    …ent/uploads/2012/10/vlcsnap-2012-10-04-17h36m06s242.png&w=150&h=150&zc=1&q=100"

    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 355, Column 159: entity was defined here
    …ent/uploads/2012/06/vlcsnap-2012-06-11-13h47m20s104.png&w=125&h=125&zc=1&q=100"
  • Warning Line 414, Column 167: reference not terminated by REFC delimiter
    …ent/uploads/2012/10/vlcsnap-2012-10-04-17h36m06s242.png&w=150&h=150&zc=1&q=100"

    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 414, Column 167: reference to external entity in attribute value
    …ent/uploads/2012/10/vlcsnap-2012-10-04-17h36m06s242.png&w=150&h=150&zc=1&q=100"

    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 414, Column 167: reference to entity "h" for which no system identifier could be generated
    …ent/uploads/2012/10/vlcsnap-2012-10-04-17h36m06s242.png&w=150&h=150&zc=1&q=100"

    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 355, Column 165: entity was defined here
    …ent/uploads/2012/06/vlcsnap-2012-06-11-13h47m20s104.png&w=125&h=125&zc=1&q=100"
  • Warning Line 414, Column 174: reference not terminated by REFC delimiter
    …ent/uploads/2012/10/vlcsnap-2012-10-04-17h36m06s242.png&w=150&h=150&zc=1&q=100"

    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 414, Column 174: reference to external entity in attribute value
    …ent/uploads/2012/10/vlcsnap-2012-10-04-17h36m06s242.png&w=150&h=150&zc=1&q=100"

    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 414, Column 174: reference to entity "zc" for which no system identifier could be generated
    …ent/uploads/2012/10/vlcsnap-2012-10-04-17h36m06s242.png&w=150&h=150&zc=1&q=100"

    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 355, Column 171: entity was defined here
    …ent/uploads/2012/06/vlcsnap-2012-06-11-13h47m20s104.png&w=125&h=125&zc=1&q=100"
  • Warning Line 414, Column 178: reference not terminated by REFC delimiter
    …ent/uploads/2012/10/vlcsnap-2012-10-04-17h36m06s242.png&w=150&h=150&zc=1&q=100"

    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 414, Column 178: reference to external entity in attribute value
    …ent/uploads/2012/10/vlcsnap-2012-10-04-17h36m06s242.png&w=150&h=150&zc=1&q=100"

    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 414, Column 178: reference to entity "q" for which no system identifier could be generated
    …ent/uploads/2012/10/vlcsnap-2012-10-04-17h36m06s242.png&w=150&h=150&zc=1&q=100"

    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 355, Column 176: entity was defined here
    …ent/uploads/2012/06/vlcsnap-2012-06-11-13h47m20s104.png&w=125&h=125&zc=1&q=100"
  • Warning Line 432, Column 152: reference not terminated by REFC delimiter
    …//wp-content/uploads/2012/10/IMG00884-20120108-1435.jpg&w=150&h=150&zc=1&q=100"

    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 432, Column 152: reference to external entity in attribute value
    …//wp-content/uploads/2012/10/IMG00884-20120108-1435.jpg&w=150&h=150&zc=1&q=100"

    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 432, Column 152: reference to entity "w" for which no system identifier could be generated
    …//wp-content/uploads/2012/10/IMG00884-20120108-1435.jpg&w=150&h=150&zc=1&q=100"

    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 355, Column 159: entity was defined here
    …ent/uploads/2012/06/vlcsnap-2012-06-11-13h47m20s104.png&w=125&h=125&zc=1&q=100"
  • Warning Line 432, Column 158: reference not terminated by REFC delimiter
    …//wp-content/uploads/2012/10/IMG00884-20120108-1435.jpg&w=150&h=150&zc=1&q=100"

    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 432, Column 158: reference to external entity in attribute value
    …//wp-content/uploads/2012/10/IMG00884-20120108-1435.jpg&w=150&h=150&zc=1&q=100"

    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 432, Column 158: reference to entity "h" for which no system identifier could be generated
    …//wp-content/uploads/2012/10/IMG00884-20120108-1435.jpg&w=150&h=150&zc=1&q=100"

    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 355, Column 165: entity was defined here
    …ent/uploads/2012/06/vlcsnap-2012-06-11-13h47m20s104.png&w=125&h=125&zc=1&q=100"
  • Warning Line 432, Column 165: reference not terminated by REFC delimiter
    …//wp-content/uploads/2012/10/IMG00884-20120108-1435.jpg&w=150&h=150&zc=1&q=100"

    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 432, Column 165: reference to external entity in attribute value
    …//wp-content/uploads/2012/10/IMG00884-20120108-1435.jpg&w=150&h=150&zc=1&q=100"

    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 432, Column 165: reference to entity "zc" for which no system identifier could be generated
    …//wp-content/uploads/2012/10/IMG00884-20120108-1435.jpg&w=150&h=150&zc=1&q=100"

    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 355, Column 171: entity was defined here
    …ent/uploads/2012/06/vlcsnap-2012-06-11-13h47m20s104.png&w=125&h=125&zc=1&q=100"
  • Warning Line 432, Column 169: reference not terminated by REFC delimiter
    …//wp-content/uploads/2012/10/IMG00884-20120108-1435.jpg&w=150&h=150&zc=1&q=100"

    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 432, Column 169: reference to external entity in attribute value
    …//wp-content/uploads/2012/10/IMG00884-20120108-1435.jpg&w=150&h=150&zc=1&q=100"

    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 432, Column 169: reference to entity "q" for which no system identifier could be generated
    …//wp-content/uploads/2012/10/IMG00884-20120108-1435.jpg&w=150&h=150&zc=1&q=100"

    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 355, Column 176: entity was defined here
    …ent/uploads/2012/06/vlcsnap-2012-06-11-13h47m20s104.png&w=125&h=125&zc=1&q=100"
  • Warning Line 450, Column 148: reference not terminated by REFC delimiter
    …src=//wp-content/uploads/2012/10/IMG-20120627-00193.jpg&w=150&h=150&zc=1&q=100"

    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 450, Column 148: reference to external entity in attribute value
    …src=//wp-content/uploads/2012/10/IMG-20120627-00193.jpg&w=150&h=150&zc=1&q=100"

    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 450, Column 148: reference to entity "w" for which no system identifier could be generated
    …src=//wp-content/uploads/2012/10/IMG-20120627-00193.jpg&w=150&h=150&zc=1&q=100"

    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 355, Column 159: entity was defined here
    …ent/uploads/2012/06/vlcsnap-2012-06-11-13h47m20s104.png&w=125&h=125&zc=1&q=100"
  • Warning Line 450, Column 154: reference not terminated by REFC delimiter
    …src=//wp-content/uploads/2012/10/IMG-20120627-00193.jpg&w=150&h=150&zc=1&q=100"

    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 450, Column 154: reference to external entity in attribute value
    …src=//wp-content/uploads/2012/10/IMG-20120627-00193.jpg&w=150&h=150&zc=1&q=100"

    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 450, Column 154: reference to entity "h" for which no system identifier could be generated
    …src=//wp-content/uploads/2012/10/IMG-20120627-00193.jpg&w=150&h=150&zc=1&q=100"

    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 355, Column 165: entity was defined here
    …ent/uploads/2012/06/vlcsnap-2012-06-11-13h47m20s104.png&w=125&h=125&zc=1&q=100"
  • Warning Line 450, Column 161: reference not terminated by REFC delimiter
    …src=//wp-content/uploads/2012/10/IMG-20120627-00193.jpg&w=150&h=150&zc=1&q=100"

    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 450, Column 161: reference to external entity in attribute value
    …src=//wp-content/uploads/2012/10/IMG-20120627-00193.jpg&w=150&h=150&zc=1&q=100"

    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 450, Column 161: reference to entity "zc" for which no system identifier could be generated
    …src=//wp-content/uploads/2012/10/IMG-20120627-00193.jpg&w=150&h=150&zc=1&q=100"

    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 355, Column 171: entity was defined here
    …ent/uploads/2012/06/vlcsnap-2012-06-11-13h47m20s104.png&w=125&h=125&zc=1&q=100"
  • Warning Line 450, Column 165: reference not terminated by REFC delimiter
    …src=//wp-content/uploads/2012/10/IMG-20120627-00193.jpg&w=150&h=150&zc=1&q=100"

    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 450, Column 165: reference to external entity in attribute value
    …src=//wp-content/uploads/2012/10/IMG-20120627-00193.jpg&w=150&h=150&zc=1&q=100"

    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 450, Column 165: reference to entity "q" for which no system identifier could be generated
    …src=//wp-content/uploads/2012/10/IMG-20120627-00193.jpg&w=150&h=150&zc=1&q=100"

    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 355, Column 176: entity was defined here
    …ent/uploads/2012/06/vlcsnap-2012-06-11-13h47m20s104.png&w=125&h=125&zc=1&q=100"
  • Warning Line 468, Column 161: reference not terminated by REFC delimiter
    …ent/uploads/2012/10/vlcsnap-2012-10-04-17h30m57s207.png&w=150&h=150&zc=1&q=100"

    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 468, Column 161: reference to external entity in attribute value
    …ent/uploads/2012/10/vlcsnap-2012-10-04-17h30m57s207.png&w=150&h=150&zc=1&q=100"

    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 468, Column 161: reference to entity "w" for which no system identifier could be generated
    …ent/uploads/2012/10/vlcsnap-2012-10-04-17h30m57s207.png&w=150&h=150&zc=1&q=100"

    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 355, Column 159: entity was defined here
    …ent/uploads/2012/06/vlcsnap-2012-06-11-13h47m20s104.png&w=125&h=125&zc=1&q=100"
  • Warning Line 468, Column 167: reference not terminated by REFC delimiter
    …ent/uploads/2012/10/vlcsnap-2012-10-04-17h30m57s207.png&w=150&h=150&zc=1&q=100"

    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 468, Column 167: reference to external entity in attribute value
    …ent/uploads/2012/10/vlcsnap-2012-10-04-17h30m57s207.png&w=150&h=150&zc=1&q=100"

    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 468, Column 167: reference to entity "h" for which no system identifier could be generated
    …ent/uploads/2012/10/vlcsnap-2012-10-04-17h30m57s207.png&w=150&h=150&zc=1&q=100"

    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 355, Column 165: entity was defined here
    …ent/uploads/2012/06/vlcsnap-2012-06-11-13h47m20s104.png&w=125&h=125&zc=1&q=100"
  • Warning Line 468, Column 174: reference not terminated by REFC delimiter
    …ent/uploads/2012/10/vlcsnap-2012-10-04-17h30m57s207.png&w=150&h=150&zc=1&q=100"

    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 468, Column 174: reference to external entity in attribute value
    …ent/uploads/2012/10/vlcsnap-2012-10-04-17h30m57s207.png&w=150&h=150&zc=1&q=100"

    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 468, Column 174: reference to entity "zc" for which no system identifier could be generated
    …ent/uploads/2012/10/vlcsnap-2012-10-04-17h30m57s207.png&w=150&h=150&zc=1&q=100"

    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 355, Column 171: entity was defined here
    …ent/uploads/2012/06/vlcsnap-2012-06-11-13h47m20s104.png&w=125&h=125&zc=1&q=100"
  • Warning Line 468, Column 178: reference not terminated by REFC delimiter
    …ent/uploads/2012/10/vlcsnap-2012-10-04-17h30m57s207.png&w=150&h=150&zc=1&q=100"

    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 468, Column 178: reference to external entity in attribute value
    …ent/uploads/2012/10/vlcsnap-2012-10-04-17h30m57s207.png&w=150&h=150&zc=1&q=100"

    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 468, Column 178: reference to entity "q" for which no system identifier could be generated
    …ent/uploads/2012/10/vlcsnap-2012-10-04-17h30m57s207.png&w=150&h=150&zc=1&q=100"

    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 355, Column 176: entity was defined here
    …ent/uploads/2012/06/vlcsnap-2012-06-11-13h47m20s104.png&w=125&h=125&zc=1&q=100"
  • Warning Line 486, Column 138: reference not terminated by REFC delimiter
    …thumb.php?src=//wp-content/uploads/2012/10/IMGP0504.JPG&w=150&h=150&zc=1&q=100"

    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 486, Column 138: reference to external entity in attribute value
    …thumb.php?src=//wp-content/uploads/2012/10/IMGP0504.JPG&w=150&h=150&zc=1&q=100"

    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 486, Column 138: reference to entity "w" for which no system identifier could be generated
    …thumb.php?src=//wp-content/uploads/2012/10/IMGP0504.JPG&w=150&h=150&zc=1&q=100"

    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 355, Column 159: entity was defined here
    …ent/uploads/2012/06/vlcsnap-2012-06-11-13h47m20s104.png&w=125&h=125&zc=1&q=100"
  • Warning Line 486, Column 144: reference not terminated by REFC delimiter
    …thumb.php?src=//wp-content/uploads/2012/10/IMGP0504.JPG&w=150&h=150&zc=1&q=100"

    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 486, Column 144: reference to external entity in attribute value
    …thumb.php?src=//wp-content/uploads/2012/10/IMGP0504.JPG&w=150&h=150&zc=1&q=100"

    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 486, Column 144: reference to entity "h" for which no system identifier could be generated
    …thumb.php?src=//wp-content/uploads/2012/10/IMGP0504.JPG&w=150&h=150&zc=1&q=100"

    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 355, Column 165: entity was defined here
    …ent/uploads/2012/06/vlcsnap-2012-06-11-13h47m20s104.png&w=125&h=125&zc=1&q=100"
  • Warning Line 486, Column 151: reference not terminated by REFC delimiter
    …thumb.php?src=//wp-content/uploads/2012/10/IMGP0504.JPG&w=150&h=150&zc=1&q=100"

    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 486, Column 151: reference to external entity in attribute value
    …thumb.php?src=//wp-content/uploads/2012/10/IMGP0504.JPG&w=150&h=150&zc=1&q=100"

    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 486, Column 151: reference to entity "zc" for which no system identifier could be generated
    …thumb.php?src=//wp-content/uploads/2012/10/IMGP0504.JPG&w=150&h=150&zc=1&q=100"

    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 355, Column 171: entity was defined here
    …ent/uploads/2012/06/vlcsnap-2012-06-11-13h47m20s104.png&w=125&h=125&zc=1&q=100"
  • Warning Line 486, Column 155: reference not terminated by REFC delimiter
    …thumb.php?src=//wp-content/uploads/2012/10/IMGP0504.JPG&w=150&h=150&zc=1&q=100"

    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 486, Column 155: reference to external entity in attribute value
    …thumb.php?src=//wp-content/uploads/2012/10/IMGP0504.JPG&w=150&h=150&zc=1&q=100"

    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 486, Column 155: reference to entity "q" for which no system identifier could be generated
    …thumb.php?src=//wp-content/uploads/2012/10/IMGP0504.JPG&w=150&h=150&zc=1&q=100"

    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 355, Column 176: entity was defined here
    …ent/uploads/2012/06/vlcsnap-2012-06-11-13h47m20s104.png&w=125&h=125&zc=1&q=100"
  • Warning Line 504, Column 152: reference not terminated by REFC delimiter
    …//wp-content/uploads/2012/10/IMG00046-20090817-1739.jpg&w=150&h=150&zc=1&q=100"

    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 504, Column 152: reference to external entity in attribute value
    …//wp-content/uploads/2012/10/IMG00046-20090817-1739.jpg&w=150&h=150&zc=1&q=100"

    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 504, Column 152: reference to entity "w" for which no system identifier could be generated
    …//wp-content/uploads/2012/10/IMG00046-20090817-1739.jpg&w=150&h=150&zc=1&q=100"

    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 355, Column 159: entity was defined here
    …ent/uploads/2012/06/vlcsnap-2012-06-11-13h47m20s104.png&w=125&h=125&zc=1&q=100"
  • Warning Line 504, Column 158: reference not terminated by REFC delimiter
    …//wp-content/uploads/2012/10/IMG00046-20090817-1739.jpg&w=150&h=150&zc=1&q=100"

    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 504, Column 158: reference to external entity in attribute value
    …//wp-content/uploads/2012/10/IMG00046-20090817-1739.jpg&w=150&h=150&zc=1&q=100"

    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 504, Column 158: reference to entity "h" for which no system identifier could be generated
    …//wp-content/uploads/2012/10/IMG00046-20090817-1739.jpg&w=150&h=150&zc=1&q=100"

    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 355, Column 165: entity was defined here
    …ent/uploads/2012/06/vlcsnap-2012-06-11-13h47m20s104.png&w=125&h=125&zc=1&q=100"
  • Warning Line 504, Column 165: reference not terminated by REFC delimiter
    …//wp-content/uploads/2012/10/IMG00046-20090817-1739.jpg&w=150&h=150&zc=1&q=100"

    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 504, Column 165: reference to external entity in attribute value
    …//wp-content/uploads/2012/10/IMG00046-20090817-1739.jpg&w=150&h=150&zc=1&q=100"

    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 504, Column 165: reference to entity "zc" for which no system identifier could be generated
    …//wp-content/uploads/2012/10/IMG00046-20090817-1739.jpg&w=150&h=150&zc=1&q=100"

    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 355, Column 171: entity was defined here
    …ent/uploads/2012/06/vlcsnap-2012-06-11-13h47m20s104.png&w=125&h=125&zc=1&q=100"
  • Warning Line 504, Column 169: reference not terminated by REFC delimiter
    …//wp-content/uploads/2012/10/IMG00046-20090817-1739.jpg&w=150&h=150&zc=1&q=100"

    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 504, Column 169: reference to external entity in attribute value
    …//wp-content/uploads/2012/10/IMG00046-20090817-1739.jpg&w=150&h=150&zc=1&q=100"

    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 504, Column 169: reference to entity "q" for which no system identifier could be generated
    …//wp-content/uploads/2012/10/IMG00046-20090817-1739.jpg&w=150&h=150&zc=1&q=100"

    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 355, Column 176: entity was defined here
    …ent/uploads/2012/06/vlcsnap-2012-06-11-13h47m20s104.png&w=125&h=125&zc=1&q=100"
  • Warning Line 522, Column 160: reference not terminated by REFC delimiter
    …tent/uploads/2012/10/vlcsnap-2012-10-04-17h39m09s24.png&w=150&h=150&zc=1&q=100"

    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 522, Column 160: reference to external entity in attribute value
    …tent/uploads/2012/10/vlcsnap-2012-10-04-17h39m09s24.png&w=150&h=150&zc=1&q=100"

    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 522, Column 160: reference to entity "w" for which no system identifier could be generated
    …tent/uploads/2012/10/vlcsnap-2012-10-04-17h39m09s24.png&w=150&h=150&zc=1&q=100"

    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 355, Column 159: entity was defined here
    …ent/uploads/2012/06/vlcsnap-2012-06-11-13h47m20s104.png&w=125&h=125&zc=1&q=100"
  • Warning Line 522, Column 166: reference not terminated by REFC delimiter
    …tent/uploads/2012/10/vlcsnap-2012-10-04-17h39m09s24.png&w=150&h=150&zc=1&q=100"

    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 522, Column 166: reference to external entity in attribute value
    …tent/uploads/2012/10/vlcsnap-2012-10-04-17h39m09s24.png&w=150&h=150&zc=1&q=100"

    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 522, Column 166: reference to entity "h" for which no system identifier could be generated
    …tent/uploads/2012/10/vlcsnap-2012-10-04-17h39m09s24.png&w=150&h=150&zc=1&q=100"

    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 355, Column 165: entity was defined here
    …ent/uploads/2012/06/vlcsnap-2012-06-11-13h47m20s104.png&w=125&h=125&zc=1&q=100"
  • Warning Line 522, Column 173: reference not terminated by REFC delimiter
    …tent/uploads/2012/10/vlcsnap-2012-10-04-17h39m09s24.png&w=150&h=150&zc=1&q=100"

    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 522, Column 173: reference to external entity in attribute value
    …tent/uploads/2012/10/vlcsnap-2012-10-04-17h39m09s24.png&w=150&h=150&zc=1&q=100"

    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 522, Column 173: reference to entity "zc" for which no system identifier could be generated
    …tent/uploads/2012/10/vlcsnap-2012-10-04-17h39m09s24.png&w=150&h=150&zc=1&q=100"

    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 355, Column 171: entity was defined here
    …ent/uploads/2012/06/vlcsnap-2012-06-11-13h47m20s104.png&w=125&h=125&zc=1&q=100"
  • Warning Line 522, Column 177: reference not terminated by REFC delimiter
    …tent/uploads/2012/10/vlcsnap-2012-10-04-17h39m09s24.png&w=150&h=150&zc=1&q=100"

    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 522, Column 177: reference to external entity in attribute value
    …tent/uploads/2012/10/vlcsnap-2012-10-04-17h39m09s24.png&w=150&h=150&zc=1&q=100"

    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 522, Column 177: reference to entity "q" for which no system identifier could be generated
    …tent/uploads/2012/10/vlcsnap-2012-10-04-17h39m09s24.png&w=150&h=150&zc=1&q=100"

    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 355, Column 176: entity was defined here
    …ent/uploads/2012/06/vlcsnap-2012-06-11-13h47m20s104.png&w=125&h=125&zc=1&q=100"
  • Warning Line 540, Column 143: reference not terminated by REFC delimiter
    ….php?src=//wp-content/uploads/2012/10/05-22-11_1126.jpg&w=150&h=150&zc=1&q=100"

    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 540, Column 143: reference to external entity in attribute value
    ….php?src=//wp-content/uploads/2012/10/05-22-11_1126.jpg&w=150&h=150&zc=1&q=100"

    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 540, Column 143: reference to entity "w" for which no system identifier could be generated
    ….php?src=//wp-content/uploads/2012/10/05-22-11_1126.jpg&w=150&h=150&zc=1&q=100"

    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 355, Column 159: entity was defined here
    …ent/uploads/2012/06/vlcsnap-2012-06-11-13h47m20s104.png&w=125&h=125&zc=1&q=100"
  • Warning Line 540, Column 149: reference not terminated by REFC delimiter
    ….php?src=//wp-content/uploads/2012/10/05-22-11_1126.jpg&w=150&h=150&zc=1&q=100"

    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 540, Column 149: reference to external entity in attribute value
    ….php?src=//wp-content/uploads/2012/10/05-22-11_1126.jpg&w=150&h=150&zc=1&q=100"

    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 540, Column 149: reference to entity "h" for which no system identifier could be generated
    ….php?src=//wp-content/uploads/2012/10/05-22-11_1126.jpg&w=150&h=150&zc=1&q=100"

    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 355, Column 165: entity was defined here
    …ent/uploads/2012/06/vlcsnap-2012-06-11-13h47m20s104.png&w=125&h=125&zc=1&q=100"
  • Warning Line 540, Column 156: reference not terminated by REFC delimiter
    ….php?src=//wp-content/uploads/2012/10/05-22-11_1126.jpg&w=150&h=150&zc=1&q=100"

    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 540, Column 156: reference to external entity in attribute value
    ….php?src=//wp-content/uploads/2012/10/05-22-11_1126.jpg&w=150&h=150&zc=1&q=100"

    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 540, Column 156: reference to entity "zc" for which no system identifier could be generated
    ….php?src=//wp-content/uploads/2012/10/05-22-11_1126.jpg&w=150&h=150&zc=1&q=100"

    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 355, Column 171: entity was defined here
    …ent/uploads/2012/06/vlcsnap-2012-06-11-13h47m20s104.png&w=125&h=125&zc=1&q=100"
  • Warning Line 540, Column 160: reference not terminated by REFC delimiter
    ….php?src=//wp-content/uploads/2012/10/05-22-11_1126.jpg&w=150&h=150&zc=1&q=100"

    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 540, Column 160: reference to external entity in attribute value
    ….php?src=//wp-content/uploads/2012/10/05-22-11_1126.jpg&w=150&h=150&zc=1&q=100"

    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 540, Column 160: reference to entity "q" for which no system identifier could be generated
    ….php?src=//wp-content/uploads/2012/10/05-22-11_1126.jpg&w=150&h=150&zc=1&q=100"

    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 355, Column 176: entity was defined here
    …ent/uploads/2012/06/vlcsnap-2012-06-11-13h47m20s104.png&w=125&h=125&zc=1&q=100"
  • Warning Line 558, Column 148: reference not terminated by REFC delimiter
    …src=//wp-content/uploads/2012/10/IMG-20120313-00364.jpg&w=150&h=150&zc=1&q=100"

    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 558, Column 148: reference to external entity in attribute value
    …src=//wp-content/uploads/2012/10/IMG-20120313-00364.jpg&w=150&h=150&zc=1&q=100"

    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 558, Column 148: reference to entity "w" for which no system identifier could be generated
    …src=//wp-content/uploads/2012/10/IMG-20120313-00364.jpg&w=150&h=150&zc=1&q=100"

    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 355, Column 159: entity was defined here
    …ent/uploads/2012/06/vlcsnap-2012-06-11-13h47m20s104.png&w=125&h=125&zc=1&q=100"
  • Warning Line 558, Column 154: reference not terminated by REFC delimiter
    …src=//wp-content/uploads/2012/10/IMG-20120313-00364.jpg&w=150&h=150&zc=1&q=100"

    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 558, Column 154: reference to external entity in attribute value
    …src=//wp-content/uploads/2012/10/IMG-20120313-00364.jpg&w=150&h=150&zc=1&q=100"

    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 558, Column 154: reference to entity "h" for which no system identifier could be generated
    …src=//wp-content/uploads/2012/10/IMG-20120313-00364.jpg&w=150&h=150&zc=1&q=100"

    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 355, Column 165: entity was defined here
    …ent/uploads/2012/06/vlcsnap-2012-06-11-13h47m20s104.png&w=125&h=125&zc=1&q=100"
  • Warning Line 558, Column 161: reference not terminated by REFC delimiter
    …src=//wp-content/uploads/2012/10/IMG-20120313-00364.jpg&w=150&h=150&zc=1&q=100"

    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 558, Column 161: reference to external entity in attribute value
    …src=//wp-content/uploads/2012/10/IMG-20120313-00364.jpg&w=150&h=150&zc=1&q=100"

    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 558, Column 161: reference to entity "zc" for which no system identifier could be generated
    …src=//wp-content/uploads/2012/10/IMG-20120313-00364.jpg&w=150&h=150&zc=1&q=100"

    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 355, Column 171: entity was defined here
    …ent/uploads/2012/06/vlcsnap-2012-06-11-13h47m20s104.png&w=125&h=125&zc=1&q=100"
  • Warning Line 558, Column 165: reference not terminated by REFC delimiter
    …src=//wp-content/uploads/2012/10/IMG-20120313-00364.jpg&w=150&h=150&zc=1&q=100"

    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 558, Column 165: reference to external entity in attribute value
    …src=//wp-content/uploads/2012/10/IMG-20120313-00364.jpg&w=150&h=150&zc=1&q=100"

    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 558, Column 165: reference to entity "q" for which no system identifier could be generated
    …src=//wp-content/uploads/2012/10/IMG-20120313-00364.jpg&w=150&h=150&zc=1&q=100"

    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 355, Column 176: entity was defined here
    …ent/uploads/2012/06/vlcsnap-2012-06-11-13h47m20s104.png&w=125&h=125&zc=1&q=100"
  • Warning Line 576, Column 161: reference not terminated by REFC delimiter
    …ent/uploads/2012/10/vlcsnap-2012-10-10-19h57m52s246.png&w=150&h=150&zc=1&q=100"

    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 576, Column 161: reference to external entity in attribute value
    …ent/uploads/2012/10/vlcsnap-2012-10-10-19h57m52s246.png&w=150&h=150&zc=1&q=100"

    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 576, Column 161: reference to entity "w" for which no system identifier could be generated
    …ent/uploads/2012/10/vlcsnap-2012-10-10-19h57m52s246.png&w=150&h=150&zc=1&q=100"

    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 355, Column 159: entity was defined here
    …ent/uploads/2012/06/vlcsnap-2012-06-11-13h47m20s104.png&w=125&h=125&zc=1&q=100"
  • Warning Line 576, Column 167: reference not terminated by REFC delimiter
    …ent/uploads/2012/10/vlcsnap-2012-10-10-19h57m52s246.png&w=150&h=150&zc=1&q=100"

    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 576, Column 167: reference to external entity in attribute value
    …ent/uploads/2012/10/vlcsnap-2012-10-10-19h57m52s246.png&w=150&h=150&zc=1&q=100"

    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 576, Column 167: reference to entity "h" for which no system identifier could be generated
    …ent/uploads/2012/10/vlcsnap-2012-10-10-19h57m52s246.png&w=150&h=150&zc=1&q=100"

    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 355, Column 165: entity was defined here
    …ent/uploads/2012/06/vlcsnap-2012-06-11-13h47m20s104.png&w=125&h=125&zc=1&q=100"
  • Warning Line 576, Column 174: reference not terminated by REFC delimiter
    …ent/uploads/2012/10/vlcsnap-2012-10-10-19h57m52s246.png&w=150&h=150&zc=1&q=100"

    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 576, Column 174: reference to external entity in attribute value
    …ent/uploads/2012/10/vlcsnap-2012-10-10-19h57m52s246.png&w=150&h=150&zc=1&q=100"

    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 576, Column 174: reference to entity "zc" for which no system identifier could be generated
    …ent/uploads/2012/10/vlcsnap-2012-10-10-19h57m52s246.png&w=150&h=150&zc=1&q=100"

    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 355, Column 171: entity was defined here
    …ent/uploads/2012/06/vlcsnap-2012-06-11-13h47m20s104.png&w=125&h=125&zc=1&q=100"
  • Warning Line 576, Column 178: reference not terminated by REFC delimiter
    …ent/uploads/2012/10/vlcsnap-2012-10-10-19h57m52s246.png&w=150&h=150&zc=1&q=100"

    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 576, Column 178: reference to external entity in attribute value
    …ent/uploads/2012/10/vlcsnap-2012-10-10-19h57m52s246.png&w=150&h=150&zc=1&q=100"

    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 576, Column 178: reference to entity "q" for which no system identifier could be generated
    …ent/uploads/2012/10/vlcsnap-2012-10-10-19h57m52s246.png&w=150&h=150&zc=1&q=100"

    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 355, Column 176: entity was defined here
    …ent/uploads/2012/06/vlcsnap-2012-06-11-13h47m20s104.png&w=125&h=125&zc=1&q=100"
  • Warning Line 620, Column 145: reference not terminated by REFC delimiter
    …hp?src=//wp-content/uploads/2009/07/vlcsnap-6051443.jpg&w=125&h=125&zc=1&q=100"

    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 620, Column 145: reference to external entity in attribute value
    …hp?src=//wp-content/uploads/2009/07/vlcsnap-6051443.jpg&w=125&h=125&zc=1&q=100"

    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 620, Column 145: reference to entity "w" for which no system identifier could be generated
    …hp?src=//wp-content/uploads/2009/07/vlcsnap-6051443.jpg&w=125&h=125&zc=1&q=100"

    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 355, Column 159: entity was defined here
    …ent/uploads/2012/06/vlcsnap-2012-06-11-13h47m20s104.png&w=125&h=125&zc=1&q=100"
  • Warning Line 620, Column 151: reference not terminated by REFC delimiter
    …hp?src=//wp-content/uploads/2009/07/vlcsnap-6051443.jpg&w=125&h=125&zc=1&q=100"

    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 620, Column 151: reference to external entity in attribute value
    …hp?src=//wp-content/uploads/2009/07/vlcsnap-6051443.jpg&w=125&h=125&zc=1&q=100"

    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 620, Column 151: reference to entity "h" for which no system identifier could be generated
    …hp?src=//wp-content/uploads/2009/07/vlcsnap-6051443.jpg&w=125&h=125&zc=1&q=100"

    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 355, Column 165: entity was defined here
    …ent/uploads/2012/06/vlcsnap-2012-06-11-13h47m20s104.png&w=125&h=125&zc=1&q=100"
  • Warning Line 620, Column 158: reference not terminated by REFC delimiter
    …hp?src=//wp-content/uploads/2009/07/vlcsnap-6051443.jpg&w=125&h=125&zc=1&q=100"

    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 620, Column 158: reference to external entity in attribute value
    …hp?src=//wp-content/uploads/2009/07/vlcsnap-6051443.jpg&w=125&h=125&zc=1&q=100"

    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 620, Column 158: reference to entity "zc" for which no system identifier could be generated
    …hp?src=//wp-content/uploads/2009/07/vlcsnap-6051443.jpg&w=125&h=125&zc=1&q=100"

    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 355, Column 171: entity was defined here
    …ent/uploads/2012/06/vlcsnap-2012-06-11-13h47m20s104.png&w=125&h=125&zc=1&q=100"
  • Warning Line 620, Column 162: reference not terminated by REFC delimiter
    …hp?src=//wp-content/uploads/2009/07/vlcsnap-6051443.jpg&w=125&h=125&zc=1&q=100"

    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 620, Column 162: reference to external entity in attribute value
    …hp?src=//wp-content/uploads/2009/07/vlcsnap-6051443.jpg&w=125&h=125&zc=1&q=100"

    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 620, Column 162: reference to entity "q" for which no system identifier could be generated
    …hp?src=//wp-content/uploads/2009/07/vlcsnap-6051443.jpg&w=125&h=125&zc=1&q=100"

    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 355, Column 176: entity was defined here
    …ent/uploads/2012/06/vlcsnap-2012-06-11-13h47m20s104.png&w=125&h=125&zc=1&q=100"
  • Warning Line 630, Column 158: reference not terminated by REFC delimiter
    …ontent/uploads/2009/05/la_roxana_de_la_catolica_001.jpg&w=125&h=125&zc=1&q=100"

    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 630, Column 158: reference to external entity in attribute value
    …ontent/uploads/2009/05/la_roxana_de_la_catolica_001.jpg&w=125&h=125&zc=1&q=100"

    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 630, Column 158: reference to entity "w" for which no system identifier could be generated
    …ontent/uploads/2009/05/la_roxana_de_la_catolica_001.jpg&w=125&h=125&zc=1&q=100"

    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 355, Column 159: entity was defined here
    …ent/uploads/2012/06/vlcsnap-2012-06-11-13h47m20s104.png&w=125&h=125&zc=1&q=100"
  • Warning Line 630, Column 164: reference not terminated by REFC delimiter
    …ontent/uploads/2009/05/la_roxana_de_la_catolica_001.jpg&w=125&h=125&zc=1&q=100"

    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 630, Column 164: reference to external entity in attribute value
    …ontent/uploads/2009/05/la_roxana_de_la_catolica_001.jpg&w=125&h=125&zc=1&q=100"

    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 630, Column 164: reference to entity "h" for which no system identifier could be generated
    …ontent/uploads/2009/05/la_roxana_de_la_catolica_001.jpg&w=125&h=125&zc=1&q=100"

    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 355, Column 165: entity was defined here
    …ent/uploads/2012/06/vlcsnap-2012-06-11-13h47m20s104.png&w=125&h=125&zc=1&q=100"
  • Warning Line 630, Column 171: reference not terminated by REFC delimiter
    …ontent/uploads/2009/05/la_roxana_de_la_catolica_001.jpg&w=125&h=125&zc=1&q=100"

    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 630, Column 171: reference to external entity in attribute value
    …ontent/uploads/2009/05/la_roxana_de_la_catolica_001.jpg&w=125&h=125&zc=1&q=100"

    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 630, Column 171: reference to entity "zc" for which no system identifier could be generated
    …ontent/uploads/2009/05/la_roxana_de_la_catolica_001.jpg&w=125&h=125&zc=1&q=100"

    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 355, Column 171: entity was defined here
    …ent/uploads/2012/06/vlcsnap-2012-06-11-13h47m20s104.png&w=125&h=125&zc=1&q=100"
  • Warning Line 630, Column 175: reference not terminated by REFC delimiter
    …ontent/uploads/2009/05/la_roxana_de_la_catolica_001.jpg&w=125&h=125&zc=1&q=100"

    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 630, Column 175: reference to external entity in attribute value
    …ontent/uploads/2009/05/la_roxana_de_la_catolica_001.jpg&w=125&h=125&zc=1&q=100"

    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 630, Column 175: reference to entity "q" for which no system identifier could be generated
    …ontent/uploads/2009/05/la_roxana_de_la_catolica_001.jpg&w=125&h=125&zc=1&q=100"

    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 355, Column 176: entity was defined here
    …ent/uploads/2012/06/vlcsnap-2012-06-11-13h47m20s104.png&w=125&h=125&zc=1&q=100"
  • Warning Line 640, Column 162: reference not terminated by REFC delimiter
    …nt/uploads/2012/05/Alejandra-IMG00310-20120109-1349.jpg&w=125&h=125&zc=1&q=100"

    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 640, Column 162: reference to external entity in attribute value
    …nt/uploads/2012/05/Alejandra-IMG00310-20120109-1349.jpg&w=125&h=125&zc=1&q=100"

    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 640, Column 162: reference to entity "w" for which no system identifier could be generated
    …nt/uploads/2012/05/Alejandra-IMG00310-20120109-1349.jpg&w=125&h=125&zc=1&q=100"

    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 355, Column 159: entity was defined here
    …ent/uploads/2012/06/vlcsnap-2012-06-11-13h47m20s104.png&w=125&h=125&zc=1&q=100"
  • Warning Line 640, Column 168: reference not terminated by REFC delimiter
    …nt/uploads/2012/05/Alejandra-IMG00310-20120109-1349.jpg&w=125&h=125&zc=1&q=100"

    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 640, Column 168: reference to external entity in attribute value
    …nt/uploads/2012/05/Alejandra-IMG00310-20120109-1349.jpg&w=125&h=125&zc=1&q=100"

    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 640, Column 168: reference to entity "h" for which no system identifier could be generated
    …nt/uploads/2012/05/Alejandra-IMG00310-20120109-1349.jpg&w=125&h=125&zc=1&q=100"

    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 355, Column 165: entity was defined here
    …ent/uploads/2012/06/vlcsnap-2012-06-11-13h47m20s104.png&w=125&h=125&zc=1&q=100"
  • Warning Line 640, Column 175: reference not terminated by REFC delimiter
    …nt/uploads/2012/05/Alejandra-IMG00310-20120109-1349.jpg&w=125&h=125&zc=1&q=100"

    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 640, Column 175: reference to external entity in attribute value
    …nt/uploads/2012/05/Alejandra-IMG00310-20120109-1349.jpg&w=125&h=125&zc=1&q=100"

    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 640, Column 175: reference to entity "zc" for which no system identifier could be generated
    …nt/uploads/2012/05/Alejandra-IMG00310-20120109-1349.jpg&w=125&h=125&zc=1&q=100"

    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 355, Column 171: entity was defined here
    …ent/uploads/2012/06/vlcsnap-2012-06-11-13h47m20s104.png&w=125&h=125&zc=1&q=100"
  • Warning Line 640, Column 179: reference not terminated by REFC delimiter
    …nt/uploads/2012/05/Alejandra-IMG00310-20120109-1349.jpg&w=125&h=125&zc=1&q=100"

    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 640, Column 179: reference to external entity in attribute value
    …nt/uploads/2012/05/Alejandra-IMG00310-20120109-1349.jpg&w=125&h=125&zc=1&q=100"

    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 640, Column 179: reference to entity "q" for which no system identifier could be generated
    …nt/uploads/2012/05/Alejandra-IMG00310-20120109-1349.jpg&w=125&h=125&zc=1&q=100"

    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 355, Column 176: entity was defined here
    …ent/uploads/2012/06/vlcsnap-2012-06-11-13h47m20s104.png&w=125&h=125&zc=1&q=100"
  • Warning Line 650, Column 138: reference not terminated by REFC delimiter
    …thumb.php?src=//wp-content/uploads/2012/04/DSC01837.jpg&w=125&h=125&zc=1&q=100"

    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 650, Column 138: reference to external entity in attribute value
    …thumb.php?src=//wp-content/uploads/2012/04/DSC01837.jpg&w=125&h=125&zc=1&q=100"

    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 650, Column 138: reference to entity "w" for which no system identifier could be generated
    …thumb.php?src=//wp-content/uploads/2012/04/DSC01837.jpg&w=125&h=125&zc=1&q=100"

    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 355, Column 159: entity was defined here
    …ent/uploads/2012/06/vlcsnap-2012-06-11-13h47m20s104.png&w=125&h=125&zc=1&q=100"
  • Warning Line 650, Column 144: reference not terminated by REFC delimiter
    …thumb.php?src=//wp-content/uploads/2012/04/DSC01837.jpg&w=125&h=125&zc=1&q=100"

    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 650, Column 144: reference to external entity in attribute value
    …thumb.php?src=//wp-content/uploads/2012/04/DSC01837.jpg&w=125&h=125&zc=1&q=100"

    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 650, Column 144: reference to entity "h" for which no system identifier could be generated
    …thumb.php?src=//wp-content/uploads/2012/04/DSC01837.jpg&w=125&h=125&zc=1&q=100"

    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 355, Column 165: entity was defined here
    …ent/uploads/2012/06/vlcsnap-2012-06-11-13h47m20s104.png&w=125&h=125&zc=1&q=100"
  • Warning Line 650, Column 151: reference not terminated by REFC delimiter
    …thumb.php?src=//wp-content/uploads/2012/04/DSC01837.jpg&w=125&h=125&zc=1&q=100"

    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 650, Column 151: reference to external entity in attribute value
    …thumb.php?src=//wp-content/uploads/2012/04/DSC01837.jpg&w=125&h=125&zc=1&q=100"

    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 650, Column 151: reference to entity "zc" for which no system identifier could be generated
    …thumb.php?src=//wp-content/uploads/2012/04/DSC01837.jpg&w=125&h=125&zc=1&q=100"

    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 355, Column 171: entity was defined here
    …ent/uploads/2012/06/vlcsnap-2012-06-11-13h47m20s104.png&w=125&h=125&zc=1&q=100"
  • Warning Line 650, Column 155: reference not terminated by REFC delimiter
    …thumb.php?src=//wp-content/uploads/2012/04/DSC01837.jpg&w=125&h=125&zc=1&q=100"

    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 650, Column 155: reference to external entity in attribute value
    …thumb.php?src=//wp-content/uploads/2012/04/DSC01837.jpg&w=125&h=125&zc=1&q=100"

    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 650, Column 155: reference to entity "q" for which no system identifier could be generated
    …thumb.php?src=//wp-content/uploads/2012/04/DSC01837.jpg&w=125&h=125&zc=1&q=100"

    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 355, Column 176: entity was defined here
    …ent/uploads/2012/06/vlcsnap-2012-06-11-13h47m20s104.png&w=125&h=125&zc=1&q=100"
  • Error Line 654, Column 13: 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 601, Column 1: start tag was here
    <p align="center">
  • Error Line 657, Column 4: end tag for element "p" which is not open
    </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.

  • Warning Line 684, Column 131: reference not terminated by REFC delimiter
    …ipts/timthumb.php?src=//wp-content/uploads/2010/02/7.jpg&w=315&h=315&zc=1&q=50"

    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 684, Column 131: reference to external entity in attribute value
    …ipts/timthumb.php?src=//wp-content/uploads/2010/02/7.jpg&w=315&h=315&zc=1&q=50"

    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 684, Column 131: reference to entity "w" for which no system identifier could be generated
    …ipts/timthumb.php?src=//wp-content/uploads/2010/02/7.jpg&w=315&h=315&zc=1&q=50"

    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 355, Column 159: entity was defined here
    …ent/uploads/2012/06/vlcsnap-2012-06-11-13h47m20s104.png&w=125&h=125&zc=1&q=100"
  • Warning Line 684, Column 137: reference not terminated by REFC delimiter
    …ipts/timthumb.php?src=//wp-content/uploads/2010/02/7.jpg&w=315&h=315&zc=1&q=50"

    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 684, Column 137: reference to external entity in attribute value
    …ipts/timthumb.php?src=//wp-content/uploads/2010/02/7.jpg&w=315&h=315&zc=1&q=50"

    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 684, Column 137: reference to entity "h" for which no system identifier could be generated
    …ipts/timthumb.php?src=//wp-content/uploads/2010/02/7.jpg&w=315&h=315&zc=1&q=50"

    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 355, Column 165: entity was defined here
    …ent/uploads/2012/06/vlcsnap-2012-06-11-13h47m20s104.png&w=125&h=125&zc=1&q=100"
  • Warning Line 684, Column 144: reference not terminated by REFC delimiter
    …ipts/timthumb.php?src=//wp-content/uploads/2010/02/7.jpg&w=315&h=315&zc=1&q=50"

    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 684, Column 144: reference to external entity in attribute value
    …ipts/timthumb.php?src=//wp-content/uploads/2010/02/7.jpg&w=315&h=315&zc=1&q=50"

    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 684, Column 144: reference to entity "zc" for which no system identifier could be generated
    …ipts/timthumb.php?src=//wp-content/uploads/2010/02/7.jpg&w=315&h=315&zc=1&q=50"

    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 355, Column 171: entity was defined here
    …ent/uploads/2012/06/vlcsnap-2012-06-11-13h47m20s104.png&w=125&h=125&zc=1&q=100"
  • Warning Line 684, Column 148: reference not terminated by REFC delimiter
    …ipts/timthumb.php?src=//wp-content/uploads/2010/02/7.jpg&w=315&h=315&zc=1&q=50"

    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 684, Column 148: reference to external entity in attribute value
    …ipts/timthumb.php?src=//wp-content/uploads/2010/02/7.jpg&w=315&h=315&zc=1&q=50"

    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 684, Column 148: reference to entity "q" for which no system identifier could be generated
    …ipts/timthumb.php?src=//wp-content/uploads/2010/02/7.jpg&w=315&h=315&zc=1&q=50"

    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 355, Column 176: entity was defined here
    …ent/uploads/2012/06/vlcsnap-2012-06-11-13h47m20s104.png&w=125&h=125&zc=1&q=100"
  • Error Line 698, Column 16: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <iframe border=0 frameborder=0 marginheight=0 marginwidth=0 width=308 height=25…
  • Error Line 698, Column 30: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <iframe border=0 frameborder=0 marginheight=0 marginwidth=0 width=308 height=25…
  • Error Line 698, Column 45: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …e border=0 frameborder=0 marginheight=0 marginwidth=0 width=308 height=258 scr…
  • Error Line 698, Column 59: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …meborder=0 marginheight=0 marginwidth=0 width=308 height=258 scrolling=no allo…
  • Error Line 698, Column 67: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …=0 marginheight=0 marginwidth=0 width=308 height=258 scrolling=no allowtranspa…
  • Error Line 698, Column 78: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ight=0 marginwidth=0 width=308 height=258 scrolling=no allowtransparency=true …
  • Error Line 698, Column 92: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …idth=0 width=308 height=258 scrolling=no allowtransparency=true src=http://ads…
  • Error Line 698, Column 113: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ht=258 scrolling=no allowtransparency=true src=http://adserver.juicyads.com/ad…
  • Error Line 698, Column 122: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …rolling=no allowtransparency=true src=http://adserver.juicyads.com/adshow.php?…
  • Error Line 698, Column 128: NET-enabling start-tag not immediately followed by null end-tag
    …g=no allowtransparency=true src=http://adserver.juicyads.com/adshow.php?adzone…

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

  • Error Line 698, Column 183: end tag for element "iframe" which is not open
    …parency=true src=http://adserver.juicyads.com/adshow.php?adzone=11317></iframe>

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

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

  • Error Line 714, Column 26: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
            <div class="last">

    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 722, Column 26: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
            <div class="last">

    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 730, Column 26: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
            <div class="last">

    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 738, Column 26: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
            <div class="last">

    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 746, Column 26: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
            <div class="last">

    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 26: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
            <div class="last">

    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 763, Column 16: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <iframe border=0 frameborder=0 marginheight=0 marginwidth=0 width=168 height=60…
  • Error Line 763, Column 30: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <iframe border=0 frameborder=0 marginheight=0 marginwidth=0 width=168 height=60…
  • Error Line 763, Column 45: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …e border=0 frameborder=0 marginheight=0 marginwidth=0 width=168 height=608 scr…
  • Error Line 763, Column 59: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …meborder=0 marginheight=0 marginwidth=0 width=168 height=608 scrolling=no allo…
  • Error Line 763, Column 67: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …=0 marginheight=0 marginwidth=0 width=168 height=608 scrolling=no allowtranspa…
  • Error Line 763, Column 78: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ight=0 marginwidth=0 width=168 height=608 scrolling=no allowtransparency=true …
  • Error Line 763, Column 92: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …idth=0 width=168 height=608 scrolling=no allowtransparency=true src=http://ads…
  • Error Line 763, Column 113: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ht=608 scrolling=no allowtransparency=true src=http://adserver.juicyads.com/ad…
  • Error Line 763, Column 122: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …rolling=no allowtransparency=true src=http://adserver.juicyads.com/adshow.php?…
  • Error Line 763, Column 128: NET-enabling start-tag not immediately followed by null end-tag
    …g=no allowtransparency=true src=http://adserver.juicyads.com/adshow.php?adzone…

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

  • Error Line 763, Column 183: end tag for element "iframe" which is not open
    …parency=true src=http://adserver.juicyads.com/adshow.php?adzone=11443></iframe>

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

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

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

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

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

  • Error Line 777, Column 16: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <iframe border=0 frameborder=0 marginheight=0 marginwidth=0 width=168 height=60…
  • Error Line 777, Column 30: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <iframe border=0 frameborder=0 marginheight=0 marginwidth=0 width=168 height=60…
  • Error Line 777, Column 45: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …e border=0 frameborder=0 marginheight=0 marginwidth=0 width=168 height=608 scr…
  • Error Line 777, Column 59: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …meborder=0 marginheight=0 marginwidth=0 width=168 height=608 scrolling=no allo…
  • Error Line 777, Column 67: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …=0 marginheight=0 marginwidth=0 width=168 height=608 scrolling=no allowtranspa…
  • Error Line 777, Column 78: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ight=0 marginwidth=0 width=168 height=608 scrolling=no allowtransparency=true …
  • Error Line 777, Column 92: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …idth=0 width=168 height=608 scrolling=no allowtransparency=true src=http://ads…
  • Error Line 777, Column 113: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ht=608 scrolling=no allowtransparency=true src=http://adserver.juicyads.com/ad…
  • Error Line 777, Column 122: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …rolling=no allowtransparency=true src=http://adserver.juicyads.com/adshow.php?…
  • Error Line 777, Column 128: NET-enabling start-tag not immediately followed by null end-tag
    …g=no allowtransparency=true src=http://adserver.juicyads.com/adshow.php?adzone…

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

  • Error Line 777, Column 183: end tag for element "iframe" which is not open
    …parency=true src=http://adserver.juicyads.com/adshow.php?adzone=73472></iframe>

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

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

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

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

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

  • Warning Line 809, Column 161: reference not terminated by REFC delimiter
    …tent/uploads/2009/04/36710_csy16i169685-02_122_497lo.jpg&w=315&h=315&zc=1&q=50"

    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 809, Column 161: reference to external entity in attribute value
    …tent/uploads/2009/04/36710_csy16i169685-02_122_497lo.jpg&w=315&h=315&zc=1&q=50"

    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 809, Column 161: reference to entity "w" for which no system identifier could be generated
    …tent/uploads/2009/04/36710_csy16i169685-02_122_497lo.jpg&w=315&h=315&zc=1&q=50"

    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 355, Column 159: entity was defined here
    …ent/uploads/2012/06/vlcsnap-2012-06-11-13h47m20s104.png&w=125&h=125&zc=1&q=100"
  • Warning Line 809, Column 167: reference not terminated by REFC delimiter
    …tent/uploads/2009/04/36710_csy16i169685-02_122_497lo.jpg&w=315&h=315&zc=1&q=50"

    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 809, Column 167: reference to external entity in attribute value
    …tent/uploads/2009/04/36710_csy16i169685-02_122_497lo.jpg&w=315&h=315&zc=1&q=50"

    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 809, Column 167: reference to entity "h" for which no system identifier could be generated
    …tent/uploads/2009/04/36710_csy16i169685-02_122_497lo.jpg&w=315&h=315&zc=1&q=50"

    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 355, Column 165: entity was defined here
    …ent/uploads/2012/06/vlcsnap-2012-06-11-13h47m20s104.png&w=125&h=125&zc=1&q=100"
  • Warning Line 809, Column 174: reference not terminated by REFC delimiter
    …tent/uploads/2009/04/36710_csy16i169685-02_122_497lo.jpg&w=315&h=315&zc=1&q=50"

    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 809, Column 174: reference to external entity in attribute value
    …tent/uploads/2009/04/36710_csy16i169685-02_122_497lo.jpg&w=315&h=315&zc=1&q=50"

    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 809, Column 174: reference to entity "zc" for which no system identifier could be generated
    …tent/uploads/2009/04/36710_csy16i169685-02_122_497lo.jpg&w=315&h=315&zc=1&q=50"

    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 355, Column 171: entity was defined here
    …ent/uploads/2012/06/vlcsnap-2012-06-11-13h47m20s104.png&w=125&h=125&zc=1&q=100"
  • Warning Line 809, Column 178: reference not terminated by REFC delimiter
    …tent/uploads/2009/04/36710_csy16i169685-02_122_497lo.jpg&w=315&h=315&zc=1&q=50"

    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 809, Column 178: reference to external entity in attribute value
    …tent/uploads/2009/04/36710_csy16i169685-02_122_497lo.jpg&w=315&h=315&zc=1&q=50"

    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 809, Column 178: reference to entity "q" for which no system identifier could be generated
    …tent/uploads/2009/04/36710_csy16i169685-02_122_497lo.jpg&w=315&h=315&zc=1&q=50"

    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 355, Column 176: entity was defined here
    …ent/uploads/2012/06/vlcsnap-2012-06-11-13h47m20s104.png&w=125&h=125&zc=1&q=100"
  • Error Line 855, Column 23: document type does not allow element "style" here
    <style type="text/css">

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

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

  • Error Line 876, Column 17: document type does not allow element "td" here
    <td colspan="11"> <center>

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

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

  • Error Line 882, Column 30: required attribute "type" not specified
    <script language="JavaScript"> showLink(1)</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 885, Column 30: required attribute "type" not specified
    <script language="JavaScript"> showLink(2)</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 889, Column 30: required attribute "type" not specified
    <script language="JavaScript"> showLink(3)</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 892, Column 30: required attribute "type" not specified
    <script language="JavaScript"> showLink(4)</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 897, Column 30: required attribute "type" not specified
    <script language="JavaScript"> showLink(5)</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 901, Column 30: required attribute "type" not specified
    <script language="JavaScript"> showLink(6)</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 904, Column 30: required attribute "type" not specified
    <script language="JavaScript"> showLink(7)</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 907, Column 30: required attribute "type" not specified
    <script language="JavaScript"> showLink(8)</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 913, Column 30: required attribute "type" not specified
    <script language="JavaScript"> showLink(9)</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 916, Column 30: required attribute "type" not specified
    <script language="JavaScript"> showLink(10)</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 919, Column 30: required attribute "type" not specified
    <script language="JavaScript"> showLink(11)</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 922, Column 30: required attribute "type" not specified
    <script language="JavaScript"> showLink(12)</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 928, Column 30: required attribute "type" not specified
    <script language="JavaScript"> showLink(13)</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 931, Column 30: required attribute "type" not specified
    <script language="JavaScript"> showLink(14)</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 934, Column 30: required attribute "type" not specified
    <script language="JavaScript"> showLink(15)</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 938, Column 30: required attribute "type" not specified
    <script language="JavaScript"> showLink(16)</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 945, Column 17: document type does not allow element "td" here
    <td colspan="11"> <center>

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

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

  • Error Line 996, Column 5: end tag for "ul" which is not finished
    </ul>

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

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

  • Error Line 1006, Column 165: there is no attribute "data-cfemail"
    …re.com/email-protection" data-cfemail="bfccd0d3d0c9dad1dac5d0d3ded1deccffd8d2d…

    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 1012, Column 35: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <div align="center" class="style2">Solovenezolanas.com no se hace responsable d…

    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 1015, Column 223: end tag for "a" omitted, but OMITTAG NO was specified
    …d abandona el site pulsando <a href="http://www.soloenvenezuela.com">aqui</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 1015, Column 173: start tag was here
    …nor de edad abandona el site pulsando <a href="http://www.soloenvenezuela.com"…
  • Warning Line 1037, Column 56: cannot generate system identifier for general entity "n"
    …tp://x6.xclicks.net/sc/add.php?s=7174&n=16e5c" target="_blank">Trade Traffic</…

    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 1037, Column 56: general entity "n" not defined and no default entity
    …tp://x6.xclicks.net/sc/add.php?s=7174&n=16e5c" target="_blank">Trade Traffic</…

    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 1037, Column 57: reference not terminated by REFC delimiter
    …p://x6.xclicks.net/sc/add.php?s=7174&n=16e5c" target="_blank">Trade Traffic</a…

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

  • Warning Line 1037, Column 57: reference to external entity in attribute value
    …p://x6.xclicks.net/sc/add.php?s=7174&n=16e5c" target="_blank">Trade Traffic</a…

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

  • Error Line 1037, Column 57: reference to entity "n" for which no system identifier could be generated
    …p://x6.xclicks.net/sc/add.php?s=7174&n=16e5c" target="_blank">Trade Traffic</a…

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

  • Info Line 1037, Column 55: entity was defined here
    …ttp://x6.xclicks.net/sc/add.php?s=7174&n=16e5c" target="_blank">Trade Traffic<…
  • Error Line 1039, Column 7: end tag for "div" omitted, but OMITTAG NO was specified
    </body>

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

  • Info Line 1012, Column 1: start tag was here
    <div align="center" class="style2">Solovenezolanas.com no se hace responsable d…
  • Error Line 1039, Column 7: end tag for "span" omitted, but OMITTAG NO was specified
    </body>

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

  • Info Line 1006, Column 56: start tag was here
    …r" class="style2">Envianos tus fotos a<span class="style1"> <a class="__cf_ema…
  • Error Line 1039, Column 7: end tag for "div" omitted, but OMITTAG NO was specified
    </body>

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

  • Info Line 1006, Column 1: start tag was here
    <div align="center" class="style2">Envianos tus fotos a<span class="style1"> <a…
  • Error Line 1039, Column 7: end tag for "center" omitted, but OMITTAG NO was specified
    </body>

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

  • Info Line 945, Column 19: start tag was here
    <td colspan="11"> <center>
  • Error Line 1039, Column 7: end tag for "td" omitted, but OMITTAG NO was specified
    </body>

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

  • Info Line 945, Column 1: start tag was here
    <td colspan="11"> <center>
  • Error Line 1039, Column 7: end tag for "p" omitted, but OMITTAG NO was specified
    </body>

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

  • Info Line 944, Column 1: start tag was here
    <p style="text-align: center;">
  • Error Line 1039, Column 7: end tag for "center" omitted, but OMITTAG NO was specified
    </body>

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

  • Info Line 876, Column 19: start tag was here
    <td colspan="11"> <center>
  • Error Line 1039, Column 7: end tag for "td" omitted, but OMITTAG NO was specified
    </body>

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

  • Info Line 876, Column 1: start tag was here
    <td colspan="11"> <center>
  • Error Line 1039, Column 7: end tag for "p" omitted, but OMITTAG NO was specified
    </body>

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

  • Info Line 875, Column 1: start tag was here
    <p style="text-align: center;">

Visitor Analysis

Daily Visitor
  • 1.517 visits