Press Ctrl / CMD + C to copy this to your clipboard.
This post will be reported to the moderators as potential spam to be looked at
Ok, this is confusing me. The basic problem is tweets not displaying, as others have found. I have taken the XSLT and Umbraco.Library out of it altogether and written a little tool (using the guts of the Umbraco GetXmlDocumentByUrl method) but I'm still getting System.Net.WebException: The remote server returned an error: (400) Bad Request errors. I am calling the Twitter API from an .aspx page. The tool works here from my development environment but not from my server (EUKHost). What was at the root of other people's problems?
Hello ManWood.If it works locally and not on your server I recommend, remote desktoping into the server and checking if you can load up the twitter XML API URL in a browser on the server, to see if it can actually connect to the URL.
Let me know how that goes first and then we can try and take it from there.
I can't remote into the server unfortunately and my host are being awkward, claiming it's all third party and not their issue. I have had a cryptic message back from Twitter - they are suggesting using oAuth. I will update when I've had a chance to implement it. I've also written a little code for caching results which you might want to include in your package.
Hello Manwood.The feed that we are using does not require oAuth unless your tweets are protected?It is a shame you cannot RDP into the server, have you got another server you can test it with. As the server you are using might have some firewall on it, that prevents it to connecting to the XML URLhttp://api.twitter.com/1/statuses/user_timeline.xml?screen_name=warrenbuckley&include_rts=1&count=200
Also have yout tried with other twitter user accounts to see if there is any problem there.
Re caching I know I have forgotton to use caching using the umbraco.library:GetXmlDocumentByUrl call but if you have a better solution for me to update this call I would be happy to know.
I have the same problem. It throws the error at random. When the error occurs, the twitter URL is still accessable from Firefox.
I had this problem too once and it had to do with the request limit twitter sets. I believe it's 150 request an hour.
Maybe this link can help :
Just figured that out. What would be the best way to cache this?
I think caching the macro is the easiest.
Testing now with cach at 60 seconds. I think that should do it. Thanks for for helping out. :-)
Chris - how do you 'cache a macro'?
I wrote a little mod to cache results in ASP.NET, I will post the code when I get a chance (I need to revisit this in the next few days)..
You set the cache properties on the macro in the Macros section under Developer.
is working on a reply...
Write your reply to:
Image will be uploaded when post is submitted