Thursday, June 6, 2024
34 changes · saas-17.3
Resolved issues and error corrections
This update addresses follow-up comments from the recent expense onboarding work, polishing how expense-related products and list or kanban views behave. It helps make the onboarding experience more consistent and reduces minor issues for users setting up expenses.
Original PR description
This commit resolves the unresolved comments mentioned on the expense onboarding PR https://github.com/odoo/odoo/pull/166321 task-3919542 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The self-ordering product screen now opens product information correctly when users tap the info button. This prevents an error from interrupting customers or staff during ordering, improving checkout reliability.
Original PR description
Before this commit: ========== - Clicking the product info button on the product screen caused a traceback. After this commit: ========== - The product info button functions properly, and the traceback is no longer present. task-3972473
The payment reminder email template can now be previewed without failing when a payment link is unavailable. This prevents confusion for users reviewing reminder emails and keeps template setup smoother.
Original PR description
**Version:** - master **Steps to reproduce:**: - open 'subscription: payment reminder' template - click on preview **Issue:** - preview payment reminder template it is giving error because it is not getting payment link for 'pay now' button. **Solution:** - added a fallback value for 'pay now' button if it not get payment link value. task-3956795
Miscellaneous changes
Current behavior: In certain currencies, you have coin of values like 0.025 that requires more than 2 decimal places. But in the coin/bills view they were not correctly showed. Values like 0.025 would appear as 0.02 Steps to reproduce: - Create a new company using a currency that needs 3 decimal places (Bahraini Dinar) - Try to create coin/bills with a value like 0.025 - After saving the last part cannot be seen anymore opw-3950930 --- I confirm I have signed the CLA and read the PR
Original PR description
Current behavior: In certain currencies, you have coin of values like 0.025 that requires more than 2 decimal places. But in the coin/bills view they were not correctly showed. Values like 0.025 would appear as 0.02 Steps to reproduce: - Create a new company using a currency that needs 3 decimal places (Bahraini Dinar) - Try to create coin/bills with a value like 0.025 - After saving the last part cannot be seen anymore opw-3950930 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#168011 Forward-Port-Of: odoo/odoo#167497
Problem: When a quotation is printed for a client in a different language that uses different decimal separators, the discounted price for optional products are not being displayed with the same decimal separators used throughout the quotation. Purpose: The formats of the price should be consistent. Steps to Reproduce on Runbot: 1. Install Sales 2. Enable Discounts in Setting > Sales 3. Create a quotation with a German customer and discounted optional products 4. Print the quotation 5
Original PR description
Problem: When a quotation is printed for a client in a different language that uses different decimal separators, the discounted price for optional products are not being displayed with the same decimal separators used throughout the quotation. Purpose: The formats of the price should be consistent. Steps to Reproduce on Runbot: 1. Install Sales 2. Enable Discounts in Setting > Sales 3. Create a quotation with a German customer and discounted optional products 4. Print the quotation 5. Observe the discounted price has inconsistent formatting (ex. shows 140.00 instead of 140,00 since German uses , as decimal separators) opw-3853464 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#167688 Forward-Port-Of: odoo/odoo#165888
### Issue: Pickings associated to different customers are merged in 2 steps delivery setups. ### Steps to reproduce: - Create 2 storable products: P1 and P2 - Enable multistep routes in the settings > set Warehouse Routes - Create a new warehouse WH2 with 2 steps delivery - Go to inventory > Pick (WH2) - Create and validate a new pick for Customer 1: 1 x P1 Note: A delivery order was created for customer 1 - Create and validate a new pick for Customer 2: 1 x P2 ### Expected b
Original PR description
### Issue: Pickings associated to different customers are merged in 2 steps delivery setups. ### Steps to reproduce: - Create 2 storable products: P1 and P2 - Enable multistep routes in the settings…
### Issue: Pickings associated to different customers are merged in 2 steps delivery setups. ### Steps to reproduce: - Create 2 storable products: P1 and P2 - Enable multistep routes in the settings > set Warehouse Routes - Create a new warehouse WH2 with 2 steps delivery - Go to inventory > Pick (WH2) - Create and validate a new pick for Customer 1: 1 x P1 Note: A delivery order was created for customer 1 - Create and validate a new pick for Customer 2: 1 x P2 ### Expected behavior: A delivery order is created for customer 2 ### Current behavior: The new delivery order is merged with delivery order created for customer 1 and the delivery address is erased as the picking would be associated with 2 contacts. ### Cause of the issue: When generated for the customer delivery is generated by the 2 step delivery the `_assign_picking` methods tries to assign the move to an existing picking if possible: https://github.com/odoo/odoo/blob/71b4a97c9e3da94bfc0130371db2c02beb81eebe/addons/stock/models/stock_move.py#L1250-L1254 However, the `partner_id` is only used in the search domain of this picking if the usage of the `location_id/dest_id` is a transit: https://github.com/odoo/odoo/blob/71b4a97c9e3da94bfc0130371db2c02beb81eebe/addons/stock/models/stock_move.py#L1240-L1241 This should also be the case when the destination is a customer. ### Note: The issue did not occur prior to saas-17.2 since no "Out" transfer were generated by manual pick transfer in 2 steps delivery prior to this version. opw-3857526 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#163135
Current behavior: Sometimes payment made with adyen where blocked in the "Waiting for card" status when cancelling a payment. As the issue is not reproducible consistantly I made a diagram to show what I think is happening. It was probably happening because the last_adyen_status was emptied at a wrong moment. To fix this we make sure that a real new payment request is made before emptying it. Before this fix when doing a cancel request, it would empty the last_adyen_status  opw-3427860 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#168056 Forward-Port-Of: odoo/odoo#165792
Currently, if you have `pos_restaurant` but not `pos_self_order`, if you add a note on one line of the restaurant order, it visually disappears if you change table and then come back to it. Steps to reproduce: ------------------- * Install `pos_restanrant` * Uninstall `pos_self_order` * Open the restaurant session * Select a table and add an item to the order * Write an internal note > You can see the note on the line * Select **Change table** * Come back to the previous table > T
Original PR description
Currently, if you have `pos_restaurant` but not `pos_self_order`, if you add a note on one line of the restaurant order, it visually disappears if you change table and then come back to it. Steps to…
Currently, if you have `pos_restaurant` but not `pos_self_order`, if you add a note on one line of the restaurant order, it visually disappears if you change table and then come back to it. Steps to reproduce: ------------------- * Install `pos_restanrant` * Uninstall `pos_self_order` * Open the restaurant session * Select a table and add an item to the order * Write an internal note > You can see the note on the line * Select **Change table** * Come back to the previous table > The note is not visible anymore Why the fix: ------------ The note added is correctly registered but just invisible to the waiter. It is also visible in the display if you send the order in. The note field is added by the module `pos_restaurant` but loaded to the ui in `pos_self_order`. Technically the module `pos_self_order` gets auto-installed when `pos_restaurant` is installed but some customer might not have `pos_self_order` if they uninstalled it for example. `pos_self_order` depends on `pos_restaurant` so we can safely move the code that exports it inside the root module (`pos_restaurant`). The fix starts in 17.0 as in previous versions it was working fine with only `pos_restaurant` installed. opw-3917013 Forward-Port-Of: odoo/odoo#167839 Forward-Port-Of: odoo/odoo#167223
## Pull Request HOOT (PROOT) - part 16 Part 1: https://github.com/odoo/odoo/pull/152930 Part 2: https://github.com/odoo/odoo/pull/153018 Part 3: https://github.com/odoo/odoo/pull/153023 Part 4: https://github.com/odoo/odoo/pull/153203 Part 5: https://github.com/odoo/odoo/pull/153425 Part 6: https://github.com/odoo/odoo/pull/153700 Part 7: https://github.com/odoo/odoo/pull/154054 Part 8: https://github.com/odoo/odoo/pull/154579 Part 9: https://github.com/odoo/odoo/pull/155073 Part 10:
Original PR description
## Pull Request HOOT (PROOT) - part 16 Part 1: https://github.com/odoo/odoo/pull/152930 Part 2: https://github.com/odoo/odoo/pull/153018 Part 3: https://github.com/odoo/odoo/pull/153023 Part 4:…
## Pull Request HOOT (PROOT) - part 16 Part 1: https://github.com/odoo/odoo/pull/152930 Part 2: https://github.com/odoo/odoo/pull/153018 Part 3: https://github.com/odoo/odoo/pull/153023 Part 4: https://github.com/odoo/odoo/pull/153203 Part 5: https://github.com/odoo/odoo/pull/153425 Part 6: https://github.com/odoo/odoo/pull/153700 Part 7: https://github.com/odoo/odoo/pull/154054 Part 8: https://github.com/odoo/odoo/pull/154579 Part 9: https://github.com/odoo/odoo/pull/155073 Part 10: https://github.com/odoo/odoo/pull/155639 Part 11: https://github.com/odoo/odoo/pull/156255 / https://github.com/odoo/enterprise/pull/58135 Part 12: https://github.com/odoo/odoo/pull/156869 Part 13: https://github.com/odoo/odoo/pull/158384 / https://github.com/odoo/enterprise/pull/59019 Part 14: https://github.com/odoo/odoo/pull/158916 Part 15: https://github.com/odoo/odoo/pull/160292 / https://github.com/odoo/enterprise/pull/59971 Part 15.5: https://github.com/odoo/odoo/pull/166463 Enterprise: https://github.com/odoo/enterprise/pull/62998 This pull requests brings various improvements and fixes to Hoot and the Odoo unit test ecosystem. See the different commit messages for more details. Note: these changes are made in stable to avoid having to support multiple versions of the HOOT API. As such, these changes are intended to be strictly limited to unit tests as to not put the rest of the code base at risk. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#166311
Issue: ====== list doesn't appear in quick edit of html_field Steps to reproduce the issue: ============================= - Go to any sale order - Send by email - Add a list inside the email - It doesn't appear Origin of the issue: ==================== Most of the templates have hardcoded `padding = 0px`, so when we convert a `p` element to a `ul` or `ol` element it will have have the same styling and we loose the default padding for the list elements. Solution: ========= We
Original PR description
Issue: ====== list doesn't appear in quick edit of html_field Steps to reproduce the issue: ============================= - Go to any sale order - Send by email - Add a list inside the email - It doesn't appear Origin of the issue: ==================== Most of the templates have hardcoded `padding = 0px`, so when we convert a `p` element to a `ul` or `ol` element it will have have the same styling and we loose the default padding for the list elements. Solution: ========= We set the padding as null to remove any forced padding used. opw-3900433 Forward-Port-Of: odoo/odoo#167916 Forward-Port-Of: odoo/odoo#165773
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#164643
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 Forward-Port-Of: odoo/odoo#164643
Prior to this commit, if a reward product domain contained a field that was not loaded into the Point of Sale (PoS), the promotion would not function correctly. This commit resolves this issue by adding the missing fields, ensuring that the promotion operates as expected. opw-3896038 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#164892
Original PR description
Prior to this commit, if a reward product domain contained a field that was not loaded into the Point of Sale (PoS), the promotion would not function correctly. This commit resolves this issue by adding the missing fields, ensuring that the promotion operates as expected. opw-3896038 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#164892
opw-3940549 opw-3943985 opw-3943909 opw-3937897 opw-3932111 Forward-Port-Of: odoo/odoo#166980
Original PR description
opw-3940549 opw-3943985 opw-3943909 opw-3937897 opw-3932111 Forward-Port-Of: odoo/odoo#166980
Before this commit, the attendees were not allowed to remove anyone from the event (including themselves) when editing the event in the form view. This was a problem that came after updating the views to OWL and also reverting the PR [#133504](https://github.com/odoo/odoo/pull/133504). After this commit, the event attendees can perform attendee removals normally because we check inside the compute if it the current attendee was indeed an attendee right before the change is completed. task-
Original PR description
Before this commit, the attendees were not allowed to remove anyone from the event (including themselves) when editing the event in the form view. This was a problem that came after updating the views to OWL and also reverting the PR [#133504](https://github.com/odoo/odoo/pull/133504). After this commit, the event attendees can perform attendee removals normally because we check inside the compute if it the current attendee was indeed an attendee right before the change is completed. task-3948322 Forward-Port-Of: odoo/odoo#166696
Steps to reproduce: - In Website edit mode. - Drag and drop a "Form" snippet onto the page. - Add a multi checkboxes field to the form. - Edit the text of a checkboxes input. - click on the toggle button next to this input. - Bug: the button remains disabled. (next click is ok) This bug occurs because when we search for the checkbox that should be selected in the "values" variable (in the "_notifyCurrentState()" function of the "we-list" widget), we search for it based on its ID in
Original PR description
Steps to reproduce: - In Website edit mode. - Drag and drop a "Form" snippet onto the page. - Add a multi checkboxes field to the form. - Edit the text of a checkboxes input. - click on the toggle button next to this input. - Bug: the button remains disabled. (next click is ok) This bug occurs because when we search for the checkbox that should be selected in the "values" variable (in the "_notifyCurrentState()" function of the "we-list" widget), we search for it based on its ID in the DOM. However, on the first click on the toggle, the ID has not yet been defined in the DOM according to the "values" variable. task-3901472 Forward-Port-Of: odoo/odoo#167842 Forward-Port-Of: odoo/odoo#165264
opw-3954458 Forward-Port-Of: odoo/odoo#167078
Original PR description
opw-3954458 Forward-Port-Of: odoo/odoo#167078
To facilitate the usage of the router in custom webclients like the Knowledge portal, `url-state` conversion functions are attached to the router object to allow patching them, in order to handle a custom router state. task-3743416 Forward-Port-Of: odoo/odoo#166994
Original PR description
To facilitate the usage of the router in custom webclients like the Knowledge portal, `url-state` conversion functions are attached to the router object to allow patching them, in order to handle a custom router state. task-3743416 Forward-Port-Of: odoo/odoo#166994
Problem: There is taxes added to the gift card discount Steps to reproduce: - Install "Point of sale" app - Go to Settings and activate gift cards - Create a gift card (for ex 100€) - Copy the code - Open PoS > Add a product (more than the price of the gift card to understand better) > add the gift card - The card value is not 100€ but more because it includes taxes Solution: Set an empty Array as tax will allow this.tax_ids to be evaluated as true in a if statement and will define
Original PR description
Problem: There is taxes added to the gift card discount Steps to reproduce: - Install "Point of sale" app - Go to Settings and activate gift cards - Create a gift card (for ex 100€) - Copy the code - Open PoS > Add a product (more than the price of the gift card to understand better) > add the gift card - The card value is not 100€ but more because it includes taxes Solution: Set an empty Array as tax will allow this.tax_ids to be evaluated as true in a if statement and will define an empty Array for the tax of the gift card https://github.com/odoo/odoo/blob/7df8fc435c6ea199292f47954202d4f3c93b2629/addons/point_of_sale/static/src/app/store/models.js#L745-L749 opw-3862427 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#163928
**Description of the issue/feature this PR addresses:** fine tuning of https://github.com/odoo/odoo/commit/f8182fb625eb3e20c85388d4c342553af4fe7ab9 to prevent an olverload of postgres. @thle-odoo @sofiagvaladze I have update the commit. I use 'inselect' to reduce the query size. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#167439
Original PR description
**Description of the issue/feature this PR addresses:** fine tuning of https://github.com/odoo/odoo/commit/f8182fb625eb3e20c85388d4c342553af4fe7ab9 to prevent an olverload of postgres. @thle-odoo @sofiagvaladze I have update the commit. I use 'inselect' to reduce the query size. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#167439
Before this commit, loading an attribute value with an image would cause a TypeError due to the image data being of bytes type, which is not JSON serializable. This commit prevents this error by removing the image data before serialization. opw-3957587 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#167765
Original PR description
Before this commit, loading an attribute value with an image would cause a TypeError due to the image data being of bytes type, which is not JSON serializable. This commit prevents this error by removing the image data before serialization. opw-3957587 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#167765
starts. If the user language cannot be determined, it uses the one set in the html `lang` attribute. If this language is not installed, the webclient translation route does not return lang parameters such as date fortmat. However, the JS code expects those parameters to be available and missing parameters lead to multiple errors (e.g. when calling `parseDatetime` which requires the date format). This PR ignore the lang passed to this route if it is not installed in order for it to fallback
Original PR description
starts. If the user language cannot be determined, it uses the one set in the html `lang` attribute. If this language is not installed, the webclient translation route does not return lang parameters such as date fortmat. However, the JS code expects those parameters to be available and missing parameters lead to multiple errors (e.g. when calling `parseDatetime` which requires the date format). This PR ignore the lang passed to this route if it is not installed in order for it to fallback to the context lang. Steps to reproduce the issue: - Create an html page and set the lang attribute value to the IETF Xhosa tag (xh-ZA) - A request to `/web/webclient/translation` is made and an error is displayed in the console. opw-3953457 Forward-Port-Of: odoo/odoo#167491
Before, if a bank transaction contain the sale order reference, the reconciliation model will try to reconcile with the invoices created from this sale order but ignore the payment records for those. This leads to situations where it looks like there were two payments on the invoices (one payment record and one bank transaction) while there is just one partial payment. Steps to reproduce: 0/ Have default reconciliation models 1/ Create SO for 100$ and confirm invoice 2/ Partially pay invoi
Original PR description
Before, if a bank transaction contain the sale order reference, the reconciliation model will try to reconcile with the invoices created from this sale order but ignore the payment records for those. This leads to situations where it looks like there were two payments on the invoices (one payment record and one bank transaction) while there is just one partial payment. Steps to reproduce: 0/ Have default reconciliation models 1/ Create SO for 100$ and confirm invoice 2/ Partially pay invoice for 70$ 3/ Create bank transaction with SO ref and same partner for 70$ 4/ Match transaction => will match the 30$ residual of the invoice instead of 70$ payment Now, the system will try to reconcile with the payments of those invoices first before considering invoice reconciliation. opw-3904177 Forward-Port-Of: odoo/enterprise#62972
In the Payroll app with a Belgian company, we can do Reporting > Paid Time Off Allocation. This opens a wizard and if we filled the department then the time off type, the app would crash because of a terrible sql query. Also, the query was doing unnecessary subqueries that have been removed. Task: 3878904 Forward-Port-Of: odoo/enterprise#62293
Original PR description
In the Payroll app with a Belgian company, we can do Reporting > Paid Time Off Allocation. This opens a wizard and if we filled the department then the time off type, the app would crash because of a terrible sql query. Also, the query was doing unnecessary subqueries that have been removed. Task: 3878904 Forward-Port-Of: odoo/enterprise#62293
## Pull Request HOOT (PROOT) - part 16 Part 1: https://github.com/odoo/odoo/pull/152930 Part 2: https://github.com/odoo/odoo/pull/153018 Part 3: https://github.com/odoo/odoo/pull/153023 Part 4: https://github.com/odoo/odoo/pull/153203 Part 5: https://github.com/odoo/odoo/pull/153425 Part 6: https://github.com/odoo/odoo/pull/153700 Part 7: https://github.com/odoo/odoo/pull/154054 Part 8: https://github.com/odoo/odoo/pull/154579 Part 9: https://github.com/odoo/odoo/pull/155073 Part 10:
Original PR description
## Pull Request HOOT (PROOT) - part 16 Part 1: https://github.com/odoo/odoo/pull/152930 Part 2: https://github.com/odoo/odoo/pull/153018 Part 3: https://github.com/odoo/odoo/pull/153023 Part 4:…
## Pull Request HOOT (PROOT) - part 16 Part 1: https://github.com/odoo/odoo/pull/152930 Part 2: https://github.com/odoo/odoo/pull/153018 Part 3: https://github.com/odoo/odoo/pull/153023 Part 4: https://github.com/odoo/odoo/pull/153203 Part 5: https://github.com/odoo/odoo/pull/153425 Part 6: https://github.com/odoo/odoo/pull/153700 Part 7: https://github.com/odoo/odoo/pull/154054 Part 8: https://github.com/odoo/odoo/pull/154579 Part 9: https://github.com/odoo/odoo/pull/155073 Part 10: https://github.com/odoo/odoo/pull/155639 Part 11: https://github.com/odoo/odoo/pull/156255 / https://github.com/odoo/enterprise/pull/58135 Part 12: https://github.com/odoo/odoo/pull/156869 Part 13: https://github.com/odoo/odoo/pull/158384 / https://github.com/odoo/enterprise/pull/59019 Part 14: https://github.com/odoo/odoo/pull/158916 Part 15: https://github.com/odoo/odoo/pull/160292 / https://github.com/odoo/enterprise/pull/59971 Part 15.5: https://github.com/odoo/odoo/pull/166463 Community: https://github.com/odoo/odoo/pull/166311 This pull requests brings various improvements and fixes to Hoot and the Odoo unit test ecosystem. See the different commit messages for more details. Note: these changes are made in stable to avoid having to support multiple versions of the HOOT API. As such, these changes are intended to be strictly limited to unit tests as to not put the rest of the code base at risk. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/enterprise#62998
The aim of this commit is to make the code more robust and defensive by handling a bad value for the `vat` field. Context: Partners having a `partner.vat=False` were making the compact function crash. Before the commit: The flow crash even if the value shouldn't be processed. After the commit: The flow is smooth. task-id: None Forward-Port-Of: odoo/enterprise#63865
Original PR description
The aim of this commit is to make the code more robust and defensive by handling a bad value for the `vat` field. Context: Partners having a `partner.vat=False` were making the compact function crash. Before the commit: The flow crash even if the value shouldn't be processed. After the commit: The flow is smooth. task-id: None Forward-Port-Of: odoo/enterprise#63865
...d on foreign_currency_code received from odoofin Send `include_foreign_currency` to odoofin to avoid throwing errors when odoofin returns `foreign_currency_code` and `amount_currency` for customers that don't have the fix. Convert `foreign_currency_code` to corresponding `foreign_currency_id` in order to be displayed correctly alongside the amount in `account.bank.statement.line` To avoid a validation error(Currency is not activated) pop up for every foreign currency resides in trans
Original PR description
...d on foreign_currency_code received from odoofin Send `include_foreign_currency` to odoofin to avoid throwing errors when odoofin returns `foreign_currency_code` and `amount_currency` for customers that don't have the fix. Convert `foreign_currency_code` to corresponding `foreign_currency_id` in order to be displayed correctly alongside the amount in `account.bank.statement.line` To avoid a validation error(Currency is not activated) pop up for every foreign currency resides in transactions received from Odoofin while fetching transactions, Automatically activating foreign currencies. Remove foreign_currency_id and amount_currency from retrieved transactions in `Fetch Missing Transactions` flow in order to not break the flow in stable.(These fields will be added to `account.bank.statement.line.transient` in master) Odoofin PR: https://github.com/odoo/odoofin/pull/265 task id: 2870614 Forward-Port-Of: odoo/enterprise#60337
Intended: Generate pdfs is meant to run in every hour. It was intention as well at creation and it shows from how nextcall is defined: <field name="nextcall" eval="(DateTime.now() + timedelta(hours=1))"/> Current behavior: But regardless how nextcall is defined, now the cron runs in every month. This is because interval_type is not explicitly defined on the cron and thus it takes default value - that is 'months'. To correct the cron behavior, we explicitly define interval_number
Original PR description
Intended: Generate pdfs is meant to run in every hour. It was intention as well at creation and it shows from how nextcall is defined: <field name="nextcall" eval="(DateTime.now() + timedelta(hours=1))"/> Current behavior: But regardless how nextcall is defined, now the cron runs in every month. This is because interval_type is not explicitly defined on the cron and thus it takes default value - that is 'months'. To correct the cron behavior, we explicitly define interval_number and interval_type task-3960037 Forward-Port-Of: odoo/enterprise#63709 Forward-Port-Of: odoo/enterprise#63565
Include the version of Odoo in the UserAgent header of SIP requests so that the information is available to the provider. Task-3940569 Forward-Port-Of: odoo/enterprise#63281 Forward-Port-Of: odoo/enterprise#62879
Original PR description
Include the version of Odoo in the UserAgent header of SIP requests so that the information is available to the provider. Task-3940569 Forward-Port-Of: odoo/enterprise#63281 Forward-Port-Of: odoo/enterprise#62879
This reverts commit 819ed2a64d0f11f33190af0c804955e380242968. opw-3955626 but there are many others Forward-Port-Of: odoo/enterprise#63484
Original PR description
This reverts commit 819ed2a64d0f11f33190af0c804955e380242968. opw-3955626 but there are many others Forward-Port-Of: odoo/enterprise#63484
Before this commit, when adding an outdated activity from kanban activity widget, it crashed with the following errors: `TypeError: cannot read property of undefined (reading `mail_template_ids`)` `TypeError: Cannot read properties of undefined (reading 'toLocaleString')` Steps to reproduce: - on crm lead schedule call activity and make sure that activity is at least 1 month old - book activity and save it - try to access/edit activity This happens because when the `get_today_call_a
Original PR description
Before this commit, when adding an outdated activity from kanban activity widget, it crashed with the following errors: `TypeError: cannot read property of undefined (reading `mail_template_ids`)` `TypeError: Cannot read properties of undefined (reading 'toLocaleString')` Steps to reproduce: - on crm lead schedule call activity and make sure that activity is at least 1 month old - book activity and save it - try to access/edit activity This happens because when the `get_today_call_activities` function is called. Function fetches fields during the records formatting, but it doesn't fetch `date_deadline` and `mail_template_ids`, therefore those fields remain undefined, hence the errors rise. task-3945492 Forward-Port-Of: odoo/enterprise#63792
Handle barcode lookup api key and get from the tools to secure and avoid server action or any other unnecessary calls for getting API key. Forward-Port-Of: odoo/enterprise#62245
Original PR description
Handle barcode lookup api key and get from the tools to secure and avoid server action or any other unnecessary calls for getting API key. Forward-Port-Of: odoo/enterprise#62245
This PR fixes two issues with the portal web client of Knowledge: - When a portal user opens an article and clicks on an article of the sidebar, the article id specified in the route url and the session are not updated. The router only updates the url params of the url. When the user loads the page, the client script will load the article specified in the session. As the session is not updated when switching article, the script can load an incorrect article when reloading the page. This PR ai
Original PR description
This PR fixes two issues with the portal web client of Knowledge: - When a portal user opens an article and clicks on an article of the sidebar, the article id specified in the route url and the…
This PR fixes two issues with the portal web client of Knowledge: - When a portal user opens an article and clicks on an article of the sidebar, the article id specified in the route url and the session are not updated. The router only updates the url params of the url. When the user loads the page, the client script will load the article specified in the session. As the session is not updated when switching article, the script can load an incorrect article when reloading the page. This PR aims to fix that issue by ensuring that the client script will load the article with the id specified in the url params of the url. - When a portal user opens an article, clicks on an article of the sidebar and presses the back button, the system updates the url params and set the right id but it doesn't load the corresponding article in the view. This PR aims to fix that issue by ensuring that the web client load the article whenever the url changes. task-3743416 Forward-Port-Of: odoo/enterprise#63218 Forward-Port-Of: odoo/enterprise#60845
In the salary configurator, we use a meal voucher amount by default: 7 .45€/worked day. It should really copy the meal voucher amount from the contract instead. Task: Forward-Port-Of: odoo/enterprise#63851 Forward-Port-Of: odoo/enterprise#61655
Original PR description
In the salary configurator, we use a meal voucher amount by default: 7 .45€/worked day. It should really copy the meal voucher amount from the contract instead. Task: Forward-Port-Of: odoo/enterprise#63851 Forward-Port-Of: odoo/enterprise#61655
Steps to reproduce: 1. Install the planning module and open it. 2. Open events in calendar view. 3. Click on any event. 4. In the calendar popover, observe the spacing around the percentage (%). Issue: There is inconsistency in spacing around the percentage (%). Solution: Add a space before the percentage and remove the space after it in the common calendar popover. task-3908815 Forward-Port-Of: odoo/enterprise#62083
Original PR description
Steps to reproduce: 1. Install the planning module and open it. 2. Open events in calendar view. 3. Click on any event. 4. In the calendar popover, observe the spacing around the percentage (%). Issue: There is inconsistency in spacing around the percentage (%). Solution: Add a space before the percentage and remove the space after it in the common calendar popover. task-3908815 Forward-Port-Of: odoo/enterprise#62083