Not a developer? Go to


Movable Type 6.0.4 Release Notes

This version of Movable Type was released September 8, 2014.

Known issues

Read before upgrading / new issues

  • Pagination based on mt-search.cgi does not work correctly because of a problem with the limit parameter. (#112365)
  • The Ignore block tag’s contents is erroneously parsed, which can result in build errors if Ignore blocks happen to contain template code that would not be valid outside the Ignore block. (#112393)
  • Upgrade does not finish correctly if site has the MultiBlog plugin configured with a trigger for “All blogs in this website” for one or more websites in the installation. (#112418)
    • If user upgrades by command line with tools/upgrade script, the upgrade process will stop prematurely.
    • If user upgrades by the GUI in the browser, the upgrade will finish, but the MultiBlog trigger for “All blogs in this website” will not be saved correctly. This can be resolved by navigating to the MultiBlog settings and saving again.

Other issues

New and improved

Movable Type Advanced

  • Movable Type can now retrieve and properly paginate member and group information from an LDAP server using Active Directory when there are more than 1,500 members. (#111294)
  • If user synchronization is configured on an LDAP environment, it is now possible to sync only specific fields. See the LDAPUserSyncAttributes and LDAPGroupSyncAttributes configuration directive documents for more information. (#111295)
  • The Active Directory “Domain Users” group can now be synchronized. (#110622)


File location will be displayed on the asset editing screen even if the file no longer exists at that location. Previously an “is missing” message was displayed, but that was unhelpful in potentially retrieving the missing file from a backup or elsewhere. (#111794)

Data API

Revision history is now saved when entries are created or updated via the Data API. (#110929)

Additional template tags

New plugins available

The following plugins have been created from code removed from various Movable Type core files and are now required to support mt-view.cgi and mt-add-notify.cgi. They do not come packaged with Movable Type Pro or Movable Type Advanced, and technical support is not available.

Additional modifiers

  • The parent modifier can now be used with the WidgetSet tag. (#111700)
  • The include_private modifier can now be used with the Tags tag. (#111633)
  • The raw modifier, which prevents underscores in theme IDs from being replaced with hyphens, can now be used with BlogThemeID and WebsiteThemeID. (#110304)
  • The ignore_archive_context modifier, used to escape from the current archive context, can now be used with the Assets tag. (#111351)

PHP 5.5 support

  • PHP 5.5 is now supported. (#110627)
  • Connections with MySQLi are now supported. (#110725)


Data API

  • Login requests using the DataAPICORSAllowOrigin configuration directive are now possible for published websites or blogs. (#111411)
  • The session will not distinguish between different caller paths originating from the same application. (#110473)

Websites and blogs

A forward slash (/) will be automatically added to the end of all site URLs that do not have one included. (#112148)

Template tags

  • If a trim_to modifier has a negative number value, that number of characters will be trimmed from the end of the output. (#111767)
  • The AssetCount tag no longer includes system generated thumbnails in the asset count total. The output of the AssetCount tag now equals the number of assets output by an Assets block. (#80745)


The language specified by the DefaultLanguage configuration directive will now also be used on the login screen. (#110443)

For developers

  • The fourth item called by the MT::Revisable::Local object_from_revision function will be returned as the Revision object. (#111864)
  • It is now possible to assign a subroutine to a Data API resource’s updatable_fields condition in the config.yaml file. (#111497)
  • For all objects based on MT::Object, secondary sort is now performed using the primary key. (#110910)


Alert messages will appear when values for the following settings are overwritten in the mt-config.cgi file:

The following modules have been added to the list of perl modules checked by mt-check.cgi and the installation wizard (#111408, #111550, #111234):

  • Time::HiRes
  • IO::Socket::SSL
  • Mozilla::CA
  • Crypt::SSLeay
  • XML::SAX::ExpatXS (1.30+)
  • XML::LibXML::SAX (1.70+)
  • XML::SAX::Expat (0.37+)

YAML::Tiny (packaged with Movable Type) has been updated to version 1.62. (#111716)

TinyMCE has been updated to version 3.5.10. (#111547)

Solved issues

Movable Type Advanced

On environments with LDAP authentication enabled:

  • authentication would fail if the LDAP username included parentheses. (#112170)
  • an installation wizard error would occur if a connection could not be made to the LDAP server. (#112177)
  • it was not possible to progress past the installation wizard’s account creation screen. (#112208)

If an LDAPGroupIdAttribute configuration directive contained parentheses and a group sync was attempted, that group would be deleted from Movable Type. (#111647)

Installing and upgrading

  • Users with certain environments could not complete the installation wizard. (#111489)
  • Movable Type could not be installed successfully on environments using SQLServer and FastCGI. (#110790)
  • When using DBD::Oracle 1.55 or above, certain database tables were updated unnecessarily upon upgrade. (#111758)
  • Some messages were not completely translated. (#112229)

Websites and blogs

  • Website archive URL input validation was not working correctly. (#111473)
  • On a Windows environment, if the BaseSitePath configuration directive was left undefined, the site path would not reflect the correct value following restoration from backup. (#111480)
  • On environments with specified website paths, the path name for blog site paths would not reflect the correct path following restoration from backup. (#110481)
  • Site URL input validation was not working correctly during new website creation. (#111311)
  • “Vox” was mistakenly displayed as an authentication method. (#111361)
  • The word “blog” was mistakenly used on the website settings screen. (#111279)
  • When using subdomains with blogs, input validation would not work for subdomain values. (#111373)
  • After saving website or blog settings, some sections of the generated log were not being translated. (#111965)
  • After saving blog settings, unnecessary parts of the revision history would appear in the generated log. (#111739)
  • On the entry or webpage creation screen, input validation was not working for entry basename, listing limit and excerpt character limit. (#55672)

Custom fields

  • After previewing an entry or page that contains image custom fields and then returning to edit the entry or page, the image data became corrupted. (#111714)
  • If the basename for a custom field contained a hyphen, the field would not be included in an entry export file. (#111735)
  • On the configuration screen for page custom fields, if a folder was selected, all other folders with the same basename as the selected folder would also be selected. (#111645)
  • Custom fields specifically related to a category in a saved entry would continue to be displayed even if that category was removed. (#111309)
  • Some sections of the filtering options on the custom field listing screen were not translated. (#111896)

Data API

  • Entry excerpts were not always properly generated and returned. (#112138)
  • Depending on the caller’s URL, getTokenData could return an incorrect token. (#111875)
  • When updating an entry, the entry’s tags could not be removed. (#111485)
  • An error would occur when the Data API was used to save entries with specified trackback destinations. (#111601)
  • The correct data would not be retrieved during Google Analytics data retrieval. (#111346)

Backup and restore

  • If an error message appeared due to a restoration failure, the transition to the login screen was not possible. (#111847)
  • If the OS differed between the backup and restoration locations, path separation character strings would not transition to the restored location. (#111090)
  • Entry scores were not restored correctly. (#111319)


  • The Eiger theme would fail to load if YAML::Tiny was in use.(#111825)
  • The wording on the system theme listing has been revised. (#111816)
  • ZenBack would not display in preview mode. (#111347)
  • <meta name=”description” …> would be mistakenly displayed if the summary contained an equal or unequal sign.(#111360)
  • The title and description of a community blog or community forum would not be displayed if using dynamic publishing. (#111366)
  • After posting an entry to a community blog or community forum, an error would occur if the “Sign Out” link was clicked. (#111265)
  • An incorrect input validation error message would appear when posting an entry from a community blog or community forum. (#112250)
  • The Rainier theme’s translated about page has been revised. (#111840)


  • For website templates modules and widgets, when an entry or page was created or updated, the disable cache option could not be selected. (#112127)
  • The refresh template confirmation message has been revised. (#111817)
  • Old administration screen headers would be displayed in preview mode. (#111742)

Dynamic publishing

  • An error message would occur if SHIFT_JIS was selected for PublishCharset. (#111116)
  • The template module cache activation period was not being determined correctly. (#112140)

Template tags

  • Results were not being generated when the AuthorUserpicURL tag was used in the Entries block tag. (#111377)
  • If a custom field was in use, the sort_by modifier for the Entries tag had issues sorting and comparing character strings. (#111404)
  • An error would occur if the Calender tag category modifier was left unspecified. (#111851)
  • The ignore_archive_context modifier would not work when used with dynamic publishing. (#111087)
  • The include_with_website modifier could not be used in combination with the Entries/Pages tags. (#112061)
  • If blog_id was specified in the WidgetSet tag, the include template link destination would not be evaluated correctly. (#111700)
  • When the category modifier was used with the Calendar tag, the specified category would not be filtered. (#111945)
  • In a nested If, if the name modifier was omitted and the Else and ElseIf tags were used, the calculated result would be incorrect. (#111805)
  • If the type modifier was used with the IfCategory tag outside of an entry context, the correct error message would not be displayed. (#111793)
  • The trim_to modifier could not have 0 after the plus sign in the value. (#111778)
  • The convert_breaks modifier did not work with the EntryExcerpt tag. (#111709)
  • Even after a vote was deleted, IfEntryRecommended would continue generating results as if the vote were not deleted. (#111297)
  • If the regex_replace modifier was used on a character string containing the @ character, it would not work correctly. (#111688)
  • The regex_replace modifier would not work correctly when used with the < and > characters. (#111691)
  • The role modifier would not work correctly for certain role names when used with the Author tag. (#111534)
  • Results generated by CustomFieldHTML could differ for static and dynamic publishing. (#111451)
  • When determining whether to execute code in an Unless tag for an array variable, an error could occur if dynamic publishing was in use. (#111460)
  • Japanese would become garbled if the nofollowfy modifier was set. (#111350)
  • If Assets was used with a date based archive, the date filters currently being processed would be mistakenly used. (#111351)
  • When filtering by custom field within the Entries tag, an error would occur if the offset value was higher than the limit. (#111398)
  • If a value including a character other than a number was used with the AssetThumbnailURL width and height modifiers, a thumbnail would not be generated. (#109425)

Entries and pages

  • If the host or domain differed between the admin screen and the published site, the URL link to the editing screen for inserted items would be displayed incorrectly. (#111996)
  • If the body text and read more were replaced, the text area height would also be changed. (#111751)
  • The English translation for the search box label was revised. (#111640)
  • The tag auto-complete function was erroneously detecting symbol input. (#111441)
  • When an existing entry was saved, depending on the archive mapping, the entry’s permalink would reflect the older value. (#111456)
  • When using the rich text editor with Internet Explorer 11, The “Edit HTML source” button would not work. (#111547)
  • When returning to the editing screen from preview mode, the “Entry item” widget display would break. (#111587)
  • When using Safari or Chrome, the HTML would break if an image inserted in the rich text editor was selected and then swapped with a different image. (#111917)
  • After a tag was added to a selected entry or web page from the listing, the “update date” information would not update. (#80072)
  • When using the publish queue, even after an entry status was set to “unpublish”, the published file would not be deleted. (#111248)


If a published entry was unpublished, the entry information would not be displayed in the top access stats. (#110904)

Server syncing

  • Syncing was not working consistently. (#111253)
  • If FTP connection information (login user name, password, etc.) included symbols, syncing would not work properly. (#111877, #111326)
  • If SSL use was edited to either enabled or disabled, the save button became unusable. (#111328)
  • If a scheduled task was scheduled and set to ignore a website or blog’s offset, the task would not be processed at the specified time. (#111344)


  • When uploading an asset, if the upload destination folder name beginning with a path delimiter (either / or \) was entered, the internal file reference destination would be given an invalid value. (#111668)
  • If an asset upload was canceled, the asset record and the uploaded file could remain. (#80850)
  • If an asset’s cache directory could not be created, the thumbnail’s file path would be displayed incorrectly. (#82495)

Comments and trackbacks

Smartphone option

  • Styles would break when viewed on iOS 7. (#111439)
  • A JavaScript error would occur when body text was entered on a smartphone. (#111474)

For developers

  • If two of the same filename were passed to the MT::FileMgr->rename, the specified file would be deleted. (#111881)
  • When using dynamic publishing, if multiple values were specified for UserPasswordValidation, only the first value would be retrieved. (#111823)
  • The $count (search result number limit) passed to the callback from MT::App:Search would not use the limit count parameter. (#110758)
  • The MT::CMS::Common::is_disabled_mode,,, and callbacks would not be called when the “Registration/Authentication” settings screen was opened. (#110977)
  • The MT::CMS::Common::is_disabled_mode,,, and callbacks would not be called when the “Community” settings screen was opened. (#110978)
  • An error would occur when the MTDatabase class (PHP) MTDatabase tags_entry_count variables were called. (#111654)
  • The set_notification_dashboard callback would be called multiple times. (#111445)
  • When the set_notification_dashboard callback called XHR, nothing would happen. (#111283)
  • In the Listing Framework, if either the author_id or created_by columns were left blank, an undefined user name would be displayed. (#111382)


  • The search results listing column was not being displayed correctly. (#111792)
  • User images could not be changed in some situations. (#111785)
  • When operating under a PSGI environment, the execution environment was mistakenly displayed as CGI in the system information. (#111741)
  • The Community Pack would not load if YAML::Tiny was in use. (#111733)
  • If using IO::Socket::INET6 version 2.57 or earlier, an error would occur when connecting to Google Analytics. (#111396)
  • In Internet Explorer, it was not possible to scroll in image pop up windows linked to items embedded in entries. (#81259)
  • An error would occur when setting classification filters for the system log. (#111619)
  • System information was not being displayed in the language specified by the user. (#111484)
  • On the pages search result listing, the creation date was being listed in the last modified line. (#111603)
  • If a scheduled publish and scheduled unpublish occurred at the same time, the published entry would not appear in the archive. (#111612)
  • Styles would break in preview mode. (#110746)
  • The listing style would break if viewed in Internet Explorer 11. (#111050)
  • When Imager was used as the ImageDriver, an error would not occur when libjpeg could not be found. (#105860)
  • An error would occur if attempting to access mt-cp.cgi without a parameter. (#111298)
  • An error would occur if the user changed his language settings. (#111335)
  • Automatic redirect to mt-wizard.cgi was not occurring on FastCGI environments. (#111278)
  • A spelling error in HidePerformanceLoggingSettings was corrected. (#111563)
  • If run-periodic-tasks was executed with Perl 5.8.x, an invalid regular expression error would occur. (#111773)
  • If syncing failed on the group listing, an error would occur if the link to the log listing included in the sync fail error message was clicked. (#112210)


The release of Movable Type 6.0.4 brings with it a large number of improvements that were made possible by the help and support of Movable Type community members. We would like to include a special shout out to the following members for their contributions to this update:

Bug IDs link to an external site ( You must have a valid account and be logged in as a member on FogBugz in order to see report details.