Is it just me? Or has anyone else noticed that links inside of comments are being eaten by MT ever since the upgrade to 2.661? Nothing in my sanitize spec has changed and I have the href option listed in the default config, but MT seems to be ignoring my settings and eating that option out of any anchor tags coded by hand in my comments. Damned annoying and I'm not sure how to fix it.

Suggestions?

Weblog Config/Preferences

is Auto-link URLs? checked?
is Allow HTML in comments? checked?

No, and yes. I'm a long time MT user, something this simple wouldn't have gotten by me. I've not made any config changes between upgrading from 2.65 and 2.661. The anchor tags are still there, just the HREF option has been eaten as though it's not defined in the Sanitize specs, but it is.

Okay, just to test, I'm running 2.661 with "a href" defined in my Sanitize Specs, and I just left a gratuitous link to MT in my own comments. So it's most likely you specifically - and I mean that in a nice way. If the "a" is in there, can you think of anything else that's changed? How about on thehosting end?

Donna

Yeah, I had a feeling it was specifically me when I couldn't find anyone else talking about it in the forums here. :-)

I tried re-uploading the full install of 2.661 to see if perhaps I missed a file during the upgrade process, but that didn't help. I'll have to go through my plugins and see if I can identify if any of the ones I'm using are responsible.

Thanks, I just wanted to check and see if anyone else had noticed an issue.

OK, looks like I managed to figure this out. I had an older copy of the QuickCodes plugin installed and with the upgrade to 2.661 it seemed to be causing the problem I was having. Now that I've upgraded that to the latest release things are once again back to normal.

Yay me.

Checking for plugin conflicts was a genius idea; I've seen that work before and I'm now officially filing that away in my "possible resolutions for unexplained behavior" file. Good work!