Daily updates from Odoo
Wednesday, January 29, 2025
13 changes
Resolved issues and error corrections
The web tour test suite has been re-enabled after being temporarily disabled to unblock an earlier release process. This helps improve confidence that guided tour behavior continues to work correctly, while avoiding an issue that interfered with the test engine.
Original PR description
In [1], we commented out the tour_automatic unit test file in the manifest to merge this PR as soon as possible. In this commit, we uncomment this file. The solution is to not patch browser.console because it can cause big problems in the Hoot unit test engine.
This fix prevents an internal error from occurring when Odoo tries to show a company-related warning. The warning can now be logged correctly, improving reliability in situations where company consistency checks are triggered.
Original PR description
Description of the issue/feature this PR addresses: In the company check warning message, self.model_name was used instead of self._name. Current behavior before PR: model_name is not an attribute of the class BaseModel, which causes an AttributeError when the warning message is triggered. Desired behavior after PR is merged: Warning message correctly logged without having an error. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fixes an issue where invoice identifiers could appear repeatedly in accounting report line names when the same sequence was used as both customer and payment reference. The report now avoids duplicate wording, making entries easier to read and reducing confusion for accounting users.
Original PR description
### Steps to reproduce: - Go to Accounting > Reports > Aged Receivable - Unfold any customer shown, click on the three dots next to an invoice, and select "View Journal Entry" - On the Journal Entry,…
### Steps to reproduce:
- Go to Accounting > Reports > Aged Receivable
- Unfold any customer shown, click on the three dots next to an invoice, and select "View Journal Entry"
- On the Journal Entry, add the invoice sequence to Customer Reference and Payment Reference
- Go back to the report, you should see the invoice name is now shown 4 times
### Cause:
The bug appeared in this commit (https://github.com/odoo/odoo/commit/eb872c09897eb9edd5b6e5b9e8171fa6764be3dc). When computing the line `display_name`, if there is a name, a reference and `line_name`. The variable line_name already include the reference:
`name = f'{line.move_id.ref} - {line.move_id.payment_reference}'` (https://github.com/odoo/odoo/commit/a6cbb7c2d3538d57dc8498f0dacf4566ea1492e7)
So `line_name` is different from `move_name` and the result is:
`line.move_id.name (line.move_id.ref) line.move_id.ref - line.move_id.payment_reference`
### Solution:
Check if the move_ref and the payment ref are the same, in that case only put one of the two as line_name. Then when computing the display_name, line_name will equal to move_name so line_name will not be included.
opw-4492298This fixes an issue where the user switch option could disappear on the login page when debug mode was enabled. Users can now switch between recently used accounts reliably while troubleshooting or testing.
Original PR description
**Description of the issue/feature this PR addresses:** The user switch component fails in debug mode with the following error in the console log > Error message: > OwlError: Got duplicate key in t-foreach: [object Object] > at UserSwitch.template This error happens because we are using the user object as a key ([object Object]), instead we should use the user_index **Current behavior before PR:** 1. Open a runbot 2. Log in and log out with admin account 3. Log in and log out with demo account 4. The user switch component appears on the login page 5. Adding ?debug=1 to the URL causes: - User switch component disappears - Console shows duplicate key error **Desired behavior after PR is merged:** - Having possibility to use switch user component in debug mode --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The autocomplete dropdown now keeps the highlighted option visible when users move through long lists with the keyboard. It also closes consistently when tabbing backward, making form navigation more predictable and reducing user frustration.
Original PR description
When the list of sources is longer than the `<AutoComplete>` height, navigating with the arrow keys did not scroll the menu. This commit makes sure the active option is always in focus and visible. task-3758859
The website editor no longer shows an unnecessary help tooltip beside the option to serve custom fonts from Google servers. This reduces confusion for internal users configuring website fonts, without changing any website behavior.
Original PR description
Steps to reproduce: 1. Open website app 2. Click edit 3. Click on "Font Family" 4. Click on "Add a Custom Font" 5. Click on the question mark tooltip showing next to "Serve font from Google servers" - Removed the tooltip since the form is only accessible internally and not relevant to all users. This was only added in v18+ --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update prevents a Point of Sale crash that could happen when missing information was processed. It makes checkout-related data handling more reliable and helps avoid interruptions for users.
Original PR description
The error was caused by calling .trim() on a variable that could be undefined. This commit adds a check to ensure the variable is defined before calling .trim()
The product configuration screen now respects the same editor setting that hides or shows the quantity selector on product pages. This keeps the shopping experience consistent and prevents customers from seeing a quantity button that the business intended to hide.
Original PR description
version: 18.0 Issue : When the "Select Quantity" button is hidden on the product page via the editor, it remains visible on the product configuration page. Fix: Added a condition for showQuantity to ensure the visibility of the "Select Quantity" button is consistently managed on both the product page and the product configuration page. With this fix, the visibility of the "Select Quantity" button can now be properly controlled for the product configuration page as well, aligning with the editor's settings. opw-4316784
This fixes a problem where partner autocomplete could fail during company onboarding because a required identifier was missing from the relevant company form. It also avoids problems when the autocomplete feature is later uninstalled, keeping the setup more reliable for businesses using or removing this option.
Original PR description
`partner_gid` was missing from `res_company_form_view_onboarding` view which was creating a bug when applying the partner autocomplete. Rollback of odoo/195000 as it created issues if you uninstalled `partner_autocomplete`. The field will still be present in the view, but it wouldn't exist in the database. opw-4489441 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Users can now open IAP accounts even after the SMS module has been uninstalled. This prevents an unexpected error caused by SMS-specific account data remaining after the module is removed.
Original PR description
A traceback occurs when the user tries to open IAP accounts after uninstalling the SMS module. To reproduce: 1) Install hr 2) open IAP accounts from settings/technical/iap/iap accounts 3) Create a…
A traceback occurs when the user tries to open IAP accounts after uninstalling the SMS module. To reproduce: 1) Install hr 2) open IAP accounts from settings/technical/iap/iap accounts 3) Create a new iap account with service as `SMS` 4) Uninstall `SMS` module 5) Try to open the iap accounts again Error:- ``` ValueError: Invalid field 'sender_name' in 'iap.account' ``` This error occurs from the below line https://github.com/odoo/odoo/blob/1e7c2ca8c929d15c9015b960f7fcbe4560413e98/addons/iap/models/iap_account.py#L128 Because when the user creates an iap account with service_name as `SMS`, We include `sender_name` in the dict of updating fields. https://github.com/odoo/odoo/blob/1e7c2ca8c929d15c9015b960f7fcbe4560413e98/addons/iap/models/iap_account.py#L123-L126 But, the `sender_name` field is defined in the SMS module, So it will lead to the above traceback as the `SMS` module is uninstalled. https://github.com/odoo/odoo/blob/1e7c2ca8c929d15c9015b960f7fcbe4560413e98/addons/sms/models/iap_account.py#L9 sentry-6249864173
The scheduled payment status check now runs only when there are payments that actually need checking. This reduces unnecessary background activity and helps keep online payment processing more efficient without changing the user experience.
Original PR description
The aim of this commit is making sure cron that runs every 6 hours and which checks all the payment status is only used when we do have payment that needs to be checked. no task id
This fixes a missing return in the Chilean electronic invoicing point-of-sale flow. It helps ensure POS order data is passed back correctly, reducing the risk of interrupted or incomplete processing for Chilean sales receipts.
Original PR description
The return was forgotten in a previous commit for an override of the `read_pos_data` method in the `pos_order` model.
This update hides certain Shopee-related fields unless debug mode is enabled, reducing clutter and preventing accidental changes in normal use. It also lets users manually choose which products should have their inventory synced, improving control over stock updates.
Original PR description
Commit 6845ca19567577f70910ed269f91232453c93b20 let some fields visible in the view where they should only be available in debug mode. Also allows to manually change which product should have its inventory synced.