Yeah, so much for the upgrade going off without a hitch.

All appeared to be well until I went to check one of the shorts pages for xhtml validation and it failed — but not because of anything I’d added.

What is failing is a new script injection by the underlying content engine that isn’t valid code.  Oh, it works — it’s just not valid code in xhtml strict.

Nobody will notice it from a user side, but it irritates the hell out of me.  I spent hours researching and recoding regurgitated code from places like Facebook so the crap would validate and still function properly.

I’ve got a support topic posted on the content creation forum, but that’s always hit and miss.  I assume I’m not the only one who gives a shit about proper validation.  Somebody has probably figured it out, and I’m not afraid to tinker with default files if necessary ( though not having to do that was part of what I loved about the content creation system in the first place. )  The issue is whether any of said people will see the topic on the forum and bother to respond.

I really don’t want to have to dig through the distribution files to fix this myself.  I don’t have the time for that kind of crap any more :S

It’s not really a bug in the product, so I can’t submit a ticket about it.  All I can do is make a suggestion that it be changed in the next update, and that’s even more hit and miss than somebody answering a support topic.

Yeah, I’m a little pissed.  Some of the recoding I did to make junk code like the Facebook plugin on the front page work while validating was incredibly annoying, and all that work is essentially down the drain until/unless I can fix this problem as well.

Paid for an upgrade, and there are some nice features on the backend that I’m pleased with, but it also broke validation in the process.

It really fucking honks me off.

I’ll quit ranting now.  Just had to let this vitriol out somewhere 😛