Saturday, June 7, 2025
4 changes · saas-18.1
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, 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 compu
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. Forward-Port-Of: odoo/odoo#213419
Steps to reproduce ================== - Open the JS unit test page - Enable the "Mid-tier mobile" option in the devtools in order to have a 4X CPU slowdown - Run the test "url should not use the record last updated date when the field is related" => It fails Cause of the issue ================== We check that a timestamp generated after a patchDate is at most 100ms after. When we have a high CPU usage or a slow CPU, it can happen that the value is more than 100ms after. Soluti
Original PR description
Steps to reproduce ================== - Open the JS unit test page - Enable the "Mid-tier mobile" option in the devtools in order to have a 4X CPU slowdown - Run the test "url should not use the record last updated date when the field is related" => It fails Cause of the issue ================== We check that a timestamp generated after a patchDate is at most 100ms after. When we have a high CPU usage or a slow CPU, it can happen that the value is more than 100ms after. Solution ======== The test simply needs to check that the date is either the `2017-02-06` or the `2017-02-09`. We can use the luxon function `a.hasSame(b, "days")` runbot-115469 Forward-Port-Of: odoo/odoo#213237 Forward-Port-Of: odoo/odoo#212515
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