Thursday, April 24, 2025
9 changes · saas-17.4
Resolved issues and error corrections
The invoice form warning about invoices soon being sent to EDI now displays correctly. This prevents a broken-looking interface and improves clarity for users reviewing invoices.
Original PR description
### Before this commit: The warning message `Invoice will soon be sent to EDI` was not displayed correctly, resulting in a broken UI at the top of the invoice form. - **UI before fix:**  ### After this commit: The warning UI has been fixed by adding appropriate CSS classes, ensuring proper alignment and styling. - **UI after fix:**  --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Some text was not translatable in the kiosk view mode of the HR attendance app. This commit contains the regenerated pot file for these texts to be translatable. task-4526927
Original PR description
Some text was not translatable in the kiosk view mode of the HR attendance app. This commit contains the regenerated pot file for these texts to be translatable. task-4526927
Miscellaneous changes
## Issue: Survey's PDF certifications no longer display the company logo when printed by other companies' users. ## Steps to reproduce: - Create a survey with certification and ensure `Require Login` is checked; - Share the survey (copy the `Survey Link`); - In a private navigator (to ensure no login data are saved): - Log in as Demo user; - Answer the survey (using the copied link above); - Go to Surveys / Participations; - Enter the record of your test (`Contact` field shoul
Original PR description
## Issue: Survey's PDF certifications no longer display the company logo when printed by other companies' users. ## Steps to reproduce: - Create a survey with certification and ensure `Require Login`…
## Issue:
Survey's PDF certifications no longer display the company logo when printed by other companies' users.
## Steps to reproduce:
- Create a survey with certification and ensure `Require Login` is checked;
- Share the survey (copy the `Survey Link`);
- In a private navigator (to ensure no login data are saved):
- Log in as Demo user;
- Answer the survey (using the copied link above);
- Go to Surveys / Participations;
- Enter the record of your test (`Contact` field should match Demo's data);
- Open the PDF certification in the chatter.
## Cause:
The company `logo` field is a Binary field related to the partner's `image_1920`.
The retrieval method was changed to access `partner_id.image_1920` directly with `sudo`, since `sudo` does not apply when accessing the related field (`logo`) directly.
However, this change broke the standard certification printing layout, likely due to rendering issues with the direct access method.
## Fix:
Reverts logo access back to the related field `company_id.logo` to restore compatibility with certification printing.
Partial revert of commit 9b4c4ad8d1a238c6f7f4bea52d3f64016a6ff325 as already applied by JKE on Odoo.
Ensures the certification printing is still allowed for other companies' users.
opw-4266445
opw-4657294
---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Forward-Port-Of: odoo/odoo#204262Explanation: Includes previously missing supported payment methods for AsiaPay, such as Alipay (distinct from AlipayHK). Forward-Port-Of: odoo/odoo#206836
Original PR description
Explanation: Includes previously missing supported payment methods for AsiaPay, such as Alipay (distinct from AlipayHK). Forward-Port-Of: odoo/odoo#206836
We get an Access Error when trying to print check from a journal that is shared between branches. Steps: - Have a company X and a branch Y - Make a vendor payment with only X selected in company selector, set payment method as 'Checks' - Confirm and print check - Now select only branch Y in company selector - Create a vendor payment with same config as previous one - Condirm, and try to print check -> Access Error This is because we try to get the previous check number from the last payment
Original PR description
We get an Access Error when trying to print check from a journal that is shared between branches. Steps: - Have a company X and a branch Y - Make a vendor payment with only X selected in company selector, set payment method as 'Checks' - Confirm and print check - Now select only branch Y in company selector - Create a vendor payment with same config as previous one - Condirm, and try to print check -> Access Error This is because we try to get the previous check number from the last payment of the journal, but even if the record shares the same journal, we don't necessary have access to it. Fix: Get `check_number` directly from the SQL query instead of a record opw-4520708 Forward-Port-Of: odoo/odoo#206304
To reproduce: - Install both `hr_contract_salary` and `project_timesheet_holidays` - Create a public holiday for the company (ex. on May 01) - Create a employee => This create leaves for employee's company public holidays - Create a contract for that employee - Send a signing request to both employee and HR responsible - The employee sign the document - The responsible sign the document => At that time, we're going to update the contract after both parties signed the contract and f
Original PR description
To reproduce: - Install both `hr_contract_salary` and `project_timesheet_holidays` - Create a public holiday for the company (ex. on May 01) - Create a employee => This create leaves for employee's company public holidays - Create a contract for that employee - Send a signing request to both employee and HR responsible - The employee sign the document - The responsible sign the document => At that time, we're going to update the contract after both parties signed the contract and force unarchiving the employee even if it's already active. This commit ensure that unarchiving an already active employee does not create duplicate *future* public holidays. opw-4134712 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#206997
Problem --------- SPV requires the CIUS-RO xml. However, when selecting the "sending to SPV" uniquely in the move send wizard, it fails becuase it's missing the XML. Solution --------- When sending to SPV, generate the XML by default instead of doing nothing if it's not present. task-4720583 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#206828
Original PR description
Problem --------- SPV requires the CIUS-RO xml. However, when selecting the "sending to SPV" uniquely in the move send wizard, it fails becuase it's missing the XML. Solution --------- When sending to SPV, generate the XML by default instead of doing nothing if it's not present. task-4720583 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#206828
…terms Steps to reproduce: - With an ES company setup - Create 1 invoice to an EU partner with the payment term "30% Now, Balance 60 Days" - Make sure Mod349 Invoice Type is set - Go to Accounting / Reporting / Statement Reports / Tax Report - Select Tax Report (Mod 349) (ES) Issue: Amount shown on lines "Total amount of intra-community operations" and "E. Intra-community sales" is doubled. This occurs because each installment of the payment terms will be a payment term line, an
Original PR description
…terms Steps to reproduce: - With an ES company setup - Create 1 invoice to an EU partner with the payment term "30% Now, Balance 60 Days" - Make sure Mod349 Invoice Type is set - Go to Accounting / Reporting / Statement Reports / Tax Report - Select Tax Report (Mod 349) (ES) Issue: Amount shown on lines "Total amount of intra-community operations" and "E. Intra-community sales" is doubled. This occurs because each installment of the payment terms will be a payment term line, and the query retrieving values to compose MOD349 will take the whole move amount for each payment term line. opw-4637439 Forward-Port-Of: odoo/enterprise#83294 Forward-Port-Of: odoo/enterprise#82435
…arning domain The unposted entries warning was sometimes triggered unnecessarily due to the domain used for querying move not accounting for the companies accessible by the report. This led to cases where unposted entries from unrelated companies were considered, resulting in misleading warnings. This commit addresses the issue by using the company IDs returned by `get_report_company_ids()` to properly scope the domain. no-task Forward-Port-Of: odoo/enterprise#83846 Forward-Port-Of
Original PR description
…arning domain The unposted entries warning was sometimes triggered unnecessarily due to the domain used for querying move not accounting for the companies accessible by the report. This led to cases where unposted entries from unrelated companies were considered, resulting in misleading warnings. This commit addresses the issue by using the company IDs returned by `get_report_company_ids()` to properly scope the domain. no-task Forward-Port-Of: odoo/enterprise#83846 Forward-Port-Of: odoo/enterprise#83025