Friday, January 31, 2025
12 changes · 18.0
Resolved issues and error corrections
Event proposal forms now exclude tags that are meant to stay hidden on the public website. This keeps the tag list cleaner and helps visitors choose only relevant, intended options.
Original PR description
Colorless tags are always hidden in the frontend interface, this allows to manage them in backend without showing them. Since there's no filter on the `websiteEventTrackProposalFormTags` widget, those tags were still selectable from the website, resulting in the following issues: - Adding useless noise in the selection. - Letting users select tags that are not intended to be selected. - Users could also wrongly select a tag instead of the intended one.
This update makes several automated user journeys more dependable by adding checks that keep each test on the intended path. It reduces inconsistent test results across website, events, CRM, and point of sale areas, helping teams validate changes with more confidence.
Original PR description
In this commit, we fix multiple tours on step that can cause non deterministic behaviors by adding additionnal steps to ensure tour is well on the way to taking the right path. 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 fixes an internal test validation issue so JavaScript test failures are detected more reliably. It reduces false failures caused by wording changes in error messages, helping keep development and release checks stable.
Original PR description
Before this commit, the error_checker asserting that a JS unit test run failed performed a strict equality with an outdated string on error logs. Now, the message has been changed, flagged explicitly as something that shouldn't be changed and the presence of that message is checked accross the entire message for robustness. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update removes two unrelated steps from an automated web test that had been copied in by mistake. It helps keep the test suite clearer and easier to maintain, with no expected change for end users.
Original PR description
Commit https://github.com/odoo/odoo/commit/98218629f88b619ca9c8013ecbffaa221d82531c introduced a test with two non-related steps (these steps were certainly copy-pasted from another test, in spreadsheet). This commit removes these steps. 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
Restaurant point-of-sale users can now create a new floor plan by clicking anywhere on the create button, not just the plus icon. This removes a small usability frustration and makes setup more intuitive.
Original PR description
Before this commit: ========== - To create a new floor plan, the user must click the plus icon on the floor plan's create button; clicking anywhere else on the floor plan's create button was not working. After this commit: ========== - Users can click anywhere on the floor plan's create button to create a floor plan. task-4517219
Point of Sale reports now avoid showing duplicate order lines when a sold product belongs to multiple POS categories. This keeps sales reporting clearer and prevents inflated or confusing report details for affected products.
Original PR description
If you sell a product that has multiple pos categories, the report would contain as many lines as the number of categories. Steps to reproduce: ------------------- * Create product A with atleast 2 pos categories * Make a sale in PoS with this product * Go to PoS order report and click on the graph * This will open a view containing all the lines of the report > Observation: You have multiple lines for the same order Why the fix: ------------ To avoid this issue, we select only the first category of the product. opw-4451101
This fix prevents Odoo spreadsheets from unnecessarily reloading pivot data when a global filter is changed. Users get a smoother spreadsheet experience with fewer interruptions while working with filtered business data.
Original PR description
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 Point of Sale sample setup no longer triggers an error when users reopen the Clothes section after deleting the Clothes Shop. This prevents confusing log errors and keeps the POS setup flow working smoothly.
Original PR description
Currently a `Parseerror` appears when the user clicks 'Clothes' in POS. ### Error: ``` ParseError while parsing /home/odoo/src/odoo/18.0/addons/point_of_sale/data/scenarios/clothes_data.xml:337 A combo choice can't contain duplicate products. View error context: '-no context-' ``` ### Steps to reproduce above error :- - Install 'Point of Sale' (without demo data). - Open POS and click 'Clothes', then delete 'Clothes Shop'. - Click again 'Clothes'. - The error appears in the log. This commit resolves the issue by using `Command.clear()`, to clear the link before creating the combo products. sentry-6191520798
The dashboard no longer shows the bank selection prompt when a journal is already linked to a bank account. This avoids confusing users with an unnecessary setup option and keeps the banking dashboard clearer.
Original PR description
The aim of this commit is making sure that we don't display the bank selection in the dashboard if the journal is already connected to a bank account. no task id
This fix addresses two recurring nightly test failures in the Kenya OSCU localization and its Point of Sale integration. It removes an unnecessary dependency trigger and adjusts access handling so validation information can be read reliably by the right users.
Original PR description
This commit fix 2 tests who nightly fails on runbot: Test 1, `test_01_orders_no_invoiced` (https://runbot.odoo.com/odoo/runbot.build.error/111519): This test failed because of a `flush_all()`, who raised an error because of an `api.depends_context` on a computed field in `product_template` Solution: remove the `api.depends_context` as he's useless (the compute still trigger as it should) Test 2, `test_read_purchase_order` (https://runbot.odoo.com/odoo/runbot.build.error/111518): This test failed because of access right error Solution: add a compute_sudo on `l10n_ke_validation_message` field and add a `groups="point_of_sale.group_pos_user"` on account_move view. no-task
Subscription totals are now calculated more accurately when orders include multiple lines with tax-included prices. This prevents small rounding discrepancies, especially in certain foreign currencies, so recurring and non-recurring amounts shown to users match the expected billed values.
Original PR description
Subscriptions with multiple lines and tax-included prices introduced a rounding error in some cases. This commit fixes the _compute_recurring_total method by using the same rounding method as _compute_amounts in the sale/ module, based on AccountTax helper methods. opw-[4460812](https://www.odoo.com/odoo/all-tasks/4460812)
The Documents app now correctly highlights the Info & Tags button when users open it from the cog wheel menu. This makes the interface clearer and keeps the button state consistent across the document view.
Original PR description
Steps to reproduce: 1. Click the 'Info & Tags' button from the cog wheel dropdown menu next to the breadcrumb. 2. The info button on the right side (near the view switch button) is not getting the 'active' class as it should be. Technical Reason: `this.documentsState.isChatterVisible` in `documents_control_panel` couldn't be updated through the cog menu component directly. This commit adds a reactive object which can be modified and observed by several components. After this Commit: The Button will get the 'active' class accordingly to the state. This commit also removes duplicate code by using an existing mixin. Task-4427575