Tuesday, November 12, 2024
18 changes
3 changes
Resolved issues and error corrections
This fix prevents users from accidentally creating new field definitions from quick-create options in selected automation and data cleanup screens. It avoids confusing errors and keeps configuration choices limited to valid existing fields.
Original PR description
\* = base_automation_hr_contract, data_cleaning, marketing_automation Quick create an `ir.model.fields` should not be possible in the UI, This commit prevents it instead of raising an error see https://github.com/odoo/odoo/pull/186295#pullrequestreview-2417762562 community pr: https://github.com/odoo/odoo/pull/186738
This fix prevents financial report export settings from being recalculated unnecessarily when reports are exported as files. It helps ensure comparison data remains consistent during file exports and reduces the risk of incorrect report output.
Original PR description
This commit add a condition for the generation of options. If the report is exported in export_mode = file, we don't re-compute the options for the comparison.
Fixed an issue that could cause an error when exporting from Web Studio due to an unsupported field format. The export configuration now uses a compatible format, helping users complete exports without interruption.
Original PR description
Issue: ====== 'domain' widget used on field `domain` does not support Text type thus giving validation error. After this commit: ================== Changed data type of `domain`field to Char, supported in 'domain' widget. Task-4319471
10 changes
Resolved issues and error corrections
A small typo was corrected in the Live Chat chatbot setup logic. This helps ensure chatbot step information is stored consistently and avoids issues caused by the earlier typo.
Original PR description
This PR fixes a typo introduced by this commit ce0f8d9e608acdcc6fd8495e7b9cd8f7d2757349. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
5 changes
Resolved issues and error corrections
This pull request reverts a recent change that displayed general ledger reports using invoice dates instead of the actual accounting date. This ensures reports accurately reflect the date the transaction occurred, improving financial reporting accuracy. The change corrects a previous update that caused discrepancies in reporting.
Original PR description
…or the general ledger In a previous pull request: https://github.com/odoo/enterprise/pull/46498, the columns date was switched to invoice date. We want to revert back to the state before this commit. So using the accounting_date instead of the invoice_date on the general ledger. task-4270453
Muted mail notifications will now correctly hide the unread indicator. This prevents users from seeing misleading unread markers on conversations they have chosen to mute.
Original PR description
There was `opacity-0` on muted item, but due to `opacity-50` being mistakenly present at all time, it had precedence over the `opacity-0` thus the unread indicator was always visible. 
This fixes an internal automated test so it checks the intended shared behavior rather than only one specific implementation. It helps prevent false test failures when country-specific electronic invoicing extensions add their own data.
Original PR description
Fix a failing test that was incorrectly patching a class method, instead of patching the base object. Indeed, before this fix the test was only patching `account_edi_ubl_cii._get_ubl_cii_formats_info()` and not extensions such as `l10n_ro_edi._get_ubl_cii_formats_info()`). Therefore extensions could add data to the returned value of the method, and could make the test fail. Related runbot error id: 104916 task-no
Invoice document previews now show only the intended sample QR code when SEPA payment QR codes are enabled. This avoids confusing users during the print and send setup by replacing the real generated QR code in the preview instead of adding a second one.
Original PR description
Version: 18.0 Issue: With a valid SEPA bank account enabled, 2 QR codes are generated on the report invoice preview document. This is because we are xpathing to the `qr_code` element and adding a dummy qr code after for the preview. Purpose of this PR: To replace the generated QR code with the preview, dummy QR code for the preview wizard. Steps to Reproduce on Runbot: install a new company enable QR code in the settings set up a valid SEPA bank account for the bank journal create an invoice and click 'print & send' to trigger the Configure Document Layout wizard view 2 QR codes in the preview opw-4267407 I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fixes a test helper in the HTML editor so moving the text selection no longer rebuilds the page content when nothing has changed. It reduces unnecessary background updates during tests, helping keep editor testing more stable and efficient without changing user-facing behavior.
Original PR description
Before this commit, in the tests, when the setContent utils is used to move the selection, the entire html is recreated. This implies a set of unnecessary mutations in the dom. This commit will therefore prevent the creation of all these mutations by checking if the ‘content’ is different from that in ‘el’. 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
Odoo now shows a server-side warning when older Kanban view templates are used, helping teams identify views that need updating. This complements the existing browser warning and helps prevent deprecated configurations from being introduced unnoticed.
Original PR description
A new API for kanban templates has been introduced in [1], which deprecates the former API (the one defining a "kanban-box" template). A client side warning has been added when a legacy kanban view was met. However, there was a lack of server side warning, especially when a legacy kanban arch was introduced. This commit adds this warning. More information about the new Kanban API can be found in the documentation [2]. [1] https://github.com/odoo/odoo/pull/167751 [2] https://www.odoo.com/documentation/master/developer/reference/user_interface/view_architectures.html#kanban 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 fix ensures website notification popups appear in the visible browser window even when visitors are scrolled down the page. It prevents important confirmations, such as newsletter signup messages, from being hidden at the top of the page.
Original PR description
Since [1], the notifications were not positioned properly anymore. Indeed, if the page was scrolled, the notifications were scrolled with it, meaning that they would not be visible at the top of the viewport as intended, but at the top of the scrolled body. Steps to reproduce: - Install website_mass_mailing - Go to your website homepage in edit mode - Add enough content to make the page scrollable - Add a "Newsletter" inner block inside the footer - Save - Scroll to your footer and register to the newsletter => A popup is shown but you can't see it (scroll to the top to see it). The solution is simple: the previous notification manager was positioned based on the fact the body is never scrolled (position: absolute), we now position it based on the viewport (position: fixed) as it could have already been. [1]: https://github.com/odoo/odoo/commit/189a7c96e6e26825dc05c0c6466576fe63aa091e Closes https://github.com/odoo/odoo/issues/186432 Related to task-4190506
The point of sale food delivery setup no longer pre-selects Glovo as the default provider, giving businesses a neutral starting point when configuring platforms. Order notes have been cleaned up by removing an extra bullet point, and the related settings label is clearer for users managing food delivery platforms.
Original PR description
Before this commit : - Glovo was selected as default delivery provider. - Extra Dot(Bullet Point) is visible in the Order notes - Label to be changed under Food delivery connector field. Following this commit : - Default delivery provider is removed. - Extra dot is been removed in order notes. - Label is been updated to Food Delivery Platforms. task - 4315841
This update fixes an internal automated test for document folder deletion that could fail when the expected test folder was not selected. It helps keep quality checks stable without changing how users delete folders in Documents.
Original PR description
The tour is failing because the test folder ("Folder1") is not always selected when starting the test with its access token. As the test is checking the folder deletion, we select the test folder manually by clicking on it.
Task-4247011This fix removes an incorrect warning shown around Web Studio kanban views after a naming change from "kanban-card" to "card". It helps avoid confusing users or administrators with a warning about something that no longer exists, with no expected change to business workflows.
Original PR description
The warning was erroneous as "kanban-card" doesn't exist, we renamed it into "card" [1]. [1] odoo/odoo#180999
This update replaces the outdated icon for the UPS delivery module within Odoo Enterprise. The change ensures a consistent and professional visual representation of the UPS integration, improving the user experience. This is a minor cosmetic update.
Original PR description
The `delivery_ups_rest` module icon was using the old one. This commit replaces it for the new UPS icon. task-4317822
This update clarifies the user interface for rounding methods in the Point of Sale settings. Previously, 'HALF-UP' was confusing, so the term has been changed to 'Nearest' to better align with user expectations and provide a more intuitive experience. This ensures accurate and easily understood calculations within the POS system.
Original PR description
The rounding method 'HALF-UP' is confusing for regular users when they see it in the UI. Replacing the user-facing term by the less specific 'Nearest' is clearer, since people naturally expect that to round halves up. This commit adapts an error message to the new term. [opw-4266444](https://www.odoo.com/odoo/all-tasks/4266444) Related to https://github.com/odoo/odoo/pull/186237 Forward-Port-Of: odoo/enterprise#73285
This update resolves an issue where helpdesk tickets created from child contacts couldn't access products associated with their parent contacts. Previously, this limitation existed across several Odoo versions. This fix ensures that child contacts can now correctly see and utilize products linked to their parent contacts within the helpdesk system.
Original PR description
Steps to reproduce: - Install helpdesk_stock and Studio - Create 2 contacts, with one parent of the other - Create a quotation for parent contact with any product - Create a quotation for child contact with another product - Helpdesk app > Create a ticket - Add the 'product_id' field with studio - (Under 'Existing Fields' search product) - (View tab > Show invisible elements > Find product field > untick invisible) - Parent contact as Customer => Can only see their product (Expected) - Child contact as Customer => Can only see their product (Wrong) Between 15.0 and saas-17.4, the child contact cannot access its parent's sale order products. This is due to an improvement made in saas-17.4 https://github.com/odoo/enterprise/pull/48624 which lets child contacts use parent SOs in repair/return flows etc... opw-4285382 Forward-Port-Of: odoo/enterprise#73391
This update resolves an issue where selecting a document record in the documents module would lose its selection when column widths were adjusted. The fix prevents the system from removing selections triggered by resizing columns, ensuring users can consistently select and manage documents. This improves the overall usability of the documents module.
Original PR description
Steps to reproduce ================== - Go to documents - Switch to the list view - Select a record - Resize a column => The selection is lost Solution ======== Ignore clicks in the header opw-4203375