Not a developer? Go to MovableType.com

Documentation

Movable Type 4.34 Release Notes

This version of Movable Type was released February 17, 2010.

Resolved Issues in Movable Type 4.34

  • Reimplemented the malicious image detection capabilities that were added to Movable Type 4.33 to protect asset management functions more consistently. (103383)
  • Recreated an index on the comment_parent_id column in the mt_comment table. This index was incorrectly removed in a previous version of Movable Type 4.3x. (103782)

Warning: The schema change listed above may require customers with large Movable Type databases to upgrade using the tools/upgrade method. See instructions in the Upgrade Guide for Movable Type for more information.

  • Corrected a problem with user privilege changes implemented in Movable Type 4.33 that prevented a user from uploading a userpic (a picture of himself or herself) in some situations. (103783)
  • Fixed a typographical error in the lib/MT/Summary/Proxy.pm Perl module in Movable Type 4.33 that resulted in “subroutine redefined” errors being reported in some circumstances. (103699)
  • Fixed a problem with the internal search facility within the Movable Type 4 CMS that prevented more than 125 results matching the search criteria to be displayed. Thanks to Mark Carey for the patch. (101036)
  • Fixed a problem with the internal search facility within the Movable Type 4 CMS that caused all “Regex Match” searches to return no matches. (103784)
  • Fixed a problem in Movable Type 4.33 where searching for entries by date ranges returned incorrect results. This problem was most noticeable to users of the Blog Stats Dashboard Widget. It often displayed no activity for entries or comments regardless of actual activity. (103357)

Housekeeping

  • Confirmed that a patch had been applied to previous versions of Movable Type 4.3x that corrects the results when MT:Entries is filtered by a category name whose name contains one or more spaces. This case was not resolved and closed when the fix was applied to the code base. (100402)

Known Issues in Movable Type 4.34

Resolved

Note: These fixes aren’t currently included in Movable Type 4.34. Consult the FogBugz cases for instructions on how to patch your installation.

  • Corrected the problem where author archive mappings incorrectly implied that Display Names would be used in generating URLs when there is no guarantee that Display Names are unique. Basenames must be used instead. The code actually does the right thing in that it uses Author Basenames already, but the information displayed to the blog administrators in the CMS was never corrected until now. (86237)
  • The Archive File Path Specifiers page of Movable Type documentation was changed to reflect the use of Author Basename rather than Author Display Name as had previously been stated in most cases. (103737)
  • Recreated an index on the comment_blog_id, comment_ip, and comment_created_on columns in the mt_comment table. This index was removed in a previous version of Movable Type 4.3x and is causing performance problems on sites with a large number of comments. (103831)

Warning: The schema change listed above may require customers with large Movable Type databases to upgrade using the tools/upgrade method. See instructions in the Upgrade Guide for Movable Type for more information.

Resolved but Needs Testing / QA

  • Fixed a problem where User Custom Field data wasn’t displayed on the CMS Edit Profile Page under certain circumstances. (103714)

Note: Caution should be used in deploying the patch referenced above in production environments where memcached is in use until further QA testing can be done.

  • Fixed a situation in MT::Template::ContextHandlers where MT::Entries was producing incorrect results. Specifically, if the tag parameter was present, the limit or lastn parameter was being evaluated before the category parameter. (102843)

  • Fixed a problem in the Community.Pack where the author_modified_on value for a registered user was not being updated after the user’s profile was modified using the “Edit Profile” header link in many Community template sets. (103853)

Unresolved

  • Zemanta Plugin: The Zemanta plugin does not use the HTTPProxy configuration directive. (103239)
  • AtomPub Server: The AtomPub server may fail to publish entries with large embedded files in certain situations. (103423)
  • Movable Type Enterprise customers using Oracle databases may experience an error when an empty array is passed to an object load method (Typically "DBD::Oracle::db prepare_cached failed: ORA-00936: missing expression (DBD ERROR: error possibly near <*> indicator at char… in ‘SELECT….’"). (103418)
  • Assets uploaded via a custom field do not have the asset label field populated. (100701)
  • PHP 5.3.x Reports “PHP Deprecated” Warnings For Some Functions in ~/php/mt.php and Some Supporting Libraries. (103926)
  • Output from CMS System Overview > System Information Should Not Be Cached (79429)
Back

Leave a Comment