Monday, December 16, 2024
18 changes
1 change
Resolved issues and error corrections
Fixes an issue that caused an error when duplicating multiple users at once while the signup module is installed. This helps administrators manage user records in bulk without interruptions.
Original PR description
When we try to duplicate users in the Users section, this error occurs. Steps to reproduce: - Install the ``auth_signup`` module - Go to users and select ``Mitchell Admin`` and ``Marc Demo`` - Now duplicate both of them Traceback: ``ValueError: Expected singleton: res.users(2, 6)`` This error occurs at [1], where we are receiving multiple values in ``self``. This commit will fix the above error by changing the method name from ``copy`` to ``copy_data``. [1]- https://github.com/odoo/odoo/blob/0a52ad52b1a17f2732f92a5e24ec0814d929329b/addons/auth_signup/models/res_users.py#L348 sentry-5635211309 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
3 changes
Resolved issues and error corrections
The Moroccan reports module now allows users to manually edit the Payment Channel even though it is automatically calculated. This fixes cases where the calculated value needs to be adjusted, helping keep payment reporting accurate during upgrades and daily use.
Original PR description
Upgrade PR: https://github.com/odoo/upgrade/pull/6842 task-4226448
This corrects a typo introduced during an earlier code cleanup in the Chilean electronic invoicing integration for Point of Sale. It helps ensure the POS order process continues calling the right function, reducing the risk of failures for businesses using Chilean localization.
Original PR description
Fix : ------- A previous refactor [PR](https://github.com/odoo/odoo/pull/185252) introduced a typo in a function name. This fixes it. Related Community PR: https://github.com/odoo/odoo/pull/189565
Clicking a line in the Accounting amounts to settle view no longer opens a detailed record form. This keeps the view aligned with its intended purpose and avoids confusing navigation for users reviewing unpaid or late invoices and bills.
Original PR description
Description of the issue this commit addresses: The amounts to settle view which is accessible via the accounting dashboard upon clicking on unpaid or late invoice or bills hyperlink and is an modified version of the journal items view has a different behavior than the original journal items view upon clicking a record. In the amounts to settle view, it opens a form view of the record which is not wanted. --- Steps to reproduce: 1. Install Accounting 2. Go to the accounting dashboard with demo data 3. Click on "Late bills" to open the amounts to settle 4. Click on a line 5. A form view opens --- Desired behavior after this commit is merged: When clicking on a record in the amounts to settle view, nothing should happen. --- Note on the fix: This bug happend because a js_class was missing to disable the reactiveness of the record lines. --- task-4164683
13 changes
Resolved issues and error corrections
This fixes an error that could occur in the accounting currency logic after a recent change. It helps keep accounting workflows stable by preventing an unexpected system failure in affected cases.
Original PR description
Fix an UnboundLocalError introduced by c440bb52d19b8dcec8b708509973c4095a577b34
The emoji picker now uses the intended background color so it appears correctly when dark theme is enabled. This fixes a visual inconsistency from a previous backport and keeps the picker easier to read without changing functionality.
Original PR description
Follow-up of https://github.com/odoo/odoo/pull/190586 Backport mistakenly removed the `.bg-view` on EmojiPicker rather than replacing it to `.bg-100`. As a result, the style of emoji picker is off in dark theme. White theme color is slightly off but the difference is barely visible, so this is a non-issue in white theme. This commit makes the correct intended change: replace `.bg-view` by `.bg-100`. Also in master the component PickerContent is no more, but in 18.0 we have to take into account for the overall bg-color. This commit also makes this change. Before <img width="307" alt="Screenshot 2024-12-16 at 12 48 09" src="https://github.com/user-attachments/assets/f4bc0a49-9e63-43c6-acb5-1fb2c41bb0fb" /> After <img width="306" alt="Screenshot 2024-12-16 at 12 48 36" src="https://github.com/user-attachments/assets/2b2ff197-e0f3-48bd-9830-9715142fbebe" />
This fixes an automated donation checkout test so it now confirms that the donation process has fully completed. The change helps prevent false test failures, improving confidence in website payment quality without changing the customer-facing donation flow.
Original PR description
In this commit, we fix the tour test_01_donation by adding a final step that attest the donation has successfully completed. By adding this final step, we avoid a "failed to fetch" type error. 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 fixes an internal automated test so it checks the intended device-detection path after route names changed. It helps ensure the test properly verifies that no tracking trace is created when the session flag disables it, reducing the risk of unnoticed regressions.
Original PR description
The `test_detection_no_trace_mechanism` test checks that no trace is created with the flag in the session. Commit 7aa53005688291a6c903ba759f76574cd35bff77 renamed the routes in `test_http`. This test does not fail, because even if the route does not exist, no trace is created. It is necessary to correct the route so that the test covers the use of the flag in the session.
The Sign module now ensures its guided test tour can continue correctly after redirecting to the documents page. This prevents automated checks from timing out, improving reliability without changing normal user workflows.
Original PR description
When tour resume at redirect step, the route is /sign/documents/. For this route, tour js file is not in manifest. Then the tour abort and is not resumed. After this commit, the tour is not aborted and the error "Script timeout exceeded" is avoided.
Installing Website Product Barcode Lookup no longer fails when users have previously removed manufacturer or brand product attributes. This prevents setup interruptions and makes the module more reliable for databases with customized product attributes.
Original PR description
Currently an error occurs when a user deletes 'manufacturer' or 'brand' product attributes and tries to install `website_product_barcodelookup`. error: `Exception: Cannot update missing record 'product_barcodelookup.product_attribute_lookup_5'` This error is generated because at the time of installing above mentioned module, it tries to update the value of the above-deleted product attribute. This commit solves the above issue by using `forcecreate="False"` to bypass record creation if it violates checks. sentry-5771768396
The payroll payment report now uses the correct SEPA credit transfer format instead of the broader ISO 20022 format. This helps ensure payroll payment files match bank expectations and reduces the risk of rejected payment submissions.
Original PR description
The format of the payment report was iso20022 but it should be sepa_ct. Task: 4392276
The Re-Generate button now stays available when the online payment module is installed, so users can still regenerate SEPA payment files when needed. The button remains hidden for online payments, preventing it from appearing where it is not relevant.
Original PR description
This commit ensures the Re-Generate button remains accessible even when the account_online_payment module is installed. Previously, the button would disappear upon installation of the module. The updated logic ensures the button is available for SEPA payments while remaining hidden for online payments. task-4382642
Fixes an issue where sign request emails could fail when linked to a record that does not have a name field. This improves reliability for custom or unusual records connected to signing workflows.
Original PR description
Before this commit the following traceback could be observed if a record did not had any name field and was linked to a sign request: `` 2024-12-16 08:41:09,063 27947 INFO…
Before this commit the following traceback could be observed if a record did not had any name field and was linked to a sign request:
``
2024-12-16 08:41:09,063 27947 INFO 18.0-sale_commission-next-sub-arj odoo.addons.mail.models.mail_render_mixin: Failed to render template: 683 Traceback (most recent call last):
File "<683>", line 44, in template_683
File "<683>", line 12, in template_683_content
AttributeError: 'x_toto' object has no attribute 'name'. Did you mean: '_name'?
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/home/arj/PycharmProjects/worktree/18.0/odoo/addons/mail/models/mail_render_mixin.py", line 415, in _render_template_qweb_view
render_result = self.env['ir.qweb']._render(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/arj/PycharmProjects/worktree/18.0/odoo/odoo/tools/profiler.py", line 306, in _tracked_method_render
return method_render(self, template, values, **options)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/arj/PycharmProjects/worktree/18.0/odoo/odoo/addons/base/models/ir_qweb.py", line 601, in _render
result = ''.join(rendering)
^^^^^^^^^^^^^^^^^^
File "<683>", line 52, in template_683
odoo.addons.base.models.ir_qweb.QWebException: Error while render the template AttributeError: 'x_toto' object has no attribute 'name' Template: 683
Path: /t/p/t
Node: <t t-esc="request.reference_doc.name"/>
```
OPW-ticket: 4366583Resizing a Gantt chart item so its dates would become invalid is now safely cancelled. Users receive a clear warning instead of encountering an error, reducing disruption when adjusting schedules.
Original PR description
This commit fixes an issue with pill resizing: if the result of the resize would have the start date after the end date or the end date before the start date, it would result in an invalid operation error. After this commit, such an operation will only result in being cancelled with a warning notification to explain the problem. task-4320664
Batch payment checks were updated to ensure the feature continues to work even when the full Accounting app is not installed. This prevents related failures and supports smoother use for customers using a lighter accounting setup.
Original PR description
Make sure that the batch payments are working even if Accounting is not installed, related to a fix in community. [runbot-104545](https://runbot.odoo.com/web#id=104545&model=runbot.build.error)
Knowledge articles without a title now receive the expected name when users save changes with the save button. This prevents untitled articles from remaining unnamed and keeps article behavior consistent across save flows.
Original PR description
This commit fixes an issue with the knowledge controller when a record is saved without a name. Usually when an article has no name we ensure that it has the name when saving. One case where this issue wasn't covered is when you save the changes done via the save button. Before, the name of the article wasn't updated if it was not yet set and when they clicked on save. Now, the title is updated according to the logic applied everywhere. task-4398229
Fixed an error that occurred when users started a timer in Timesheets, selected a Helpdesk project, and then chose a task. This restores a missing background field so task selection works normally and reduces disruption for service teams tracking time.
Original PR description
Steps to reproduce: - In Timesheets app, go to kanban view. - Start the timer. - Select any Helpdesk project. - Try to select a task. Issue: - A traceback is thrown. Fix: - It is due to the fact that company_id field is removed from the kanban xml. - Thus not getting the value is throwing out a traceback. Solution: - Inject back the field into the kanban view. Issue from the PR: https://github.com/odoo/odoo/pull/172375 task-4382051
1 change
Resolved issues and error corrections
This update corrects a formatting issue within the WhatsApp composer, ensuring phone numbers are correctly displayed without spaces or dashes. Previously, incorrect formatting caused errors preventing message delivery and channel linking. Now, users can reliably send WhatsApp templates from within Odoo.
Original PR description
**Before this Commit :** - When using the whatsapp composer on a record to send a whatsapp template, the number (phone/mobile) taken from the partner comes with the phone widget format (including spaces and dashes). - This would cause an error when linking the response received to the associated record, thus not creating an associated whatsapp channel, printing a link to the related SO,lead,etc and not posting a message on the record with a link to the whatsapp channel. **With this Commit :** - The composer phone field has the correct format when opened, preventing this behaviour to occur.