Greasemonkey Manual:Getting Help: Difference between revisions
| Line 22: | Line 22: | ||
And finally, if you are a script author, including the exact code that is causing problems is really important. | And finally, if you are a script author, including the exact code that is causing problems is really important. | ||
The best option is to provide a URL to some sort of pastebin service, like ''gist.github.com'' | The best option is to provide a URL to some sort of pastebin service, like [''gist.github.com''| http://gist.github.com] or [''pastebin.com''|http://pastebin.com/], which can communicate the entire, and exact, source code causing the problem. | ||
Equally important is providing the ''whole'' script, not just a few lines of code. | Equally important is providing the ''whole'' script, not just a few lines of code. | ||
The real problem might lie elsewhere; without being able to see that code, nobody can help you. | The real problem might lie elsewhere; without being able to see that code, nobody can help you. | ||
Revision as of 00:00, 26 March 2011
 Greasemonkey Manual |
| Using Greasemonkey |
|---|
| Installing Scripts |
| Monkey Menu |
| Getting Help |
| User Script Authoring |
| Editing |
| Environment |
| API |
If you've run through all the troubleshooting steps and you still can't get things to work right, there are communities you can turn to to seek more help.
What to Say
If you're having problems, you should always A) start by troubleshooting yourself and B) be prepared to explain what you've already done, and what the results were. Without that information, even someone who wants to help you can only, at best, guess. You'll have to type all this information out sooner or later, so doing it ahead of time makes things easier for you and someone who might help, and therefore makes it more likely that someone will be willing to help.
There's also a lot of specifics that may be different from person to person, and may be contributing to the problem. Please be sure to communicate all of the following information:
- Operating System (E.G. Windows XP, Windows 7, Mac OS X Snow Leopard, Ubuntu Linux 8.10)
- Firefox version (Open Help, About Mozilla Firefox then select and copy the last line of text, E.G. "Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.9.2) Gecko/20100115 Firefox/3.6".)
- Greasemonkey version (Find it in Tools, Add-ons, E.G. 0.8.20091209.4.)
- Exactly which script, if any, is causing a problem? Give an exact name, and if at all possible, the URL where it can be found.
- Exactly which page, if any, is exhibiting this problem. Please give a URL. If some sort of registration or login or other permission is required, please state this instead.
And finally, if you are a script author, including the exact code that is causing problems is really important. The best option is to provide a URL to some sort of pastebin service, like [gist.github.com| http://gist.github.com] or [pastebin.com|http://pastebin.com/], which can communicate the entire, and exact, source code causing the problem. Equally important is providing the whole script, not just a few lines of code. The real problem might lie elsewhere; without being able to see that code, nobody can help you.
If you provide the source code via email, please do not paste it into the body of your message: e-mail clients will wrap lines, change characters, and generally break the code in other subtle ways. Attaching the source code as a file makes sure it is not broken in transit.
Where to Say It
To find assistance, there are some good places to look:
- Problems with one user script should be brought to the attention of that script's author.
- If you are the author of the script, or otherwise still need help, you can turn to the greasemonkey-users mailing list.
- Also available are the forums at userscripts.org, with multiple appropriate topics.
- Finally, you may also try IRC: irc://irc.freenode.net/#greasemonkey
