Last night we silently released our second release candidate and took another significant step towards a full fledged release of Movable Type 4.0. This release contains its usual impressive number of fixes, but if you look at the change log, the vast majority of issues addressed had to do with browser compatibility and minor style fixes. Many of the issues fixed were found by the community, but a large number were also found by our dedicated QA staff who have been engaged in a systematic and thorough walk through of a complex testing matrix looking at how Movable Type performs on multiple operating systems, databases and browsers.
Here are some highlights from the Movable Type 4.0 RC2 release:
But that only scratches the surface, more is documented in our change log.
So, do you think you are ready for MT4? Download and try it out for yourself now.
Here are some highlights from the Movable Type 4.0 RC2 release:
- A new configuration directive called "AllowedTextFilters" has been added that allows administrators to define what list of text editors (such as Markdown, Rich Text, Textile and others) they permit users on their system to use.
- A number of browser compatibility issues across Safari, Internet Explorer 6 and 7 and Firefox following an exhaustive sweep of the application.
- Movable Type has been translated into 5 different languages including German, French, Dutch, Spanish and Japanese.
- The plugin management screens have been significantly redesigned to give administrators a more compact and optimized view of the plugins installed in their system.
But that only scratches the surface, more is documented in our change log.
So, do you think you are ready for MT4? Download and try it out for yourself now.
Syca
August 3, 2007 10:17 AM | Reply
Great! Can't wait to install it.
One thing I've noticed still even as we get closer to the release is that in Firefox the WYSIWYG editor still doesn't use paragraph tags for paragraphs. It just uses break tags and un-escaped ones at that.
I remember seeing this issue in the "Known Issue's" list a few updates ago, but it has since disappeared without a fix. Has that fix been given up on?
If it's been fixed in RC2 then forgive me and this comment because I haven't installed it yet but didn't see it in the change log.
Jason
August 3, 2007 10:39 AM | Reply
I see in the changelog that the remaining styles have been "uploaded to sixapart.com" -- but how do we get access to them in our MT4 installations? On my installation -- which began life from the RC1 installer, and has now been upgraded to RC2 -- I have two categories, "Default Styles" and "MT4 Style Library". "Default Styles" has the nine shipping styles in it; "MT4 Style Library" is completely empty.
Bud
August 5, 2007 4:58 PM | Reply
I think this is a reasonable response to the rich text editor issues many have raised on pronet (and which I recall suggesting in an email last weekend even). Consider this same response for CAPTCHAs if people can't get those to reliably work on what seem like stock systems where everything indicates they should.
I think people understand that you may not be able to get all of the amazing number of planned features to work across the full set of "supported" systems by the time of the MT4 release. Well, let people opt out of features that just don't work.
Moreover, if the check says the feature is supposed to work (mine says this for CAPTCHA), it just should (CAPTCHA not working on my system). Otherwise, you think something is broken and lose confidence. Also, if you decide not to install an optional perl package like Image::Magick (because it is wildly complicated), you should not have to see an error message in your console about a feature not working because of it. Optional things should not lead to permanent error messages.