Tuesday, October 31, 2023
15 changes · 17.0
Resolved issues and error corrections
The stock picking screen no longer shows advanced forecast information by default. This keeps the view simpler for everyday warehouse users while still preserving the underlying functionality for cases where it is needed.
Original PR description
It adds advanced data on the picking view. It's not needed by default so we hide it Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Opening a discussion channel that no longer exists now fails gracefully instead of causing an error. This helps users stay in the messaging area without disruption when links or channel data are outdated.
This fix restores proper formatting for error messages shown when sending electronic invoices. Users now see readable errors both in pop-up alerts and in the document chatter, reducing confusion during invoice processing.
Original PR description
…sage formatting With https://github.com/odoo/odoo/pull/139311, we broke the formatting of errors. We need to handle two formats: - one for the raised Error, likely formatted with \n - one for the chatter, likely formatted with html ### Before the fix  ### After the fix  
The Put In Pack button on stock picking forms is now shown on the right and uses a secondary visual style. This makes the action less visually dominant while keeping it available in a more appropriate place for warehouse users.
Original PR description
Main changes:
Change the style and postion of the Put In Pack Button on the stock.picking form view
Before:
Button is aligned on the left and has the style primary
After:
Button is aligned on the right and has the style secondary
---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-prManufacturing order lists now hide duration fields that are not needed by default, reducing visual clutter for users. The bill of materials overview also hides component availability unless opened from the manufacturing forecast, so teams see that detail only where it is most relevant.
Original PR description
This commit fixes: - hide `read_duration` and `expected_duration` in MO list view. - hide `component availability` byt default in bom overview, unless if coming from mrp forecast. task-3547356 Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fixes a small visual issue where disabled arrow-shaped buttons appeared darker when hovered. Users now see a more consistent disabled state, reducing visual confusion in the interface.
Original PR description
This commit fixes an issue where the interior of the arrow of the disabled `o_arrow_button` was darker on hover task-3573542 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Fixed an issue where images from the Images Wall could keep a hover overlay when opened in the slideshow. This keeps website image galleries looking clean and consistent for visitors after editing.
Original PR description
Steps to reproduce the bug: - In Website edit mode, drag and drop an `Images Wall` snippet onto the page. - Click on the first image of this snippet. - In the "Animation" options of the image, select "On Hover". - Save the page. - Click on the first image of the `Images Wall` snippet. - Bug: The image in the slideshow still has the overlay that appeared due to the hover effect. This commit fixes this issue by resetting images to their original source in the slideshow. task-3562305
This update corrects how formatted content is combined in mass mailing lists, preserving the intended markup instead of accidentally stripping it. It helps ensure mailing-related content is rendered consistently without changing user workflows.
Original PR description
- using a string to join `Markup`s is useless, that just strips out the `Markup` - the entire toplevel `Markup` can be formatted in one shot
Payment summaries with long text now wrap properly and use adjusted sizing to avoid layout problems. This helps customers and portal users read payment information clearly without broken or overflowing page content.
Original PR description
Prior to this commit, the content of the payment summary did not include line breaks when the text was too long, creating layout issue. To fix that, this commit adapts the font size and forces the text to break. task-3576830 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update adds test coverage to ensure invalid pivot spreadsheet expressions are detected correctly. It helps reduce the risk of spreadsheet errors reaching users by guarding against a previously discussed edge case.
Original PR description
See https://github.com/odoo/odoo/pull/139871#discussion_r1377199846 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Barcode scans for valid command-style actions no longer show an unnecessary warning when another module handles the action. This avoids confusing users who successfully scan operational barcodes, such as stock menu shortcuts, but previously still saw an alert.
Original PR description
Before this commit, when a barcode starting with "O-CMD." is scanned, the barcode handler checks if it knows a command and either calls it if it exists, either displays a notification. The issue with the notification is that some modules can use barcodes starting with "O-CMD." (`stock_barcode` with "O-CMD.MAIN-MENU" for example), meaning scanning one of those will display a warning notification even if the action linked to the barcode is correctly called. Since there is no notification in case a scanned "O-BTN." does nothing, it seems not so crazy to make the CMD part to not display a notification in case there is no command for the scanned barcode.
Removing all social links from the website header no longer triggers an error. This keeps website editing stable when businesses choose not to display social media links.
Original PR description
Prior to this commit, when you removed all social links in the header, there was an error. This is because `website.header_social_links_no_color` targets selectors that don't exist in this situation. This commit adapts this template so that it works even if we remove all social links. task-3572219 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The checkout page now works even when no payment provider supports express checkout. This prevents customers from seeing a broken checkout form in stores where express checkout is unavailable or not configured.
Original PR description
The express checkout form template could not be rendered when no payment provider supporting express checkout was passed.
This update fixes a bug where the return button was incorrectly appearing in the barcode scanning interface in two situations: when viewing picking details and when processing completed manufacturing orders. The button now only displays when it should be available, improving the user experience and reducing confusion.
Original PR description
Fixes 2 cases of the return button in barcode showing when it shouldn't. - when in the "info" view of the picking then the button was showing on top of the chatter when it shouldn't show in this view at all - in done manufacturing orders Note that a getter isn't added to the JS to handle whether or not the button should be shown because mrp_model extends the picking_model and batch pickings do not currently offer the "Return" option in the backend, so it didn't seem necessary to create a getter to only override it to be "False" for mrp_model only. Forward-Port-Of: odoo/enterprise#49824
This fix eliminates false warning notifications that appeared when scanning certain barcodes used by the stock barcode system. Previously, valid barcode commands were triggering warning messages even though they were working correctly. The update ensures that recognized barcode commands no longer display unnecessary alerts to users.
Original PR description
Before this commit, when a barcode starting with "O-CMD." is scanned, the barcode handler checks if it knows a command and either calls it if it exists, either displays a notification if not. The issue with the notification is that some modules can use barcodes starting with "O-CMD." (`stock_barcode` with "O-CMD.MAIN-MENU" for example), meaning scanning one of those will display a warning notification even if the action linked to the barcode is correctly called. This commit adds an empty function for each "O-CMD." barcode used by `stock_barcode` to let `barcodeGenericHandlers` know those commands exist and should not trigger a warning.