Closed L041S closed 1 month ago
u mean theme store ?
Sorry, addons is not the right term, I meant extensions that you install from mozilla website
the OP is talking about Extensions as he clarified, NOT about theme's
Can confirm this behaviour here as well.. on 1.0.0.a.34, also on Linux.
Oh no, i'd somehow not realised this problem til now, but yes it's true for me too: Version 1.0.0-a.37 (64-bit)
in ArchLinux KDE Plasma
.
Examples of Firefox AddOns / Extensions now out of date in my ZenBrowser:
Bookmark search plus 2
-- 2.0.129
in Floorp, of 10 August 2024, but still only 2.0.128
of 8 August 2024 in ZenDark Reader
-- 4.9.89
in Floorp, of 28 August 2024, but still only 4.9.88
of 8 August 2024 in ZenLibRedirect
-- 2.9.1
in Floorp, of 23 August 2024, but still only 2.9.0
of 8 August 2024 in ZenSidebery
-- 5.2.0.9
in Floorp, updated yesterday, but still only 5.2.0.8
of 13 August 2024 in ZenStylus
-- 1.5.51
in Floorp, of 23 August 2024, but still only 1.5.48
of 8 August 2024 in ZenWidevine Content Decryption Module provided by Google Inc
-- 4.10.2830.0
in Floorp, updated yesterday, but still only 4.10.2710.0
of 8 August 2024 in ZenZen is great, a marvellous project, & i love it despite acknowledging it's still only in alpha development phase. However, having out of date AddOns is more than only inconvenient, IMO it's also an actual security hazard.
Pls Dev, i know you now have a million enthusiastic users haranguing you for all their pet bugs & features, but i think this bug needs fixing with urgency.
The same here (1.0.0-a.39 64-bit + Windows 11)
Im looking into it 👍🏽
This should be fixed with the next update
@mauro-balades or @n7itro
Should probably be re-opened, as I still cannot update any of my extensions (many are out of date) on 1.0.1-a on Linux, clicking 'Check for updates' in the dropdown in about:addons
still says it can't find any updates when there are clearly many needed.
Unless I have to reset my profile from scratch or something to make the fix mentioned above that's supposed to be in this version work... which I'd hope could be avoided, because that'd be a pain to have to do on any sort of a regular basis.
@mauro-balades Any idea when this will finally be dealt with?
Still an issue as of 1.0.1-a.2
Oh, look! Seems that it will be resolved in the next update... https://github.com/zen-browser/desktop/commit/8f7b8506a625f242d22a85a2621ca31937088ade
Oh no. I just don't understand. I've just excitedly updated to a3, but the AOs still do not update. Yet, afaict from the Commit, the problem-solution should have been included in this build:
Oh, look! Seems that it will be resolved in the next update... 8f7b850
@guigirl42
It was supposed to be fixed 2 releases ago, hence why the issue got re-opened, the fix didn't have an affect.
That commit was from 1.0.1-a, look at the date (it says last week), 2 updates were released since then and when I got the issue re-opened is also after that commit.
That commit was from 1.0.1-a
Ah, silly me, i got myself a bit over-excited for nothing & then misunderstood; t/y.
Overall i am really pleased with today's update to 1.0.1-a.3
, but this ongoing severe bug is really spoiling the party now. :cry:
Still broken on Version 1.0.1-a.5
.😢
https://github.com/user-attachments/assets/34d212b1-403f-4bf0-b220-603f9c90702e
This issue should be fixed with https://github.com/zen-browser/desktop/commit/c9df1d8b993a1810b7b1db145f7fbe1161a302e6 and https://github.com/zen-browser/desktop/commit/576541c4f1ace0f3cfc619c41b3ac226ead5cefe .
Please let me know whether it is fixed when the next update releases (a-6
)
Please let me know whether it is fixed when the next update releases (
a-6
)
Yay yay YAY, yessss, now finally it works! I'm so pleased about this fix, as obsolete AOs was the one primary bug with Zen that really had been disturbing me for a long time. Now it's great.
Thank you to the Dev/s for this latest lovely work! 💜🤗🎉 🥳
Captchas
What happened?
It seems that browser addons won't update automatically, even if we force the update in the addons page of Zen.
Reproducible?
Version
1.0.0-a.32
What platform are you seeing the problem on?
Linux
Relevant log output
No response