Products.CMFPlone 4.2b2

The Plone Content Management System (core)

About Plone

Plone is a user friendly Content Management System running on top of Python, Zope and the CMF.

It benefits from all features of Zope/CMF such as: RDBMS integration, Python extensions, Object Oriented Database, Web configurable workflow, pluggable membership and authentication, Undos, Form validation, amongst many many other features. Available protocols: FTP, XMLRPC, HTTP and WEBDAV Turn it into a distributed application system by installing ZEO.

Plone shares some of the qualities of Livelink, Interwoven and Documentum. It aims to be the open source out-of-the-box publishing system.

What is Plone?

Plone is a ready-to-run content management system that is built on the powerful and free Zope application server. Plone is easy to set up, extremely flexible, and provides you with a system for managing web content that is ideal for project groups, communities, web sites, extranets and intranets.

• Plone is easy to install. You can install Plone with a a click and run installer, and have a content management system running on your computer in just a few minutes.

• 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 international. The Plone interface has more than 35 translations, and tools exist for managing multilingual content.

• Plone is standard. Plone carefully follows standards for usability and accessibility. Plone pages are compliant with US Section 508, and the W3C’s AAA rating for accessibility.

• Plone is Open Source. Plone is licensed under the GNU General Public License, the same license used by Linux. This gives you the right to use Plone without a license fee, and to improve upon the product.

• Plone is supported. There are over three hundred developers in the Plone Development Team around the world, and a multitude of companies that specialize in Plone development and support.

• Plone is extensible. There is a multitude of add-on products for Plone to 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.

Technical overview

Plone is a content management framework that works hand-in-hand and sits on top of Zope, a widely-used Open Source web application server and development system. To use Plone, you don’t need to learn anything about Zope; to develop new Plone content types, a small amount of Zope knowledge is helpful, and it is covered in the documentation.

Zope itself is written in Python, an easy-to-learn, widely-used and supported Open Source programming language. Python can be used to add new features to Plone, and used to understand or make changes to the way that Zope and Plone work.

By default, Plone stores its contents in Zope’s built in transactional object database, the ZODB. There are products and techniques, however, to share information with other sources, such as relational databases, LDAP, filesystem files, etc.

Plone runs on Windows, Linux, BSD, Mac OS X, and many other platforms; double-click installers are available for Windows and Mac OS X, and RPM packages are available for Linux. For full information, see the plone.org product page.

Changelog

4.2b2 (2012-02-09)

• Changed link from search to @@search for the “More” link in livesearch_reply. [vincentfretin]

• Notify ObjectModifiedEvent when a content title is modified through action > rename. Fixes http://dev.plone.org/ticket/12460 [thomasdesvenain]

• Fixed some mail tests in combination with five.pt. [maurits]

• Do not display the author contact form when the logged in user does not have an email address. Fixes http://dev.plone.org/ticket/12258 [maurits]

4.2b1 (2011-12-05)

• Define a ZCML feature called plone-42 in addition to the existing plone-4 and plone-41 to be used in conditional ZCML registrations. [vincentfretin]

• Allow “Site Administrator to add keywords” [kleist, suggested by keul]

• IE critical fix on toggle select and form submit helpers. [thomasdesvenain]

• Fixed the two high priority scenarios (global sections viewlet and nav portlet) of http://dev.plone.org/ticket/11189. [fulv]

• Call the view to unlock an item on unload synchronously, so that the call succeeds on Webkit browsers. This closes http://dev.plone.org/ticket/7885 [davisagli]

• Remove uneeded kss debugging code [jfroche]

• Allow users with the Manage Users permission to change the login name of other users; specifically this allows them to change the email address when this is used as login name. Fixes http://dev.plone.org/plone/ticket/11255 [maurits]

• Removed the ‘What’ row in the event view that displayed the keywords; this is already handled by the keywords viewlet. Fixes http://dev.plone.org/plone/ticket/10818 [maurits]

• Make control panel action GS export return actions alphabetically since there is no other natural ordering. [ggozad]

• Fixed folder_listing template so that listing macro can be used outside of folder_listing. [thomasdesvenain]

• Fix PloneTool.changeOwnershipOf to not pass MemberData to the underlying Owned.changeOwnership, but a plain User object only. [stefan]

• Fixed bug that treated ids of objects outside the portal, but on the acquisition path, as reserved. Fixeѕ https://dev.plone.org/ticket/10547 [rochecompaan]

4.2a2 - 2011-08-25

• AuthenticatedUsers group is used for local roles etc, and is not the same as Authenticated role. Thus, it can not be optimized away in catalog queries. [tesdal]

• getFolderContents only sets b_size if batching is true. [do3cc]

4.2a1 - 2011-08-08

• Added hidden year/month/day/hour/minute/ampm labels to calendar macros. Part of a form accessibility cleanup. [smcmahon]

• Removed registration of the input-label.js from the portal_javascript tool. Those with a desperate need to support the ‘placeholder’ text functionality in the obsolete browsers are free to re-register the script in their own instances. [spliter]

• Deprecated input-label.js — instead we are using the HTML5 ‘placeholder’ attribute on the input fields. [spliter]

• Deprecated IEFixes.css after we have introduced Modernizr and removed it’s GS registration. References http://dev.plone.org/plone/ticket/11300 [spliter]

• Added Modernizr 2 library. References http://dev.plone.org/plone/ticket/11300 [spliter]

• Switch to HTML5 doctype. References http://dev.plone.org/plone/ticket/11300 [spliter]

• Include plone.app.collection and related packages. Refs http://dev.plone.org/plone/ticket/10902 [esteele]