Daily updates from Odoo
Saturday, June 7, 2025
5 changes · 18.0
Resolved issues and error corrections
Chat windows now keep their intended size more consistently in Safari. This prevents the chat panel from becoming too narrow when the browser window has limited vertical space, improving usability for Safari users.
Original PR description
Before this commit, chat window size on Safari sometimes look off. The intended sizing is 380px in width and 9/15 ratio, with height being limited by 95vh. Safari `aspect-ratio` has strange behavior: instead of shrinking just the height from max-height, it gives too much priority on enforcing the aspect-ratio, thus the chat window becomes thinner and thinner the less vertical space there are. This commit fixes the issue by replacing the `aspect-ratio` style by a max-height that is computed with ratio and 95vh.
This fix prevents portal users from seeing an error when they click Comment to reply in the chatter. Replies now correctly show the user's avatar and keep the conversation flow working as expected.
Original PR description
Before this commit, clicking on "Comment" button in portal chatter to reply to a message leads to the following crash: ``` TypeError: Cannot read properties of null (reading 'effectiveSelf') ``` This…
Before this commit, clicking on "Comment" button in portal chatter to reply to a message leads to the following crash: ``` TypeError: Cannot read properties of null (reading 'effectiveSelf') ``` This happens because it opens the composer to reply to the message. Replying to a message should normally use the composer of thread and rely on `props.messageToReplyTo` from the `useMessageToReplyTo` hook, but portal chatter instead makes a composer linked to the message. The problem is that a message linked to a composer is actually meant to say the composer is for editing the message, and when editing the message the composer shows no avatar as this is shown by the `Message` component. Portal chatter reply to comment should display avatar of self user, but the problem is that the component `Composer` isn't directly linked to `thread`, therefore the LOC `thread.effectiveSelf` crashes in template. This commit fixes the issue by using the `message` linked to composer when no immediate thread is found in order to display the `effectiveSelf` avatar. A composer is necessarily linked to either a thread or composer, thus this ensures the `effectiveSelf` is defined.
Miscellaneous changes
When the user tries to send & print the invoice, A traceback will appear. Steps to reproduce the error: - Create a new Customer: A > Country: Netherlands > In Invoicing, Format: NLCIUS Peppol e-address (EAS): 0106 > Save - Create a new invoice > Customer: A > Confirm > Send & Print > Select NLCIUS > Send & Print Traceback: ``` TypeError: object of type 'bool' has no len() ``` https://github.com/odoo/odoo/blob/d123df0a0aacd88d89cefb51a795e7865374a46d/addons/account_edi_ubl_ci
Original PR description
When the user tries to send & print the invoice, A traceback will appear. Steps to reproduce the error: - Create a new Customer: A > Country: Netherlands > In Invoicing, Format: NLCIUS Peppol e-address (EAS): 0106 > Save - Create a new invoice > Customer: A > Confirm > Send & Print > Select NLCIUS > Send & Print Traceback: ``` TypeError: object of type 'bool' has no len() ``` https://github.com/odoo/odoo/blob/d123df0a0aacd88d89cefb51a795e7865374a46d/addons/account_edi_ubl_cii/models/account_edi_xml_ubl_bis3.py#L84-L87 Here, If ``nl_id`` is False, It results in the traceback mentioned above. opw-4840552 sentry-6653896965 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#212904
Before this commit, if the module was installed, the delivered quantity for non-rental products in a sale order paid through PoS would be doubled. opw-4805368 Forward-Port-Of: odoo/enterprise#87175
Original PR description
Before this commit, if the module was installed, the delivered quantity for non-rental products in a sale order paid through PoS would be doubled. opw-4805368 Forward-Port-Of: odoo/enterprise#87175
2 fix in this PR: ## [FIX] l10n_be_reports: 281.50 pdf use debtor where required The aim of this commit is to display the debtor info on the 281.50 pdf report instead of the sender info. Context: If there is a representative for the company, he will be set as the sender of the 281.50 and 325 instead of the company. Before this commit: The sender information was used in the pdf instead of the debtor information. After this commit: The debtor information are used as required.
Original PR description
2 fix in this PR: ## [FIX] l10n_be_reports: 281.50 pdf use debtor where required The aim of this commit is to display the debtor info on the 281.50 pdf report instead of the sender info. Context: If…
2 fix in this PR: ## [FIX] l10n_be_reports: 281.50 pdf use debtor where required The aim of this commit is to display the debtor info on the 281.50 pdf report instead of the sender info. Context: If there is a representative for the company, he will be set as the sender of the 281.50 and 325 instead of the company. Before this commit: The sender information was used in the pdf instead of the debtor information. After this commit: The debtor information are used as required. opw-4852895 ## [FIX] l10n_be_reports: 281.50 pdf add national number if available The aim of this commit is to add the national number on the 281.50 pdf if it is available. Context: The customer expects it to be filled if they filled it and it helps the authorities to identify the receiver. Before this commit: The national number wasn't added even if we had it. After this commit: The national number is added to the pdf if it is available for that partner. opw-4852895 Forward-Port-Of: odoo/enterprise#87234 Forward-Port-Of: odoo/enterprise#87109