Downloaded Twitter Timeline for a 1.6 install, but the zipped version refers to itself as 1.3.2. use_stale_cache seem to work but not create_links, which I would really like to use. When I add the create_links parameter, I get no output. Any ideas?
This is an archived forum and the content is probably no longer relevant, but is provided here for posterity.
The active forums are here.
March 02, 2011 2:23pm
Subscribe [3]#1 / Mar 02, 2011 2:23pm
Downloaded Twitter Timeline for a 1.6 install, but the zipped version refers to itself as 1.3.2. use_stale_cache seem to work but not create_links, which I would really like to use. When I add the create_links parameter, I get no output. Any ideas?
#2 / Mar 02, 2011 5:13pm
Yes, I am afraid 1.3.2 is the current version for EE 1. The EE2 compatible version is 1.4.2.
#3 / Mar 02, 2011 7:19pm
Well, this fills me with sadness, but thanks for the reply.
#4 / Mar 03, 2011 4:14am
Michael,
More are available at devot-ee
#5 / Mar 03, 2011 8:59am
John - I didn’t see another add-on for 1.6 that displays tweets; most of them seem to be for publishing tweets from EE. It looks like Twit-ee would fit the bill, but comments indicate that it stopped working when Twitter changed the authorization procedure, and the developer is no longer maintaining it.
#6 / Mar 03, 2011 3:43pm
Sorry we have no better news :(
#7 / Mar 21, 2011 8:13pm
Michael,
I just downloaded the current version and did a very basic test run – it’s converting links properly on my 1.7 install. This is the test I used:
{exp:twitter_timeline screen_name="ellislab" limit="5" twitter_refresh="20" use_stale_cache="yes" create_links="user_mentions|hashtags|urls"}
{text}
{/exp:twitter_timeline}Good luck!
#8 / Mar 22, 2011 1:07pm
Thanks for the follow-up on this David! Michael, why not give it a try and see if it does what you need?
Let us know if you have any other questions.
#9 / Mar 22, 2011 2:02pm
The current version is what I tried, and it didn’t work in my 1.6.2 install. I’m using the Twitter widget for now, and the client is happy with that.
#10 / Mar 22, 2011 2:04pm
Hrm. 1.6.2 is a few years old and there have been many bug fixes - and more importantly - security updates since then. I’d strongly recommend you update to 1.7.
In any case, you have a solution that is working for you?
#11 / Mar 22, 2011 2:10pm
Oops - thinking of another client (who is not ready for the change - the next upgrade will be to 2.x, but that’s another story). This client is on 1.6.8, but an upgrade is on the schedule. Anyway, yes, the solution is working. Thanks for the help.
#12 / Mar 23, 2011 8:01am
Good stuff Michael. Feel free to start anew thread if you have any more questions.