firefox zeigt ein template von meinem shop anders an

    hallo!

    ich bin ein absoluter firfox fan aber 2 sachen sind sehr schade!

    1. ich habe einen shop erstellt und der wird im ie 6 richtig angezeigt aber im firefox ist das template nicht komplett?!
    2. wenn ich in den adminbereich des shops gehe ist dieser nicht vollständig. d. h. bei dem what you see ... editor nicht komplett.

    kann man das irgendwie abstellen? denn ich möchte den ie 6 eigentlich gar nicht mehr benutzen.

    so ein mist, sorry das ich meinen beitrag in das falsche thema gesetzt habe.

    deine Probleme lassen dadrauf schließen das ie standard benutzt wurde und sich nicht an den w3c standard gerichtet worden ist ;).

    aber mit einer demo könnte man dir sicherlich besser helfen.

    mmh, das schmeißt die seite mir dann raus:

    keine ahnung.

    Below are the results of attempting to parse this document with an SGML parser.

    1.

    Line 26, column 29: required attribute "TYPE" not specified

    <script language="javascript"><!--

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

    ✉
    2.

    Line 72, column 29: required attribute "TYPE" not specified

    <script language="javascript"><!--

    ✉
    3.

    Line 80, column 35: there is no attribute "LEFTMARGIN"

    <body bgcolor="#FFFFFF" leftmargin="0" topmargin="0" bottommargin="0" rightmarg

    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.

    ✉
    4.

    Line 80, column 49: there is no attribute "TOPMARGIN"

    <body bgcolor="#FFFFFF" leftmargin="0" topmargin="0" bottommargin="0" rightmargin="">

    ✉
    5.

    Line 80, column 67: there is no attribute "BOTTOMMARGIN"

    ...FFFFF" leftmargin="0" topmargin="0" bottommargin="0" rightmargin="">

    ✉
    6.

    Line 80, column 83: there is no attribute "RIGHTMARGIN"

    ...in="0" bottommargin="0" rightmargin="">

    ✉
    7.

    Line 80, column 85: document type does not allow element "BODY" here

    ...="0" bottommargin="0" rightmargin="">

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

    ✉
    8.

    Line 81, column 27: there is no attribute "HEIGHT"

    <table width="100%" height="600" border="0" cellpadding="0" cellspacing="0">

    ✉
    9.

    Line 84, column 64: there is no attribute "BACKGROUND"

    ...n="6" valign="top"><table background="templates/knopptemp/img/logo_bg.png" wi

    ✉
    10.

    Line 88, column 108: required attribute "ALT" not specified

    ...mg/logo.png" width="429" height="121"></div></td>

    ✉
    11.

    Line 97, column 25: there is no attribute "BACKGROUND"

    <td background="templates/knopptemp/Bilder/knoppshop_04.jpg" width="44

    ✉
    12.

    Line 126, column 153: cannot generate system identifier for general entity "XTCsid"

    ....http://knoppshop.de/shop/index.php…d64cd8343b1da3c"

    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 "&" (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.

    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.

    ✉
    13.

    Line 126, column 153: general entity "XTCsid" not defined and no default entity

    ....http://knoppshop.de/shop/index.php…d64cd8343b1da3c"

    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.

    ✉
    14.

    Line 126, column 159: reference to entity "XTCsid" for which no system identifier could be generated

    ...http://shop.de/shop/index.php…d64cd8343b1da3c">Leine

    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.

    ✉
    15.

    Line 126, column 152: entity was defined here

    ...http://w.knoppshop.de/shop/index.php…d64cd8343b1da3c
    16.

    Line 126, column 287: reference to entity "XTCsid" for which no system identifier could be generated

    ...http://shop.de/shop/index.php…d64cd8343b1da3c">Spiel

    ✉
    17.

    Line 126, column 152: entity was defined here

    ...http://w.knoppshop.de/shop/index.php…d64cd8343b1da3c
    18.

    Line 126, column 402: reference to entity "XTCsid" for which no system identifier could be generated

    ...http://hop.de/shop/index.php…d64cd8343b1da3c">Zubeh

    ✉
    19.

    Line 126, column 152: entity was defined here

    ...http://w.knoppshop.de/shop/index.php…d64cd8343b1da3c
    20.

    Line 126, column 515: reference to entity "XTCsid" for which no system identifier could be generated

    ...http://shop.de/shop/index.php…d64cd8343b1da3c">Büc

    ✉
    21.

    Line 126, column 152: entity was defined here

    ...http://w.knoppshop.de/shop/index.php…d64cd8343b1da3c
    22.

    Line 126, column 635: reference to entity "XTCsid" for which no system identifier could be generated

    ...http://ppshop.de/shop/index.php…d64cd8343b1da3c">Ges

    ✉
    23.

    Line 126, column 152: entity was defined here

    ...http://w.knoppshop.de/shop/index.php…d64cd8343b1da3c
    24.

    Line 161, column 165: reference to entity "XTCsid" for which no system identifier could be generated

    ...e/shop/shop_content.php?coID=1&XTCsid=093ed99ae98da536ad64cd8343b1da3c">Versa

    ✉
    25.

    Line 126, column 152: entity was defined here

    ...http://w.knoppshop.de/shop/index.php…d64cd8343b1da3c
    26.

    Line 161, column 289: reference to entity "XTCsid" for which no system identifier could be generated

    ...e/shop/shop_content.php?coID=2&XTCsid=093ed99ae98da536ad64cd8343b1da3c">Daten

    ✉
    27.

    Line 126, column 152: entity was defined here

    ...http://w.knoppshop.de/shop/index.php…d64cd8343b1da3c
    28.

    Line 161, column 411: reference to entity "XTCsid" for which no system identifier could be generated

    ...e/shop/shop_content.php?coID=3&XTCsid=093ed99ae98da536ad64cd8343b1da3c">Unser

    ✉
    29.

    Line 126, column 152: entity was defined here

    ...http://w.knoppshop.de/shop/index.php…d64cd8343b1da3c
    30.

    Line 161, column 534: reference to entity "XTCsid" for which no system identifier could be generated

    ...e/shop/shop_content.php?coID=4&XTCsid=093ed99ae98da536ad64cd8343b1da3c">Impre

    ✉
    31.

    Line 126, column 152: entity was defined here

    ...http://w.knoppshop.de/shop/index.php…d64cd8343b1da3c
    32.

    Line 161, column 654: reference to entity "XTCsid" for which no system identifier could be generated

    ...e/shop/shop_content.php?coID=7&XTCsid=093ed99ae98da536ad64cd8343b1da3c">Konta

    ✉
    33.

    Line 126, column 152: entity was defined here

    ...http://w.knoppshop.de/shop/index.php…d64cd8343b1da3c
    34.

    Line 198, column 144: there is no attribute "BORDER"

    ...german/button_quick_find.gif" border="0" alt="Suchen!" title=" Suchen! "></..

    ✉
    35.

    Line 236, column 205: reference to entity "XTCsid" for which no system identifier could be generated

    ...roduct_info.php?products_id=66&XTCsid=093ed99ae98da536ad64cd8343b1da3c"><img

    ✉
    36.

    Line 126, column 152: entity was defined here

    ...http://w.knoppshop.de/shop/index.php…d64cd8343b1da3c
    37.

    Line 236, column 312: required attribute "ALT" not specified

    ...mbnail_images/KSV1002.jpg" border="0"></a><br> Calming Sig

    ✉
    38.

    Line 278, column 61: an attribute value must be a literal unless it contains only name characters

    ...s="main"><P align=center><FONT color=#ffcc33 size=4>Herzlich Willkommen auf u

    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.

    ✉
    39.

    Line 281, column 2: document type does not allow element "P" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag

    <P></P>Daher finden Sie bei uns z.B. keine schmerzauslösenden Erziehungshilfen

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

    ✉
    40.

    Line 282, column 2: document type does not allow element "P" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag

    <P></P>Nur was für unsere eigenen Hunde gut genug ist, wird auch in unser Sorti

    ✉
    41.

    Line 283, column 2: document type does not allow element "P" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag

    <P></P>Viel Spaß beim stöbern!</FONT></STRONG></FONT><BR>

    ✉
    42.

    Line 283, column 45: end tag for element "STRONG" which is not open

    <P></P>Viel Spaß beim stöbern!</FONT></STRONG></FONT><BR>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occured in a script section of your document, you should probably read this FAQ entry.

    ✉
    43.

    Line 283, column 52: end tag for element "FONT" which is not open

    <P></P>Viel Spaß beim stöbern!</FONT></STRONG></FONT><BR>

    ✉
    44.

    Line 285, column 30: an attribute value must be a literal unless it contains only name characters

    <DIV align=center><FONT color=#ffcc33><STRONG><BR><FONT face=Verdana size=4>Das

    ✉
    45.

    Line 286, column 32: required attribute "ALT" not specified

    <img src="/design/startbild.jpg"><br></DIV></DIV><br> </td>

    ✉
    46.

    Line 346, column 62: document type does not allow element "TABLE" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag

    ...100%" cellspacing="0" cellpadding="0"><form name="login" method="post" action

    ✉
    47.

    Line 346, column 164: reference to entity "XTCsid" for which no system identifier could be generated

    .../shop/login.php?action=process&XTCsid=093ed99ae98da536ad64cd8343b1da3c">

    ✉
    48.

    Line 126, column 152: entity was defined here

    ...http://w.knoppshop.de/shop/index.php…d64cd8343b1da3c
    49.

    Line 346, column 198: document type does not allow element "FORM" here

    ...sid=093ed99ae98da536ad64cd8343b1da3c">

    ✉
    50.

    Line 347, column 17: document type does not allow element "TR" here

    <tr>

    ✉
    51.

    Line 350, column 17: document type does not allow element "TR" here

    <tr>

    ✉
    52.

    Line 353, column 17: document type does not allow element "TR" here

    <tr>

    ✉
    53.

    Line 356, column 17: document type does not allow element "TR" here

    <tr>

    ✉
    54.

    Line 359, column 17: document type does not allow element "TR" here

    <tr>

    ✉
    55.

    Line 362, column 26: end tag for "TABLE" which is not finished

    </form></table>

    Most likely, You nested tags and closed them in the wrong order. For example <p><em>...</p> is not acceptable, as <em> must be closed before <p>. Acceptable nesting is: <p><em>...</em></p>

    Another possibility is that you used an element (e.g. 'ul') which requires a child element (e.g. 'li') that you did not include. Hence the parent element is "not finished", not complete.

    ✉
    56.

    Line 378, column 19: end tag for element "P" which is not open

    </p>

    Ich hab das ganze jetzt nur mal überflogen. Diese Zeilen sagen mir, daß du eine Tabelle dicht gemacht hast, die noch nicht korrekt beendet war, und das du <TR> Elemente verwendet hast, da wo sie nicht sein dürfen. Dazu kommt noch, daß du ein </P> irgendwo hast, das kein <P> als Gegenstück hat.

    Das scheinen die Hauptprobleme zu sein. Der Rest sieht mir nicht ganz so schlimm aus.

    Sagt ihr jemand, dass du schließen sollst?
    Ausbessern!!!

    Kannst du es dir wirklich erlauben, annährend 20 % deiner Kundschaft wegzuschicken?

    Edit: die Zahl bezieht sich auf http://www.spiegel.de/netzwelt/techn…,326109,00.html
    und ist damit nicht völlig aus der Luft gegriffen. Und nicht jeder hat noch zusätzlich nen IE in Reichweite - ich hab jedenfalls keinen.


    ..and some might argue that the earth is flat
    ..and some might argue that smoking is not harmful
    ..and some might argue that even Windows XP has become stable

    ohne sich die seite anschauen zu können, kann da garniemand was dazu sagen. und das hat auch weniger mit php zu tun, als schicht und einfach damit, dass eine tabelle innerhalb der seite nicht ordentlich geschlossen wurde.