Skip to main content

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 the plone.org product page.

Changelog

3.2.2 - March 3, 2009

  • Register 3.2 -> 3.2.1 migration step with the migration machinery. This fixes problems due to a missing site property for migrated sites. [matthewwilkes]

  • Fix the internalization of folder_rename status message http://dev.plone.org/plone/ticket/8750 [encolpe]

3.2.1 - February 4, 2009

  • Add dependency on Products.NuPlone to prevents sites who use NuPlone from breaking when upgrading from Plone 3.0.x or 3.1.x to 3.2 or later. [wichert]

  • Fix contact_info.cpt so it bases the appearance of the fullname and email fields on whether they are set in the current member’s profile, rather than on whether the current user is anonymous or not. This closes http://dev.plone.org/plone/ticket/8526 [davisagli]

  • Update default frontpage to refer to Plone 3 instead of 3.0. [wichert]

  • Added time_only for use with toLocalizedTime so that event_view now localizes the start/end times if the start/end dates are the same. Added migration for 3.2 to 3.2.1 to add new property to the propery tool. Closes http://dev.plone.org/plone/ticket/8607 [jnelson, calvinhp]

  • Fixed links-plain issue on the front-page. This closes http://dev.plone.org/plone/ticket/6479. [cwainwright, calvinhp]

  • Put in workaround for IE6 background caching problem, closes http://dev.plone.org/plone/ticket/7445 [cwainwright, calvinhp]

  • Removed old background icon from personal bar for RTL scripts. Closes http://dev.plone.org/plone/ticket/4570 [emanlove]

  • Moved history icon off text and shifted history header to the right under RTL scripts. Closes http://dev.plone.org/plone/ticket/6368 [emanlove]

  • Cleaned up document actions for RTL scripts. Closes http://dev.plone.org/plone/ticket/8863 [emanlove]

3.2 - December 31, 2008

3.2rc1 - December 15, 2008

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]

Project details


Release history Release notifications | RSS feed

This version

3.2.2

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

Plone-3.2.2.zip (1.6 MB view hashes)

Uploaded Source

Supported by

AWS AWS Cloud computing and Security Sponsor Datadog Datadog Monitoring Fastly Fastly CDN Google Google Download Analytics Microsoft Microsoft PSF Sponsor Pingdom Pingdom Monitoring Sentry Sentry Error logging StatusPage StatusPage Status page