-
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.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 13
-
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.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 13
-
plone.app.locales-4.3.3-1.lbn13.noarch
This package contains the translation files for Plone Core and the
LinguaPlone add-on product.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 13
-
plone.app.lockingbehavior-1.0.1-2.lbn13.noarch
Locking integration for dexterity content objects.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 13
-
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.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 13
-
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.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 13
-
plone.app.querystring-1.1.1-1.lbn13.noarch
plone.app.querystring
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 13
-
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
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 13
-
plone.app.referenceablebehavior-0.5-1.lbn13.noarch
Referenceable dexterity type behavior
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 13
-
plone.app.registry-1.2.3-1.lbn13.noarch
Zope 2 and Plone integration for plone.registry
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 13
