June 2005 Archives
We are pleased to announce that the release of Movable Type 3.2 is nearly upon us. Feature development for this version was driven almost entirely by requests from our community of users and, therefore, the changes are tightly focused around the way you use the software. Overall, Movable Type 3.2 makes all the common tasks we perform with Movable Type much more satisfying.
Between now and the time it is released, we will be covering "Our 32 Favorite features in Movable Type 3.2" on the Professional Network weblog. Though we'll only be covering highlights of the new version, this release features over 100 new features and improvements. We're sure all users will find this to be a significant update.
Today we are releasing a patch to fix an issue for customers running Movable Type versions 3.16 or 3.17 and using UTF-8 character encoding on their weblogs. Specifically, a bug introduced in Movable Type 3.16 causes the dirify routine to preserve dashes in transformed text where, historically, it has suppressed them. This could be problematic because the dirify routine is used to create all URLs in Movable Type.
While default Movable Type installations are not adversely affected by this bug, there are certain common or legacy customizations (which will be detailed below) that could cause problems. For that reason, if you are using UTF-8 and MT 3.16 or 3.17, we suggest that you download and install the patch just to be safe. The steps are as follows:
- Download the patch plugin (1K): tar/gzip (good for Unix), zip (good for Windows)
- Uncompress the file as you would Movable Type (e.g. double click it or use a decompression program like Winzip or Stuffit)
- Upload the uncompressed file (named patch-20050616-utf8dirify-nodash.pl) to the 'plugins' folder of your main Movable Type application directory.
- Rebuild any templates or archives that published statically
More details on the bug and the patch can be found below. We apologize for any inconvenience that this may have caused and thank those of you who brought the issue to light.
Today we are releasing Movable Type 3.17. This release addresses four issues that do not affect the majority of installations, but are critical for users with certain configurations.
Version 3.17 is not a required upgrade if your Movable Type installation is not affected by these issues.
Changes in this release include:
- Installation at the root of a domain no longer continually logs out the user.
- Fixed URL-encoding of uploaded file paths (e.g. images%2fbeach-pic.jpeg)
- Fixed a bug in the nofollow plugin which causes HTML sanitization of everything within an <MTPings> block.
- Fixed a bug in
mt-db2sql.cgiwhich caused it to fail in certain situations when subcategories are in use before conversion.
Again, this update is not required unless you have been affected by any of the issues mentioned above.
For a more detailed information about this release, see:
If you already purchased Movable Type, or downloaded the free version, you'll be able to download the new release for free from your Movable Type account. Otherwise, you can find it on the Pricing and Licensing page.
As always, there is a free, unsupported personal version of Movable Type 3.17 which will satisfy the needs of a large number of personal users.
