1) Loading the script into Chrome may be a useful troubleshooting step. The chrome error message and debugging tools may provide errors that are not provided by greasemonkey/firefox tools. Chrome may display other interesting symptoms that can help debug a problem.
2) In my particular case, I had problems with updater.php. It may be desirable to mention updater.php in the troubleshooting page. Specifically, it was not immediately obvious to me that the error message I eventually found in my firefox error console referring to updater.php was relevant. The specific symptoms: a file works, but stops working when reloaded, may indicate a problem in updater.php. A pointer to more information about updater.php may be useful. -- You received this message because you are subscribed to the Google Groups "greasemonkey-users" group. To view this discussion on the web visit https://groups.google.com/d/msg/greasemonkey-users/-/5I1ELFBMeBgJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/greasemonkey-users?hl=en.
