BeTwittered updates are live.
February 23, 2008 – 7:37 amI got a bit of a lesson this morning. I updated BeTwittered, and was very pleased. Well, until I noticed that the formatting was junk. What did I learn? Stylesheets get cached, and pretty liberally. So if you were using BeTwittered this morning, and it suddenly looked a bit clunky, my apologies. One interesting thing, IE was better than Firefox in this case. It surprised me that IE picked up the changes when I closed it and re-opened. Firefox was VERY stubborn… So, here’s the “official” notice.
7 Responses to “BeTwittered updates are live.”
Holding Control and hitting F5 (or clicking refresh) will cause IE to refresh everything including CSS. ie7 is better and picking up changes then ie6 in these cases (but CTRL-F5 ALWAYS works).
(I think a similar key combination works on FF - not I’m too lazy to check).
By kdobey on Feb 25, 2008
Hi kdobey. Thanks much for the tip. I was only aware of using the shift key during for a refresh. I’ll have to check it out on Firefox, too.
By robert on Feb 25, 2008
I’m late to the party, but yep — ctrl-F5 is a forced reload for Firefox as well.
Say… would you consider adding a little js field length counter on the new tweet field? Sometimes my tweets get a bit long… it’d be nice to make sure I don’t go over!
By Chris on Mar 3, 2008
Hi Chris,
You know, I have the same issue! The field is limited to 140 characters, but it drives me nuts not to have the countdown. I’ll definitely put that in. Thanks for the input!
By robert on Mar 3, 2008
Robert:
I’ve been trying to add Betwittered to igoogle now for about a month. Every time I login in I receive a message that says “Oops something went wrong, undocumented error.” I’m using a Windows XP Pro PC and running FireFox 2.0. Any update on when this will be fixed?
Matt
By Matt on May 4, 2008
Hi Matt,
Wow, I missed this comment for a while! sorry about that. It seems that some people get that error, and I’m not sure why, at least not for all cases. It seems most often to be related to a school campus or work site firewall causing this. Sometimes this error is what you’ll see if Twitter is just REALLY slow, or down. But that would obviously go away. Are you able to test from other locations or computers? You might be able to verify that it’s related to a specific firewall (location), or a specific PC.
Thanks,
robert
By robert on May 29, 2008
Matt, what happens if you go directly to http://betwittered.com/twittergadget/gadget-v2.php ?
If this works, then it is likely you have configured your browser NOT to accept third-party cookies.
Change your browser settings to accept third-party cookies and the gadget should work on the iGoogle page.
Cheers,
Nathan
By Nathan on Jun 25, 2008