Search results

collective.local.userlisting-1.3-1.lbn19.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.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.lbn19.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.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.lbn13.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.localrolesdatatables-1.0.1-1.lbn19.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.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.lbn19.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.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.lbn19.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)