-
ftw.bridge.client-1.0.7-1.lbn13.noarch
The ftw.bridge tools are used for communication between several Plone instances. It is
also possible to cummuncate with other web services. Requests between web services are
proxied through the ftw.bridge.proxy. This makes it possible to move or reconfigure
certain dependent webservices (clients) only by reconfiguring the proxy. The clients do
not know where other target clients are located - they only communicate with the proxy
directly, which forwards the requests to the target client.
Features
ftw.bridge.client integrates ftw.bridge support into Plone. It provides tools and
utilities for communication and authentication.
* Authentication: A PAS plugin authenticates requests and logs the user in on the
target client without transmitting his password. Only requests from the configured
ftw.bridge.proxy are authenticated.
* Requests: The IBridgeRequest utility is used for making requesting other clients.
It is also able to make remote catalog queries and transmitting the result brains
to the sources by using fake brains.
* Brain transport: By using a BrainRepresentation it is possible to get brains from a
remote client. A BrainSerializer utility serializes and deserializes all brain
metadata so that they can be used on the source client.
* Watcher portlet: A recently-modified portlet can be used for generic listing a list
of recently modified objects on the remote client but it is also possible to list
other links. There is a browser view @@watch which creates a recently-modified
portlet on the remote client dashboard. The watcher portlet loads its data
asynchronously using javascript for not blocking while loading the dashboard.
* Favorites: A browser view @@remote-add-favorite adds the context to the favorites
on the remote client dashboard.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 13
-
ftw.bridge.proxy-1.1.1-4.lbn13.noarch
ftw.bridge.proxy is a small pyramid based web application for proxying requests
between multiple plone instances. It's purpose is to isolate the plone instances
by routing through this proxy. This allows to easily move plone instances to
other servers.
Maintenance mode
Each configured client (plone site) can be switched into maintenance mode on the
bridge. When maintenance mode is enabled, the bridge answers every request to this
client with a HTTP 503 (Service Unavailable).
The maintenance mode can be enabled in the manage view of the bridge (/manage).
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 13
-
ftw.dashboard-1.3.4-1.lbn13.noarch
ftw.dashboard module
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 13
-
ftw.dashboard.dragndrop-1.5.3-1.lbn13.noarch
ftw.dashboard.dragndrop adds persistent dragndrop functionality to the standard plone dashboard.
http://onegov.ch/approved.png/image
Certified: 01/2013
Features:
Drag'n'drop: All dashboard portlets can be moved with drag'n'drop from column to column and reordered in the column.
Folding: Dashboard porlets are foldable.
Edit portlet icon: Dashboard portlets have an icon on the top (pencil) for editing the portlet.
close/remove portlet: Dashboard portlets have an icon on the top (cross) for removing the portlet from the dashboard.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 13
-
ftw.dashboard.portlets.postit-1.3.4-1.lbn13.noarch
How to use ftw.dashboard.postit
==================================
1.) Install the ftw.dashboard.portlets.postit product with the portal_setup tool.
2.) add a postit portlet to your dashboard
3.) create notes ...
Description:
============
the postit portlet is a usefull plone 3 portlet for your dashboard.
The adding and removing function are ajax implemented (jquery).
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 13
-
ftw.dictstorage-1.2-3.lbn13.noarch
This package provides a layer for storing key / value paires. The storage can be
configured dinamically by providing a IConfig adapter of the context on which the
dict storage is used.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 13
-
ftw.publisher.core-2.3.3-1.lbn13.noarch
The ftw.publisher packages provide tools for publishing plone contents from one instance to another.
This package provides shared tools and utils used by ftw.publisher.sender and ftw.publisher.receiver.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 13
-
ftw.publisher.receiver-2.0.2-1.lbn13.noarch
The ftw.publisher packages provide tools for publishing plone contents from one
instance to another.
This package should be installed on the receiver instance. It provides tools for
unserializing publishing requests and creating, updating or deleting objects.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 13
-
ftw.publisher.sender-2.2.0-1.lbn13.noarch
Introduction
The ftw.publisher packages provide tools for publishing plone contents from one instance
to another.
By providing a simple mechanism to invoke the publishing, it's possible to set up the
publisher in a variety of ways, such as workflow bound, manually invoked or automated
publication.
The ftw.publisher package library also provides a variety of surveillance and analysis
tools for making maintenance confortable.
Staging
The ftw.publisher is meant to be used in a environment where there are two seperate
plone-sites which do not share their database. The editors work on a editorial site and
the contents are published to a public site when they are ready. Setting up such an
environment with ftw.publisher let you have a powerful staging solution with completly
isolated instances.
Network security
Using an environment with two isolated installations makes it possible to protect the
editorial site with firewalls or to put it even in a private company network. This way the
editorial site is completly protected from the internet, which is in some use cases
mandatory for protecting other - unpublished - contents (for example when publishing the
internet contents from the intranet).
Component support
* Archetypes objects
* Standard Archetypes field types
* Topics: criterias are published automatically when topic is published
* Backreferences - references are added automatically as soon both objects are published
* Additional interfaces added on /manage_interfaces or by other products
* Contextual portlets
* Properties
With the publisher adapter structure it is as easy as creating another adapter to support
other components. For instance annotations are not supported by design, because you may not
want to publish all annotations but only certain ones. Therefore it is easyer to implement
custom adapters for those annotations which need to be published.
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 13
-
ftw.tabbedview-3.3.8-1.lbn13.noarch
Introduction
============
This package provides a generic view with multiple tabs for plone. It
provides a generic base tab for listing contents in a table, based on
`ftw.table`_.
Features
========
- Generic tabbed view
- Tabs are registered through FTI actions
- Base view for listing tabs
- Listing tabs are filterable
- Perform configurable actions on listed items
- `ftw.table`_'s `Ext JS`_ support works also in listing tables
- Fallback tables
- Drag'n drop multiple file upload functionality (using quickupload plugin)
Located in
LBN
/
…
/
Plone and Zope
/
BastionLinux 13