Modified items

All recently modified items, latest first.

plone.app.search-1.1.7-1.lbn13.noarch: plone.app.search combines search results listing with Advanced Search form. This provides search results view for Plone CMS with possibilities to filter, sort and apply advanced filters to the search results without. When changing a search criteria on the search view, AJAX call is delivering you the updated results instead of reloaded page that lets you get to what you're searching for faster without much distraction caused by page reloading. The package is part of Plone 4.1. plone.app.search also updates main search field (usually located at the top right of your Plone site by default) and search portlet to return results in the updated listing view. plone.app.search has the aim to give intuitively clear and understandable interface for searching in Plone. But there might be some new things that are not so obvious. Let's see how the search results works now.

plone.app.robotframework-0.8.5-1.lbn13.noarch: plone.app.robotframework provides Robot Framework compatible resources and tools for writing functional Selenium tests (including acceptance tests) for Plone CMS and its add-ons. Plone/Robot Framework requires robot-server and an appropriate test layer: $ robot-server my.product.testing.MY_PRODUCT_ROBOT_TESTING To test plone.app.robotframework, this command would be something like: $ robot-server --no-reload plone.app.robotframework.testing.PLONE_ROBOT_TESTING Then we suggest something like the python-robotframework-ride graphical editor to open, run, and report Robotframework tests.

plone.app.relationfield-1.2.1-1.lbn13.noarch: Plone support for z3c.relationfield

plone.app.registry-1.2.3-1.lbn13.noarch: Zope 2 and Plone integration for plone.registry

plone.app.referenceablebehavior-0.5-1.lbn13.noarch: Referenceable dexterity type behavior

plone.app.redirector-1.2.1-1.lbn13.noarch: ============ Bring dead links back to life! plone.app.redirector knows where your content used to be and can bring you to its new location when content moves. This component expects you to register storage.RedirectionStorage as a local utility providing IRedirectionStorage (CMFPlone does this). Once that's done, the subscribers in subscribers.py will listen for object moved and object deleted events. When an object is moved (renamed or cut/pasted into a different location), the redirection storage will remember the old path. It is smart enough to deal with transitive references and circular references. When an object is deleted, all references to it are deleted as well. The view in browser.py contains methods (used in Plone's default_error_message.pt when it gets a NotFound error) that do the following: - attempt to redirect from the assumed intended path to the new path of an object, if the redirection storage holds a reference from the old path. - if not, look for the first valid parent of the assumed intended path, and present it as an option to the user - further, use the last id of the assumed intended path and attempt to search for objects in the catalog that contain this, presenting the options to the user

plone.app.querystring-1.1.1-1.lbn13.noarch: plone.app.querystring

plone.app.portlets-2.5.0-1.lbn13.noarch: plone.app.portlets provides a Plone-specific user interface for plone.portlets, as well as a standard set of portlets that ship with Plone.

plone.app.openid-2.0.2-2.lbn13.noarch: This packages makes Plone a complete OpenID consumer, allowing people to authenticate in a site using their OpenID identity. It relies on the plone.openid_ package to implement authentication of identities and needs an external session management plugin such as plone.session_ to add session management.

plone.app.lockingbehavior-1.0.1-2.lbn13.noarch: Locking integration for dexterity content objects.

plone.app.locales-4.3.3-1.lbn13.noarch: This package contains the translation files for Plone Core and the LinguaPlone add-on product.

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.

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.

plone.app.layout-2.3.11-1.lbn13.noarch: This package contains various visual components for Plone, such as viewlets and general views.

plone.app.kss-1.7.1-3.lbn13.noarch

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.

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.

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.

plone.app.intid-1.0.2-1.lbn13.noarch: Installation and migration support for five.intid within Plone/CMF

plone.app.imaging-1.0.10-1.lbn13.noarch: User-configurable, blob-aware image scaling for Plone.

« Previous 20 items Next 20 items » 1 ... 2370 2371 2372 2373 2374 2375 2376 ... 2425


	Copyright © 2000-2025 Corporation of Balclutha Inc. All rights reserved.

Sections

Modified items