Interviewed by CNN on 13/05/2011 00:12, Justin Wood (Callek) told the world: > SeaMonkey 2.1 Release Candidate 1 is now available for free download [1] > on the SeaMonkey website. We encourage testers to get involved [2] in > discussing and reporting problems as well as further improving the product. > > SeaMonkey 2.1 RC 1 includes a total of 19 languages, including en-US and > brings our backend up to date with the latest Gecko (Firefox) releases. > > We have a targeted Release Date of May 19, 2011. >
Since it hit RC stage, I decided to give it a try. Of course, I backed up my profile first... Well, it loaded fine, it seems to be working fine, generally speaking. A number of extensions are deemed "incompatible," including a couple that really surprised me for not being already updated -- but quite a lot are working (I guess those would be the ones where the developers tagged maxversion as "2.9.9" instead of "2.0.9". We may still have some fallback from overly-optimistic developers...). Anyway, I expect that most of those extensions will trickle back into the fold over the next few weeks -- at least half officially, the other ones by hacking the maxversion after testing. Not an unexpected scenario overall. What DID surprise me was that a few extensions and themes that SHIPPED WITH 2.1.0 RC1 were also tagged as "incompatible." Those were: - Javascript Debugger - Seamonkey Default Theme (that despite the fact that Seamonkey was, in fact, USING the Default theme) - Seamonkey Modern Theme That happened in my original do-it-like-a-regular-luser-would-do-it, install-over-the-old-version attempt. So I figured that was probably because in 2.1 those were moved from the main application folder to the user's profile, or so I understand. Well, perhaps the old files were left there and were causing the problem? Let me try to fix it... So, I uninstalled 2.1.0 RC1, reinstalled 2.0.14, UNINSTALLED 2.0.14 and reinstalled 2.1.0 RC1. This time, I had the following results: - Weirdly enough, Seamonkey 2.1.0 RC1 loaded with the "Pinball" theme, which is not supposed to be compatible with 2.1.x. - Both the "Modern" and "Default" themes were available. I could switch to either one (but after I did it once, Pinball got tagged as incompatible -- as it should be, by the way). - Javascript Debugger was STILL tagged as incompatible. - My bookmarks disappeared. So, I figured that all that back-and-forth uninstall/reinstall hosed parts of my profile, including the bookmarks. Since I have a backup, no big deal, I had just to start over. I uninstalled RC1 AGAIN, but this time I restored my original profile before reinstalling 2.0.14. 2.0.14 worked fine, and all my extensions were back. I took this moment to uninstall the old "Firefox Sync" extension (which wasn't working right anyway, and would be redundant under 2.1) and switch the theme to "Default." Then I uninstalled 2.0.14. I checked the installation folder to make sure that all the files were deleted (well, except for the Plugins folder). They were. Now I installed RC1. And... the problem with "incompatible" Default and Modern themes IS BACK! I can't understand it! So... I think there's still a few bugs with the installation/upgrading process. -- MCBastos This message has been protected with the 2ROT13 algorithm. Unauthorized use will be prosecuted under the DMCA. -=-=- ... Sent from my Zuse Z1. *Added by TagZilla 0.066.2 running on Seamonkey 2.0.14 * Get it at http://xsidebar.mozdev.org/modifiedmailnews.html#tagzilla _______________________________________________ support-seamonkey mailing list [email protected] https://lists.mozilla.org/listinfo/support-seamonkey
