Search results

Products.PloneHelpCenter-4.0-2.lbn25.noarch

Plone Help Center is an application designed to aid the documentation of Plone, and is used on plone.org to categorize and keep documentation up to date. It should be usable for documenting other open source products (such as Plone Product add-ons) or even for other documentation projects.

Products.PloneSVNaccess-0.4.3.3-_rc_1.3.3.lbn25.8.noarch

Plone SVN access provides subversion access (read&write) for plone.

Products.PloneSoftwareCenter-1.6.4-4.lbn25.noarch

Formerly ArchPackage, PloneSoftwareCenter is a tool that keeps track of software projects, software releases, and other related information; it was originally written to power the download area of plone.org.

Products.PloneSoftwareCenter-devel-1.6.4-4.lbn25.noarch

The PloneSoftwareCenter testing harness should only be used and deployed by power users.

Products.PloneboardSubscription-0.5-3.lbn25.noarch

Products.PloneboardSubscription enables users to subscribe/unsubscribe to email notification to a Ploneboard forum or a particular conversation, and has an option to automatically add as subscriber a member adding a comment to a conversation. A "Subscribe/Unsubscribe" link is provided on the forum or conversation and if the user chooses to subscribe, any further comments made to the forum or conversation triggers an email. Configuration ============= The product creates a tool "portal_pbnotification" at the Plone site which contains some parameters that can be set: * debug mode : if checked, mail is not sent but only logged ! * send interval : in seconds. The email contains modifications done during the last send interval. * last sent : int time of the last send verification (not to be manually changed...) * html mail format : must be checked if the email template contains html. * mail template : the mail template can be plain text or html. The following special parts will be replaced: * [PORTAL_TITLE] : by the portal title * [URLS] : by the modified conversation urls * [FORUMS] : by the modified conversation urls and the corresponding forum (only in html format) * [COMMENTS] : by the modified conversation urls, the corresponding forum and the new comments (only in html format) * auto_subscribe : if checked, each member adding a comment will be added in the conversation subscribers list.

Products.PluggableAuthService-1.11.3-1.lbn25.noarch

This product defines a fully-pluggable user folder, intended for use in all Zope sites.

Products.PluginRegistry-1.4.1-1.lbn25.noarch

Products.PluginRegistry offers a simple persistent registry which allows the site manager to registe components for specific interfaces, and to order them.

Products.PortalTransforms-2.1.12-1.lbn25.noarch

This Zope product provides two new tools for the CMF in order to make MIME types based transformations on the portal contents, and so an easy to way to plugin some new transformations for previously unsupported content types. The provided tools are : portal_transform (the transform tool) handle transformation of data from a mime type to another A bunch of ready to use transformations are also provided. Look at the documentation for more information. Notice this package can also be used as a standalone Python package. If you've downloaded the Python distribution, you can't make it a Zope product since Zope files have been removed from this distribution. This product is an off-spring of the Archetypes project.

Products.PythonField-1.1.3-1.lbn25.noarch

Archetypes field for Python input

Products.PythonScripts-4.0.1-1.lbn25.noarch

The Python Scripts product provides support for restricted execution of Python scripts, exposing them as callable objects within the Zope environment. Providing access to extra modules Python script objects have a limited number of “safe” modules available to them by default. In the course of working with Zope, you will probably wish to make other modules available to script objects. The Utility.py module in the PythonScripts products provides a simple way to make modules available for use by script objects on a site-wide basis. Before making a module available to Python scripts, you should carefully consider the potential for abuse or misuse of the module, since all users with permission to create and edit Python scripts will be able to use any functions and classes defined in the module. In some cases, you may want to create a custom module that just imports a subset of names from another module and make that custom module available to reduce the risk of abuse. The easiest way to make modules available to Python scripts on your site is to create a new directory in your Products directory containing an __init__.py file. At Zope startup time, this “product” will be imported, and any module assertions you make in the __init__.py will take effect. Here’s how to do it: In your Products directory (either in lib/python of your Zope installation or in the root of your Zope install, depending on your deployment model), create a new directory with a name like “GlobalModules”. In the new directory, create a file named __init__.py. Edit the __init__.py file, and add calls to the ‘allow_module’ function (located in the Products.PythonScripts.Utility module), passing the names of modules to be enabled for use by scripts. For example: from Products.PythonScripts.Utility import allow_module allow_module('base64') allow_module('re') allow_module('DateTime.DateTime') This example adds the modules ‘base64’, ‘re’ and the ‘DateTime’ module in the ‘DateTime’ package for use by Python scripts. Note that for packages (dotted names), each module in the package path will become available to script objects. Restart your Zope server. After restarting, the modules you enabled in your custom product will be available to Python scripts. Placing security assertions within the package/module you are trying to import will not work unless that package/module is located in your Products directory. This is because that package/module would have to be imported for its included security assertions to take effect, but to do that would require importing a module without any security declarations, which defeats the point of the restricted Python environment. Products work differently as they are imported at Zope startup. By placing a package/module in your Products directory, you are asserting, among other things, that it is safe for Zope to check that package/module for security assertions. As a result, please be careful when place packages or modules that are not Zope Products in the Products directory.