Daily updates from Odoo
Monday, July 4, 2022
7 changes · master
Enhancements to existing features
This update simplifies how the mail form view manages the message panel and attachment viewer. It reduces duplicated logic and fixes an issue where the chatter could be incorrectly positioned inside a form sheet, improving reliability for users working with records and messages.
Original PR description
Part of task-2871070 https://github.com/odoo/odoo/pull/95218
Resolved issues and error corrections
The payroll accounting module now prevents salary-related accounting journals from being deleted when they are still needed. This helps avoid payroll processing errors and preserves important financial records used for salary payments.
This fix prevents the app from crashing when the home menu disappears immediately after a user leaves the search box. It improves reliability in a specific navigation scenario without changing user-facing features.
Original PR description
In some cases, it could happen that the home menu would be removed from the dom right after a blur happens on the search input element. The previous code assumed that the inputRef was still valid, but it is not necessarily true.
Code cleanup and technical improvements
This update reorganizes spreadsheet-related code so it can be separated from the Documents app in a future release. For users, there should be little immediate visible change, but it helps make spreadsheet features more flexible and easier to maintain going forward.
Miscellaneous changes
How to reproduce the bug ? - install account_accountant - create a second company - in the accounting module, in Settings>Follow-up levels, create for each company, 2 follow-up levels. Each level must have the "Save an Email" and "Auto Execute" - for each company, create one invoice with a 1 month old invoice date - post the invoices - in debug mode, in the Settings app, go to Technical > Scheduled Actions and select the "Account Report Followup; Execute followup" action. click on th
Original PR description
How to reproduce the bug ? - install account_accountant - create a second company - in the accounting module, in Settings>Follow-up levels, create for each company, 2 follow-up levels. Each level must have the "Save an Email" and "Auto Execute" - for each company, create one invoice with a 1 month old invoice date - post the invoices - in debug mode, in the Settings app, go to Technical > Scheduled Actions and select the "Account Report Followup; Execute followup" action. click on the "Run manually button". - Go back in the accounting module and select Customers > Follow-up Reports. What is the bug ? When you create a new company, only the admin has access to it. Nevertheless, the cron task processing the follow-up reports is executed by Odoobot who doesn't have access to the new company except if the user has given access to it. Signed-off-by: Adrien Minet <admi@odoo.com> Forward-Port-Of: odoo/enterprise#28961
The aim of this commit is to allow the make commercial_partner with a parent_id to get a form 281.50. Context: A company partner is supposed to be completly distinct from its parent and thus should have its own form 281.50. Before this commit: If a partner has a company and thus be a commercial_partner and has a parent, it wouldn't get a 281.50 form created for it After this commit: The partner being a company gets a form created for it even if he has a parent. task: 2820482 E
Original PR description
The aim of this commit is to allow the make commercial_partner with a parent_id to get a form 281.50. Context: A company partner is supposed to be completly distinct from its parent and thus should have its own form 281.50. Before this commit: If a partner has a company and thus be a commercial_partner and has a parent, it wouldn't get a 281.50 form created for it After this commit: The partner being a company gets a form created for it even if he has a parent. task: 2820482 Enterprise-PR: Forward-Port-Of: odoo/enterprise#28993 Forward-Port-Of: odoo/enterprise#28394
Use request.redirect instead of werkzeug.utils.redirect It allows to always have a OdooResponse Object and don't allow redirect to external except when you allow it explicitly with local=False. - social_facebook, sale_amazon_spapi: redirect to non local url, but controlled by code so not an openredirect - social_instagram: redirect to /web... so local only. Forward-Port-Of: odoo/enterprise#28960 Forward-Port-Of: odoo/enterprise#28544
Original PR description
Use request.redirect instead of werkzeug.utils.redirect It allows to always have a OdooResponse Object and don't allow redirect to external except when you allow it explicitly with local=False. - social_facebook, sale_amazon_spapi: redirect to non local url, but controlled by code so not an openredirect - social_instagram: redirect to /web... so local only. Forward-Port-Of: odoo/enterprise#28960 Forward-Port-Of: odoo/enterprise#28544