Products.CMFPlone 4.1a2

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.1a2 - 2011-02-10

• On search form don’t show list of users when anonymous unless explicitly allowed in @@security-controlpanel. Fixes http://dev.plone.org/plone/ticket/11346 [msmith64]

• Add fallback icon for control panels with no icon, in the portlet_prefs portlet. This fixes http://dev.plone.org/plone/tickets/11112. [topherh, davisagli]

• Use the new optimized BooleanIndex for the is_default_page and is_folderish indexes and the new UUIDIndex for the UID index. [hannosch]

• Remove js-generated inline style from searchbox. Same CSS is in public.css. Fixes http://dev.plone.org/plone/tickets/11186. [msmith64]

• Use nocall: when getting the @@sitemap_view in sitemap.pt. [elro]

• Hide plone.app.registry, z3c.form as an add-on options from the @@plone-addsite view, quickinstaller. [esteele]

• Merge in PLIP #9288: Improved commenting infrastructure. Refs http://dev.plone.org/plone/ticket/9288 [timo]

• Fixed handling of relative links used as default pages http://dev.plone.org/plone/ticket/11340 [fRiSi]

4.1a1 - 2011-01-18

• Removing unused import from testCatalogTool. [thet]

• Alphabetical ordering of metadata.xml dependencies. [thet]

• Using tom gross’ improved and tested safeToInt version. [tom_gross, thet]

• Move PlacefulWorkflow, kupu, iterate and openid to Plone egg dependencies. [elro]

• Depend on plone.app.uuid for indexing content UUIDs. [toutpt, davisagli]

• Added ++resource++blank.html, a building block for cross-domain iframe communication (e.g. with Disqus.) [elro]

• Added iframe option for single sign on login templates. [elro]

• Removed duplicate code in login templates. [elro]

• Added ajax_include_head request parameter for use with cross domain iframe. [elro]

• Single Sign On support in login forms. [elro]

• Refactored URLTool.isURLInPortal, adding allow_external_login_sites property to site_properties for external sites considered to be internal for the purposes of logging in. [elro]

• Improve table sort of ‘listing’ class tables. We can use a sortabledata-xxxx class in a cell (td) where xxxx is a sortable data value, then, sort uses xxxx value to compare cell values, instead of td text content. Refs http://dev.plone.org/plone/ticket10809 [thomasdesvenain]

• Merge in PLIP #10901: Set and enforce base coding standards for our own JavaScript. Refs http://dev.plone.org/plone/ticket/10901 [esteele]

• Removed IOrderedContainer-implementation from PloneFolder in favour of implementation in OFS.OrderSupport [tom_gross]

• Renamed package to Products.CMFPlone. [elro]

• Deprecated the following scripts that are only used by deprecated templates. These will be removed in Plone 5: prefs_group_edit.py, prefs_valid_search_restriction.py, prefs_user_group_search.py, prefs_portrait_delete.py. [davisagli]

• Replaced the prefs_group_details.pt template with a browser view in plone.app.controlpanel. Ss a side effect this means group creation is now protected by the Plone Users and Groups control panel permission, rather than the CMF Manage Groups permission. [davisagli]

• Turn plone_control_panel.pt into a deprecated alias for the @@overview-controlpanel view from plone.app.controlpanel. [davisagli]

• Protect most control panels with specific permissions instead of the generic “Manage portal”. [davisagli]

• Configure the Site Administrator role in the default rolemap and workflows. This role is intended for people who should have full content editing privileges but not Manager access (i.e. to the ZMI). [davisagli]

• Updated to use Zope 2.13. [hannosch]