You are here: Home

Modified items

All recently modified items, latest first.
RPMPackage plone.app.lockingbehavior-1.0.1-2.lbn13.noarch
Locking integration for dexterity content objects.
RPMPackage plone.app.locales-4.3.3-1.lbn13.noarch
This package contains the translation files for Plone Core and the LinguaPlone add-on product.
RPMPackage plone.app.linkintegrity-1.5.4-1.lbn13.noarch
This package tries to integrate PLIP 125, link integrity checking, into Plone. It is making use of the zope3 event system in order to modify Plone itself as little as possible.
RPMPackage plone.app.ldap-1.3.0-2.lbn13.noarch
plone.app.ldap provides a user interface in a Plone site to manage LDAP and Active Directory servers. This package succeeds the simplon.plone.ldap package. It builds on the functionality provided by LDAPMultiPlugins, LDAPUserFolder and PloneLDAP.
RPMPackage plone.app.layout-2.3.11-1.lbn13.noarch
This package contains various visual components for Plone, such as viewlets and general views.
RPMPackage plone.app.kss-1.7.1-3.lbn13.noarch
 
RPMPackage plone.app.jquerytools-1.5.6-1.lbn13.noarch
plone.app.jquerytools adds jquery.tools and some related overlay and form-handling JavaScript libraries to Plone. plone.app.jquerytools was developed for Plone 4. Earlier versions could be used in Plone 3.x by adding a zcml slug and running its GS Setup extension profile. This version requires Plone 4.x. Plone developers will wish to use plone.app.jquerytools to provide DOM popups, particularly if they require AJAX. There is extensive support for AJAX form posting. It's also useful for adding dateinput and forminput widgets that are HTML5 compatible. The AJAX and AJAX-form support is Plone-specific, and is documented in this module. Dateinput, rangeinput, accordions, and tooltips are all unchanged from jquerytools, and the jquerytools docs should be consulted.
RPMPackage plone.app.jquery-1.8.3-1.lbn13.noarch
plone.app.jquery adds jquery library to Plone. Version numbers of the package is the same as the jQuery library + packaging version.
RPMPackage plone.app.iterate-2.1.12-1.lbn13.noarch
iterate is a plone product that allows one to utilize a checkin / checkout procedure for content editing. It integrates in versioning, locking, and utilizes zope3 technology like adapters and events to allow for easy customization. Features -------- - versioning utilizing cmf editions - locking using zope dav locks - pluggable behavior for policies via adapters - observable behavior via events - specialized handling for archetypes references - simple, clean integration with the plone user interface Use Cases --------- iterate was designed to solve/enable the following use cases. Collaborative Document Editing Scenario ======================================= Workgroup or person working on a document, the ability to checkout and lock a document allows for a editing cycle, without concern of overwrites, and with an audit trail of versions. Publish/Modify/Review Cycles on a CMS ===================================== A common theme in content management, is publishing a web document, and then needing to revise it but not to change the published web content, till the modified document has undergone a review cycle. Iterate Lifecycle via the User Interface ---------------------------------------- iterate integrates with the plone user interface mainly through the actions menu. it adds three conditional actions to the menu.. checkout, checkin, and cancel checkout. checkout form ============= on this form a user is asked to which location they wish to checkout the current content, the vocabulary of checkouts is overridable via template customization and is currently the current folder, and the user's home folder. if the content is not yet versioned, versioning is applied and a new version is created before the checkout is performed. an adapter is utilized to perform the checkout mechanics and an object lifecycle event is generated with the baseline ( origin ) and checkout as attributes. the adapter is responsible for effecting a copy of the content to the checkout location and taking a lock on the origin content. whether this form and action are active on a given piece of content depends on the iterate policy adapter found for this content. checkouts have some system additional properties, versioning and workflow. they can be versioned independently of the baseline, with only changes from the latest version being merged into the baseline on checkin. they can undergoe separate workflows different from the baseline content. (this last feature requires some customization see docs/workflow.rst ). checkout status form ==================== visually checkouts are distinguished by an extra document icon (next to sendto, and rss links). clicking on this icon will lead to a checkout status page. which allows for looking at information regarding the checkout itself, such as when the checkout was performed and by whom. checkin form ============ a user is asked for a checkin message. on checkin the working copy is merged into the baseline, and a new version of the baseline is created, and the baseline is unlocked. cancel checkout =============== a confirmation dialog is displayed, if the checkout is canceled the working copy is destroyed, and the baseline is unlocked.
RPMPackage plone.app.intid-1.0.2-1.lbn13.noarch
Installation and migration support for five.intid within Plone/CMF
RPMPackage plone.app.imaging-1.0.10-1.lbn13.noarch
User-configurable, blob-aware image scaling for Plone.
RPMPackage plone.app.i18n-2.0.2-1.lbn13.noarch
Plone specific i18n extensions.
RPMPackage plone.app.form-2.2.4-1.lbn13.noarch
This package enables zope.formlib forms to work in Zope 2 code, styled to look like Plone forms. Note that developers should use zope.formlib directly, not Products.Five.formlib.
RPMPackage plone.app.folder-1.0.6-1.lbn13.noarch
Overview This package provides base classes for folderish Archetypes / ATContentTypes content types based on B-trees, a.k.a. "large folders" in Plone. Storing content in such folders provides significant performance benefits over regular folders. The package only contains the integration layer for the base class provided by plone.folder, however. Please see there for more detailed information. Caveats If you are using plone.app.folder in your product you may notice that PloneTestCase will fail to setup a Plone site for your functional tests. This can be resolved by adding this line to your functional test source: from plone.app.folder.tests import bbb
RPMPackage plone.app.event-1.2.1-1.lbn13.noarch
Plone.app.event is the calendaring framework for Plone. It provides Dexterity behaviors and an Archetypes type, Timezone support, RFC5545 icalendar export, Recurrence support, event views and a lot more. For a Dexterity event type using plone.app.event, use plone.app.contenttypes 1.1 or newer.
RPMPackage plone.app.drafts-1.0a2-2.lbn13.noarch
plone.app.drafts implements services for managing auto-saved content drafts in Plone. This addresses two problems: * If the browser is accidentally closed or crashes whilst a page is being edited, all changes are lost. * Some data may need to be managed asynchronously, e.g. via a pop-up dialogue box in the visual editor. This data should not be saved until the form is saved (and in the case of an add form, it is impossible to do so). The former problem pertains to any content add or edit form. The latter applies in particular to the "tiles" model as implemented by plone.app.tiles and its dependencies.
RPMPackage plone.app.discussion-2.2.12-1.lbn13.noarch
plone.app.discussion replaces the old commenting system in Plone 4.1 and is also available as an add-on product for Plone 3 and 4.
RPMPackage plone.app.dexterity-2.0.11-1.lbn13.noarch
Dexterity is a content type framework for CMF applications, with particular emphasis on Plone. It can be viewed as an alternative to Archetypes that is more light-weight and modular.
RPMPackage plone.app.debugtoolbar-1.0a2-1.lbn13.noarch
Debug toolbar for Plone
RPMPackage plone.app.customerize-1.2.2-2.lbn13.noarch
This package integrates five.customerize_ into Plone, which enables site administrators to customize templates used for five/zope3-style views, viewlets and portlets through the web via the ZMI in a way similar to overriding filesystem-based skin elements via the portal skin "customize" procedure.