![]() |
It seems to work again for me too :)
|
Thanks folks. Fixed here too.
|
Many thanks to baliktad for a clear, detailed analysis of the problem and possible remedies.
|
So far, working for me. THanks!
|
Due to this problem, I had significantly decreased my activity on FT and discovered many new things in life :) but thanks for finally fixing it anyway.
I am a bit disappointed, however, that I originally reported the problem on April 15th (and I was not the first person) and it seemed that there was no attempt from IB until 2-3 weeks ago to really understand the problem. Three months is too long for such an issue to be resolved. |
First, let me say how happy we are to have resolved this issue at last, and how thankful we are to have had help from so many FTers in getting this done, from those who reported it, to those who provided their specific technical details, and those tech-minded FTers who contributed directly to tracking down the problem and leading to a plan of action.
But let me address the time frame as well. There are three parts to resolving tech issues like this. One is member(s) reporting a problem. Then there's me "triaging" the issue. Then there's tech addressing it if it appears to be a site issue. In most cases, there needs to be some sort of critical mass reached before tech gets involved; otherwise we are in the position of troubleshooting a hundred thousand users' computers for them, to see where the issue lies -- and clearly we can't do that. This particular issue looked for all the world like a browser settings issue, and with conflicting reports there was no way to tell what exactly was happening early on. Read through the thread. Also, it was initially affecting a small group of users -- another sign that it was likely not a site issue. So we treated it as a browser issue and as you can see, at no point was the issue ignored; if it was a browser or settings issue, there's only so much we can say to resolve it from our end. But if you read the thread, you'll see that Dick, Kim and I frequently addressed this as it progressed from looking like an isolated browser issue to a clear-cut site problem affecting many users. This was a particularly vexing issue and it took some time to resolve for many reasons, but not because we did not want to resolve it, not because anyone was ignored, or because there was foot-dragging. While of course we'd have preferred to get it done the day it was reported, things take time, and resources, and testing, and detailed behavior reports and some educated guessing to get resolved. We're just happy it was. Thank you again, all, for your patience and contributions. Paul O'Brien Community Manager |
This issue has been resolved for me for a few days, but now it's back... However, it's on just one thread that I can find so far. Below is the culprit thread URL:
http://www.flyertalk.com/forum/ameri...ng-airbus.html It keeps taking me to post 205, despite the fact that I (and many, many other AA forum regulars) have been following this thread very closely. I have verified that the new message URL is the following: http://www.flyertalk.com/forum/ameri...new-post1.html I'm not an expert in such things like others here, but the symptoms for this thread seem the same to me as those that were before, so I'm posting here rather than starting a new thread. I've not changed my system setup at all in the intervening time, same version of Firefox and everything. Any suggestions are welcome. |
Originally Posted by Microwave
(Post 16770967)
This issue has been resolved for me for a few days, but now it's back... However, it's On just one thread that I can find so far. Below is the culprit thread URL:
http://www.flyertalk.com/forum/ameri...ng-airbus.html It keeps taking me to post 205, despite the fact that I (and many, many other AA forum regulars) have been following this post very closely. I have verified that the new message URL is the following: http://www.flyertalk.com/forum/ameri...new-post1.html I'm not an expert in such things like others here, but the symptoms for this thread seem the same to me as those that were before, so I'm posting here rather than starting a new thread. I've not changed my system setup at all in the intervening time, same version of Firefox and everything. Any suggestions are welcome. |
Same situation, yet another thread: Ideas for stopover LEX - PHL
|
I also experienced the same problem, confined to one thread, for about 2 days:
http://www.flyertalk.com/forum/milea...0-usd-all.html However, the problem eventually resolved itself. So far, all other threads are functioning fine. |
Originally Posted by Microwave
(Post 16770967)
I've not changed my system setup at all in the intervening time, same version of Firefox and everything. Any suggestions are welcome.
Code:
// ==UserScript== |
Happening on a couple of other threads now too. Not all, oddly enough. Extraordinarily aggravating.
|
It is happening to me as well on a couple of select yet apparently random threads.
|
I thought I saw this problem once, and I think it happened when using the old style link, so it is a different problem.
Hint for IB tech: it was immediately after I had merged two threads, suggesting the merge resulted in an incorrect database entry. |
Everything seems to still be working for me, but I did have something strange happen earlier. I clicked on this thread, and this one opened opened up.
Apparently this was one one of the first threads on FT in 1998, and was closed five years ago. :confused: |
| All times are GMT -6. The time now is 9:07 am. |
This site is owned, operated, and maintained by MH Sub I, LLC dba Internet Brands. Copyright © 2026 MH Sub I, LLC dba Internet Brands. All rights reserved. Designated trademarks are the property of their respective owners.