Script stopped working suddenly in firefox

547 views
Skip to first unread message

Chuck Simmons

unread,
Nov 19, 2012, 3:48:35 AM11/19/12
to greasemon...@googlegroups.com
I'm stuck and looking for ideas as to what I might try next to figure out how to revive my script on firefox.

I had a script I was using in firefox.  I made a backup copy of the script, modified the script, and installed the new script.  Upon trying to run the new script by accessing the relevant web page, nothing happens.  This is typically the kind of behavior I see when I introduce a gross syntax error.  By "nothing happens", I mean I cannot get console.log() to print out messages on the firebug console nor on the firefox web console or the firefox error console.  Eventually I gave up on trying to figure out what I had broken, and reloaded the backed up copy.  Now, the backup copy that used to work fine also exhibits the "nothing happens" behavior.   It seems unlikely that a new firefox release might have shown up in the hour or so that I was screwing around, and the web page my script runs agains also probably didn't get updated.  Chrome runs my script just fine.  I've restarted firefox and I've disabled and removed firebug, but things aren't coming back to life.

I'd use Chrome, but Chrome doesn't work well with the web site (Lord of Ultima) that I'm adding a script to.  Chrome apparently doesn't do a stable sort, and Chrome has some weird ideas about when short pieces of text should be truncated to have '...' appended.

I haven't been able to get any output logged to the console when using firefox...

Chuck Simmons

unread,
Nov 19, 2012, 5:02:16 AM11/19/12
to greasemon...@googlegroups.com
As near as I can tell, the updater.php file that greasemonkey uses for a script installed from disk must have changed at some point.  When I reloaded my app, it must have installed a broken updater.php that prevented my script from being executed.  I was getting an error to the effect that there was a missing '=' sign in some xml in updater.php.  Replacing updater.php with a file containing a comment seems to have fixed my problem.

Anthony Lieuallen

unread,
Nov 19, 2012, 10:43:43 AM11/19/12
to greasemon...@googlegroups.com
I don't know what updater.php is, but it is not part of Greasemonkey.

When you want help with a particular script, you basically always have to post a link to it, or nobody can really do anything besides guess wildly.  Whatever updater.php is, there's almost definitely a reference to it somewhere within your script.

Chuck Simmons

unread,
Nov 26, 2012, 3:47:05 AM11/26/12
to greasemon...@googlegroups.com
See, you didn't need a link to my script to tell me that.  ;-)

Thanks.  I got past that part of my confusion.  There was an @requires tag in the header of the script.

The key symptoms in this problem report are that I had installed a new version of the script, and when I reinstalled the old version which had been working, things continued to be broken.  Since greasemonkey (well, something) fetches files as of installation time, reinstalling the old script does not restore the state of the gm_scripts/ directory.  It should be possible for sufficiently experienced troubleshooting documentation to eventually list this symptom and point to the gm_script/ directory and the @requires tag in the header of the script.  All without needing to have a link to my script.

I wasn't asking "can you proofread my 6,000 line script"; I was asking "what general techniques do people use to troubleshoot greasemonkey scripts, particularly when they see <these> symptoms".

g'luck, Chuck


--
You received this message because you are subscribed to the Google Groups "greasemonkey-users" group.
To post to this group, send email to greasemon...@googlegroups.com.
To unsubscribe from this group, send email to greasemonkey-us...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/greasemonkey-users?hl=en.

Josef Davies-Coates

unread,
Nov 26, 2012, 6:17:34 AM11/26/12
to greasemon...@googlegroups.com
Greasemonkey as completely stopped working for me on ubuntu 12.10, firefox 17 and greasemonkey 1.5 so perhaps you're having a similar problem and it has nothing to do with your script?
To unsubscribe from this group, send email to greasemonkey-users+unsub...@googlegroups.com.

Josef Davies-Coates

unread,
Jan 6, 2013, 5:06:59 PM1/6/13
to greasemon...@googlegroups.com
On Monday, 26 November 2012 11:17:34 UTC, Josef Davies-Coates wrote:
Greasemonkey as completely stopped working for me on ubuntu 12.10, firefox 17 and greasemonkey 1.5 so perhaps you're having a similar problem and it has nothing to do with your script?


Actually, it is only 2 scripts that have stopped working in firefox. 

These two:
http://userscripts.org/scripts/show/126440 (which is based on the other)

The exact same scripts still work in chromium using tampermonkey.

Any ideas why?

Many thanks,

Josef.


Josef Davies-Coates

unread,
Jan 6, 2013, 5:10:18 PM1/6/13
to greasemon...@googlegroups.com
I'm guessing it might be something to do with?

Also, I noticed that with the Google Link Cleanup script enabled I was unable to save events on Google Calendar (whilst using firefox, not yet checked with chromium).  So I guess the script is doing something, but it isn't doing what it used to do...

Hmz, perhaps there is a newer version or something that would make it work again?

Any tips greatly appreciated, I don't really know what I'm doing! :P

Cheers,

Josef.


Reply all
Reply to author
Forward
0 new messages