New Features

1) Boilerplate

2) New Theme: "Rainier"

3) Movable Type Advanced

4) Other Features

Bug Fixes

• [104094] After changing the destination folder for published web page data, an old web page data still remains in the the old folder.
• [104665] The "maximum open cursors" occurs when using Oracle.
• [106224] An error will occur if the MT generated .htaccess file includes "SymLinksIfOwnerMatch", as multi-server hosting is not supported.
• [106534] Creation and deletion of the category archive page is not executed in appropriate timing.
• [107118] If Japanese is used with LDAPAuthURL, a user search will not work
• [108797], [108797] An error occurs on the user profile screen when building a community blog on Oracle or MS SQL Server.
• [107961] In Oracle and SQL Server, an error occurs when trying to destroy old session information.
• [107963], [107994] Request to enable use of custom field tags with archive mapping.
• [108513] If a thumbnail already exists for an image and MTAssetThumbnailURL is set to square="1", the image appearance is not updated, even after rebuilding.
• [108570] Request for the addition of an e-mail validation process when resetting a password.
• [108631], [108862] When user edit comments data from the search/replace screen, the keyword search option disappears from the input field.
• [108654] When there is a sub-domain input error, the error is displayed as originating from a different location.
• [108661] app.saveHTML() returns information currently displayed in the rich text editor.
• [108667] Please add the ecape=html value to the mt:CommentParentID tag, available for use in professional website and professional blog templates.
• [108718] The dynamic publishing MTWidgetSet tag ignores the blog_id setting.
• [108728] After upgrading from MT 3.38 to MT 5.2, users with the "send notification" option enabled will not be able to create new blog entries.
• [108730] When restoring MT from a back up file, multiple copies of the profile image will be restored as well.
• [108733] When operating in an environment running memcached, the template module cache will not be cleared at the specified time.
• [108734] The template cache will not be cleared after a new category is created.
• [108748] Incorrect HTML is generated from unlabeled item custom fields.
• [108799] When executing bulk user updates with CSV, even though the same user name is specified in the new user name input field, an error occurs.
• [108802] When Config Directive "SingleCommunity" is set to 0, the member's list in the Movable Type authenticated users folder will be displayed incorrectly
• [108803] When Config Directive "SingleCommunity" is set to 0, users with third party authentications, such as OpenID, will not be able to be removed from a blog.
• [108804] Although website administrative privileges are granted to a user group, users do not have access to blogs linked to those websites.
• [108805] When restoring from back up data, group member data is not restored.
• [108815] Code generated from custom fields with multiple lines of text will not be converted correctly
• [108824] When specifying a publishing path with BaseSitePath through Windows, an error will occur if case sensitivity is not specified.
• [108841] When using dynamic publishing, upper and lower case characters used in tag attributes are treated as completely different characters.
• [108845] If IncludeBlogs is set to "all", an error will occur in the blog search.
• [108846] An error will occur if IncludeBlogs or blog_id is not specified in the search form template.
• [108856] The error message for the Facebook commenter's plug-in should be revised
• [108858] StyleCatcher display breaks in the Apache+Starman environment.
• [108866] When using dynamic publishing, an error occurs when half-width alphanumeric characters are used to write folder or category names.
• [108872] MTArchiveTitle is output differently depending on whether dynamic or static publishing is used.
• [108876] Category and folder selection cannot be saved on FireFox16.
• [108877] An automated message should be displayed when a commenter's identity cannot be authenticated.
• [108891] Blog entries marked as "NO ENTRY" cannot be imported.
• [108901] Templates using the alt-tmpl directory, included with theme files, do not function correctly
• [108909] When ignoring the revision history, the latest blog entry author is displayed as the user who is currently logged in.
• [108920] MT doesn't hold Compose Settings when change the field basename
• [108924] Individual archive pages are not displayed when using dynamic publishing.
• [108946] Comment pagination does not work when running MT through PSGI.
• [108947] When using dynamic publishing, an error will occur if someone tries to view a website that does not have a blog.
• [108948] When using dynamic publishing with PHP5.4, the "Sign In" characters will not be displayed.
• [108953] When TAB data is inserted in the comment data, comment pagination will not work correctly.
• [108958] System privileges cannot be changed
• [108959] A template error will occur if "(" is set in a category modifier with MTEntries tags.
• [108967] The {{theme_static}} setting cannot be used in the StyleCatcher repository.
• [108982] After re-applying a theme, the theme thumbnail will not update.
• [108989] The MTMultiBlog tag does not work correctly in the blog entry list archive.
• [108999] Assets may not be correctly retrieved when importing data from WordPress.
• [109003] If a blog entry with an index template that is using the MTEntryCustomFields tag is saved and rebuilt, the value for all custom fields will be reset to the default value.
• [109004] Blog restoration can not be completed if a website does not exist.
• [109009] When specifying the BaseSitePath, case sensitivity is automatically turned on in Website Path field.
• [109022] When importing an exported blog entry that includes a blank custom field, a half-width character space is arbitrarily inserted as the value for the empty custom field.
• [109023] The user date archive (by year, month, week or day) is not displayed when using dynamic publishing.
• [109024] search_apis cannot be added through plugins.
• [109026] When using the external environment SMTP server, if an e-mail is sent to multiple recipients, the e-mail header will look strange.
• [109032] If a folder with sub-folders is deleted, the user will not be able to save changes.
• [109036] When executing bulk user updates with CSV, multi-byte e-mail addresses can be saved without error.
• [109038] When executing bulk user updates with CSV, a user name with over 85 full width characters can be saved without error.
• [109039] When executing bulk user updates with CSV, a user name with over 255 half width characters can be saved without error.
• [109055] When executing bulk user updates with CSV, even if a blog theme has not been saved, an error will not occur.
• [109097] Files that already exist cannot be renamed when using a Windows operating environment.
• [109105] When importing WordPress data, neither categories nor tags can be imported.
• [109112] The mteval modifier will work even if a value other than 1 is used.
• [109133] The numify modifier will cause output discrepancies between static and dynamic publishing.
• [109134] When the sanitize modifier is set to 0, an error will occur if dynamic publishing is used.
• [109149] When the environmental variable UserSessionCookieDomain is not set, the value for the domain of the cookie will not be generated correctly.
• [109156] An error will occur if an embedded custom field value is saved.

This is supposed to be the last beta before releasing v5.1.

Jun's announced today about the release of this bugfix version.

I've upgraded to put it up for you right away!



Remember that in order to get the login details to this version, you have to click on v5.x from the top navigation.

One of the things I love at Six Apart is that these guys are always working (pretty the same as I do).

I recall from Le Web 3, 4th edition in Paris, France, way back in December 1997 that Chris Alden (Six Apart CEO) and the other board members said to me:

'We are wondering if you even get some time to sleep! You're doing so many wonderful things.'

At that time we were talking about this 'movable type demo project' that I've initiated on June 2007.

Did Six Apart adopt my working fashion? It looks like... :)

They are always surprising me with launching new movable type versions and more and more features. I have no reasons to regret that I've chosen movable type and to advocate for it vs. wordpress.

Movable Type Motion Available For Demo

Last night they've launched movable type v4.25 which contains the motion extra feature!

Since motion is an excellent social feature, I cannot wait to reveal it to you here.

This being said, I'm delighted to invite you to have a look at movable type v4.25, both professional and open source versions.

Let me add one more thing! If you find this demo project helpful, please support it by giving my any movable type work or by making a paypal donation to info[at]pro-it-service[dot]com.

To login to movable type live demo use the following details:

- username: demo
- password: demo

1. Movable Type Professional v4.25

- release date: March the 17^th, 2009

- access url: http://www.movabletype4.org/cgi-bin/mt.cgi

2. Movable Type Open Source v4.25

- release date: March the 17^th, 2009

- access url: http://www.movabletype4.org/opensource/cgi-bin/mt.cgi

This morning Natalie Podrazik, Manager @ Movable Type Support announced movable type v4.24 on the movable type professional list (pronet).

This release was launched mainly to address a security issue that relates to the exposure of user profile data. This bug impacts the Community Pack code directly.

Together with this security issue fix, the new movable type version contains an improved Password Recovery mechanism. Now only an email address is required for MT to trigger the recovery email, making the Password Hint obsolete.

I've just upgraded our two movable type demo installations so that you could enjoy the new release.

Do you need assistance to have your movable type installation upgraded? Get in touch!

Guys, we were in holiday until now and during this time, more specifically on December the 3rd, Six Apart announced Movable Type v4.23

This release is very important as it addresses a good number of bugs and security issues!

You are very welcome to start checking it out right away!

I've also noticed that the movable type commercial installation had some issues. Basically, after providing the username and password movable type was displaying an Error 500 message...

On the back end it was generating a dump core file measuring about 30 megabytes for each and every login attempts! Don't ask me how many dumps were in...

The problem has been fixed and you can now browse both the commercial and open source version of the latest released movable type v4.23. Enjoy!

These days everybody is interested on various programming jobs, from optimizing Movable Type driven Web sites to creating new blogs or online communities.

While I'm very pleased to satisfy all my customers and I'm truly thankful to them for bringing in more and more work, as well as more contacts, I'm again very pleased to let you evaluate the final release of Movable Type v4.01 which was just lunched last night.

I cannot wait to let you discover this release, so until Byrne and the rest of the Six Apart team will make it available online you are free to check it out here.

Time to give it a try live on this Web site!

Point your browser to:
http://www.movabletype4.org/cgi-bin/mt.cgi

And login with:
- username: demo
- password: demo

As always you could support this initiative by checking out our Movable Type Consultancy services

I was out for a conference and business meeting in Germany from September the 11th till the 15th

During this time Six Apart already launched the Movable Type v4.01 RC 2 which is addressing a couple of bugs. For the entire change log click here: http://www.movabletype.org/beta/

Six Apart just launched a new Movable Type version last night. The Movable Type v4.01 Release Candidate 1 addresses a couple of issues that are documented at: http://www.movabletype.org/beta/

The update is recommended but not strictly required. What makes it worth trying ASAP is the fact that it is expected to increase performance in the overall application and publishing.