Search results

collective.blueprint.usersandgroups-0.2.0-1.lbn19.noarch

transmogrifier blueprints for importing users and groups into plone

collective.categories-1.0-1.lbn19.noarch

Introduction Categories are not tags. Categories allowed for a broad grouping of post topics. They can be hierarchical but you should not have that much categories. This addon add a field categories to all content types based on archetypes and in the portal_catalog to be able to do search based on categories. Features You can add categories to your content. Pluggable backend. This addon by default use the same storage and widget as the tags keyword. But you can install and configure extra storage / widget. Configure the backend using the registry configlet or in a profile as follow: <record name="collective.categories.backend"> <value>archetypes.linguakeywordwidget</value> <!-- or Products.ATVocabularyManager--> </record> Products.ATVocabularyManager Using Products.ATVocabularyManager, you can add tree vocabularies for your categories. You have in this case to create a 'collective.categories' vocabulary in the configlet of the vocabulary manager And if you add Products.LinguaPlone to ATVocabularyManager you can also make your vocabulary multilingual ! archetypes.linguakeyword This backend add support to multilingual categories but use default Plone LinesField for storage. If you use this backend you should check the skin directories order because they both override the script collectKeyword.py. 'linguakeywordwidget' skin directory should be before the 'collective_categories' one.

collective.chimpfeed-2.0-1.lbn19.noarch

This add-on provides a number of integration points between MailChimp and Plone: Assign interest groups to existing content and automatically expose the result sets as RSS-feeds. Sign up form in both portlet- and view format, complete with an optional selection of interest groups. Create newsletter campaigns from existing content using the dashboard, with conditional interest group merge tags. Moderation built-in. Quick start: Define a set of interest groups for one or more lists, configure Plone with your API key and start tagging content.

collective.clipboardupload-1.0-1.lbn19.noarch

Quintagroup has developed a collective.clipboardupload tool that essentially allows you to copy images and past them directly into TinyMCE visual editor.

collective.contentleadimage-1.3.4-1.lbn19.noarch

This products adds complete support for adding descriptive image to any Archetypes based content in Plone site. Each object has new tab "Edit lead image", which allows to upload new or remove current image. It is similar behaviour as Plone News Item (you can add image to news item and this image is displayed in news item overview listing. There is folder_leadimage_view page template, which can be used to list all items in the folder together with images attached. There is configuration control panel, where you can set maximum width and height of the uploaded images. The width and height is applied on each image upload (image is automatically resized). You can specify smaller width and height which is used as image preview in the below content title viewlet (next to content Description). Large image is used in the above content body viewlet (floated left at the top of content body). Below content title viewlet is preffered, but Manager can easily switch the viewlets on/off in the control panel. There is FieldIndex and metadata in portal_catalog: hasContentLeadImage (True/False). This may help developers to create own templates optimized for displaying lead image.

collective.contentlicensing-2.2.6-3.lbn25.noarch

This tool is used to manage copyright licenses within plone. It allows for both a site wide copyright license to be set by default, and the ablility to set licenses on individual objects. It supports a number of licenses including all rights reserved, GFDL, and Creative Commons (with an integrated license picker). You can also enter and select licenses not supported by default, or configure new licenses that will appear in the selection widget for your Plone instance.

collective.contentrules.mailtogroup-1.5-1.lbn19.noarch

s action rule allows you to send e-mail to groups and users. The groups and users are defined in the action rule, it's possible to combine both. This action was made because the current actions cannot mail to a dynamic set of users (group). Adding multiple members was also added because you don't always know the e-mail of a certain user.

collective.contentrules.mailtolocalrole-1.3-1.lbn19.noarch

Using content rules in Plone 3 it's very easy to register for certain events and perform actions upon occurrence. One of these actions provided by Plone 3 is a mail action. A limitation in the supplied mail action is that one can only provide fixed email addresses. But sometimes you'd like to send an email to a user having a certain role on the object that was involved in triggering the content rule. An examplary use case and reason for creation of this package is the reviewer role. If an object in a certain location of the site is submitted for publication, you would like to inform the user that has the 'reviewer' role on this area of the site that a new document/object is available for review. Before contentrules was available in Plone 3 the place to add this functionality was to to create a python script and attach it to the workflow 'submit' transition that was used for the objects. .. Note:: This product is superceded by `collective.contentrules.mailtorole`, which can send mail to all members having a role on the object, including global roles.

collective.contentrules.mailtorole-1.7-1.lbn19.noarch

Using content rules (available since Plone 3) it's very easy to register for certain events and perform actions upon occurrence. One of these actions provided by Plone is a mail action. A limitation in the supplied mail action is that one can only provide fixed email addresses. But sometimes you'd like to send an email to a user having a certain role on the object that was involved in triggering the content rule. An examplary use case and reason for creation of this package is the reviewer role. If an object in a certain location of the site is submitted for publication, you would like to inform the user that has the 'reviewer' role on this area of the site that a new document/object is available for review. Before contentrules was available in Plone the place to add this functionality was to to create a python script and attach it to the workflow 'submit' transition that was used for the objects.

collective.contextimage-1.3.1-1.lbn19.noarch

Provide extension fields for context specific images and markup. This elements can be used as layout elements. If the current context does not provide the specific context related field, it is aquired from its parents. It is useful i.e. if you like to have a different logo or header background on different sections of your site, if you want to set a background image for your content, if you want to place an image in context somehwere in the page using a viewlet. Separate schema extenders are provided with corresponsing renderers bound to browserlayers loaded by different profiles. This way its possible to enable only one of the several features: Viewlet context image An image which gets rendered by a viewlet as img tag. Profile is profile-collective.contextimage:viewlet. Header context image An image which gets rendered as portal header background. Profile is profile-collective.contextimage:header. Page context image An image which gets rendered as page background. Profile is profile-collective.contextimage:page. Logo context image An image which gets rendered as portal logo. This is a drop in replacement for the logo viewlet with fallback to default logo). Profile is profile-collective.contextimage:logo. Footer Viewlet Richtext which can be displayed as portal footer. Profile is profile-collective.contextimage:footer.