GOF and Bacall, on 16 September 2011 - 04:06 AM, said:
t4e, on 16 September 2011 - 03:49 AM, said:
Don_J, on 15 September 2011 - 08:58 PM, said:
t4e, on 15 September 2011 - 08:16 PM, said:
for those that the logs are not showing must be an issue at your end...
Don't think so. Everything has been fine for me until about five minutes ago. In fact, I have had a cache with a couple thousand of logs on it, open in it's own tab and have occasionally gone to it over the last few hours and paged down. New logs were loaded almost instantly, until five minutes ago. Now, just the "loading" message and the spinning circle. This now true for every cache I look at.
Nothing has changed here. Working one moment, not the next.
i've been on it since the update was finished and i tried caches with hundreds of logs as well as shorter ones, not once did i get a blank page with no logs and except for the very first one that i tried just after the update was finished the page loads instantly on scroll, i don't even see the "loading" icon...so i still think its something local to those that have issues
GOF and Bacall, on 16 September 2011 - 03:36 AM, said:
t4e, on 15 September 2011 - 08:16 PM, said:
for those that the logs are not showing must be an issue at your end...
Lets see. They made changes to there product. I made no changes to my computer. Yup, must be my fault.
neither have i and works like a charm, both at work and at home...how can that be explained?
although i am a full time FF user i did try other browsers like IE and Opera and still no issues
I don't explain it. It is not in my field of expertise. I can only tell you that it worked until they mucked around with things.
This is in my area of expertise and, strange as it may sound, it could well be that neither is broken.
Since it is working for some and not for others, this tells me that their good is (generally) OK and since you didn't change anything, your configuration is (generally) OK. What isn't OK is how their new code works with your configuration and/or network. Something about what they are now doing is either messing with your network or your system, for whatever reason, is having trouble handling it. Without knowing more of what they are doing "under the covers" it's darn difficult to recommend things to check for compatibility. Hopefully G-Speak is looking at those possibilities as well as inspecting code, but stuff like that can be a tough booger to track down.
Unfortunately this is a big problem with websites that want to use all kinds of whiz-bang technologies and techniques. Not everyone is properly configured to use them or folks prefer to keep their configuration and security settings set at a level which makes sites anywhere from annoying to unusable.
Not saying this is the situation in all, or any, cases with this logs issue, just trying to help some folks understand just one of the possibilities.