The Plone Content Management System
Project description
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/Perl 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 mantain 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 close to a 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 Download.
Changelog
3.2rc1 - December 15, 2008
Shifted profile and personal preferences to the left for RTL scripts. Closes http://dev.plone.org/plone/ticket/8169 [emanlove]
Load the plone.app.locales configure.zcml. This fixes http://dev.plone.org/plone/ticket/8788. [hannosch]
Cleaned up Livesearch results for RTL Languages. Closes http://dev.plone.org/plone/ticket/4632 [emanlove]
For RTL languages adjusted document content padding so welcome text fits inside text area. Closes http://dev.plone.org/plone/ticket/6919 [emanlove]
For RTL languages shifted portrait photo to the left. Closes http://dev.plone.org/plone/ticket/6214 [emanlove]
Added ‘context’ as an alias for ‘object’ in action expressions. [davisagli]
Include missing dependency on plone.app.locales. [hannosch]
Moved plone specific diff tool configuration back to Plone default profile, since it’s both plone specific and was never actually added to CMFDiffTool. Closes http://dev.plone.org/plone/ticket/8590 [alecm]
Fixed Forbidden error when attempting to login for the first time as a newly created user, if the must_change_password property has been added (as a Boolean) to the portal_memberdata tool and set to True. Closes http://dev.plone.org/plone/ticket/8425 [hexsprite]
Fixed the toc.js to not turn heading text containing an “@” into the link. Closes http://dev.plone.org/plone/ticket/7949 [sbruno, calvinhp]
Fixed the form_tabbing to use the correct buttons names. Closes http://dev.plone.org/plone/ticket/7559 [lucie, calvinhp]
Fixed the full_review_list select all link to only select the items shown and not all of the items at the portal root. This closes: http://dev.plone.org/plone/ticket/6991 [garbas, calvinhp]
Gave RTL.css higher priority within the stylesheet registry. loses http://dev.plone.org/plone/ticket/8505 [emanlove]
For RTL languages shifted Info Bar to the right. Closes http://dev.plone.org/plone/ticket/8140 [emanlove]
For RTL languages shifted comment icon to the right. Closes http://dev.plone.org/plone/ticket/6366 [emanlove]
3.2a1 - October 11, 2008
Take getNotAddableTypes into account when determining if the editable border should be shown. [wichert]
First fully eggified Plone release (ignoring the not yet eggified Zope2). [wichert]
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
