I was told by ProximateXbox to put my question under the “Waypoint” section in the forums, so here it is (and I apologize if I am violating a rule about retyping the same forum somewhere else).
“I can’t access the file browser on my computer. After clicking on “File Browser” under Community, I get sent to a page that gives me a choice of pictures, films, rendered films, maps, etc. But that’s it. There’s nothing under it, and when I click on one of the buttons nothing happens. I’m sorry if I’m just tech-limited, but I would appreciate help.”
PrimateXbox also suggested I use a different browser, like switching from Google Chrome to IE.
Any additional information regarding this problem is appreciated.
You should be able to click on the images, buttons, etc. If you can’t, I would recommend that you clear your browser’s cache, close it down, and then try to load the page again. Hope that helps!
You’re using Chrome? I can’t reproduce any errors when I view the page in Chrome…
If clearing your cache doesn’t work, then try the following:
1. Go to the File Browser.
2. On your toolbar, click the wrench icon. Go to Tools -> JavaScript console.
3. A small panel will open at the bottom of the window, filled with a bunch of technical crap. Copy anything that’s written in red, and paste it into this thread.
If any errors are occurring on that page, those steps should reveal some technical information about them.
Sorry for the confusion, but Google Chrome is not my browser. That was just an example. The browser I’ve been using is Internet Explorer.
> Sorry for the confusion, but Google Chrome is not my browser. That was just an example. The browser I’ve been using is Internet Explorer.
Oh.
Well, have you tried clearing your cache yet, as Eagle suggested? :\
Clearing the cache worked. The rest of the file browser loaded. Thank you guys for the help.
[EDIT]
No, wait, it actually didn’t work…
When I deleted the cache it loads more of the page but not all of it and I still can’t access anything. I downloaded Google Chrome and tested that, but it did the same thing as my IE… Is there anything else I can do?
> When I deleted the cache it loads more of the page but not all of it and I still can’t access anything. I downloaded Google Chrome and tested that, but it did the same thing as my IE… Is there anything else I can do?
How much more of the page does it load?
It loaded the search options for the Screenshots, but I still couldn’t access anything. It had the loading circle thing, but it was doing that for so long I gave up on it. Tell me if you need more specific details.
> It loaded the search options for the Screenshots, but I still couldn’t access anything. It had the loading circle thing, but it was doing that for so long I gave up on it. Tell me if you need more specific details.
Hm…
If you’re using IE, can you try the following, please?
1. Go to the File Browser.
2. Hit F12 to open IE’s developer tools.
3. In the window or panel that appears, select the “Console” tab.
4. Refresh the File Browser page.
5. Look at the Console, and copy any error details (red text) into this thread.
If you’ve switched to Chrome, the instructions I posted earlier in the thread will work. Either way, I’m hoping that if the problem is some kind of code error, this will help to reveal it.
“SCRIPT5007: Unable to get value of the property ‘show’: object is null or undefined”
This is what was highlighted in red.
I am experiencing the same issue. Using Internet Explorer, when attempting to access my fileshare, I see the tabs for a second or two then a box covers the tabs so I cannot access them.
I followed the instructions above and am receiving these errors…
SCRIPT1028: Expected identifier, string or number
fileshareDetails.js?v=12222, line 10 character 5
SCRIPT5009: ‘JSON’ is undefined
fileshare.js?v=12222, line 524 character 5
Any help would be greatly appreciated!
Thanks for the details.
It looks like the problem is occurring because you’re using older versions of Internet Explorer.<mark>*</mark> (You could also be using a newer version that’s set to Compatibility Mode, which makes it act like an old version.) Older IE versions are very… temperamental… and there are a few things in the File Browser’s code that cause them to flip out.
There are things that the Waypoint web devs could do to accommodate a few older versions of IE, but seeing as most of 343i’s staff is working almost non-stop on Halo 4, I honestly don’t know how long it’d take them to get around to fixing these issues.
In the meantime, you could try updating your Internet Explorer to the newest available version, disabling Compatibility Mode if it’s on, and/or switching browsers. Note that the newest IE versions don’t work on Windows XP, so if that’s your operating system, switching browsers is your best option.
Free alternatives to Internet Explorer:
Google Chrome
Mozilla Firefox
Opera
Safari
<mark>*</mark> @Shevla: you said that Chrome also isn’t working. If you post the error details for that, I can look into it and see if there are any other problems that might be causing it. I don’t experience any issues in my copy of Chrome, though, so I can’t look into it on my own. :\
> Thanks for the details.
>
> It looks like the problem is occurring because you’re using older versions of Internet Explorer.<mark>*</mark> (You could also be using a newer version that’s set to Compatibility Mode, which makes it act like an old version.) Older IE versions are very… temperamental… and there are a few things in the File Browser’s code that cause them to flip out.
>
> \
Wow, I actually received a response, lol!
The issue WAS with compatibility view. I’m using Windows 7 with the latest Internet Explorer and it seems “compatibility view” was set to on. Toggled off and fileshare appeared as if by magic, lol.
I cannot thank you enough for the help DavidJCobb!! You da man!!
To Shevla Fett – You could try to toggle compatibility view off and it may fix your issue. Hope to see your issue resolved soon as well.
- Choot
17
Uncaught TypeError: Cannot call method ‘setFileDetailsClickHandlers’ of null fileshare.js:101
Uncaught TypeError: Cannot call method ‘each’ of null Core.js:101
844
Uncaught TypeError: Cannot call method ‘setFileDetailsClickHandlers’ of null fileshare.js:101
Uncaught TypeError: Cannot call method ‘hide’ of null header.js:97
209
Uncaught TypeError: Cannot call method ‘setFileDetailsClickHandlers’ of null fileshare.js:101
Uncaught TypeError: Cannot call method ‘setFileDetailsClickHandlers’ of null fileshare.js:101
2Uncaught TypeError: Cannot call method ‘eq’ of null Core.js:77
1470Uncaught TypeError: Cannot call method ‘setFileDetailsClickHandlers’ of null fileshare.js:101
Uncaught TypeError: Cannot call method ‘setFileDetailsClickHandlers’ of null fileshare.js:101
2
Uncaught TypeError: Cannot call method ‘eq’ of null Core.js:77
2352
Uncaught TypeError: Cannot call method ‘setFileDetailsClickHandlers’ of null fileshare.js:101
That was everything in red on Chrome. And how do you toggle off the compatibility view?
Unsure exactly for Chrome but using Internet Explorer, the toggle is found here, below the RED arrow…
compatibility view image
Hope this helps Shevla Fett!
Sorry for the double-post! Bad storm equals bad connection, lol!
> 17
> Uncaught TypeError: Cannot call method ‘setFileDetailsClickHandlers’ of null fileshare.js:101
> Uncaught TypeError: Cannot call method ‘each’ of null Core.js:101
> 844
> Uncaught TypeError: Cannot call method ‘setFileDetailsClickHandlers’ of null fileshare.js:101
> Uncaught TypeError: Cannot call method ‘hide’ of null header.js:97
> 209
> Uncaught TypeError: Cannot call method ‘setFileDetailsClickHandlers’ of null fileshare.js:101
> Uncaught TypeError: Cannot call method ‘setFileDetailsClickHandlers’ of null fileshare.js:101
> 2Uncaught TypeError: Cannot call method ‘eq’ of null Core.js:77
> 1470Uncaught TypeError: Cannot call method ‘setFileDetailsClickHandlers’ of null fileshare.js:101
> Uncaught TypeError: Cannot call method ‘setFileDetailsClickHandlers’ of null fileshare.js:101
> 2
> Uncaught TypeError: Cannot call method ‘eq’ of null Core.js:77
> 2352
> Uncaught TypeError: Cannot call method ‘setFileDetailsClickHandlers’ of null fileshare.js:101
>
> That was everything in red on Chrome. And how do you toggle off the compatibility view?
The errors you’ve listed for Chrome seem to be the result of your computer failing to load jQuery, a package of code that the File Browser relies on very heavily.
My first recommendation is to clear Chrome’s cache, and then see if any problems still occur when using it to view the File Browser.
If you still have problems after clearing Chrome’s cache, then I’d like to see if you can load the problematic code files directly, by themselves. All you’ll have to do is open the following links; if you see a ton of code, or if you’re prompted to download a file, then that means you should be able to access the code files (in which case I’d have no idea what’s wrong). If, on the other hand, you receive any error messages, then we can go from there.
jQuery, hosted on a Microsoft server.
jQuery, hosted on Halo Waypoint as a fallback.
jQuery UI, hosted on a Microsoft server.
Uncaught TypeError: Cannot call method ‘append’ of null jquery-1.5.1.min.js:16
Uncaught TypeError: Cannot call method ‘each’ of null Core.js:101
2
Uncaught TypeError: Cannot call method ‘eq’ of null Core.js:77
That was what was in red after clearing the cache on Chrome.
And I checked out each of the links for Chrome, but just saw a whole lot of codes on the pages.
> And I checked out each of the links for Chrome, but just saw a whole lot of codes on the pages.
Then we know that your copy of Chrome is downloading the site’s code files properly.
I did some Googling for the errors you’re seeing… Could you please try the following?
1. Open the JavaScript console.
2. Type in the following code, and hit “Enter”:
$ == jQuery
3. Tell me if you see anything other than the word “true” appear.
I think the problem is that multiple pieces of code are trying to give themselves the same name ("$"). jQuery takes it first, some other piece of code takes it afterward, and then everything that’s expecting “$” to refer to jQuery gets broken. The instructions above should help to test this possibility.
