Frown, Darn Ya, Frown! Not Quite Fixed After All.

Writing these daily updates on our server woes is starting to feel like delivering State of the Union addresses every afternoon the week after a direct nuclear strike on the heartland of America. “My fellow Americans, while all of Idaho’s potatoes have mutated into shambling, blood-thirsty spudstronsities, the good news is that they remain fluorescent but edible.” “Many Americans have noticed their pineal gland pustulously expanding into a literal third eye. We ask you all to look at the bright side: not only will you now be able to see invisible Cthulhu monsters ectoplasmically swimming through the air, but at least those freaky Kodak advertisements now make sense.”

Anyway, obviously, we spoke a bit prematurely yesterday: we are almost but not quite fixed. The remaining problems of which we are currently aware:

1) Black text on black background. A lot of you guys are reporting this. Please let us know what OS and browser you are using. I’ve tried reproducing this in Firefox, Opera and Safari to no avail; on the other hand, I’ve had this happen in the past when the site was healthy. A reload usually solved it then, so be sure to give it a try.

2) RSS feeds are not working. Anything under “Read More” doesn’t come through and the subject links are still borked.

3) You’re having a hard time commenting, either through logging in or being told that your “Comment Can Not Be Posted.” If the former, please try using the Forgot Your Password link, just to make sure you’re using the right log-in. If the latter, try logging out and logging back in again… that’s a long standing issue.

If we’re missing anything or you have any more light to shed upon these issues, mail us and we’ll do what we can.

Again, sorry for the mess, but rest assured… we’re in the homestretch. Pregnant pause, fraught with insinuation. We think.


Edit Your Comment

  1. ModerateSnark says:

    I commented on this under “We’re fixed”, but it bears repeating:

    Beware the percent sign when commenting on interest rates or discounts. Comments containing percent signs are getting blocked with a “try again later!” message since the Movable Type “upgrade.”

    Also, plus signs disappear:

    Principal (plus) Interest becomes
    Principal Interest.

    There could be other “special character” problems, but these are the only ones I’ve noticed so far.

    I don’t know much about Movable Type, but there may be some override character to put in front of a percent sign that would allow it to be entered. Does anyone know?

  2. Ishmael says:

    I’m posting just because I can.


  3. ModerateSnark says:

  4. ModerateSnark says:

    Hee hee, I may have figured this out, too. For the post above, I entered a percent sign followed by “20” which y’all have seen here and there in URLs substituting for a space, right? (It’s hexadecimal.) So, if I’m right, I can achieve the elusive percent sign by using a percent sign followed by “25”:


  5. ModerateSnark says:


    …and % 2B (without a space between) should get me a plus sign…
    (Note that I had to type a percent sign and “25 2B” to get the above.)

    % + % + % + % + % + % + % + %

  6. Mauvaise says:

    Re. #1 – I had this happend a couple times yesterday. I’m running Windows XP (not my choice) and using Firefox. A refresh did correct the problem so I didn’t think of reporting it, but I guess it wasn’t just me.

  7. mschlock says:

    RSS XML Parse Error indeed.

    You’re just teasing me now, aren’tcha…

  8. Gina Trapani says:

    Ha! HA! HA!! HA!!!!

    Welcome to my new hell.

  9. ModerateSnark says:

    Update: % and + are fixed. I just typed them normally here.