Tuesday, April 30, 2024
34 changes
Enhancements to existing features
Odoo has updated its JavaScript language support to ES2022, which requires Node.js version 16.11 or higher. This change makes that requirement explicit in the development tooling configuration, preventing developers from encountering confusing errors when using outdated Node.js versions.
Original PR description
Starting with Odoo 16.1, the ECMAScript version supported by Odoo has been bumped to ES2022, but support for all ES2022 features has only been achieved with Node.js 16.11*, making it the minimum required version to run Odoo. This commit updates the package.json to make this requirement explicit, preventing from using the tooling with an outdated version of Node.js, which would otherwise result in an unclear syntax error. *: From all the features added in ES2022, support for static initialization blocks is the latest to have been added, in Node.js 16.11, according to MDN's compatibility data. Forward-Port-Of: odoo/odoo#163787
This update enhances the Bulgarian tax report by adding two missing sections (D and E) that were previously unavailable. Additionally, a specific line item has been changed to allow direct editing instead of automatic calculation, giving users more flexibility in reporting their tax information.
Original PR description
- Adds missing section D and E to the tax report. - Change line 43 to editable instead of aggregation. task-3672445 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#161658 Forward-Port-Of: odoo/odoo#155223
Resolved issues and error corrections
This update corrects how rounding precision is applied in the manufacturing and inventory management systems. The system was using incorrect parameters when calculating rounded values, which could have led to inaccurate quantity calculations in bills of materials and stock movements. This fix ensures rounding is applied correctly across these critical business processes.
Original PR description
Versions -------- - 16.0+ Issue ----- `precision_rounding` values were being passed incorrectly as `precision_digits` parameters. Solution -------- Pass them as named `precision_rounding` parameters instead. Forward-Port-Of: odoo/odoo#163154
This fix resolves an issue where extra down-payment invoice lines with zero price were being automatically created when taxes were removed from the initial down-payment invoice. The solution improves the down-payment calculation logic to properly exclude down-payment lines and only consider actual sales order product lines, preventing duplicate entries in subsequent down-payment invoices.
Original PR description
… when remove the tax on first downpayment invoice Issue: ====== Extra down-payment line is creating Steps to reproduce the issue: ============================= - create an SO, then create…
… when remove the tax on first downpayment invoice
Issue:
======
Extra down-payment line is creating
Steps to reproduce the issue:
=============================
- create an SO, then create downpayment with 30% percent, remove the tax in generated INV and post the invoice.
- go back to SO create another downpayment with 30%
Solution:
=========
Typically, when calculating the value of down-payment lines,
we only consider sales order lines for products, not down-payment lines.
This is because, according to the Odoo workflow, down-payment lines are
created based on product lines in the sales order, not on down-payment
lines themselves. Therefore, I am filtering out those lines here.
closes odoo/odoo#163699
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-prThis fix resolves an issue where extra down-payment invoice lines with zero price were being automatically created when removing taxes from the first down-payment invoice. The solution ensures that down-payment calculations only consider actual sales order product lines, not previously created down-payment lines, preventing duplicate entries from being generated.
Original PR description
…erated when remove the tax on first downpayment invoice Issue: ====== Extra down-payment line is creating Steps to reproduce the issue: ============================= - create an SO, then create…
…erated when remove the tax on first downpayment invoice
Issue:
======
Extra down-payment line is creating
Steps to reproduce the issue:
=============================
- create an SO, then create downpayment with 30% percent, remove the tax in generated INV and post the invoice.
- go back to SO create another downpayment with 30%
Solution:
=========
Typically, when calculating the value of down-payment lines,
we only consider sales order lines for products, not down-payment lines.
This is because, according to the Odoo workflow, down-payment lines are
created based on product lines in the sales order, not on down-payment lines themselves.
Therefore, I am filtering out those lines here.
closes odoo/odoo#163699
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-prThe Kitchen Display app was causing testing failures when its conditional menu interacted with other applications, resulting in log errors and system failures. This fix skips the problematic menu during testing to prevent these cascading failures and improve system stability.
Original PR description
The Kitchen Display app uses a conditional menu that can leads to the frontend. In some situation, other apps are tested again during the Kitchen Display test leading to a mess in the logs and a epic failure. As no viable solution was found, the menu is now skippep with this commit.
The portal's mobile navigation menu was extending beyond the navbar boundaries on mobile devices, which could cause unwanted horizontal scrollbars in certain configurations. This fix removes an unnecessary negative margin that was causing the overflow, improving the mobile user experience and preventing layout issues.
Original PR description
The portal mobile navbar menu was overflowing its parent (the navbar) on the left and right once opened. This is because of a combination of commits [1] and [2]. Indeed, [1] added a negative margin…
The portal mobile navbar menu was overflowing its parent (the navbar) on the left and right once opened. This is because of a combination of commits [1] and [2]. Indeed, [1] added a negative margin on that menu to compensate the parent navbar's padding. However, [2] later forced that parent padding to 0 with a class. This commit removes the negative margin compensation to fix the issue. Note: the design may not seem that broken without this fix. But in custo it could look very bad as it could introduce a horizontal scrollbar: just make the portal layout use a fluid container and have `$navbar-padding-x` be higher than `$grid-gutter-width`. Also, note that the design is not perfect as the inner padding of that menu also relies on the navbar padding value... which is ok in Odoo but only because we change the default of Bootstrap, which is 0. It was chosen to ignore that problem in stable. In master, the navbar padding will be left back to the BS default (0) and another spacing value will thus be used for the portal menu. [1]: https://github.com/odoo/odoo/commit/f8940943592b696b4f27c0013f837a6cdecb0433 [2]: https://github.com/odoo/odoo/commit/df8535fbd40e1e5c09dbe616a3332c76c23525c8 Related to https://github.com/odoo/odoo/pull/163996 | Before | After | | -------- | -------- | |  |  |
This update modernizes how Odoo handles Python code analysis to align with Python 3.12+ standards. The changes remove deprecated code patterns that will stop working in Python 3.14, ensuring the system continues to function properly as Python evolves. This is a maintenance fix that keeps Odoo compatible with current and future Python versions.
Original PR description
Since 3.8, some ast object and parameters changed, with backward compatibility. They are now deprecate in 3.12 and will be removed in 3.14. Keeping a compatibility between both solutions is possible but hard to do with python > 3.7, the solution was to mute the warning in odoo 15.0 since it is unlikely to make it compatible with python 3.14, but we can fix it a cleaner way in 16.0 since the minimal python version is higher than 3.8. see #162438 for 15.0 suppress warning fix part of #162438 , adaptations for ubuntu noble Forward-Port-Of: odoo/odoo#163487
This fix resolves a system error that occurred when creating sales orders with products from different company branches. The issue was in how the system validated company access, and this update corrects the validation logic to check companies individually rather than as a group, allowing sales orders with mixed-company products to save successfully.
Original PR description
Issue: A traceback error is raised when a sales order is saved with products with varying company ids. Was trying to lookup a list of ids rather than a singular id which triggered the traceback. Purpose of this PR: To check accessible company branches on a individual company rather than a recordset of companies. Steps to Reproduce on Runbot: 1) Create branch of main company. 2) Create products one with company id of the branch and the other of company id in the main company. 3) Create sale order, order lines with each of the products. 4) On save, a traceback error is raised. Notes: opw-3810770 Forward-Port-Of: odoo/odoo#162547