Results 1 to 6 of 6
  1. #1
    Join Date
    Aug 2006
    Posts
    52
    Plugin Contributions
    0

    help question My website not compatible?

    hello

    Ive noticed that my site looks completely different on some browsers. I searched the forums and found the page validator . I came up with 17 errors. What I'm not understanding is the technical language. Can someone halp me sort through this. I have a habit of going in and changing the file and messing things up. Heres what i came up with: Below are the results of checking this document for XML well-formedness and validity.

    1. Error Line 195 column 84: end tag for "div" omitted, but OMITTAG NO was specified.

    ...c/images/mirrorbottom.png" /> --></td>

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


    2. Info Line 67 column 0: start tag was here.

    <div id="navColumnOneWrapper" style="width: 160px"><!--// bof: categories //-->

    3. Error Line 215 column 64: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified.

    ...ntent" class="content"><table border=0 width="80%" align="center"><tr><td bgc


    4. Error Line 215 column 109: an attribute value must be a literal unless it contains only name characters.

    ..."80%" align="center"><tr><td bgcolor=#D0ECEE colspan=2 height=150>

    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.


    5. Error Line 215 column 125: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified.

    ...ter"><tr><td bgcolor=#D0ECEE colspan=2 height=150>


    6. Error Line 215 column 134: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified.

    ...<td bgcolor=#D0ECEE colspan=2 height=150>


    7. Error Line 216 column 99: required attribute "alt" not specified.

    ...templates/classic/images/siloa.gif" /><font size="5"><span style="font-family

    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>.


    8. Error Line 216 column 770: an attribute value must be a literal unless it contains only name characters.

    ...pan></font></td></tr><tr><td bgcolor=#F7F6CA width="40%" height=150>


    9. Error Line 216 column 797: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified.

    ...d bgcolor=#F7F6CA width="40%" height=150>


    10. Error Line 217 column 82: required attribute "alt" not specified.

    ...templates/classic/images/silob.gif" /><span style="font-family: gabrielle,ari


    11. Error Line 217 column 333: an attribute value must be a literal unless it contains only name characters.

    ...sans-serif;"></span></span></td><td bgcolor=#C99BC6 rowspan=2>


    12. Error Line 217 column 349: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified.

    ...pan></span></td><td bgcolor=#C99BC6 rowspan=2>


    13. Error Line 218 column 133: required attribute "alt" not specified.

    ...es/english/images/turquoise clutch" /><img vspace="0" hspace="0" border="0" a


    14. Error Line 218 column 306: required attribute "alt" not specified.

    ...anguages/english/images/red clutch" /><img style="width: 202px; height: 142px


    15. Error Line 218 column 435: required attribute "alt" not specified.

    ...nguages/english/images/blue clutch" /><br />


    16. Error Line 219 column 26: an attribute value must be a literal unless it contains only name characters.

    </td></tr><tr><td bgcolor=#F3CDE3 height=150>


    17. Error Line 219 column 41: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified.

    </td></tr><tr><td bgcolor=#F3CDE3 height=150>


    18. Error Line 220 column 82: required attribute "alt" not specified.

    ...templates/classic/images/siloc.gif" /> <br /> <spa




    Sorry this is so long. Thanks for your help..

  2. #2
    Join Date
    Jan 2004
    Posts
    66,364
    Blog Entries
    7
    Plugin Contributions
    274

    Default Re: My website not compatible?

    Most of the issues are related to how you built your table-related tags, etc. Each element should be assigned a value enclosed in quotes.

    Thus for example, this:
    HTML Code:
    <td bgcolor=#D0ECEE colspan=2 height=150>
    would become something like this:
    HTML Code:
    <td bgcolor="#D0ECEE" colspan="2" height="150">

    The discussion about IMG tags not containing ALT references ... means you need to add an alt element to your IMG tags ... something like this:
    HTML Code:
    <img src="green.jpg" alt="this is green" />
    Fixing those kinds of things will help narrow your list.
    Of course, if your site is all tables-based for layout, then this is a pain to tidy.
    .

    Zen Cart - putting the dream of business ownership within reach of anyone!
    Donate to: DrByte directly or to the Zen Cart team as a whole

    Remember: Any code suggestions you see here are merely suggestions. You assume full responsibility for your use of any such suggestions, including any impact ANY alterations you make to your site may have on your PCI compliance.
    Furthermore, any advice you see here about PCI matters is merely an opinion, and should not be relied upon as "official". Official PCI information should be obtained from the PCI Security Council directly or from one of their authorized Assessors.

  3. #3
    Join Date
    Aug 2006
    Posts
    52
    Plugin Contributions
    0

    xhtml problem Re: My website not compatible?

    Thank you for that. Is there a way to find out what files to edit. I tried the developers tool kit , but it found nothing.

  4. #4
    Join Date
    Oct 2006
    Location
    Cheney WA
    Posts
    26
    Plugin Contributions
    0

    Default Re: My website not compatible?

    You already know where the problems are, you just have to read between the lines. Like this.

    1. Error Line 195 column 84: end tag for "div" omitted, but OMITTAG NO was specified.

    ...c/images/mirrorbottom.png" /> --></td>

    Answer: your missing the closing element. Search for that line and make sure that every <*> has a </*> at the end of the line. THe * is a wildcard for one or two letters, for inssance the </td> at the end of that line should have a <td> just above the line somewhere before the next </td>.

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


    2. Info Line 67 column 0: start tag was here.

    <div id="navColumnOneWrapper" style="width: 160px"><!--// bof: categories //-->

    Answer: You're missing a quotation mark in front of 160px. it should look like this "160px".

    3. Error Line 215 column 64: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified.

    ...ntent" class="content"><table border=0 width="80%"
    align="center"><tr><td bgc

    Answer: Not sure about this one, but If you cange the 80% to the actuaul width of the table, you should fix the problem. Select the table in your design program and it should show you the actual width.


    4. Error Line 215 column 109: an attribute value must be a literal unless it contains only name characters.

    ..."80%" align="center"><tr><td bgcolor=#D0ECEE colspan=2 height=150>

    Answer: Put Parenthises around 150, llike this, 2 height="150">

    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.


    5. Error Line 215 column 125: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified.

    ...ter"><tr><td bgcolor=#D0ECEE colspan=2 height=150>

    Answer: Same fix as 4.

    6. Error Line 215 column 134: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified.

    ...<td bgcolor=#D0ECEE colspan=2 height=150>

    Answer: Same fix as 4.


    7. Error Line 216 column 99: required attribute "alt" not specified.

    ...templates/classic/images/siloa.gif" /><font size="5"><span style="font-family

    Answer: This shouldn't cause any visual problems, unelss there is an <alt> tag above this line, but still this shouldn't cause any problems.

    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>.


    8. Error Line 216 column 770: an attribute value must be a literal unless it contains only name characters.

    ...pan></font></td></tr><tr><td bgcolor=#F7F6CA width="40%" height=150>

    Answer: Again with the percentages, findthand put quotes around 150 (height="150">


    9. Error Line 216 column 797: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified.

    ...d bgcolor=#F7F6CA width="40%" height=150>

    Answer: Again with the percentages, findthand put quotes around 150 (height="150">


    10. Error Line 217 column 82: required attribute "alt" not specified.

    ...templates/classic/images/silob.gif" /><span style="font-family: gabrielle,ari

    Answer: This shouldn't cause any visual problems, unelss there is an <alt> tag above this line, but still this shouldn't cause any problems.


    11. Error Line 217 column 333: an attribute value must be a literal unless it contains only name characters.

    ...sans-serif;"></span></span></td><td bgcolor=#C99BC6 rowspan=2>

    Answer: rowspan="2">


    12. Error Line 217 column 349: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified.

    ...pan></span></td><td bgcolor=#C99BC6 rowspan=2>

    Answer: rowspan="2">


    13. Error Line 218 column 133: required attribute "alt" not specified.

    ...es/english/images/turquoise clutch" /><img vspace="0" hspace="0" border="0" a

    Answer: Check that alt tag again.

    Well you get the idea by now. Just find those pages and fix the errors as best as you can.

    Good luck!

    JP

  5. #5
    Join Date
    Mar 2005
    Location
    Tempe, AZ
    Posts
    324
    Plugin Contributions
    0

    Default Re: My website not compatible?

    How do i fix this line

    Line 56, Column 32: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    document.write("<script id=__ie_onload defer><\/script>");
    Lextechs.com Powered By ZenCart

  6. #6
    Join Date
    Mar 2005
    Location
    Tempe, AZ
    Posts
    324
    Plugin Contributions
    0

    Default Re: My website not compatible?

    I started out at 200 errors most i have fixed myself and got my home page down to 27 Errors, 4 warning(s). I posted the rrors and woarns if anyone has fixed these can you please let me know Thanks

    # Error Line 56, Column 32: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified

    document.write("<script id=__ie_onload defer><\/script>");


    # Error Line 56, Column 49: the name and VI delimiter can be omitted from an attribute specification only if SHORTTAG YES is specified

    document.write("<script id=__ie_onload defer><\/script>");



    "VI delimiter" is a technical term for the equal sign. This error message means that the name of an attribute and the equal sign cannot be omitted when specifying an attribute. A common cause for this error message is the use of "Attribute Minimization" in document types where it is not allowed, in XHTML for instance.

    How to fix: For attributes such as compact, checked or selected, do not write e.g <option selected ... but rather <option selected="selected" ...
    # Error Line 56, Column 49: required attribute "type" not specified

    document.write("<script id=__ie_onload defer><\/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>.
    # Error Line 56, Column 49: document type does not allow element "script" here

    document.write("<script id=__ie_onload defer><\/script>");



    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).
    # Warning Line 56, Column 50: character "<" is the first character of a delimiter but occurred as data

    document.write("<script id=__ie_onload defer><\/script>");



    This message may appear in several cases:

    * You tried to include the "<" character in your page: you should escape it as "&lt;"
    * You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    * Another possibility is that you forgot to close quotes in a previous tag.

    # Error Line 110, Column 115: document type does not allow element "script" here

    …ipt/cot.js" type="text/javascript" /></script>



    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 122, Column 68: required attribute "type" not specified

    …fe.com/private/rollover/rollover.js"></script><span id="BuySafeSealSpan"><scr



    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>.
    # Error Line 198, Column 10: ID "navMain" already defined

    <div id="navMain"><div id="logo"><a href="http://www.lextechs.com/"><img src="in



    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).
    # Info Line 131, Column 13: ID "navMain" first defined here

    <div id="navMain">

    # Error Line 198, Column 28: ID "logo" already defined

    <div id="navMain"><div id="logo"><a href="http://www.lextechs.com/"><img src="in



    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).
    # Info Line 144, Column 13: ID "logo" first defined here

    <div id="logo"><a href="http://www.lextechs.com/"><img src="includes/templat

    # Error Line 233, Column 31: document type does not allow element "td" here; assuming missing "tr" start-tag

    <td align="center" colspan="2">


    # Error Line 235, Column 111: document type does not allow element "link" here

    …ss" type="text/css" media="screen" />



    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 409, Column 277: Attribute "oncontextmenu" is not a valid attribute

    …to see a BBB report." oncontextmenu="alert('Use without permission is prohibi



    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 409, Column 445: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag

    …aus, Inc.'); return false;" /></a><p><a href="http://www.lextechs.com/index.p



    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
    # Error Line 409, Column 599: end tag for "p" omitted, but OMITTAG NO was specified

    …all our Credentials</b></a></p></div></div>



    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
    # Info Line 408, Column 61: start tag was here

    …id="hackersideboxContent" class="sideBoxContent"><p></p><p><!-- Start bbbonline-->

    # Error Line 443, Column 353: end tag for "hr" omitted, but OMITTAG NO was specified

    …increased as of 1/2/08</a><br /><hr><a href="http://www.lextechs.com/index.ph



    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
    # Info Line 443, Column 348: start tag was here

    …ates increased as of 1/2/08</a><br /><hr><a href="http://www.lextechs.com/ind

    # Error Line 468, Column 4: document type does not allow element "ul" here; assuming missing "li" start-tag

    <ul>


    # Error Line 471, Column 6: end tag for "li" omitted, but OMITTAG NO was specified

    </div>



    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
    # Info Line 468: start tag was here

    ><ul>

    # Error Line 471, Column 6: end tag for "ul" omitted, but OMITTAG NO was specified

    </div>



    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
    # Info Line 457: start tag was here

    ><ul>

    # Error Line 521, Column 96: character "/" is not allowed in the value of attribute "target"

    …ws__mid--109914.html" target="https://www.shopzilla.com"><img src="https://ww



    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.
    # Warning Line 526, Column 92: cannot generate system identifier for general entity "utm_source"

    …hs.1-866-569-9443?utm_medium=widget&utm_source=MClogo" target="_new" style="b



    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 "&amp;" (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 &aelig; 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.
    # Error Line 526, Column 92: general entity "utm_source" not defined and no default entity

    …hs.1-866-569-9443?utm_medium=widget&utm_source=MClogo" target="_new" style="b



    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.
    # Warning Line 526, Column 102: reference not terminated by REFC delimiter

    …69-9443?utm_medium=widget&utm_source=MClogo" target="_new" style="border:none



    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.
    # Warning Line 526, Column 102: reference to external entity in attribute value

    …69-9443?utm_medium=widget&utm_source=MClogo" target="_new" style="border:none



    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 '&amp;'.
    # Error Line 526, Column 102: reference to entity "utm_source" for which no system identifier could be generated

    …69-9443?utm_medium=widget&utm_source=MClogo" target="_new" style="border:none



    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.
    # Info Line 526, Column 90: entity was defined here

    …echs.1-866-569-9443?utm_medium=widget&utm_source=MClogo" target="_new" style=

    # Error Line 526, Column 253: required attribute "alt" not specified

    …_widget1.gif" style="border:none;" /></a>



    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>.
    # Error Line 56, Column 31: XML Parsing Error: AttValue: " or ' expected

    document.write("<script id=__ie_onload defer><\/script>");


    # Error Line 56, Column 31: XML Parsing Error: attributes construct error

    document.write("<script id=__ie_onload defer><\/script>");


    # Error Line 56, Column 31: XML Parsing Error: Couldn't find end of Start Tag script line 56

    document.write("<script id=__ie_onload defer><\/script>");


    # Error Line 56, Column 50: XML Parsing Error: StartTag: invalid element name

    document.write("<script id=__ie_onload defer><\/script>");


    # Error Line 110, Column > 80: XML Parsing Error: Opening and ending tag mismatch: head line 3 and script

    …secure.comodo.net/trustlogo/javascript/cot.js" type="text/javascript" /></scr…


    # Error Line 111, Column 7: XML Parsing Error: Opening and ending tag mismatch: html line 2 and head

    </head>
    Lextechs.com Powered By ZenCart

 

 

Similar Threads

  1. My ZenCart not compatible on dreamhost php 5.4
    By deltasoft in forum Upgrading to 1.5.x
    Replies: 7
    Last Post: 5 Nov 2014, 09:14 PM
  2. My header is not cross browser compatible
    By bonnit in forum Templates, Stylesheets, Page Layout
    Replies: 9
    Last Post: 22 Feb 2011, 12:55 PM
  3. Group Pricing addon not compatible with 1.3.9g
    By wexzone in forum All Other Contributions/Addons
    Replies: 0
    Last Post: 24 Oct 2010, 03:27 PM
  4. Host site not compatible with Zen Cart?
    By missterri in forum General Questions
    Replies: 17
    Last Post: 16 Apr 2008, 04:50 PM
  5. Is Zen Cart compatible with a MS Office Live website?
    By shoponlyhere in forum General Questions
    Replies: 4
    Last Post: 8 Jan 2008, 08:43 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