Thursday, September 4, 2025
12 changes · 18.0
Resolved issues and error corrections
When selling event tickets through Point of Sale, company names entered in registration questions are now correctly carried over to the event registration. This prevents missing attendee company information in the backend after a sale is validated.
Original PR description
Steps to reproduce: 1. Add a question to an event with type 'Company'. 2. Sell a ticket for that event in a POS, making sure to fill in the company question. 3. Validate the sale 4. In the backend, check the new event registration that was created. EXPECTED: The company name you filled in is saved to the registration. ACTUAL: The company name is blank. There were three things that needed to be fixed in order for the company name to work: 1. Use `company_name` instead of `company` on the JS side 2. Add `company_name` to the list of loaded POS fields 3. Tell the POS that `company_name` is not computed (this was already being done for name, email, phone) --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Live chat agents now see a visitor's recent page visit times in their own timezone instead of UTC. This makes the visitor context banner easier to understand and helps agents respond with accurate timing information.
Original PR description
Before this PR, when browsing a website livechat in the discuss app, the banner containing the 3 last pages browsed by the user showed the utc time instead of the time in the timezone of the agent. Now, the livechat agent is seeing the visit timings in his timezone. To achieve this, we now construct the visit string in the frontend and receive the page and datetime (utc) info from the backend task-4937769 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Restaurant point-of-sale users can now perform Cash In/Out actions even when they are not on the product screen. This prevents an unexpected error caused by having no active selected order in that context, making cash handling more reliable during service.
Original PR description
Before this commit, performing a Cash In/Out operation in a restaurant while not on the product screen caused an error, as there was no selected order in that context. opw-5042755 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
When users switch from a website page into the website management area, the system now keeps the selected debug mode active in the main interface. This avoids confusion for administrators and support teams who rely on debug mode to diagnose or configure website behavior.
Original PR description
Before this commit, the debug mode was not correctly applied in the website backend when navigating from a website page. While the `?debug=assets` URL parameter was present, the debug mode was only active within the website's iframe, not the main backend interface itself. Steps to reproduce: - Go on a website page - Enter debug mode by adding `?debug=assets` to the URL (not ctrl+k) - Click on editor on the top left to navigate to website backend - Check with `odoo.debug` in console - Debug is activated in the iframe not in the backend
This fixes a crash that could happen when running Odoo tests with certain external test tools if no test tag setting was provided. It helps CI test reports run reliably without affecting normal business workflows.
Original PR description
Description of the issue/feature this PR addresses: The issue arises when using pytest (to get junit xml for CI) with [pytest-odoo==1.0.1](https://github.com/camptocamp/pytest-odoo) ``` run_tests def get_method_additional_tags(self, test_method): run_tests """Guess if the test_methods is a query_count and adds an `is_query_count` tag on the test run_tests """ run_tests additional_tags = [] run_tests > if 'is_query_count' in odoo.tools.config['test_tags']: run_tests E TypeError: argument of type 'NoneType' is not iterable run_tests run_tests ../custom/src/odoo/odoo/tests/common.py:778: TypeError ``` Info @wt-io-it --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#225496
This update improves the internal Hoot testing tools used to validate Odoo, making automated tests faster, cleaner, and easier to diagnose when failures happen. The changes are limited to unit testing infrastructure, reducing risk to normal business workflows while helping developers maintain quality more efficiently.
Original PR description
## Pull Request HOOT (PRHOOT) 36 This pull requests brings various improvements and fixes to Hoot and the Odoo unit test ecosystem. See the different commit messages for more details. Note: these changes are made in stable to avoid having to support multiple versions of the HOOT API. As such, these changes are intended to be strictly limited to unit tests as to not put the rest of the code base at risk. Enterprise: https://github.com/odoo/enterprise/pull/93167 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fixes an issue where checkbox-style many-to-many fields did not pass needed context when looking up available records. It helps ensure those fields show the correct choices in cases where business rules or related records depend on context settings.
Original PR description
**Description of the issue/feature this PR addresses:** When `name_search` is called, the `context` is not passed to the method. In some cases, this is necessary, for example, if the field is related to `ir.attachment` and you want to pass `skip_res_field_check` in the context (see https://github.com/OCA/social/pull/1672). **Current behavior before PR:** The `context` is not passed to `name_search`. **Desired behavior after PR is merged:** Ability to pass `context` to `name_search`. From #215420 Forward-Port-Of: odoo/odoo#216588
A new automated test helps ensure contact tags can be searched without causing an error. This reduces the risk of a previous issue returning and supports smoother contact management.
Original PR description
Add basic test case for PR https://github.com/odoo/odoo/pull/221866 to ensure that the _search_display_name method on res.partner.category returns a list domain
The dialog for creating a new website now displays the title "Add Website". This makes the action clearer for users and improves consistency in the website setup flow.
Original PR description
The modal used to create a new website was missing a title. This commit fixes the issue by setting its header to "Add Website". Forward-Port-Of: odoo/odoo#225302
When a recruitment candidate is turned into a contact, Odoo now uses the candidate’s actual name instead of their email address as the contact name. Related point of sale loyalty tests were adjusted to reliably find customers before selecting them, reducing false test failures.
Original PR description
**Steps to reproduce:**
1. Install hr_recruitment
2. Go to the Candidates menu from Applications in recruitment
3. Create a candidate with both a name and an email
4. Search for the email in Contacts
**Issue:**
The created contact uses the email address as the name instead of the candidate’s name.
**Cause:**
The `find_or_create` method for partners was called without passing the candidate’s name in the parameter.
**Solution:**
Embed the candidate’s name into the email string ('Name <email>') so `find_or_create` creates the partner with the correct name.
**Additonally** some test cases were failing in pos_loyalty due to not loaded partners
so added the extra step to search customer before clicking in on the customer.
Ref commit with same issue where alphabatically low ranked partners doesn't loaded:
https://github.com/odoo/odoo/commit/25e31ac6b7966da73dcdd858322e52d5310cbd98
opw-4953299This update fixes an intermittent failure in an automated Web Studio rename test. It helps keep validation checks stable so development and release processes are less likely to be blocked by false test failures.
Original PR description
The def test_rename function (tour web_studio_main_and_rename) crashed undeterministically because the tour engine is now faster, inputs soimetime do not have the time to update. This commit fixes one instance of this. runbot-error-163471
This update cleans up how Odoo’s internal unit tests access shared testing helpers, making the test ecosystem easier to maintain. The change is limited to test code, reducing risk for regular business workflows while supporting more consistent quality checks.
Original PR description
## Pull Request HOOT (PRHOOT) 36 This pull requests brings various improvements and fixes to Hoot and the Odoo unit test ecosystem. See the different commit messages for more details. Note: these changes are made in stable to avoid having to support multiple versions of the HOOT API. As such, these changes are intended to be strictly limited to unit tests as to not put the rest of the code base at risk. Community: https://github.com/odoo/odoo/pull/221367