qsm-odoo
954e690edd
If an user modifies a theme value through the "Theme" tab of the website builder, a custo of the related SCSS file is made. To make a SCSS custo, the related python methods need to know for which bundle the custo is made. This is to ensure that if a file appears in multiple bundles, the custo targets the right one (amongst other things). For those automatic SCSS custo made via the website builder, the given bundle does not matter as those are custo made in variables SCSS files, which appear in all bundles, more precisely in a sub-bundle included in all bundles. The code should be more robust to leverage that fact. When the "assets_frontend" received all "assets_common" files in order to only use one unique bundle for main frontend pages with [1], it was though smart to leave that given bundle to "assets_common" although "assets_common" is not used on the frontend anymore as it would allow to not care about migration of those automatically edit SCSS files and it was also "not wrong" as you effectively cannot edit those files without impacting all bundles. It was although very wrong as editing those variables files via the SCSS editor automatically considers them as part of "assets_frontend" and not "assets_common". So editing them via the SCSS editor would create/update the files relying on the fact the related bundle is "assets_frontend" but the website builder would create/update them relying on the fact the related bundle is "assets_common". This would lead to creating two ir.asset records trying to replace the same file in the sub-bundle which is used by both those assets... and thus to make the database crash. The work done at [1] actually forgot about other things related to all this. Those will of course be fixed but they are less urgent. This commit here just fixes the SCSS edition issue described above for now. [1]: https://github.com/odoo/odoo/commit/08dcbc8f1def06476d025b110049ee596e906816 task-2994071 closes odoo/odoo#101312 X-original-commit: 15e503a841d757e622c8ef2070043b766b28bfde Signed-off-by: Romain Derie (rde) <rde@odoo.com> Signed-off-by: Quentin Smetz (qsm) <qsm@odoo.com>
Odoo
Odoo is a suite of web based open source business apps.
The main Odoo Apps include an Open Source CRM, Website Builder, eCommerce, Warehouse Management, Project Management, Billing & Accounting, Point of Sale, Human Resources, Marketing, Manufacturing, ...
Odoo Apps can be used as stand-alone applications, but they also integrate seamlessly so you get a full-featured Open Source ERP when you install several Apps.
Getting started with Odoo
For a standard installation please follow the Setup instructions from the documentation.
To learn the software, we recommend the Odoo eLearning, or Scale-up, the business game. Developers can start with the developer tutorials