Question

This is just too bizarre.
I’m new to Greasemonkey, but I downloaded a script from userscripts.org and it works fine. I then created a duplicate of that script using ‘New User Script’ from the GM menu and then pasted the original script into the new script. I then disable the old script and enable the new script and the new script doesn’t work.

Answer 1

You “pasted the original script into the new script” without any edits?

Some things that can go wrong:

1. The new script should have a different name — other wise the script installation(s) could get corrupted.

2. Does the script have @require line(s) in the header? If so, then know that the necessary resources are only fetched during a pure install and this mechanism does not work when using the “New User Script” menu.

   To resolve this:

   1. Save the new script file to a handy folder, perhaps, C:\Work\YourScript.user.js. Do not use the windows temp folder as GM install is buggy there.

   2. In Greasemonkey’s “Manage User Scripts” dialog, Uninstall the new script (and any potential name-conflicts).

   3. In the browser, use File->Open File and browser to your script (EG C:\Work\YourScript.user.js) and open it. The Greasemonkey Install dialog should pop up.

   4. Install the script. The required resources should now be fetched and saved properly. You can check this by looking in the scripts install folder — which will be something like:
      C:\Documents and Settings\{Win Username}\Application Data\Mozilla\Firefox\Profiles\{Random string}.default\gm_scripts\YourScript\ on a windows system.

3. Make sure the “Included Pages” are what you think they are. You can check this in Greasemonkey’s “Manage User Scripts” dialog.

4. Double check the script edits. In Greasemonkey’s “Manage User Scripts” dialog, press the Edit button and inspect the code.

5. If all else fails, paste the full, unedited, script code here — there’s probably a syntax and/or code error we can help you with. Including the code is always a good idea.