User Help for Seamonkey and Mozilla Suite
The Firefox Add-on GrabMyBooks (https://addons.mozilla.org/en-us/firefo ... src=search) is full compatible to Seamonkey, when using the converter.
Config Descriptions 1.0 is described as "Not available for SeaMonkey 2.39". It does work if the SeaMonkey version in the extension's install.rdf file is changed to 2.*.
If your AMO Browsing for SeaMonkey https://unofficialseamonkeynews.wordpress.com/2016/03/19/amo-browsing-add-on-eases-conversion-and-installation-of-ff-and-tb-add-ons/does no longer work after AMO has changed to new Style https://unofficialseamonkeynews.wordpress.com/2016/04/09/new-style-at-amo/ you sould try this solution https://unofficialseamonkeynews.wordpress.com/2016/04/09/new-style-at-amo/#comment-22.
I have converted policeman https://addons.mozilla.org/en-US/firefo ... policeman/ and popup controller https://addons.mozilla.org/en-US/firefo ... p-control/ - they both work, but there are no icons in the toolbar - so they can only be disabled in the addons, not controlled with full function. Is there a way to get the icons from the xpi - has anyone had this occur with other conversions?
I used 7-zip and toolbarbutton.js is in lib\ui - it is the same in both the seamonkey converted and the firefox original xpi. I dragged and dropped toolbarbutton.js into the seamonkey addons page, it seamonkey said it is from an unknown host and appears to be corrupt - is there a way to get the toolbarbutton.js to show and work in the seamonkey toolbar?
The Firefox Add-on Password Exporter (https://addons.mozilla.org/en-US/firefo ... d-exporter) is full compatible to Seamonkey, when using the converter.
Here's an interesting dilemma: many (or even ALL) of the converted addons will NOT work on Adrian Kalla's unofficial Seamonkey 2.44 beta builds (32bit) (64bit) produced on 5/17/2016 as they get blocked (aka. disabled) and are treated as "unsigned" as I have experienced myself. The SM 2.44 builds that he made will only accept "signed" addons from the Seamonkey addons page.
I had to use a Seamonkey version earlier than 2.44 for the converted addons to function. I've downgraded to the unofficial SM 2.43 win64 build on my Win7 x64 machine. which still supports the converted addons.
So guys, if you want to use any of the converted FF/TB addons in Seamonkey, use SM 2.43 or earlier; do not use SM 2.44 or later.
the "xpinstall.signatures.required" preference in about:config was already set to false but adrian's SM 2.44 build of 5/17/2016 did not work with it and the converted addons were still disabled, even with xpinstall.signatures.required=false already set. Downgraded to adrian's unofficial SM 2.43 release build and the xpinstall.signatures.required=false preference worked correctly and the converted addons were enabled (I guess it's a bug that adrian needs to fix before the release version of SM 2.44). Looks like there won't be an official SM 2.43 release as I found out it'll be skipped.
Edit 6/21: the unofficial release version of Adrian Kalla's SM 2.44 6/08 build has the problem fixed and the converted addons work as expected [yay ]
Thanks for letting us know.
No, really. I've been trying to keep an eye out for him to point him to this thread, but if he's already fixed it, no more need.
Fire 750, bring back 250.
Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:220.127.116.11) Gecko/20110420 SeaMonkey/2.0.14 Pinball CopyURL+ FetchTextURL FlashGot NoScript
Who is online
Users browsing this forum: No registered users and 1 guest