Thursday, November 9, 2023
6 changes · 17.0
Resolved issues and error corrections
This fix allows interface components to be prepared even when their related page widget is not yet visible or attached. It helps prevent display issues during page loading or dynamic content setup, improving reliability for users.
Original PR description
Before this commit, a component couldn't be mounted on a public widget that wasn't yet attached in the dom.
Miscellaneous changes
Enterprise PR: odoo/enterprise#49584 Task link: http://www.odoo.com/web#id=3569752&model=project.task task-3569752 Forward-Port-Of: odoo/odoo#141554 Forward-Port-Of: odoo/odoo#139912
Original PR description
Enterprise PR: odoo/enterprise#49584 Task link: http://www.odoo.com/web#id=3569752&model=project.task task-3569752 Forward-Port-Of: odoo/odoo#141554 Forward-Port-Of: odoo/odoo#139912
This PR fixes the missing caret in some of the selection fields inside the settings. It is not possible to fix it another way than adding a `:not` targeting the settings `formView`, because the `formView` css rule is overriding any css in settings. The caret was also hidden in the `datepicker` field. This PR also change the `$-down-arrow` variable to a global one, `$o-caret-down`. This issue was discovered while fixing the new milk version of Odoo, but this PR target 16.0 because t
Original PR description
This PR fixes the missing caret in some of the selection fields inside the settings. It is not possible to fix it another way than adding a `:not` targeting the settings `formView`, because the `formView` css rule is overriding any css in settings. The caret was also hidden in the `datepicker` field. This PR also change the `$-down-arrow` variable to a global one, `$o-caret-down`. This issue was discovered while fixing the new milk version of Odoo, but this PR target 16.0 because the issue appeared in this version, but the task is a part of the 16.3 Milk fixes. task-3451370 Related to task-3326263 Forward-Port-Of: odoo/odoo#140570 Forward-Port-Of: odoo/odoo#130490
Forward-Port-Of: odoo/odoo#141458
Original PR description
Forward-Port-Of: odoo/odoo#141458
Setting a default value for an integer that is greater than that allowed by a 32-bit integer raises an error when we save a new record so it isn't clear that the issue comes from the default value Steps to reproduce: 1. Install Contacts and Studio 2. Go to Contacts and open any contact 3. Toggle Studio and add an integer field in the view 4. In the Studio sidebar, set the default value to 3 000 000 000 5. Save and close Studio 6. Create a new contact, give it a name and try to save the
Original PR description
Setting a default value for an integer that is greater than that allowed by a 32-bit integer raises an error when we save a new record so it isn't clear that the issue comes from the default value Steps to reproduce: 1. Install Contacts and Studio 2. Go to Contacts and open any contact 3. Toggle Studio and add an integer field in the view 4. In the Studio sidebar, set the default value to 3 000 000 000 5. Save and close Studio 6. Create a new contact, give it a name and try to save the record 7. An error is thrown Solution: Raise an error if we set an integer field's default value out of the bounds of a 32-bit integer opw-3360160 Forward-Port-Of: odoo/odoo#139189
Steps to reproduce: - Install website_sale_loyalty module and all dependencies. - Create a promo code with amount limit, like 1000$. - Now add one product to the cart that doesn't reach the limit and try the promo code. Issue: The `get_promo_code_error()` is being calle more than once, and when we try to access the `error_promo_code` from the session, it's empty as we have deleted it in the first run. Solution: Having a template to manage and store the message directly into the
Original PR description
Steps to reproduce: - Install website_sale_loyalty module and all dependencies. - Create a promo code with amount limit, like 1000$. - Now add one product to the cart that doesn't reach the limit and try the promo code. Issue: The `get_promo_code_error()` is being calle more than once, and when we try to access the `error_promo_code` from the session, it's empty as we have deleted it in the first run. Solution: Having a template to manage and store the message directly into the cart will avoid us to lose the message before we can display it. opw-3262476 Forward-Port-Of: odoo/odoo#128480 Forward-Port-Of: odoo/odoo#124701