First and foremost, we have fixed a lot of migration bugs that people on Plone 2.0.x were experiencing, and improved the migration code in general.
The result is that you should find the migration to Plone 2.1.2 from Plone 2.0.5 much easier now. To help with the migration, I recently wrote up a "migration guide for migrating a Plone 2.0 site to 2.1":/documentation/migration/2.1. Please read the entire migration document before you migrate; it will save you a lot of pain later. There is also a Chinese translation available.
If you tried migrating from Plone 2.0.x to 2.1 or 2.1.1 and failed, please try again with this release — migration is much improved.
Plone 2.1.2 also brings an amazing amount of bug fixes, "over 300 issues were fixed":http://trac.plone.org/plone/milestone/2.1.2 for this release, and the developers have made a tremendous effort to make this release as bug-free as possible.
Summarized, this is a very stable and polished release in the 2.1 series, and makes the Plone experience as polished and consistent as you are already pampered with. And if you couldn't make the jump from 2.0 earlier, make sure you try again with this release.
**On behalf of the Plone Team,**
— Alexander Limi
- "Download Plone 2.1.2":/download
- "Full change log for the 2.1.2 relase":/products/plone/releases/2.1.2
Some improvements in Plone 2.1.2
- All-new look for the Thumbnail (Photo Album) view - see screenshot above.
- A folder's display setting is now inherited from its parent on creation - so now the thumbnail view is the default if you create additional folders inside a folder with that view mode.
- Resolved most migration issues.
- Improved organization of CSS. Now, you can customize the public appearance of site just by deactivating or customizing the public.css and portlet.css files. This makes it much easier to skin a Plone site, and leads to less CSS code duplication. Existing CSS customizations will of course continue to work. Note: If you have already started using this technique before 2.1.2, you should review which classes have been moved. Full details are in the change log.
- Removed a lot of deprecation warnings.
- HTML filtering is now configurable. Although it needs a proper UI — planned for 2.1.3 — in the meantime, you can access the configuration at /portal_transforms/safe_html/manage_main.
- Login process is streamlined and had some improvements; you are no longer redirected to the "you are now logged in" page, but rather sent directly to the page you were trying to access. Note: If you have made significant customizations of the login scripts, you should review the changes before upgrading. "The particular changes performed can be inspected here":http://trac.plone.org/plone/changeset/8765.
- We simplified (i.e. reduced) the number of portlet-related classes that you should use. Only three classes are used now - portletHeader, portletItem and portletFooter - this makes it easier to make flexible portlet layouts. Your old portlets will continue to work. We will support this old markup in the 2.1 line, but it will be deprecated faster than usual (since the code that by mistake shipped in 2.1 was not supposed to be there).
- Tableless skin harmonized with the one using tables, minimizing duplication of code.
- Re-instated link to previous events in the events portlet.
- Made Plone smarter about logging out; if you are still logged in (since you're using HTTP auth), you will now be warned about this.
Notable bugs fixed
- Plone was showing the editable border on all content items when you were logged in as a Member. This is now fixed.
- Fixed the Internet Explorer visual bug where portlets would gradually lose their left margin and move further and further to the left the more elements were contained inside the portlet.
- Comments were connected to the wrong object (usually the parent) in certain cases; fixed.
- Various External Editor and WebDAV issues fixed.
- Meta tags were not emitted correctly, fixed.