erp5_officejs, erp5_web_renderjs_ui: add setVolatileSetting
-
Maintainer
I do not understand advantage of using in this context. Especially when there are two layers (one part stored in erp5_launcher and the other part in setting gadget)
-
Maintainer
@cedric.leninivin , please correct me if i'm wrong. There are 2 way to store gadget persistent settings:
- erp5_launher
- setting gadget.
In my case on d1 server for default is 1-st way is used. For each way of store the Volatile Settings saving/getting should be realized. Otherwise the portal type (as example) will be the same for all gadgets.
You can change the code as you think it's correct.
-
Maintainer
Maybe I was unclear. To store settings, erp5_launcher use the gadget_setting which also implement the setVolatileSetting. For consistency setVolatileSetting of erp5_launcher should also use setVolatileSetting from gadget_setting.
-
Maintainer
I've deleted this commit. i made it as i thought the global setting gadget had been not working, but i just hadn't understood correctly how it had to work. For my testing purposes i have made subdomains for each application, so now i have the similar environment as Nexedi's production, and as a result i don't need this patch too.