Tuesday, May 27, 2025
18 changes · 17.0
Resolved issues and error corrections
Website pages now keep a solid white page background even if the body color is set to transparent. This prevents hidden fallback content from showing through, keeping pages like Contact Us visually clean for visitors.
Original PR description
Steps to reproduce: - Enter Website edit mode. - Click on the Theme tab. - Click the 4th colorpicker in the colors options to change the body background color. - Choose a transparent color. - Save and exit edit mode. - Navigate to the "Contact Us" page. - Issue: The fallback iframe is visible beneath the website iframe. To prevent this, this commit adds a white background to the website's HTML element, so the fallback iframe will never be visible. task-4816245
The TDS payment wizard no longer shows a warning when the tax calculation base is higher than the payment amount. This avoids unnecessary confusion for users because that situation can be valid in Indian withholding tax workflows.
Original PR description
Before this commit: - A warning was shown in the TDS payment wizard when the base amount used for TDS calculation was greater than the amount being paid. - However, this warning was misleading, as the TDS base amount can exceed the paid amount. After this commit: - The warning has been removed from the TDS payment wizard. task-4787113
This fix prevents an error when setting up or changing mail activity plans by ensuring the needed model information is available. It improves reliability for users configuring planned activities, with no expected change to normal workflows beyond avoiding the crash.
Original PR description
Trigger an onchange requiring res_model_id to be returned. Before this commit, there was an error because the dependency field "res_model" was False and injected into a function that required it not to be. After this commit, there is no crash. runbot-error-223466 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 fix adds coverage to ensure manufacturing work order costs are calculated correctly when multiple employees work on the same order. It helps prevent the same working time from being counted more than once, improving cost accuracy for production reporting.
Original PR description
Test coverage for community-side diff about calculating a workcenter's cost in a way that omits counting duration within a working interval that was previously counted. opw-4430375
The follow-up report now hides the company field from view. This removes an unnecessary field from the screen, making the report cleaner and reducing possible confusion for users.
Original PR description
This commit make the company field on the followup report invisible. opw-46693397
Miscellaneous changes
Added FI and LT, and updated extra terms for others. Related to https://github.com/odoo/enterprise/pull/86440 Forward-Port-Of: odoo/odoo#211714
Original PR description
Added FI and LT, and updated extra terms for others. Related to https://github.com/odoo/enterprise/pull/86440 Forward-Port-Of: odoo/odoo#211714
Requested by @cima-odoo
Original PR description
Requested by @cima-odoo
Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: This PR separates the schedule method from scheduleActivity method, so that it can be overridden. Needed to be done to trigger reloadParentView method for documents.document. See here: odoo-dev/enterprise@14c7a95 Task - 3786861 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#160069
Original PR description
Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: This PR separates the schedule method from scheduleActivity method, so that it can be overridden. Needed to be done to trigger reloadParentView method for documents.document. See here: odoo-dev/enterprise@14c7a95 Task - 3786861 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#160069
Manual backport of 207974 Forward-Port-Of: odoo/odoo#207975
Original PR description
Manual backport of 207974 Forward-Port-Of: odoo/odoo#207975
When a numeric field (float, integer, monetary) had a value of 0, it was evaluated to an empty string when called through an `odoo.list` formula. Task: 4805167 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 Forward-Port-Of: odoo/odoo#210757
Original PR description
When a numeric field (float, integer, monetary) had a value of 0, it was evaluated to an empty string when called through an `odoo.list` formula. Task: 4805167 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 Forward-Port-Of: odoo/odoo#210757
*: l10n_cl, l10n_nz, sale_expense --- Description of the issue this commit addresses: [This PR](https://github.com/odoo/odoo/pull/211150) has brought our attention to some files that were in the codebase but not included in their module's manifest. Therefore they are useless as is and can either be deleted or need to be put in the manifest. --- Desired behavior after this commit is merged: Unused useless files have been removed from the codebase. Unused useful files have been
Original PR description
*: l10n_cl, l10n_nz, sale_expense --- Description of the issue this commit addresses: [This PR](https://github.com/odoo/odoo/pull/211150) has brought our attention to some files that were in the codebase but not included in their module's manifest. Therefore they are useless as is and can either be deleted or need to be put in the manifest. --- Desired behavior after this commit is merged: Unused useless files have been removed from the codebase. Unused useful files have been added to their module's manifest. --- task-4822341 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#211609
All instances of "_t" in emoji shortcodes were incorrectly replaced with "_lt" (e.g., "christmas_tree" became "christmas_ltree"). This commit restores the proper spelling. Forward-Port-Of: odoo/odoo#211741
Original PR description
All instances of "_t" in emoji shortcodes were incorrectly replaced with "_lt" (e.g., "christmas_tree" became "christmas_ltree"). This commit restores the proper spelling. Forward-Port-Of: odoo/odoo#211741
### Description of the issue/feature this PR addresses: When an event is synced with an external calendar (Google/ Microsoft), the external calendar is responsible for sending reminders, and Odoo should not send any additional reminders. However, the current implementation does not properly handle this, with the default crone job running daily sending email reminders up to one day late. ### Current behavior before PR: Although the current implementation ensures the crone is not t
Original PR description
### Description of the issue/feature this PR addresses: When an event is synced with an external calendar (Google/ Microsoft), the external calendar is responsible for sending reminders, and Odoo…
### Description of the issue/feature this PR addresses: When an event is synced with an external calendar (Google/ Microsoft), the external calendar is responsible for sending reminders, and Odoo should not send any additional reminders. However, the current implementation does not properly handle this, with the default crone job running daily sending email reminders up to one day late. ### Current behavior before PR: Although the current implementation ensures the crone is not triggered for alarms of external-calendars-synced events, the default crone job that is running daily is going all over the events with reminders need to be sent and send them up to one day late. ### Desired behavior after PR is merged: When the crone goes to trigger the _send_reminder method, it will check first if the events are synced or not, and if synced then no reminders will be sent from odoo's side. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr task-id: 4316693 Forward-Port-Of: odoo/odoo#192876
Related to https://github.com/odoo/odoo/pull/211714 Forward-Port-Of: odoo/enterprise#86440
Original PR description
Related to https://github.com/odoo/odoo/pull/211714 Forward-Port-Of: odoo/enterprise#86440
Before this PR: Activity created from Chatter was not reflecting on records in UI without reloading the screen. Mainly because parent view was not reloading with updated data. After this PR: Activity methods are patched such that if there is any change in activities from chatter in documents.documents model, it will reload the view with updated data. Task - 3786861 Forward-Port-Of: odoo/enterprise#59875
Original PR description
Before this PR: Activity created from Chatter was not reflecting on records in UI without reloading the screen. Mainly because parent view was not reloading with updated data. After this PR: Activity methods are patched such that if there is any change in activities from chatter in documents.documents model, it will reload the view with updated data. Task - 3786861 Forward-Port-Of: odoo/enterprise#59875
Issue: When having a folder with user_specific where we move a document to it that we do not own, we will get a traceback, this traceback is generated due to the `record.getChanges()` inside our `_multiSave` catch which is triggered after trying to load the document we just moved, because we lost the access to this document we are going to get an accessError, but we won't be able to have access to the record inside the catch either. Steps to reproduce: 1. Install Documents App 2. Gi
Original PR description
Issue: When having a folder with user_specific where we move a document to it that we do not own, we will get a traceback, this traceback is generated due to the `record.getChanges()` inside our `_multiSave` catch which is triggered after trying to load the document we just moved, because we lost the access to this document we are going to get an accessError, but we won't be able to have access to the record inside the catch either. Steps to reproduce: 1. Install Documents App 2. Give Demo only User rights for documents. 3. Sign in as Demo. 4. Try to change a document that we don't own to the Spreadsheet workspace. Solution: Since It's not clear why do we need to check the `record.getChanges()` before discarding, we can get rid of it to keep a behavior more aligned with the original `_multiSave`. opw-3410103 Forward-Port-Of: odoo/enterprise#57747 Forward-Port-Of: odoo/enterprise#55439
*: account_sepa_direct_debit, l10n_ec --- Description of the issue this commit addresses: [This PR](odoo#211150) has brought our attention to some files that were in the codebase but not included in their module's manifest. Therefore they are useless as is and can either be deleted or need to be put in the manifest. --- Desired behavior after this commit is merged: Unused useless files have been removed from the codebase. Unused useful files have been added to their module's m
Original PR description
*: account_sepa_direct_debit, l10n_ec --- Description of the issue this commit addresses: [This PR](odoo#211150) has brought our attention to some files that were in the codebase but not included in their module's manifest. Therefore they are useless as is and can either be deleted or need to be put in the manifest. --- Desired behavior after this commit is merged: Unused useless files have been removed from the codebase. Unused useful files have been added to their module's manifest. --- task-4822341 Forward-Port-Of: odoo/enterprise#86397
In this commit, I added the post_install and -at_install tags to the TesthelpdeskAccount class to delay its execution until all required journals and accounts are populated in the database, as the test depends on these records. runbot-163222 Forward-Port-Of: odoo/enterprise#86412
Original PR description
In this commit, I added the post_install and -at_install tags to the TesthelpdeskAccount class to delay its execution until all required journals and accounts are populated in the database, as the test depends on these records. runbot-163222 Forward-Port-Of: odoo/enterprise#86412