qsm-odoo
f57f611dcc
This commit fixes a symptom of a more general problem which will be investigated later. Steps to reproduce: - Go to apps - Install website - Follow the configurator flow up to entering edit mode - Go to the 3rd tab of the editor panel - Change the "background" color of the third color combination and choose one of the gray colors - Go to the backend => SCSS compilation crash Basically, "frontend" color (complex) maps are available in all assets (via the variables parts that all assets have in common). The original plan was for them to be used in shared "frontend" environment like the mass_mailing application. The web_editor SCSS generation uses those variables to customize bootstrap variables... but it conflicts with the backend also customizing those. That's why there is code to "clean" what the web_editor app does when you are in the backend environment. The problem after the mentioned steps is that this "cleaning" is done too soon: gray colors are removed from maps to not alter backend grays and a web_editor css rules wants to access those gray values if configured to be used as mentioned in the steps to reproduce. This commit basically reviews what was done at [1]. In master it should be reviewed so that the web_editor probably does not touch any bootstrap variable when in a backend environment and/or some code should simply be moved to the website app only. See also web_editor.common.scss where many CSS rules depends on this and are available in the backend... while they probably should not (like the one which tried to use that gray value like explained above). But in stable, we wanted to avoid changing too many things. However, this was only a symptom of the problem: the fact that some CSS rules should not be loaded in the backend is not a critical issue. The real problem is that those CSS rules were breaking because the backend assets are actually generated using website-specific assets while the backend is supposed to be website-independant. That's probably a bug introduced with the new assets system (ir.asset) which would explain why this bug cannot be reproduced in 14.0. This will be looked into in a future update. Also, this could be backported later if judged necessary or if a traceback is actually found. Note: the forward-ported commit also includes the fix made at [2]. [1]: https://github.com/odoo/odoo/commit/70f35620babdfdf43e2c603efbf37f2cf7399240 [2]: https://github.com/odoo/odoo/commit/0fef8cfb5dc2fc0a2d9e0352ea6a473a0d7b9dbc opw-2735123 closes odoo/odoo#88968 X-original-commit: c58cee82939edb0ae0a95b5141d5c3b85dc404c0 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