It would be real useful to be able to have more than one Tweet button on certain content type. For content types that usually ends up being several screen sizes long I would like to have the default at the top, but then a second after the content. My gut tells me that most users wont scroll back to the top just to tweet, but if there is a button right where they finish reading the likelihood is much higher they will use it.

Preferable it should be possible to use different button styles, such as vertical at the top and horizontal at the bottom.

When #884830: Manage using Fields UI? is implemented my guess is this should not be difficult to implement as well.


chia’s picture

In the lastest D7 dev version this can be done without any effort. Just enable the button on "Node links" on the admin/config/services/tweetbutton/node, it will show as vertical at top(if configured) and horizontal at bottom.

Yes, I have created the branch 7--2 and tweetbutton will be a field, you can add it to any entity and have by default view support for the field. I will commit the code to that branch this week.

tsvenson’s picture

Brilliant @chia, looking forward to test this as soon as the new dev version pops up on the project page.

chia’s picture

Status: Active » Fixed

marking this issue as fixed, the 7.x-1.x and 7.x-2.x can both have more than 1 tweetbutton for a node,

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.