Hi wishy,
I'm sure you're aware of these issues and more but there are two basic problems with the CMS output that prevent it from validating properly. One is the CMSSESSID entity that seems to get injected into every page link whether dynamic or manually added to a template. I think it just needs to be close with a semicolon and/or have the ampersand not being properly escaped. I'm not even going to try to hack this myself.
And the other is simply that generated input tags from certain plugins aren't self-closing.
e.g.
I think the majority of these are generated by the search plugin and represent an easy fix.
Thanks!
2c,
Paul
CMS output validation
Re: CMS output validation
The svn dailys fix the CMSSESSID problem for all php versions above 4.3.2. As for the search plugin, that's an easy fix. I'll look into it quickly tonight.
Re: CMS output validation
Just committed the fix for the serarch plugin. Was easy. Thanks for pointing it out!
-
iNSiPiD
Re: CMS output validation
Hi again,
One more slight modification needed to get XHTML 1.0 strict validation. It seems input tags are inline elements and need to be wrapped in a block element. Apparently a form tag isn't good enough.
The simplest fix I've found which also allows more complete styling of the form's elements is to wrap a div around them as a child to the form. Wrapping the entire form is also invlaid.
Also, if you could stick with the supplied id name I won't need to change anything.
Note that I've also removed the (redundant?) value="utf-8"> from the input fields as this seems to be the default for CMS anyway.
And adding a value parameter for the text box would allow people to put in some default text.
One more slight modification needed to get XHTML 1.0 strict validation. It seems input tags are inline elements and need to be wrapped in a block element. Apparently a form tag isn't good enough.
The simplest fix I've found which also allows more complete styling of the form's elements is to wrap a div around them as a child to the form. Wrapping the entire form is also invlaid.
Also, if you could stick with the supplied id name I won't need to change anything.
Note that I've also removed the (redundant?) value="utf-8"> from the input fields as this seems to be the default for CMS anyway.
And adding a value parameter for the text box would allow people to put in some default text.
