Thursday, November 2, 2023
38 changes · 17.0
Enhancements to existing features
The employee profile screens now use a better placeholder image when no employee photo is available. This makes HR records look cleaner and more consistent, improving the experience for users browsing employee information.
Original PR description
task-3568588 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Resolved issues and error corrections
The Point of Sale category selector now displays more consistently across browsers such as Firefox and Safari. Category images are constrained and hidden when space is limited, reducing layout issues for cashiers using smaller or resized screens.
Original PR description
This commit fixes the issues related to the category selector. The issues are very obvious when switching browser (e.g. Firefox or Safari). The width of the container containing the category image…
This commit fixes the issues related to the category selector. The issues are very obvious when switching browser (e.g. Firefox or Safari). The width of the container containing the category image thinks that its width should be the original width of the contained image. This is a quick fix which sets a max-width of 100px on the container (which is approximately 75% of the image width matching the 75% height set on the image). Additionally, we hide the image when the category panel becomes to thin. **BEFORE**    **AFTER**   
Code cleanup and technical improvements
This update replaces an outdated search interface component in the Twitter integration with a modern, more maintainable version. The change removes legacy code dependencies and improves the overall system architecture without affecting how users interact with the feature.
Documentation and clarification updates
This pull request records Harsh Bhatt's signed Contributor License Agreement. It supports Odoo's contribution process by confirming the legal permission needed to accept future contributions.
Original PR description
[CLA] signature for harshbhatt --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Miscellaneous changes
When creating a sub company with l10n_ar, we get a ValidationError due to the check on existing accounting entries on parent company. Steps: - Create a new company with l10n_ar, and create some moves - Create a branch for the company and save -> ValidationError: "Could not change the AFIP Responsibility of this company because there are already accounting entries." In `account.res_company._existing_accounting`, we check if there are existing move lines in both parent and child compani
Original PR description
When creating a sub company with l10n_ar, we
get a ValidationError due to the check on
existing accounting entries on parent company.
Steps:
- Create a new company with l10n_ar, and
create some moves
- Create a branch for the company and save
-> ValidationError: "Could not change the AFIP
Responsibility of this company because there
are already accounting entries."
In `account.res_company._existing_accounting`,
we check if there are existing move lines in
both parent and child companies, while we would
like to check only new company when it is calling
from `l10n_ar.res_company._check_accounting_info`.
With this commit, we change the return value of
`_existing_accounting` from bool to a mapping
{'company_id': bool} in order to be able to check
either existing entries from a specific company
or from all companies like we did before, by
checking whether the returned value is truthy
or not.
opw-3572926
Forward-Port-Of: odoo/odoo#140637This update corrects how live call sessions are counted in Discuss. It prevents duplicate notification sounds from playing in situations such as starting a meeting, making the calling experience smoother for users.
Original PR description
**Current behavior before PR:** The logic used to count the number of RTC Sessions was incorrect. Which led to multiple sounds being played sometimes. Etc, on start a meeting **Desired behavior after PR is merged:** Corrected the RTC Sessions counting logic. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fix prevents web push notifications from being sent for muted discussion channels. It helps ensure user notification preferences are respected and reduces unwanted interruptions.
Original PR description
Do not send the web_push notificaiton if the channel is muted. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update removes documentation for a field configuration option that is no longer supported. It helps avoid confusion for developers and implementation teams while keeping internal compatibility needed for migrations.
Original PR description
Since https://github.com/odoo/odoo/pull/104741, `Field.states` is no longer supported, remove this attribute and the documentation associated.
The web install prompt now appears in the correct position on iOS devices instead of being partially off-screen. This makes the app installation experience clearer and easier for mobile users.
Original PR description
Before this commit, the install prompt was half shifted out of screen. After this commit, the install prompt is not shifted anymore. Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fix prevents payroll-related upgrade tests from failing when some leave records are missing start or end request dates. It safely skips incomplete records during date calculations, improving reliability without changing normal user workflows.
Original PR description
We need to filter out records without `request_date_from` and `request_date_to` to avoid the error:
```
File "/tmp/tmpiaelju95/odoo/17.0/addons/hr_work_entry_holidays/models/hr_leave.py", line 180, in write
stop = datetime.combine(max(stop_dates) + relativedelta(days=1), time.max)
TypeError: '>' not supported between instances of 'datetime.date' and 'bool'
```
Issue observed in test upgrades of `l10n_hk_hr_payroll`
```tests
upgrade 17.0: l10n_hk_hr_payroll
```This fix adjusts employee presence status icons so they no longer appear oversized in views such as kanban cards. It reduces visual clutter and makes employee cards easier to read without changing the underlying presence information.
Original PR description
This PR adjusts the size of the icons used for the employee presence status. Prior to this PR, these icons were using a rule to define if they should be diplayed in large or not, by checking the html tag of the element they are in. These icons were also styled with custom CSS to adjust their size, while classes like `fa-lg` could eventually provide a workaround. This approach was causing issues especially in kanban cards, were these icons would appear massive and cause visual cluttering. To improve the render of these inside cards, we simply remove the custom styling applied to these icons. | 17.0 | 17.0-fix-presence-status-icon-size-chgo | | ------------- | ------------- | | <img alt="image" src="https://github.com/odoo/odoo/assets/128030743/53a380d0-10af-495a-9008-1e80c0bd0119"> | <img alt="image" src="https://github.com/odoo/odoo/assets/128030743/6402d4d9-4552-4c51-b2fc-8af3b01d456c"> task-3573702
A link in the employee skills area now gives clear visual feedback when users hover over it. This small accessibility fix helps users recognize clickable actions more easily and reduces confusion.
Original PR description
This commit fixes an accessibility issue about a link which does not provide any visual feedback to the user who would hover it. Prior to this commit, this link did not provide any visual feedback, due to the lack of `cursor-pointer` BS class or `btn-link` styling. The easiest way to fix this is to add a `cursor-pointer` class to the link. We could have turned the link into a button with `btn btn-link` classes but this would requires more layout and design adjustments. task-3573737
The website editor now automatically disables live preview for options that require a page reload. This prevents an unexpected error message when users adjust settings such as mobile alignment in the website header.
Original PR description
This commit resolves the issue that arises when a widget contains a reload attribute but lacks a no-preview attribute. The bug leads to an "Uncaught Promise" error. With this update, when a reload attribute is detected, the no-preview attribute is now automatically added, preventing the error from occurring. The problem arisen with [this other commit]. [this other commit]: https://github.com/odoo/odoo/commit/fcb16a3b1bd373726ffb54f0fbe41fb6d1784769 task-3572334
The mail chatter now avoids refreshing its data on every form change, especially when the record has not been saved. This reduces unnecessary background requests and should make form navigation and editing feel smoother without changing user workflows.
Original PR description
This RPC /mail/thread/data is called on every form view change, even when not saved. It comes from the chatter onWillUpdateProps and calling `load` then `fetchData` We don't want to reload chatter when every time props updates. Do it when the record `onWillLoadRoot` Task: 3569123 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fix prevents an error when users generate serial numbers from a repair order. By ensuring the needed destination location is available, the repair workflow can continue without an unexpected interruption.
Original PR description
Main changes :
Force context values to avoid traceback in action_generate_lot_line_vals
Before :
When calling action_generate_lot_line_vals from a repair order, a traceback occurs due to the missing 'default_location_dest_id' in the context.
After :
We enforce 'default_location_dest_id' in the repair order form to ensure it is available when we call action_generate_lot_line_vals
---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-prThis update fixes an issue where completed activity dates could appear as “Invalid date” in the activity popover. It also strengthens automated checks so activity views update correctly when activities are completed, helping prevent regressions in day-to-day task tracking.
Original PR description
[IMP] mail: add/modify activity client tests We add a test that checks the rendering of the activity view and the activity popover with activities done. We also add a test that marks as done an activity and verify that the activity view is updated accordingly. And we do a correction in the test "activity menu widget: activity menu with 2 models" (assert.ok(selectContaining... was always true as an array is always returned and [] is true in javascript). [FIX] mail: fix invalid date done in the activity list popover Date done field was in camel case instead of snake case leading to undefined value and "Invalid date" in the interface. Task-3558929
Favorite star icons now line up more consistently across several Odoo kanban views, including accounting, recruitment, projects, lunch, and manufacturing. This improves visual polish and keeps the favorite marker clearly visible without custom layout workarounds.
Original PR description
*: account, hr_recruitment, project, lunch, mrp PR https://github.com/odoo/odoo/pull/130702 fixes a few issues encountered with the favorite icon that can be found in some kanban and list views. However the alignment is still off. In previous backend designs, custom CSS had been added to allow the cards in the Project's kanban view to appear/disappear on hovering the card, thus needing an absolute positioning on the icon. By removing the absolute positioning and allowing `.o_favorite` to align itself naturally within the content, we allow ourselves to remove a whole lot of custom CSS and give a better visual result to the star's alignment. The margin on the kanban heading in the Manufacturing Orders has been removed to realign the top elements. task-3462098 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Point of Sale now stops automatically applying a default pricelist when flexible pricelists are turned off. This prevents unnecessary pricing settings from being loaded in POS sessions and keeps configuration behavior aligned with the merchant’s selected options.
Original PR description
Pricelist is no longer required. Because of that, pos no longer need to implicitly load a default pricelist when "Flexible Pricelists" (use_pricelist) flag is active. Therefore, when deactivating the option, we clear the value of pos.config.pricelist_id. We also make sure that during loading of data when opening a session, default_pricelist is not set if use_pricelist is false. Also note that we are not clearing available_pricelist_ids because of some limitation in the synchronization between res.config.settings and pos.config. It's okay to keep the links because it won't be loaded when use_pricelist is false. Also, it's nice to see it filled when reactivating the flag.
The Point of Sale product selection screen now shows the search button with the correct styling on mobile and responsive views. This makes the interface clearer and easier to use for staff working from smaller devices.
Original PR description
**not proper search button style** Impacted versions: - 17.0 Steps to reproduce: 1. Open pos product selection page in mobile or in responsive device Current behavior: - not proper button style (attached screenshot) Expected behavior: - make proper button style Video/Screenshot link (optional):  --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update fixes a display issue where forum posts shared from helpdesk tickets were missing a space between the post name and the forum post indicator. When users share a helpdesk ticket to a forum and view the post, the text now displays correctly with proper spacing in the ticket's activity log.
Original PR description
Steps: - In helpdesk ticket click on share on forum - click on create and view post - it will redirect to website - click back and see the chatter of the helpdesk ticket Issue: - missing space between name of the post and forum post created Fix: - we have added a space from the place where the message is posted task-3463622 Forward-Port-Of: odoo/enterprise#46224
A test in the Web Studio module was failing after October due to a hardcoded month value in the test code. This fix temporarily disables the problematic test to prevent system failures, with plans to properly refactor it later.
Original PR description
The web_studio clickbot qunit test fails after October because of a hard coded month. It needs to be refactored but let's skip it in emergency. Forward-Port-Of: odoo/enterprise#49983
A technical issue was preventing account reports from properly saving configuration options due to incompatible data format. The team resolved this by removing an unused option that was causing the problem, ensuring reports function smoothly without affecting any user-facing features.
Original PR description
A bug was caused by trying to converting the options that contained a set into json. We fix it by removing the option that used the set as it doesn't seem to be used anymore.
This fix reorganizes the timesheet menu structure to give timesheet managers access to the tips menu, which was previously unavailable to them. This improves manager capabilities by allowing them to view helpful tips and guidance within the timesheet application.
Original PR description
This PR changes the timesheets menuitems order and groups so that the tips menu is available to timesheets managers, which was not the case before. task-3579920
1. `searchPartnerSuggestions` uses`authorizedGroupFullName` to see if the channel is public or not 2. `filteredThreads` and `getThreads` uses `hasSelfAsMember` and `is_pinned` along with the channel type 3. search should use `displayName` otherwise the search on the group with a default empty name will fail 4. fix tests. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#140201 Forward-Port-Of: odoo/odoo#140065
Original PR description
1. `searchPartnerSuggestions` uses`authorizedGroupFullName` to see if the channel is public or not 2. `filteredThreads` and `getThreads` uses `hasSelfAsMember` and `is_pinned` along with the channel type 3. search should use `displayName` otherwise the search on the group with a default empty name will fail 4. fix tests. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#140201 Forward-Port-Of: odoo/odoo#140065
Problem --------- When creating and editing a bank account, a creation model pops-up to edit the bank account information. The previously entered bank account must be entered again which isn't user-friendly. Examples of models where I noticed the issue: - account.journal - account.payment - bacs.ddi - sdd.mandate - hr.employee Objective --------- The data entered on the bank account bank account should pre-fill acc_number on partner bank pop-up. Solution --------- When crea
Original PR description
Problem --------- When creating and editing a bank account, a creation model pops-up to edit the bank account information. The previously entered bank account must be entered again which isn't user-friendly. Examples of models where I noticed the issue: - account.journal - account.payment - bacs.ddi - sdd.mandate - hr.employee Objective --------- The data entered on the bank account bank account should pre-fill acc_number on partner bank pop-up. Solution --------- When create & edit, `name` could be used to pass (in the context) the value input by the user. However, we want to set the default value of `acc_number` variable instead. By overriding the default_get method, we can get modify the context to do just that. task-3557753 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#140606 Forward-Port-Of: odoo/odoo#139211
This commit sets `s_text_cover` default color preset to `o_cc4` to make it look more like the header of "Anelusia" theme that was the initial reference for the design of this snippet It also fixes a typo in `o_ccx` class introduced in commit [1] [1]45c4a2f66661e560359d30b67321475c2c8a9844 task-3568868 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#139624
Original PR description
This commit sets `s_text_cover` default color preset to `o_cc4` to make it look more like the header of "Anelusia" theme that was the initial reference for the design of this snippet It also fixes a typo in `o_ccx` class introduced in commit [1] [1]45c4a2f66661e560359d30b67321475c2c8a9844 task-3568868 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#139624
Scenario: - go to a model in technical - create a new field and set "Related Field" to id => error "Unknown field name 'id' in related field 'id'" because we get the field in self.model which is not present in the form view. Fallback to self.model_id.model as was the case before 16.0 commit: 76f699ca0be5ccb2167f856b6358e48da03e24eb opw-3138440 closes #112495 Forward-Port-Of: odoo/odoo#140467 Forward-Port-Of: odoo/odoo#139927
Original PR description
Scenario: - go to a model in technical - create a new field and set "Related Field" to id => error "Unknown field name 'id' in related field 'id'" because we get the field in self.model which is not present in the form view. Fallback to self.model_id.model as was the case before 16.0 commit: 76f699ca0be5ccb2167f856b6358e48da03e24eb opw-3138440 closes #112495 Forward-Port-Of: odoo/odoo#140467 Forward-Port-Of: odoo/odoo#139927
To reproduce ======== - having eCommerce installed - let's take a product with price 1 000$ - for simplicity let's say 1$ = 0.5€ - make two orders for the product in € and $ - first order will be 1 000$ - second one will be 500€ - send the digest email - the email shows total eCom sales = 1 500$ Problem ======= - the total amount is a sum between $ and € which gives a wrong value Solution ======== convert all orders amount to the currency of the company opw-3518064 Forward-P
Original PR description
To reproduce ======== - having eCommerce installed - let's take a product with price 1 000$ - for simplicity let's say 1$ = 0.5€ - make two orders for the product in € and $ - first order will be 1 000$ - second one will be 500€ - send the digest email - the email shows total eCom sales = 1 500$ Problem ======= - the total amount is a sum between $ and € which gives a wrong value Solution ======== convert all orders amount to the currency of the company opw-3518064 Forward-Port-Of: odoo/odoo#140026 Forward-Port-Of: odoo/odoo#139599
When decreasing the qty of a subcontracted POL, it can create an unexpected receipt To reproduce the issue: 1. Create a BoM for a subcontracted product P 2. Create and confirm a PO with 5 x P 3. Process the receipt 4. Return one 5. Update the POL qty to 4 Error: a new receipt is created for 3 x P. When updating the POL, nothing should happen with the receipts Updating the POL qty leads to the create/update of the related picking: https://github.com/odoo/odoo/blob/1495b54aa452498
Original PR description
When decreasing the qty of a subcontracted POL, it can create an unexpected receipt To reproduce the issue: 1. Create a BoM for a subcontracted product P 2. Create and confirm a PO with 5 x P 3.…
When decreasing the qty of a subcontracted POL, it can create an unexpected receipt To reproduce the issue: 1. Create a BoM for a subcontracted product P 2. Create and confirm a PO with 5 x P 3. Process the receipt 4. Return one 5. Update the POL qty to 4 Error: a new receipt is created for 3 x P. When updating the POL, nothing should happen with the receipts Updating the POL qty leads to the create/update of the related picking: https://github.com/odoo/odoo/blob/1495b54aa452498c79f4178c2e38426b1b423e66/addons/purchase_stock/models/purchase.py#L426 And this will lead to `_prepare_stock_moves`: https://github.com/odoo/odoo/blob/1495b54aa452498c79f4178c2e38426b1b423e66/addons/purchase_stock/models/purchase.py#L447-L450 Where we will define the values of the new SM (for the new qty). However, there are two similar issues: to get the current qty, we sum the quantities of the incoming/outgoing stock moves. But, the condition is incorrect and we therefore consider the subcontracting return as an incoming qty. So, this current qty is incorrect. Then, we get the dest moves to compute some quantities to push/attach. Here is the second issue, the filter condition to exclude the return SM is incorrect: again, we don't exclude the subcontracting return OPW-3515275 Forward-Port-Of: odoo/odoo#139720 Forward-Port-Of: odoo/odoo#138836
This replaces the former domain operator '?=' which is not allowed, This domain property, new to Odoo 16 does not permit the edition of the field with Studio, this change will enhance the configuration and will prevent future issues. owp-3484144 Forward-Port-Of: odoo/odoo#135243
Original PR description
This replaces the former domain operator '?=' which is not allowed, This domain property, new to Odoo 16 does not permit the edition of the field with Studio, this change will enhance the configuration and will prevent future issues. owp-3484144 Forward-Port-Of: odoo/odoo#135243
Since 40f0482b680a7872d338fa8fd10eec4663637b46, pricelist is no longer required. Because of that, pos no longer needs to implicitly load a default pricelist when "Flexible Pricelists" (use_pricelist) flag is active. Therefore, when deactivating the option, we clear the value of pos.config.pricelist_id. We also make sure that during loading of data when opening a session, default_pricelist is not set if use_pricelist is false. Also note that we are not clearing available_pricelist_ids becau
Original PR description
Since 40f0482b680a7872d338fa8fd10eec4663637b46, pricelist is no longer required. Because of that, pos no longer needs to implicitly load a default pricelist when "Flexible Pricelists" (use_pricelist) flag is active. Therefore, when deactivating the option, we clear the value of pos.config.pricelist_id. We also make sure that during loading of data when opening a session, default_pricelist is not set if use_pricelist is false. Also note that we are not clearing available_pricelist_ids because of some limitation in the synchronization between res.config.settings and pos.config. It should okay to keep the links because they won't be loaded when use_pricelist is false. Also, it's nice to see the field filled when reactivating the flag. Forward-Port-Of: odoo/odoo#140563
**Steps:** - Open Project - Create New Project - Select the blank new project and click on see examples below the stage. - This also appears in the existing project where you want to add more stages. - A Kanban Examples popup view will open. **Issue:** - A scrollbar appears on the bottom left due to the long name of the example. **Cause:** - Due to the overflow property, when the name is long, it will automatically create a scrollbar, making it look weird. **Fix:** - Add overfl
Original PR description
**Steps:** - Open Project - Create New Project - Select the blank new project and click on see examples below the stage. - This also appears in the existing project where you want to add more stages. - A Kanban Examples popup view will open. **Issue:** - A scrollbar appears on the bottom left due to the long name of the example. **Cause:** - Due to the overflow property, when the name is long, it will automatically create a scrollbar, making it look weird. **Fix:** - Add overflow-x visible in notebook It will counterbalance the overflow-x: auto; rule used in the general (aka. horizontal) use case, and force the overflowing element to take the space it needs, adjusting the headers column's width accordingly. **Task:** 3422009 Forward-Port-Of: odoo/odoo#128438
When we add a smart button on a contact tag related to contacts, the button adds a default search filter that hides the related records Steps to reproduce: 1. Install Contacts and Studio 2. Go to Contacts > Configuration > Contact Tags 3. Open tag "Vendor / Desk Manufacturers" 4. Toggle Studio 5. Add a button (at the top right of the form) related to field "Tags (Contact)" 6. Close Studio 7. Click on the button 8. A list view of the related contacts opens but there is a filter that hi
Original PR description
When we add a smart button on a contact tag related to contacts, the button adds a default search filter that hides the related records Steps to reproduce: 1. Install Contacts and Studio 2. Go to Contacts > Configuration > Contact Tags 3. Open tag "Vendor / Desk Manufacturers" 4. Toggle Studio 5. Add a button (at the top right of the form) related to field "Tags (Contact)" 6. Close Studio 7. Click on the button 8. A list view of the related contacts opens but there is a filter that hides the records Solution: Remove the `filter_domain` attribute on the field category_id and replace it by the `operator` attribute in order to use the raw value in the domain Problem: In `_getFieldDomain`, we replace the `self` in the domain by the stringified id which essentially checks for a category that has a name containing the id opw-3471959 Forward-Port-Of: odoo/odoo#140333
[FIX] event_sale : Incorrect event sales value upon cancelling Steps to reproduce: 1- Install Sales and Events modules 2- Create a new Event and event registration 3- Create a sale order for this event 4- Check the sales smart button in the event's form 5- Cancel the sale order and check the smart button Current behavior before PR: When you create a sale order for an event and then cancel it the value of this sale order will not be deducted from the sum of the sale values at the sale
Original PR description
[FIX] event_sale : Incorrect event sales value upon cancelling Steps to reproduce: 1- Install Sales and Events modules 2- Create a new Event and event registration 3- Create a sale order for this event 4- Check the sales smart button in the event's form 5- Cancel the sale order and check the smart button Current behavior before PR: When you create a sale order for an event and then cancel it the value of this sale order will not be deducted from the sum of the sale values at the sale smart button in the event form. Desired behavior after PR is merged: When you cancel a sale order related to an event the sale smart button value will be updated opw-3543943 Forward-Port-Of: odoo/odoo#140022 Forward-Port-Of: odoo/odoo#139614
In order to improve the user Experience and not uselessly block access to the document, we prevent collaboration error to open the traceback dialog. task-3568680 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#139571
Original PR description
In order to improve the user Experience and not uselessly block access to the document, we prevent collaboration error to open the traceback dialog. task-3568680 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#139571
In some cases the changes done in the editor were lost when using other element of the the UI. For example : changing the tab containing the editor component to another one. To avoid loosing the changes made by the user in those cases, we force an urgent commit change in the `onWillUnmount` hook. task-3530998 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#139548 Forward-Port-Of: odoo/odoo#137716
Original PR description
In some cases the changes done in the editor were lost when using other element of the the UI. For example : changing the tab containing the editor component to another one. To avoid loosing the changes made by the user in those cases, we force an urgent commit change in the `onWillUnmount` hook. task-3530998 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#139548 Forward-Port-Of: odoo/odoo#137716
The clickbot test fails after October because of a hard coded month. It needs to be refactored but let's skip it in emergency. Forward-Port-Of: odoo/odoo#140631
Original PR description
The clickbot test fails after October because of a hard coded month. It needs to be refactored but let's skip it in emergency. Forward-Port-Of: odoo/odoo#140631
Previously, this page was relying on the DB UUID to retrieve the IAP accounts of the user. In the case where account tokens are shared across multiple databases or are re-created, this becomes an issue as inconsistencies will appear. It will either show information about accounts that no longer exist in the database, or it will miss the information about accounts that were manually imported from another database. To solve this issue, the route to the page will now take the active account tok
Original PR description
Previously, this page was relying on the DB UUID to retrieve the IAP accounts of the user. In the case where account tokens are shared across multiple databases or are re-created, this becomes an issue as inconsistencies will appear. It will either show information about accounts that no longer exist in the database, or it will miss the information about accounts that were manually imported from another database. To solve this issue, the route to the page will now take the active account tokens as parameter and display the information for those accounts only. Forward-Port-Of: odoo/odoo#140168 Forward-Port-Of: odoo/odoo#139928