Like subject says, when updating extensions, i go to the extensions page, click re-check all extensions, open in a new tab the details page of the extension that is not up to date, download it, close the tab, open in a new tab the disable page and disable it.
So as you can see it's quite a few steps to update an extension, so it would be nice to have a step less and disable it on the details page.
I don't need to "get a life." I'm a Gamer, I have lots of lives!
Q: Whats a hash and a root password?
A: hash gets you high, root password gives you god powers, combine the 2 and you are invincible.
Ok, but 3.3.a1 is still a long way of release right? (policy page says December 2017, don't think they are gonna make that, on the other hand, milestone page says 83% done, maybe enough for a alpha release)
I would love to see an notification/email that there is a new version for a extension and update it through acp like for example wordpress does.
I don't need to "get a life." I'm a Gamer, I have lots of lives!
Q: Whats a hash and a root password?
A: hash gets you high, root password gives you god powers, combine the 2 and you are invincible.
Ok, but 3.3.a1 is still a long way of release right? (
But still a lot nearer than having an idea incorporated into the core
David Remember: You only know what you know and - you don't know what you don't know! My CDB Contributions | How to install an extension I will not be accepting translations for any of my extensions in Github - please post any translations in the appropriate topic. No support requests via PM or email as they will be ignored
true, oh well, it was a good idea if it gets defaulted in 3.3 so eventually it will be incorporated into the core then
I don't need to "get a life." I'm a Gamer, I have lots of lives!
Q: Whats a hash and a root password?
A: hash gets you high, root password gives you god powers, combine the 2 and you are invincible.