Wednesday, June 26, 2024
20 changes · 17.0
Resolved issues and error corrections
This fix prevents the website courses area from crashing when users add a new tag or upload content with no existing tags or only one tag. It makes tag handling more reliable, so course content management continues smoothly.
Original PR description
In 76d328624fecaed5167b0e4fc1210014309d59a9, the underscore methods were removed. Following this change, a traceback occurs because concat is supposed to be used on an Array. When no element is in existing tags, addedTags is null, and if there is a single tag, it is not an array but an object. In order to fix this, we format properly the addedTags to have an array, allowing the use of the concat method. Task-3527175
The keyboard shortcut for checking Italian EDI document sending status was changed so it no longer conflicts with the shortcut for creating a new record. This prevents accidental actions and makes the workflow more reliable for users handling Italian electronic invoicing.
Original PR description
The keyboard shortcut for the `Check Sending` action was the same as the one used to create a new record. Ticket [link](https://www.odoo.com/web#model=project.task&id=3970056) opw-3970056
The restaurant point-of-sale setup now avoids changing default restaurant settings while the main restaurant has an active session. This reduces the risk of errors or disruption during ongoing sales activity.
Original PR description
Ensure that _setup_main_restaurant_defaults is only called when the main restaurant does not have an active session. This prevents potential errors that could occur if the method is called while a session is active. E.g: https://runbot.odoo.com/runbot/build/64372543 opw-3937178
Receipts for non-GCC countries no longer show a confusing colon and number that only applies to GCC receipts. This makes printed point-of-sale receipts clearer for customers and staff outside the GCC region.
Original PR description
Before this commit, when is_gcc_country was false, a colon followed by a number would appear in the receipt, which was confusing. This commit removes this misleading information for receipts in non-GCC countries. opw-3992612 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fix updates the Gmail and Outlook email server setup screens so their help links point to the correct Odoo documentation version. It helps users access accurate guidance when configuring email integrations, reducing confusion during setup.
Original PR description
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 update fixes display issues in Project screens on smaller devices. Customer rating frequency values now fit properly on mobile, and sub-task assignee controls appear only when needed to reduce visual clutter.
Original PR description
In this PR fixes the following issue:
- This pull request addresses a mobile view issue in the 'customer ratings' section by setting
the 'frequency' field width to 'auto.' This adjustment prevents content overflow on mobile devices,
enhancing user experience. Your review and feedback are appreciated for seamless integration.
- I'm submitting a pull request to address an issue in the 'project.task' kanban card. The problem is
the persistent visibility of the 'Assign People' button for sub-tasks, causing UI clutter. My solution
involves displaying the 'Assign People' button only upon hovering over a sub-task line within the
'project.task' kanban card's sub-tasks list. Your review and feedback on this change are appreciated.
task- 3549267
---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-prIssue ---- Quote is erroneously changed in the translation of python-expression-containing xml. Steps ----- - Change the language of the current user to swedish. - Try creating a new payment from Accounting -> Customers -> Payments -> New. - A parse error is thrown. Cause ----- The translated value of a xml snippet containing a python expression changed `'` to `’`, which has no meaning in python. opw-3989869
Original PR description
Issue ---- Quote is erroneously changed in the translation of python-expression-containing xml. Steps ----- - Change the language of the current user to swedish. - Try creating a new payment from Accounting -> Customers -> Payments -> New. - A parse error is thrown. Cause ----- The translated value of a xml snippet containing a python expression changed `'` to `’`, which has no meaning in python. opw-3989869
This change updates an internal automated test so it works consistently whether the mail app is installed or not. It helps prevent false test failures during development and supports more reliable release validation, with no direct change for end users.
Original PR description
We assert a hardcoded string with the name of the base.partner_root data inside test_onchange_one2many_default(). Without mail this name is "System", with the mail module it becomes "OdooBot". Then the test works if we have mail installed
The Mexican eCommerce invoicing information page can now be included in translation workflows, so customers using French no longer see that checkout step in English. This helps multilingual websites provide a more consistent shopping experience for international visitors.
Original PR description
To recreate the bug follow the instruction: - Install website with eCommerce app - Install l10n_mx modules - Add french as language for the website - Add an item from the eCommerce page to the cart - Go to Expedition page then to Invoicing Info page We remark that the pagee is in english (the default language) and not translated to french A client from Mexico suffered from translation problem in his website. He has 3 languages [English, Spanish, France]. The globality of the website get translated successfully to the 3 languages, except the "invoicing info" page in the eCommerce app. The thing is that this page is not normally existent in the standard eCommerce Site, it only get added if you install l10n_mx_edi_website_sale modul witch contains only translation from english to spanich. I suggest adding the french translation since a website is supposed to be visitable every country. opw-3881171
Miscellaneous changes
Steps: - Install l10n_fr and make sure fr company has tax id filled - Go to bank journal and set a bank account number - Go to Customer invoice journal and check `Factur-X` in the Advenced Settings tab - Create a french customer F with an email address - Open a pos session, and make an invoice forF for a product with tax, select Bank payment method and confirm - Go to invoices and select the newly created invoice -> "Error occured while creating the EDI document" Cause: The field `partner
Original PR description
Steps: - Install l10n_fr and make sure fr company has tax id filled - Go to bank journal and set a bank account number - Go to Customer invoice journal and check `Factur-X` in the Advenced Settings tab - Create a french customer F with an email address - Open a pos session, and make an invoice forF for a product with tax, select Bank payment method and confirm - Go to invoices and select the newly created invoice -> "Error occured while creating the EDI document" Cause: The field `partner_bank_id` is not set from the pos order to the invoice cbe1cf5b1044827a058a4cde5d0492a545ac6da4 added a condition specifically for swiss localisation. Fix: Movr the condition to a bridge module for swiss localisation opw-3992498 Forward-Port-Of: odoo/odoo#170762
Purpose ======= Fix the display of the quiz comment line: - the trash icon is displayed under the line instead of next to it. - the comment input is too large and should be aligned with the answers inputs. Specification ============= The comment input is too large because the "form-control" class has a "width: 100%" style that overwrites the "width: 66.66666667%" one applied by the "col-8" class. The good fix would be to create a new parent for the input and apply the "col-8" class
Original PR description
Purpose ======= Fix the display of the quiz comment line: - the trash icon is displayed under the line instead of next to it. - the comment input is too large and should be aligned with the answers inputs. Specification ============= The comment input is too large because the "form-control" class has a "width: 100%" style that overwrites the "width: 66.66666667%" one applied by the "col-8" class. The good fix would be to create a new parent for the input and apply the "col-8" class to limit its width accordingly while still keeping the good row gutters and margins. However as changing the xml structure is not recommended in stable, the fix is to add the "col-8" on the current "row" parent and forcing the trash icon to be next to by using the "flex-nowrap" class. Task-3986982 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#169237
This pull request does not include enough change details to identify a specific business impact. Based on the available information, it appears to be a placeholder or miscellaneous update with no listed affected files or commits.
Original PR description
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
### Steps to reproduce: - Create a storable product P using the manifacturing route - Create a BOM for that product with 2 lines: 1 x storable product COMP 1 using buy route and with a set vendor and a delivery lead time of 1 day 1 x storable product COMP 2 without any route or using the buy route without vendor - In the inventory tab of your storable product P, click on compute the "Days to prepare Manufacturing Order" from BoM ### Current Behavior: Since the second component is not
Original PR description
### Steps to reproduce: - Create a storable product P using the manifacturing route - Create a BOM for that product with 2 lines: 1 x storable product COMP 1 using buy route and with a set vendor and…
### Steps to reproduce: - Create a storable product P using the manifacturing route - Create a BOM for that product with 2 lines: 1 x storable product COMP 1 using buy route and with a set vendor and a delivery lead time of 1 day 1 x storable product COMP 2 without any route or using the buy route without vendor - In the inventory tab of your storable product P, click on compute the "Days to prepare Manufacturing Order" from BoM ### Current Behavior: Since the second component is not available, the final product is not available and the number of days to prepare the MO is set to 0 so that nothing happens: https://github.com/odoo/odoo/blob/2744217900c4eb985bd71919ef86614ab95c0fd0/addons/mrp/report/mrp_report_bom_structure.py#L680-L688 ### Expected behavior: A warning should be raised to notify the user that at least one of the component is not availabe. opw-3933989 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#167136
According to the documentation, the user receives their registration code through SMS, so phone number label is misleading. Steps to reproduce: 1.Install account_peppol > install an peppol egilible accounting l10n (i.e l10n_be) 2.In settings > technical > system parameter > set account_peppol.edi.mode to test 2.in settings search for peppol 3.notice how the phone number is requested in the registration form 4.click on validate registration 5.notice how the validation button displays
Original PR description
According to the documentation, the user receives their registration code through SMS, so phone number label is misleading.
Steps to reproduce:
1.Install account_peppol > install an peppol egilible accounting l10n (i.e l10n_be)
2.In settings > technical > system parameter > set account_peppol.edi.mode to test
2.in settings search for peppol
3.notice how the phone number is requested in the registration form
4.click on validate registration
5.notice how the validation button displays "verify phone number" while the verification code is sent by sms
Solution:
refactor labels, buttons, helps and errors message to indicate mobile number. The actual field account_peppol_phone_number is not renamed as per stable version changes condition.
opw-3977664
---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Forward-Port-Of: odoo/odoo#169607Steps: - Install Project - Inside project task list view, select all task - Print timesheets Issues: - Header of some tables appears double Cause: - Missing grouping container css inside table header Fix: - Proper css was added to group container inside table header task-3744319 Forward-Port-Of: odoo/odoo#154840
Original PR description
Steps: - Install Project - Inside project task list view, select all task - Print timesheets Issues: - Header of some tables appears double Cause: - Missing grouping container css inside table header Fix: - Proper css was added to group container inside table header task-3744319 Forward-Port-Of: odoo/odoo#154840
the fix replaces the `\xa0` with ` ` for html translated values and keeps the consistent logic as odoo/odoo#110148 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#170692
Original PR description
the fix replaces the `\xa0` with ` ` for html translated values and keeps the consistent logic as odoo/odoo#110148 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#170692
## Steps to reproduce: - Install POS app - Change the warehouse to a 2-step delivery method - Create a sales order for a product and confirm - Ensure the product is reserved for the picking transfer **as** the issue doesn't exist (all transfers are successfully cancelled) if there are no products reserved - Go to POS and settle the sales order - The delivery transfer is cancelled but the picking transfer (with product reserved) is not cancelled. although all transfers should be cancelled i
Original PR description
## Steps to reproduce: - Install POS app - Change the warehouse to a 2-step delivery method - Create a sales order for a product and confirm - Ensure the product is reserved for the picking transfer **as** the issue doesn't exist (all transfers are successfully cancelled) if there are no products reserved - Go to POS and settle the sales order - The delivery transfer is cancelled but the picking transfer (with product reserved) is not cancelled. although all transfers should be cancelled if the order is fully delivered! ## Investigation: - When the product is already reserved, the picking transfer is in the **Ready/assigned** state - When updating the steps, the **Ready/assigned** state is not taken into consideration and so the picking transfer is not updated to be **cancelled** opw-3474929 Forward-Port-Of: odoo/odoo#169197 Forward-Port-Of: odoo/odoo#164753
This commit fixes an issue introduced by https://github.com/odoo/odoo/pull/170159. forEach is not available for mapIterator on non-chromium based browser. opw-4008053 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#170702
Original PR description
This commit fixes an issue introduced by https://github.com/odoo/odoo/pull/170159. forEach is not available for mapIterator on non-chromium based browser. opw-4008053 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#170702
Problem --------- A new version of the SEPA Direct Debit Schema (Pain 008.001.08) is available and will soon be usable in some countries. In Belgium for example, it will be supported by ISABEL soon, and is already published in the Netherlands. Objective --------- Add the new schema and allow the user to select which version to use. Solution --------- 1. In Bank Journal configuration, tab Incoming Payments, add a configuration section where the user can select what version of SEPA Dir
Original PR description
Problem --------- A new version of the SEPA Direct Debit Schema (Pain 008.001.08) is available and will soon be usable in some countries. In Belgium for example, it will be supported by ISABEL soon, and is already published in the Netherlands. Objective --------- Add the new schema and allow the user to select which version to use. Solution --------- 1. In Bank Journal configuration, tab Incoming Payments, add a configuration section where the user can select what version of SEPA Direct Debit he wants to use. Done through a selection field. 2. Implement the SEPA Direct Debit 008.001.08 format and allow the xml export of that schema. task-3440881 Forward-Port-Of: odoo/enterprise#65216 Forward-Port-Of: odoo/enterprise#65083
The MX_EDI page does not show up on delivery orders, preventing the user from creating one with the 'Federal Transport' transport type. ### Steps to reproduce: - Install l10n_mx_edi_stock and l10n_mx_edi_stock_30 - Switch to a Mexican company - Go in Inventory > Delivery Orders and create a new one - Select 'Federal Transport' for the Transport Type field. - The MX_EDI page does not show up preventing you from validating because the field 'Vehicle Setup' is in this page and is required
Original PR description
The MX_EDI page does not show up on delivery orders, preventing the user from creating one with the 'Federal Transport' transport type. ### Steps to reproduce: - Install l10n_mx_edi_stock and l10n_mx_edi_stock_30 - Switch to a Mexican company - Go in Inventory > Delivery Orders and create a new one - Select 'Federal Transport' for the Transport Type field. - The MX_EDI page does not show up preventing you from validating because the field 'Vehicle Setup' is in this page and is required ### Cause: In l10n_mx_edi_stock_30 the page is given a new attribute making it invisible if the state of the picking is not done. ### Solution: Remove the problematic attribute. opw-3988230 Forward-Port-Of: odoo/enterprise#65410