Movable Type Knowledge Base

Answer

• Configuration
  • A new application method ("app_path") prevents the login cookie from being set when Movable Type is installed in the root folder, rather than a subfolder. See Keep getting login screen for the solution.
• Archives
  • It is impossible to produce files with no file extension by using the File extension for archive files box. Even if you leave this setting empty, Movable Type will add .html automatically as a file extension.

  • After the first weblog, additional weblogs have category archives turned off by default, even though the default templates have category archives listed on the Main Index.
• Database Drivers
  • Movable Type is incompatible with DBD::Pg 1.4 because of a bug in that version of the database driver.

  • Plugins that need to save configuration data cannot be used with the DBI::postgres driver (mt_plugindata.data column has incorrect type).
• Categories
  • It is impossible to create two categories with the same name, even if they have different parents (on MySQL, PostgreSQL, or SQLite).

  • Better error checking disallows blank names in new categories, but they are still allowed when you edit and save a previously existing category.
• Templates, Tags and Attributes
  • When a template is linked to a file, changes to the file are not written to the database until the user views the template and hits the SAVE button. As a result, when using dynamic pages, changes to the file are not reflected on the dynamic pages until the user saves the template.

  • When using MySQL 4.1, "modified" date strings will be mangled - for example, the output of the <MTEntryModifiedDate> tag is incorrect. See MTEntryModifiedDate gives invalid output for further explanation of this issue.

  • <MTComments> with lastn attribute produces an error message on dynamic pages.

  • <MTEntryBasename> isn't yet supported in dynamic templates.

  • <MTCalendarCellNumber> isn't yet supported in dynamic templates.

  • The new locale attribute for <MTBlogLanguage> returns a value in dynamic templates that is inconsistent with its return value on static templates.

  • The recently_commented_on attribute to MTEntries may function incorrectly when the MTEntries block is nested in a constraining block such as MTSubCategories.

  • The Nofollow plugin removes HTML from body of MTPings. See this Knowledge Base article for the solution.

  • The show_email="1" attribute for <MTEntryAuthorLink> and <MTCommentAuthorLink> does not force email addresses to be displayed in static templates. For a workaround to this issue for commenter email addresses, see Show email addresses for commenters.
• TrackBack
  • If a post contains the URL of a large binary file (such as an image or a music file) and TrackBack auto-discovery is on, saving the post may fail.

  • TrackBack pings received from a site using a different character encoding are displayed incorrectly.

  • Under Windows XP (with IIS), the TrackBack URL that is displayed by <MTEntryTrackBackLink> does not work without further server configuration. See 404 on TrackBack URLs with IIS for more information.
• User Interface
  • Categories are shown without hierarchy in the Assign Multiple Categories... popup.

  • On some versions of Internet Explorer, after maximizing the QuickPost window, the entry text may appear wider than the window itself, obscuring the scrollbar.

  • Clicking Go Back when receiving an error in a pop-up rebuilding window only re-tries the last chunk of pages, rather than taking the user back to a previous choice. On full-page error messages, Go Back does return the user to the screen where the action was taken.
• Miscellaneous
  • When a thumbnail is generated for a GIF image with animation, the thumbnail appears broken.

  • If an error occurs while run-periodic-tasks is running, an entry may be put into Published status but not rebuilt.

  • When importing or exporting a weblog, unique IDs in Atom feeds may change.

  • When a reader submits the Mail This Entry form, no confirmation is displayed.

  • The Documentation Link for the Nofollow plugin results in a Six Apart "page not found" error. See Link to Documentation for Nofollow is broken for the correct link, and how to patch the file if desired.