New & Improved Functions

Server Sync (Movable Type Advanced)

The server sync function is now available for Movable Type Advanced users.

By using server sync, content created on Movable Type Advanced can be sent to and published on an external server. As Movable Type Advanced does not need to be installed on the external content publishing server, this greatly decreases security risks, such as unauthorized access.

If the server containing Movable Type Advanced is set up to act as a staging environment, that server can then be used to store backup content.

Blogs and websites can be sent to and published from multiple servers and both FTP and rsync are supported as viable distribution methods.

Internet Explorer 11 Support

Movable Type should now run smoothly on Microsoft’s Internet Explorer 11. (The Modern UI is no longer recommended.)

[IE=Edge] is the new setting for compatibility mode across all admin screens.

Microsoft IIS Server Fast CGI Support

FastCGI is now supported for use on the Microsoft IIS server. FastCGI can help enhance operation performance on the Movable Type admin screen, although please note there are some known issues and restrictions.

Additional Modifiers

When using dynamic publishing, the [by_author] and [by_category] modifiers can now be used alongside the MTEntryPrevious, MTEntryNext, MTPagePrevious, MTPageNext template tags. Please refer to the document page for each template tag for more information. (#110830)

The [by_folder] modifier can also now be used as a tag modifier for the MTPagePrevious and MTPageNext template tags. Please refer to the document page for each template tag for more information. (#110830)

Loupe Style Guide

A style guide explaining how to customize Loupe, as well as how to add new cards, is now available. The style guide can be found in the styleguide directory located in the cloned repository from GitHub.

For Developers

The [ID] attribute for the MTInclude tag that loads [include/header.tmpl] now holds a [header_include] value. With the Transformer function, it can be used as a placeholder when overwriting the template. (#110496, #110793)

New Configuration Directives

If a connection to the database is unable to be established, the system can be set to automatically retry at regular intervals until successfully connected or the max number of retries have been reached. Please refer to the DBMaxRetries and DBRetryInterval documents for more information. (#111131)

The user can also set connection timeouts during SMTP server connection attempts. Please refer to the SMTPTimeout document for more information. (#111129)

New Callbacks

The callbacks below can be used with the new server sync function.

cms_save_permission_filter.sync_setting

Called out before server sync settings are saved.

Parameters

$cb: MT::Callback object

$app: MT::App::CMS object

$id: Always undef

Return Value

If the user has permission to save server sync settings, a value of 1 (true) should be returned.

If the user does not have permission to save server sync settings, a value of 0 (false) should be returned. When this occurs, the message registered with $app->error() will be displayed along with a default error message.

cms_view_permission_filter.sync_setting

Called out before the server sync settings screen is displayed.

Parameters

$cb: MT::Callback object

$app: MT::App::CMS object

$id: Always undef

$obj_promise: Server sync settings object

Return Value

If the user has permission to open the server sync settings screen, a value of 1 (true) should be returned.

If the user does not have permission to open the server sync settings screen, a value of 0 (false) should be returned. When this occurs, the message registered with $app->error() will be displayed along with a default error message.

cms_save_filter.sync_setting

Called out before server sync settings are saved. Can also be used for validating data.

Parameters

$cb: MT::Callback object

$app: MT::App::CMS object

Return Value

Normal operation should return a value of 1 (true). Otherwise, a value of 0 (false) should be returned. When this occurs, the message registered with $app->error() will be displayed along with a default error message.

cms_pre_save.sync_setting

Called out before server sync settings are saved. Can also be used for confirming changes made to saved objects.

Parameters

$cb: MT::Callback object

$app: MT::App::CMS object

$obj: MT::SyncSetting object

$original: Pre-modified MT::SyncSetting object

Return Value

Nothing

cms_post_save.sync_setting

Called out after server sync settings have been saved.

Parameters

$cb: MT::Callback object

$app: MT::App::CMS object

$obj: MT::SyncSetting object

$original: Pre-modified MT::SyncSetting object

Return Value

Nothing

cms_edit.sync_setting

Called out before the server sync settings screen is displayed.

Parameters

$cb: MT::Callback object

$app: MT::App::CMS object

$id: Always undef

$obj: MT::SyncSetting object

$param: Parameter hash passed to the server sync settings screen template

Return Value

Normal operation should return a value of 1 (true). Otherwise, a value of 0 (false) should be returned.

Updated Functions

Install / Upgrade

• During installation, an error message will appear if the support directory cannot be written to. (#110606)

Website / Blog

• When creating a new website, there is now a check in place to make sure the site path is writable. (#110577)

For Developers

• When saving a website, the called out callback was changed from cms_post_save.blog to cms_post_save.website. To preserve compatibility, we recommend calling out both callbacks at the same time. (#110764)

• The MT::AccessToken record is no longer included in backup or restoration. (#111267)

• After mt.cgi automatically transitions to mt-upgrade.cgi, the [set_notification_dashboard] callback will no longer be called out.(#111155)

Miscellaneous

• The HTTPTimeout value is the new value used when a system information retrieval request times out. (#110738)

• The Google API Console is now known as the Google Cloud Console. (#111036)

Resolved Issues

Install / Upgrade

• When installing Movable Type, an error would occur if a theme containing custom fields was selected for a new website. (#110700)

• An issue that prevented upgrading when using the Microsoft SQL Server is now fixed. (#110868)?Movable Type Advanced?

• An issue that unnecessarily forced the mt_ts_error table to update is now fixed. (#110683)

Dashboard

• For logged in users, the [Access stat settings] link remained visible in the Site Stats widget even when access stat settings should have been inaccessible. (#110674)

• For logged in users, the [Access stat settings] link was not displayed in the Site Stats widget even when access stat settings should have been accessible. (#110673)

• Incorrect numbers were being displayed on graphs and tooltips in the Site Stats widget. (#110763)

• If CGIPath and SupportDirectoryURL were operating from different domains, the Site Stats widget data could not be retrieved. (#111037)

• An error would occur when clearing the Site Stats data cache.(#110786)

Theme

• An issue regarding professional website theme styling is now fixed. (#110671)

• Most recent comments were not being displayed in the Rainier theme entry archive and page archive. (#110657)

• [Community Message Boards] The [mtapp:statusmsg] tag has become standard for some templates. (#110780)

• Comments could not be left on entries if Eiger was used as the website theme. (#111163)

• The [Powered By Movable Type] logo was partially cut off. (#110919)

API

• Entries could not be updated via XML-RPC. (#110911)

Dynamic Publishing

• If a nonexistent category archive was included in the mt_fileinfo table, an error would occur if the MTCategoryArchiveLink tag was used with dynamic publishing. (#110984)

• When using dynamic publishing, a connection could not be established if a port number was specified on the Microsoft SQL server. (#111064)?Movable Type Advanced?

• Dynamically published content would break when published using PHP 5.1.6. (#110704)

• Extra blank lines were being inserted when using dynamic publishing. (#110945)

• The MTEntries blog_ids modifier and tag modifier could not be used at the same time  when using dynamic publishing. (#111125)

Entry / Webpage

• If edited boilerplate text was inserted into an entry on Internet Explorer, the pre-edited text was displayed instead. (#111092)

• Links could not be inserted in the rich text editor if using Internet Explorer. (#111046)

• An error would occur if a plugin was added to the rich text editor in a PSGI environment. (#111149)

• The style for inserted links would break. (#110914)

• When adding categories on FireFox 25, the default help text could not be deleted or replaced with new text. (#110841)

• Items connected to the MTEntryAssets tag would not be output in the associated entry. (#111164)

Listing Screen

• Filters could not be removed on the listing screen. (#110462)

• Time of publication was ignored when filtering by date. (#111152)

• The tag filter did not work correctly when using [“does not contain”]. (#111151)

• When filtering using the [“do not include character string”] option, any field with a value of null would be excluded. (#110358)

Group Management

• An error would occur when a group status was changed. (#110605)

• An error would occur if a group was deleted. (#110955)

Backup and Restoration

• Global templates and system widgets were not being backed-up properly. (#110906, #110903)

• If a backup file was restored on an OS that differed from the OS used when backing up the file, the item path would ignore the directory separator restoration path. (#111000)

Loupe

• The entry confirmation card would not be displayed if there were 25 or more saved blogs. (#110916)

• The submit button would be displayed for users who did not have authority to publish entries. (#111167)

For Developers

• Filtering by [class] was not possible when loading objects using [id]. (#110475)

• If a user changed their password, the user object could not be retrieved from $app->user. (#111182)

• If an MTEntries tag was used within a MultiBlog tag, the retrieved entry data was unusable. (#110597)

Miscellaneous

• If PerformanceLogging was active, AdminCGIPath settings became inactive. (#111188)

• On PSGI environments, the TimeOffset configuration directive value would automatically overwrite the blog / website offset value. (#111245)

• The flickering notation on the website and blog admin screen was fixed. (#110521)

• The revision history date and time ignored time zones. (#111229)

• On Microsoft SQL Server and Oracle environments, problems occurred when using limit and offset to calculate formulas. (#110042)?Movable Type Advanced?

• When using LDAP authorization, inactive users could not be changed to an active status. (#110996)?Movable Type Advanced?

Limitations

There is currently no estimated date for when the following issues will be resolved.

• An error occurs when posting new entries via Atom API on a Microsoft IIS server.

• When using MySQL on Windows Server 2012, the DBI module must be updated to version 1.623 or higher.

Known Issues

Solutions for the following issues are currently being investigated and fixes will be included in future updates.

• When using the publish queue, published entries that are unpublished remain undeleted from the currently published entry archive. (#111248)

• When using FastCGI on the Microsoft IIS server, if the FastCGI timeout value is too short, the act of processing will cause a timeout. (#111130)

• On a Windows Azure environment, if an item with a filename containing Japanese characters is uploaded, the text becomes garbled and the file becomes inaccessible from the web. (#111240)

Thanks to:

• Shingo Watanabe (#110673, #110674, #110764, #111188)

• Kondo@alfasado (#110496, #111064, #111182, #110680, #110945)

• Junnama Noda (#110657, #110475, #110770, #110701)

• Dan Wolfgang (#110763)

• Toru Motchie MOCHIDA (#110868)

• taiju@alfasado (#110984, #111046)

• Yasuhiro Takahashi (#110780)

• David Phillips (#110597)

? Bug IDs are linked to an external site (http://movabletype.fogbugz.com). A FogBugz user account is required in order to view details on each case.