This is a pre-production deployment of Warehouse, however changes made here WILL affect the production instance of PyPI.
Help us improve Python packaging - Donate today!
Project Description
========================
collective.twitter.tweet
========================

.. contents:: Table of Contents

Overview
--------

This product provides a twitter action to be used with content rules.

Prerequisites
-------------

This product depends on `collective.twitter.accounts`_.

Usage
-----

Just add this product to your buildout, and you should get the action to be used in the content rules.
Optionaly, you can specify a separate URL to be used as the beginning of the link.

Example
-------

- Go to the content rules, and add the "Tweet new content's title and url".
- Select the account you want to use, or just choose "First valid account"
- If you have a separate site for your public site, you can specify it in the "separate host" field.
example: your public site is http://my-site.com/ and your editing one is
http://another-host:8080/Plone and you want tweets to use the public host, specify it here.


.. _`collective.twitter.accounts`: http://pypi.python.org/pypi/collective.twitter.accounts

Installation
------------

To enable this product in a buildout-based installation:

1. Edit your buildout.cfg and add ``collective.twitter.tweet`` to the list
of eggs to install ::

[buildout]
...
eggs =
collective.twitter.tweet

After updating the configuration you need to run ''bin/buildout'', which will
take care of updating your system.

Go to the 'Site Setup' page in a Plone site and click on the 'Add-ons' link.

Check the box next to ''collective.twitter.tweet'' and click the
'Activate' button.

Note: You may have to empty your browser cache and save your resource
registries in order to see the effects of the product installation.


Contributors
------------

* Franco Pellegrini (frapell@ravvit.net)

Development sponsored by Open Multimedia.

Changelog
---------

1.0 (unreleased)
^^^^^^^^^^^^^^^^

- Initial release.
Release History

Release History

1.0

This version

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

1.0b3

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

1.0b2

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

1.0b1

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

Supported By

WebFaction WebFaction Technical Writing Elastic Elastic Search Pingdom Pingdom Monitoring Dyn Dyn DNS Sentry Sentry Error Logging CloudAMQP CloudAMQP RabbitMQ Heroku Heroku PaaS Kabu Creative Kabu Creative UX & Design Fastly Fastly CDN DigiCert DigiCert EV Certificate Rackspace Rackspace Cloud Servers DreamHost DreamHost Log Hosting