-
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.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 13
-
plone.app.discussion-2.3.3-1.lbn25.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.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 19
-
plone.app.discussion-3.4.0-2.lbn25.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.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 25
-
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.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 13
-
plone.app.drafts-1.1.2-1.lbn25.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.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 25
-
plone.app.drafts-1.1.2-1.lbn25.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.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 19
-
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.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 13
-
plone.app.event-1.2.7-1.lbn25.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.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 19
-
plone.app.event-1.2.7-1.lbn25.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.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 25
-
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
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 13
