Monday, May 5, 2025
6 changes · saas-18.2
Resolved issues and error corrections
The Discuss interface now uses softer shadows around message bubbles, reactions, attachments, and the composer. This makes the screen easier to read and less visually flat without adding heavy or distracting effects.
Original PR description
Discuss style was too flat, which makes it slightly impractical with the floating elements like message bubbles, message reactions, and composer bg. This commit fixes the issue by using a `o-shadow-sm-light` that is a `.shadow-sm` half less harsh. This makes Discuss UI less flat without making the shadows too harsh due to the big amount of this UI elements on a single screen.
This change makes the self-order product option test wait until the product page has fully loaded before selecting an option. It prevents false test failures caused by products or attributes not being ready yet, improving release stability without changing customer-facing behavior.
Original PR description
since the product page is loaded asynchronously, we need to wait for the product page to be loaded before clicking on the attribute this is to avoid the issue where the attribute is not clickable and the test fails  as you can see in the screenshot products are not loaded yet ! build_error-163168
This fix stops users from marking a message as starred while it is still being processed. It prevents a server crash that could occur when users act very quickly, improving reliability in the messaging experience.
Original PR description
If the user is fast (which happens in tours), it is possible to star a pending message, which leads to a crash on the server. This should simply not be possible. runbot-164180
Fixes an incorrect internal reference that caused the scheduled check for unfinished Dutch SBR report submissions to fail. This helps ensure submitted reports continue to have their processing status updated automatically without manual intervention.
Original PR description
When ``Process statusses of the unfinished submitted SBR reports`` cron runs,
A traceback will appear.
https://github.com/odoo/enterprise/blob/8456e61bb5ce952576c223f401330e295574f2e9/l10n_nl_reports/models/l10n_nl_reports_sbr_status_service.py#L30
Here, ``_l10n_nl_reports_get_server_root_certificate_bytes`` method is called instead of ``_l10n_nl_get_server_root_certificate_bytes`` method at https://github.com/odoo/enterprise/commit/0303a980523a884579b699198d6a3522708c69a3
Traceback:
```
File "/home/odoo/src/enterprise/l10n_nl_reports/models/l10n_nl_reports_sbr_status_service.py", line 30, in _cron_process_submission_status
serv_root_cert = ongoing_processes[0].company_id._l10n_nl_reports_get_server_root_certificate_bytes() # The root certificate is the same for all processes
AttributeError: 'res.company' object has no attribute '_l10n_nl_reports_get_server_root_certificate_bytes'
```
sentry-6572844985This fixes New Zealand invoice PDFs so they show only the correct document title when printed. It prevents confusing output where multiple possible invoice titles appeared on the same PDF.
Original PR description
### Steps to reproduce: - Install "l10n_nz" and switch company - Create an invoice - Click "Print" - On the generated PDF all possible document titles show ### Cause: This [commit](https://github.com/odoo/odoo/commit/af06243092fd194c993451ea9c165be9ec2b4188) changed the way the invoices title were displayed but it has a typo: it hasn't deleted the xpath like in `l10n_au` but added the change inside the xpath. ### Solution: Remove the xpath. opw-4710851
This fixes an issue where sending and printing a Hungarian invoice could fail if the company VAT number was not set, especially in demo NAV credential mode. Users can now complete the invoice send and print flow without encountering an unexpected error in that scenario.
Original PR description
When vat is unset in Company and user tries to send & print invoice, a traceback will appear. Steps to reproduce the error: - Install ``l10n_hu_edi`` module > Switch to ``HU Company`` - Open ``HU…
When vat is unset in Company and user tries to send & print invoice, a traceback will appear. Steps to reproduce the error: - Install ``l10n_hu_edi`` module > Switch to ``HU Company`` - Open ``HU Company`` > Unset vat field > Save - Go to Invoicing > Configuration > Settings > NAV Credentials > Mode: Demo > Save - Create a new invoice > Confirm > Send & Print > Send & Print Traceback: ``` QWebException: Error while render the template TypeError: argument of type 'bool' is not iterable Template: ir.ui.view(2872,) Path: /t/t[1]/base:taxpayerId Node: <ns0:taxpayerId xmlns:ns0="http://schemas.nav.gov.hu/OSA/3.0/base" t-out="vat[:8]"/> ``` https://github.com/odoo/odoo/blob/33b728c5917b06dd8ab46c48b160e3cf24ddc1ba/addons/l10n_hu_edi/models/res_company.py#L95-L96 For NAV Credentials(Mode: Demo), Credentials are not required. https://github.com/odoo/odoo/blob/33b728c5917b06dd8ab46c48b160e3cf24ddc1ba/addons/l10n_hu_edi/data/template_invoice.xml#L124-L131 When user unset the vat field , ``vat`` will be False. It will lead to the above traceback. sentry-6242690591 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr