Use case: When the server is restarted, the python is updated, but some users may have an ongoing session in a browser tab This may lead to code being unsynchronized and ultimately to some odd bugs. Purpose: When we are in such a case, that is, the assets were recomputed after a update of the code and a restart of the server by the request of another user, notify connected users that assets have changed. Then propose them to reload the page. Known caveats: - This is not a developer's feature. Since assets computing is ORM cached, they have limited opportunities to rebuild. Namely, the feature won't trigger each time the JS has changed, rather, it will when JS has changed AND the cache has been reset somehow (e.g. when the server is restarted). - This not a portal/website feature either, but only in backend. Business clients won't be notified that the JS has changed. - While requests debug=assets do trigger a recomputing of the *components* of bundles, they do not save a bundle This means that the requests that sends the notification cannot be debug=assets. Task 2034462 closes odoo/odoo#39875 Signed-off-by: Mathieu Duckerts-Antoine <Polymorphe57@users.noreply.github.com>
* add a `raw` computed field, though only update some of base to use it (addons for which that makes sense can be migrated progressively) * avoid working with base64 data when it's possible to work with the actual data * improve datas (base64 encoded content): should depend on bin_size closes odoo/odoo#47212 Signed-off-by: Raphael Collet (rco) <rco@openerp.com>
Since we now use native promises, the code in charge of alerting the user of bundle compilation errors was opening both an alert and a dialog (fwp of https://github.com/odoo/odoo/pull/46437). In 13.0, the mention fwp is not enough. On the website, the JS is also lazy loaded now so we need to wait for that lazy loading before being able to open a modal. The whole alerting code should be improved to not be defined in python. Fixes https://github.com/odoo/odoo/issues/45447 closes odoo/odoo#46482 X-original-commit: d5a2469b1edd0d22b366b44086d08c6f0b2247b2 Signed-off-by: Quentin Smetz (qsm) <qsm@odoo.com>
Fine-tunning of 42eec88e5da164e4930c48113109f2c8d4b73da3 Before this commit, the assets were not found when the user is connected in mode debug assets in a multi-website and multi-company. This occurs because the attachments (assets) were created only for the first website accessed, and cannot be loaded when trying to access the second website. Now, the attachments are created for each website accessed and can be loaded withtout problems. closes odoo/odoo#42593 X-original-commit: 95077a8cdd9f2cd99c2ef85bdf7ca5d58e006b71 Signed-off-by: Jorge Pinna Puissant (jpp) <jpp@odoo.com>
Assets bundle creation will try to find previous version of assets and unlink them. This needs to invalidate ormcache to notify other workers. Since assets are never commited during test, assets will be generate at each request if request is not commited (cursor closed) whtch is the case with 404. Invalidating the orm cache only when a previous attachement was existing will help to mitigate the problem, and slightly improve HTTPCases test speed. closes odoo/odoo#38979 X-original-commit: d4d63549e1b31e3f3c97a2b91155023dbac62847 Signed-off-by: Xavier Dollé (xdo) <xdo@odoo.com>
Before this commit, the assets were not found when the user is connected in mode debug assets in a multi-website and multi-company. This occurs because the attachments (assets) were created with the number of the first website accessed, and cannot be loaded when trying to access the second website. The website_id is added in the creation of the views see: 092870270eb059bc848f82684a4d1d4b84758e30 Now, the attachments are created without the website number and is shared between all the websites. opw-2076768 closes odoo/odoo#37789 X-original-commit: 42eec88e5da164e4930c48113109f2c8d4b73da3 Signed-off-by: Jorge Pinna Puissant (jpp) <jpp@odoo.com>
closes odoo/odoo#37372 Signed-off-by: Christophe Simonis <chs@odoo.com>
closes odoo/odoo#37314 Signed-off-by: Christophe Simonis <chs@odoo.com>
As explained here: https://github.com/odoo/odoo/commit/770aec399c4e6e29cfc5854318cbda19a605315d#diff-3d7991d8bc534e0372f0bd9b4f9165a7R424 we have to post-process the generated css to add some vendor prefixes. The flex-wrap property was not post-processed yet. Related to opw-2045424 closes odoo/odoo#37283 X-original-commit: 8c251ec835edb04821cd45087f92756be3d5731f Signed-off-by: Quentin Smetz (qsm) <qsm@odoo.com>