« The Movable Type 3.3 beta begins... | Main | Movable Type 3.3 (Beta-1) release notes »

Known issues with Movable Type 3.3 beta

Like any beta software, there are a few known issues. Below is a list of those issues which will be updated continuously until the final release.

Extremely important issues

The following known issues are extremely important and should be understood before upgrading to Movable Type 3.3 (Beta-3):

Other known issues

The following are known issues in Movable Type 3.3 (Beta-3) and shall be fixed in an upcoming release:

  • Many actions for Activity log and feed items have not yet been implemented

Previously reported/fixed issues

  • The number of entries on the tag listing screens is inconsistent with the number of entries returned when clicking on it if the tag is a non-normalized derivative of another tag (e.g. Tag vs tag vs t.a.g)
  • Weirdness abounds in multiple blog searches from the public blog (i.e. not from admin interface)
  • Users without the XML::Parser perl module installed will receive an error upon request for Activity feeds.
  • The entry tags auto-complete feature is currently disabled
  • The template textarea height is not persistent after resize and save
  • A warning is not currently triggered when navigating away from an edited template

Won't fix prior to release

  • Entry tag intersections are not currently supported in the tag search mode

Comments

I'm not sure if you know this or not, but when I go to make a new entry, and hit save, it won't save. I have to preview it and then save it in order for it to be saved. My MT is on a linux server, Kernel version 2.6.16.16-grsec, Machine Type i686, Apache version 1.3.34 (Unix), PERL version 5.8.5, PHP version 4.4.2, and MySQL version 4.1.19-standard...I'm not sure if any of that helps you at all or not :$ But that's almost all of the info I get from the control panel of my domain =)

Hi Heidi. Thanks for the note. If you feel like you've found a bug and you've tested it on the latest beta (currently Beta-3), please go ahead and submit a full bug report. By submitting it through the form, it is entered directly into our bug tracking software where the MT engineering team will see it. This eliminates the need for the engineers to waste precious moments trawling through may comments and forum posts searching for bugs.

The only thing that I can imagine causing your problem is an out-of-date mt.js in the mt-static folder. Again, try updating to the latest beta and testing to see whether or not it still occurs.

Thanks again for the note!

Post a comment



Six Apart
Makers of weblog software and services for individuals, organizations and businesses.
This website is powered by Movable Type.