-
Products.BastionBanking-VeriSign-4.2.3-2.lbn19.noarch
VeriSign PayFlow API
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 19
-
Products.BastionBanking-VeriSign-doc-4.2.3-1.lbn19.noarch
VeriSign PayFlow API documentation
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 19
-
Products.BastionBase-5.1.3-1.lbn25.noarch
Wrappers to isolate ourselves from Zope source code changes with
which we disagree.
A set of utility functions to manage Zope installations
Useful base classes (Archetypes wrappers), tools for Plone (timezone tool),
JSON/Properties support and some indexing/OCR features.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 19
-
Products.BastionBase-ldap-5.1.3-1.lbn25.noarch
Role management into LDAP/PAS
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 19
-
Products.BastionCrypto-4.4.0-2.lbn25.noarch
BastionCrypto, Zope-ZMI PGP/X509 cryptographic suite
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 19
-
Products.BastionLedger-5.1.1-1.lbn19.noarch
General Ledger, Order Management, Debtor and Creditor Management,
Shareholder Management, Asset Register, Forecasting, ...
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 19
-
Products.BeakerSessionDataManager-1.1-1.lbn19.noarch
Products.BeakerSessionDataManager is a replacement for the default Zope 2 session implementation. It
uses Beaker as a backend (via collective.beaker) and adapts the Beaker session to provide the same
interface as a normal Zope session.
Beaker is a better alternative to the default session implementation for several reasons:
* The Zope session implementation does not perform well in high-write scenarios.
* Beaker provides better flexibility in where session data is actually stored.
* Beaker is used and maintained outside of the Zope ecosystem.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 19
-
Products.BlueAwstats-2.0-9.lbn19.noarch
BlueAwstats is a front-end for the third party software AWStats log
file analyzer and statistics generator.
AWStats itself consists of two parts: A log file analyzer to compute
raw-statistical data and a renderer for websites. BlueAwstats is using
the raw statistical data and replacing the html-renderer.
BlueAwstats consists of three parts:
1. python module bda.awstatsparser to parse raw-data files generated
by AWStats, see http://pypi.python.org/pypi/bda.awstatsparser
2. Zope Product BlueAwstatsMangementTool defines the settings i.e. the
path to the awstats-raw-data on the filesystem and constraining the
sites available.
3. CMF/Plone Product BlueAwstats to be placed as a tool in the Plone-site.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 19
-
Products.BlueAwstatsManagementTool-2.0-3.lbn19.noarch
BlueAwstatsManagementTool is a products to manage access to the available
statistics from AWStats on a Server.
Added outside a plone site in the ZMI you can controll access to statistics in
general.
Installed Inside a plone site you have better abilities to control access to
statistics on user level.
There must be at least one Management Tool inside a zope instance to use
BlueAwstats (and only one per folder level). The first one found by aquisition
is used for the calling plone site.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 19
-
Products.CMFActionIcons-2.1.3-3.lbn25.noarch
The action icons tool provides a centralized registry mapping CMF
"actions" (identified by their category and ID) to additional presentation
metadata (display title and icon). The skins here show alternative
mechanisms for using this metadata within a site template.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 19
