Daily updates from Odoo
Sunday, May 10, 2026
12 changes
2 changes
Resolved issues and error corrections
This update fixes a reporting issue related to Goods and Services Tax (GST) filings in India (GSTR-3B). Previously, reverse charge tax entries were incorrectly placed in a specific table. Now, these entries are correctly reported in the appropriate table, ensuring accurate tax reporting and compliance.
Original PR description
Previously, journal items for import of services with reverse charge tax were shown only in table 4(A)(2) and not in table 3.1(d). However, since table 3.1(d) is meant for supplies liable to reverse charge, those entries should also be reported there. With this commit, import of service reverse charge entries are now correctly included in table 3.1(d) as well. Forward-Port-Of: odoo/enterprise#116827 Forward-Port-Of: odoo/enterprise#116708
This update fixes an issue where the image cropper in the HTML editor didn't correctly apply style settings like rounded corners. Now, users will see a precise preview of how their images will look after cropping, ensuring consistent results and a better user experience. This was previously addressed and temporarily lost during a website builder update.
Original PR description
When cropping images with style option applied (e.g., circle), the cropper ignored these styles, causing a mismatch between the preview and the final rendered image.This made the issue especially noticeable for rounded styles. This commit ensures the cropper reflects the applied style, allowing users to preview the final result more accurately. This behavior was previously fixed in https://github.com/odoo/odoo/pull/197374 but was lost during the website builder refactoring (see commit https://github.com/odoo-dev/odoo/commit/9fe45e2b7ddbbfd0445ffe25a859e67a316d02b2). This change restores the expected behavior. task-6088098 Forward-Port-Of: odoo/odoo#263432 Forward-Port-Of: odoo/odoo#256966
2 changes
Resolved issues and error corrections
This update fixes an issue where the image cropper in the HTML editor didn't correctly display style options like rounded corners. The change ensures users see a precise preview of how the final image will look, improving the user experience and reducing errors when customizing images. This was previously addressed and temporarily lost during a website builder update.
Original PR description
When cropping images with style option applied (e.g., circle), the cropper ignored these styles, causing a mismatch between the preview and the final rendered image.This made the issue especially noticeable for rounded styles. This commit ensures the cropper reflects the applied style, allowing users to preview the final result more accurately. This behavior was previously fixed in https://github.com/odoo/odoo/pull/197374 but was lost during the website builder refactoring (see commit https://github.com/odoo-dev/odoo/commit/9fe45e2b7ddbbfd0445ffe25a859e67a316d02b2). This change restores the expected behavior. task-6088098 Forward-Port-Of: odoo/odoo#263432 Forward-Port-Of: odoo/odoo#256966
This update corrects a flaw in how missing transactions are identified for online accounts. Previously, the system only checked transactions from the last sync date, leading to missed records. Now, the system prioritizes the provided start date, ensuring a more complete and accurate retrieval of online transaction data.
Original PR description
When you want to find missing transactions, you have to put a starting date. But we don't use this starting date to find the last statement line, we only use the last sync date, which is wrong, because if the last sync date is after the starting date, the online transaction identifier will have the wrong date. It means we will only fetch the transactions from last sync date to today. This commit makes sure we take the start date first if it exists, then the last sync date. task-6197277 Forward-Port-Of: odoo/enterprise#116624
5 changes
Resolved issues and error corrections
This update fixes a visual discrepancy in the image cropping preview. Previously, styles like 'circle' weren't correctly applied, leading to inaccurate previews. Now, the cropper accurately reflects the chosen style, ensuring users see the final image result more precisely.
Original PR description
When cropping images with style option applied (e.g., circle), the cropper ignored these styles, causing a mismatch between the preview and the final rendered image.This made the issue especially noticeable for rounded styles. This commit ensures the cropper reflects the applied style, allowing users to preview the final result more accurately. This behavior was previously fixed in https://github.com/odoo/odoo/pull/197374 but was lost during the website builder refactoring (see commit https://github.com/odoo-dev/odoo/commit/9fe45e2b7ddbbfd0445ffe25a859e67a316d02b2). This change restores the expected behavior. task-6088098 Forward-Port-Of: odoo/odoo#263432 Forward-Port-Of: odoo/odoo#256966
This update enhances the logging process during cloud storage migration, providing more detailed information about the progress and any potential issues. Previously, migration logs were limited, making it harder to track and troubleshoot problems. Now, the logs will offer clearer insights, allowing our team to quickly identify and resolve any challenges related to migrating data to the cloud.
Original PR description
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#263669 Forward-Port-Of: odoo/odoo#263557
This update resolves a crash that could occur when attempting to unassign items from stock reception reports if the associated source document (like an MO) was empty. The fix prevents the system from attempting to remove references to empty source documents, making the report more reliable and robust. This primarily impacts clients with specific configurations.
Original PR description
#### Issue: Clicking `Unassign` from the stock reception report could raise a traceback when the outgoing move source document was empty. ``ValueError: Expected singleton: mrp.production()`` Please…
#### Issue: Clicking `Unassign` from the stock reception report could raise a traceback when the outgoing move source document was empty. ``ValueError: Expected singleton: mrp.production()`` Please note that this is not expected in standard Odoo, where reception report moves should normally be linked to a source document, such as an MO, SO, or picking. This case seems specific to the client database and may be due to a customization, but handling it makes the reception report more robust. #### Cause: The reception report built report lines from `source = (move._get_source_document(),)` and checked `if not source`. Since the tuple itself is truthy, moves whose `_get_source_document()` returned an empty recordset were not filtered out. For example if `out_move._get_source_document()` returns `mrp.production()`, then `source = (mrp.production(),)` is still truthy, so the report keeps the line even though the source document is empty. later `action_unassign()` called `_remove_reference()` on that empty source document, which crashed on `ensure_one()`. #### Fix: Added a helper function that skips moves where `_get_source_document()` is empty. Also skip reference synchronization in `_action_assign()` and `_action_unassign()` when the source document is empty just for more protection. opw-6174870 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#263366
This update fixes an issue where images in Odoo still contained unnecessary data after being modified (shapes removed). The change cleans up this data, resulting in faster and more efficient image loading and display. This improves the overall user experience and website performance.
Original PR description
Steps to see the issue: - Add a shape to an image - Remove it => Image element in the DOM still has some data related to the shape. This commits adds a shared method to `ImageShapeOptionPlugin` to…
Steps to see the issue: - Add a shape to an image - Remove it => Image element in the DOM still has some data related to the shape. This commits adds a shared method to `ImageShapeOptionPlugin` to clean shape-related data when we apply a shape, or remove it, the method mirrors the behavior we had before the [html builder refactoring]. Also, commit [1] fixed the issue when the builder transfered shape or hover related data to incompatible images, when replacing an image with a shape/hover on it. However if these data attributes had already been saved prior to that commit, it would stay there indefinitely. The same could happen with hover effects attributes. Therefore, we add a resource that we call before saving data to clean any stale image data. Example of a CORS protected image: [2] [1]: https://github.com/odoo-dev/odoo/commit/137a6d7e59e1d788745c3b796a14839e52a8c5bc [2]: https://tinyjpg.com/images/social/website.jpg [html builder refactoring]: github.com/odoo/odoo/9fe45e2b7ddbbfd0445ffe25a859e67a316d02b2 task-5172640 Forward-Port-Of: odoo/odoo#263433 Forward-Port-Of: odoo/odoo#259226
This update corrects a flaw in how Odoo retrieves online transaction data. Previously, users were limited to seeing transactions from the last sync date, even if a specific date range was requested. Now, the system prioritizes the user-provided start date, ensuring a more complete and accurate view of online statements.
Original PR description
When you want to find missing transactions, you have to put a starting date. But we don't use this starting date to find the last statement line, we only use the last sync date, which is wrong, because if the last sync date is after the starting date, the online transaction identifier will have the wrong date. It means we will only fetch the transactions from last sync date to today. This commit makes sure we take the start date first if it exists, then the last sync date. task-6197277 Forward-Port-Of: odoo/enterprise#116624
1 change
Resolved issues and error corrections
This update corrects a flaw in how Odoo retrieves online accounting transactions. Previously, users were limited to seeing transactions from the last sync date, even if a specific date range was requested. Now, the system prioritizes the user-provided start date, ensuring a more complete and accurate view of online transactions.
Original PR description
When you want to find missing transactions, you have to put a starting date. But we don't use this starting date to find the last statement line, we only use the last sync date, which is wrong, because if the last sync date is after the starting date, the online transaction identifier will have the wrong date. It means we will only fetch the transactions from last sync date to today. This commit makes sure we take the start date first if it exists, then the last sync date. task-6197277 Forward-Port-Of: odoo/enterprise#116624
1 change
Resolved issues and error corrections
This update corrects an issue where users weren't able to retrieve all transactions when specifying a starting date. The system now correctly prioritizes the provided date, ensuring a more complete and accurate display of online statements. This improves the reliability of financial reporting.
Original PR description
When you want to find missing transactions, you have to put a starting date. But we don't use this starting date to find the last statement line, we only use the last sync date, which is wrong, because if the last sync date is after the starting date, the online transaction identifier will have the wrong date. It means we will only fetch the transactions from last sync date to today. This commit makes sure we take the start date first if it exists, then the last sync date. task-6197277 Forward-Port-Of: odoo/enterprise#116624
1 change
Resolved issues and error corrections
This update resolves issues preventing the correct export of general ledger data in CSV format. Specifically, it corrects errors related to integer formatting and inactive currency handling, ensuring reliable reporting for financial data. This improves the accuracy and usability of the general ledger reports.
Original PR description
Follow-up to 8dfe4c0, addressing two issues in `_generate_csv_lazy_export`: 1. `AttributeError: 'int' object has no attribute 'id'` when `col['currency']` is a raw integer on aggregate lines returned by `_get_lines` with `no_format=True`. 2. `KeyError` on `decimal_places_per_cur_id` when a foreign currency account uses an inactive currency. The currency lookup was built with the default `active_test=True`, excluding archived currencies. opw-5994050 Forward-Port-Of: odoo/enterprise#112500