Friday, January 5, 2024
12 changes · 17.0
Resolved issues and error corrections
This fixes how the website editor identifies XML content when editing page head or body code. It helps ensure the editor applies the right behavior and formatting, reducing confusion for users making website code changes.
The Belgian localization demo setup now uses the proper expense account for negative cash differences in cash journals. This prevents losses from being classified as income, improving accounting accuracy for Belgian demo configurations.
Original PR description
This fix is to solve a bug that appears in the demo data of the l10n_be specifically in the cash journal using an income type account for the negative cash difference which should be an expense type. current behavior: using income type in a loss account. desired behavior: expense account instead. opw-3642586
Header buttons that are meant to always display will now still respect rules that hide them when appropriate. This prevents users from seeing actions in list and kanban views when those actions should be hidden based on the page setup.
Original PR description
Since the commit odoo/odoo@0d99f4b9d9de404fea44ecf5480ec3b07c2b0fd6 , the header buttons with display="always" can't be invisible. The invisible attribute is ignored for this type of button in list view and kanban view. This commit fixes this issue by adding t-if that will evaluate the invisible attribute. 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 keyboard shortcut for completing an activity and scheduling the next one has been changed so it no longer conflicts with the Save/Schedule action. This helps users avoid triggering the wrong action when using keyboard shortcuts in the activity dialog.
Original PR description
This commit simply replaces the shortcut for the action_done_schedule_next buttons from alt+q to alt+z in the activity view dialog because the alt+q shortcut is already used for the Save/Schedule buttons. This was already done in https://github.com/odoo/odoo/pull/145738 but the wizard which appeared in 17.0 hadn't been corrected. opw-3565747
A bug has been fixed where the pager (pagination controls) was not appearing in the Timesheet Timer List View. This issue was caused by a technical interaction problem in the framework that has been resolved. Users will now be able to see and use pagination controls when viewing timesheet timers, improving navigation through large lists.
Original PR description
Before this commit and it's community counter part [1], the pager wasn't displayed in the TimesheetTimerListView. This was due to a wrong interaction between two calls to useSubEnv and useChildSubEnv (more information available on [1]). The issue has been fixed directly in the framework, so this commit only adds a test. opw 3636182 Forward-Port-Of: odoo/enterprise#53317 Forward-Port-Of: odoo/enterprise#53286
This fix resolves a crash that occurs when users import PDF invoices using OCR if they have uninstalled the Italian EDI module. The issue was caused by code in the reports module trying to access a function that only exists in the EDI module. We've reorganized the code to restore proper dependencies, ensuring invoice imports work reliably regardless of which modules are installed.
Original PR description
After odoo/enterprise#38518, there are cases in which people uninstall `l10n_it_edi` so the following traceback is given when importing a PDF invoice (OCR):
```
File "/home/odoo/src/enterprise/saas-16.4/l10n_it_reports/models/account_move.py", line 9, in <lambda>
lambda rec: self.env['account.edi.format']._check_filename_is_fattura_pa(rec.name)
AttributeError: 'account.edi.format' object has no attribute '_check_filename_is_fattura_pa'
```
We move everything back to `l10n_it_edi`, ~~but the test will be excised.~~
Community PR: odoo/odoo#147370
Forward-Port-Of: odoo/enterprise#53333Customer statements were displaying the wrong year at the end of certain weeks due to an incorrect date format code. This fix corrects the date formatting so that year-end dates like December 31, 2024 display correctly instead of showing 2025. This ensures financial reports show accurate dates to customers.
Original PR description
The dates in the customer statements header is using the format 'Y'. This is an issue as the capital Y is using the ISO year-week calendar, leading to the wrong year being displayed in the report during some weeks. To reproduce on runbot, simply open the partner ledger on 2024 and print. The end date should be 31/12/2024 but formatted as 31/12/2025
This fix resolves a crash that occurred when users tried to autofill cells upward in spreadsheet pivot tables by dragging to column headers. The issue happened because the system was passing incorrect parameters when autofilling the last column. Now the autofill feature works correctly regardless of which column is selected.
Original PR description
Steps to reproduce: - Select a cell from last column (Total) - Autofill vertically upwards by targeting a column header (drag upto measure, total or beyond) - It leads to a traceback error since in cases with step <= -2, incorrect params are being passed to `makePivotFormula` of `_autofillColFromValue` method. This PR fixes the issue by handling the case of last column seperately. It ensures that correct params are passed in each case, and hence an accurate resultant formula is formed. Task ID : 3461853 Forward-Port-Of: odoo/enterprise#53568 Forward-Port-Of: odoo/enterprise#45685
This update corrects a test case in the payroll module that was failing due to year-related validation issues. The fix ensures that salary attachment tests run correctly and reliably, improving the stability of payroll testing processes.
Original PR description
Forward-Port-Of: odoo/enterprise#53623 Forward-Port-Of: odoo/enterprise#53554
A bug was fixed where purchase taxes could incorrectly be applied to customer invoices when the OCR system detected a matching tax. The system now correctly uses sales tax settings for customer invoices instead of purchase tax settings, ensuring accurate tax classification.
Original PR description
The default purchase tax could be set on a customer invoice when it matched the tax found by the OCR. Now, it will properly check `account_sale_tax_id` instead of `account_purchase_tax_id` for customer invoices. Forward-Port-Of: odoo/enterprise#53717 Forward-Port-Of: odoo/enterprise#53558
This update fixes an issue where the Knowledge export feature was including unnecessary interface elements like discussion tabs and toolbars in exported documents. The fix ensures that only the main content is exported, resulting in cleaner, more professional exported files that contain only the information users actually need.
Original PR description
This commit fixes a bug where the export button would take into account elements that are useless to print (such as discuss tabs). Now we added a scss rule inside the `knowledge_print.scss` file to remove any element that is not inside of the action_manager => all of the discuss containers, the editor toolbar, etc. task-3653295 Forward-Port-Of: odoo/enterprise#53573
This fix resolves an issue where translated text in the bank reconciliation interface was causing unwanted line breaks in partner-related buttons (such as "Client:" and "Payable:" labels). The problem occurred when translations introduced extra whitespace, making buttons appear broken or misaligned. This fix ensures buttons display properly regardless of language, improving the user experience in the bank reconciliation process.
Original PR description
Translations may introduce whitespace into the text of some buttons. The text of the buttons may then contain a linebreak. This i.e. concerns the buttons in the "Manual Operations" tab that are visible when a non-liquidity line is selected and has a partner set: "Client:", "Payable:" below the partner. Reproduce 1. Select French language 2. Go to the bank reconciliation widget and select an unmatched statement line. 3. On the right side: Select any line that is not the liquidity line 4. Ensure that the "Manual Operations" tab is selected 5. Ensure that a partner is set and the 2 buttons below the partner are visible. 6. The 2 buttons contain linebreaks. Forward-Port-Of: odoo/enterprise#53574 Forward-Port-Of: odoo/enterprise#52027