为提升您的使用体验,本站正在维护,部分功能暂时无法使用。如果本站文章无法解决您的问题,您想要向社区提问的话,请到 Twitter 上的 @FirefoxSupport 或 Reddit 上的 /r/firefox 提问,我们的支持社区将会很快回复您的疑问。

搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

Lost v68 incompatible extensions

  • 3 个回答
  • 1 人有此问题
  • 2 次查看
  • 最后回复者为 stdedos

more options

I thought that updating to v68 (like all previous updates) would be 2 minutes. So I routinely accepted the update.

I have wasted 3 hours counting.

For a reason or another, "old" extensions which I use got blocked. I tried to downgrade a previous release. Apparently, here https://archive.mozilla.org/pub/thunderbird/releases/ there is none available except 8 (!!) major versions before: Dir 60.9.1/ Dir 63.0b1/ Dir 64.0b1/ Dir 64.0b2/ Dir 64.0b3/ Dir 64.0b4/ Dir 65.0b1/ Dir 65.0b2/ Dir 65.0b3/ Dir 65.0b4/ Dir 66.0b1/ Dir 66.0b2/ Dir 66.0b3/ Dir 67.0b1/ Dir 67.0b2/ Dir 67.0b3/

I tried downgrading to v67. No luck, it would not pickup my profile (and there there was this known issue of customizing "From:" address). I tried downgrading to v66. "All good", but then my extensions disappeared, and the few supported ones were "unsupported".

I panickly tried to open v68 to at least write down the list of my extensions, and try to manually download them again. They disappeared. There is none of the files https://support.mozilla.org/en-US/kb/unable-install-add-on-extension-theme-thunderbird#w_corrupt-extension-files listed here, nor .xpi files stored anywhere.

I thought that updating to v68 (like all previous updates) would be 2 minutes. So I routinely accepted the update. I have wasted 3 hours counting. For a reason or another, "old" extensions which I use got blocked. I tried to downgrade a previous release. Apparently, here https://archive.mozilla.org/pub/thunderbird/releases/ there is none available except 8 (!!) major versions before: Dir 60.9.1/ Dir 63.0b1/ Dir 64.0b1/ Dir 64.0b2/ Dir 64.0b3/ Dir 64.0b4/ Dir 65.0b1/ Dir 65.0b2/ Dir 65.0b3/ Dir 65.0b4/ Dir 66.0b1/ Dir 66.0b2/ Dir 66.0b3/ Dir 67.0b1/ Dir 67.0b2/ Dir 67.0b3/ I tried downgrading to v67. No luck, it would not pickup my profile (and there there was this known issue of customizing "From:" address). I tried downgrading to v66. "All good", but then my extensions disappeared, and the few supported ones were "unsupported". I panickly tried to open v68 to at least write down the list of my extensions, and try to manually download them again. They disappeared. There is none of the files https://support.mozilla.org/en-US/kb/unable-install-add-on-extension-theme-thunderbird#w_corrupt-extension-files listed here, nor .xpi files stored anywhere.

所有回复 (3)

more options

Perhaps look again here https://archive.mozilla.org/pub/thunderbird/releases/

I just clicked the link and the list starts with version .1 (so before the first public release) and up to version 73 beta 2 and everything in between. If you are seeing something else, that might suggest a problem with Chrome. Firefox is still a free download.

I have no idea what you have done with your chasing around, just be aware that there was no true release versions between V60 and V68. There were builds, but they were not released as Thunderbird only does a release inline with Firefox ESR versions. So they have gone 52,60 and not 68. Thunderbird next will be 70 something, 78 I think.

Were you asked to configure your accounts again? I can only hope you were as this should fix that. https://thunderbirdtweaks.blogspot.com/2019/09/i-lost-my-profilemail-on-update-to.html

more options
So they have gone 52,60 and not 68.

I suppose this should have been 'So they have gone 52,60 and now 68.'?

more options

Matt said

Perhaps look again here https://archive.mozilla.org/pub/thunderbird/releases/ I just clicked the link and the list starts with version .1 (so before the first public release) and up to version 73 beta 2 and everything in between. If you are seeing something else, that might suggest a problem with Chrome. Firefox is still a free download.

I merely copy-pasted the "relevant" part (i.e. `6\d` builds). Blame site's text-field parsing for that weird output