BigPAPI plugin incompatibility
Movable Type 3.3 introduces the ability to create "Transformer plugins" which can modify and control input and output for the Movable Type admin interface in any way. This feature was not only inspired by Kevin Shay's BigPAPI plugin but actually uses an extremely similar model. However, because BigPAPI overrides the portion of the Movable Type code which offers this function, it has the potential to cause severe weirdness.
If you are upgrading an installation to Movable Type 3.3, you should disable BigPAPI from the System Overview plugin listing if you have it installed. We shall shortly have updates for all known BigPAPI plugins which use the native Transformer plugin callbacks.
Posted on June 2, 2006 3:01 PM in Known issues
Comments
Now that 3.3 is about to be released, is there an update on this? I've got one site that I can't upgrade until I know that these plug-ins are working as the users expect.
Posted by: Judi Sohn![[TypeKey Profile Page]](http://www.sixapart.com/movabletype/beta/nav-commenters.gif)
|
June 28, 2006 5:24 AM
Judi, I have 3.3-compatible versions of my BigPAPI-based plugins (except for WeblogsActionMenu, which is still a bit up in the air--there was a discussion on ProNet about this) ready to go as soon as 3.3 is released:
RightFields MainMenuRecent LinkEntryToFile UpdateAuthoredOn
Changing the callbacks is literally a matter of renaming them, which should take a couple of minutes for any given plugin. However, since some of the CMS templates are different in 3.3, the template code a plugin is trying to replace may need to be modified slightly within the plugin.
Posted by: staggernation![[TypeKey Profile Page]](http://www.sixapart.com/movabletype/beta/nav-commenters.gif)
|
June 28, 2006 8:32 AM