The ‘herders recently dropped $100 on getting the latest version of you (and I paid another $40 to get my own higher education version to use on CHLT), and now we’re starting to think that what we have now is actually worse than what we had before.
Your comment function doesn’t seem to work right. The TypeKey authentication system, which ought to be easy peasy, is confusing and apparently buggy. You encourage people to download and install MT-Blacklist, but when it doesn’t work (and trust me, there are lots of problems), you respond to questions with “We don’t support 3rd-party plugins.” Note that this particular plug-in is only available on your site. Why would you tell people to download and install something from your site and then refuse to help them when it doesn’t work?
If I were just starting out blogging, I’d be dropping you like a hot potato right now and asking for my money back (and perhaps going with Expression Engine or WordPress) because your software looks like it sucks: it’s not working right, the instructions are inadequate, and your customer support abdicates responsibility. Back when you were free, I was understanding, but we paid money for you. What happened? I have hundreds of blog entries stored in MT format, so I’m hesitant to switching to something else.
However, I’m not completely opposed to the idea, either. So are you gonna help us out or what?
P.S. Here’s the email I received in response to my query about errors in MT functions:
From: Movable Type Support
Date: 03 Dec 2004, 09:59:17 PM
Subject: Response to Movable Type support ticket ‘problems when commenting’
Movable Type Customer Support has responded to your ticket
‘problems when commenting’. This email notification has been
automatically sent by Movable Type Customer Support.
DO NOT REPLY TO THIS EMAIL. Instead, please click the link below
to view and respond to your ticket.
Hi, George. We are unable to provide support for MT
Blacklist errors since it is a third-party plugin. Please
post for assistance at the MT Blacklist forum:
You may also be able to seek a solution through our
Here’s what Jay Allen has to say about this same error (note that this is only one of many errors I’m encountering):
“Use of uninitialized value in concatenation (.) or string at /some/path/to/extlib/File/Spec/Unix.pm line 78”
Many people are reporting the “error” above. In fact, this a superfluous perl warning. It should affect absolutely nothing, and is in fact a bug (probably in MT) related to finding the plugin template files. Essentially MT tries several places to find the template files and if it doesn’t find them, the warning from that attempt is written out to the browser. Eventually though, the MT-Blacklist templates are found as evidenced by the fact that you have a full working page in front of you.
You should completely ignore this warning. I will attempt to suppress it in the next version.
You say it’s Jay Allen’s fault; he says it’s your fault. Have we paid $140 for the honor of getting the runaround?