CMS output validation
Posted: Tue Jul 05, 2005 12:54 am
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
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