Tuesday, March 26, 2024
10 changes · 17.0
Enhancements to existing features
The portal icon size is now restricted to a standard 64x64 pixel dimension. This ensures consistency across the platform and eliminates the need for manual icon resizing, making the portal experience more uniform and reducing administrative overhead.
Original PR description
-Sometime we may receive a portal icon that can be a little big or a little small in size, then in order to make it perfectly fit to client portal we will have to edit the icon to 64x64, invoice, sale, project app all have the same 64x64 portal icon. -Therefore we should restrict it to 64x64 to ensure no further action is needed 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
Resolved issues and error corrections
This fix ensures that when an Italian company turns off the tax representative setting, the previously selected representative is removed from invoices and related XML exports. This prevents outdated representative details from being used and helps keep Italian electronic invoicing data aligned with current company settings.
Original PR description
[FIX] l10n_it: empties the l10n_tax_representative_partner_id if the l10n_it_has_tax_representative field is unchecked. When a xml file is generated from the invoice, the company tax code is used and not the previous tax representative, after the setting has changed. Current behavior before PR: Tax representative is still assigned even if the setting to use a tax representative is unchecked. Desired behavior after PR is merged: Have the tax representative field emptied when the setting to use representative is unchecked. opw-3694076 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Miscellaneous changes
Reversing an invoice wizard provides an option to use the original entry date, but does not set the invoice_date to the same date. This behaviour is strange because the UI displays today's date, but the move is actually posted on a different date. This commit, keeps the dates in sync. Source: https://github.com/odoo/odoo/pull/93609 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#158640 Forward-Port-Of: odoo/odoo#1
Original PR description
Reversing an invoice wizard provides an option to use the original entry date, but does not set the invoice_date to the same date. This behaviour is strange because the UI displays today's date, but the move is actually posted on a different date. This commit, keeps the dates in sync. Source: https://github.com/odoo/odoo/pull/93609 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#158640 Forward-Port-Of: odoo/odoo#158530
This fix removes a duplicate variable that was accidentally introduced in the Dutch localization tax reporting module. The change cleans up test code to ensure the module functions correctly without redundant data.
Original PR description
During this commit: https://github.com/odoo/enterprise/commit/02252c3af7637835e34d0c19a609e1aa05b5a653#diff-fcb2837955e2fcf5fb3885f86c0f12f8facd7cd24d73e1f151957c33db381f9e A duplicate variable was introduced. This commit will remove that. no task-id
This fix corrects an incorrect visibility setting for the phone field in the WhatsApp message composer. The issue occurred during a code merge and has been resolved to ensure the phone field displays properly when composing WhatsApp messages.
Original PR description
Wrong conflict resolution when forward porting odoo/enterprise@7ff6e2b04110d1e3c046388927409ec46d39800e Task-3778173
This update fixes the visual appearance of the import tool when using dark mode. The background colors were too dark and inconsistent with other parts of the system, making the interface less appealing. The changes adjust the background colors to look better in both light and dark modes while maintaining consistency across the application.
Original PR description
This commit adapts `base_import`'s background that was too dark compared to other modules. This was caused by the use of a `bg-white` class that is not very "dark-mode friendly" as it will display as…
This commit adapts `base_import`'s background that was too dark compared to other modules. This was caused by the use of a `bg-white` class that is not very "dark-mode friendly" as it will display as a pure black, which is not visually appealing and not wanted. This commit also adapts the background color of the sidebar to make it more consistent with other modules. We also add a `bg-view` class to the table, so it stands out more in light mode and stays the same in dark mode. task-3814508 | Before | After | |--------|--------| | <img width="1728" alt="Screenshot 2024-03-22 at 08 32 26" src="https://github.com/odoo/odoo/assets/110090660/85c0d0bf-19af-4a19-aa1b-cf990a6147d8"> | <img width="1728" alt="Screenshot 2024-03-22 at 08 34 08" src="https://github.com/odoo/odoo/assets/110090660/dfe7198a-c011-4ead-bf6f-cfba50db93a9"> | | <img width="1726" alt="Screenshot 2024-03-22 at 08 32 42" src="https://github.com/odoo/odoo/assets/110090660/ed5914c2-bf1c-44ee-baa6-58fb5f537d9a"> | <img width="1725" alt="Screenshot 2024-03-22 at 08 34 19" src="https://github.com/odoo/odoo/assets/110090660/fb80a723-d1d0-4d44-aded-d603385cce70"> | | <img width="1714" alt="Screenshot 2024-03-22 at 08 59 52" src="https://github.com/odoo/odoo/assets/110090660/98c543a0-05dd-4b71-b5bf-9d702f513fb4"> | <img width="1715" alt="Screenshot 2024-03-22 at 08 57 41" src="https://github.com/odoo/odoo/assets/110090660/4005b050-4a2a-4137-b6c0-47ecbdbe89a7"> | | <img width="1726" alt="Screenshot 2024-03-22 at 08 33 08" src="https://github.com/odoo/odoo/assets/110090660/fde063f8-48f5-4ae2-a5c1-b1973d94f0b3"> | <img width="1728" alt="Screenshot 2024-03-22 at 08 33 59" src="https://github.com/odoo/odoo/assets/110090660/b5875104-7d6f-4a36-8303-0cf7c14c113d"> | --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#158019
A test in the Purchase MRP module was using incorrect field references that could cause validation issues. This fix corrects the test to use the proper field names, ensuring the test accurately validates the system's behavior when processing purchase orders with backorders.
Original PR description
this commit https://github.com/odoo/odoo/pull/158788/commits/07e2fca9e39e9c32182f10bae6ba814a4241b6bf uses `qty_done` instead of `quantity` in test `test_valuation_with_backorder`
This update removes a broken email sending method in the Partner module that has been non-functional since version 14.5. The underlying email functionality it relied on was removed years ago, but this method was accidentally left behind. Removing it prevents confusion and potential errors from attempting to use this obsolete feature.
Original PR description
The underlying `odoo.tools.email_send` was removed in 82de620424e22f9ca7cb9768db638c3a2b4f9318 (merged in 14.5) but this callsite was missed, this method has been broken ever since. Forward-Port-Of: odoo/odoo#159113
When creating a new invoice, the browser tab title was showing confusing technical information (NewId_0x7f545c9d6980) alongside the invoice name. This fix removes that unnecessary technical identifier so users see a clean, professional tab title like "Draft Invoice" instead.
Original PR description
Steps to reproduce ================== - Create a new Invoice => The tab title is `Odoo - Draft Invoice (* NewId_0x7f545c9d6980)` Cause of the issue ================== In 17, the display_name is computed for the tab title https://github.com/odoo/odoo/blob/82fd8e702588d2cc5bdad474ed21188257cc7397/addons/web/static/src/views/form/form_controller.js#L342 opw-3794671
This fix addresses a flaky test in the scheduled jobs system that was producing inconsistent results. The issue occurred because data was being flushed at the wrong time, causing conflicting settings to override each other. By reordering when the data flush happens, the test now runs reliably every time.