CMS Twitter API
Has anyone run into issues using the CMS Twitter API. While
using the API are tweets are being displayed intermittently?
About 80% of the time we are getting the following message on our
site: "Loading tweets...".
Is this a known issue with the API?
When it does show up it works beautifully.
Cheers,
Matthew
Discussions are closed to public comments.
If you need help with Cascade CMS please
start a new discussion.
Keyboard shortcuts
Generic
? | Show this help |
---|---|
ESC | Blurs the current field |
Comment Form
r | Focus the comment reply box |
---|---|
^ + ↩ | Submit the comment |
You can use Command ⌘
instead of Control ^
on Mac
1 Posted by Ryan Griffith on 20 Sep, 2012 06:45 PM
Hi Matthew,
I'm curious if during times that you only see the Loading tweets... preloader message there is a connection issue with Twitter or if you have hit the API limit from your machine (I believe this goes by IP address).
When it does happen, try hitting the API directly with the following URL and see if your tweets load:
http://api.twitter.com/1/statuses/user_timeline.json?screen_name=uoit
Please let me know if you have any questions.
Thanks.
2 Posted by matthew.norton on 20 Sep, 2012 07:08 PM
Thanks Ryan, we actually discussed that possibility. Is there a way for us to set a limit on the API requests per hour? It will be difficult to not exceed 150 calls per hour.
I don't think we can manipulate the CMS API from our end?
Thanks.
3 Posted by matthew.norton on 20 Sep, 2012 07:10 PM
Or, is it possible to store API responses in the CMS application or on our site?
4 Posted by Ryan Griffith on 20 Sep, 2012 07:43 PM
Hi Matthew,
The API limit is actually enforced from Twitter's end, so unfortunately there isn't much that can be done in that respect. Since this is an AJAX request, the limit will count towards the client's IP address. If you are sitting on the page for a long time or doing quite a bit of development, you can definitely hit the limit; however, it should eventually reset itself.
There really isn't a way to customize the Twitter Feed Block since it is all self contained. If you are concerned about hitting the limit, you could try building your own tweet list by pulling in the timeline as an RSS Feed Block or XML Block and display it with a Format.
To get the timeline as RSS, you would use this URL
http://api.twitter.com/1/statuses/user_timeline.rss?screen_name=uoit
.To get the timeline as XML, you would use this URL
http://api.twitter.com/1/statuses/user_timeline.xml?screen_name=uoit
.Note the user_timeline.rss and user_timeline.xml.
You could then use Scheduled Publishing to keep the list updated on a schedule basis.
You could suggest adding more advanced options to the Twitter Feed Block by posting on our Idea Exchange. For example, being able to specify the length of time the Twitter Feed Block JavaScript refreshes itself.
Please let me know if you have any questions.
Thanks!
Ryan Griffith closed this discussion on 18 Oct, 2012 06:55 PM.