Mambo , warto ?

[andrzejj9]

Napisany przez misz_masz

Wedle mojej wiedzy nie da się. Zwyczajnie każda przeglądarka interpretuje troche inaczej pewne komponenty, moduły i tak to juz jest, że strona "pracuje".

No to co, Joomla jest niekompatybilna z Explorerem??

[MaciejT]

Napisany przez andrzejj9

No to co, Joomla jest niekompatybilna z Explorerem??

***379;e jak?? A od kiedy Explorer jest kompatybilny ze standardami W3C?

Sprawdz strone Validatorem (http://validator.w3.org/) i jesli sie validuje, to jest zrobiona poprawnie. Jesli sie nie validuje to popraw wskazane bledy, i wtedy strona bedzie zgodna ze standardami.
Jesli dalej w Explorerze bedzie wygladala zle, umiesc o tym informacje na swojej stronie, daj link do Validatora (od razu z referrerem, zeby zvalidowal w locie Twoja strone), i wyjasnij lagodnie, ze g***o Cie to interesuje, ze MS nie trzyma sie standardow (i znow link, tym razem do BrowseHappy).

[andrzejj9]

Napisany przez MaciejT

Że jak?? A od kiedy Explorer jest kompatybilny ze standardami W3C?

Sprawdz strone Validatorem (http://validator.w3.org/) i jesli sie validuje, to jest zrobiona poprawnie. Jesli sie nie validuje to popraw wskazane bledy, i wtedy strona bedzie zgodna ze standardami.
Jesli dalej w Explorerze bedzie wygladala zle, umiesc o tym informacje na swojej stronie, daj link do Validatora (od razu z referrerem, zeby zvalidowal w locie Twoja strone), i wyjasnij lagodnie, ze g***o Cie to interesuje, ze MS nie trzyma sie standardow (i znow link, tym razem do BrowseHappy).

Zły wygląd aż tak mi nie przeszkadza. Spróbuję z innym szablonem i powinno być dobrze. Bardziej martwi mnie to, że nie otwierają się obrazki, do których są hyperlinki (w postaci miniaturek)..

Sprawdziłem stronę validatorem i niestety nie wygląda to dobrze, wykrywa 18 błędów. Niektóre z nich wyglądają tak:

---------------------

Warning Line 23 column 101: cannot generate system identifier for general entity "no_html".

...gi.ovh.org/index2.php?option=com_rss&no_html=1" type="application/rss+xml" />

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

***9993;
Error Line 23 column 101: general entity "no_html" not defined and no default entity.

...gi.ovh.org/index2.php?option=com_rss&no_html=1" type="application/rss+xml" />

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.

***9993;
Warning Line 23 column 108: reference not terminated by REFC delimiter.

...org/index2.php?option=com_rss&no_html=1" type="application/rss+xml" />

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.

***9993;
Warning Line 23 column 108: reference to external entity in attribute value.

...org/index2.php?option=com_rss&no_html=1" type="application/rss+xml" />

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

***9993;
Error Line 23 column 108: reference to entity "no_html" for which no system identifier could be generated.

...org/index2.php?option=com_rss&no_html=1" type="application/rss+xml" />

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.

***9993;
Info Line 23 column 100: entity was defined here.

...ogi.ovh.org/index2.php?option=com_rss&no_html=1" type="application/rss+xml"..
Error Line 35 column 5: end tag for element "div" which is not open.

</div>

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.

***9993;
Error Line 41 column 48: there is no attribute "height".

...ign="top"><table width="1000" height="0" border="0" cellpadding="0" cellspaci

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.

***9993;
Error Line 45 column 156: required attribute "alt" not specified.

...d_left.png" width="28" height="191" /></td>

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

***9993;
Error Line 59 column 175: required attribute "alt" not specified.

...=2)" width="8" height="26" border="0"></div>

***9993;
Error Line 59 column 181: end tag for "img" omitted, but OMITTAG NO was specified.

...idth="8" height="26" border="0"></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 ">".

--------------------------------
Teraz pytanie - jak to poprawić. Instrukcje wydają się w miarę jasne (w miarę..), ale nie wiem, do którego pliku odnoszą się wskazówki typu "linia któraśtam". O który plik tu chodzi?