Search results

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.lbn19.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.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.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