Manage and automate social publishing on Plone sites
Project description
Introduction
Provides a viewlet (and under-the-hood machinery) for managers that allows to publish contents to social networks (only twitter ATM). Social publication can be automated by enabling it per-content.
To enable the viewlet just mark the content-type you want with collective.socialpublisher.interfaces.IPublishable. You can do it from ZMI or trough ZMCL:
<class class="Products.ATContentTypes.content.event.ATEvent"> <implements interface="collectinve.socialpublisher.interfaces.IPublishable" /> </class> NOTE: this is already done by the package in this alpha stage.
Twitter accounts management is done by collective.twitter.accounts.
You can provide a publisher by registeriing an utility providing collective.socialpublisher.interfaces.ISocialPublisherUtility. See collective.socialpublisher.utility for details.
To enable auto-publishing you have to enable it per-content (waiting for global configuration) and you have to create a cron the calls @@social-auto-publish. You can do it using Products.cron4plone or trough buildout like this:
[instance] ... zope-conf-additional = <clock-server> method /plonesite/@@social-auto-publish period 1000 user admin password admin </clock-server>
See also http://collective-docs.readthedocs.org/en/latest/misc/asyncronoustasks.html.
Tested on
Plone 4.2rc1
Credits
This product was developed by Domsense.
Changelog
1.0a2
[fix] old twitter import
[imp] ‘update’ button for saving settings without publishing
[imp] ‘one-shot-text’ a flag for changing the text only for the current publishing without overwriting the stored one
[imp] if cron4plone is present display any available cron schedule
[imp] improved styles a bit
1.0a1
Initial release
Project details
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.