Just a quick one for anyone using Movable Type who has yet to upgrade to version 4.2: Don’t. Despite more than two months of public beta testing I’d wait for the next round of bug fixes (I should have learned this by now).
Perhaps the most serious problem so far affects anyone using Custom Fields. From the #movabletype IRC channel via ProNet:
Upgrading an mt 4.1 install to 4.2 that has custom fields data for more than 100 objects of a given type (for example, more than 100 entries have custom entry field data) will result in partial custom field data loss… the bug is that only some of the entries have their entry_meta data moved to the mt_entry_meta table, then the entry_meta column in the mt_entry table is deleted so whatever has not been migrated to the new mt_entry_meta table is gone for good.
This happened to me: random latitudes, longitudes, Wikipedia links and temperatures on Pepys’ Diary entries disappeared. I had a backup of the 4.1 database but had to spend much of yesterday coding something to extract that data and put it into the new database, hoping I was doing it correctly. Data loss caused by an upgrade really should be something that’s picked up before a final release.
Someone else on ProNet reported several problems, such as inaccurate search results and the system asking to be upgraded several times. One oddity I’ve found is with the recently_commented_on attribute of the MTEntries tag. With MT 4.1 this showed the n most recent entries to receive comments. After the upgrade, on most but not all of my blogs, it only showed one or two or three entries.
The solution, for reasons which escape me, are to add the limit attribute with a high value:
<MTEntries recently_commented_on="10" limit="100"> ... </MTEntries>
Incidentally, the documentation for recently_commented_on suggests its value is the number of days to use to limit the number of entries, when in fact it’s simply the number of entries to display. Incomplete documentation is another current problem with MT.