Monday, October 14, 2024
7 changes · 18.0
Resolved issues and error corrections
This fix prevents list views from visually breaking when users drag and drop records in configurations where automatic column sizing is disabled. It keeps tables aligned and usable during record reordering, improving reliability in a niche list view setup.
Original PR description
This is more a theoretical issue than a real issue per se. The list renderer has a flag (`useMagicColumnWidths`) that allows to disable the column widths logic. It is enabled by default, and there's only one usecase in Odoo where we disable it (and this usecase is very custom, and doesn't allow to d&d records). However, when the feature is disabled, the table layout is broken when the user drags a record. This commit is a simple patch that ensures that the layout of the list remains intact when drag&dropping a record, whether the column widths logic is enabled or not. 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 accounting dashboard now shows the correct number of vendor bills that are waiting to be paid or late. This prevents confusion when bills use split payment terms, where one bill could previously be counted more than once.
Original PR description
Description of the issue this commit addresses: Since recently, the <[X] To Pay> and <[X] Late> buttons don't send the user to an account.move.line model view anymore but to an account.move model one…
Description of the issue this commit addresses:
Since recently, the <[X] To Pay> and <[X] Late> buttons don't send the user to an account.move.line model view anymore but to an account.move model one but when that change was made, the computation of the number of items on the dashboard was not changed so it was still counting the amount of account.move. line there was in the account.move items that were shown in the view resulting in wrong totals.
---
Steps to reproduce:
1. Install account
2. Create new Vendor Bill with a split payment term ("30% now, Balance 60 Days" for example) on today's date for Bill Date.
3. Go to the dashboard, click the <[X] To Pay> button.
4. the amount of moves in the view that is opened with the button is one above the value of "X" in the button.
This is due to using a split payment term that creates two installment for a single vendor bill hence counting one more aml than there are moves.
---
Desired behavior after this commit is merged:
The right amount of To Pay and Late moves is shown at all times.
---
Enterprise PR: https://github.com/odoo/enterprise/pull/70725
No task
---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-prThe translation button now appears in the correct position when multi-language support is enabled. This improves the editing experience by removing a small visual misalignment that could confuse users working with translations.
Original PR description
Version: - 18.0 Steps to Reproduce: - Install the sign, project, and web_editor modules. - Enable multi-language support. Issue: - The translation button is misaligned. Cause: - The button is positioned using absolute within a div tag, which causes the alignment issue. Solution: - Remove the absolute positioning to fix the alignment. task-4244696
Follow-up emails now attach the Partner Ledger in the customer’s selected language instead of the sender’s language. This helps customers receive account information they can understand and reduces confusion in multilingual collections processes.
Original PR description
If a language is set on the customer when doing the followup, the attached Partner Ledger was always generated in the language of the active user. Instead, if a language is set on the customer, we want to use it.
A previously disabled automated test for the mobile web interface has been re-enabled after the underlying testing issue was fixed. This improves confidence that mobile event handling continues to work correctly without changing user-facing behavior.
Original PR description
Since the fix in HOOT was merged the test can actually be run. https://github.com/odoo/odoo/pull/183099
Fixed an error that could stop recruitment data extraction when adding candidate skills. The system now uses the correct candidate reference, helping recruiters avoid failed or interrupted candidate processing.
Original PR description
Error is generated because ``applicant_id`` field is used to create record of ``hr.candidate.skill`` model. Error: ``ValueError: Invalid field 'applicant_id' on model 'hr.candidate.skill'`` https://github.com/odoo/enterprise/blob/0c7c006dcd0ba53ff9a7aa8ca2446794505a6916/hr_recruitment_extract/models/hr_candidate.py#L60-L61 Here, ``applicant_id`` field is used instead of ``candidate_id`` field. sentry-5983999720
The dashboard now shows accurate counts for bills waiting to be paid or overdue, including bills with split payment terms. This helps users trust the dashboard figures and avoid confusion when opening the related bill lists.
Original PR description
Description of the issue this commit addresses: Since recently, the <[X] To Pay> and <[X] Late> buttons don't send the user to an account.move.line model view anymore but to an account.move model one…
Description of the issue this commit addresses:
Since recently, the <[X] To Pay> and <[X] Late> buttons don't send the user to an account.move.line model view anymore but to an account.move model one but when that change was made, the computation of the number of items on the dashboard was not changed so it was still counting the amount of account.move. line there was in the account.move items that were shown in the view resulting in wrong totals.
---
Steps to reproduce:
1. Install account
2. Create new Vendor Bill with a split payment term ("30% now, Balance 60 Days" for example) on today's date for Bill Date.
3. Go to the dashboard, click the <[X] To Pay> button.
4. the amount of moves in the view that is opened with the button is one above the value of "X" in the button.
This is due to using a split payment term that creates two installment for a single vendor bill hence counting one more aml than there are moves.
---
Desired behavior after this commit is merged:
The right amount of To Pay and Late moves is shown at all times.
---
Note on the fix:
The fix for this issue is in the community PR of the bundle, the fix modifies a method which was overriden in enterprise and this PR addresses the override to match with the new version of the method.
---
Community PR: https://github.com/odoo/odoo/pull/181535
No task