-
Notifications
You must be signed in to change notification settings - Fork 298
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Module system improvements #3783
Comments
It would be useful to also have the option to install multiple modules at once - There may be dependencies between custom modules which require them to remain synchronized. (it is not always possible to combine those separate modules into a single module as long as a custom module can only implement a single tab, chart etc.) |
Perhaps a better solution is to allow modules to provide multiple tabs, charts, etc.? |
That would be useful in general anyway. For modules providing a lot of (partly unrelated) functionality, it may still be better to keep them separated. |
Support additional module meta information (version ranges, changelog) so that compatibility of a module can be determined prior to a) module upgrade b) webtrees upgrade, and so that the webtree admin may decide the urgency of the module An example of this meta information handling is currently implemented in Vesta Common. (see also #3543 (comment)) |
(some of the following has been mentioned above - to summarize:)
Depending on the solution of the first issue, the second issue may not have to be addressed separately. E.g. if we introduce something like a 'container module', which contains a number of sub-modules that are treated just like separate modules within webtrees, but are installed via a single folder. That may in fact the easiest way to implement all of this. |
/modules_v?/*
to/data/modules/*
. Since webtrees can write to this folder, we will be able to install and upgrade modules from the control panel.The text was updated successfully, but these errors were encountered: