Greasemonkey script doesn't work on Firefox? [closed]

Question

Hi,

After I have installed Greasemonkey on my Firefox, and also the last version of the script of the Tampermonkey site (and then browser-reboot and so on...), the script doesn't seems to work on Firefox? 

However in Chrome work great!

Chrome:

 

Firefox:

 

May I forgot one step or something? Or there is a bug...?

Thank you :-)

Regards

Daniel

Comments

What versions of Firefox, Greasemonkey and the script? And, what operating system.

It works fine for me, but I am probably not using the latest Firefox version.

If others has issues as well, feel free to write your versions and OS as well.

---

Sure!
Firefox: 38.0.1
Greasemonkey: 3.2
Script: (The last one) 1.4.4
OS: Windows and Ubuntu

---

Two different computers:

1)
* Firefox Developer Edition 40.0a2
* Windows 7
* Greasemonkey 3.2
* G+PGC-script 1.4.4

2)
* Firefox 38.0.1
* Windows 7
* Greasemonkey 3.2
* G+PGC-script 1.4.4

Both worked fine last week, and both does not work today.

---

Upgraded my FF and are now running version 38 in Ubuntu. GM 3.2 and the latest script as well. No issues here.

One thing it COULD be, is that Groundspeak has pushed web changes to some of their users. But then I would expect it to break in Chrome as well. It's a fairly common way to test new web releases. If there are issues, only a random part will be affected and the issue will in that way be less urgent. But I honestly doubt that is the case this time, I don't even know if Groundspeak works like that.

We will have to keep investigating this. Until someone who can repair it can reproduce it, it will be hard to fix. More bug reports regarding this are welcome. It is a bit weird according to me, that it only affects Firefox, at least this far.

---

Yes, same conclusion here: a long working Firefox on Linux. Installed the GreasedMonkey script and enjoyed it very much. Bong: a few days ago the script stopped working altogether. I hope it gets fixed. And at the same, also the Connect To Facebook thing doesn't work anymore. Related? A GC.com problem more than a Project-GC or GM problem?

---

I'm having the same problem with FireFox 38.0.5

---

I have the same problem. It worked directly after the installation on my Firefox-Browser - but somehow stopped during this week. I re-installed the script but it doesn't help.

It works fine on my other Laptop with Firefox!?

---

No it doesn't work for either. I down graded the desktop to 37.0.2 and reinstalled GM and the script and still nothing.

EDIT: I downgraded to GreaseMonkey 3.1 from 3.2 and it works.

* Firefox 38.0.5
* Windows 7
* Greasemonkey 3.1
* G+PGC-script 1.4.4

And everything is fine. GreaseMonkey updating broke it. NOT FF

---

If anyone feel that they might have a chance to debug it, an "easy" way would be like this:
1) Go to about:addons using the location bar.
2) Click user scripts
3) Click the Geocaching.com + Project-GC
4) Click Preferences.
5) Click the Edit this User Script button in the bottom.
6) Add a line like this
console.log('foo');
as a first line inside the Main function (around line 52).
7) File menu, save.
8) Open a new tab
9) Open the console (Ctrl-shift-k). At least on my platform, otherwise use the menus, menu, developer, Web console.
10) Open a cache page.
In the console window, it should now say foo when loading the page. If not, the user script has not reached the row where we added the console.log. We will need to know where and why it breaks, so if it writes foo. Try moving the console.log to after ReadSettings() instead, save, and reload the cache page.

This is to my knowledge the best way to debug greasemonkey scripts in the current versions of Firefox.

---

I added the line into the script - and now it says "foo" in the console directly in the first line. After that a lot of errors are listed...

"foo" Geocachingcom_+_Project-GC.user.js:53:8
ReferenceError: $ is not defined GC5V45T_wwfm-xii-bubbles-vs-muggles-in-gutersloh:33:2
Diese Website verwendet ein SHA-1-Zertifikat; es wird empfohlen, Zertifikate mit Signaturalgorithmen zu verwenden, die stärkere Hashfunktionen verwenden als SHA-1.[Weitere Informationen] 5668133f-3be3-41f4-bc7d-286b0639f97e.gif
Diese Website verwendet ein SHA-1-Zertifikat; es wird empfohlen, Zertifikate mit Signaturalgorithmen zu verwenden, die stärkere Hashfunktionen verwenden als SHA-1.[Weitere Informationen] bd50392b-9adf-42e9-a3d4-c06ac002236c_a.jpg
Diese Website verwendet ein SHA-1-Zertifikat; es wird empfohlen, Zertifikate mit Signaturalgorithmen zu verwenden, die stärkere Hashfunktionen verwenden als SHA-1.[Weitere Informationen] badafcd7-28b9-4da1-aa0b-6a5c5cf7bcd6_a.jpg
Diese Website verwendet ein SHA-1-Zertifikat; es wird empfohlen, Zertifikate mit Signaturalgorithmen zu verwenden, die stärkere Hashfunktionen verwenden als SHA-1.[Weitere Informationen] cd0f6e32-a7b8-4137-b808-831bcf77e92a_a.jpg
Diese Website verwendet ein SHA-1-Zertifikat; es wird empfohlen, Zertifikate mit Signaturalgorithmen zu verwenden, die stärkere Hashfunktionen verwenden als SHA-1.[Weitere Informationen] 4ee55749-0c74-44e0-8edd-47e185c1d0ee_a.jpg
Diese Website verwendet ein SHA-1-Zertifikat; es wird empfohlen, Zertifikate mit Signaturalgorithmen zu verwenden, die stärkere Hashfunktionen verwenden als SHA-1.[Weitere Informationen] 849ba7f6-60af-4ed0-a780-19c596af4446_a.jpg
Diese Website verwendet ein SHA-1-Zertifikat; es wird empfohlen, Zertifikate mit Signaturalgorithmen zu verwenden, die stärkere Hashfunktionen verwenden als SHA-1.[Weitere Informationen] 0b11aebd-d2b1-4ed1-878d-4f3d277c13a8_a.jpg
Diese Website verwendet ein SHA-1-Zertifikat; es wird empfohlen, Zertifikate mit Signaturalgorithmen zu verwenden, die stärkere Hashfunktionen verwenden als SHA-1.[Weitere Informationen] f456ef05-f4ef-4cd3-884e-34543f144699_a.jpg
Diese Website verwendet ein SHA-1-Zertifikat; es wird empfohlen, Zertifikate mit Signaturalgorithmen zu verwenden, die stärkere Hashfunktionen verwenden als SHA-1.[Weitere Informationen] 8640b618-fbf2-4dd6-a10d-636d7a305a5a_a.jpg
Diese Website verwendet ein SHA-1-Zertifikat; es wird empfohlen, Zertifikate mit Signaturalgorithmen zu verwenden, die stärkere Hashfunktionen verwenden als SHA-1.[Weitere Informationen] 0986e53d-4b65-4895-aa4d-eb71188b5086_a.jpg
Diese Website verwendet ein SHA-1-Zertifikat; es wird empfohlen, Zertifikate mit Signaturalgorithmen zu verwenden, die stärkere Hashfunktionen verwenden als SHA-1.[Weitere Informationen] 7004bd1a-7e33-4f64-affc-f43db39754d6_a.jpg
Diese Website verwendet ein SHA-1-Zertifikat; es wird empfohlen, Zertifikate mit Signaturalgorithmen zu verwenden, die stärkere Hashfunktionen verwenden als SHA-1.[Weitere Informationen] 1ac2533c-e57f-4525-8c2d-e5f24b5e509a_a.jpg
Diese Website verwendet ein SHA-1-Zertifikat; es wird empfohlen, Zertifikate mit Signaturalgorithmen zu verwenden, die stärkere Hashfunktionen verwenden als SHA-1.[Weitere Informationen] 248d6cd1-995e-4430-a90f-b2c07a6e98fe_a.jpg
Diese Website verwendet ein SHA-1-Zertifikat; es wird empfohlen, Zertifikate mit Signaturalgorithmen zu verwenden, die stärkere Hashfunktionen verwenden als SHA-1.[Weitere Informationen] 37850737-b2e4-435b-9a9a-8742eb0f98fd_a.jpg
Diese Website verwendet ein SHA-1-Zertifikat; es wird empfohlen, Zertifikate mit Signaturalgorithmen zu verwenden, die stärkere Hashfunktionen verwenden als SHA-1.[Weitere Informationen] 5828a867-0b4c-45ca-a670-8eb0efbc14f5_a.jpg
Diese Website verwendet ein SHA-1-Zertifikat; es wird empfohlen, Zertifikate mit Signaturalgorithmen zu verwenden, die stärkere Hashfunktionen verwenden als SHA-1.[Weitere Informationen] e7997b10-2b8a-4afc-b479-e9d3135ca265_a.jpg
Diese Website verwendet ein SHA-1-Zertifikat; es wird empfohlen, Zertifikate mit Signaturalgorithmen zu verwenden, die stärkere Hashfunktionen verwenden als SHA-1.[Weitere Informationen] 18ae75d0-59af-4bfc-bb58-6a04678f327d_a.jpg
Diese Website verwendet ein SHA-1-Zertifikat; es wird empfohlen, Zertifikate mit Signaturalgorithmen zu verwenden, die stärkere Hashfunktionen verwenden als SHA-1.[Weitere Informationen] 2044a6d3-9bc6-4166-bb0b-6adfd9cae8c9_a.jpg
Diese Website verwendet ein SHA-1-Zertifikat; es wird empfohlen, Zertifikate mit Signaturalgorithmen zu verwenden, die stärkere Hashfunktionen verwenden als SHA-1.[Weitere Informationen] b326e3c7-59cc-4666-a12a-9d8e362a9c93_a.jpg
Diese Website verwendet ein SHA-1-Zertifikat; es wird empfohlen, Zertifikate mit Signaturalgorithmen zu verwenden, die stärkere Hashfunktionen verwenden als SHA-1.[Weitere Informationen] af07d0d1-ff81-4538-9ce5-8fe24ecca287_a.jpg
Diese Website verwendet ein SHA-1-Zertifikat; es wird empfohlen, Zertifikate mit Signaturalgorithmen zu verwenden, die stärkere Hashfunktionen verwenden als SHA-1.[Weitere Informationen] 52191d86-c5b0-4270-88df-1d7c6836d17c_a.jpg
Diese Website verwendet ein SHA-1-Zertifikat; es wird empfohlen, Zertifikate mit Signaturalgorithmen zu verwenden, die stärkere Hashfunktionen verwenden als SHA-1.[Weitere Informationen] e657b89d-a97f-4c91-a581-db7e38fac890_a.jpg
Diese Website verwendet ein SHA-1-Zertifikat; es wird empfohlen, Zertifikate mit Signaturalgorithmen zu verwenden, die stärkere Hashfunktionen verwenden als SHA-1.[Weitere Informationen] a5c226ce-e649-4344-8bdb-7e38b184cdb3_a.jpg
Diese Website verwendet ein SHA-1-Zertifikat; es wird empfohlen, Zertifikate mit Signaturalgorithmen zu verwenden, die stärkere Hashfunktionen verwenden als SHA-1.[Weitere Informationen] 5a6b855c-1107-41c5-919f-0fa9e8c72a37_a.jpg
Diese Website verwendet ein SHA-1-Zertifikat; es wird empfohlen, Zertifikate mit Signaturalgorithmen zu verwenden, die stärkere Hashfunktionen verwenden als SHA-1.[Weitere Informationen] 5dd2595a-a267-438f-b397-9d9d37070b1d_a.png
getPreventDefault() sollte nicht mehr verwendet werden. Verwenden Sie stattdessen defaultPrevented. coreJS:1:0

---

I don't think the errors are related. The only thing I am not sure of is the first one.
ReferenceError: $ is not defined GC5V45T_wwfm-xii-bubbles-vs-muggles-in-gutersloh:33:2
To me it seems like there is some inline javascript in the HTML that references jQuery, but it's not loaded. And if it's from inline JS it's not relevant.
Then you have a lot of complaints about image loading, I can't translated it exactly, but it's some form of complaint that it doesn't like SHA1 I guess.
The last error is from coreJS, which I assume is something that geocaching.com uses itself.

I would suggest moving the console.log('foo'); after ReadSettings();, if you still see it, move it to after CheckPGCLogin(); Here I doubt that you will see it since it doesn't work.

If it is as I assume, that you see foo when it's after ReadSettings(), but not when after CheckPGCLogin(), then we need to follow. CheckPGCLogin() calls BuildPGCUserMenu() and Router(). Since you don't get the PGC-username in the top. I assume something is wrong within BuildPGCUserMenu() actually. Find the function BuildPGCUserMenu() and move console.log in there to see how far it gets.

I hope I am not confusing you a lot here. Trying to be fairly verbose, always hard when I don't know the experience of the one I speak with.

---

Code:
function ReadSettings() {
        settings = GM_getValue('settings');
        console.log('foo10');
        if (typeof(settings) != 'undefined') {
            settings = JSON.parse(settings);console.log('foo11');
        } else {
            settings = [];console.log('foo12');
        }

        var items = GetSettingsItems();
        console.log('foo13');
        for (var item in items) {
            console.log('foo14');
            if (typeof(settings[item]) == 'undefined') {
                settings[item] = items[item].default;
                console.log('foo15');
            }
        }
        console.log('foo16');

Console:
"foo10" Geocachingcom_+_Project-GC.user.js:145:8
"foo11" Geocachingcom_+_Project-GC.user.js:147:44
"foo13" Geocachingcom_+_Project-GC.user.js:153:8
"foo14" Geocachingcom_+_Project-GC.user.js:155:12
This site makes use of a SHA-1 Certificate; it's recommended you use certificates with signature algorithms that use hash functions stronger than SHA-1.[Learn More] 749a92f4-ca2e-4d72-a053-a60021d90e45_a.png
This site makes use of a SHA-1 Certificate; it's recommended you use certificates with signature algorithms that use hash functions stronger than SHA-1.[Learn More] 2da30d3b-76a7-4a70-8127-9b409cb62674_a.jpg
This site makes use of a SHA-1 Certificate; it's recommended you use certificates with signature algorithms that use hash functions stronger than SHA-1.[Learn More] 7fd91583-b695-46f8-869c-68ea6155c150_a.jpg
This site makes use of a SHA-1 Certificate; it's recommended you use certificates with signature algorithms that use hash functions stronger than SHA-1.[Learn More] e4965118-0167-4da9-9968-96eef81eaef4_a.jpg
This site makes use of a SHA-1 Certificate; it's recommended you use certificates with signature algorithms that use hash functions stronger than SHA-1.[Learn More] 8e2b489c-6f7f-46d0-804d-c0bb9c36c3a7_a.jpg
This site makes use of a SHA-1 Certificate; it's recommended you use certificates with signature algorithms that use hash functions stronger than SHA-1.[Learn More] e0a7d34e-b41d-42df-a713-2c222e838141_a.jpg
Use of getPreventDefault() is deprecated.  Use defaultPrevented instead. coreJS:1:0

And then it stops...

---

That's great! Now we can see almost exactly where it stops. The downside is that I can't figure out why. I have sent a message to Surfoo to see if he can understand it as well.
Meanwhile, could you try to add:
console.log(settings);
console.log(items);
just after you log foo13? It would be interesting to see what they are.

Maybe also add a
console.log('foo14.5');
before
settings[item] = items[item].default;
I assume this line is what actually breaks, I just can't understand why.

---

"foo10" Geocachingcom_+_Project-GC.user.js:145:8
"foo11" Geocachingcom_+_Project-GC.user.js:147:44
"foo13" Geocachingcom_+_Project-GC.user.js:153:8
null Geocachingcom_+_Project-GC.user.js:154:8
Object { showVGPS: Object, addChallengeCheckers: Object, makeCopyFriendly: Object, addPgcMapLinks: Object, addLatestLogs: Object, cloneLogsPerType: Object, addPGCLocation: Object, addAddress: Object, removeUTM: Object, addPgcFp: Object, 8 more… } Geocachingcom_+_Project-GC.user.js:155:8
"foo14" Geocachingcom_+_Project-GC.user.js:157:12
Use of getPreventDefault() is deprecated.  Use defaultPrevented instead. coreJS:1:0

---

After settings = JSON.parse(settings);
add
            if(settings === null) {
                settings = [];
            }
I bet this fixes it, though I do not know why it broke. If this fixes the issue, we will release a new script with that fix in it, and within 24 hours from that, all your own changes will be removed again, since we are bumping the version number.

---

YEAH!! Now it works!! :-)

---

Thank you for your help. Greatly appreciated, hopefully not the least from other users. I will try to make a release of a new script today or tomorrow. It takes up to 24h for them to auto-update.

---

Great! Thank you! :-)

---

Yeah, it works - GREAT!!
Sorry for not responding earlier this afternoon – but summer just decided to hit ground here in Germany!   ;-)

---

Great job, guys: it works well now. Good show!

Answer 1

Same problem here. Seems like the script doesn't work anymore with the last Firefox-update.

Comments

Same here stopped working in firefox

---

Just received the script update - it works fine again. Thanks to Dandroider and ganja1447. Great Job!

Answer 2

It has stopped working during the last 24/48 hours - both on Firefox and on Firefox Developer Edition.

Probably a browser update.

Answer 3

Very strange. I have tried to

* uninstall/reinstall the script

* install greasemonkey + script on a new computer

* remove other scripts (Geocaching Map Enhancements)

...and nothing works.

 

I already love this script so much, that I actually took the time to install chrome/tampermonkey/both scripts and there everyting works fine :)

Answer 4

For me it doesn't work on neither browser. It stopped working on firefox maybe a week ago, so i tried it with tampermonkey on chrome but it does not work there either. I really like the script so its too bad that its not working.

Comments

After the update to 1.4.5 it now works for me, thanks.