Markup Validation Service
Check the markup (HTML, XHTML, …) of Web documents
Markup Validation Service
Check the markup (HTML, XHTML, …) of Web documents
Line 578,
Column 37:
ID "golden" already defined
<a class="closethis" id="golden" href="#" name="golden"><img src=An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).
Line 572,
Column 51:
ID "golden" first defined here
… <a class="watchthis" id="golden" href="#" name="golden"><img src=
Line 585,
Column 45:
cannot generate system identifier for general entity "width"
…li><a href="http://vimeo.com/32580903&width=700" rel="prettyPhoto" title="Codi…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 "&" (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 æ 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.
Line 585,
Column 45:
general entity "width" not defined and no default entity
…li><a href="http://vimeo.com/32580903&width=700" rel="prettyPhoto" title="Codi…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.
Line 585,
Column 50:
reference not terminated by REFC delimiter
… href="http://vimeo.com/32580903&width=700" rel="prettyPhoto" title="Coding Ti…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.
Line 585,
Column 50:
reference to external entity in attribute value
… href="http://vimeo.com/32580903&width=700" rel="prettyPhoto" title="Coding Ti…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 '&'.
Line 585,
Column 50:
reference to entity "width" for which no system identifier could be generated
… href="http://vimeo.com/32580903&width=700" rel="prettyPhoto" title="Coding Ti…This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.
Line 585,
Column 44:
entity was defined here
…<li><a href="http://vimeo.com/32580903&width=700" rel="prettyPhoto" title="Cod……250px; height:250px; background:transparent; display:hidden;"> </div> </a></li>The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
Line 594,
Column 50:
reference not terminated by REFC delimiter
… href="http://vimeo.com/35532214&width=700" rel="prettyPhoto" title="See my Ph…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.
Line 594,
Column 50:
reference to external entity in attribute value
… href="http://vimeo.com/35532214&width=700" rel="prettyPhoto" title="See my Ph…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 '&'.
Line 594,
Column 50:
reference to entity "width" for which no system identifier could be generated
… href="http://vimeo.com/35532214&width=700" rel="prettyPhoto" title="See my Ph…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.
Line 585,
Column 44:
entity was defined here
…<li><a href="http://vimeo.com/32580903&width=700" rel="prettyPhoto" title="Cod……250px; height:250px; background:transparent; display:hidden;"> </div> </a></li>The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
