this post concerns three pages.
1. this page: http://www.katherine-designs.com/sendemail.php i get the following errors:
a lot of it seems to deal with the PHP code i inserted to the page. as my PHP skills are close to nil, i'm wary about fiddling with it myself. =\
2. now this page: http://www.katherine-designs.com/contact.php
i get these errors:
I tried to insert the input fields into divs because that seems to work for some people. Didn't work for me.
3. Finally, this page: http://www.katherine-designs.com/
The errors are coming from the Twitter 'widget' code I inserted to my page. I can't any alternatives that validate well in XHTML 1.0 Strict so any help would be greatly appreciated!
1. this page: http://www.katherine-designs.com/sendemail.php i get the following errors:
# Error Line 59, Column 135: end tag for "img" omitted, but OMITTAG NO was specified
…lance design and illustration" ></a>
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
# Info Line 59, Column 35: start tag was here
<div id="top"><a href="index.htm l"><img src="img/header_name.gif " alt="Katherine
# Error Line 79, Column 10: end tag for "div" omitted, but OMITTAG NO was specified
Use ba…
✉
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
# Info Line 76: start tag was here
><div id="contact">
# Error Line 79, Column 10: end tag for "div" omitted, but OMITTAG NO was specified
Use ba…
✉
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
# Info Line 57: start tag was here
><div id="wrapper">
# Error Line 79, Column 10: end tag for "body" omitted, but OMITTAG NO was specified
Use ba…
✉
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
# Info Line 56: start tag was here
><body>
# Error Line 79, Column 10: end tag for "html" omitted, but OMITTAG NO was specified
Use ba…
✉
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
# Info Line 2: start tag was here
><html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
# Error Line 59, Column > 80: XML Parsing Error: Opening and ending tag mismatch: img line 59 and a
…="img/header_name.gif " alt="Katherine Valenzuela - Freelance design and illus…
✉
# Error Line 74, Column 6: XML Parsing Error: Opening and ending tag mismatch: a line 59 and div
</div>
✉
# Error Line 79, Column 9: XML Parsing Error: Premature end of data in tag div line 76
Use back!
✉
# Error Line 79, Column 9: XML Parsing Error: Premature end of data in tag div line 59
Use back!
✉
# Error Line 79, Column 9: XML Parsing Error: Premature end of data in tag div line 57
Use back!
✉
# Error Line 79, Column 9: XML Parsing Error: Premature end of data in tag body line 56
Use back!
✉
# Error Line 79, Column 9: XML Parsing Error: Premature end of data in tag html line 2
Use back!
…lance design and illustration" ></a>
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
# Info Line 59, Column 35: start tag was here
<div id="top"><a href="index.htm l"><img src="img/header_name.gif " alt="Katherine
# Error Line 79, Column 10: end tag for "div" omitted, but OMITTAG NO was specified
Use ba…
✉
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
# Info Line 76: start tag was here
><div id="contact">
# Error Line 79, Column 10: end tag for "div" omitted, but OMITTAG NO was specified
Use ba…
✉
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
# Info Line 57: start tag was here
><div id="wrapper">
# Error Line 79, Column 10: end tag for "body" omitted, but OMITTAG NO was specified
Use ba…
✉
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
# Info Line 56: start tag was here
><body>
# Error Line 79, Column 10: end tag for "html" omitted, but OMITTAG NO was specified
Use ba…
✉
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
# Info Line 2: start tag was here
><html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
# Error Line 59, Column > 80: XML Parsing Error: Opening and ending tag mismatch: img line 59 and a
…="img/header_name.gif " alt="Katherine Valenzuela - Freelance design and illus…
✉
# Error Line 74, Column 6: XML Parsing Error: Opening and ending tag mismatch: a line 59 and div
</div>
✉
# Error Line 79, Column 9: XML Parsing Error: Premature end of data in tag div line 76
Use back!
✉
# Error Line 79, Column 9: XML Parsing Error: Premature end of data in tag div line 59
Use back!
✉
# Error Line 79, Column 9: XML Parsing Error: Premature end of data in tag div line 57
Use back!
✉
# Error Line 79, Column 9: XML Parsing Error: Premature end of data in tag body line 56
Use back!
✉
# Error Line 79, Column 9: XML Parsing Error: Premature end of data in tag html line 2
Use back!
2. now this page: http://www.katherine-designs.com/contact.php
i get these errors:
1. Error Line 81, Column 54: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
2. Error Line 82, Column 47: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
<input type="hidden" name="httpref" value="" />
3. Error Line 83, Column 68: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
2. Error Line 82, Column 47: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
<input type="hidden" name="httpref" value="" />
3. Error Line 83, Column 68: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
3. Finally, this page: http://www.katherine-designs.com/
# Warning Line 83, Column 92: cannot generate system identifier for general entity "count"
…oh_k.json?call back=twitterCal lback2&count=2" type="text/javascript"></script>
✉
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.
# Error Line 83, Column 92: general entity "count" not defined and no default entity
…oh_k.json?call back=twitterCal lback2&count=2" type="text/javascript"></script>
✉
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 83, Column 97: reference not terminated by REFC delimiter
…json?callback= twitterCallback 2&count=2" type="text/javascript"></script>
✉
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 83, Column 97: reference to external entity in attribute value
…json?callback= twitterCallback 2&count=2" type="text/javascript"></script>
✉
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 '&'.
# Error Line 83, Column 97: reference to entity "count" for which no system identifier could be generated
…json?callback= twitterCallback 2&count=2" type="text/javascript"></script>
✉
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 83, Column 90: entity was defined here
…e/oh_k.json?callb ack=twitterCall back2&count=2" type="text/javascript"></scri…
# Error Line 83, Column > 80: XML Parsing Error: EntityRef: expecting ';'
…er_timeline/oh_k.json?callb ack=twitterCall back2&count=2" type="text/javascrip…
…oh_k.json?call back=twitterCal lback2&count=2" type="text/javascript"></script>
✉
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.
# Error Line 83, Column 92: general entity "count" not defined and no default entity
…oh_k.json?call back=twitterCal lback2&count=2" type="text/javascript"></script>
✉
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 83, Column 97: reference not terminated by REFC delimiter
…json?callback= twitterCallback 2&count=2" type="text/javascript"></script>
✉
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 83, Column 97: reference to external entity in attribute value
…json?callback= twitterCallback 2&count=2" type="text/javascript"></script>
✉
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 '&'.
# Error Line 83, Column 97: reference to entity "count" for which no system identifier could be generated
…json?callback= twitterCallback 2&count=2" type="text/javascript"></script>
✉
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 83, Column 90: entity was defined here
…e/oh_k.json?callb ack=twitterCall back2&count=2" type="text/javascript"></scri…
# Error Line 83, Column > 80: XML Parsing Error: EntityRef: expecting ';'
…er_timeline/oh_k.json?callb ack=twitterCall back2&count=2" type="text/javascrip…
Comment