Pay with a tweet implements tweet payment feature. This allows the website to
make downloads available to users with a tweet as payment.
Pay with a tweet provides a token and unlimited blocks to show the downloads.
Requeriments
- oAuth Module
- Create a twitter application in https://dev.twitter.com/
- In the Pay with a tweet configuration page you can fin the Callback URL value for your twitter application
- In your twitter application you have to set the Access level to Read and write
- You must paste the Consumer key and Consumer secret of your twitter application in the Pay with a Tweet configuration page
Benefits
Your visitors will get content without having to pay money and the website
benefit from this viral marketing system based on the social network Twitter
Blocks
You can configure that each button has a block.
You can configure the number of extra blocks you can use. In each extra block
can indicate which button to use. So you can have the same download in
different blocks areas.
Token
Pay with a Tweet has a token [pay_with_a_tweet:pid:?]. This way you can add
buttons anywhere on your website. For inclusion in text areas without token
support you must to allow the use of PHP Filter and include the token follows:
<?php print(token_replace('[pay_with_a_tweet:pid:?]')); ?>
Note: You must replace "?" for the pay_with_a_tweet entity pid
Credits
The original module is writen by Rolando Caldas Sanchez http://rolandocaldas.com
(rolando.caldas[at]gmail [doc]com) and use one third-party classes:
- OAuth class (https://drupal.org/project/oauth)
Current maintainers:
Rolando Caldas Sánchez - http://rolandocaldas.com
Extensions
Commerce pay with a tweet
"Commerce Pay with a tweet implements commerce payment module to provide
pay with tweet payment on checkout process (payment option list)."
The "Commerce pay with a tweet" module is written by Florian LE BRENN - http://florianlebrenn.fr
Module Page: https://drupal.org/project/commerce_pay_with_a_tweet
Project information
- Created by rolando.caldas on , updated
Stable releases for this project are covered by the security advisory policy.
There are currently no supported stable releases.


