Can any of you who have "updated" to 157 noticed if any of your
extensions were disabled?
When that happens to me, it's very frustrating to have to find kludges
and alternatives to make things work the way it did before a major
update like this one.
It's down to individual extensions to declare what range of versions
they work with
157 hasn't shown up for me yet (just 156.0.1)
You can use the add-on checker compatibility add-on
<https://addons.thunderbird.net/en-GB/thunderbird/addon/addon-compatibility-check/?src=search>
On Wed, 30 Sep 2026 13:55:31 +0100, Andy Burns wrote:
It's down to individual extensions to declare what range of versions
they work with
157 hasn't shown up for me yet (just 156.0.1)
You can use the add-on checker compatibility add-on
<https://addons.thunderbird.net/en-GB/thunderbird/addon/addon-compatibility-check/?src=search>
Or... if Mozilla have added the extension to their blacklist.
"John C." wrote:
Can any of you who have "updated" to 157 noticed if any of your
extensions were disabled?
When that happens to me, it's very frustrating to have to find kludges
and alternatives to make things work the way it did before a major
update like this one.
It's down to individual extensions to declare what range of versions
they work with
157 hasn't shown up for me yet (just 156.0.1)
You can use the add-on checker compatibility add-on
<https://addons.thunderbird.net/en-GB/thunderbird/addon/addon- compatibility-check/?src=search>
Can any of you who have "updated" to 157 noticed if any of your
extensions were disabled?
When that happens to me, it's very frustrating to have to find kludges
and alternatives to make things work the way it did before a major
update like this one.
| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 74 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 01:08:11 |
| Calls: | 1,194 |
| Files: | 1,352 |
| Messages: | 290,880 |