Hello, I've posted two W3C validation errors that I'm getting obviously related to scripts run by Zymic. There is no script type within them such as 'text/script' is it possible to change this soon and allow W3C validation. Thanks
Validation Output: 2 Errors
1. Error Line 107, Column 62: required attribute "TYPE" not specified.
…<script src="http://www.hosting.zymic.com/fixstats.php"></script>
Error Line 107, Column 62: document type does not allow element "SCRIPT" here.
…<script src="http://www.hosting.zymic.com/fixstats.php"></script>
✉
The element named above was found in a context where it is not allowed. This could m
Full Version: W3c Validation Error
Zymic Webmaster Forums > Zymic Free Web Hosting > Zymic Free Web Hosting - General Discussion & Help
Sounds like this other thread: http://www.zymic.com/forum/index.php?showt...=W3C+validation
I get 4 errors total myself, same ones on all of my pages, just different lines. At this point all I can leave is the W3C CSS validation link because this inserted code BREAKS my pages in W3C validation.
The Error Messages
Part of the XHTML source code.
I get 4 errors total myself, same ones on all of my pages, just different lines. At this point all I can leave is the W3C CSS validation link because this inserted code BREAKS my pages in W3C validation.
The Error Messages
CODE
1. Error Line 70, Column 14: an attribute value must be a literal unless it contains only name characters
<script type=\"text/javascript\">
✉
You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.
2. Error Line 70, Column 33: document type does not allow element "script" here
<script type=\"text/javascript\">
✉
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).
3. Error Line 74, Column 14: an attribute value must be a literal unless it contains only name characters
<script type=\"text/javascript\">
✉
You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.
4. Error Line 74, Column 33: document type does not allow element "script" here
<script type=\"text/javascript\">
✉
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).
<script type=\"text/javascript\">
✉
You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.
2. Error Line 70, Column 33: document type does not allow element "script" here
<script type=\"text/javascript\">
✉
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).
3. Error Line 74, Column 14: an attribute value must be a literal unless it contains only name characters
<script type=\"text/javascript\">
✉
You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.
4. Error Line 74, Column 33: document type does not allow element "script" here
<script type=\"text/javascript\">
✉
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).
Part of the XHTML source code.
CODE
1.
2. <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
3. <html xmlns="http://www.w3.org/1999/xhtml">
4. <head>
.
.
.
68. </body>
69. </html>
70. <script type=\"text/javascript\">
71. var gaJsHost = ((\"https:\" == document.location.protocol) ? \"https://ssl.\" : \"http://www.\");
72. document.write(unescape(\"%3Cscript src=\'\" + gaJsHost + \"google-analytics.com/ga.js\' type=\'text/javascript\'%3E%3C/script%3E\"));
73. </script>
74. <script type=\"text/javascript\">
75. try {
76. var pageTracker = _gat._getTracker(\"UA-950416-50\");
77. pageTracker._trackPageview();
78. } catch(err) {}</script>
2. <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
3. <html xmlns="http://www.w3.org/1999/xhtml">
4. <head>
.
.
.
68. </body>
69. </html>
70. <script type=\"text/javascript\">
71. var gaJsHost = ((\"https:\" == document.location.protocol) ? \"https://ssl.\" : \"http://www.\");
72. document.write(unescape(\"%3Cscript src=\'\" + gaJsHost + \"google-analytics.com/ga.js\' type=\'text/javascript\'%3E%3C/script%3E\"));
73. </script>
74. <script type=\"text/javascript\">
75. try {
76. var pageTracker = _gat._getTracker(\"UA-950416-50\");
77. pageTracker._trackPageview();
78. } catch(err) {}</script>
What are your domains? We can fix this.
QUOTE(Bread @ Jul 17 2009, 08:57 PM) 
What are your domains? We can fix this.
domain URL: http://babic.zxq.net
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.