Greg has indicated in the news section that 3.4 has been released. He also indicates that the upgrade process from 3.2.2 "is complicated". Does anybody have more information on what this process encompasses ?
Its on the release notes screen of the 3.4.0 release. If you click any of those download links, it shows you a step by step process for upgrading from 3.2.2 to 3.4.0 (just scroll down a little).
Other than myself, Avi's also attempted a couple. They're complicated in that they can take a while to perform, the site will experience some downtime while everything comes together (at some point, the code is going to be different to the database tables it references), and there may be other things that come up from doing the upgrade that just hasn't been even considered before… for example, if you have right parenthesis in your design's url, and are using an import() statement for your stylesheet, firefox no longer sees the stylesheet because it thinks the import is about to close, whereas IE goes about its merry way.
Yes - the site upgrade we just completed went well except several odd things occurred. These include the actual table divisions loosing their Live status (easily fixed when the problem was located) and tables now formatting weirdly on IE 6 (they still work fine in FireFox). They now seem to truncate the contents and the rest seems to overflow into no where land (IE 6 never did this previously with 3.2.2).
However, beyond that the upgrade went relatively well.
When you say the tables are formatting weirdly, do you mean tables in the WYSIWYG or table assets? If you can describe the problem a bit more we can take a look at it too.
I examined the problem. In 3.2.2 when the tables were set at a 100% width and had a menu next to them they adjusted to fit into the web browser window. Likewise, with release 3.4 FireFox correctly did this as well. With IE 6 the tables were simply cut to fit in the screen basically cutting off any text which overflowed (eg. hid the remaining 10% of text or whatever). Since I removed the 100% width on the tables the problem has been resolved.
However, Matrix 3.4 is a worthwhile upgrade. I has fixed so many issues over 3.2.2 including the living editing module toolbar which now actually is usualable (e.g. doesnt seem to span several screens like it used to). Additionally, it feels slightly faster.
3.4 is significantly faster than 3.2 on large sites, btw.
You may be triggering an IE CSS bug with table widths set to 100% and a menu set to float: left. I know that I have to set a maximum table width of 95% or IE pushes the table down below the menu.