Monday, December 4, 2023
43 changes · 17.0
Enhancements to existing features
The mail push-to-talk browser extension now includes correctly sized icons and a required screenshot for Chrome Web Store publication. The documentation also notes that ChromeOS does not support global keyboard commands, helping set expectations for users on that platform.
Original PR description
In order to be published on the chrome extension store, an extension must provide at least one screenshot and a 128x128 icon. Until now, the extension assets only contained a 100x100 icon that was used as 128 and did not contain any screenshot. In order to ease updates on the chrome extension store, this commit updates the two icons used by this extension to match the expected dimensions and adds the required screenshot. At the same time, this commit updates the extension readme to warn about ChromeOS limitations (ChromeOS does not support global commands).
The point of sale receipt screen now shows a larger receipt preview, making it easier for cashiers to read and verify details before starting the next order. The new order button was resized to keep the screen layout balanced with the larger receipt.
Original PR description
This commit increase the receipt size on the receipt screen and shrink the new order button to fit the new size. Old:  New:  --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update adjusts the Calendar menu ordering so it stays in the expected position after upgrades. It helps avoid confusing menu shifts for users without requiring a separate upgrade script.
Original PR description
The sequence is equal to 10 and it is causing issues during upgrade. The order used by the menus is _order = sequence, id As the menu has a new xmlid, it will be placed after the existing one because if his sequence. We could 1) lower the sequence value 2) don't provide a sequence (menuitem is noupdate False) and update the value in the upgrade script. Proposal 1 is chosen as it does not require an upgrade script. taskid: 3618126 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Resolved issues and error corrections
The draft record message “Creating a new record...” now correctly displays the current user as its author. This removes a confusing blank author in the chatter and makes draft activity easier to understand.
Original PR description
Before this commit, when a record is in draft, the chatter message "Creating a new record..." shown no author. The intended showing is to display current user as author of this message. Persona model requires `id` and `type`, the latter to determine whether the persona is a guest or partner. Only the id of current user was provided, so it was not enough to determine the appropriate `Persona`.
Miscellaneous changes
`is_published` has been renamed in `website_published` in e3d2b01 but not in `_track_subtype`(). **steps to reproduce:** - add a follower to an event, select the two event subtypes on this follower - check this event on the website and publish/unpublish it - check chatter, tracking values have been created - no message have been sent - **before this commit:** - subtypes `mt_event_published` and `mt_event_unpublished` are not used **after this commit:** - a message is sent when an
Original PR description
`is_published` has been renamed in `website_published` in e3d2b01 but not in `_track_subtype`(). **steps to reproduce:** - add a follower to an event, select the two event subtypes on this follower - check this event on the website and publish/unpublish it - check chatter, tracking values have been created - no message have been sent - **before this commit:** - subtypes `mt_event_published` and `mt_event_unpublished` are not used **after this commit:** - a message is sent when an event is (un)published opw-3582596 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#144819 Forward-Port-Of: odoo/odoo#143676
Recent chat channels now appear in a consistent order even when they have the same activity time. This reduces rare, confusing ordering issues and helps prevent related chat palette errors during startup.
Original PR description
Fallback to ID compare when the dates are the same. Added some extra steps in the test to help further debugging if this PR does not completely resolve the issue. runbot-28637
Pivot views now remove repeated date/grouping choices before requesting report data. This prevents reports and spreadsheet pivots from failing when the same field is grouped in overlapping ways, keeping business analysis views reliable.
Original PR description
Since https://github.com/odoo/odoo/pull/103510, the read_group parameter "groupby" can no longer contain implicit duplicates. For example groupby=['date', 'date:month] doesn't work anymore. Here we remove all duplicates from groupby before making a read_group.
This update fixes a display issue where the day selection control could be misplaced or less responsive in timesheet-related calendar views. The layout behavior is now applied only where appropriate, helping users navigate dates more reliably without disrupting the timesheet interface.
Original PR description
In commit f9222c4976a78c2f02264db897bc9826bbda0944 the class `order-3` is applied on the ViewScaleSelector component but it breaks the view in timesheet. This commit creates a props to contextually use this class on the component. task-3580643 Enterprise: - https://github.com/odoo/enterprise/pull/50055  --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fix ensures receipt headers in Gulf region point of sale flows receive the country-region flag they need. It prevents inconsistent or missing regional receipt information for GCC and Saudi localization setups.
Original PR description
There was an inconsistency due to the separation of ReceiptHeader from OrderReceipt. The 'is_gcc_country', which is utilized in both l10n_gcc_pos and l10n_sa_pos modules within the ReceiptHeader, was not being appropriately passed due to this separation. This commit resolves the issue by overriding the 'getReceiptHeaderData' method to include the 'is_gcc_country' in the ReceiptHeader data. This ensures that the ReceiptHeader correctly reflects the necessary information. opw-3610862 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The website editor now handles a missing text selection safely when users select text around a banner and apply a color. This prevents an error screen and keeps page editing uninterrupted.
Original PR description
**Current behavior before PR:** selecting text after banner to inside the banner and apply color gives traceback because the selection is null or rangeCount of selection is 0. **Desired behavior after PR is merged:** Now after adding check for selection and rangeCount selecting text after banner to inside the banner and apply color will not give traceback. task-3500897 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The course join popup now displays correctly when a visitor clicks “Join This Course” without being logged in. This prevents an error and helps prospective learners continue toward signing in or joining a course smoothly.
Original PR description
**Before this PR**: Clicking on the 'Join This Course' button without login triggers an error. Reason: The`'slide.course.join.popupContent` template contains multiple root nodes. For correct template rendering text and anchor tags are placed inside `div` tags. **After this PR**: Correct popup content renders when clicking on the 'Join This Course' button, without login. **Task**-3559181
A small issue in an automated Point of Sale sales test was corrected after a previous update used an outdated test step format. This helps keep internal testing reliable and reduces the risk of future changes being blocked by a faulty test.
Original PR description
The forward port commit 96645bd31b2ea9c924521aa65734c65bb055c77c introduce a wrong tour step which uses the old way of declaring a tour step in pos. We fix that in this commit. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Saving newly added configuration sections now works consistently after the first save. This prevents errors that could interrupt setup or maintenance of IoT-related configuration changes.
Original PR description
[FIX] config.py Traceback when saving new added section
Before: When creating new section in odoo.conf (eg: [IOT]), first
save is ok since it doesn't exists. But subsequent save fails ->
configparser.DuplicateSectionError: Section 'IOT' already exists
Now: Subsequent saves work
mool
---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-prUser avatar images on eLearning pages now keep a consistent circular shape even when the original image is not square. This improves visual polish and prevents stretched or oval-looking profile pictures.
Original PR description
Prior to this commit, if the avatar image didn't have a 1:1 ratio, the `rounded-circle` image would be oval instead of the intended circle. To fix this we add the `o_avatar` class to the `img`, and since this class already contains `object-fit: cover` we can remove it from the element's inline styles. <img width="63" alt="Screenshot 2023-11-22 at 12 48 47" src="https://github.com/odoo/odoo/assets/19491443/80c31085-991d-48b8-a398-e41c171f1ab0"> _ratio 3:5_ | Before | After | |--------|--------| ||| task-3607243 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Clicking a website editor snippet now shows the expected helper tooltip, matching the guidance users see during drag-and-drop actions. This restores a small but useful cue that helps users understand how to work with snippets in the editor.
Original PR description
Prior to this commit, clicking on a snippet did not display the helper tooltip which would usually display After this commit, it does, however it's unknown why ATM, needs to be investigated further. task-3582562
This fix restores the hiding of the appraisal survey type option in the survey application. The appraisal type is only meant for the HR appraisal module and should not be visible to survey users. A recent technical change inadvertently made this option visible again, and this fix corrects that by targeting the appraisal option with updated styling rules.
Original PR description
In odoo/enterprise#38268, we have added a survey type to allow to simplify the survey creation by only displaying relevant options for the type chosen. We have also added the appraisal type in the hr_appraisal_survey module, and hidden it in the survey views because that type is only relevant for the appraisal module and we don’t want to see it in the survey app. From 16.4, that type is no longer hidden in the app survey. This fix solves the problem. Technical notes: Following the change in odoo/enterprise#37387 that makes "primary" the override of the survey form that hide the appraisal type, the appraisal type is no longer hidden in the survey app. This is because in the override, we add a class used in css to hide that option (no longer present in survey because of the primary). To avoid modifying view in stable, we target the "appraisal" option without that added class. Task-3613370 Forward-Port-Of: odoo/enterprise#51591
This update fixes a display issue in the Field Service module where partner names and cities were incorrectly breaking onto separate lines. The fix ensures this information displays properly on the same line, improving the readability of customer details in project sharing views.
Original PR description
This commit ensures the partner name and partner city are displayed in the same line. It also updates the code according to the changes made in community (see #144492) Task-3383519
This update corrects the configuration for the Chinese yuan offshore currency (CNH) to properly reference the newly added currency code. This ensures that currency rate systems correctly identify and process offshore Chinese yuan transactions without errors or mismatches.
Original PR description
[FIX] res_config: change the Chinese yuan offshore currency unique name/code to point to the newly added currency. complementary of [adding the CNH currency PR](https://github.com/odoo/odoo/pull/144331) opw-3599124 Forward-Port-Of: odoo/enterprise#51831
This update corrects how the Field Service Stock module references product quantities to align with recent changes in the core Odoo system. The fix ensures the module uses the correct field name for product quantity calculations, improving consistency across the system and preventing potential data handling issues.
Original PR description
Small refactoring to be coherent with odoo/odoo#144574 Correction of the changes of odoo/enterprise#48709
Problem -------- In ver 16, field payment_state of model hr_expense_sheet use _fields[] to get item selection field payment_state of account_move. This causes the file translation of this module to not accept the description item of field payment_state This commit ------ Use the PAYMENT_STATE_SELECTION of account_move as the selection value of payment_state (hr_expense_sheet) ### Please help me with this or is there any other way to translate the descriptiom item of fields payment_sta
Original PR description
Problem -------- In ver 16, field payment_state of model hr_expense_sheet use _fields[] to get item selection field payment_state of account_move. This causes the file translation of this module to not accept the description item of field payment_state This commit ------ Use the PAYMENT_STATE_SELECTION of account_move as the selection value of payment_state (hr_expense_sheet) ### Please help me with this or is there any other way to translate the descriptiom item of fields payment_state, Thanks a lot --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#144384 Forward-Port-Of: odoo/odoo#142458
Steps to reproduce: - Get the eLearning App. - Go to an existing course or create a new one. - Add a new content of type article. - Go to website preview and to edit this slide. - Write plain text inside the box of content. - Go to Fullscreen. The issue is that we are using `.append()` and this expects that we pass it an html or a jquery object which is not the case when we just type plain text inside it, so using `.html()` will allow us to render any content as HTML. opw-3265113
Original PR description
Steps to reproduce: - Get the eLearning App. - Go to an existing course or create a new one. - Add a new content of type article. - Go to website preview and to edit this slide. - Write plain text inside the box of content. - Go to Fullscreen. The issue is that we are using `.append()` and this expects that we pass it an html or a jquery object which is not the case when we just type plain text inside it, so using `.html()` will allow us to render any content as HTML. opw-3265113 Forward-Port-Of: odoo/odoo#136675
The issue is not easy to reproduce, so the fix is not a guaranteed one. Estimation: the click on the "send message" buttons happens too early, and it is either doing nothing, or being immediately reset by another action that happens at page load. Adding a little bit of extra delay (in particular waiting for messages to be loaded) might resolve the issue. Also back-port code allowing to use contains in tours. runbot-27847 Forward-Port-Of: odoo/odoo#144216 Forward-Port-Of: odoo/odo
Original PR description
The issue is not easy to reproduce, so the fix is not a guaranteed one. Estimation: the click on the "send message" buttons happens too early, and it is either doing nothing, or being immediately reset by another action that happens at page load. Adding a little bit of extra delay (in particular waiting for messages to be loaded) might resolve the issue. Also back-port code allowing to use contains in tours. runbot-27847 Forward-Port-Of: odoo/odoo#144216 Forward-Port-Of: odoo/odoo#142084
### Steps - Go to website -> courses. - Make a search. ### Issue Whatever if there are records found or not, on the search button we see "(0) found". ### Reason In the method responsible of search ``slides_channel_all_values()`` we don't pass ``search_count`` to the dict to be rendered. opw-3544856 Forward-Port-Of: odoo/odoo#143356
Original PR description
### Steps - Go to website -> courses. - Make a search. ### Issue Whatever if there are records found or not, on the search button we see "(0) found". ### Reason In the method responsible of search ``slides_channel_all_values()`` we don't pass ``search_count`` to the dict to be rendered. opw-3544856 Forward-Port-Of: odoo/odoo#143356
Steps to reproduce : - install field service module - install industry_fsm_report bridge module - click on configuration - click on worksheet template - try to delete more than one record Issue: - error while deleting more than one record Cause: - because ,this issue is from base while deleting the model id's Solution: - if we write condition for filtering manual models and calling prepare_update() method and then non manual models ,then the issue will be solved task-36070
Original PR description
Steps to reproduce : - install field service module - install industry_fsm_report bridge module - click on configuration - click on worksheet template - try to delete more than one record Issue: - error while deleting more than one record Cause: - because ,this issue is from base while deleting the model id's Solution: - if we write condition for filtering manual models and calling prepare_update() method and then non manual models ,then the issue will be solved task-3607053 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#144478
When a dropdown open a dialog and on the dialog there is a new dropdown, before this commit, when clicking on the second dropdown, the first one will close. This is an issue with closing the first dropdown, is if the dialog is opened using useOwnedDialogs, the dialog will also close. Also, if the dialog is open to throw a "find more" of a x2many field, even if the dialog is not close, as the dropdown will close, the original field will also be destroyed and it will raise an error. Now,
Original PR description
When a dropdown open a dialog and on the dialog there is a new dropdown, before this commit, when clicking on the second dropdown, the first one will close. This is an issue with closing the first dropdown, is if the dialog is opened using useOwnedDialogs, the dialog will also close. Also, if the dialog is open to throw a "find more" of a x2many field, even if the dialog is not close, as the dropdown will close, the original field will also be destroyed and it will raise an error. Now, we avoid closing dropdown's, when opening new dropdowns that there are not on the same active element. opw-3464528 Forward-Port-Of: odoo/odoo#144119
1. minor mistake, prefix for account move line instead of line.company_id, use `aml.company_id` 2. syntax error : typecase for `::int =` to compare parent_path with integer value. 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#144705
Original PR description
1. minor mistake, prefix for account move line instead of line.company_id, use `aml.company_id` 2. syntax error : typecase for `::int =` to compare parent_path with integer value. 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#144705
There is a specific rule that set the `o_AttachmentViewer_view` background color to a static white color (i.e. `#FFFFFF`). Then in dark mode, while the font color for the attachement "view" is set to white due to the `color-scheme` meta, the background keeps its white color, which makes the content unreadable. In this commit we use instead the `$white` variable, which is properly adapted in "dark mode", for the background color. Steps to reproduce: * Open Odoo * Set Odoo in Dark mode using
Original PR description
There is a specific rule that set the `o_AttachmentViewer_view` background color to a static white color (i.e. `#FFFFFF`). Then in dark mode, while the font color for the attachement "view" is set to white due to the `color-scheme` meta, the background keeps its white color, which makes the content unreadable. In this commit we use instead the `$white` variable, which is properly adapted in "dark mode", for the background color. Steps to reproduce: * Open Odoo * Set Odoo in Dark mode using the dropdown menu of the user * Open the Note app * Make a note or open one * Upload a JSON attachment in the chatter * Open the preview of the attachment => BUG text in white and background color in white => text not visible --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#144600 Forward-Port-Of: odoo/odoo#144513
Steps to reproduce: - Install Accounting and Contacts - Create a contact (e.g. Contact X) - Add an Invoice Address to the contact (e.g. Invoice Address X) - Create an invoice with Invoice Address X as partner - Confirm it - In invoices list view, Customer field is "Contact X, Invoice Address X" - Go to Contacts and rename "Contact X" to "Contact Y" => In invoices list view, Customer field is still "Contact X, Invoice Address X" Cause: "invoice_partner_display_name" field is not recomp
Original PR description
Steps to reproduce: - Install Accounting and Contacts - Create a contact (e.g. Contact X) - Add an Invoice Address to the contact (e.g. Invoice Address X) - Create an invoice with Invoice Address X as partner - Confirm it - In invoices list view, Customer field is "Contact X, Invoice Address X" - Go to Contacts and rename "Contact X" to "Contact Y" => In invoices list view, Customer field is still "Contact X, Invoice Address X" Cause: "invoice_partner_display_name" field is not recomputed when the name of the parent partner is changed. opw-3597741 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#144688 Forward-Port-Of: odoo/odoo#143749
Before this commit: When we try to delete a Meeting type Activity from the technical menu "Settings > Technical > Activities" it do not delete the associated calendar event. After this commit: The calendar event will be deleted when the associated Activity gets deleted. task-3493426 Forward-Port-Of: odoo/odoo#144526
Original PR description
Before this commit: When we try to delete a Meeting type Activity from the technical menu "Settings > Technical > Activities" it do not delete the associated calendar event. After this commit: The calendar event will be deleted when the associated Activity gets deleted. task-3493426 Forward-Port-Of: odoo/odoo#144526
**Description of the issue/feature this PR addresses:** The color was only used on the calendar event form view, but it was ignored in these other views. **Current behavior before PR:** <img width="1314" alt="Screenshot 2023-11-29 at 09 05 13" src="https://github.com/odoo/odoo/assets/1914185/76980af4-fe8f-4a9a-8fcd-1577efe58979"> <img width="1314" alt="Screenshot 2023-11-29 at 09 05 51" src="https://github.com/odoo/odoo/assets/1914185/128ae207-aa5c-47a7-9a02-e923814f5cb3"> **Desired b
Original PR description
**Description of the issue/feature this PR addresses:** The color was only used on the calendar event form view, but it was ignored in these other views. **Current behavior before PR:** <img…
**Description of the issue/feature this PR addresses:** The color was only used on the calendar event form view, but it was ignored in these other views. **Current behavior before PR:** <img width="1314" alt="Screenshot 2023-11-29 at 09 05 13" src="https://github.com/odoo/odoo/assets/1914185/76980af4-fe8f-4a9a-8fcd-1577efe58979"> <img width="1314" alt="Screenshot 2023-11-29 at 09 05 51" src="https://github.com/odoo/odoo/assets/1914185/128ae207-aa5c-47a7-9a02-e923814f5cb3"> **Desired behavior after PR is merged:** <img width="1314" alt="image" src="https://github.com/odoo/odoo/assets/1914185/972e9a4b-cc75-4463-ba88-288718cb12e1"> <img width="1314" alt="Screenshot 2023-11-29 at 09 06 50" src="https://github.com/odoo/odoo/assets/1914185/635408b3-d956-4d2a-bf76-5e0df0714721"> ping @flch-odoo @leonardopavanrocha --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#144370 Forward-Port-Of: odoo/odoo#144165
Current behavior: When printing receipt from an iOS device, the QRCode is not printed at the good position. Steps to reproduce: - Install l10n_sa_pos - Install an ePoS printer - Go on an iOS device - Go to POS - Create a new order - Pay the order - Print the receipt opw-3560424 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#142755
Original PR description
Current behavior: When printing receipt from an iOS device, the QRCode is not printed at the good position. Steps to reproduce: - Install l10n_sa_pos - Install an ePoS printer - Go on an iOS device - Go to POS - Create a new order - Pay the order - Print the receipt opw-3560424 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#142755
Steps: - Install project app. - Share project editable to user which has no task. - Open that project in project sharing. Issue: - No content hepler is not properly showing. Cause: - Helper in project sharing action is not markup even and that action is type object so we have to markup no content manually. Fix: - Markup project sharing helper. task-3293310 Forward-Port-Of: odoo/odoo#122230
Original PR description
Steps: - Install project app. - Share project editable to user which has no task. - Open that project in project sharing. Issue: - No content hepler is not properly showing. Cause: - Helper in project sharing action is not markup even and that action is type object so we have to markup no content manually. Fix: - Markup project sharing helper. task-3293310 Forward-Port-Of: odoo/odoo#122230
**Steps:** - Open Settings > Users - Change the name of the user by typing it multiple times - Open Project > Choose a Project - Create a task with the assignee as our user - Now open the Kanban view of the Project, where we have the task stages. **Issue:** - In the Kanban view, we can see the name of the assignee overflowing. - This same issue is also present in Project Sharing **Cause:** - The text is not truncated due to which the name overflows. **Fix:** - adding the class
Original PR description
**Steps:** - Open Settings > Users - Change the name of the user by typing it multiple times - Open Project > Choose a Project - Create a task with the assignee as our user - Now open the Kanban view of the Project, where we have the task stages. **Issue:** - In the Kanban view, we can see the name of the assignee overflowing. - This same issue is also present in Project Sharing **Cause:** - The text is not truncated due to which the name overflows. **Fix:** - adding the class text-truncate and d-block to correct it **Task:** 3383519 Forward-Port-Of: odoo/odoo#144227 Forward-Port-Of: odoo/odoo#126811
https://github.com/odoo/odoo/commit/a66ac063e01afbcc5bec2e6f56da81340b28aaa7 introduced the use of `_post_invoice_edi` method on `account.edi.format`, as it is a forward port of a fix in v15, where this method still existed. But it doesn't exist anymore in v16, due to https://github.com/odoo/odoo/commit/0e5626ca5126e6fea7fb95b694229948540764d7. The fix is to use the method specific to the spain edi: `_l10n_es_edi_sii_post_invoices` opw-3604907 Forward-Port-Of: odoo/odoo#143310
Original PR description
https://github.com/odoo/odoo/commit/a66ac063e01afbcc5bec2e6f56da81340b28aaa7 introduced the use of `_post_invoice_edi` method on `account.edi.format`, as it is a forward port of a fix in v15, where this method still existed. But it doesn't exist anymore in v16, due to https://github.com/odoo/odoo/commit/0e5626ca5126e6fea7fb95b694229948540764d7. The fix is to use the method specific to the spain edi: `_l10n_es_edi_sii_post_invoices` opw-3604907 Forward-Port-Of: odoo/odoo#143310
This commit improves the readability of the label inside an arrow button. Prior to this commit, the label of an arrow button was styled with a `opacity-50` class. This would render well visually, but does not provide sufficient contrast. This becomes especially true in dark mode. To improve the readability of this label, we simply set a `text-muted` class to it, which will still apply an opacity, but more subtle, making our label readable. task-3575154 | 17.0 (Lightmode) | 17-0-fi
Original PR description
This commit improves the readability of the label inside an arrow button. Prior to this commit, the label of an arrow button was styled with a `opacity-50` class. This would render well visually, but does not provide sufficient contrast. This becomes especially true in dark mode. To improve the readability of this label, we simply set a `text-muted` class to it, which will still apply an opacity, but more subtle, making our label readable. task-3575154 | 17.0 (Lightmode) | 17-0-fix-contrast-issue-in-arrow-btn-chgo | | ------------- | ------------- | | <img alt="image" src="https://github.com/odoo/odoo/assets/128030743/0a4d32a3-7f5f-4807-b6a9-73cd14838e1e"> | <img alt="image" src="https://github.com/odoo/odoo/assets/128030743/b15e2edc-d56c-4dab-8cd0-acd5df84d925"> | Forward-Port-Of: odoo/odoo#140247
When the width of the column is too small to fit the date, the date was cut by the following column instead of having its content truncated.  Enterprise PR: https://github.com/odoo/enterprise/pull/51011 task-3463329 part of task-3326263 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#142771 Forward-Port-Of: odoo/odoo#132215
Original PR description
When the width of the column is too small to fit the date, the date was cut by the following column instead of having its content truncated.  Enterprise PR: https://github.com/odoo/enterprise/pull/51011 task-3463329 part of task-3326263 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#142771 Forward-Port-Of: odoo/odoo#132215
1. If the name of a product on an imported EDI document is a substring of the name of a product on the DB, said product could be used instead of the correct one, depending on their order (i.e. ID) in the DB. Example: There are 2 products named "Placement" and "Displacement" in a DB. A PDF is imported. It contains a product named "Placement". If the "Displacement" product on the DB appears before the "Placement" one, the product on the AML will be set to the "Displacement" one. To fix
Original PR description
1. If the name of a product on an imported EDI document is a substring of the name of a product on the DB, said product could be used instead of the correct one, depending on their order (i.e. ID) in…
1. If the name of a product on an imported EDI document is a substring of the name of a product on the DB, said product could be used instead of the correct one, depending on their order (i.e. ID) in the DB. Example: There are 2 products named "Placement" and "Displacement" in a DB. A PDF is imported. It contains a product named "Placement". If the "Displacement" product on the DB appears before the "Placement" one, the product on the AML will be set to the "Displacement" one. To fix this, we first check if there is a product identically named to the one in the EDI document. 2. In case a product from the DB is used, if possible, the UoM used should be the one present on the EDI document. Thus there should be a check to ensure that the UoM category on said document matches the one of the product's UoM before assigning it, to avoid a compatibility error. Co-authored-by: Julien Van Roy <juvr@odoo.com> opw-3470969 Forward-Port-Of: odoo/odoo#142754 Forward-Port-Of: odoo/odoo#136109
Multi-currency setup. On a bill, if the bill date and the accounting date are not the same, there will be some errors in the stock valuation. To reproduce the issue: (Company in USD) 1. Enable EUR, with specific rates: - Today: 100 EUR = 150 USD - One day ago: 100 EUR = 130 USD - Two days ago: 100 EUR = 125 USD 2. Create an auto-avco storable product P 3. Confirm a PO with 1 x P at 100 EUR 4. Receive the product 5. Bill it: - Bill date: two days ago - Accounting da
Original PR description
Multi-currency setup. On a bill, if the bill date and the accounting date are not the same, there will be some errors in the stock valuation. To reproduce the issue: (Company in USD) 1. Enable EUR, with specific rates: - Today: 100 EUR = 150 USD - One day ago: 100 EUR = 130 USD - Two days ago: 100 EUR = 125 USD 2. Create an auto-avco storable product P 3. Confirm a PO with 1 x P at 100 EUR 4. Receive the product 5. Bill it: - Bill date: two days ago - Accounting date: one day ago 6. Open the inventory valuation Error: a price diff layer has been created, which makes sense, but its value is incorrect: -20 USD. It should be -25 USD. When computing the price difference, we use the bill value at accounting date (130 USD). This is incorrect, it should be based on the bill date (125 USD). OPW-3544318 Forward-Port-Of: odoo/odoo#144500
The clean_attachment was invalidation the cache before 16.4, mainly because if an attachment is in cache of another worker and deleted, this will cause a 404 when this worker serves a page needing this attachment. This was changed because an attachment should be unlink through clean_attachments in two cases: - the code source changed on the server and a cold worker generates a bundle - an ir_asset was modified In the first case, we consider that the server restarted (normally) and all ca
Original PR description
The clean_attachment was invalidation the cache before 16.4, mainly because if an attachment is in cache of another worker and deleted, this will cause a 404 when this worker serves a page needing this attachment. This was changed because an attachment should be unlink through clean_attachments in two cases: - the code source changed on the server and a cold worker generates a bundle - an ir_asset was modified In the first case, we consider that the server restarted (normally) and all caches should be emptied. In the second case, a specific invalidation is made. But when something goes wrong, it is hard to debug, especially because there is no information on when the new attachment was created, and the previous one deleted. This should solve the issue by helping to identify the cause of the deletion. Forward-Port-Of: odoo/odoo#143765
Current behavior: When printing a PoS receipt from an SA company, the bottom of the receipt was cropped out. This was happening because the height of the receipt was calculated before the receipt was fully rendered. To fix this we wait a little bit before printing the receipt. Steps to reproduce: - Install l10n_sa_pos module - Link an ePos printer to the PoS - Create a PoS order - Validate it - Go in the paid order list, and try to print the receipt - The receipt will have his bottom c
Original PR description
Current behavior: When printing a PoS receipt from an SA company, the bottom of the receipt was cropped out. This was happening because the height of the receipt was calculated before the receipt was fully rendered. To fix this we wait a little bit before printing the receipt. Steps to reproduce: - Install l10n_sa_pos module - Link an ePos printer to the PoS - Create a PoS order - Validate it - Go in the paid order list, and try to print the receipt - The receipt will have his bottom cropped opw-3560618 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#144452 Forward-Port-Of: odoo/odoo#142727
[FIX] mail : HTML characters displayed in email Current behavior before PR: When you send an email at the receivers end you will see ` ` shown before you open the mail and it disappears once you open the email Desired behavior after PR is merged: Corrected and now the ` ` doesn't appear as a word where I replace it in the HTML template with its equivalent character opw-3481781 Forward-Port-Of: odoo/odoo#140712
Original PR description
[FIX] mail : HTML characters displayed in email Current behavior before PR: When you send an email at the receivers end you will see ` ` shown before you open the mail and it disappears once you open the email Desired behavior after PR is merged: Corrected and now the ` ` doesn't appear as a word where I replace it in the HTML template with its equivalent character opw-3481781 Forward-Port-Of: odoo/odoo#140712
Steps to reproduce: - Create a stored product - Update on hand quantity to 30 package P location WH-STOCK - Create and confirm an SO for that product - On the barcode app select the related picking - scan source location then scan the product and validate Bug: package is still set which will create a negative quantity for that package in the new location Fix: clear the package when changing source location if the package is not there opw-3546239 Forward-Port-Of: odoo/enterprise#
Original PR description
Steps to reproduce: - Create a stored product - Update on hand quantity to 30 package P location WH-STOCK - Create and confirm an SO for that product - On the barcode app select the related picking - scan source location then scan the product and validate Bug: package is still set which will create a negative quantity for that package in the new location Fix: clear the package when changing source location if the package is not there opw-3546239 Forward-Port-Of: odoo/enterprise#51709 Forward-Port-Of: odoo/enterprise#50713
Recurring value in reporting are now computed based on the recurrence and the line subtotal. opw-3550672 Forward-Port-Of: odoo/enterprise#51347
Original PR description
Recurring value in reporting are now computed based on the recurrence and the line subtotal. opw-3550672 Forward-Port-Of: odoo/enterprise#51347