Subscribe
In recent days two significant issues in the Movable Type 4.2 release were reported by our community. One of these bugs can potentially result in some form of limited data loss, and the other could cause loss of some configuration data in some circumstances. We have reproduced these issues as quickly as possible, and created patches to remedy the problems. Most users are not at any risk from these issues, but here are the circumstances under which you may have been affected:
Custom fields data. If you are upgrading from Movable Type Commercial or Enterprise 4.1 to Movable Type Pro or Enterprise 4.2 and you are using custom fields on any object in Movable Type and there are more than 100 rows in the table for that object, some of your custom field data could be lost in the migration.
Archive mappings. If you create a new blog on your Movable Type 4.2 installation and you delete an archive mapping from one of the archive templates, this action will remove the rest of your blog archive mappings inadvertently.
Both of these issues have been fixed and verified by our quality assurance team. The fixes can be found in the newly released Movable Type 4.21, a free update for all users of Movable Type 4.2. If you've downloaded 4.2, but have not yet upgraded, please download 4.21 first and then upgrade.
As always, please make a backup before performing any system update or upgrade.
To the best of our knowledge, only a very small number of people have been affected by this bug. To those people, we offer our sincerest apologies for any inconvenience or frustration. We work our hardest to prevent issues of this sort. It's thanks to our community that we've been able to find, fix, and respond to this issue so quickly. We appreciate your participation, and we thank you for using Movable Type.
Creating Drop-Down Navigation with Movable Type
Creating Drop-Down Navigation with Movable Type