Univention Bugzilla – Bug 39274
UMC - we need a way to disable the cache for a UDM syntax
Last modified: 2016-01-28 12:33:24 CET
See Ticket #2015071021000133 They added a ext. attribute to the users module with a special syntax. The syntax fills a select box with values. These values are added/removed by another UMC module. Without a udm.cache.reset() in the UMC module that is used to change the values, the select box for the ext. attribute is filled during startup (of the UDM module?) and does not get changes on the values in the same session (only after a logout/login). The problem is, that the UMC module is used on a slave and udm.cache.reset() is not available on slave (univention-management-console-module-udm). So it might be a good idea to disable the cache for a syntax (maybe as parameter on the ext. attribute).
Btw: The cache is reset after each move/remove/edit of an object and when renewing the session or module-list (e.g. after app installation, ...).
There is no cache involved in the requests for the syntax class from the named module in that ticket. The rendering of the detailpage makes a call to udm/properties which also returns the property and the syntax choices of the syntax. This call is done every time the detailpage gets rendered. There is no caching involved - neither in the backend nor in the frontend. The problem exists because the detailpage is either prerendered or rendered after closing a detailpage (in the case of a user object) and not rendered before opening a object. So you need to open the users module either afterwards or 1. open a object 2. close the object 3. open the object again. Changing this behavior would be a revert of Bug #38190.
OK