- Steve McNiven
Twitter announced long ago it was switching it’s API to prevent 3rd part apps and abuse (limiting the daily hits from a site).
You could see this coming if you opened the console tab in your debug window on any Sitefinity site.
In the last couple days, this is what we see now:
(apologies for the sizing you can inspect your own sites though.
So teleriks response was initially “we’ll get right on it” and they did, next release we had another widget…buuuut…The widget might as well be called “Google Analytics” or “Poll Daddy”…the designer is just a giant empty textbox that just doesn’t render it’s contents in design mode. You can throw anything in there and it’ll render (not in design mode).
By comparison, these guys did took some time on user experience. They are rightfully promoting it in this forum thread too. @telerik, this is what we want…options, a comprehensive designer. However I think they callback serverside…if I’m right that could be problematic, I don’t want a serverside external dependancy.
There’s so much it could have been…like twitter has a request limit on api calls, who needs to hit them every time the page refreshes. There could have been a sf json cache implementation where the json results for multiple services are cached locally for a period of time, or something like that. At a bare minimum at least give the user a link to know where to get the code from in the designer.
So here’s a preview of what the twitter widget (on twitters end not sitefinity) generates.
So not a simple styleable ul\li of tweets we’re used to, but an external script to generate a whole UI in an iframe. (Inline iframe scrollbar #ghetto, thanks twitter).
@Telerik, lets sit down and talk, pull up a seat…The thing is, you guys are the experts, clearly better coders than we are…you should be doing things we cannot do and “deliver more than expected”. In this case the delivery was less than expected because it’s less than what we have.
If you can’t budget the time to do it right, just tell us it’s “on the way” and we will wait for a proper implementation (begrudgingly, or vocally, not gonna lie). Just let us know you’re working on it for a hotfix or next release. Because right now we’re feeling the heat on this from end users.
This is all resolved in Sitefinity 6.1 SP1. Not just fixed, but implemented BETTER than the original widget. It uses publishing pipes, so in theory we shouldn’t ever hit the twitter api cap because the content is coming from sitefinity, polled at an interval on twitter/
They yanked it again lol, I made a better one, you can go see it here