Forgot your password?
New user?
Document Actions
Plone
Category: Plone releases
—
Other products by this author
Current release: Plone 3.1.3
Released Jul 16, 2008
Bugfix release for Plone 3.1.x
List all releases… Full release announcement…
Get
Plone
for
Linux
(33MB)
Unified Installer - for Linux/BSD/OS X/UNIX/Solaris (compiles and installs Python, Zope and Plone plus dependencies for you)
Get
Plone
for
all platforms
(14 Mb)
Product Package (requires Zope 2.10.6 and Python 2.4.4 already installed)
Experimental releases
Upcoming and alpha/beta/candidate releases
- Alpha releases should only be used for testing and development.
- Beta releases and Release Candidates are normally released for production testing, but should not be used on mission-critical sites.
- Always install on a separate test server first, and make sure you have proper backups before installing.
Project Description
- Project resources
Documentation
Releases
Roadmap
Features
Project page
Issue tracker
Code repositoryPlone is powerful and flexible. 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 been translated into over 40 languages, 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 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 supported. There are close to a hundred developers in the Plone Development Team around the world, and a multitude of companies specializing in Plone development and support.
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.
Plone is built using Zope, an object oriented application server. The language that drives Zope and Plone is Python - the agile language preferred by Google, NASA, Industrial Light and Magic and many others. Why? Because Python offers unprecedented programmer productivity.
Errata for Plone 3.1.3
The version of plone.app.customerize shipping with Plone 3.1.3 contains a bug preventing new view template customizations via /portal_view_customizations. Existing customizations will continue to work.
To fix the problem an upgrade to version 1.1.2 is required. Buildout-based installations such as the one provided by the "Unified Installer" can easily be upgraded by making the following changes to buildout.cfg. For instances set up using the "Unified Installer" this file is located at zinstance/buildout.cfg relative to the target directory — usually /opt/Plone-3.1 or $HOME/Plone-3.1.
The required changes are: A new [versions] section needs to be added, for example directly after the [buildout] section:
[versions] plone.app.customerize = 1.1.2
In addition the line:
eggs = plone.app.customerize
needs to be added to the [plone] section. For a visual representation of these changes please refer to the ticket originally reporting the bug. After incorporating the changes buildout needs to be run again:
$ bin/buildout -n
The -n parameter should be used to ensure buildout is "Run in newest mode.".
