-
python3-plone-api-1.11.1-1.lbn36.noarch
plone.api A simple API, built for humans wishing to develop with Plone.The
intention is* to cover as much as possible the tasks carried out by a Plone
developer * to provide clear API methods for Plone functionality which may be
confusing or difficult to access, * keeping everything in one place, * staying
introspectable and discoverable, important aspects of being Pythonic.
Located in
LBN
/
…
/
Plone 5
/
BastionLinux 36
-
python3-plone-app-blob-1.8.2-1.lbn36.noarch
plone.app.blob Overview This package aims to be an add-on for Plone (> 3.x)
integrating ZODB (>3.8) blob support, which allows large binary data to be
managed by the ZODB, but separately from your usual FileStorage database, i.e.
Data.fs. This has several advantages, most importantly a much smaller Data.fs
and better performance both cpu- as well as memory-wise. .. |__| unicode:: U+20
.....
Located in
LBN
/
…
/
Plone 5
/
BastionLinux 36
-
python3-plone-app-blocks-6.0.1-1.lbn36.noarch
Introduction to Blocks This package implements the 'blocks' rendering model,
by providing several transform stages that hook into plone.transformchain.The
rendering stages are:plone.app.blocks.parsexml (order 8000) Turns the response
in a repoze.xmliter XMLSerializer object. This is then used by the subsequent
stages. If the input is not HTML, the transformation is...
Located in
LBN
/
…
/
Plone 5
/
BastionLinux 36
-
python3-plone-app-blocks-6.0.1-1.lbn36.noarch
Introduction to Blocks This package implements the 'blocks' rendering model,
by providing several transform stages that hook into plone.transformchain.The
rendering stages are:plone.app.blocks.parsexml (order 8000) Turns the response
in a repoze.xmliter XMLSerializer object. This is then used by the subsequent
stages. If the input is not HTML, the transformation is...
Located in
LBN
/
…
/
Plone 5
/
BastionLinux 36
-
python3-plone-app-caching-2.2.1-1.lbn36.noarch
plone.app.caching Introduction plone.app.caching provides a Plone UI and
default rules for managing HTTP response caching in Plone. It builds on
z3c.caching, plone.caching and plone.cachepurging.plone.app.caching version 2.x
requires Plone 5.2 or later. For earlier Plone versions, use a release from
branch 1.x. Installation plone.app.caching is shipped as a dependency of the
Plone package....
Located in
LBN
/
…
/
Plone 5
/
BastionLinux 36
-
python3-plone-app-changeownership-1.0-1.lbn36.noarch
Introduction plone.app.changeownership as it sounds is a Plone package to
change objects ownership.Problem While for a single content you can call the
/change- owner view, there is no way in Plone to transfer **ownership of all
objects** owned by an user to a new user. To delete a Plone member in such case
is not an option. Solution plone.app.changeownership makes easy to transfer
ownership...
Located in
LBN
/
…
/
Plone 5
/
BastionLinux 36
-
python3-plone-app-collection-1.2.8-1.lbn36.noarch
Collections in Plone are the most powerful tool content editors and site
managers have to construct navigation and site sections.This is a brand new
implementation of collections for Plone, using ajax/javascript to make a
simpler, easier and streamlined user experience for using collections. Having a
more lightweight backend that does not depend on many nested criteria
types.It's designed with...
Located in
LBN
/
…
/
Plone 5
/
BastionLinux 36
-
python3-plone-app-content-3.8.10-1.lbn36.noarch
Introduction plone.app.content contains various views for Plone, such as
folder_contents, as well as general content infrastructure, such as base
classes and name choosers. Source Code Contributors please read the document
Process for Plone core's development < are at the Plone code repository hosted
at Github < Changelog .. You should *NOT* be adding new change log entries to
this file. You...
Located in
LBN
/
…
/
Plone 5
/
BastionLinux 36
-
python3-plone-app-contentlisting-2.0.8-1.lbn36.noarch
Listing and working with Plone content objects using plone.app.contentlisting
This is valid for Plone 4.1 upwards.Many of the operations for customizations,
templates, views and portlets in Plone are related to lists of content objects.
Their sources can be different, although usually they are some sort of catalog
search, the contents of a particular folder or a list of objects from a...
Located in
LBN
/
…
/
Plone 5
/
BastionLinux 36
-
python3-plone-app-contentmenu-2.3.4-1.lbn36.noarch
Introduction plone.app.contentmenu contains the logic that powers Plone's
content menu which is part of the toolbar.It provides the menus items (and its
submenues) for- factories menu (order10) - workflows menu (order20) - actions
menu (order30) - display menu (order40) - manage portlets menu (order50)Note
that menu items are ordered by an 'ordered' property. To allow third party
products to...
Located in
LBN
/
…
/
Plone 5
/
BastionLinux 36