Monday, January 9, 2023
11 changes · master
Resolved issues and error corrections
This fixes an issue where page breadcrumb labels could appear missing or undefined after a screen name was updated. Users should see more reliable navigation context while moving through Odoo screens.
Original PR description
--- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Embedded list views no longer download full binary file contents unless they are actually needed. This reduces unnecessary data transfer and can make affected pages load faster, especially where dashboards or related records include file fields.
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
The Point of Sale quotations and orders button has been fixed so staff can open sales orders from the POS screen again. This restores access to quotations created in the Sales app, helping sales and checkout teams continue their normal workflow without browser errors.
Original PR description
The quotation/orders button in the POS application was not working anymore. Current behavior before PR: When pressing the button Quotations/Orders in the product screen of a POS config, the browser send an error saying that 'contexts' is undefined. Desired behavior after PR is merged: The Quotations/Orders button works again (the Quotation made in the Sales application are visible and usable from a POS config) Change made: The fix changes the import made to PosContext and the use of this import in the SaleOrderManagementScreen.js file so that the press of the SO button works as it should. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fixes a product pricing issue that could occur when no suitable pricing rule was found. The change prevents the system from treating a product record as a price, helping avoid incorrect pricing behavior or errors in affected product workflows.
Original PR description
unprotected variable: price_type `product[False] == product` `price` should not be a product. It doesn't make any sense. Got this bug when suitable_rules is an empty record set. The fallback when no rule is found has been dropped here: https://github.com/odoo/odoo/commit/a7f30ce91766da3b9a6c97180cf97803c9de0528#diff-21fdb0b99c09254c9445e27ceee2d2e27503e93d9dd99481c010d92226db6f75R159 @Feyensv 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 update helps Croatian accounting setups migrate cleanly from older versions by aligning the Euro-based localization with the main Croatia module. It also preserves the former Kuna-based setup under a clearer name so companies can keep historical accounting data accessible.
Original PR description
To allow people from v16.0 to have the new module in EURO, we added the module l10n_hr_euro in stable, this PR modify the l10n_hr module to allow people to migrate without problem since l10n_hr_euro become l10n_hr in master. Also the old module l10n_hr of the stable version will be added so that they can keep an history. But like the other, we renamed the module to facilitate the comprehension. l10n_hr in stable become l10n_hr_kuna in master. task-id: 3102242 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This change brings back the price difference account for purchased products using standard cost and real-time valuation. It helps companies track differences between invoice prices and standard costs during the accounting period, improving cost reporting and reducing manual reconciliation work.
Original PR description
Version 16.0 removed the price different account following this pull request https://github.com/odoo/odoo/pull/99411 This decision has been made because it was only used anymore by standard cost…
Version 16.0 removed the price different account following this pull request https://github.com/odoo/odoo/pull/99411 This decision has been made because it was only used anymore by standard cost method and real time valuation. We thought that standard was not a valid accounting method and we didn't want to maintain code for it. But: - Standard could be valid if you manualy complete the accounting entries by yourself (e.g. employees/machines cost in mrp). - It's also accepted as legal inventory valuation if you record the difference between invoice and standard price + regular update of the standard price to match the reality - If you want to have an estimation of your cogs (benefits and loss) during an accounting period. People just do a manual correction at the end but they have a real time reporting on the situation. Since delivery/receipt interim accounts already exists we could say that user could simply reconcile them by himself. It could be but it would be a pain to know what part of the account is already invoiced and need a correction vs the part not yet invoiced. This commit remove the fix module added in 16.0 and put the fields back in purchase
This fix resolves visual layout issues in the Employees app on mobile devices. Employee names and job details no longer overlap profile photos, and status/activity icons in employee cards are now aligned correctly, making mobile use clearer and more polished.
Original PR description
Before this commit, two visual errors were present on mobile: - In the employee form view, the name and professions were overlapping with the profile picture; - In the employee kanban view, the presence logo and the activity logo were misaligned This commit also fixes some indentation errors.
Fixes an issue in Point of Sale where a temporary screen could cause a navigation-blocking overlay to cover the entire POS interface instead of only the navigation bar. This keeps protected flows safe while allowing the rest of the POS screen to remain usable as intended.
Original PR description
*: pos_hr_restaurant, pos_restaurant In #108891 the navbar was extracted out of the Chrome and into its own components, but when a temp screen is shown, an overlay is placed over the navbar to prevent the user from using it to navigate away as this can break some flows, and the overlay was not moved inside the navbar. This caused the overlay to go over the entire Chrome which was not the goal. This commit moves the block-header overlay into the navbar (and adapts some code to make the tempScreen state accessible inside the navbar).
This change prevents product pricing from using an invalid value when no suitable pricing rule is found. It helps avoid incorrect price calculations or errors in product-related workflows when pricing rules are missing or empty.
Original PR description
unprotected variable: price_type `product[False] == product` `price` should not be a product. It doesn't make any sense. Got this bug when suitable_rules is an empty record set. The fallback when no rule is found has been dropped here: https://github.com/odoo/odoo/commit/a7f30ce91766da3b9a6c97180cf97803c9de0528#diff-21fdb0b99c09254c9445e27ceee2d2e27503e93d9dd99481c010d92226db6f75R159 @Feyensv I have closed https://github.com/odoo/odoo/pull/109443 by error, can't re-open it. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The import screen now organizes field choices correctly when matching spreadsheet columns to Odoo fields. This makes imports easier and less error-prone by showing the right suggested, additional, and related fields without duplicate or confusing labels.
Original PR description
[FIX] base_import: Fix filtered fields shown in select menu During the conversion to Owl of the base_import action, the fields mapping for each column was made incorrect. The fields are now properly sorted between the suggested, additional and relational categories and the subfields are also correctly handled (no more duplicates and correct labels). (See legacy fields sorting: https://github.com/odoo/odoo/blob/16.0/addons/base_import/static/src/legacy/js/import_action.js#L759) --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Salary simulation links now use the employee's actual contract instead of a separate default contract setting. This helps ensure generated salary links reflect the correct employment terms and reduces the risk of incorrect salary simulations.
Original PR description
Before this commit, the default contract for a generation link used to be the default_contract_id for the employee. After this commit, the contract of the employee is used instead. task-3106778