This page is not Valid XHTML 1.0 Transitional!

[gdblaster]

I tested my fresh install of SMF 1.1.2 with the W3 Markup Validator and the page was Valid XHTML 1.0 Transitional. No errors! Everything was perfect! After TP 0.9.7.1 installation (package-info.xml modified for 1.1.2) i tested again with the validator! And until now i have 5 errors in code without changing anything! Here is the code! I think anyone can see the errors doing the same steps!

Below are the results of checking this document for XML well-formedness and validity.

Error Line 173, column 103: there is no attribute "cellpadin" .
...border="0" cellspacing="0" cellpadin="0" width="100%"><tr><td align="center">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.

âÅ"‰

Warning Line 227, column 179: cannot generate system identifier for general entity "id" .
...itic.net/main/index.php?action=tpmod&id=shout" method="post"><input type="hidAn 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 227, column 179: general entity "id" not defined and no default entity .
...itic.net/main/index.php?action=tpmod&id=shout" method="post"><input type="hidThis 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 227, column 181: reference not terminated by REFC delimiter .
...ic.net/main/index.php?action=tpmod&id=shout" method="post"><input type="hiddeIf 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 227, column 181: reference to external entity in attribute value .
...ic.net/main/index.php?action=tpmod&id=shout" method="post"><input type="hiddeThis 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 227, column 181: reference to entity "id" for which no system identifier could be generated .
...ic.net/main/index.php?action=tpmod&id=shout" method="post"><input type="hiddeThis 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 227, column 178: entity was defined here .
...ritic.net/main/index.php?action=tpmod&id=shout" method="post"><input type="hiError Line 227, column 254: end tag for "input" omitted, but OMITTAG NO was specified .
...idden" name="tp-shout-name" value="">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 227, column 203: start tag was here .
...action=tpmod&id=shout" method="post"><input type="hidden" name="tp-shout-nameError Line 228, column 75: end tag for "input" omitted, but OMITTAG NO was specified .
..." type="hidden" value="action=forum"><input type="hidden" name="sc" value="e3âÅ"‰

Info Line 228, column 13: start tag was here .
             <input name="tp-shout-url" type="hidden" value="action=forum"><inpu

[Zetan]

I'm sure I posted this somewhere else today... Admin Zone maybe.. I forget.
Theres loads of sites that are not compliant. TinyPortal at the moment is not.
SMF is.

And if the site isn't compliant.. then I don't think the site should be displaying this:

Code Select Expand

<p>
    <a href="http://validator.w3.org/check?uri=referer"><img
        src="http://www.w3.org/Icons/valid-xhtml10"
        alt="Valid XHTML 1.0 Transitional" height="31" width="88" /></a>
  </p>

in the HTML.

Just my opinion. I'm going to try a clean my site up. I've fixed some errors, but I work a lot and don't get all the time I need to sort it all out.


ZTN

[IchBin]

The themes are compliant to my knowledge. TinyPortal is not the theme. When you start adding blocks and articles I think you'll find it nearly impossible to stay compliant.

[gdblaster]

ok ... thanks for the info ... but it was to nice if it was compliant

[IchBin]

Being compliant for TP is on the list. But there are a lot of things ahead of that.

[gdblaster]

that's a good news thanks

[BLueSS]

I just tried searching for any recent updates on this topic, but didn't find any (so bump, instead of new topic).

When I edit an html article in TP, it messes up the html a bunch and still isn't xhtml compatible.

One part in particular that is annoying is the auto "correcting" of
 to
 tags.

Are there any updates on making this valid??  I'm using 1.0 beta 4.

[IchBin]

Those types of errors are from the editor. Unfortunately, there isn't a lot we can do about the editor at this time as it is third party.

[BLueSS]

Are there other editors I can replace the default one with?

[IchBin]

Only if you know how to integrate them. There is quite a bit of work to make TP use an editor.