Daily updates from Odoo
Tuesday, October 25, 2022
23 changes · master
Enhancements to existing features
This update replaces an older template instruction with the current supported one across accounting and localization modules. It helps keep reports and dashboards working as expected while reducing unnecessary warning messages in system logs.
Original PR description
Due to the deprecation of t-esc to the unique use of t-out in the rendering template, this replace every usage of it and ensures everything continues to work as inteded. Removing deprecation warnings polluting terminal deprecation commit: https://github.com/odoo/odoo/commit/9ce5bc8881ae06b613ef61eb07453b224f62bae6 Signed-off-by: Julien Alardot (jual) <jual@odoo.com>
Resolved issues and error corrections
Demo and test records for several country-specific accounting modules were adjusted to match stricter invoice partner consistency checks. This helps keep sample data and automated tests aligned with the latest validation rules, reducing false failures and setup issues.
Original PR description
adapt demo/test files to be compliant with the new constraint checking inconsistencies between partners on the move and on its move.line (for invoices) see [PR#87523](https://github.com/odoo/odoo/pull/87523)
Badges now display with the correct rounded shape without requiring an extra styling class. This keeps status labels and visual indicators consistent across several Odoo apps, improving clarity and polish for users.
Original PR description
Mirror changes in community, https://github.com/odoo/odoo/pull/98547 . Solve an issue causing badges to have incorrect border-radius unless the `rounded-pill` class was added.
Code cleanup and technical improvements
The emoji picker setup was simplified in Knowledge and Social, with unused code removed. This is a minor cleanup that helps keep the messaging experience easier to maintain without changing how users work day to day.
Original PR description
This commit cleans up a bit of the emoji picker modeling, and removes a bit of dead code The linked PR for odoo-dev is https://github.com/odoo/odoo/pull/103411 Task-2985893
Miscellaneous changes
In order to better reflect actual Odoo models some test model fields have been updated. This has a small impact on query counters are some fields are not computed. Task-3012789 Forward-Port-Of: odoo/enterprise#33184
Original PR description
In order to better reflect actual Odoo models some test model fields have been updated. This has a small impact on query counters are some fields are not computed. Task-3012789 Forward-Port-Of: odoo/enterprise#33184
Steps to reproduce ================== - Uninstall the unsplash addon (it is auto installed) - Go to knowledge - Click on the article title -> `this._onNameClick is not a function` Cause of the issue ================== - KnowledgeCoverDialog imports UnsplashError - KnowledgeArticleFormRenderer imports KnowledgeCoverDialog - Since the unsplash dependency is missing, the default FormRenderer is used opw-3030694 Forward-Port-Of: odoo/enterprise#33166
Original PR description
Steps to reproduce ================== - Uninstall the unsplash addon (it is auto installed) - Go to knowledge - Click on the article title -> `this._onNameClick is not a function` Cause of the issue ================== - KnowledgeCoverDialog imports UnsplashError - KnowledgeArticleFormRenderer imports KnowledgeCoverDialog - Since the unsplash dependency is missing, the default FormRenderer is used opw-3030694 Forward-Port-Of: odoo/enterprise#33166
Before this commit, when the user stops the timer and resume the timer, the timer flicker, as if there were 2 timers running at the same time. The reason is because the `onWillUpdateProps` is called 2 times on the row (once since the value of timer_start has changed and another since timer_pause changed) because of that, since `onWillUpdateProps` is a async method, it seems the method starts 2 timers. This commit avoids that by calculating the server offset in `onWillStart` hook and then the
Original PR description
Before this commit, when the user stops the timer and resume the timer, the timer flicker, as if there were 2 timers running at the same time. The reason is because the `onWillUpdateProps` is called 2 times on the row (once since the value of timer_start has changed and another since timer_pause changed) because of that, since `onWillUpdateProps` is a async method, it seems the method starts 2 timers. This commit avoids that by calculating the server offset in `onWillStart` hook and then the `onWillUpdateProps` will no longer be a async hook since no rpc will be called anymore. closes odoo/odoo#103196 Forward-Port-Of: odoo/enterprise#32989
The wrong bus was used to trigger a file upload resulting in the documents upload request simply not working. opw-3035606 Forward-Port-Of: odoo/enterprise#33160
Original PR description
The wrong bus was used to trigger a file upload resulting in the documents upload request simply not working. opw-3035606 Forward-Port-Of: odoo/enterprise#33160
Steps to reproduce: - Install the module `l10n_mx_edi` - Switch to a Mexican company (that have PAC set) - Create a customer invoice and confirm it - Create a credit note (full refund) for the invoice - Check in the chatter the generated CFDI document filename Issue: The filename is not right : `INV--MX-Invoice-4.0.xml` (instead of `INV-RINV202200004-MX-Invoice-4.0.xml`). Cause: Using the payment reference in the filename while it is not set. Solution:
Original PR description
Steps to reproduce: - Install the module `l10n_mx_edi` - Switch to a Mexican company (that have PAC set) - Create a customer invoice and confirm it - Create a credit note (full refund) for the invoice - Check in the chatter the generated CFDI document filename Issue: The filename is not right : `INV--MX-Invoice-4.0.xml` (instead of `INV-RINV202200004-MX-Invoice-4.0.xml`). Cause: Using the payment reference in the filename while it is not set. Solution: Fallback on the move name if payment reference not set on move. opw-3007278 Forward-Port-Of: odoo/enterprise#33009 Forward-Port-Of: odoo/enterprise#32841
To avoid user navigation when we switch on dark mode, we added a call to the `blockUI` method when we switch the color scheme, we also remove duplicated code Forward-Port-Of: odoo/enterprise#32775
Original PR description
To avoid user navigation when we switch on dark mode, we added a call to the `blockUI` method when we switch the color scheme, we also remove duplicated code Forward-Port-Of: odoo/enterprise#32775
Fixes 2 small UX issues: - stock_barcode: Cleaned up grammar and wording to match the options in the dropdowns when chosing when source/destination location mandatory scan. Hopefully this makes it clearer to users as to how they fix their misconfiguration. - mrp_plm: fix Eco Stages form view layout Forward-Port-Of: odoo/enterprise#33149
Original PR description
Fixes 2 small UX issues: - stock_barcode: Cleaned up grammar and wording to match the options in the dropdowns when chosing when source/destination location mandatory scan. Hopefully this makes it clearer to users as to how they fix their misconfiguration. - mrp_plm: fix Eco Stages form view layout Forward-Port-Of: odoo/enterprise#33149
This PR removes unused files from timesheet_grid module. task-3016956 Forward-Port-Of: odoo/enterprise#32771
Original PR description
This PR removes unused files from timesheet_grid module. task-3016956 Forward-Port-Of: odoo/enterprise#32771
This PR fixes and adapts some color issues for the dark mode. Requires: - https://github.com/odoo/odoo/pull/102961 task-2710677 Forward-Port-Of: odoo/enterprise#32657
Original PR description
This PR fixes and adapts some color issues for the dark mode. Requires: - https://github.com/odoo/odoo/pull/102961 task-2710677 Forward-Port-Of: odoo/enterprise#32657
Batch of fixes for sale subscription 1. We still increment the next_invoice_date if no line is invoiceable. 2. The filter on subscription product is now consistent with other app and available on all Product list 3. It should not be possible to create "recurring price rules" for non recurring product. 4. Rename recurring price rules across the different views 5. Breadcrumbs name for sale.order.log 6. When creating a product from the SOL line in the subscription Application, t
Original PR description
Batch of fixes for sale subscription 1. We still increment the next_invoice_date if no line is invoiceable. 2. The filter on subscription product is now consistent with other app and available on all Product list 3. It should not be possible to create "recurring price rules" for non recurring product. 4. Rename recurring price rules across the different views 5. Breadcrumbs name for sale.order.log 6. When creating a product from the SOL line in the subscription Application, the product is now recurring by default. task-id : 2986247 Forward-Port-Of: odoo/enterprise#32880 Forward-Port-Of: odoo/enterprise#31444
Remove the call to t-on-click in the arch of form/kanban views as it crashes when the view is opened in studio. Instead use a dedicated <widget>. Forward-Port-Of: odoo/enterprise#33135
Original PR description
Remove the call to t-on-click in the arch of form/kanban views as it crashes when the view is opened in studio. Instead use a dedicated <widget>. Forward-Port-Of: odoo/enterprise#33135
Add Chart of Accounts, Taxes, Tax report, Balance Sheet and Profit & Loss. This module provides basic funtionalities for Serbian accounting. task-2697970 Linked PR: https://github.com/odoo/odoo/pull/80256 Doc: Attached files to task 2352412 https://www.apr.gov.rs/registers/financial-statements/financial-statements-forms/legal-entities-that-apply-ifrs-or-ifrs-for-smes.1707.html https://www.wtsserbia.com/wp-content/uploads/2019/01/NEW-Chart-of-accounts-Kontni-okvir-FINAL-Srpski-En
Original PR description
Add Chart of Accounts, Taxes, Tax report, Balance Sheet and Profit & Loss. This module provides basic funtionalities for Serbian accounting. task-2697970 Linked PR: https://github.com/odoo/odoo/pull/80256 Doc: Attached files to task 2352412 https://www.apr.gov.rs/registers/financial-statements/financial-statements-forms/legal-entities-that-apply-ifrs-or-ifrs-for-smes.1707.html https://www.wtsserbia.com/wp-content/uploads/2019/01/NEW-Chart-of-accounts-Kontni-okvir-FINAL-Srpski-English-Deutsch.xlsx https://www.paragraf.rs/obrasci/PPPDV.pdf https://www.paragraf.rs/dokumenti/korisnicko-uputstvo-za-obrazac-popdv.html -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/enterprise#32322 Forward-Port-Of: odoo/enterprise#24630
During Reportalypse, the calculations of Modelo 347 have been refactored, which introduced a bug causing the acquisitions over 3005.56 EUR not to be displayed anymore in the report. This PR fixes this issue. Forward-Port-Of: odoo/enterprise#32900
Original PR description
During Reportalypse, the calculations of Modelo 347 have been refactored, which introduced a bug causing the acquisitions over 3005.56 EUR not to be displayed anymore in the report. This PR fixes this issue. Forward-Port-Of: odoo/enterprise#32900
Force move type as entry when a user reevaluate positively an asset. Forward-Port-Of: odoo/enterprise#32491
Original PR description
Force move type as entry when a user reevaluate positively an asset. Forward-Port-Of: odoo/enterprise#32491
Backport 3d5c61764d924896fc304d590bc8325493667ef0 1. Make the checkbox closer to product name and align them 2. Make the product column sticky and always show checkbox Forward-Port-Of: odoo/enterprise#33095
Original PR description
Backport 3d5c61764d924896fc304d590bc8325493667ef0 1. Make the checkbox closer to product name and align them 2. Make the product column sticky and always show checkbox Forward-Port-Of: odoo/enterprise#33095
Steps to reproduce: - go to Documents app; - select a document and create an activity and make it late; - edit another document and create an activity for today; - edit yet another document and create a future activity; - click on the activity clock in the main menu bar (there are one late activity, one today and one in the future); - click on "late". Issue: All three documents with activities are shown. Cause: There is no filter provided for this purpose. Solution: Add a filte
Original PR description
Steps to reproduce: - go to Documents app; - select a document and create an activity and make it late; - edit another document and create an activity for today; - edit yet another document and create a future activity; - click on the activity clock in the main menu bar (there are one late activity, one today and one in the future); - click on "late". Issue: All three documents with activities are shown. Cause: There is no filter provided for this purpose. Solution: Add a filter on documents according to the activity deadline. opw-3002778 Forward-Port-Of: odoo/enterprise#33107 Forward-Port-Of: odoo/enterprise#33035
Edit a form view in studio, display the xml editor, go back to the normal webClient Before this commit, the Model of the formView was potentially altered programmatically when switching the edition mode of studio. After this commit, there is no risk, as nothing is ever written onto the view object from the view registry. Forward-Port-Of: odoo/enterprise#33033
Original PR description
Edit a form view in studio, display the xml editor, go back to the normal webClient Before this commit, the Model of the formView was potentially altered programmatically when switching the edition mode of studio. After this commit, there is no risk, as nothing is ever written onto the view object from the view registry. Forward-Port-Of: odoo/enterprise#33033
Before this commit: Let's consider 2 slots: - slot 1 having allocated_hours = 40, starting 01 and ending 04. - slot 2 having allocated_hours = 30, starting 01 and ending 03. Let's suppose we're in view_type = 'week' In that case, we have 4 pills: Let's focus on pill 1. - pill on day 01 with total_allocated_hours = 70 = 30 + 40 instead of 20 20 = slot1_allocated_hours / number_of_days + slot2_allocated_hours / number of days 20 = 40 / 4 + 30 / 3 20 = 10 + 10 Moreover, pill progress b
Original PR description
Before this commit: Let's consider 2 slots: - slot 1 having allocated_hours = 40, starting 01 and ending 04. - slot 2 having allocated_hours = 30, starting 01 and ending 03. Let's suppose we're in view_type = 'week' In that case, we have 4 pills: Let's focus on pill 1. - pill on day 01 with total_allocated_hours = 70 = 30 + 40 instead of 20 20 = slot1_allocated_hours / number_of_days + slot2_allocated_hours / number of days 20 = 40 / 4 + 30 / 3 20 = 10 + 10 Moreover, pill progress bar is counted according to slots number not total_allocated_hours per pill and pills are planned during non working days. In this commit: The calculation is fixed taking into consideration non_working_days (public holidays, weekends, employee time off) Pill progress bar is calculated as pill_total_allocated_hours / max_total_allocated_hours Task-2971118 Forward-Port-Of: odoo/enterprise#31032
Before this Commit, Planning->shift templates->add planned hours getting traceback when entering time greater or equal to 24 hours because SQL constraints were not raising an error After this Commit, a Validation error will be raised when entering hours greater than 24 task-3010685 Forward-Port-Of: odoo/enterprise#32671
Original PR description
Before this Commit, Planning->shift templates->add planned hours getting traceback when entering time greater or equal to 24 hours because SQL constraints were not raising an error After this Commit, a Validation error will be raised when entering hours greater than 24 task-3010685 Forward-Port-Of: odoo/enterprise#32671