Search results

plone.app.themingplugins-1.0-1.lbn19.noarch

plone.app.theming supports plugins that allow theme authors to bundle more advanced functionality with their themes. This package contains two such plugins: The ability to override specific Zope Page Templates when a theme is enabled The ability to register views providing custom markup using Zope Page Templates when a theme is enabled Both of these only work for themes distributed on the filesystem (either in a Python package or in the global themes resource directory), i.e. not for themes imported through-the-web in ZIP archives. That said, the features provided by these plugins are more likely to be useful in building “customer” sites (where filesystem development is likely to be the norma) than in distributing generic themes (where the through-the-web ZIP import is more attractive).

plone.app.tiles-3.1.1-1.lbn25.noarch

Plone UI integration for plone.tiles. This package contains the following things: A view @@add-tile, and an associated form, which can be used to create a new tile based on the tile's schema. For transient tiles, this merely redirects to a URL with an appropriate query string. For persistent tiles, it will also save the necessary data. This will fire an IObjectCreatedEvent as well as an IObjectAddedEvent for the newly created tile (a transient object) when successfully submitted. In the case of the IObjectAddedEvent, the newParent attribute will be the tile's context, and the newName attribute will be the tile's id. The @@add-tile view, when accessed directly, allows the user to choose from all available tiles (subject to the tile's add permission) and redirects to the appropriate @@add-tile/<tile-type> URL to configure the tile. A view @@edit-tile, and an associated form, which can be used to edit a tile based on the tile's schema. This will fire an IObjectModifiedEvent for the modified tile (a transient object) when successfully submitted. A view @@delete-tile, where the user may select a tile type, enter a tile id, and opt to clear out any persistent data for that tile. This can also be called by AJAX code given appropriate request parameters. This will fire an IObjectRemovedEvent for the removed tile (a transient object). The oldParent attribute will be the tile's context, and the oldName attribute will be the tile's id. The default add and edit forms should suffice for most use cases. You can use plone.autoform to configure alternative widgets, either by hand or via plone.directives.form. If you need a custom form, you can register an add view as an adapter from (context, request, tileType), where tileType is an instance providing plone.tiles.interfaces.ITileType. The actual integration of the various views is left up to other packages (such as the Deco editor).

plone.app.toolbar-1.4.0-1.lbn19.noarch

plone.app.toolbar installs a new content editing toolbar for Plone.

plone.app.transmogrifier-1.4-1.lbn19.noarch

This package contains several blueprints for collective.transmogrifier pipelines, commonly used to import content into a Plone site.

plone.app.upgrade-2.0.0-1.lbn25.noarch

This package contains the upgrade machinery to upgrade a Plone site to a newer version.

plone.app.users-2.1.0-5.lbn25.noarch

This package provide the registration form for new users using z3c.form forms. It allows the site administrator to select fields from a schema to appear on the registration form.

plone.app.uuid-1.1.3-1.lbn25.noarch

Plone integration for the basic plone.uuid package

plone.app.versioningbehavior-1.2.10-1.lbn25.noarch

The IVersionable behavior is used for enabling the CMFEditions functionality for dexterity contents. It adds a changeNote-field to the edit- and add-forms and creates a new version when the content is edited, if enabled for the content type. It's based on Products.CMFEditions. For listing the versions of an object use CMFEdtions' view versions_history_form or the history viewlet (see default @@view).

plone.app.viewletmanager-2.0.12-1.lbn25.noarch

This component expects you to register storage.ViewletSettingsStorage as a local utility providing IViewletSettingsStorage (CMFPlone does this). The viewlet manager in manager.OrderedViewletManager can then get the filter and order settings. These settings can be configured by 3rd party products and TTW to customize the viewlets per skin.

plone.app.vocabularies-2.1.25-1.lbn25.noarch

Overview ======== A collection of generally useful vocabularies for usage in zope.formlib. Common Named Vocabularies plone.app.vocabularies.AvailableContentLanguages plone.app.vocabularies.SupportedContentLanguages plone.app.vocabularies.Roles plone.app.vocabularies.Groups plone.app.vocabularies.AllowedContentTypes plone.app.vocabularies.AllowableContentTypes plone.app.vocabularies.PortalTypes plone.app.vocabularies.ReallyUserFriendlyTypes plone.app.vocabularies.UserFriendlyTypes plone.app.vocabularies.Skins plone.app.vocabularies.Workflows plone.app.vocabularies.WorkflowStates plone.app.vocabularies.WorkflowTransitions plone.app.vocabularies.AvailableEditors plone.app.vocabularies.Keywords plone.app.vocabularies.SyndicationFeedTypes plone.app.vocabularies.SyndicatableFeedItems plone.app.vocabularies.Users plone.app.vocabularies.Catalog Date/Time Related Vocabularies plone.app.vocabularies.Timezones all timezones provided by pytz plone.app.vocabularies.CommonTimezones common timezones provided by pytz. This are those a user would choose from and is not too much confused. plone.app.vocabularies.AvailableTimezones timezones configured in the portal. plone.app.vocabularies.Weekdays the seven weekdays in fullname. Value is the day number start counting at zero on monday. Title of the term is an i18n messagestring in plonelocales namespace, so it translates. plone.app.vocabularies.WeekdaysAbbr same as above but with 3 character abbreviations. plone.app.vocabularies.WeekdaysShort same as above but with 2 character abbreviations. plone.app.vocabularies.Month same as above but with month names starting with zero in january. plone.app.vocabularies.MonthAbbr same as above but with 3 character abbreviations.