Thread: W3c Errors

Page 1 of 3 123 LastLast
Results 1 to 10 of 25
  1. #1
    Join Date
    Nov 2011
    Posts
    97
    Plugin Contributions
    0

    Default W3c Errors

    hi guys and girls
    i have been doing a bit of seo on my site and have checked the w3c validation but i am getting errors.
    can some one please help i have done some of the errors but the remaining i cannot find were (which file) and how i have to change
    something to do with  :: 
    www dot leedskoiandpondcentre dot co dot uk
    Thanksin advance

  2. #2
    Join Date
    Feb 2005
    Location
    Lansing, Michigan USA
    Posts
    20,024
    Plugin Contributions
    3

    Default Re: W3c Errors

    It looks like you have set the EZpage separator to :: . Since you aren't displaying them anyway, try changing them to just the   in Admin - Configuration - EZ Pages Settings. Your template designer has made the EZ page links into list items, which may be causing the problem.
    Last edited by stevesh; 5 Feb 2014 at 10:01 PM.

  3. #3
    Join Date
    Nov 2011
    Posts
    97
    Plugin Contributions
    0

    Default Re: W3c Errors

    Quote Originally Posted by stevesh View Post
    It looks like you have set the EZpage separator to :: . Since you aren't displaying them anyway, try changing them to just the ## in Admin - Configuration - EZ Pages Settings. Your template designer has made the EZ page links into list items, which may be causing the problem.
    Hi
    have just tried changing to  
    now get this if you would kindley look ?

  4. #4
    Join Date
    Nov 2011
    Posts
    97
    Plugin Contributions
    0

    Default Re: W3c Errors

    Your template designer has made the EZ page links into list items

    How do you mean?

  5. #5
    Join Date
    Nov 2011
    Posts
    97
    Plugin Contributions
    0

    Default Re: W3c Errors

    i have just set the ezy settings to blank no &nbs; errors gone now but will this affect anything but now i have more errors?
    thanks

  6. #6
    Join Date
    Jul 2005
    Location
    Upstate NY
    Posts
    22,010
    Plugin Contributions
    25

    Default Re: W3c Errors

    No it will not hurt to eliminate the separator; your template handles the ez-page links as list items, so the separator's purpose of distinguishing between links is not needed.

  7. #7
    Join Date
    Nov 2011
    Posts
    97
    Plugin Contributions
    0

    Default Re: W3c Errors

    Thanks
    Now I have more errors can anyone advise and also do I have to check every page or is there a way to check every page automatically.
    Thanks

  8. #8
    Join Date
    Jul 2005
    Location
    Upstate NY
    Posts
    22,010
    Plugin Contributions
    25

  9. #9
    Join Date
    Nov 2011
    Posts
    97
    Plugin Contributions
    0

    Default Re: W3c Errors

    If you could take a look at my home page and view page source .
    Isn't w3c errors damage how my site is ranked just trying to get my site ranking better
    Thanks

  10. #10
    Join Date
    Nov 2011
    Posts
    97
    Plugin Contributions
    0

    Default Re: W3c Errors

    Quote Originally Posted by scooby3134 View Post
    If you could take a look at my home page and view page source .
    Isn't w3c errors damage how my site is ranked just trying to get my site ranking better
    Thanks
    PROBLEMS

    Line 560, Column 22: end tag for "img" omitted, but OMITTAG NO was specified

    alt="web counter"></a></div></noscript>

    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 571, Column 97: document type does not allow element "link" here

    …eet" type="text/css" href="http://www.heartinternet.co.uk/eu-cookie/main.css"/>

    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

    Error Line 573, Column 108: there is no attribute "read_more"

    …tinternet.co.uk/eu-cookie/require-opt-in.js" read_more=privacy-polivy></script>

    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.

    Error Line 573, Column 108: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified

    …tinternet.co.uk/eu-cookie/require-opt-in.js" read_more=privacy-polivy></script>

    Line 574, Column 8: required attribute "type" not specified

    <script>

    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 591, Column 7: end tag for "div" omitted, but OMITTAG NO was specified

    </body></html>


    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">"

    Any Help Apreciated
    Thanks

 

 
Page 1 of 3 123 LastLast

Similar Threads

  1. v151 W3C errors
    By Renz in forum General Questions
    Replies: 9
    Last Post: 8 Nov 2013, 02:51 AM
  2. v150 w3c validation errors with dynamicfilterContent output
    By Darion in forum General Questions
    Replies: 8
    Last Post: 13 Feb 2013, 12:00 AM
  3. W3C and W3CS validation errors
    By Yiannis in forum Templates, Stylesheets, Page Layout
    Replies: 9
    Last Post: 27 Jul 2010, 08:52 AM
  4. W3C Markup Validation Errors Help
    By mw4kids in forum General Questions
    Replies: 3
    Last Post: 12 Nov 2009, 05:04 AM
  5. W3C Errors
    By thefashionhut in forum General Questions
    Replies: 3
    Last Post: 24 Feb 2009, 04:25 PM

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
  •  
disjunctive-egg
Zen-Cart, Internet Selling Services, Klamath Falls, OR