Tuesday, November 12, 2024
28 changes
4 changes
Resolved issues and error corrections
Sendcloud delivery documents are now posted as separate messages instead of being grouped together. This helps route labels, slips, and A4 documents to the correct printers and avoids mixed print jobs during transfer validation.
Original PR description
Validating a transfer for a Sendcloud delivery puts all attachments in the same chatter message, which seems to cause problems with all files being sent to the same printer in one go. This is undesirable when stickers, slips and A4 documents need separate printers. This change makes it generate a new message for every attachment. Task ID: [4011224](https://www.odoo.com/odoo/966/tasks/4011224)
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
19 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
2 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. 
The Point of Sale cash closing autofill now respects the user's language and currency formatting. This prevents amounts with comma decimal separators, such as 120,20 €, from being entered as much larger incorrect values like 12020 €.
Original PR description
When using the new auto fill cash count button, the amount filled in was not using the correct separator. That leads to wrong closing amounts Steps to reproduce: ------------------- * Change the language to a one that use different separator (Dutch) * Open PoS and make some sales (atleast 100€) * Close the session and click on the copy button that will autofill the closing amount. > Observation: The amount would be wrongly filled. If the amount to fill was 120,20 € it would become 12020 € Why the fix: ------------ To fix this we just use the correct helpers to format currencies opw-4265952
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
This fix prevents an error when adding a customer account payment in Point of Sale while invoicing is enabled. It helps cashiers complete customer-account transactions smoothly without interruption.
Original PR description
Before this commit, if invoicing is enabled, adding a customer account payment would cause an error. opw-4318917 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fix prevents an error from interrupting the register closing process in Point of Sale. Cashiers can now close registers reliably, reducing disruption at the end of a sales session.
Original PR description
Before this commit: ========== - A traceback occurred when the user attempted to close the register. After this commit: ========== - Close register process functions correctly. task-4280911
The Bill of Materials overview now checks stock available at the subcontractor instead of the company warehouse. This gives planners a more accurate view of component availability for subcontracted manufacturing and helps avoid misleading availability information.
Original PR description
In the availability column of the BOM overview, consider the subcontractor's stock instead of the current warehouse stock. task: 4285581 I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
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
Fixed an issue that could prevent the UAE corporate tax report from opening after it had already been opened once. This ensures users can access the report repeatedly without errors, supporting smoother tax reporting workflows.
Original PR description
Opening the corporate tax report more than once resulted in an error, making it impossible to open the report. The reason for this was an undefined comparison filter when opening the report for the second time. This was a result of setting the export mode to `file` when opening the report, which in turn makes the comparison undefined. This commit fixes this by temporarily setting the export mode to `file` when creating the entry. ticket: https://www.odoo.com/odoo/project/49/tasks/4288546
Applicants signing contracts now see their real name instead of a placeholder, dependent benefit options are only shown when relevant, and salary configurator dropdowns look editable. This reduces confusion during contract signing and salary package configuration.
Original PR description
1. When an applicant (who doesn't have an employee record yet) signs a contract their name is shown as `simulation employee` instead of their actual name. 2. Dependent benefits are visible although the mandatory benefits aren't selected. For example: the dialog box showing the number of insured children under ambulatory insurance is visible although the abulatory insurance isn't selected on the salary configurator. 3. The dropdown menus on the salary configurator have a grey color which makes the user think that they aren't editable. These changes fixes the above issues. task-4280657
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
Partner ledger statements are no longer emailed to all followers of a partner record. This helps prevent unintended recipients from receiving customer statement emails, ensuring statements go only to the partner or explicitly selected recipients.
Original PR description
Statements (using the partner ledger send button) are currently being sent to followers of the partner. This should not be the case, only the partner or specified recipients should receive the email. Task-4320475
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 fix restores the form used to view or create email aliases in Documents settings. Users can once again open existing aliases or add new ones without seeing a blank page, reducing configuration friction.
Original PR description
Steps to reproduce: Documents / Configuration / Email Aliases Click on any alias or try to create a new one, the form view is empty. This is occurred after merging `documents.folder` into `documents.documents` [commit link] The reason why this append is that the form view was left empty in the XML file. OPW-4298418
This update fixes several issues affecting website shopping, accounting localization, email sending, reports, and automated product tours. It improves reliability for users by preventing misleading product availability messages, avoiding email form errors, improving German accounting mapping, and speeding up stock-related sales processing.
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