Repository navigation
Vesta Module: will only install all or remove all module #75
Description
Just noticed that an upgrade for the Vesta modules was available (2.2.6.1.0).
In the CMM, the various Vesta modules are listed individually. However, when I update one of them, all Vesta modules are installed, including those I am not using and that were not previously installed. Likewise, when I remove one of the modules, all Vesta modules are removed.
Since the Vesta modules are listed individually in the CMM, this is not the behavior I was expecting.
Is this a bug or normal behaviour?
Activity
Jefferson49 commentedon Jul 27, 2026
Yes, it is normal behavior. The reason is that the author of Vesta only provides one single ZIP file as download, which includes all Vesta modules alltogather.
Some users might want to get information about the different Vesta modules, which are also shown separately in the webtrees control panel. In Custom Module Manager (CMM), the module information can be selected for each of the modules, e.g. version, GitHub issues, and so on. From the updated versions in CMM, it is possible to see, which of the Vesta modules are updated.
Maybe, I will think about adding a check question before starting the update. However, the user cannot go for a different decision - than to install all modules - anyway.
SnarfW commentedon Jul 28, 2026
I did not expect that updating a single module would download all modules, or that removing one module would delete them all. An additional warning would therefore have been helpful.
If the intended behavior is to always install or update all Vesta modules, I personally don't see why they are listed individually. After the first installation or update, all modules will always be on the same version anyway. Wouldn't it make more sense to have a single Install/Update All option instead?
I'm not a programmer, so this may not be feasible, but would it be possible to download the ZIP package and only install the selected Vesta module/folder
Jefferson49 commentedon Jul 28, 2026
I understand your point; and maybe, the installation warning might be a suitable approach.
Like described above, everywhere else in webtrees the individual modules can be seen:
Therefore, it would be confusing for the user if it is different in Custom Module Manager:
Some of the environment around the modules is also directly linked to the single modules:
With some effort, it might be possible. However, the Vesta author does not support it, because the Vesta ZIP packages contain dependencies; for example to some common Vesta modules. If the dependent modules are not installed, the single modules wont work.
SnarfW commentedon Jul 30, 2026
Actually this why I expected that only the selected Vesta module would be installed...
Feel free to close this issue. I won't make the same mistake again. However, I think there should at least be a warning just before the installation starts.