Is anyone else having trouble searching the MacRumors forums? For the last two days, I've consistently received the message:
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Search function down?
- Thread starter IJ Reilly
- Start date
- Sort by reaction score
IJ Reilly said:
i have even gotten that over at vbulletin.org i believe it has to do with vB 3.5 and Safari incompatibilities
I believe that... I've seen it occasionally at home (Safari) but never at work (Firefox/XP).eva01 said:
I can't seem to use either the simple or the advanced search function. Essentially, I seem to be getting a timeout. I'm sure they have worked since the board upgrade. This is recent -- last couple of days. Everything else is fine, on this board and elsewhere.
I'm the opposite of you-- my MR stuff works fine and dandy but I keep getting that same irritating time out error message all over the place! ARGH! It's driving me nuts. I do what Katie suggested; just reload the page over and over again, wasting lots of time waiting for a page to finally load.IJ Reilly said:
I know we're at vB 3.5.1 now... is that recent (i.e., did we start with vB 3.5)?IJ Reilly said:
I just tried it with my PowerBook -- same thing. Both are running 10.4.2.
Edit: Reset my router. Still the same. That's about all I know to do.
Edit: Reset my router. Still the same. That's about all I know to do.
Now that you mention it, I've seen that same Safari alert a couple of times over the last few weeks, and I don't recall seeing it before then. But yes, a reload fixed things just fine. No problems using the MR search now, and I don't think I've had any problems right along...
solvs said:
Doesn't work with Firefox either. I get a blank page instead of search results. Is this not strange?
I know you reset your router, but have you check the settings just to make sure it isn't blocking something? That is weird though. Maybe try the direct connection to see if that does it. Maybe something in 10.4.3 if you just d/l'ed the update. Weird.IJ Reilly said:
After a bit of additional research, I find that this problem is fairly widespread, though by no means common. It seems to be bug in Tiger that hits users with no discernible pattern. Many have reported the problem to Apple.
http://www.macfixitforums.com/php/showflat.php?Cat=&Board=Forum7&Number=721686
http://www.macosx.com/content/faq.php/q12519/Connection-Via-Airport.html
http://discussions.apple.com/thread.jspa?messageID=979381󯆵
Some have found that deleting the cookies for a given site fixes the problem, but only temporarily. Others have found that changing the Maximum Packet Size (MTU) in their network configuration cures it (this did not work for me).
My entire subnet appears to be affected, but so far at least, the only page that I've found to be dysfunctional is the MR search page. Others have experienced a much more serious impact. Apple is silent on the issue.
Further suggestions...?
http://www.macfixitforums.com/php/showflat.php?Cat=&Board=Forum7&Number=721686
http://www.macosx.com/content/faq.php/q12519/Connection-Via-Airport.html
http://discussions.apple.com/thread.jspa?messageID=979381󯆵
Some have found that deleting the cookies for a given site fixes the problem, but only temporarily. Others have found that changing the Maximum Packet Size (MTU) in their network configuration cures it (this did not work for me).
My entire subnet appears to be affected, but so far at least, the only page that I've found to be dysfunctional is the MR search page. Others have experienced a much more serious impact. Apple is silent on the issue.
Further suggestions...?
Have you tried any other browsers? Camino, OmniWeb... IE. Seems strange that it happens with FF too. Maybe a reinstall if it is a Tiger bug (I don't have a problem with it though). E-mail Apple and complain.
Seems strange that it happens with FF too. Maybe a reinstall if it is a Tiger bug (I don't have a problem with it though). E-mail Apple and complain.
I've only tried Safari and Firefox, but consistent with the experiences of many others who have encountered this problem, it is a not browser-specific bug nor does it appear to be an OSX corruption of any kind. In fact I'd guess the problem is generated by something completely outside of my network not playing well with Tiger, given that all of the Macs on my subnet behave the same way, even when the router is taken out of the picture. I'm going to try upgrading my PowerBook to 10.4.3 and see if that makes any difference.