InformAction Forums

I just completed a standard diagnostic to determine that Noscript 1.9.1.7 has been causing me issues with the extensions Stylish and Greasemonkey, both of which are the latest versions themselves.

When I try to open the "manage scripts" window with greasemonkey or "manage styles" in stylish, the same thing happens.

I get a window that's been reduced to nothing but the title bar, and only long enough to fit the min/restore/max buttons. When I expand it, it says "page load error" in the title bar and gives me the following information.

Address not found
Firefox can't find the server at c.
The browser could not find the host server for the provided address.
* Did you make a mistake...

I think we all know the error page.

Quite frustrating. I can't modify, delete, or add user scripts or user styles.

That is interesting because I am running NS 1.9.17 and also Stylish and no issues. Granted no greasemonkey component but still, no clash here. Does disabling NS resolve the issue? If not there might be something else involved. Any error details in the console you can share on this?

Yes, disabling NS resolves the issue. It's the only thing that does.

To further test these issues I always create a new defaulted/reset profile and install the two extensions I think are clashing. In this case, it came down to ns 1.9.1.7 that was the problem.

Aerik wrote:Yes, disabling NS resolves the issue. It's the only thing that does.

To further test these issues I always create a new defaulted/reset profile and install the two extensions I think are clashing. In this case, it came down to ns 1.9.1.7 that was the problem.

Ok, I think that is sufficient now to turn it over to Giorgio and see if he can figure out something specific on this.

I'm unable to reproduce Aerik's problem in Firefox 3.0.8 using a fresh profile, default theme, and only the GM, ST, and NS extensions:
greasemonkey-0.8.20090123.1-fx.xpi
noscript-1.9.1.7.xpi
stylish-0.5.9-fx+tb+sm.xpi

Since you're using Fx 3.0.8, GµårÐïåñ, I'm not surprised it works for you too. I suspect it might be caused by Aerik's using 20090402 Shiretoko/3.5b4pre and not 3.0.8, but I'll leave that up to Giorgio and him to work out.

@Aerik:
Related to your continuing problems with extensions in nightly builds, such as this one.
I noticed you complained about problems with the ExExceptions extension on its amo review page, but failed to mention that was in a nightly build, not Fx 3.0.8. I've already verified the problems you noted did not exist when it's installed in Fx 3.0.8. http://forums.informaction.com/viewtopi ... 1258#p1258
You might want to consider editing your review to include the fact you were testing with a nightly, so potential users of ExExceptions won't be misled by it. Make sense?

Edit: Greasemonkey 0.8.20090123.1 is marked as compatible up to 3.1b3 not b4pre, the build Aerik's using.

Alan Baxter wrote:Since you're using Fx 3.0.8, GµårÐïåñ, I'm not surprised it works for you too. I suspect it might be caused by Aerik's using 20090402 Shiretoko/3.5b4pre and not 3.0.8, but I'll leave that up to Giorgio and him to work out.

Agreed, I wasn't able to reproduce it either and figured to give the benefit of the doubt that the information reported below the post "may" not be totally accurate so work despite it because I didn't want to say you are not using the latest release build and be wrong or get accused of presuming I know about their installation so I am glad you said it, thanks. I suspect since we can't reproduce it, unless we are doing something super special, it should fix the OP's problem but ultimately I figured I might be oversimplifying and decided to let Giorgio weigh in since he keeps his extensions forward compatible, but I agree with you totally, this "should" fix it.