-
plone-4.3.20-1.lbn25.noarch
Plone is ideal as an intranet and extranet server, as a document
publishing system, a portal server and as a groupware tool for
collaboration between separately located entities. A versatile
software product like Plone can be used in a myriad of ways. Look
through the sites that use Plone section to see a variety of ways
people have implemented Plone and Zope solutions.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 25
-
plone.app.contentmenu-2.0.12-1.lbn25.noarch
============
plone.app.contentmenu contains the logic that powers Plone's content menu
(the green one with the drop-down menus).
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 25
-
plone.app.contentrules-4.0.17-1.lbn25.noarch
plone.app.contentrules provides Plone-specific conditions and actions, as well
as a user interface for plone.contentrules.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 25
-
plone.app.customerize-1.2.3-1.lbn25.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.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 25
-
plone.app.debugtoolbar-1.0a2-1.lbn25.noarch
Debug toolbar for Plone
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 25
-
plone.app.dexterity-2.3.6-3.lbn25.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.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 25
-
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.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.folder-1.1.3-1.lbn25.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 25
-
plone.app.form-2.2.7-1.lbn25.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.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 25
