I got a panicked message from my blog's author -- they had created a new entry, then published it. The individual archive appeared okay, but the entry didn't appear on the homepage. When they tried to delete and recreate the post, they got this error on republishing:

"Error in <MTEntries> tag: Error in <MTEntryID>tag:"
(That's the full text of the error)

I logged in as them and looked at the entries. At the top of the list, the latest entry was there, but with no title; clicking on it reavealed no contents at all. I tried to delete, but after deleting, the entry STILL SHOWED UP IN THE LIST.

Deeply spooked, I tried re-publishing, and got the same error.

Going back to the blog admin screen, I moused over the entries, and noticed that the "id" querystring parameter was missing a value. The link looked like this:
"[blog url]/admin/mt.cgi?__mode=view&_type=entry&id=&blog_id=2" <-- note missing value for "id"
...while the entry previous to it looked like this:
"[blog url]/admin/mt.cgi?__mode=view&_type=entry&id=137&blog_id=2"

So I tried following the bum link and manually adding in "138" for "id", since that was the next number.
Voila, the post popped up, and I was able to "save" it, at which time it appeared TWICE in the entry list, both with the same ID. I checked ONE of the two posts and deleted, and it went away this time. Now the blog is able to republish.

So it seems obvious that a post got mis-published in the database, and its "id" parameter didn't get saved in one or more necessary places. My questions to you guys are:
* Has anyone seen this behavior before?
* Any theories about what might have happened?
* Any suggestions about recommended prudent next steps -- any maintenance tasks to clean the database? Upgrade to 3.3? Tip out a libation?

Thanks very much for any thoughts!

What database are you using? You may be able to use phpMyAdmin and look at the mt_entry table to find that bad entry. Don't delete anything from the database directly without making a backup first!

I'm using MySQL, and have access both through phpMyAdmin and the command line. I'm less worried about clearing up this particular problem (looks like I was able to delete out the offending entry just by guessing the ID number), and more worried about the same thing happening again. Is this a sign of things to come, I wonder -- is this a sign of a buggy install, or should I just file under "one of those things"?

I haven't seen a report like that before, so it's a new one to me.

I would try repairing your database tables to see if there's some corruption there.

Also, you really should upgrade to 3.33 as it's to be considered a mandatory update. Please do take steps to ensure you have the latest code.

http://www.sixapart.com/movabletype/news/2...03_updates.html