NoScript Not Listed In Firefox Extensions

[jdnoscript]

Hey all,
Recently when opening Firefox, I noticed that the NoScript icon was missing from the toolbar. I looked in Tools > Addons > Extensions and it appears that NoScript is no longer listed in Firefox extensions. NoScript was installed right after I first downloaded and installed Firefox many years ago. Not sure what happened but any suggestions and/or info is appreciated.

[Thrawn]

What happens if you try to reinstall it?

[jdnoscript]

What happens if you try to reinstall it?

Thanks for the reply Thrawn.
I haven't attempted to reinstall NoScript as of yet. I wasn't sure if it was still installed but just wasn't showing up in the Firefox Extensions list.
Is there a way of determining if NoScript is still installed? And if it isn't, what happened to the previous NoScript installation?

[Hecuba's daughter]

nvm

[jdnoscript]

determining if NoScript is still installed?

Inspect your profile folder. http://kb.mozillazine.org/Profile_folde ... ile_folder
Extensions are saved ready to load at each session as their .xpi archives in the Extensions directory - NS index is {73a6fe31-595d-460b-a920-fcc0f8843232}.

Thanks for the reply Hecuba's daughter.
There is a NoScript folder in the Firefox profile folder. However, I'm not sure how to go about re-enabing NoScript?
Here are the contents of the folder:
chrome folder
GPL text document
install.rdf file
NoScript Licence

[therube]

> There is a NoScript folder in the Firefox profile folder.

The folder is named, extensions.
Within /extensions/ should be found the folder noted above.

> Within /extensions/ should be found the folder noted above.

And actually even that is wrong, usually.
As (usually) NoScript is not unpacked into a folder (in Tor it is different), but left as an xpi, {73a6fe31-595d-460b-a920-fcc0f8843232}.xpi.

Oh, you're on 3.6.28, so unpacking was the way they did it back then.

> how to go about re-enabing NoScript

Well, just reinstall it, should make things right.

[jdnoscript]

> There is a NoScript folder in the Firefox profile folder.

The folder is named, extensions.
Within /extensions/ should be found the folder noted above.

> Within /extensions/ should be found the folder noted above.

And actually even that is wrong, usually.
As (usually) NoScript is not unpacked into a folder (in Tor it is different), but left as an xpi, {73a6fe31-595d-460b-a920-fcc0f8843232}.xpi.

Oh, you're on 3.6.28, so unpacking was the way they did it back then.

> how to go about re-enabing NoScript

Well, just reinstall it, should make things right.

Thanks for the reply therube.
In order to reinstall NoScript with no conflicts with the contents of the current NoScript Extensions folder, would it better to start over with a new install of NoScript or is there something within the current NoScript Extensions folder to click on(ie:install.rdf) to reinstall NoScript?

[barbaz]

In order to reinstall NoScript with no conflicts with the contents of the current NoScript Extensions folder, would it better to start over with a new install of NoScript or is there something within the current NoScript Extensions folder to click on(ie:install.rdf) to reinstall NoScript?

I'd try deleting that folder, then doing a re-install at AMO or http://noscript.net/getit#devel.

[jdnoscript]

In order to reinstall NoScript with no conflicts with the contents of the current NoScript Extensions folder, would it better to start over with a new install of NoScript or is there something within the current NoScript Extensions folder to click on(ie:install.rdf) to reinstall NoScript?

I'd try deleting that folder, then doing a re-install at AMO or http://noscript.net/getit#devel.

Thanks for the reply barbaz.
After deleting the contents of the previous NoScript Extensions folder, I'll try reinstalling NoScript and see how it goes.

[Hecuba's daughter]

nvm.

[jdnoscript]

Due to an ongoing computer issue not related to Firefox/NoScript, I may have to wait on reinstalling NoScript for the moment as a System Restore could be necessary.
Thanks again to all that have replied and contributed to this thread.