Installation

I'm going to assume that everyone reading this and testing out the beta has installed Movable Type before. If you have not, you should wait until MT 3.2 is released to production and documentation is available.

The differences in installation between Movable Type 3.2 and previous versions are outlined below:

• mt-config.cgi is the new config file combining mt.cfg and mt-db-pass.cgi. You must rename the distributed version (to remove the appended -original) and configure that file as normal. MySQL and Postgres users should also set the DBPassword directive in that file.

• All static files are now bundled in one directory called mt-static. If you are installing Movable Type into the cgi-bin, you can move that entire directory to somewhere under your web root and set the StaticWebPath to specify the path to the files (should end in mt-static/)

• There is no mt-load.cgi. Instead, you simply run mt.cgi.

Upgrade

First of all, back up everything before you upgrade!! This is still a beta which contains bugs with large, sharp teeth and one collective nasty grudge. Failing to back up your files and data will inevitably lead to the complete and utter loss of it all.

After that, it's easy easy easy! Just overlay the files onto your current installation and run mt.cg. There is no step 3!

What's new since Beta-1

Below represents a list of many — but not all — completed features and fixed bugs since the release of the first beta version of Movable Type 3.2. I will be adding to both of the sections below in a second, but wanted to get the beta in your hands ASAP.

More Features

The following are a number of features which are now fully functional but were either incomplete at the shipping of beta-1 or too buggy to be useful.

• Now shipping new MT 3.2 templates which are included in all new blogs. The templates in your existing blogs are not touched.

• Now supporting mt-config.cgi (with a new DBPassword directive) as a recommended replacement for mt.cfg and mt-db-pass.cgi, which are now deprecated. Distributing the config file as mt-config.cgi-original to prevent users from accidentally overwriting their active config file on uprrade.

• New upgrade process which eliminates the double-authentication necessary in beta-1.

• Changed button label of Rebuild button on index templates to reflect the new Save and Rebuild functionality

• Provided a option for intra-weblog auto-discovery (for sending TrackBacks to your own entries) on the New Entry Defaults settings page.

• Addressed an issue where upgraders who used external XML-RPC or Atom clients were required to set their API password after upgrade before they could use the client. Now, the old client setup will continue to work while also giving the user the opportunity to be more secure by setting a different password for access by those clients.

• Now logging upgrade action to activity log upon completion.

• Added itemset actions to the system blog list

• Return of the top View site link in a more proper location (which caused a surprising and wonderful uproar in its disappearance)

Fewer Bugs

Since the launch of the initial beta version, you all have submitted hundreds of bug reports which have, for the most part, been really excellent in terms of their detail and helpfulness to the MT team. Without that help, beta-2 would not be anywhere near as solid as it is. For that, the Movable Type team and Six Apart thanks you. You rock!

We've worked really hard behind the scenes going through those reports and working with our QA team to digest and address all of the known issues. Below is just a partial list of all of the bugs fixed since the initial beta version of Movable Type 3.2.

• Temporarily reverted a feature which suppressed the archive paths for upgraders whose archive paths were beneath the site path and added the archive path to the archive mapping table.

• Fixed an issue for those of you whose hosts are using a cgi-wrapper program called 'sbox' (e.g. GoDaddy) where you would be incorrectly redirected to a non-existent mt-upgrade.cgi script in your web root folder.

• Removed AUTOLOAD code from MT which was wreaking havoc with many plugins including BookQueueToo, MT-Protect, and others

• Fixed an upgrade bug that changed the status of all comments on closed entries to 'unpublished'

• Fixed an issue with some mod_perl setups under 3.16/3.17 which would return empty pages in the admin UI

• Fixed an bug that prevented the templates_c directory from being created and given the correct permissions when switching to dynamic publishing . Also added a warning in the administration UI if the directory can't be created because of lack of permission on the parent directory

• Fixed an issue with the rebuild button displayed on the feedback settings page. Now, those users using new (static) templates only need to rebuild indexes to have their changes take effect. Users with old templates must rebuild all of their individual archives.

• Fixed a bug which cause TrackBacks to be ignored in import

• Fixed an issue that prevented useful and accurate password reset notices from being printed to the activity log

• Fixed a bug where the lastn attribute of the MTEntries tag was being ignored if "Entries to display" was chosen on the General Settings page.

• Fixed a bug where comments from banned commenters were being accepted.

• Fixed a bug where the feedback scoring framework was activated despite not having plugins which use it installed. This caused all feedback to be sent to the junk folder if, for some reason, you raised your junk threshold above 0.

• No longer forcibly adding new index templates into existing blogs of during upgrade. New system templates are still added.

• Fixed a number of interaction issues between the new comment settings and the comment forms in default MT 3.1x and MT 3.2 templates.

• Fixed an issue with errors encountered during inline rebuilds (including on saving an entry) not displaying within the admin UI.

• Fixed a issue with upgrade where MySQL 5.x users would be shown an error about 'multiple primary keys'

• Fixed a bug with the TypeKey profile icon not being created under certain circumstances.

• Fixed an incorrect assumption in MT::App::CMS that caused problems with plugins which subclassed the class (would cause 'Can't call method "id" on an undefined value' error)

• Fixed a few areas in the application where links and buttons were displayed to users who didn't have permissions to use them leading to 'permission denied' errors.

• Now alphabetically sorting blog list on author permission page

• Now forcing database setup upon initialization instead of assuming a default of BerkeleyDB (./db)

• Fixed a broken link to mt-check.cgi System Overview Main Menu

• Fixed a bug that would suppress the comment and TrackBack tabs on the edit entry screen if they were disabled

• Fixed an issue with mod_perl where the weblog name would disappear after saving the general settings page (core config in 3.17)

• Fixed an issue with category editing where TrackBack pings could not be turned off once they were turned on

• Fixed Javascript errors on comment listing page (when clicking on Junk Comments) and search/replace screen (when selecting Is Junk)

• Fixed documentation in App.pm to indicate that a relative AltTemplatePath (like all relative paths in mt-config.cgi) is relative to the the MT config file and not to the tmpl directory.

• Fixed a broken imagine on the comment and ping editing pages

• Fixed a bug which cause category archive listings to return the wrong posts if you chose Entries to display on the general settings page.

• Fixed a problem with entry listings which would cause an error when displaying entries posted by deleted authors.

• Fixed a bug where TypeKey signin would be displayed in dynamic templates even if not set up due to a faulty tag (MTIfRegistrationAllowed)

• Fixed a bug with dynamic template conversion which would add code to an already present .htaccess file without adding a newline causing a webserver error

• Wrapped a number of phrases in MT_TRANS tags (for localization) which had been overlooked

• Fixed a bug which suppressed the "Limited Fields" option for commenters search.

• Fixed a bug with handling outrageous dates (the year 3000) on authors and entries listings.

• Now displaying reminder that servers running under mod_perl need to be restarted when plugins are enabled/disabled

• Fixed a bug on the comments listing screen when choosing to display all rows would revert back to 20 rows.

• Fixed a bug that would cause errors when setting the default Atom/RDF/RSS templates to dynamic publishing

• Fixed a problem with contextual search on templates pages which would cause a search of entries instead.

Known issues

We'll be updating the known issues list shortly.

Documentation

Unfortunately, the new 3.2 documentation is still being cooked up. It shouldn't be long before we can release it, assuming we stop opening the oven to check on it. Knowledge. Mmmmmmm, smells good.

Feedback

As usual, the following channels of feedback have been provided and we would appreciate it if you would use them for their respective functions:

• Bug reporting
• Support
• Feature requests

Pretty please? Danke!!!