Admin Forum:My wiki returns blank pages constantly in Safari 4.1.3, but in no other browsers

This Forum has been archived

Visit the new Forums!

Forums: Admin Central Index → Technical Help → My wiki returns blank pages constantly in Safari 4.1.3, but in no other browsers

Wikia's forums are a place for the community to help other members.
To contact staff directly or to report bugs, please use Special:Contact.

Okay, I'm being driven slowly mad by a problem of what I think is likely my own doing. At c:tardis, using Safari (for Mac) 4.1.3, I'm constantly getting blank or half-blank pages. The behavior only happens at tardis, so I'm sure it's something I've added to the Wikia or Common.css, or possibly something funky about the .js. In any event, it's highly specific error, and I'm the only one who is apparently having the problem.

The problem is not entirely consistent, but these things seem to provoke it on a regular enough basis:

• Virtually any instance of using a section-specific URL results in a total blank of the page. This is highly annoying because most of the time when you edit, you edit a section. So when you hit "publish" you get a URL that is appended with #Section_Name. The net result is that I have to keep reloading the page just to see my latest edit. That's become so frustrating, I've largely abandoned Wikia when using Safari, and have returned to editing in MonoBook, unless I really need to see a Wikia-skin feature.
• When I go to a page initially, it's usually fine. But if I hit reload, I go through the page blanking thing again.
• If I push "page down" while the page is reloading, I can usually break the cycle and get a "good" load.
• Likewise, if I can start entering text in the search bar, I can usually prevent the page from blanking.
• It's definitely something about my customisations. I experience the problems nowhere else on Wikia — even at c:tardistest, our "coding test wiki", which contains some, but not all of the .js and .css coding.

I've tried comparing the css between c:tardis and c:tardistest, but to no particular avail. I think my eyes just aren't seeing something very basic which doesn't bother Firefox, but which makes Safari trip out.

If anyone has ever heard of something like this, I'd appreciate any help you can give. czechout ☎ ✍  fly tardis  04:36:25 Mon 29 Aug 2011 

Oh, I should point out that I get a fairly consistent message in Safari's Console when a blank is returned:

oasis: DOM ready after 2289 ms
images1.wikia.nocookie.net/__am/41319/group//oasis_shared_js:25tracker: /1_wikia/user/view
images1.wikia.nocookie.net/__am/41319/group//oasis_shared_js:25tracker: /1_wikia/tardis/user/view
images1.wikia.nocookie.net/__am/41319/group//oasis_shared_js:25tracker: /1_wikia/loggedin/user/view
images1.wikia.nocookie.net/__am/41319/group//oasis_shared_js:25ImageLightbox: init
images1.wikia.nocookie.net/__am/41319/group//oasis_shared_js:25AchievementsModule: init
images1.wikia.nocookie.net/__am/41319/group//oasis_shared_js:25oasis: window onload after 2674 ms
images1.wikia.nocookie.net/__am/41319/group//oasis_shared_js:25FB: onFBloaded
2connect.facebook.net/en_US/all.js:3The "fb-root" div has not been created.
images1.wikia.nocookie.net/__am/41319/group//oasis_shared_js:25FB: onFBloaded
images1.wikia.nocookie.net/__am/41319/group//oasis_shared_js:25getScript: eval() fallback applied for http://connect.facebook.net/en_US/all.js

The item of particular notw here is "The "fb-root" div has not been created." and the lines beneath it. Those don't appear upon a successful load of a page, but it seems weird that something facebook related would trip up the entire page. czechout ☎ ✍  fly tardis  05:06:45 Mon 29 Aug 2011 

I'm also sometimes getting this:

oasis: DOM ready after 2702 ms
images1.wikia.nocookie.net/__am/41319/group//oasis_shared_js:25tracker: /1_wikia/user/view
images1.wikia.nocookie.net/__am/41319/group//oasis_shared_js:25tracker: /1_wikia/tardis/user/view
images1.wikia.nocookie.net/__am/41319/group//oasis_shared_js:25tracker: /1_wikia/loggedin/user/view
images1.wikia.nocookie.net/__am/41319/group//oasis_shared_js:25ImageLightbox: init
images1.wikia.nocookie.net/__am/41319/group//oasis_shared_js:25oasis: window onload after 3319 ms
images1.wikia.nocookie.net/__am/41319/group//oasis_shared_js:25FB: onFBloaded
2connect.facebook.net/en_US/all.js:3The "fb-root" div has not been created.
images1.wikia.nocookie.net/__am/41319/group//oasis_shared_js:25FB: onFBloaded
images1.wikia.nocookie.net/__am/41319/group//oasis_shared_js:25getScript: eval() fallback applied for http://connect.facebook.net/en_US/all.js
images1.wikia.nocookie.net/tardis/images/6/64/Favicon.icoFailed to load resource: the server responded with a status of 404 (OK)

czechout ☎ ✍  fly tardis  06:40:12 Mon 29 Aug 2011 

CzechOut, this really needs to be reported through Special:Contact in the future. I am filing a bug ticket to get this investigated now. --daNASCAT (help forum | blog) 17:28, August 30, 2011 (UTC)

Sorry, I thought that because it was something almost certainly of my doing, that Support might've just responded with "we don't support customised CSS", or something similar. Thanks for putting it forward to the appropriate people. czechout ☎ ✍  fly tardis  22:13:48 Tue 30 Aug 2011 

No need to apologize. We can't support Custom CSS, but when you start seeing JS hanging in your console, we're definitely interested, no matter the cause. Especially since it seems to be a module on our end. --daNASCAT (help forum | blog) 00:03, August 31, 2011 (UTC)

Yes, that definitely looks like something from svn-wikia-code.com. TK999 08:14, August 31, 2011 (UTC)

So is there anything I can do about? I mean, it only happens at w:c:tardis, and only in Safari. So something I've done somewhere is triggering a bug in svn. Any thoughts as to what precisely is irritating this oyster, so that I can temporarily turn it turn it off? czechout ☎ ✍  fly tardis  13:43:38 Tue 06 Sep 2011 

Is there a reason you're using such an old version of Safari? w:c:tardis works fine on Safari 5.1. -- Fandyllic (talk · contr) 7 Sep 2011 9:58 PM Pacific

A very good reason. I don't have an Intel Mac. Which means I can't run the Safari 5.1-minimum of OS X 10.6.8. And I can't afford to change to one, because it would mean buying thousands of dollars of software in addition to the new machine. All my versions of Adobe-branded software, just for a start, are PPC only. It's a common quandry for Mac users who were early adopters of OS X. czechout ☎ ✍  fly tardis  11:22:36 Thu 08 Sep 2011 

Also I would say the browser version is irrelevant as staff has already amdmitted it's a bug in their code (and I would say the same too). (: –Tm_T ^(Talk) 12:02, September 8, 2011 (UTC)