InformAction Forums

Upgraded Seamonkey from .9 to .16. Finally got around add-ons not working -so I installed NoScript.

NoScript=noshow Went to FAQ and tried reinstall (BTW rec'd no partial install messages and have Administrator privileges on WinXP Prof SP3).

noscript.net is an allowed SW install site for Seamonkey.

Went to about:config and xpinstall is enabled = true.

Have tried both exiting and restarting Seamonkey and rebooting my machine.

Tried oddball websites but no NoScript icon appears at all.

There is a noscript JScript file under /pref in the Mozilla Profile on this PC

Help!

I upgraded the extension today, from 1.9.3.1 to 1.9.3.3 and immediately lost use of my Seamonkey web browser in Linux. Most of the items on the standard bar were missing; the exceptions were the 'View', 'Go', and 'Bookmark' items. The search and new tab buttons stopped working, and the status bar was replaced by a big gray rectangular box with a red carat.

Removing and reinstalling Seamonkey (along with the user profile) had no noticeable effect on the outcome. Only by downgrading to version 1.9.3.2 was the issue addressed.

The problem for applies only to regular accounts; the superuser/root account was never affected.

Edit: Merged here from NS Dev by Tom T., because same topic.

I'm seeing the same thing with SeaMonkey. NoScript will install but does not load or show up in the toolbars. I emailed the author with details about my experience on OS X with SeaMonkey, but I have confirmed that it affects SeaMonkey on XP as well. A fresh install of the latest 1.9.3.3 (and devel 1.9.3.5) does not install properly, even though it says it does.

I had to revert back to 1.9.2.8 in order for NoScript to work again. Something appears to have tweaked NoScript between 1.9.2.8 and 1.9.3.3.

Did you try with a clean profile?

Giorgio Maone wrote:Did you try with a clean profile?

I created a new Profile in Seamonkey, closed the browser and chose the new Profile when I reopened SM. I then installed NoScript again (telling it to install in the profile as the preferred location choice). Exited SM and restarted. I then got the same very same message (I originally encountered) about an incomplete install - and to reinstall again. I did that and closed and restarted SM (new profile) and still no sight of No Script.

There is a NoScript file in the PREF folder under the new profile, however, there was one under the old profile as well...

Giorgio Maone wrote:Did you try with a clean profile?

I also tried with a clean profile every time, clean install of SeaMonkey every time, and even setup a new user to do the testing. It definitely isn't because of any old bits hanging around.

Additional discussion here, http://www.hirsch.sth.ac.at/~robert/the ... 110003.xml.
Scroll down to <aardvaark>'s posts.

BTW, I could not duplicate in XP, though there is no real way for me to have a truly "clean" install even in a new Profile, because of the globally installed parts.

Looks like recent "modularized" NoScript doesn't play nice with Seamonkey if installed in profile (which, ironically, is still the recommended option during fresh installation).
The work-around getting rid of noscript.jar and of every instance of noscript in $profile/chrome (if you've got a regexp-enabled editor is done replacing the following regexp with an empty string: ) and reinstalling globally (using the cancel button on the install prompt).

I'm working hard to release a build automating this process.

But still defaulting to install into Profile, correct?

Nope, it will keep global install only.
Profile install is way too much problematic on Seamonkey, and I've already wasted the last 24 hours trying to support an end of life product

Do reconsider.
A Profile install is the only way to allow for a specific profile to NOT have NoScript installed. At that point (global install), it makes it very difficult to try to diagnose problems.

Is this a Linux only issue?

It's a cross-OS issue.
Would an easy way to uninstall NoScript help?

I suppose it would be better then nothing.

Having one session with NoScript & one without makes things easy.
An uninstall would again be global, so less then optimal.
Yes, I understand the constraints of SeaMonkey. (And the near obsolescence of 1.1.x. Though that may be different on the Linux end where it's life could extend past the time where the Windows user would have migrated to 2.0?)

(Wonder why I haven't been seeing a problem? Because in general I have always been installing overtop an existing version?)

(Older) NoScript.jar is left in Profile /chrome/ - haven't restarted yet.

---

Restarted.

Well I guess you know the answer. (As I watched the Profile /chrome/ version disappear.)

Then I guess you know what happened next. (The dialog box along with a fubar'd SeaMonkey.)

And yes, (another) restart did set things straight.

Just wasn't expecting that.

---

Since I've already been "unexpected", just what does an Uninstall do?
Leaves my settings in prefs.js & in /ABE/, & only installs the program portions, I'll assume?

---

Uninstall did leave noscript.jar in Program /chrome/.
Otherwise the Profile data looks untouched.
Oh, the restart dialog came up kind of behind the NoScript Options dialog.

---

My main problem with all of this is that when things (a website) don't work right, & you're not getting anywhere with it, you cannot then fire up a different Profile without NoScript in order to rule it out. If you're in a situation where you can close your browser windows & restart, then it isn't too big of a deal. But if you've got 1001 things going on, or are in the middle of placing an order (which is not working), then you've got yourself into a quandary. At that point, you're kind of relegated to fire up a different browser, be it SeaMonkey 2 or some FF version.

---

If you had two simultaneous instances of SeaMonkey running when you uninstalled it from one, it looks as if SeaMonkey does remain active in the other - until the second instance is closed & restarted. And vice-versa I suppose.