[Greasemonkey] Re: Greasemonkey 0.3 - ugh, migration - read this before installing 0.3

Aaron Boodman zboogs at gmail.com
Mon Apr 11 01:45:20 EDT 2005

Forgot to mention one rather important thing.

To support the new edit button, I changed the configuration format
slightly. This has been the first such change since greasemonkey was

I got rid of the ID attribute in the config file and replaced it with
a filename attribute. When you download files now, I come up with a
unique (in the scope of files you've already installed) name for it,
based on the scripts actual name, and append ".user.js". That way,
when the file is launched from clicking the edit button, your OS does
the right thing for javascript files.

What this means to you: If you want to keep your current user script
configuration, follow these instructions:

* Before installing, back up your current {profile
* Install GM 0.3
* navigate to the scripts folder, open config.xml
* replace all instances of id="somenumber" in the file with
* rename all the numbered files in the scripts folder with the
extension ".user.js" so that they correspond with the changes made in
the config file.
* If you screw up, restore from the backup you made in the first step
and try again :)

Sorry, I totally forgot about this till I sent the last mail. I might
have to come up with a script that does this as part of the install or


On Apr 11, 2005 12:22 AM, Aaron Boodman <zboogs at gmail.com> wrote:
> Spent a little while getting all the changes I've been working on
> separately consolidated into one big release.
> Here's what this includes:
> New
> ========================================
> * local data persistence - see below
> * added an edit button to manage dialog
> * traded enable all/disable all buttons in manage dialog for an
> enable/disable greasemonkey icon in the bottom right corner of
> browser. Some users wanted this to be able to enable and disable GM
> quickly.
> * GM_log(message)
> * added support for data urls (not for context menu though)
> * works in FF 1.0.3 (some scripts need updates though, more below)
> From 0.2.7b
> ========================================
> * scoped GM_* down to user scripts only
> * clipped user script names in manage screen with elipsises so that
> they cannot push the install button off the window
> * improved error handling; isolating scripts errors from each other
> Data Persistence
> ========================================
> * GM_setValue(name, value)
>    value can be a string, boolean, integer, or null. Other types will
> throw an error.
> * GM_getValue(name, default)
>    if value doesn't exist, default will be returned. If default is not
> specified, undefined will be returned.
> FF 1.0.3 breaks scripts that use window._content
> ========================================
> The undocumented, unsupported window._content property on the
> content's window object has disappeared in 1.0.3 breaking a few user
> scripts which were using it.
> The funny thing is that window._content just resolved to window. So it
> was totally unnecessary.
> The scripts I ran into which do this were google image relinker and
> all music guide corrector. These scripts, and any others which did
> this, should replace references to window._content with just window.

More information about the Greasemonkey mailing list