I'm having an issue where the macro is running VERY slowly. If I don't cache the macro, it takes about a minute, sometimes longer to load up the feed. Even with caching the feed, it measn that whe the cache expires the next user gets a big delay in page load. Has anyone else come accross this issue? Running on 4.5.2.
Hiya Tim, I am not entirely sure why this would be the case. Have you done the usual querstring debug to see the output and the time of stuff that is running.
Yup, it looks like the part that's running slow is when it it hits: "After performing transformation". Depending on the twitter account I try and get stuff from, it can take anything from 5 to 60+ seconds. It might be something to do with the transformation maybe? I've also noticed that it's slower when you ask for 1 status than it is for say 5, which is odd.
I've had a further play, and if I turn off everything in the template, bar just the getting of the XML, it still runs quite slowly, so I think it might be a latency problem between the server and the twitter server.......
Experienced this aswell, only the page where the Twitterfeed was on was loading very slow, workaround -> SetTwitter Cache to for example 3600 in the options and it works alot better!
Only problem for me is that the first time the Twitter loads it doesnt show.. have to refresh the page..
Hiya all, I will try and push out a change later this afternoon evening to help with speed as the twitter API has been vastly improved since I last wrote an update for this package.
The problem is that it fetches 200 tweets even if you only want to display one tweet, which was causing long loads. This was needed at the time in order to decide if the tweet was a reply or not. As if we only fetched one tweet and the most recent 50 or so tweets were all @replies then the most recent tweet would have not been displayed.
However twitter has improved the REST API for fetching tweets and we can pass in a parameter to decide if want to fetch tweets that are replies. This is a relatively simple fix and I should have it pushed out this evening.
Hiya All, I have pushed out a new package with the new change in to fix this problem and merged in some of the work of the clever Lee Kelleher was doing to enhance the package further.
So you will need to uninstall the package and re-install (a macro param changed on twitter status and the XSLT exenstion library has been refactored & renamed) so best just to do a re-install to be safe.
Macro Very Slow?
I'm having an issue where the macro is running VERY slowly. If I don't cache the macro, it takes about a minute, sometimes longer to load up the feed. Even with caching the feed, it measn that whe the cache expires the next user gets a big delay in page load. Has anyone else come accross this issue? Running on 4.5.2.
Hiya Tim,
I am not entirely sure why this would be the case. Have you done the usual querstring debug to see the output and the time of stuff that is running.
Warren
Yup, it looks like the part that's running slow is when it it hits: "After performing transformation". Depending on the twitter account I try and get stuff from, it can take anything from 5 to 60+ seconds. It might be something to do with the transformation maybe? I've also noticed that it's slower when you ask for 1 status than it is for say 5, which is odd.
I've had a further play, and if I turn off everything in the template, bar just the getting of the XML, it still runs quite slowly, so I think it might be a latency problem between the server and the twitter server.......
Experienced this aswell, only the page where the Twitterfeed was on was loading very slow, workaround -> SetTwitter Cache to for example 3600 in the options and it works alot better!
Only problem for me is that the first time the Twitter loads it doesnt show.. have to refresh the page..
Hiya all,
I will try and push out a change later this afternoon evening to help with speed as the twitter API has been vastly improved since I last wrote an update for this package.
The problem is that it fetches 200 tweets even if you only want to display one tweet, which was causing long loads. This was needed at the time in order to decide if the tweet was a reply or not. As if we only fetched one tweet and the most recent 50 or so tweets were all @replies then the most recent tweet would have not been displayed.
However twitter has improved the REST API for fetching tweets and we can pass in a parameter to decide if want to fetch tweets that are replies.
This is a relatively simple fix and I should have it pushed out this evening.
Thanks,
Warren
Nice Warren! Hope you can fix it :) We're using this plugin on a few sites, and its nice! With caching on that is ;)
Greets
Hiya All,
I have pushed out a new package with the new change in to fix this problem and merged in some of the work of the clever Lee Kelleher was doing to enhance the package further.
So you will need to uninstall the package and re-install (a macro param changed on twitter status and the XSLT exenstion library has been refactored & renamed) so best just to do a re-install to be safe.
Hope this fixes alot of problems for you all
Cheers,
Warren
For some odd reason I can't highfive your posts, but this thing works like a charm! Nice that you could do this!
If I could vote, i'd vote.. ;)
is working on a reply...