Vesta modules

[hartenthaler]

When upgrading any Vesta module, all Vesta modules become upgraded. That is ok.

But the user interface still offers the option to upgrade other Vesta modules. Last week, I unnecessarily upgraded all Vesta modules (each about 1.000 files) - one after another. That was too much. I would expect that all the Vesta modules are grouped together and that there is only one upgrade button.

[Jefferson49]

But the user interface still offers the option to upgrade other Vesta modules

I applied some optimization, since generating the list of updates with a lot of GitHub calls takes a long time. Therefore, the user can decide whether to reload the page or to continue without reload. If reloading, all the modules are updated and the newly installed vesta modules will be detected. This is your expected behavior. If deciding to continue without reloading, it is much faster, but has the pitfall to load modules, which are already loaded. This can also happen to other modules - not only for Vesta.

From the overall view, continuing fast without reloading is an important feature. I do not want to remove it. I hope it is accetable that the user can decide. Maybe, I could offer a configuration.

[hartenthaler]

Maybe making "weiter mit Neuladen" as standard and "weiter" as an alternative Option could help unexperienced users as me. Or even better: if a vesta module was upgraded: offer only "weiter mit Neuladen".

[Jefferson49]

Or even better: if a vesta module was upgraded: offer only "weiter mit Neuladen".

Good idea! I will try if I can manage to implement this.