derek765
Regular
Joined: Sep 27, 2012
Posts: 99
Location: Okinawa, Japan
|
Posted:
Sun Nov 25, 2012 2:35 am |
|
I just did a Markup Validation of my website, and got 6 errors.
The errors recieved:
Code: Line 366, Column 148: there is no attribute "onMouseover"
… 2px; padding-left: 4px;" onMouseover="copyspeed=pausespeed" onMouseout="copys…
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.
|
Code:Line 366, Column 182: there is no attribute "onMouseout"
…: 4px;" onMouseover="copyspeed=pausespeed" onMouseout="copyspeed=marqueespeed">
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.
|
Code:Line 140, Column 133: document type does not allow element "table" here
…"left" cellspacing="0" cellpadding="2"><tr><td style="background-color: #00000…
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).
|
Code:Line 376, Column 38: general entity "file" not defined and no default entity
<a href="modules.php?name=Forums&file=search">Forum Search</a><br />
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.
|
Code:Line 376, Column 42: reference to entity "file" for which no system identifier could be generated
<a href="modules.php?name=Forums&file=search">Forum Search</a><br />
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.
|
Code:Line 379, Column 54: there is no attribute "onClick"
…ast" style="cursor: pointer;" onClick="copyspeed=copyspeed+1; mqs=marqueespeed…
✉
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.
|
|
|
|
neralex
Site Admin
Joined: Aug 22, 2007
Posts: 1774
|
Posted:
Sun Nov 25, 2012 6:23 am |
|
It seems you are using 3rd party scripts (blocks or modules) in RN, because the in the core RN package are the attributes written small. If you want use an xHTML code, then you must follow the instructions of the validator and you must write the following atrributes without big letters:
onmouseover
onmouseout
onclick
Code:Line 140, Column 133: document type does not allow element "table" here
|
Here i can only say it again: follow the instructions in the error message.
Code: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).
|
Deactivate your added 3rd party scripts and check it again. If you have found the script with this line, then you must write it correct.
This one: "forums.html?file=search" is an result of activated shortlinks but without added rewrite rules. Follow the instructions in the htaccess file and use the rewrite rules from the ShortLinks.htaccess on the right place in the htacess file.
Code:# -------------------------------------------
# If you use TegoNuke(tm) ShortLinks with RavenNuke(tm) then copy your ShortLinks.htaccess file/rules below inbetween
# the <IfModule> and </IfModule> tags.
# Only process if mod_rewrite is installed
# -------------------------------------------
<IfModule mod_rewrite.c>
# TegoNuke(tm) ShortLinks - ShortLinks.htaccess file/rules should go after this line
|
|
_________________ Github: RavenNuke |
|