https://buy-zithromax.online buy kamagra usa https://antibiotics.top buy stromectol online https://deutschland-doxycycline.com https://ivermectin-apotheke.com kaufen cialis https://2-pharmaceuticals.com buy antibiotics online Online Pharmacy vermectin apotheke buy stromectol europe buy zithromax online https://kaufen-cialis.com levitra usa https://stromectol-apotheke.com buy doxycycline online https://buy-ivermectin.online https://stromectol-europe.com stromectol apotheke https://buyamoxil24x7.online deutschland doxycycline https://buy-stromectol.online https://doxycycline365.online https://levitra-usa.com buy ivermectin online buy amoxil online https://buykamagrausa.net

Upgrading … pardon my dust

Doing the upgrade now … if things seem to be not working (this front page should stay in place), that’s what’s up. UPDATE: No. Server traffic (mutter mutter) is…

Doing the upgrade now … if things seem to be not working (this front page should stay in place), that’s what’s up.

UPDATE: No. Server traffic (mutter mutter) is making things too unstable (mutter grumble) to dare doing the upgrade process right now (curse mutter grumble). I’ll have to try it tonight over over the weekend.

UPDATE (10 p.m. Friday night): Traffic is down to manageable levels (helped by some strategic IP banning, I think), so now’s the time.

44 view(s)  

8 thoughts on “Upgrading … pardon my dust”

  1. Okay, I got the 3.34 files uploaded (well, first I uploaded the 3.33 files again by accident, but who’s counting?). I’ve renamed the TB and Comment scripts as before. And everything *looks* like it’s 3.34iffic.

    Let’s see if a comment will save.

    … and, no, it won’t. Ah. Need to reflag various .cgi files to 755 so that they can execute. Let’s try that.

  2. Bingo.

    Interestingly, though the upgrade process pointed toward a video that was made for the 3.2 upgrade, I didn’t get any sort of upgrading script execution when I first started up. Weird. And irksome. And annoying that the whole 755 thing wasn’t documented.

  3. Well, I’ve been using it since, oh, early 2002 (when I hopped over from Blogger). It was what folks around me were using, and seemed as reasonable a choice at the time as any other.

    Over the years, I’ve been pleased with MT as a local (non-hosted) service, its extremely flexible templating language, and the array of plug-ins developed for it. I’ve been displeased by the limitations/problems of Perl, and the increasing repositioning by 6A of MT for the business, rather than personal, market (which makes great sense for them, but doesn’t help me all that much).

    If I were choosing afresh today, I’m not sure if MT’s the direction I’d go, but I’m not enthused about actually moving to a different platform without a lot more reason. Which isn’t to say it couldn’t happen, but I’ve a lot of other Big Projects on my list that I’d want to tackle first. 😛

Leave a Reply

Your email address will not be published. Required fields are marked *