Also, because I'm pretty slow, it occured to me after writing that last post that some might question why we do these updates when things seem to be going fairly well.  I'll explain, since it's a good question I've asked myself with so little coffee and without the meds having kicked in yet.

We use the Telerik suite of ASP.Net Ajax controls for lots of stuff.  The part your users (as guild admins) see most is the editor and, while it has been problematic at times, it is the best one out there for our platform, in my opinion.  We've gone through others:

• CuteEditor. It was cute, we'll give it that, but didn't play well with non-IE browsers when we tried it.
• CKEditor. Which was open source, and had a zero-day vulnerabilities that spread like wildfire -- specifically, a hacker could gain direct access to the web server file system through a glitch in the upload feature.
• HtmlTextBox from ActiveUp. Very bad cross-browser when we tried it. ComponentArt Editor. This was the closest in features, but by far, the most difficult to extend with custom functionality (like the WowHead item insert, YouTube embed code, custom emoticons, etc).

This isn't meant to be a review, because it's been years since we've even taken a look at any of these; it's just something harmless for me to type up while I wake up. No wait, I was getting to a point... Ah yes, why we update!

Seems like everybody's going subscription these days.  Telerik's actually been doing it for a very long time, and we pay an annual subscription fee to them for their entire suite of controls.  For here, on the site, we use their ASP.Net Ajax controls (and hopefully we'll get to use more of the Silverlight stuff moving forward!).  Internally, we use their WinForms and WPF controls for our admin application -- our side of the support ticket system is not web based and requires elevated database permissions, and it's faster to whip up a form in a Windows app than a web app, especially one that updates the database.

So, we pay the subscription, and these guys are really good about releasing a pretty decent update every quarter, followed shortly thereafter by a service pack.  I know, I know, a lot of people on GP think I'm the only person who produces buggy code.  It just ain't so.

I wait until a couple weeks after the release of the first or second service packs to any major quarter-level release before I start testing it in dev.  I really, really do try to avoid having you folks test anybody's code but mine.  *ducks*

Here's the thing: if we fall, say, two releases behind, we run the risk of having to deal with all of the headaches of two major updates at one time, and the support expertise of the Telerik staff will be focused on the newest release, so we may have extremely long wait times between our reporting a problem, and them addressing it.  Many of you experienced this with the last go-round, and that was a contributing factor to the delay.

If we're at a point where everything seems to be running along smoothly, it's especially hard for me to justify, even to myself, updating.  However, we've all seen browser manufacturers decide to switch things up on us apparently for the fun of it, and if we're not up to the latest (or close to it) release of the editor and other controls, we run a big, big risk of going a long time with... broke stuff.

So that, in something that resembles nothing like a nutshell, is why we need to keep up on the updates.

Hmmm... K, will check it out.

Thanks a bunch, Mottie -- fix for both issues being pushed in the next 10-15.

@Aaron

The problem is the CSS added to the page (line 521 in these admin forums, in red below)

<style type="text/css">
        #bodyTransbackInterior { -moz-border-radius: 2px; -webkit-border-radius: 2px; -border-radius: 2px; padding: 5px; }
        #editorSubject, .editorContent, .editorOptions, .editorButtons { padding: 3px; padding-top: 5px; }
        .editorOptions { text-align: right; }
        .editorOptions a, a:link, a:visited, a:active { text-decoration: underline; }
        #editorSubjectLabel { text-align: left; font-weight: bold; }
        #editorButtons { text-align: left; }
        #editorSubject { margin-bottom: 5px; }
        .errDiv { padding-top: 300px; padding-bottom: 300px; text-align: center; }
</style>

The line should be like this:

.editorOptions a { text-decoration: underline; }

Also, the popup window showing previous posts has a problem with the opacity slider (at least in Firefox). It seems to me that there is no background color applied until the opacity is 100% - it jumps from transparent background to 100% opaque. Here are some screen shots:

About 80%  Opacity
100% Opacity