You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Could a version of requestpolicy be made, supporting all versions of seamonkey 2.53 ?
The 0.5.27 version only gives a grey flag for all sites in seamonkey 2.53.16.
For versions <= seamonkey 2.53.16, the 0.5.28.1-signed.1-signed Info worked well.
However, now almost all content is blocked in seamonkey 2.53.17 as soon as requestpolicy the 0.5.28.1- is enabled, with no option to switch it on. RequestPolicy/requestpolicy#476
So, preferably, a newer RequestPolicy could be made working.
I don't know how to debug plugins, but I'm willing to learn.
The text was updated successfully, but these errors were encountered:
You can use 7Zip or similar to look inside the .xpi file. Find the file components\requestpolicyService.js, and edit it, you can use notepad, wordpad or similar. Search for the 2 instances of "nsIPrefBranch2" and change them to "nsIPrefBranch" so they look like this (the "// fix" indicates the original commented out line):
then save the file back inside the .xpi. Uninstall the extension from seamonkey, restart, install the edited version, restart again, and you should be back in business. Or if you want to trust some random stranger on the internet you can use requestpolicy_v05_legacy-0.5.32-fx+sm.4sm2_46.edited.xpi.zip
Could a version of requestpolicy be made, supporting all versions of seamonkey 2.53 ?
The 0.5.27 version only gives a grey flag for all sites in seamonkey 2.53.16.
For versions <= seamonkey 2.53.16, the 0.5.28.1-signed.1-signed Info worked well.
However, now almost all content is blocked in seamonkey 2.53.17 as soon as requestpolicy the 0.5.28.1- is enabled, with no option to switch it on.
RequestPolicy/requestpolicy#476
So, preferably, a newer RequestPolicy could be made working.
I don't know how to debug plugins, but I'm willing to learn.
The text was updated successfully, but these errors were encountered: