Closed (fixed)
Project:
Twitter Block
Version:
7.x-1.x-dev
Component:
Code
Priority:
Critical
Category:
Task
Assigned:
Reporter:
Created:
4 Mar 2013 at 16:09 UTC
Updated:
25 Jul 2013 at 02:17 UTC
Jump to comment: Most recent file
Twitter is turning off v1 of the API, so this module is going to stop working. Twitter Pull implemented a solution around using the Twitter module for oAuth and API access (http://drupal.org/node/1781024). Not sure if we want to go that route. Thoughts?
| Comment | File | Size | Author |
|---|---|---|---|
| #6 | migrate-to-embedded-timelines-1933164-6.patch | 27.33 KB | devin carlson |
Comments
Comment #1
ZenDoodles commentedUgh... Thanks twitter.
Looking into https://dev.twitter.com/docs/embedded-timelines now
Comment #2
cweagansDid you see this? http://www.systemseed.com/blog/twitter-timeline-module
Comment #3
jebuske commentedDamn, you gotta be kidding me. This was by far the easiest solution and we finally themed it a few weeks ago :(
Comment #4
cweagansYeah, I agree. Sadly, Twitter has a recent track record of making everything about 10000x more difficult than it really needs to be :/
Comment #5
friendlymachine commentedHey guys,
Have you made any decisions on the future of the module? I love the simplicity it provides, I hope there is a way to keep it going.
John
Comment #6
devin carlson commentedA patch to drop the current approach and add support for the Embedded Timelines API linked to in #1. Since the Twitter module can handle generating blocks using the APIs that require OAuth, I think it makes most sense for Twitter Block to move to Embedded Timelines (to avoid duplication).
If everyone is +1 on moving to Embedded Timelines, I'd recommend releasing a 2.x branch of Twitter Block to highlight the significant changes brought by the API change and to deal with the upgrade path (removing the old 1.x data).
While the patch is fully functional, a number of UX improvements could be made. @ZenDoodles, I'd appreciate the ability to roll new releases of the module if you are willing. :)
Comment #7
ZenDoodles commentedI agree. v 2.x is a good plan, and I thought you already *could* administer releases. You've got it now. Thanks for all your work on the module @Devin Carlson
Comment #8
matthewandrews commentedUpdating deathdate for API v1 as per https://dev.twitter.com/blog/api-v1-retirement-final-dates
... and yes, +1 from me for a 2.x release using the embedded timeline approach. Any idea when that might roll out?
Comment #9
devin carlson commentedI've pushed a 7.x-2.x branch which includes the patch from #6, so I'm marking this as fixed.
@ZenDoodles thanks for the added permission(s)!
I'll close out the currently open issues that no longer apply and try to get a stable 2.x release out ASAP.
Comment #11
muschpusch commentedThis needs to be backported to D6. Or did you stopped supporting it at all? The embedded timeline stuff doesn't seem to have the possibility to theme it? Right?
Comment #12
devin carlson commentedI have no plans to backport the current 7.x2.x branch of Twitter Block to Drupal 6. I've started working on a port of Twitter Block to Drupal 8 and don't have any need for a D6 release. That said, I wouldn't be against creating a D6 release if someone created one or sponsored one.
The embedded timelines have a number of visual configuration options but, unfortunately, aren't themeable as they work via JavaScript. If need a lot of theming done then I'd suggest going with the Twitter module.
If you have any additional questions please file them as a new support request.
Comment #13
alan d. commentedThree out of the three clients of ours that used this all required the theming side of things. A bit of a regression imho, but also a "won't fix" I guess unless the twitter api changes and allows more settings :(
Edit: #2049845: Theming gives one solution to the theming issues :)
It is an github script that adds an css to the iframe dom and you can style to your hearts content