You are here: Home

Modified items

All recently modified items, latest first.
RPMPackage Products.CMFEditions-2.2.9-1.lbn13.noarch
CMFEditions provides versioning in Plone. - It works out of the box. - It's higly extensible for specific use cases. Out Of The Box Experience ------------------------- Versionable content items edit views now allows saving a version on save (automatically or manually). The version history may be accessed quickly from the view view. Versionable content types also have an additional tab with version related functionality: - save new version - preview an old version - retrieve an old version (replacing the current state in the tree) - diffing versions A content panel allows configuring the versioning policy by content type: - enable or disable versioning - auto-versioning on save - auto-versioning on retrieve By default the contents of a folder is versioned independently of the folder. This may be changed through the ZMI and for specific cases on python level. Basic support for Archetypes references is built in. The current strategy is to save everything of the content item (incl. security information, workflow state, etc.). On retrieve some of these information are filtered out. This policy may completely be changed depending on specific needs (see modifiers below). Extensibility ------------- CMFEditions was from the beginning developed with extensibility in mind. A handful of tools provide the whole functionality: - repository layer: This is the public main API. The repository layer cares about recursive storing and retrieving of content items from/to Zope 2's Object File System (OFS). - archivist layer: It knows *how to clone* content items. The archivist "is Mr. Pickle". - modifiers: They're invoked by the archivist and know *what to clone*. This the main customization point. A modifier knows about what information on an object is a reference and if the referenced object has to be versioned also. - storage: Is responsible of storing content items versions in a history. The current storage implementation is a ZODB storage (it uses Zope Version Control Product from ZC). Other storages may be written (svn, file based, xml based, etc.). The storage API is quite simple and the storage implementation doesn't have to care about reference stuff as this is already done by the upper layers. - purge policy: The purge policy is called on every save operations and has full control over the version to save and the whole history. The current implementation may be configured to only hold the n current versions by purging the older versions from the repository. This functionality is by default disabled. It may be disabled through the ZMI. You should take care when you're saving objects with a lot of interrelations. Purging functionality is quite new! Additional Documentation ------------------------ A couple of presentations and ReSt documents may be found in documentation package that has to be downloaded separately (or the doc folder of CMFEditions). The CMFEditions team also started adding documentation in the download area <http://plone.org/products/cmfeditions/documentation> of plone.org. You're welcome to help out.
RPMPackage Products.CMFDynamicViewFTI-4.0.5-1.lbn13.noarch
CMFDynamicViewFTI is a product for dynamic views in CMF
RPMPackage Products.CMFDiffTool-2.1-1.lbn13.noarch
Diff tool for Plone
RPMPackage Products.CMFDefault-2.2.4-1.lbn13.noarch
This product declares basic content objects and provides default implementation of some of the framework services for the Zope Content Management Framework (CMF).
RPMPackage Products.CMFCore-2.2.7-2.lbn13.noarch
This product declares the key framework services for the Zope Content Management Framework (CMF).
RPMPackage Products.CMFCalendar-2.2.3-1.lbn13.noarch
The CMFCalendar product is an example of creating a CMF Product. The CMFCalendar product is also expected to be a generally useful *out of the box* and skinnable to accomodate customization within your existing CMF instance. To see how to go about building a CMF product, this hopefully allows a developer to follow through the process of registering their product, skins, and help with the CMF by example. It shows how an object is created and registered with the types_tool, necessary skins added to the skins_tool, with the Calendar skins directory added to the skin paths, and providing portal_metadatool with an Element policy for the content_type of the object. For installing set the *active site configuration* of your site's setup tool to the CMFCalendar profile and import all steps. After installing the CMFCalendar you should notice a calendar appear in your CMF. This is fully customisable to your portals needs.
RPMPackage Products.CMFActionIcons-2.1.3-3.lbn13.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.
RPMPackage Products.BlueAwstatsManagementTool-2.0-3.lbn13.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.
RPMPackage Products.BlueAwstats-2.0-9.lbn13.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.
RPMPackage Products.BeakerSessionDataManager-1.0b1-2.lbn13.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.
RPMPackage Products.BastionLedger-4.6.0-6.lbn13.noarch
General Ledger, Order Management, Debtor and Creditor Management, Shareholder Management, Asset Register, Forecasting, ...
RPMPackage Products.BastionCrypto-4.2.0-1.lbn13.noarch
BastionCrypto, Zope-ZMI PGP/X509 cryptographic suite
RPMPackage Products.BastionBase-ldap-4.3.2-2.lbn13.noarch
Role management into LDAP/PAS
RPMPackage Products.BastionBase-4.3.2-2.lbn13.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) and tools for Plone (timezone tool)
RPMPackage Products.BastionBanking-VeriSign-doc-4.2.2-2.lbn13.noarch
VeriSign PayFlow API documentation
RPMPackage Products.BastionBanking-VeriSign-4.2.2-2.lbn13.noarch
VeriSign PayFlow API
RPMPackage Products.BastionBanking-PinPayments-4.2.2-2.lbn13.noarch
pin.net.au merchant gateway
RPMPackage Products.BastionBanking-PayPalDirect-4.2.2-2.lbn13.noarch
PayPal Name-Value-Pair Direct Payment (no hijacking/rerouting to PayPal)
RPMPackage Products.BastionBanking-PayPal-4.2.2-2.lbn13.noarch
PayPal Internet Merchant Service
RPMPackage Products.BastionBanking-ManualPayment-4.2.2-2.lbn13.noarch
Manual preparation from schedule