here is the errors maybe you might want to address
Root Element:
html
Root Namespace:
http://www.w3.org/1999/xhtml
The W3C validators are developed with assistance from the Mozilla Foundation, and supported by community donations.
Donate and help us build better tools for a better web.
Options
Show Source
Show Outline
List Messages SequentiallyGroup Error Messages by Type
Validate error pages
Verbose Output
Clean up Markup with HTML-Tidy
Help on the options is available.
↑ Top
Validation Output: 9 Errors
Line 7, Column 65: there is no attribute "mce_href"…p://www.tynon.com/tynon.ico" mce_href="http://www.tynon.com/tynon.ico" type="i…
✉
You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Line 9, Column 108: end tag for "link" omitted, but OMITTAG NO was specified…tylesheet" href="http://static1.ucimg.co/css/ldp/ldp.css?v_0.0.87" media="all">
✉
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 9, Column 1: start tag was here<link type="text/css" rel="stylesheet" href="http://static1.ucimg.co/css/ldp/ld…
Line 255, Column 72: required attribute "action" not specified <form id="sign_form" onsubmit="return false;" method="post">
✉
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>.
Line 264, Column 128: there is no attribute "datatype"…bindex="2" class="inputtext" datatype="e" nullmsg="Fill in please" errormsg="T…
✉
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.
Line 264, Column 140: there is no attribute "nullmsg"…lass="inputtext" datatype="e" nullmsg="Fill in please" errormsg="The email add…
✉
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.
Line 264, Column 166: there is no attribute "errormsg"…tatype="e" nullmsg="Fill in please" errormsg="The email address is incorrect"/>
✉
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.
Line 276, Column 170: end tag for "input" omitted, but OMITTAG NO was specified…s="btn_green" style="border: none;cursor:pointer;margin-top:3px;" tabindex="6">
✉
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
Line 276, Column 25: start tag was here <input id="signUp" type="submit" value="" name="submitS…
Line 304, Column 122: cannot generate system identifier for general entity "nn"…00"><a href="../index.php?r=siteIndex&nn=1" style="color: #C09F5B;font: arial;…
✉
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 304, Column 122: general entity "nn" not defined and no default entity…00"><a href="../index.php?r=siteIndex&nn=1" style="color: #C09F5B;font: arial;…
✉
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 304, Column 124: reference not terminated by REFC delimiter…"><a href="../index.php?r=siteIndex&nn=1" style="color: #C09F5B;font: arial;" …
✉
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 304, Column 124: reference to external entity in attribute value…"><a href="../index.php?r=siteIndex&nn=1" style="color: #C09F5B;font: arial;" …
✉
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 304, Column 124: reference to entity "nn" for which no system identifier could be generated…"><a href="../index.php?r=siteIndex&nn=1" style="color: #C09F5B;font: arial;" …
✉
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 304, Column 121: entity was defined here…E00"><a href="../index.php?r=siteIndex&nn=1" style="color: #C09F5B;font: arial…