Daily updates from Odoo
Wednesday, August 14, 2024
5 changes
2 changes
Resolved issues and error corrections
This fixes an issue where Odoo could treat the same page address as different when URL options appeared in a different order. Users should see cleaner browser navigation behavior, especially when enabling debug assets, without repeated entries for the same page.
Original PR description
When on the main menu, `/odoo?cids=1`, if you activate the debug assets, the router will push a new key (debug) into the query string : `/odoo?cids=1&debug=assets`. To fully activate the debug, a…
When on the main menu, `/odoo?cids=1`, if you activate the debug assets, the router will push a new key (debug) into the query string : `/odoo?cids=1&debug=assets`. To fully activate the debug, a reload will be done. After the reload, the action service will push the new loaded state (the menu), taking into account the locked keys (in this case: `cid` and `debug`), which will inverse the order of the query string : `/odoo?debug=assets&cids=1`. This occurs because, the order of the keys on the query string will depend on: the push order; if the keys are locked keys or not; and of the kind of push state (replacement or simple push state). The issue with this almost "random" order of the keys, is that the router could push the same URL (with keys in different order) multiple times into the browser history. Before this commit, to compare the actual URL with the new one, we just compare the two strings, and if the order of the query strings are not the same the URLs are considered as different. This commit, will avoid this issue by deep comparing the query string as objects, so when just a difference of order exists in the query string, they will be considered as the same URL. opw-3557575
Loaded signatures now display without being stretched inside the signature field. This keeps signatures looking natural and professional on signed documents, improving the signing experience.
Original PR description
Before this commit: When loading a signature, the displayed image would be stretched to fit the signature box, messing up the ratio between width and height. This commit aims to fix this issue by: keeping the same ratio between width and height. and just multiply both of them by the same factor. Task: 4049758 Before:   After:  
2 changes
Resolved issues and error corrections
This fix prevents users from changing the refund status of a salary attachment once it has already been used in payslips. This helps protect payroll accuracy by avoiding inconsistent records after payroll processing has begun.
Original PR description
TaskID: 4040011
Scanning a barcode found in the lookup service no longer fails when the product has no image available. The product can still be created or updated from the barcode data, with the missing image simply skipped.
Original PR description
Issue: Traceback is encountered when scanning a barcode that is available in the barcodelookup api but doesn't have image. Example barcode: 9780349410159 - Traceback: `AttributeError: 'dict' obiect has no attribute 'content'` This is because of the inconsistent return value of `barcode_lookup_request`. If it succeeds, it returns a `Response` object but if not, it returns a `dict`. To fix the traceback, we check if the fetching of image failed by checking if the returned value is a `dict`. If so, we just skip the image assignment for the product.
1 change
Resolved issues and error corrections
This update refreshes translation template files across multiple accounting and business modules to ensure they are current and accurate. Outdated translation files were updated, and empty files that were no longer needed were removed. This ensures that translators have the correct and up-to-date content to work with when localizing Odoo for different languages.
Original PR description
Some were out of date. Also, there were some empty pot files that were deleted along with their obsolete .po files.