Search results

collective.lineage-1.1.1-1.lbn25.noarch

Lineage is a Plone product that allows subfolders of a Plone site to appear as autonomous Plone sites to the everyday user. This hub and spoke structure allows site administrators to easily manage multiple, seemingly independent, sub-entity websites in one Plone. Furthermore, the "parent" site can access and view the content in all the "child" sites while the child sites only view their own content. The parent site can also syndicate chosen content to the selected child sites. Lineage is less complex and easier to manage than a cluster of nested Plone sites but gives users all the same benefits. Lineage can be used within a large organization to manage multiple microsites, such as school district sites, university departments, corporate product sites, public library satellites, professional association events, and more.

collective.local.addgroup-1.2.2-1.lbn25.noarch

Allows to create a group and assign roles directly from the sharing tab for Plone 4. Tested on Plone 4.1. Content types have just to implement IAddNewGroup to have the functionnality. Also provides a dexterity behaviour. If you want to enable it for Folder, you only have to add to your buildout.cfg:: [instance] zcml = ... collective.local.addgroup If you don't want the functionality for Folder, but on your own content type, add to the configure.zcml of your policy module:: <include package="collective.local.addgroup" file="minimal.zcml" /> <class class="my.package.content.MyContent.MyContent"> <implements interface="collective.local.addgroup.interfaces.IAddNewGroup" /> </class> If you just want this for a dexterity content type, you just have to activate the behaviour. The user need to LOCALLY have the "Add Groups" permission to add a new group and "Manage users" to add and remove users from the listed groups. Add group to local list ----------------------- The site manager can add groups from sharing table to locally managed groups list. So then the user with local permissions can manage the group himself. We don't give this feature to local managers to avoid privilege escalation.

collective.local.adduser-1.5-1.lbn25.noarch

Allows to create a user and assign roles directly from the sharing tab for Plone >= 4.1. This can work with Plone 4.0.9 with plone.app.users > 1.0.6, < 1.1.x. Content types have just to implement IAddNewUser to have the functionnality. If you want to enable it for Folder, you only have to add to your buildout.cfg:: [instance] eggs = ... collective.local.adduser zcml = ... collective.local.adduser If you don't want the functionnality for Folder, but on your own content type, add to the configure.zcml of your policy module:: <include package="collective.local.adduser" file="minimal.zcml" /> <class class="my.package.content.MyContent.MyContent"> <implements interface="collective.local.adduser.interfaces.IAddNewUser" /> </class> If you don't want the roles field, you can include minimal_wo_roles.zcml instead of minimal.zcml.

collective.local.sendto-1.6.1-1.lbn25.noarch

Provides a "Mailing" tab on selected content types. It provides a 'send email' form where you can select recipients from the list of members having a local role on the content. Content types have just to implement ISendToAvailable, or, if they are dexterity type, to enable the behavior "Send mail tab". In your policy product : - Add 'collective.local.sendto' to the 'install_requires' parameter of setup.py - Add to the configure.zcml:: <include package="collective.local.sendto" /> <class class="my.package.content.MyContent.MyContent"> <implements interface="collective.local.sendto.interfaces.ISendToAvailable" /> </class> Roles whose you can select users as recipients are set by a site property : sendToRecipientRoles.

collective.local.sentmail-1.2-1.lbn25.noarch

This module creates a "Sent mails" folder in your portal root. Each time a IMailSentEvent is launched, it creates a SentMail item in this folder with the event's attributes (subject, b ody and recipients). Sent mails are visible only by their owner (the mail's sender) and editable by nobody. A IMailSentEvent implementation example can be found in collective.local.sendto package.

collective.local.userlisting-1.3-1.lbn25.noarch

Provides a "Members" tab on selected content types. The view a the list of members having a role on the content, sorted by role. Content types have just to implement IUserListingAvailable. Add to the configure.zcml on your policy product:: <include package="collective.local.userlisting" /> <class class="my.package.content.MyContent.MyContent"> <implements interface="collective.local.userlisting.interfaces.IUserListingAvailable" /> </class> You can also check the interface in "Interfaces" tab of content in ZMI. In dexterity, you can select the behaviour.

collective.local.workspace-1.0rc2-1.lbn25.noarch

This content type bundles all collective.local.* packages. It adds a workspace dexterity content type where the new WorkspaceManager user role can manage a groupware : - inviting new users (to the workspace only) - from collective.local.adduser - creating groups - from collective.local.adduser - from collective.local.addgroup Workspace container have a "Members" tab to show all group members - from collective.local.userlisting -, and an "Emailing" tab to send emails to workspace members - from collective.local.sendto. A layer IWorkspaceLayer is set on request when you are in a workspace. A `get_workspace` method in api module gives you the workspace root of any content. String interpolators give you the title and the url of the workspace in an email rule action.

collective.localrolesdatatables-1.0.1-1.lbn25.noarch

Once the addon is installed you have a controlpanel that provide a direct access to @@localrolesdatatables_catalog_view view where you can see every localroles of every content types. Because it use jquery datatbles you can search and filter per content / users / content type. This view use the portal_catalog, and build a query using the context path. So if you want to have a report with only a folder (for an extranet) you just have to call the view on this folder: mysite/extranet/@@localrolesdatatables_catalog_view

collective.mass_subscriptions-0.1.0-1.lbn25.noarch

With this product you can import in your Plone site a full set of users, providing a CSV file with all required and optional data. If your user's fieldset is customized you can also provide non-standards ones. The only required column is username. The password data, if not provided, will be generated randomly. If you have powers to manage groups, you can also add all new users to one or more groups available. Finally you can send a notification message to those users, customizing the message text (for example: to give to users the account's email address).

collective.mediaelementjs-0.4.2-1.lbn25.noarch

An integration of the MediaElementJS audio and video player for Plone. Large portions of this package have been blatantly copied from the collective.flowplayer product by Martin Aspeli. What it does Once installed, supported media files uploaded to the Plone site will automatically use a view that renders them with the MediaElementJS player. MediaElementJS uses <video> and <audio> tags on modern browsers. If the browser doesn't support HTML5 media element tags, or can not render the media natively, a Flash players that mimics the MediaElement API is used. See the MediaElementJS browser and device support chart for details. The recognized formats at the moment are: Audio MP3, Ogg, MPEG-4, WAV, Windows Media Audio, WebM Video MPEG-4, Ogg, WebM, Flash Video, Windows Media Video, MPEG and QuickTime (.mov and .qt)