If you install it from the candidate builds, then it will not
auto-install with Thunderbird. If you've done this before, then you need
to "uninstall" it, which will (hopefully?) re-activate the distribution
version of the extension.
I don't know if there is a more comfortable way. It should "just work".
Philipp
On 12/9/17 12:29 PM, Jörg Knobloch wrote:
Hi,
I've just installed TB 58 beta2 and find myself without Lightning. Is
there a way to reactivate the distribution extension or do I have to
install it from:
https://archive.mozilla.org/pub/calendar/lightning/candidates/6.0b2-candidates/build1/win32/
Users ask the same thing, they have trouble finding the right
extension for their beta installs, for example:
https://bugzilla.mozilla.org/show_bug.cgi?id=1423521
I've asked here before (enclosed), but didn't get any reply whatsoever:
http://lists.thunderbird.net/pipermail/maildev_lists.thunderbird.net/2017-September/000227.html
Jörg.
On 09/12/2017 12:34, Philipp Kewisch wrote:
If you install it from the candidate builds, then it will not
auto-install with Thunderbird. If you've done this before, then you need
to "uninstall" it, which will (hopefully?) re-activate the distribution
version of the extension.
I don't know if there is a more comfortable way. It should "just work".
Thanks for the quick reply and sorry about not being precise enough.
I of course "Remove"(d) the add on in the add-ons manager hoping that
the distribution extension would show up again as disabled, as I think
I've seen before. But that wasn't the case, neither with the 52.x I
posted about in September, nor with the beta now. After removing the
manually installed add-on there is no trace of Lightning anywhere, so
I'm forever stuck with searching for the matching version.
I believe it used to work better on Daily, but now that I switched to
Beta, it's not working as described, and for the ESR either.
I've searched the preferences to see the opt in/out preference
(mail.calendar-integration.opt-out?), that's set to false for me, so I
didn't opt out.
So what developer-level surgery is required to get "just work" to
actually work?
Jörg.
Check your prefs for extensions.installedDistroAddon.<extension-id>, for
Lightning, this is:
extensions.installedDistroAddon.{e2fda1a4-762b-4020-b5ad-a41df1933103}
Iirc, if that pref is set and the respective extension is not in the
list stored in extensions.xpiState, the installation of an addon is
prevented in XPIProvider code to prevent a once uninstalled distributed
addon from being installed again. (Unfortunately, there is not a similar
mechanism for disabled addons, which make disabled Lightning addon to
enabled on updates). So removing the pref should bring your Lightning
back on restart.
MakeMyDay
Am 09.12.2017 um 12:44 schrieb Jörg Knobloch:
On 09/12/2017 12:34, Philipp Kewisch wrote:
If you install it from the candidate builds, then it will not
auto-install with Thunderbird. If you've done this before, then you need
to "uninstall" it, which will (hopefully?) re-activate the distribution
version of the extension.
I don't know if there is a more comfortable way. It should "just work".
Thanks for the quick reply and sorry about not being precise enough.
I of course "Remove"(d) the add on in the add-ons manager hoping that
the distribution extension would show up again as disabled, as I think
I've seen before. But that wasn't the case, neither with the 52.x I
posted about in September, nor with the beta now. After removing the
manually installed add-on there is no trace of Lightning anywhere, so
I'm forever stuck with searching for the matching version.
I believe it used to work better on Daily, but now that I switched to
Beta, it's not working as described, and for the ESR either.
I've searched the preferences to see the opt in/out preference
(mail.calendar-integration.opt-out?), that's set to false for me, so I
didn't opt out.
So what developer-level surgery is required to get "just work" to
actually work?
Jörg.
On 09-12-2017 13:44, Jörg Knobloch wrote:
So what developer-level surgery is required to get "just work" to
actually work?
Try starting with -purgecaches
At least that's how I resolved it when lightning was somehow stuck on
the wrong version even though I supposedly removed it.
-Magnus