Monday, November 19, 2012

Greasemonkey 1.5 Release

The entire list of bugs handled in this release is also available via the 1.5 milestone on GitHub. Note that as always it takes some time for Mozilla to review the new version, but it's available on the all versions page immediately.

If you are using it and notice problems, it's best to log an issue or let us know at greasemonkey-dev (and be clear that it's with this version).

Enhancements:
  • Improve the clarity of the error message when installing a script with a missing sub-resource. (#1666)
  • Create opt-in only statistics gathering.  See the post about this. (#1651)
  • When displaying an update that has been found but not installed due to user settings, show the version that will be installed by the update, not the version already installed.  (#1497)
Bug fixes:
  • Fix a failure to download updates when one is found. (#1669)
  • Fix the enable/disable pattern on the User Script Commands sub menu. (#1665)
  • Do not break the script when adding a bad (i.e. 404) URL as a new @require. (#1661)
  • Avoid loops when the resource at downloadURL and updateURL disagree about the newest available version. (#1659)
  • Fix when relative URLs are provided for downloadURL or updateURL. (#1658)

3 comments:

Aaronius said...

Since my FireFox and GreaseMonkey autoupdated, My Kingdoms of Camelot (KoC) TOOLS script no longer works. This is true for the version I had and the updated version with a release date of yesterday: 11/27/12

Script 150317 in userscripts.org.

Tried all things to fix including updating, deleting, disabling all scripts, even deleting all but the one that is not working. no luck. I also use KoC PowerBOT (150307) and KoC Throne Room Organizer (132329), and both of those are working just fine.

Can you help me?

Matt Allen said...

userscripts have stopped working since firefox auto updated to v17. tried upgrading from 0.9.22 up to 1.5 but they still dont work. comment above provides KoC userscripts i cannot get to work

arantius said...

There are a small handful of complaints about those scripts, but none that I can see about any others. It's almost definitely those scripts that are broken, and you should thus be contacting the author(s) of those scripts.

Once they know what's wrong, it may be something easy to fix, or it may be appropriate for them to pass a bug report up to Greasemonkey.