FANDOM


Forums > Senate Hall archive > Multiple Reloads = Irritation


Particularly on heavy image entries, the page is reloading multiple times as each image is loaded by my browser. It's annoying as all heck. I use Firefox. It was the Obi-Wan Kenobi entry that really frayed my nerves with this behavior.Unsigned comment by Rebelgrrl (talk • contribs).

  • Yes, this has been happening ever since we upgraded to MediaWiki 1.10. It's driving me nuts too. Can someone please tell us why this is going on and when it will be fixed? -- Ozzel 22:28, 11 June 2007 (UTC)
    • No idea what you are talking about. I too use the latest version of Firefox and the Obi-Wan Kenobi article opens just fine. - JMAS 22:49, 11 June 2007 (UTC)
  • I get the same thing, whenever I read the "Palpatine" artice. 69.116.177.57 22:57, 11 June 2007 (UTC)
  • I got it on R2-D2 and to a lesser extent on a couple of less image-saturated articles as well. Haven't had the problem at home, but it was terrible at work, and I was using the latest Firefox in both places. Wildyoda 23:52, 11 June 2007 (UTC)
  • Same here (Firefox 2.0.0.4, WinXP). No problems with R2-D2, but it seems to have trouble rendering articles like Palpatine or Wookieepedia:Quote of the Day (In-Universe), the page vanishes/reappears several times while the cpu load rises to 95%(!). Doesn't happen on any other website. --Craven 00:39, 12 June 2007 (UTC)
  • Funny thing is, I'm having no problems with any articles. I use the latest version of Firefox, with Win xp at home, and an older version of Firefox on Win2000 at work, and I'm having no problems either way. This is a bizarre problem. - JMAS 23:06, 12 June 2007 (UTC)
    • Now you've all gone and jinxed me. :P Just did it to me on the Obi-Wan Kenobi article. - JMAS 00:26, 13 June 2007 (UTC)
  • Wow... that's pretty annoying. Here's what I've seen:
    • Safari: works fine
    • IE7 on XP: works fine
    • FF 2.0.0.4 on Mac: hung my browser
    • FF 2.0.0.4 on XP: reload problem
I'll have Emil and the gang look at this... but it might more of a Brion/Tim problem (over at Wikimedia). I'll spread this around and see what we can find. Johnq 05:32, 13 June 2007 (UTC)
  • We've brought wookieepedia back to 1.9.3 and the problem doesn't seem to appear. We're investigating. Johnq 23:02, 13 June 2007 (UTC)
    • Much appreciated. - JMAS 23:23, 13 June 2007 (UTC)
  • Still happening, and not on overly image-heavy articles either. Just did it to me on the Battle of Endor article. - JMAS 12:39, 15 June 2007 (UTC)
  • Firefox V1, Windows XP, I had it happen to me earlier when the wikis were slow, but now nothing. I checked the Obi-Wan Kenobi article and it loaded fine. No blank paging effect. EDIT: Battle of Endor blanked out once on me just now. -- Riffsyphon1024 13:25, 15 June 2007 (UTC)
  • Just had it happen to me on Obi-Wan. Too scared to try it elsewhere. Using XP and Firefox. Gonk (Gonk!) 16:54, 15 June 2007 (UTC)
    • FYI, I'm currently (at work) using Win2000 with Firefox 1.5.0.3 - JMAS 17:02, 15 June 2007 (UTC)
  • Just a head's up...it's happening with the Catalogue of unnamed vehicles as well. I'm using Vista with Firefox 2.0.0.4. Greyman(Paratus) 15:46, 18 June 2007 (UTC)
  • Ok... I'm having the guys look into this again. Johnq 20:40, 18 June 2007 (UTC)

How's it looking everyone? For me, the flashing has stopped (thanks Eloy and the tech team :) The whole site seems a lot faster too. Anyone still seeing problems? -- Sannse 18:39, 19 June 2007 (UTC)

  • Looks good. All pages are loading as usual, without multiple reloads for me. Thanks very much for fixing it! --Craven 01:29, 20 June 2007 (UTC)
  • No problems for me. - JMAS 01:42, 20 June 2007 (UTC)
    • Yep, looks back to normal. Thanks for fixing it! -- Ozzel 05:44, 21 June 2007 (UTC)
  • Everything checks now. -- Riffsyphon1024 05:46, 21 June 2007 (UTC)

Ad blocker interference detected!


Wikia is a free-to-use site that makes money from advertising. We have a modified experience for viewers using ad blockers

Wikia is not accessible if you’ve made further modifications. Remove the custom ad blocker rule(s) and the page will load as expected.