Monday, February 17, 2025
14 changes · 17.0
Enhancements to existing features
Installing the Turkish localization now also installs the Turkish language automatically. This reduces setup steps for Turkish companies and helps ensure the system is ready to use in Turkish right away.
Original PR description
This **PR** auto installs the Turkish language upon installing `l10n_tr`. TaskID:4504454 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Website pop-up windows now show clear borders again, making them easier to read when content is long or scrolls. This improves visual hierarchy and helps users better understand where the modal content begins and ends.
Original PR description
The lack of borders in the modals of the front-end is problematic when there is some content overflowing the height of the modal. This PR restores the borders for a better visual hierarchy. Non-optimal design introduced in front-end redesign: https://github.com/odoo/odoo/pull/120302 task-4001380 | Before | After | |--------|--------| | <img width="979" alt="Screenshot 2024-06-20 at 11 41 54" src="https://github.com/odoo/odoo/assets/110090660/31e0d3c7-fcd9-43c9-9aae-7db3b4e49af2"> | <img width="978" alt="Screenshot 2024-06-20 at 11 42 26" src="https://github.com/odoo/odoo/assets/110090660/09f12eb0-79e4-454f-9896-af238b26a7b3"> | --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update adds automated coverage to ensure Knowledge article templates keep embedded static files working correctly. It helps prevent regressions that could affect template content and attached visuals or resources.
Original PR description
The related community commit ensures that knowledge article templates correctly handle embedded static files. This commit adds a test for that behavior. opw-4380368 opw-4433248 Related Community PR: https://github.com/odoo/odoo/pull/197539
Resolved issues and error corrections
This fixes an issue where delivery transfers removed from a wave could still show a message saying they were transferred by that wave. Business users will now see accurate transfer histories, reducing confusion when reviewing warehouse operations.
Original PR description
The message "Transferred by <Wave Nb>" was posted on pickings that are detached before the wave is validated. How to reproduce: - Create Product P, storable, with 2 unit on hand - Create 2 delivery transfer for 1 unit of P each - Add both transfer to new wave - Set Picked to True on 1 of the move, and not on the other. - Validate the wave transfer => 1 transfer only is validated (OK), but both have a message saying that the transfer was "Transferred by <Wave Nb>" Removed `skip_immediate` context as it is obsolete, and allow the function to only have 1 return statement, which is needed for the fix. OPW-4503809
Miscellaneous changes
**Current behavior:** Invoicing some product at a price unit different from that at reception (with the product having manual valuation and non-standard costing) will create pdiff account move lines on the invoice. **Expected behavior:** With manual valuation, there should not be pdiff AMLs. **Steps to reproduce:** 1. Create a product with average costing and manual valuation 2. Receive 10 units @ $100 to establish some std price 3. Consume the 10 product qty (scrap, sale, ...)
Original PR description
**Current behavior:** Invoicing some product at a price unit different from that at reception (with the product having manual valuation and non-standard costing) will create pdiff account move lines on the invoice. **Expected behavior:** With manual valuation, there should not be pdiff AMLs. **Steps to reproduce:** 1. Create a product with average costing and manual valuation 2. Receive 10 units @ $100 to establish some std price 3. Consume the 10 product qty (scrap, sale, ...) 4. Create the invoice on the purchase order 5. Change the price unit on the bill to $120 per product -> post 6. In the journal items tab on the invoice, see the pdiff AMLs **Cause of the issue:** No consideration for valuation when creating the AMLs for pdiff. **Fix:** Check that valuation is not manual prior to creating the AMLs. opw-4492217 Forward-Port-Of: odoo/odoo#196786
A broken link in the contribution guide was corrected so readers can reach the intended pull request template information. This helps contributors find the right instructions and reduces confusion when reporting issues or proposing changes.
Original PR description
Description of the issue/feature this PR addresses: In the 'CONTRIBUTING.md' file , there is a list item with the text: > Use this **template** when reporting issues. Please search for duplicates first! The link named 'template' should point to a pull request template. Current behavior before PR: The link named 'template' is broken and give a 404 error. Desired behavior after PR is merged: The link named 'template' now target the 'Contributing' wiki page, section 'making-pull-request' that contains the desired template. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Fixed an inventory calculation issue where package location quantities could be compared with the wrong rounding precision. This helps ensure stock package location decisions are based on accurate quantity comparisons, reducing the risk of small rounding errors affecting warehouse operations.
Original PR description
### Issue: The spec of the `float_compare` method was not used correctly here: https://github.com/odoo/odoo/blob/dc2821d768a7b4afbb5918e4343c00abeeb31670/odoo/tools/float_utils.py#L141 https://github.com/odoo/odoo/blob/dc2821d768a7b4afbb5918e4343c00abeeb31670/addons/stock/models/stock_quant.py#L1487 opw-4574169 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Message date and time tooltips in chatter now use the user's configured language format. This ensures customized date or time formats are shown consistently when users hover over message timestamps.
Original PR description
Versions -------- - 17.0+ Steps ----- 1. Go to Settings / Languages; 2. customize the date or time format of the active lang; 3. open a chatter; 4. hover over the date text of a message. Issue ----- Customized format isn't used for the tooltip. Cause ----- In v16.0 & earlier, this tooltip was formatted using the web util `getLangDatetimeFormat`. This util has been superseded, and had been replaced with the builtin `DATETIME_SHORT` when `discuss` got refactored in 7710c3331ebd2, before getting replaced again with `DATETIME_SHORT_WITH_SECONDS` via 941e28cee11cc. Solution -------- Use the `formatDateTime` util from `web`. With the default values, this should be the same as `DATETIME_SHORT_WITH_SECONDS`, but allows for user customization. opw-4266569
Swiss payroll deductions are now posted to the correct opposite debit and credit accounts when their totals are negative. This helps ensure payroll accounting entries are accurate and reduces the need for manual correction.
Original PR description
Since deductions are negative in the total, we need to invert accounts for them to be properly posted in the inverse credit and debit accounts.
The Belgian payroll reporting logic now includes exoneration amounts when counting private car benefits. This helps ensure employee tax forms reflect company car benefits more accurately and reduces the risk of payroll reporting mistakes.
- update the `co2_fee_min, health_indice` paramters values Task: 4563950 Forward-Port-Of: odoo/enterprise#78999
Original PR description
- update the `co2_fee_min, health_indice` paramters values Task: 4563950 Forward-Port-Of: odoo/enterprise#78999
When an employee takes a leave, the private car reimbursement amount is reduced by a certain amount. However, when they take multiple leaves, the computation doesn't follow. This commit fixes the issue. task-4353922 Forward-Port-Of: odoo/enterprise#75552
Original PR description
When an employee takes a leave, the private car reimbursement amount is reduced by a certain amount. However, when they take multiple leaves, the computation doesn't follow. This commit fixes the issue. task-4353922 Forward-Port-Of: odoo/enterprise#75552
Change the "up to this date" to "before this date", to specify that its upper limit is excluded. Otherwise, when you set 31/12/24 in this field and Odoo cancels all the entries up to 30/12/24 and leave the 31/12/24 entries, you'll be disappointed. Task [link](https://www.odoo.com/odoo/project/967/tasks/4447369) task-4447369 Forward-Port-Of: odoo/enterprise#79105
Original PR description
Change the "up to this date" to "before this date", to specify that its upper limit is excluded. Otherwise, when you set 31/12/24 in this field and Odoo cancels all the entries up to 30/12/24 and leave the 31/12/24 entries, you'll be disappointed. Task [link](https://www.odoo.com/odoo/project/967/tasks/4447369) task-4447369 Forward-Port-Of: odoo/enterprise#79105
An error occurs when triggering a cron job for posting all pending posts. ```ValueError: Expected singleton: social.post(14, 13)``` A singleton error occurs when the system tries to get a value of 'post_method' from multiple records at [1]. Link [1]: https://github.com/odoo/enterprise/blob/5e968dfce025102bc27f01ba9b07304477835b47/social_push_notifications/models/social_post.py#L26 To avoid the singleton error, we can use the ```mapped()``` function to retrieve a list of values from a
Original PR description
An error occurs when triggering a cron job for posting all pending posts. ```ValueError: Expected singleton: social.post(14, 13)``` A singleton error occurs when the system tries to get a value of 'post_method' from multiple records at [1]. Link [1]: https://github.com/odoo/enterprise/blob/5e968dfce025102bc27f01ba9b07304477835b47/social_push_notifications/models/social_post.py#L26 To avoid the singleton error, we can use the ```mapped()``` function to retrieve a list of values from all the records and check the condition across them. Sentry-6055370689 Forward-Port-Of: odoo/enterprise#74698