1. previous post: The Great Category Implosion of 2004
  2. next post: Still Life Photography How-To

De-Spamming Accident Kills 20 — Film at 11

Filed under “Blogging
by Adam at 10:43 PM on November 15, 2004

4 Comments

I screwed up while de-spamming my photoblog with the latest MT-Blacklist and ended up deleting all of the last 20 comments. If you said anything there in the last four months (yeah, 20 comments in 4 months — pretty sad) then it’s now toast. My condolences.

Please don’t try to re-post any comments, at least not yet. I’m working with my hosting provider to try and get a more current backup than the one I have from late September (doh!), and even that one will still cover 2/3 of the lost time period. Just a heads-up.

Updates:

  • 11-17-2004, 6pm-ish — The lost comments haven’t been restored yet, but an upgrade to MT 3.121 has taken care of the error Chris mentioned in the comments. Meanwhile, I’ve disabled comments on the photoblog until the backup comes through from tech support so I don’t get any new comments I’ll have to replace by hand or something. MT really just shouldn’t display a comment form at all once you’ve disabled comments in the weblog configuration. Instead, it continues showing the comment form and gives your visitors an obscure error message about needing to register. But I turned off comments from even registered members! :-/

    Oh well. One more reason to be frustrated with Movable Type.

  • 11-29-2004, 11:41pm — I’ve re-enabled comments on the photoblog, and I’m writing off the ones that were deleted as lost. My apologies to anyone whose comments were affected.
Adam is a web developer and graphic designer who lives and works in south-central Kansas. He likes to speak his mind, both here and in his business blog. He only rarely writes about himself in the third person, honest. If you’d like to work with Adam, drop him a line.

4 Comments

  1. Hi Adam,
    Sorry to hear about your spam accident that’s a bloody tradgedy.

    The rest of this comment is slightly off topic:
    I had a problem similar to one of your other problems on my website. I’m sure you have fond memories of the following error.

    Can’t call method “id” on an undefined value at lib/MT.pm line 770.

    I have had the exact same problem on my site. I found the problem to be caused by a miss spelling when including a header on my site. I was using the mt include tag and I accidently typed newhooter instead of newfooter. When I changed it back to newfooter the problem went away.

    So if you know anyone else who has a similar problem just get them to check the spelling on their mt include tags.

    Comment by Chris Fryer — November 16, 2004 @ 12:00 am

  2. Yeah Adam, I wonder why millions aren’t rushing in to our blogs to comment. Waiting for the flood. Keep doing pal,

    Comment by josh — November 16, 2004 @ 7:43 pm

  3. Chris: Thanks for the pointer, but I didn’t change any template module names between MT 3.0 and 3.11. I’ve checked the templates and everything seems kosher. An upgrade looks like the only way to fix it, unfortunately.

    Josh: I think it just takes people a little while to recognize genius like ours. ;-)

    Comment by Adam M. — November 17, 2004 @ 1:47 pm

  4. Onward to WP 1.3!
    My test blog has moved from Movable Type 3.x to an alpha version of WordPress 1.3……

    Trackback by Timing Interval — November 18, 2004 @ 4:28 pm

Sorry, comments have been closed for this entry.