Confirm
396
edits
Changes
→ChatZilla woes: bug filed
It's confusing that most of the SM 2.0.14 program files were dated 2011-04-30 03:57PM , and the new 2.2b1 version went back in time to 2010-01-01 1:00AM. I confirmed by looking at Windows installer ZIP files, see bug.
== {{Bug|666492}} - sometimes SM upgrade leaves ChatZilla woes disabled ==
Startup warned the following addons are incompatible: ChatZilla 0.97 (roughly), I clicked to find an update and it reported No Compatible Add-ons Found.
Then started fine. about:addons > Extensions reports
I clicked Remove in about:addons, the directory still there. Upon restart, the extension is in a new trash subfolder and gone from about:addons.
KaiRo on chat suggested "what should help is if you remove the copy from about:addons, then go to about:config, and reset extensions.lastAppVersion and restart SeaMonkey"
That worked great for me, but not for others on IRC.
I noticed the built-in CZ has different em:maxversion than the CZ on addons.mozilla.org , yet they have identical em:versions!? See the bug.
=== BUG: http://chatzilla.hacksrus.com/faq/ is out-of-date ===
There are no chrome/chatzilla* or component/chatzilla* files, not even in omnijar.
In SM 2.2 (and 2.1?), the extension is in SeaMonkey/distribution/extensions/{59c81df5-4b7a-477b-912d-4e0fdf64e5f2}.xpi
== Unrelated: jar: file type ==
