Modified items

All recently modified items, latest first.

plone.portlet.static-2.0.2-1.lbn13.noarch: ============ A simple static HTML portlet for Plone 3.

plone.portlet.collection-2.1.5-1.lbn13.noarch: A portlet that fetches results from a collection

plone.portlet-1.0-1.lbn13.noarch: ============ plone.portlet module

plone.outputfilters-1.12-1.lbn13.noarch: plone.outputfilters provides a framework for registering filters that get applied to text as it is rendered. By default, these filters are wired up to occur when text is transformed from the text/html mimetype to the text/x-html-safe mimetype via the PortalTransforms machinery. With both Archetypes TextFields and the RichText field of plone.app.textfield, this transform is typically applied when the field value is first accessed. The result of the transform is then cached in a volatile attribute for an hour or until the value is replaced. Included Filters A default filter is included which provides the following features: Resolving UID-based links Adding captions to images (These are implemented as one filter to avoid the overhead of parsing the HTML twice.) These features used to be provided by similar transforms in both Products.kupu and Products.TinyMCE. New releases of these editors are being prepared which depend on the transform in plone.outputfilters, so that bugs don't need to be fixed in multiple places.

plone.openid-2.0.1-2.lbn13.noarch: This product implements OpenID_ authentication support for Zope_ via a Pluggable Authentication Service plugin. Using this package everyone with an OpenID authentity will be able to login on your Zope site. OpenID accounts are not given any extra roles beyond the standard Authenticated role. This allows you to make a distinction between people that have explicitly signed up to your site and people who are unknown but have succesfully verified their identity. Authentication flow ------------------- The OpenID authentication flow goes like this: - user submits a OpenID identity (which is a URL) to you site. This is done through a HTTP POST using a form variable called __ac_identity_url - the PAS plugin sees this variable during credential extraction and initiates a OpenID challenge. This results in a transaction commit and a redirect to an OpenID server. - the OpenID server takes care of authenticating the user and redirect the user back to the Zope site. - the OpenID PAS plugin extracts the information passed in via the OpenID server redirect and uses that in its authentication code to complete the OpenID authentication Session management ------------------ The PAS plugin only takes care of authenticating users. In almost all environments it will be needed to also setup a session so users stay logged in when they visit another page. This can be done via a special session management PAS plugin, for example plone.session.

plone.namedfile-2.0.5-1.lbn13.noarch: This package contains fields and wrapper objects for storing: * A file with a filename * An image with a filename BLOB based types are supported if the z3c.blobfile package is installed. This will also require the ZODB3 package to be at version 3.8.1 or later, and BLOBs to be configured in zope.conf.

plone.mockup-0.1-1.lbn13.noarch: The Plone Mockup is a project to modernize Plone's javascripts. Check out a demo at http://plone.github.io/mockup/ The project tries to achieve several goals: * Standardize configuration of patterns implemented in js to use HTML data attributes, so they can be developed and without running a backend server. * Use modern AMD approach to declaring dependencies on other js libs. * Full unit testing of js

plone.mocktestcase-1.0b3-2.lbn13.noarch: Mock unit test case based on ``mocker``

plone.memoize-1.1.1-2.lbn13.noarch: plone.memoize provides Python function decorators for caching the values of functions and methods. The type of cache storage is freely configurable by the user, as is the cache key, which is what the function's value depends on. plone.memoize has support for memcached and is easily extended to use other caching storages. It also has specialized decorators for use with Zope views. However, plone.memoize can be used without Zope.

plone.locking-2.0.4-2.lbn13.noarch: by Raphael Ritz, Jeff Roche, Martin Aspeli and others Provides basic automatic locking support for Plone. Locks are stealable by default, meaning that a user with edit privileges will be able to steal another user's lock, but will be warned that someone else may be editing the same object. Used by Plone, Archetypes and plone.app.iterate Basic locking ------------- By default, this is enabled on any ITTWLockable object. By default, this applies to any Archetypes content object. Stealable locks --------------- By default, locks can be stolen. That is, if a particular user has a lock and another user (with edit rights over the object) wants to edit the object, the second user can unlock the object. This is opposed to "safe" unlocking, which is done by the original owner. Categorised locks ----------------- So far, we have been managing a single type of lock. However, it is possible to manage different types of locks which are mutually exclusive. For example, if a particular type of lock is applied, it cannot be stolen by a user who is attempting to create another type of lock. Anonymous locking ================= When we are anonymous but do have edit rights we can also do a lock. Locking timeouts ================ Lock timeout should be ten minutes by default Turning locking on or off ========================= The status of the entire TTW locking mechanism can be controlled by setting up an ILockSettings adapter with a lock_on_ttw_edit property.

plone.keyring-2.0.1-2.lbn13.noarch: *plone.keyring* contains a Zope3 utility that facilitates handling of secrets in an application. Secrets are very important in modern applications, which is why a shared tool to manage them is useful. plone.keyring contains two basic components: * a *keyring*: a data structures which contains one or more secrets. * a *key manager*: a utility which contains the available keyrings and provides some convenience methods to manage them Keyrings ======== The keyring is the workhorse: it contains a set of secrets for a specific purpose. A ring has room for a fixed number of secrets which is set at creation time. The most recently added secret is considered to be the 'current' secret and the one that should be used. Older secrets in the ring can be used to keep data generated with older secrets valid for a period of time. Key manager =========== The key manager is a container for the available keyrings. It always contains a default system keyring which is used when no other ring is explicitly requested.

plone.intelligenttext-2.0.2-1.lbn13.noarch

plone.indexer-1.0.2-1.lbn13.noarch: This package provides primitives to help delegate ZCatalog indexing operations to adapters. It doesn't do very much on its own, but can be used by catalog implementations that want to allow individual index values to be provided not by the object itself, but by separate adapters.

plone.i18n-2.0.9-1.lbn13.noarch: Advanced i18n/l10n features useful in a CMS environment.

plone.formwidget.recurrence-1.2.1-1.lbn13.noarch: The plone.formwidget.recurrence package provides an Archetype and a z3cform widget for recurrence. The main GUI work is done with the jquery.recurrenceinput.js widget from http://github.com/collective/jquery.recurrenceinput.js . This widget also provides a simple textarea where a RFC 5545 compliant recurrence rule can be entered, if javascript is not available. The resulting value of the widget is a RFC5445 compliant recurrence rule string, ready to be used with python-dateutil's rrulestr.

plone.formwidget.namedfile-1.0.7-1.lbn13.noarch: Image widget for z3c.form and Plone

plone.formwidget.contenttree-1.0.7-1.lbn13.noarch: AJAX selection widget for Plone

plone.formwidget.autocomplete-1.2.6-1.lbn13.noarch: plone.formwidget.autocomplete is a z3c.form widget for use with Plone. It uses the jQuery Autocomplete widget, and has graceful fallback for non- Javascript browsers. There is a single-select version (AutocompleteFieldWidget) for Choice fields, and a multi-select one (AutocompleteMultiFieldWidget) for collection fields (e.g. List, Tuple) with a value_type of Choice. When using this widget, the vocabulary/source has to provide the IQuerySource interface from z3c.formwidget.query and have a search() method.

plone.formwidget-1.0.7-1.lbn13.noarch: plone.formwidget Python module/namespace base

plone.folder-1.0.5-1.lbn13.noarch: BTree-based folder implementation with order support

« Previous 20 items Next 20 items » 1 ... 2302 2303 2304 2305 2306 2307 2308 ... 2359


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

Sections

Modified items