Univention Bugzilla – Bug 33202
Reload XML files for module meta information on "modules/list" (e.g. to update the list of ""Installed Applications")
Last modified: 2014-07-14 10:05:11 CEST
Even better: a reload when GET modules/list is called. This would lead to an updated modules list upon browser page refresh. +++ This bug was initially created as a clone of Bug #32299 +++ In case a new UMC module has been installed, the UMC server needs at least a reload to re-read the new XML meta files. It would render the handling of module installations easier if the XML files would be re-read upon login.
From Bug #32299: > It is even almost possible to do it on F5 > (get/modules/list) but I think at the moment some things may go wrong > (although probably not in >99%). > > Maybe some day we can implement it this way. Then a UMC-server restart would > only be necessary on umc-server package updates!
Even better: The frontend could reload modules/list and update the overview directly without a refresh etc.
(In reply to Alexander Kläser from comment #2) > Even better: The frontend could reload modules/list and update the overview > directly without a refresh etc. Might cause problems when the frontend hash is changed after a UMC module installation.
New modules often come from apps. Apps bring their own extended attributes, but those are cached -> UDM forms are outdated if no F5 is pressed.
Change title because it's already done on login but not on modules/list UMCP command.
(In reply to Alexander Kläser from comment #3) > (In reply to Alexander Kläser from comment #2) > > Even better: The frontend could reload modules/list and update the overview > > directly without a refresh etc. > > Might cause problems when the frontend hash is changed after a UMC module > installation. This is not anymore an issue thanks to Bug 29588.
(In reply to Alexander Kläser from comment #2) > Even better: The frontend could reload modules/list and update the overview > directly without a refresh etc. +1
Thanks to Bug #34243, this works now! *** This bug has been marked as a duplicate of bug 34243 ***