Search results

plone.registry-1.1.2-1.lbn25.noarch

This package provides debconf-like (or about:config-like) settings registries for Zope applications. A ``registry``, with a dict-like API, is used to get and set values stored in ``records``. Each record contains the actual value, as well as a ``field`` that describes the record in more detail. At a minimum, the field contains information about the type of value allowed, as well as a short title describing the record's purpose. See the following doctests for more details: * ``registry.rst``, which demonstrates how registries and records work * ``events.rst``, which shows the events that are fired from the registry * ``field.rst``, which describes the behaviour of persistent fields

plone.registry-1.1.2-1.lbn25.noarch

This package provides debconf-like (or about:config-like) settings registries for Zope applications. A ``registry``, with a dict-like API, is used to get and set values stored in ``records``. Each record contains the actual value, as well as a ``field`` that describes the record in more detail. At a minimum, the field contains information about the type of value allowed, as well as a short title describing the record's purpose. See the following doctests for more details: * ``registry.rst``, which demonstrates how registries and records work * ``events.rst``, which shows the events that are fired from the registry * ``field.rst``, which describes the behaviour of persistent fields

plone.relations-2.0-1.lbn19.noarch

Tools for defining and querying complex relationships between objects. This product builds on and requires zc.relationship and also five.intid.

plone.relations-2.0-1.lbn25.noarch

Tools for defining and querying complex relationships between objects. This product builds on and requires zc.relationship and also five.intid.

plone.releaser-1.5.3-1.lbn19.noarch

Plone release management utilities

plone.releaser-1.5.3-1.lbn25.py37.noarch

Plone release management utilities

plone.reload-2.0-2.lbn13.noarch

While being logged into the ZMI as an user with the Manager role visit /@@reload on your Zope application root via a browser. If your Zope is configured to listen on port 8080 on localhost this is: http://localhost:8080/@@reload If you get a Resource not found error, make sure you have loaded the configure.zcml file from this library and you really use the ZODB application root and not a Plone site as the base url. When you press the Reload Code button, all modules that have been changed since the last time they were loaded are reloaded. You'll get a status message telling you which modules have been reloaded. To reload all ZCML without a restart, press the 'Reload Code and ZCML' button. The action to perform is determined via a simple query string, so once you did a 'Reload Code' once, you can simply reload the browser page to execute the action once again. Caveats: There's some code structures which cannot be reloaded via the approach underlying this library. Plone portlets and content types are two examples of this. In general decorators will currently not always work.

plone.reload-3.0.1-1.lbn19.noarch

While being logged into the ZMI as an user with the Manager role visit /@@reload on your Zope application root via a browser. If your Zope is configured to listen on port 8080 on localhost this is: http://localhost:8080/@@reload If you get a Resource not found error, make sure you have loaded the configure.zcml file from this library and you really use the ZODB application root and not a Plone site as the base url. When you press the Reload Code button, all modules that have been changed since the last time they were loaded are reloaded. You'll get a status message telling you which modules have been reloaded. To reload all ZCML without a restart, press the 'Reload Code and ZCML' button. The action to perform is determined via a simple query string, so once you did a 'Reload Code' once, you can simply reload the browser page to execute the action once again. Caveats: There's some code structures which cannot be reloaded via the approach underlying this library. Plone portlets and content types are two examples of this. In general decorators will currently not always work.

plone.reload-3.0.1-1.lbn25.noarch

While being logged into the ZMI as an user with the Manager role visit /@@reload on your Zope application root via a browser. If your Zope is configured to listen on port 8080 on localhost this is: http://localhost:8080/@@reload If you get a Resource not found error, make sure you have loaded the configure.zcml file from this library and you really use the ZODB application root and not a Plone site as the base url. When you press the Reload Code button, all modules that have been changed since the last time they were loaded are reloaded. You'll get a status message telling you which modules have been reloaded. To reload all ZCML without a restart, press the 'Reload Code and ZCML' button. The action to perform is determined via a simple query string, so once you did a 'Reload Code' once, you can simply reload the browser page to execute the action once again. Caveats: There's some code structures which cannot be reloaded via the approach underlying this library. Plone portlets and content types are two examples of this. In general decorators will currently not always work.

plone.resource-1.0.2-1.lbn13.noarch

plone.resource publishes directories of static files via the ZPublisher. These directories may be located either in the ZODB (as OFS folders and files), or on the filesystem. Each resource directory has a type and a name. When combined, these are used to traverse to the resource directory. For example: /++theme++mytheme/<subpath> /++sitelayout++mylayout/<subpath> /++templatelayout++mylayout<subpath>