0.6.9 Bug: Unable to Auto-Install Scripts

[David Alan]

Issue: Clicking on a user-script or clicking the "install" button when
viewing its source does not pop-up the Install dialog or install the
script. Clicking a link to *.user.js takes you to the source; where
clicking the button does nothing.

This problem surfaced only after updating to 0.6.9. Other users have
reported it:
- https://addons.mozilla.org/en-US/firefox/discussions/comments.php?DiscussionID=1182
- http://userscripts.org/forums/3/topics/431

I'm going to toggle all my addons to see if any of them are causing a
conflict and report back. Other users who have more info should report
here--I've posted a link to this in the open threads above.

[Aaron Boodman]

Dang, looks like we introduced a bug.

Do you see any interesting errors in the Firefox error console?

- a

[David Alan]

> Do you see any interesting errors in the Firefox error console?

Console is totally silent.

[David Alan]

> I'm going to toggle all my addons to see if any of them are causing a
> conflict and report back.

With no add-ons running other than GreaseMonkey, scripts still fail to
install. Behavior is the same as above.

[email.i...@googlemail.com]

I have the same issue too with 0.6.9

[Brian Donovan]

I noticed this as well but it seemed to miraculously fix itself after
I toggled Greasemonkey off and then back on again by clicking the
Greasemonkey icon in the Firefox statusbar.

After doing so, accessing a user script file again saw the auto
install dialog popping up as usual.

Sounds like voodoo, but it appeared to work for me.

[Aaron Boodman]

That makes sense because there was a change in this release to "fix"
the behavior of Greasemonkey's enabled state wrt allowing
installation.

Good detective work, Brian.

David, "email.ironside", before you try this hack, can you take a look
and see what the current value for greasemonkey.enabled is in
about:config?

Thanks,

- a

[David Alan]

> David, "email.ironside", before you try this hack, can you take a look
> and see what the current value for greasemonkey.enabled is in
> about:config?

GM seems to work fine on my laptop running OS X. As you mentioned,
it's likely I accidentally clicked it or something this morning. I
don't have access to the PC where I was having problems, but I'll
check the config value when I get back to work on Monday.

d.

[Markv]

I am running firefox 2.0.0.3 on win xp home. Same problem happening.

[Anthony Lieuallen]

On 5/11/2007 12:55 PM, David Alan wrote:
> Issue: Clicking on a user-script or clicking the "install" button when
> viewing its source does not pop-up the Install dialog or install the
> script. Clicking a link to *.user.js takes you to the source; where
> clicking the button does nothing.

I just created a fresh clean profile, and installed:
https://addons.mozilla.org/en-US/firefox/downloads/file/15526/greasemonkey-0.6.9.20070507.0-fx.xpi

And I see the exact same thing.

Back over in my regular profile, everything still works. Curious!

[Jonathan Wright]

A user of my script reported the same thing today.

I managed to reproduce the problem by creating a fresh FF profile and installing
Greasemonkey from scratch. At that point the monkey is pink and the menu item is
checked.. yet scripts are not recognised by GM. Disabling and re-enabling GM
fixes the problem (as described by Brian).

I've just checked again and notice that at the point of a fresh GM installation
(0.6.9.2007.05.07.0) the "greasemonkey.enabled" entry does NOT exist in prefs.js
so I guess a default of "false" is used (and the UI is out of step with the
internals). The entry is created the moment you untick the Greasemonkey
"enabled" menu item (I didn't test it, but I guess the same would be true when
clicking the GM icon).

hth

jont

[Aaron Boodman]

Yeah, Anthony has a fix pending for this. I will check it in and
probably do a push sometime next week.

Sorry for the crappy testing.

- a

[Techie-Micheal]

Not only am I seeing the exact same thing on my Vista on Firefox
2.0.0.4 (I think at least one person said XP on addons), but removing
one script removes everything. Attempting to reinstall the script that
I wanted to keep gave me an error saying file already existed. I had
to go in to gm_scripts and delete it there before it let me reinstall.
This was a fresh install, I haven't installed Greasemonkey before on
this machine.