Plone 3.3. RC2 / 3.2.2

Plone is a content management system for web publishing and the Zope application server.
The system provides pre-configured security and roles, a set of content types, and multi-lingual support, among other features. Plone is available under both GPL and commercial licenses.

Main features:
- Plone is flexible and powerful. It is ideal as an intranet and extranet server, as a document publishing system, a portal server and as a groupware tool for collaboration between separately located entities.
- Plone is easy to use. The Plone Team includes usability experts who have made Plone easy and attractive for content managers to add, update, and maintain content.
- Plone is easy to install. You can install Plone with a click-and-run installer, and have a content management system running on your computer in just a few minutes.
- Plone is international. The Plone interface has more than 50 language translations, and tools for managing multilingual content.
- Plone is supported. There are close to a hundred developers in the Plone Development Team around the world, and hundreds of companies specializing in Plone development and support.
- Plone is standard. Plone carefully follows standards for usability and accessibility. Plone pages are compliant with US Section 508, and the W3Cs AA rating for accessibility, in addition to using best-practice web standards like XHTML and CSS.
- Plone is Open Source. Plone is licensed under the GNU General Public License, the same license Linux uses. This gives you the right to use Plone without a license fee, and to improve upon the product.
- Plone is extensible. There are many add-on products for Plone that add new features and content types. In addition, Plone can be scripted using web standard solutions and Open Source languages.
- Plone is technology neutral. Plone can interoperate with most relational database systems, open source and commercial, and runs on a vast array of platforms, including Linux, Windows, Mac OS X, Solaris and BSD.
- Plone is protected. The nonprofit Plone Foundation was formed in 2004 to promote the use of Plone around the world and protect the Plone IP and trademarks.

Enhancements
- This is not a final release. Experimental releases should only be used for testing and development. Do not use these on production sites, and make sure you have proper backups before installing.
- After Plone 3.2 (which focused on packaging/installer improvements), this is a minor release that adds some new features. It does not include any major changes: all products that work with Plone 3.0, 3.1 & 3.2 should also work in Plone 3.3. The upgrade from Plone 3.x is simple and non-invasive, ensuring a smooth upgrade experience.
Feature enhancements in this release:
Link type should automatically redirect when accessed directly:
- Links should be capable of doing automatic redirection.
Resource Registries Improvements:
- Allow Resource Registries to use conditional comments for CSS to bring the IEFixes.css into the registry and allow external references to resources for all registries.
Standardizing our use of INavigationRoot:
- Plone has the INavigationRoot marker interface which supports rooting your tabs, navigation, breadcrumbs, sitemaps and searches to a specific container inside of a portal which itself is a INavigationRoot. Some areas of this need to be cleaned up and standardized to follow a consistent convention.
Minor i18n upgrades:
- Include PloneLanguageTool 3.0 and PTS 1.5.
Disable inline editing by default:
- The current inline editing behaviour as introduced in Plone 3 was a mistake: it is a cool technology to show off, but in practice accidental clicks very frequently lead to unwanted edit-screens.
Adapterise the Extensible Indexable Object Wrapper:
- Make it easier to register ExtensibleIndexableObjectWrapper attributes with adapters
Improve locking configurability:
- This PLIP proposes to a) make it harder to accidentally leave content items in a locked state, and b) make it easier to adjust the lock timeout or disable locking entirely.
Clean up auto-sort, auto-order code:
- Clean up, i.e. remove all code related to auto-sorting / auto-ordering folder contents as this feature was implemented for Plone 2.1, but never got enabled. Basically this proposes to revert http://plone.org/products/atcontenttypes/roadmap/3
Replace workflow history viewlet with content history viewlet:
- Plone stores both workflow history and versioning history for objects. Only workflow history is shown in a viewlet in current Plone versions. I propose to show all history data.
View for rendering events as an iCalendar file:
- Make it possible to subscribe to Plone events in the standard iCalendar format.
Automate ZCML Loading for Plone Plug-ins:
- Enable automatic plugins for Plone with z3c.autoinclude