SitePoint Sponsor

User Tag List

Results 1 to 6 of 6
  1. #1
    SitePoint Member
    Join Date
    Apr 2008
    Posts
    3
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Validation Error Confusion

    Have created and published a web using FrontPage 2000. When I checked it at w3.0rg they found a problem with a missing DOCTYPE, which I later learned was not included in FrontPage, so I searched for, and finally decided to add the code for 3.2, so older browsers could load the web (I think that was the correct choice). But the validator says that although the DOCTYPE is no longer an issue, the document is not valid HTML 3.2. I am not using frames, and I don't think it is transitional, or strict, but I confess I don't understand those terms. Also, I keep getting an error message that the HTML code Microsoft Theme cannot have a space in it, yet when I remove the space, the theme disappears from the web pages. I have other issues as well, but could use some very simple explanations and help with these!

    Thanks!

  2. #2
    Programming Team silver trophybronze trophy
    Mittineague's Avatar
    Join Date
    Jul 2005
    Location
    West Springfield, Massachusetts
    Posts
    17,290
    Mentioned
    198 Post(s)
    Tagged
    3 Thread(s)

    validation problems

    Hi Kim143, welcome to the forums,
    I can't say what is causing the validation to fail without knowing what errors the w3c validator shows. Please post them, or at least a representative sample if there's a lot of them.
    I don't know if it will work, but you could try "url encoding" the space, ie.
    "Microsoft%20Theme"

  3. #3
    SitePoint Member
    Join Date
    Apr 2008
    Posts
    3
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Validation Errors summary

    Hi, Mittineague,

    Thanks for your quick response. I tried the %20, but it just removed the theme and background from the page and the navigation buttons. (The code was generated by FrontPage!) Following are the errors noted by w3

    Line 14, Column 21: value of attribute "NAME" must be a single token.
    <meta name="Microsoft Theme" content="windborne 001, default">✉
    This attribute can not take a space-separated list of words as a value, but only one word ("token"). This may also be caused by the use of a space for the value of an attribute which does not permit it.

    Line 15, Column 21: value of attribute "NAME" must be a single token.
    <meta name="Microsoft Border" content="none, default">✉
    This attribute can not take a space-separated list of words as a value, but only one word ("token"). This may also be caused by the use of a space for the value of an attribute which does not permit it.

    Line 18, Column 153: there is no attribute "FACE".
    k="#666666"><!--mstheme--><font face="Arial Narrow">✉
    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 20, Column 15: document type does not allow element "P" here.
    <p align="left"><img border="0" src="Red-tailed_hawk7.jpg" width="234" height="1✉
    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).

    Line 22, Column 40: document type does not allow element "P" here.
    <!--msthemeseparator--><p align="center"><img src="_themes/windborne/bstrrul.gif✉
    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).

    Line 23, Column 15: document type does not allow element "P" here.
    <p align="left">&nbsp; <span style="background-color: #FFCC66"><!--webbot✉
    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).

    Line 23, Column 35: there is no attribute "STYLE".
    <p align="left">&nbsp; <span style="background-color: #FFCC66"><!--webbot✉
    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 23, Column 62: element "SPAN" undefined.
    n="left">&nbsp; <span style="background-color: #FFCC66"><!--webbot✉
    You have used the element named above in your document, but the document type you are using does not define an element of that name. 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 "Frameset" document type to get the "<frameset>" element),
    by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).

    Line 28, Column 2: document type does not allow element "P" here.
    <p>Windborne Press publishes books on a range of subjects, including Alzheimer's✉
    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).

    Line 31, Column 2: document type does not allow element "P" here.
    <p><img border="1" src="New_Cover_1.jpg" width="135" height="195" align="left">O✉
    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).

    Line 33, Column 2: document type does not allow element "P" here.
    <p><font face="Times New Roman"> <span style="text-transform: uppercase"> <b> A✉
    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).

    Line 33, Column 72: element "SPAN" undefined.
    man"> <span style="text-transform: uppercase"> <b> A✉
    You have used the element named above in your document, but the document type you are using does not define an element of that name. 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 "Frameset" document type to get the "<frameset>" element),
    by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).

    Line 37, Column 2: document type does not allow element "P" here.
    <p>The book focuses on Alzheimer's disease sufferers✉
    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).

    Line 40, Column 2: document type does not allow element "P" here.
    <p>More information can be found on the <a href="featured_title.htm">Featured✉
    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).

    Line 43, Column 2: document type does not allow element "P" here.
    <p>&nbsp;</p>✉
    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).

    Line 45, Column 2: document type does not allow element "P" here.
    <p>In 2008 Windborne Press absorbed the list of <font color="#000099"> poetry, e✉
    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).

    Line 49, Column 2: document type does not allow element "P" here.
    <p>&nbsp;</p>✉
    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).

    Line 51, Column 2: document type does not allow element "P" here.
    <p><font face="Felix Titling" size="5"><i>Windborne Press LLC 2008</i></font><✉
    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).

  4. #4
    Programming Team silver trophybronze trophy
    Mittineague's Avatar
    Join Date
    Jul 2005
    Location
    West Springfield, Massachusetts
    Posts
    17,290
    Mentioned
    198 Post(s)
    Tagged
    3 Thread(s)

    doctype

    Having a doctype, any doctype, should stop the w3c validator from complaining about there not being one. The trick is to use the right one. You can either use a doctype that goes along the HTML mark-up you're using, or change the HTML to comply with the doctype. For example, if I want to use frames, I need to use a frameset doctype or not use frames. If I want to use certain tags or attributes, eg. "target", then I need to use a transitional doctype or not use the tags/attributes.
    I guessing that it would be easier for you to find a doctype that suits the mark-up created by FrontPage rather than fix the HTML to conform to a particular doctype. This is a problem with "page creating" applications (AFAIK only with dreamweaver is it possible to create valid mark-up) and a reason I prefer to hand-code.
    For example the "current" standard is to keep style in CSS and out of the HTML. Hence some of the "style" errors.
    In any case, I can see by the valdator errors that you should not use a strict doctype. Nor is it likely that you should use an XHTML doctype.
    This leaves 3 choices
    • HTML 4.01 Transitional
    • HTML 3.2
    • HTML 2.0

    the doctypes are
    HTML Code:
    <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
       "http://www.w3.org/TR/html4/loose.dtd">
    HTML Code:
    <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
    HTML Code:
    <!DOCTYPE html PUBLIC "-//IETF//DTD HTML 2.0//EN">
    To be clear, you tried the HTML 3.2 doctype and the validator said "This page is not Valid HTML 3.2!" and gave the above errors?

  5. #5
    SitePoint Member
    Join Date
    Apr 2008
    Posts
    3
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Still Confused on Validation Situation

    Hi Mittrineague, Sorry to have taken so long to get back to you. This has been one hectic week. Yes, the response we get is that the 3.2 is not valid. It is so frustrating to have created a website that cannot be found by search engines. Nothing in FrontPage indicates that this would be a problem. I just don't know what to do next.

  6. #6
    SitePoint Enthusiast
    Join Date
    Apr 2008
    Location
    UK
    Posts
    41
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Quote Originally Posted by Kim143 View Post
    Hi Mittrineague, Sorry to have taken so long to get back to you. This has been one hectic week. Yes, the response we get is that the 3.2 is not valid. It is so frustrating to have created a website that cannot be found by search engines. Nothing in FrontPage indicates that this would be a problem. I just don't know what to do next.
    Maybe put the site online and provide a link to it in this forum and we could take a look. Learning html may be an advantage to you too, it won't take long and it is worth it if you are planning on running your own site.

    Also, using html 3.0 is not going to give you any distinct advantages as most pople browse on internet explorer 6.0+ or firefox 2.0+ and they can parse all forms of html. Stick with xhtml and it will pay for itself later when you can understand what all the errors are stating.

    Seriously though, if you want to stay away from validation errors, then hand coding is key. I have not come accross a GUI editor yet that produces perfect markup.

    Thats my contribution anyway. Don't worry and keep smiling.
    Ash

    :-D


Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •