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.
- If you're using a paid license of Movable Type Pro: Sign in to your account to download the update.
- If you're using the free Blogger license of Movable Type Pro: Grab the code from movabletype.com.
- If you're using Movable Type: The open source download is right here.
As always, Enterprise customers and licensees will be personally contacted by a Six Apart account representative.
phretor.myopenid.com
August 22, 2008 5:48 AM | Reply
An easy way to upgrade - but you must know what you're doing :)
I was moving from 4.2rc5 and I found this very useful to my end, though it may be the wrong way for you! So, beware ;)
And that's it. Just browse to your mt.cgi and get the MTOS automatically upgraded to MTOS 4.21.
Toni Hambilton
August 22, 2008 4:24 PM | Reply
Thank you so much. This little tip turned my upgrade into a 3 minute process.
dolmance
August 25, 2008 1:06 AM | Reply
I upgraded from 4.1 to 4.2 before this patch and I lost all my custom fields data. That means I've lost a lot information hosted in more than 2000 posts. You should create a little script in order to help us to recover it. Thanks.
demonsurfer
August 26, 2008 8:36 PM | Reply
Hello. MT4.21com - the archive index has a whole bunch of {/mt:Ignore} tags misplaced, so entire archive listings are ignored.. the first few types of archives on that template are ok, such as
<mt:Ignore> <!-- List of category archives, if category archives are enabled --> </mt:Ignore>but then most of the remaining ones the {/mt:Ignore} tag is placed right at the end of the code for each archive listing type, rather than at the end of the message above.
Also I entered ticket 81593 on fogbugz for another issue. A new install fixed the problem, so if someone can please delete that ticket it would be appreciated.
demonsurfer
August 29, 2008 7:12 PM | Reply
bump
JimAZtec
September 11, 2008 1:41 PM | Reply
I upgraded to from 4.12 everything went fine EXCEPT none of the comments appear. Even comment count does not show. What gives?
jkalweit.myopenid.com
September 26, 2008 11:49 AM | Reply
I upgraded to 4.21 from 4.2, and now under "Refresh Blog Templates", the "Apply a new template set" option is replaced by "Reset to factory defaults". Is there a different way to apply a new template set?