Monday, January 13, 2020
6 changes · master
Resolved issues and error corrections
This update stabilizes internal automated tests for Odoo's messaging and web components by fixing timing-related failures and improving how test errors are handled. It helps maintain release quality by reducing false test failures without changing end-user features.
The website editor now correctly previews what happens when a color picker value is reset. This helps configuration rules react properly before changes are applied, reducing misleading previews for users editing pages.
Original PR description
This is important so that trigger-value works (see https://github.com/odoo/odoo/commit/e590609ebb429c6254766aa1fd8cab3ce3fd4c74)
This fixes an issue where the web interface tried to hide dialogs even if they had never been shown. It helps avoid unnecessary dialog handling and potential interface errors when closing or destroying popup windows.
Original PR description
Before this commit: all dialogs would go through the static method (OwlDialog.hide) when destroyed, regardless of wether they had been opened or not. Now, only dialogs having an 'el' property set (= having been opened) will use the 'hide' method. Task 2170705
Field labels and help text were made consistent where the same business field appears across related apps. This prevents translations from changing depending on which modules are installed, improving reliability for multilingual users.
Original PR description
if one module does ```python foo = fields.Char(string="Foo") ``` and another module inherit of the same model and does ```python foo = fields.Char(string="Bar") ``` The field can not properly be translated as the source term will change based on the installed module (and the information of which module specify an attribute is not kept on the ir.model.fields)
Several field labels and help texts were aligned so they remain consistent when multiple apps are installed. This prevents translation inconsistencies and gives users clearer, uniform wording across affected Odoo modules.
Original PR description
Following detected duplicates at odoo/odoo#42777
The unused measurement type field has been removed from unit of measure categories. This prevents errors when users create new categories and simplifies the setup process.
Original PR description
This removes the measure_type field which has become unused and causes issues when users try to create new uom categories Task-2043927 Description of the issue/feature this PR addresses: Removing the measure_type field in uom_category. Current behavior before PR: The field has to be empty when creating a new uom_category otherwise there's an error. Desired behavior after PR is merged: Deleting this field as it is unused and creates issues.