Tuesday, October 10, 2023
8 changes · master
Resolved issues and error corrections
Fixes a problem that made a button-group switch on the online shop unusable after a supporting component was removed. Customers and site visitors can now use this shop interface control as expected, reducing friction during browsing or purchasing.
Original PR description
In commit f24e61334ec1de577c6031743199e3b713290d2f the legacy rpc files have been removed. It was not initialized in this public widget making the btn-group switch unusable. task-3547424 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The self-ordering app now shows the correct price when customers choose take away instead of eat in. This prevents pricing confusion at checkout and helps restaurants apply the right fiscal pricing automatically.
Original PR description
Steps to reproduce: - Activate "Eat in / Take away" (`pos_self_ordering_takeaway`) setting. - Set the alternative fiscal position. - ISSUE: When selecting take away in the app, the take away price is not shown. FIX: The issue is because during the loading of the products, only the default price is computed. In this PR, we are now computing the take away price as well. And in the ui, depending on the choice, we are showing the correct price.
This fixes an issue where pages with a search panel would automatically jump back to the top. Users now get consistent scrolling behavior whether or not a search panel is shown, making navigation less disruptive.
Original PR description
Before this commit, if a view contained a searchPanel the scrollbar went at the top automatically; now the behavior of the scrollbar in a view with or without a searchPanel is the same. task : 3503894 with help of @Arcasias --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update adjusts how mentions are styled in Mail so they no longer unintentionally alter button styling elsewhere on the website. It also slightly improves mention readability by refining text and background contrast in light and dark themes.
Original PR description
Follow-up of https://github.com/odoo/odoo/pull/132701 `@extend` was used to reuse classnames intended for styling, such as `.btn`. However, this has the side-effect to increase specificity on these…
Follow-up of https://github.com/odoo/odoo/pull/132701 `@extend` was used to reuse classnames intended for styling, such as `.btn`. However, this has the side-effect to increase specificity on these classnames, which results in breaking style on the website where the specificity on `.btn` must not change. This commit fixes the issue by using a mixin rather than `@extend`. Since using these mixins are not equivalent, we took the opportunity to slightly improve the constrast of text color and background. Before/After (white)   Before/After (dark)  
This fixes an issue where the command menu could fail to open correctly while editing a mailing. The editor now keeps using the correct embedded document after updates, making mailing content editing more reliable.
Original PR description
Steps to reproduce: - Create new mailing (mass_mailing) - Type to '/' to open the Powerbox The `getPowerboxElement` function fails to return the correct node because `this.options.document` is no longer the iframe document after the Wysiwyg component is re-rendered. This happens because when the Wysiwyg component has its props updated, its `options.document` is overwritten by its default option (the top document). This commit makes sure that, when the editor is mounted inside an iframe, `options.document` evaluates to the iframe's document throughout the entirety of the Wysiwyg component lifecycle. task-3548120
This fixes a duplicated barcode test that was causing some nightly validation builds to fail. The change helps keep automated checks stable so releases and module updates are not delayed by a false test issue.
Original PR description
Task: 3290154 The nightly was failing during some single module build (website_sale, account, ...) https://runbot.odoo.com/web#id=25090&view_type=form&model=runbot.build.error&menu_id=405&cids=1 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fixes several issues in Odoo Studio so editing views no longer affects the user context used elsewhere, reducing unexpected behavior when loading views. It also prevents unnecessary browser-close warnings in the form editor and fixes crashes when viewing field tooltips in the list editor.
The restaurant appointment floor screen now shows appointment names consistently, regardless of whether the appointment was created online or in the back office. This avoids confusing or incorrect labels for staff managing restaurant bookings.
Original PR description
Previously, an operation was done to retrieve the appointment name. This operation was needed because when the appointment was created in the front end, a prefix was added to it. The issue is that this prefix was not added when the appointment was created in the back end. The solution to remove the prefix from the appointment name will be done by the team that is responsible of the Event module.