After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 679551 - No more extension list on the website in Firefox 13 (javascript error)
No more extension list on the website in Firefox 13 (javascript error)
Status: RESOLVED DUPLICATE of bug 679515
Product: website
Classification: Infrastructure
Component: extensions.gnome.org
current
Other Linux
: Normal normal
: ---
Assigned To: Shell extensions maintainer(s)
Shell extensions maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2012-07-07 11:50 UTC by Rui Nibau
Modified: 2012-09-26 04:36 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Rui Nibau 2012-07-07 11:50:02 UTC
I can't see any gnome-shell extension on the website since Firefox 13. There's a javascript error in every page (visualized with Firebug) :

 Message: $.cookie is not a function
 Line :   $.ajaxSettings.headers['X-CSRFToken'] = $.cookie('csrftoken');
 File:    main.js (ligne 13)

I don't have this problem with Web (Epiphany) or Aurora (Firefox 15) on the same machine with the same gnome-shell browser plugin (libgnome-shell-browser-plugin.so).

Web Browser : Firefox 13.0.1
OS : Fedora 17 64bit
Comment 1 Jasper St. Pierre (not reading bugmail) 2012-07-07 14:54:13 UTC
This means that jquery.cookie.js isn't getting loaded somehow.
Comment 2 Rui Nibau 2012-07-07 15:12:33 UTC
(In reply to comment #1)
> This means that jquery.cookie.js isn't getting loaded somehow.

Yes, that's what happen. What i don't understand yet is why. Everything is ok with Firefox 15 (Aurora) and everything is ok with Firefox 13 under Windows (means: i have the extension's list displayed).

In fact, running my own version of Firefox 13 (picked from Mozilla website), not the one packaged on Fedora 17, there is no problem at all.

So, maybe the bug comes :

(1) From the Firefox packaged on Fedora 17.

or

(2) A conflict from the gnome-shell brower plugin and one of the many extensions i used.

I'll try to investigate a little more
Comment 3 Rui Nibau 2012-07-07 15:42:03 UTC
Well, that seems to be a firefox 's profile problem : running Firefox with a clean new profile, everything's is ok.

Have to find out what in my profile (extensions, plugins, prefs) is causing the bug.
Comment 4 Jasper St. Pierre (not reading bugmail) 2012-07-07 15:51:33 UTC
The cache is stored in the profile. It's probably that. Try going to this URL and hitting Ctrl+F5.

https://extensions.gnome.org/static/js/jquery.cookie.js

Does that fix it?
Comment 5 Rui Nibau 2012-07-07 17:10:01 UTC
(In reply to comment #4)
> The cache is stored in the profile. It's probably that. Try going to this URL
> and hitting Ctrl+F5.
> 
> https://extensions.gnome.org/static/js/jquery.cookie.js
> 
> Does that fix it?

Nope :-(

In fact, the jquery.cookie.js is clearly called in the html page, so there should not be that kind of problem. Except the website is using require.js to load js dependencies ; the main callback function is maybe ran before all dependencies (i.e. jquery.cookie.js) are loaded ; but in that case, i should see the require.js warnings in firebug console ; but there's nothing except the error.

As i said, a new clear and fresh profile resolved the problem. I have imported all my stuff (passwords, bookmarks, extensions, etc.) and everything's fine now : i can use the website again.

I'll keep my old buggy profile and try to investigate what have happened ; it was an old profile, migrate from ubuntu to Fedora and with a lot of crappy stuff in it as i'm doing my web developpements with it (i'm a js developper).

Thanks Jasper.

Marking the bug report as resolved.
Comment 6 Raphael Rochet 2012-09-20 18:24:05 UTC
I had this error too.

If this can help others : I had Firefox cache disabled from firebug. I enabled it back and the site is woking.
Comment 7 Jasper St. Pierre (not reading bugmail) 2012-09-26 04:36:04 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.

*** This bug has been marked as a duplicate of bug 679515 ***