Now comments are screwed up, too
Comments: 7
MT-Blacklist stopped working a couple of days ago. I started getting this error:
An error occurred: Byte order is not compatible at blib/lib/Storable.pm (autosplit into blib/lib/auto/Storable/thaw.al) line 363, at [path to MT] lib/MT/PluginData.pm line 28
I installed the latest beta and it started working again … for a little while. Then the error came back. I have no idea what it means.
So now comment moderation is back on, but there’s another problem. MT has stopped mailing me comments as they come in so in order to see new comments, I have to go to MT and wade through pages and pages of spam (literally hundreds of fucking spam comments: I’m getting absolutely hammered here) to try to identify legitimate comments.
So, if you’re wondering why your comment hasn’t shown up, that’s why. With sincere apologies. I barely have time to bathe these days so it remains to be seen when I’m going to get a decent chance to look at this.
•••
Posted to MetaStuff • 2005.02.10 (Thu) • 22:27
Comments
Posted by chrisb 2005.02.11, 07:15
There is a known bug within MT 3.14 that stops the moderated comment emails from being sent - however after installing MT-Blacklist they seem to return to normal, not that this will help you when your MT-Blacklist is broken :)
In regards to your broken MT-Blacklist, there seems to be some related chatter over in the MT-Blacklist forums. Hope this helps.
Posted by lil 2005.02.11, 13:23
Jeremy, Have you tried contacting SegPub about it? That happened to me as well as few months ago and they tried to help me fix the problem. It turns out if was related to them moving my site to another server, and it’s working as it should now…just a thought.
Posted by jh 2005.02.11, 15:06
lil —- I didn’t have to contact SegPub: they contacted me. :-)
I’ll say it again, it pays to host with the best.
The problem seems to be solved. I reinstalled Blacklist and seem to be back in business. Also made some changes (as you probably noticed, having had to go through an extra step to post a comment —- sorry) that ought to give Blacklist a bit less work to do in the first place.
Fingers crossed.
Posted by jh 2005.02.11, 15:40
And, Chris, thanks for the link.
Posted by yafujifide 2005.02.14, 02:04
Do like I did, and quit using MT.
I built my own very simple CMS instead. I have greater control, and no comment spam. Of course, right now I don’t have comments at all, but I’ll add that feature soon enough.
Posted by olivier 2006.05.01, 14:00
FWIW, and since all I could find on the Web on this topic were cries of despair and not a lot of solutions, here’s one that works.
connect to the SQL database holding MT info, and drop the rows about mt_blacklist, a la:
delete from mtplugindata where plugindataplugin=”Blacklist”;
This appears to work. Why the Storable perl module wouldn’t be able to read the SQL data anymore when you change hardware is beyond me, though.
Oh, and for those using db_files instead of SQL, I’m afraid you’re out of luck.
Posted by olivier 2006.05.01, 14:02
… and it’s official: Your website eats underscores.
Post a comment:
Send This Story to an Enemy
• • •
