The Plone Content Management System (core)
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 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.
Installing Plone
Plone is available on Microsoft Windows, Linux, OSX and BSD platforms.
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.3b2 (2013-01-17)
removing plone_ecmascript/test_ecmascripts.pt since its not working and since its not being ran by out test suite. [garbas]
Call searchUsers with the ‘name’ argument instead of ‘login’. ‘name’ is the officially supported way according to the PAS interface. [maurits]
4.3b1 (2012-01-02)
Changes to dependencies when creating a new site (plone-final) to fix #11997. [keul]
Generate valid atom feeds [lentinj]
Fix quoted atom.xml feed syndication content type to “html”. [elro]
Add various security fixes based on PloneHotfix20121106. [davisagli]
Fix RegistrationTool testPasswordValidity method. See https://dev.plone.org/ticket/13325 [vipod]
Fix form_tabbing.js so it stays on the same fieldset when an Archetypes edit form is submitted and returns to itself. [davisagli]
Use the ‘OFS.ObjectManager.bad_id’ pattern in ‘PloneTool.BAD_CHARS’. This allows names containing ‘@’ to pass ‘check_id’. [elro]
Pass minute_step to date_components_support_view.result(). See https://dev.plone.org/ticket/11251 [gbastien]
Improve error handling on paste action. If it is a real error, the error gets shown and logged. [do3cc]
Fix sitemap rendering. No longer uses portlet_navtree_macro.pt from the plone_deprecated skin, but a browser view template with much simplified logic. [danjacka]
Revealed hidden features for sorting folders (#11317). [keul]
Don’t swallow exceptins on object_paste and folder_paste (#9365). [gaudenz]
4.3a2 (2012-10-18)
Use prefixed ids for popup overlays [maartenkling]
Fix compatible hide fieldset legend for IE6/7/8 in form_tabbing.js [maartenkling]
Add an animated indicator of AJAX loading via Javascript. It is now called #ajax-spinner and is no longer added in main_template. [davisagli]
Remove Plone’s dependency on KSS. plone.app.kss is now an optional add-on. Functionality that used to be provided using KSS has been reimplemented. [esteele, vangheem, cah190, davisagli]
Do not block right-side portlets in Members folder on site creation. This fixes https://dev.plone.org/ticket/10764 [polyester]
Fix prefs_install_product_readme so files with non-ascii characters are rendered. This fixes https://dev.plone.org/ticket/12342 [ericof]
Fix StringIO module security so it can still be imported from restricted code in Zope 2.13.17+. [davisagli]
Filter out non existing types in getUserFriendlyTypes. This avoids an error on the search form when a no longer existing portal_type is still in the catalog. [maurits]
Declare Plone’s dependency on Pillow. [davisagli]
Merge syndication plip 12908 [vangheem]
Add body class depth registry field [vangheem]
Check if an item is locked before attempting to delete. Refs #11188 [eleddy]
We can safely move the MAX_TITLE to 50 and even move up MAX_DESCRIPTION 150 refs #11321 [maartenkling]
Remove inline styles, they do nothing, add class so someone can style it when they like refs #12438 [maartenkling]
Show forget password when entering wrong credentials refs #12463 [maartenkling]
Remove h3 to make consistent html refs #11344 [maartenkling]
Fix ‘Add New’ on Users/Groups Overviews shows overlay when clicking anywhere in form #12201 [maartenkling]
Fix events_listing #12477 [maartenkling]
Fix form_tabbing, to stay on current tab on submitting form [maartenkling]
4.3a1 (2012-08-31)
Hide ‘plone.resource’ and ‘collective.z3cform.datetimewidget’ from the site factory screen. These are only useful as dependencies of other packages. [optilude]
Define a ZCML feature called plone-43 in addition to the existing ones. [thet]
Deprecated getSiteEncoding and changed occurences to hardcoded utf-8 [tom_gross]
zope.globalrequest is a required dependency on tests. [hvelarde]
Make sure the ResourceRegistries registry setting is created for new sites. [davisagli]
Searches ignore accents. PLIP http://dev.plone.org/ticket/12110 [thomasdesvenain]
IE critical fix on toggle select and form submit helpers. [thomasdesvenain]
Fixed javascript injections on jquery.highlightsearchterms.js [gborelli]
Tweak rules for sortable_title. So far we took the first 70 chars and zero-padded numbers to six digits. Now we zero-pad to four digits and take the first 30 and the last 10 characters, thus saving space while still distinguishing long titles which only differ at the end, like imported file or image names. [hannosch]
PEP 8 (ignoring W602, E203, E241, E301, E501 and E701). [pbdiode, hvelarde]
Add ‘displayPublicationDateInByline’ to site properties property sheet in order to finish PLIP #8699: Display publication date in author byline. [vipod]
Deprecated aliases were replaced on tests. [hvelarde]
Don’t register the plone_deprecated skin layer. These items are no longer supported as part of Plone and remain here temporarily as a convenience to those who may need to move them into their own packages. [davisagli]
Ensure multiple tabbed forms on the same page work when number of tabs is greater than threshold. [davidjb]
Remove deprecated jq reference from form tabbing JavaScript. [davidjb]
Remove incorrect line of form tabbing JavaScript which broke forms with more than 6 tabs. Fixes https://dev.plone.org/ticket/12877 [davidjb]
accessibility improvements for screen readers regarding “more” links, see http://dev.plone.org/ticket/11982 [rmattb, applied by polyester]
Fix an outdated “Send this” form handler property reference. [rossp]
removed search_form-template form plone_deprecated-skin. Use collective.searchform if you need this functionality. [tom_gross]
Use plone.batching for all batches (PLIP #12235) [tom_gross]
Re-apply PLIP 10901 to table_sort.js, fixing a bug with reversing sort on the first column. [mj]
support a PAS plugin for validating passwords PLIP http://dev.plone.org/ticket/10959 [djay75]
Make redirection_view/attempt_redirect fall back to nothing in default_error_message template. If plone.app.redirector gets a URL with special characters, OOBTree.get raises a UnicodeDecodeError and the template fails. This fixes http://dev.plone.org/ticket/12976.
Channel link in RSS feed now points to the un-syndicated content for the RSS feed, instead of the portal root. [patch by pydanny, applied by kleist]
Removed unused “localTimeFormat”, “localLongTimeFormat”, and “localTimeOnlyFormat” from “/portal_properties/site_properties”. Fixes https://dev.plone.org/ticket/11171. [kleist]
CatalogTool.py, PloneBatch.py, PloneFolder.py, PloneTool.py, Portal.py: Don’t use list as default parameter value. [kleist]
Use configuration registry to override translation of date format, or fall back to ISO style as last resort. Fixes http://dev.plone.org/ticket/11171 [kleist]
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.
