Thursday, March 26, 2026
38 changes · saas-19.1
Resolved issues and error corrections
This update fixes a minor issue where many search dialogs within the Web Studio tool lacked clear titles. Now, most of these dialogs display meaningful titles, improving the user experience and making it easier to navigate and understand the available options. This enhancement ensures a more intuitive workflow for users creating and modifying web applications.
Original PR description
Before this commit, a lot of search More dialogs did not have a meaningful title because one parameter was usually not set. After this, most or all the selectCreateDialog have a meaningful title task-5932652 Forward-Port-Of: odoo/enterprise#111948
This update corrects a minor issue related to how fields are populated when creating new records in Odoo. Specifically, it ensures that the correct model is used during the filling process. This enhancement improves data accuracy and reliability within the system.
Original PR description
See https://github.com/odoo/odoo/pull/199647. Forward-Port-Of: odoo/enterprise#111898 Forward-Port-Of: odoo/enterprise#109725
This update prevents the entire reports cron job from stopping if an error occurs during a single report export. Previously, a single failure would halt the entire process. Now, the cron will continue to attempt exporting other reports, improving reliability and ensuring timely report generation.
Original PR description
If an error is raised during the export of reports cron execution, the whole cron stops due to the fact that the error is never catched This commit will ensure that even if there is an error with one of the report export, the cron won't top and will try to send to other documents task-5469038 Forward-Port-Of: odoo/enterprise#111732 Forward-Port-Of: odoo/enterprise#105191
This update addresses a security concern by hiding the total due amount from minimal cashiers when viewing partner lists. This prevents cashiers from inadvertently accessing sensitive financial information, enhancing data protection and privacy. The change was implemented as a bug fix.
Original PR description
Before this commit, the total due amount was visible for minimal cashier in the partner list. This could leak sensitive information to the cashier, which is not desirable. opw-6039529 Forward-Port-Of: odoo/enterprise#111103
This update resolves an issue where users couldn't add reactions to messages within the ‘mail.group’ model in Discuss. The fix ensures the ‘add reaction’ button isn't displayed for message types that don't inherit from the standard ‘mail.thread’ model, improving stability and usability.
Original PR description
Steps to reproduce: - Install the mail_group module - Open Discuss - Go to the History tab - Add a reaction on a message that has model mail.group - Throws an error The error occurs because the mail.group model does not implement the `_get_allowed_access_params()` method, which is invoked during the process here. Actually, the "add reaction" button should not be shown on messages whose model does not inherit from mail.thread. This commit fixes the issue by hiding the "add reaction" button on messages with models that don’t inherit from mail.thread, such as `mail.group`. community: https://github.com/odoo/odoo/pull/218615 Task-5098050 Forward-Port-Of: odoo/enterprise#111919 Forward-Port-Of: odoo/enterprise#111271
This update resolves an issue where the HR Work Entry Attendance module could only record a single attendance event. Now, multiple attendance records can be created for a single work entry, providing a more accurate and flexible way to track employee time. This improves the system's ability to capture complete attendance data.
This update fixes a discrepancy in the generation of SEPA payment files. The system was incorrectly displaying an empty field for a critical version number, which has now been corrected to PAIN 09. This ensures accurate and compliant payment file creation.
Original PR description
https://github.com/odoo/enterprise/commit/80f9f966d7db793ae82e65c76514323cb10e34ab tried to fix the issue, but assumed the field would be returned empty by the ORM when the value was inconsistent with the db. It's not true: it returns the database value ; only the UI shows the field as empty. Forward-Port-Of: odoo/enterprise#112141
This update addresses a security vulnerability where automated email systems (like Mail Defender) could unintentionally cancel or reschedule appointments. The system has been updated to replace direct links with a form, preventing these automated systems from triggering actions. This ensures appointment scheduling remains reliable and secure.
Original PR description
…ointments Mail defender services may click URLs in emails to verify their contents. Additionally they may sometimes interact with the page and visit related pages. For this reason URLs sent in emails should not trigger any action directly nor contain any simple link that could trigger an action. The "cancel/reschedule" anchor URL is replaced with a form which bots should not click. We also port the fix done in appointment to the view in appointment as it replaces the original view in this module. task-4555579 Forward-Port-Of: odoo/enterprise#112040 Forward-Port-Of: odoo/enterprise#79831
This update resolves a minor issue where the helpdesk tour occasionally failed due to the tour attempting to click a button before the kanban view was fully loaded. By ensuring the kanban view is fully rendered before the tour attempts to interact with it, this fix improves the overall stability and reliability of the helpdesk tour experience.
Original PR description
This PR fixes a flickering failure in the `helpdesk_tour` ### Problem In the kanban view, the tour occasionally tried to click the "New" (quick create) button before the view's internal structure was fully painted. This caused the tour to click a wrong element. ### Solution Updated the step trigger to include a selector for the kanban group (`.o_kanban_group`). By requiring the presence of the group container, we ensure that: 1. The page content has actually loaded. 2. The specific "New" button within the kanban context is visible and ready. **Runbot ID: 223081** Forward-Port-Of: odoo/enterprise#110333
This update corrects a technical issue where the system incorrectly limited VAT number lengths when integrating with FedEx. The change ensures that VAT numbers, particularly those used in countries like Switzerland with longer formats, are properly transmitted to FedEx, preventing delivery errors. This ensures accurate shipment processing and avoids potential disruptions.
Original PR description
Issue ----- Fedex limits VAT numbers to 18 char long strings. This is contradictory with how they are stored in db for some countries (eg Switzerland, where the format is CHE-123.456.788 VAT -> 19 char long). Steps to reproduce ----- - Setup Fedex - Create a customer - Company (for VAT number) - VAT number: CHE-123.456.788 TVA - Create a delivery and confirm it Cause ----- VAT number is retrieved as is in https://github.com/odoo/enterprise/blob/0220d413988708c662ffca3c7fb38641c3d9870a/delivery_fedex_rest/models/fedex_request.py#L332-L343 ----- Ticket: opw-5926452 Forward-Port-Of: odoo/enterprise#111864 Forward-Port-Of: odoo/enterprise#109999
This update resolves an issue where only administrators could delete work entry types within the payroll module. Now, users with SUPERUSER permissions can also delete these types, streamlining payroll administration. This change improves operational efficiency and reduces reliance on technical support for this task.
Original PR description
Forward-Port-Of: odoo/enterprise#111967
This update corrects a problem in the demo data for the l10n_ch_hr_payroll module, specifically removing an incorrect record and fixing a reference to the insurance line within the insurance group. This ensures the demo data accurately reflects the module's functionality and improves the reliability of testing.
Original PR description
This commit removes an unnecessary record and fix wrong reference to the insurance line of the insurance group in the demo data of the l10n_ch_hr_payroll module. task-6070942 Forward-Port-Of: odoo/enterprise#112121
This update resolves a minor issue in the Belgian payroll module (l10n_be_hr_payroll) that could occasionally lead to incorrect reporting of termination holidays. The fix ensures that the system correctly handles cases where specific property settings are missing, improving the accuracy of payroll reports.
This update fixes a display issue in the external value pop-up, ensuring it uses the correct decimal separator based on the user's language settings. Previously, the pop-up always used a dot, regardless of the user's locale. This change ensures numbers are displayed correctly for all users, improving data clarity and accuracy.
Original PR description
Description of the issue this commit addresses: The external value pop up doesn't take into account the locale to chose which decimal separator to use. --- Desired behavior after this commit is merged: The decimal separator is the one determined by the language of the user rather than always a dot. --- task-6010533 Forward-Port-Of: odoo/enterprise#111997 Forward-Port-Of: odoo/enterprise#109948
This update resolves an issue where attachment updates for invoices were sometimes failing, leading to inconsistencies in the system. By updating attachments within the same transaction as the move data, this change guarantees that both updates are reliably committed, maintaining data integrity. This ensures accurate invoice processing.
Original PR description
Was committing the move fields update, then updating the attachment. This might create an issue were the move update commits successfully, but setting the attachment fails and we end up with an inconsistency. Set attachment in the same transaction as the move update. task-6035727 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#255745 Forward-Port-Of: odoo/odoo#255262
This update resolves an issue where the interactive tour pointer would disappear when navigating between different elements, particularly within modals. The fix ensures the pointer remains visible and functional regardless of the currently active element, improving the user experience. This enhancement guarantees consistent tour guidance for all users.
Original PR description
Before this commit, the pointer disappeared when the active element change before the anchor of the tour pointer. So, it was not visible in modals for example. Now, the check is done when the active element change and when the isVisisble is read. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#252019
Previously, a select dialog opened from a record selector or relational field would display an incorrect title ('Search: undefined'). This fix ensures the dialog title is set to 'Search' when the expected information isn't available, providing a cleaner and more user-friendly experience. This resolves a minor visual issue.
Original PR description
…e title When opening a selectCreateDialog from a record selector or a relational field, when no (or empty) fieldString was passed to form the dialog's title , an ugly `Search: undefined` was set as the title After this commit, if we don't receive the right props, we simply set the title to `Search` part-of-task-5932652 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 Forward-Port-Of: odoo/odoo#255777
This update fixes a 404 error that occurred when users accessed public website content without logging in. The issue stemmed from how the system determined the user's website context, leading to incorrect access control. This change ensures that public website content is correctly displayed to users.
Original PR description
\* = test_website_modules ### Issue: When accessing a record from the website without logging in, a `404` error occurs if a public record rule filters records by website related domain, for example…
\* = test_website_modules
### Issue:
When accessing a record from the website without logging in, a `404`
error occurs if a public record rule filters records by website related
domain, for example `[('website_id', '=', website.id)]`.
### Steps to reproduce:
- Install the 'website_blog' module and create at least one website.
- Enable debug mode.
- Go to Settings > Technical > Database Structure > Models.
- Open the `blog.post` model.
- Go to the 'Record Rules' tab.
- For the record 'Blog Post: public: published only', change the domain
from `[('website_published', '=', True)]` to
`[('website_id', '=', website.id)]`.
- Go to Website > Configuration > Blogs.
- Open a blog (e.g., Travel).
- Select 'My Website' in its 'Website' field.
- Open 'My Website' without logging in.
- Click on the 'Blog' menu and the blog listing will appear correctly.
- Try opening a blog post and a `404` error occurs.
### Reason:
<pre>
┌─────────────────────────────────────────────────────────┐
│ Request Lifecycle │
├─────────────────────────────────────────────────────────┤
│ │
│ User Request (not logged in) │
│ ↓ │
│ ┌──────────────────────────────────────┐ │
│ │ 1. _pre_dispatch │ │
│ │ ↓ │ │
│ │ check_access_rule │ │
│ │ ↓ │ │
│ │ _eval_context (compute domain) │ │
│ │ ↓ │ │
│ │ get_request_website() │ │
│ │ ↓ │ │
│ │ request.website = None │ ← Issue │
│ │ ↓ │ │
│ │ Domain evaluation FAILS │ │
│ │ ↓ │ │
│ │ Access DENIED → 404 Error │ │
│ └──────────────────────────────────────┘ │
│ ↓ │
│ ┌──────────────────────────────────────┐ │
│ │ 2. _frontend_pre_dispatch │ │
│ │ (NEVER REACHED) │ │
│ │ ↓ │ │
│ │ request.website initialized ✓ │ ← Too Late │
│ └──────────────────────────────────────┘ │
│ │
└─────────────────────────────────────────────────────────┘
</pre>
Because `request.website` is initialized later in
`_frontend_pre_dispatch`, access rules evaluated earlier in
`_pre_dispatch` cannot rely on website context. As a result, record
rules depending on `website_id` are evaluated before `request.website`
is available, incorrectly denying access to public records.
### Fix:
Avoid totally relying on `get_request_website` during access rule
evaluation. Use the `request.is_frontend` attribute as a fallback, which
is set earlier, to detect frontend requests and ensure correct access
handling.
task-[4758311](https://www.odoo.com/odoo/project/974/tasks/4758311)
---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Forward-Port-Of: odoo/odoo#255708
Forward-Port-Of: odoo/odoo#213143This update resolves an issue where the POS settlement process would fail when encountering certain line types (specifically `line_subsection`) that didn't contain product information. The fix skips these problematic lines, ensuring the settlement process completes correctly and reliably. This prevents errors and improves the overall stability of the POS functionality.
Original PR description
`line_subsection` lines have no product, so calling `addLineToCurrentOrder` on them raised a TypeError trying to read `taxes_id` of undefined. Skip them early, the same way `line_section` is handled. opw-5949585 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#255360
This update resolves an issue where receipts were displaying company information twice. This change was triggered by a previous commit and has been corrected to ensure receipts accurately reflect the correct company details. This improves the user experience and data accuracy for sales transactions.
Original PR description
Before this commit, the receipt was showing the company information twice. It happened after the commit https://github.com/odoo/odoo/commit/dca40d16481ba504d608cc65d82e7821e01c5932. opw-6053013 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#255368
This update fixes a test failure related to email notifications within the Google Calendar and Mail modules. The previous test incorrectly checked for empty timeout emails, leading to false positives. Now, the test focuses on ensuring no emails are sent for any message, regardless of recipient, improving test reliability.
Original PR description
No need to always check the timeout email_to always contains formatted emails. task-5152917 Forward-Port-Of: odoo/odoo#255635 Forward-Port-Of: odoo/odoo#230766
This update fixes an issue where the image quality slider disappeared when using images with shapes. The change ensures the slider functions correctly regardless of whether the image format or shape options are modified, improving the user experience for images with shapes.
Original PR description
Before this commit, the quality option would not work properly for images with a shape applied by default. After changing an option, the DOM would be updated and the slider disappeared because the…
Before this commit, the quality option would not work properly for images with a shape applied by default. After changing an option, the DOM would be updated and the slider disappeared because the image format would not be considered valid anymore.
Steps to reproduce the issue :
- Drop a snippet with an image with a shape (.s_cta_mockup, ...)
- Do one of the following:
- Move the quality slider
- Change an shape option
=> The Quality slider disappeared.
If the user replaces an image with a png, sets the format to "webp" and adds a shape, the dataset would have the following :
- format-mimetype: the value of the format option ("image/webp")
- mimetype-before-conversion: the original format ("image/png")
- mimetype: the mimetype of an image with shape ("image/svg+xml")
We first evaluate "data-format-mimetype", as it indicates the current format of the image (if it was changed by the user). Otherwise, we check "data-mimetype-before-conversion" since the mimetype for an image with shape is always "image/svg+xml" and doesn't correspond to the real image format. Finally, default to getMimetype to avoid issue for images on which nothing no option was changed.
task-5358952
Forward-Port-Of: odoo/odoo#240360This update corrects a technical issue that prevented users from properly closing the online payment popup in the Point of Sale system. Previously, an error occurred when the popup was closed, disrupting the payment process. This fix ensures a smoother and more reliable payment experience for customers.
Original PR description
Before this commit, when the user closed the online payment popup, an error was raised because the currentOrder was not valid and instead order must be used. opw-6034405 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#255292
This update fixes an issue where Italian VAT invoices were sometimes incorrectly processed due to mismatched withholding reasons. The change broadens the import process to allow taxes with the same withholding type to be used, ensuring accurate VAT calculations for Italian businesses. This resolves a previous bug reported in related tasks.
Original PR description
Some invoice come in with a wrong ENASARCO withholding reason. We now broaden the search to allow taxes with the same withholding type to be used during import even if the withholding reason doesn't match. In the test, I change the Enasarco tax to reason Q to check that it gets correctly assigned. Ticket [link](https://www.odoo.com/odoo/project.task/5175587), [link](https://www.odoo.com/odoo/project.task/5933699) opw-5175587 opw-5933699 Forward-Port-Of: odoo/odoo#255725 Forward-Port-Of: odoo/odoo#236251
This update resolves an issue where a partner's identification type (e.g., tax ID) was incorrectly set based on the partner's country. The fix ensures that the ID type remains consistent with the partner's country selection, preventing errors and ensuring accurate reporting for Latin American businesses. This improves data integrity and compliance.
Original PR description
**PROBLEM** PR: https://github.com/odoo/odoo/pull/179078 Removed _onchange_country_id() which was used to set the identification type according to the country of the partner. This PR reintroduce it, so id type and country remains consistent. **STEP TO REPRODUCE** 1. install l10n_ar and l10n_co. 2. create a new partner. 3. set its country to Argentina, and select an argentinian id type. 4. set the country to Colombia and save. You end up with a partner from Colombia, with a id type that is used for Argentinian partners which shouldn't be possible. opw-5801824 Forward-Port-Of: odoo/odoo#248585
This update ensures that Point of Sale orders are automatically assigned a default preset when one isn't explicitly provided. Previously, orders created without a preset ID wouldn't use the configured default. This change aligns with how other key settings like price lists and fiscal positions are handled, ensuring consistent and reliable order setup.
Original PR description
When a pos.order was created without a preset_id (e.g. frontend order synced before the async preset dialog resolved, or any other path that omits the field), _complete_values_from_session did not fall back to the config's default_preset_id. Apply it the same way pricelist and fiscal position are defaulted, without overriding an explicitly passed value. opw-5997872 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#251934
This update resolves an issue where batch transfer operations would fail due to a problem with how the system parsed sequence identifiers containing forward slashes. The fix ensures that the system correctly handles sequences with multiple slashes, preventing crashes and allowing users to create batches with a wider range of identifiers. This improves the stability and usability of the batch transfer feature.
Original PR description
next_by_code() can return a sequence with multiple '/' in the prefix (e.g. "BATCH/test/00002" or "batch/test/2026/00002"). Using split('/') causes a ValueError: too many values to unpack.
Use rsplit('/', 1) to always split on the last '/' and correctly extract the sequence prefix and number.
Steps to reproduce the bug:
- Go to settings > technical > sequences & identifiers > sequence:
- batch transfer: - prefix: BATCH/test/
- Create a new batch:
- operation type: delivery orders
- Try to save
Problem:
a traceback is triggered:
```ValueError: too many values to unpack (expected 2)```
opw-6043880
Forward-Port-Of: odoo/odoo#255761This update resolves an issue where users couldn't add reactions to messages using the 'mail.group' model in Discuss. The fix hides the reaction button for these message types, ensuring proper functionality and preventing errors. This improves the overall stability of the Discuss feature.
Original PR description
*= im_livechat, portal, test_discuss_full **Steps to reproduce:** • Install the mail_group module • Open Discuss • Go to the History tab • Add a reaction on a message that has model `mail.group` •…
*= im_livechat, portal, test_discuss_full **Steps to reproduce:** • Install the mail_group module • Open Discuss • Go to the History tab • Add a reaction on a message that has model `mail.group` • Throws an error The error occurs because the `mail.group` model does not implement the `_get_allowed_access_params()` method, which is invoked during the process here. Actually, the "add reaction" button should not be shown on messages whose model does not inherit from mail.thread. https://github.com/odoo/odoo/blob/d12c1e07727f9b04cd2be2e7dac1ec3af49cb637/addons/mail/models/mail_message.py#L579 Desired behavior after PR is merged: This PR fixes the issue by hiding the "add reaction" button on messages with models that don’t inherit from mail.thread, such as mail.group. enterprise: https://github.com/odoo/enterprise/pull/111271 Task-5098050 [Reference](https://github.com/user-attachments/assets/aa2c4251-fd1f-4734-a62c-9fc80dd5f587) --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#255744 Forward-Port-Of: odoo/odoo#218615
This update fixes inaccuracies in the tax exemption codes and reasons used for certain taxes within the Odoo Belgium localization. These corrections ensure compliance with Belgian tax regulations and prevent potential issues with tax reporting. The changes were carefully reviewed and validated.
Original PR description
Some taxes had a wrong tax exemption code and tax exemption reason. This commit corrects them. task-4976471 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#253309
A test within the sale_timesheet module was failing due to a missing dependency on the invoicing module. The fix ensures the necessary invoicing module is automatically installed during test execution, allowing the test to run correctly. This prevents disruptions to the testing process.
Original PR description
__ ## Error description When the test runs following a specific configuration, the field `invoicing_switch_threshold` isn't found. However, we have to keep this field in the test because we can't replicate the issue the test checks without it. ## Origin of the issue This field belongs to the `account_accountant` (Invoicing) module. However, `sale_timesheet` doesn't have a dependency on this module: there's only an auto install for `account_accountant` when installing the module from the front-end. Therefore, if we launch the test without the `account_accountant` auto install, it will fail. __ original commit: https://github.com/odoo/odoo/pull/250946/changes/52a9841c754466c2df65c75d13c9ed2ae86a51ce Forward-Port-Of: odoo/odoo#254506 Forward-Port-Of: odoo/odoo#252772
This update resolves an issue where a key function (`get_conf`) was incorrectly imported, causing a minor disruption in the IoT drivers. The import was corrected, and a related call in the main Python file was updated, ensuring proper functionality and stability.
Original PR description
`get_conf` was moved to `system` instead of `helpers`, and a call in `main.py` hasn't been updated in a fw port. This commit fixes it.
This update resolves an issue where pressing the spacebar in certain HTML content could unintentionally create symbols. The fix adjusts how the HTML editor calculates text offsets, ensuring accurate symbol placement and preventing unexpected symbol generation. This improves the overall user experience and stability of the HTML editor.
Original PR description
Problem: Sometimes pressing space in content containing a symbol pattern creates the symbol even when the space is not placed directly before it. Cause: `leftLeafOnlyNotBlockPath` sums the…
Problem: Sometimes pressing space in content containing a symbol pattern creates the symbol even when the space is not placed directly before it. Cause: `leftLeafOnlyNotBlockPath` sums the `spaceOffset` of all non-block leaf nodes, then performs a substring on the whole block containing those leafs. In this case, the file box contains a `span` with `d-flex`, which is considered a block. Therefore, the file box text content length is not included in the `spaceOffset` calculation. However, we later call `substring` on the `textContent` of the `closestBlock`, which includes the file box content. This leads to an incorrect `spaceOffset`, effectively skipping the file box text. This can happen by chance when the `substring` returns the file box text content with `"-->"` immediately after it, making it the last character and triggering symbol creation. Solution: When computing the `substring`, consider only the `textContent` of the leaf nodes traversed while calculating `spaceOffset`. This ensures the offset matches the actual traversed content and prevents accidental symbol generation. Steps to reproduce: - Use the same HTML structure as in the test. - Place the selection as in the test case. - Press space. - Observe that a symbol is incorrectly created. task-6004954 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update resolves an issue where users in incognito mode couldn't download attachments linked within the HTML editor. The fix ensures the necessary access token is included in the download link URL, allowing attachments to be successfully downloaded regardless of the browsing session. This improves the user experience for all users.
Original PR description
# How to reproduce
- Go to the website in edit mode
- Select some text
- Upload and link an attachment to that text
- Open a new incognito tab
- Try to download the attachment
# The problem
An error 404 is displayed
# Why
The access token of the attachment is not correctly added in the link URL. This is because link_popover.js does not correctly call the upload function from the uploadLocalFile services.
The signature of that function is :
```py
async function upload(
{ resId, resModel },
{ accept = "*/*", multiple = false, accessToken = false } = {}
) {
```
opw-5500362
---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Forward-Port-Of: odoo/odoo#251427This update fixes a previous restriction that prevented users from editing taxes on reward lines within confirmed sales orders. Previously, confirming an order would recompute taxes, but now edits can be made to these tax lines after the order is confirmed. This improves flexibility for users managing reward orders.
Original PR description
Issue: --- Due to this issue, the tax on reward SOL cannot be edited. Cause: --- This is introduced in #172110 to prevent users from editing taxes on reward lines because confirming the order would recompute the tax. We can make it editable on confirmed SO as the tax wouldn't recomputed on reward lines later. opw-5918435 Forward-Port-Of: odoo/odoo#255644 Forward-Port-Of: odoo/odoo#255102
This update ensures that users are warned before performing a full synchronization of products in the Point of Sale system. The system now checks if the number of products exceeds a configured limit, preventing potential performance issues and data inconsistencies. This improves the reliability of the POS functionality.
Original PR description
When the user selects "Full" in the SyncPopup, the system now checks the total number of PoS-available products against the configured `point_of_sale.limited_product_count` system parameter before proceeding. opw-5484051 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#243763
This update streamlines the testing process by pre-generating a key asset bundle used by the bus module. Previously, this bundle was rebuilt repeatedly during tests, causing delays. This change significantly speeds up test execution times, improving overall development efficiency.
Original PR description
This commit sets the `bus.websocket_worker_assets` bundle to be pregenerated while running tests to avoid rebuilding it at runtime (i.e. +900 times with a db "all"). Forward-Port-Of: odoo/odoo#255843
This update resolves an issue where Odoo would crash if a module didn't include a manifest file. The system now handles this gracefully, ensuring a more stable experience. This change improves overall system reliability and prevents unexpected downtime.
Original PR description
This commit avoids a crash when a module doesn't provide a manifest (cf. Industry). Pregenerating lazy loaded bundles is a "best effort" detection and should be resilient so, not a big deal if some aren't properly found. Forward-Port-Of: odoo/odoo#256056
This update resolves a technical problem that prevented accurate product cost calculations when multiple companies were involved. The issue stemmed from incorrectly accessing BOMs across different companies, leading to access errors. This fix ensures correct product costing is calculated regardless of the number of companies a user is working with.
Original PR description
When computing the product cost in `_get_product_cost_with_moves`, iterating over `product.bom_ids` would include BOMs from all companies, causing an `AccessError` when the current user lacked read access to a BOM belonging to another company. opw-6060735 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#255859