First of all, it you used the converter within a few recent hours then it had a serious bug sometimes producing broken js files most probably resulting in js parse errors and the extensions not running at all. If you had any problematic conversions recently try it again now since it's fixed.
smsmith wrote:I was able to covert the Change Quote and Reply Header and Quote and Compose Manager extensions. The only problem I have noticed was that the Change Quote and Reply Header extension did something weird to the reply button, which I was able to get rid of with a little CSS tweak. This button appears to have several different states that vary depending on the type of mail you are going to respond to (it a popupmenu button or something or other). I only really need the reply button to be a _reply_ button, so losing this extra function doesn't bother me.
This extension seems to be ancient - still for TB versions that had the traditional reply buttons before their own "australis" revolution a couple of years ago so even in TB the drop down options don't appear. But it's not critical and good to know about the css fix!
LoudNoise wrote:Why doesn't someone running SeaMonkey download an older version of WOT, convert it and see what happens when you click to have it update? My main concern isn't that it will update but rather what happens when or if it tries. For example, does the other older one still get overwritten? Does SeaMonkey die a horrible death when it tries? Does AMO turn into a gang of fluffy, but savage, bunnies in its confusion (which would be fun to watch)?
I tried this with WOT and Text Link older versions. In both cases SM didn't find any updates when I ran "find updates" so nothing happened. Some check is in place, I'm not sure what it is but I suppose it's appversion number.
But even if SM found the update for some reason and installed it then I wouldn't predict any disaster - you would simply end up with an unmodded version installed and would most probably behave the same as if you had only tweaked install.rdf. Without tweaks in chrome.manifest most add-ons simply don't even start and those which don't need those tweaks may run or run to some extent with some js errors, etc. If this happened then the older one would certainly be overwritten because the ID is the same.
Scarlettrunner20 wrote:Any chance in getting Extended Status Bar working on SeaMonkey?
https://addons.mozilla.org/en-US/firefo ... statusbar/It's very similar to the status bar in Opera 12x and earlier. I love it because it shows me the page load speed and time. When I installed it using your converter tool and then went to a new site on a new tab I did not see the page load size, speed and time appear in the status bar.
I'm afraid this one is too complex and would require manual modifications to get it to work.