Daily updates from Odoo
Thursday, May 2, 2024
16 changes · master
Enhancements to existing features
Facebook social posts and comments now display users' different reaction types, not just likes, making engagement easier to understand at a glance. Users can also like or unlike Facebook posts directly from the comments window, improving day-to-day interaction workflows.
Original PR description
Purpose ======= Currently, we only show the likes of the users. But they can also react with something else than a like. This commit shows the emojis of the most used reactions. Other commits contain: Remove duplicated code about comment. Allow users to like posts in comments modal See underlying commits for details. Task-3595484
Documents attached through bridge modules are now moved to the trash instead of being permanently deleted when the related business record is removed. This preserves traceability and helps users recover or audit documents after associated records are deleted.
Original PR description
Purpose: Currently when a record with a document attached is deleted, the document attached is deleted as well which makes the document untraceable. Specification: Implemented a new functionality to handle document deletion in modules bridged with the documents. Instead of directly unlinking the document from the bridge module, a new function `send_to_trash()` has been created. This function changes the document's `res_model` to 'documents.document' and archives it, ensuring that the document is sent to the trash even if the associated record in the bridge module is deleted. This approach enhances document management and ensures data integrity across modules and helps in documents traceability. Task-3777950
Features or functions removed from Odoo
The Documents spreadsheet app no longer includes predefined spreadsheet templates that were unused and hard to maintain. Users creating a new spreadsheet will now go directly to a blank spreadsheet when no templates are available, reducing unnecessary choices and simplifying the workflow.
Original PR description
Task: 3761476
An unused action for opening subscriptions was removed from the Sales Subscription area. This is a small cleanup that reduces maintenance overhead without changing expected user workflows.
Original PR description
In this commit, the "action_open_subscriptions" function is no longer utilized, hence it has been removed. task-3860359
Miscellaneous changes
- Adds missing section D and E to the tax report. - Change line 43 to editable instead of aggregation. Forward-Port-Of: odoo/enterprise#61557 Forward-Port-Of: odoo/enterprise#57367
Original PR description
- Adds missing section D and E to the tax report. - Change line 43 to editable instead of aggregation. Forward-Port-Of: odoo/enterprise#61557 Forward-Port-Of: odoo/enterprise#57367
… variables To be able to render a human-readable qweb, we need to evaluate some arbitrary python expressions. Thos can produce bad sql queries because at this point, we are not, by construction in the conditions that produce correct queries (missing records etc....) Before this commit, when an query error occured at that step, the whole transaction was corrupted, and crashed the whole thing. After this commit, we do our partial evaluation things in a separate cursor, to avoid polluting
Original PR description
… variables To be able to render a human-readable qweb, we need to evaluate some arbitrary python expressions. Thos can produce bad sql queries because at this point, we are not, by construction in the conditions that produce correct queries (missing records etc....) Before this commit, when an query error occured at that step, the whole transaction was corrupted, and crashed the whole thing. After this commit, we do our partial evaluation things in a separate cursor, to avoid polluting the main one. opw-3815284 Forward-Port-Of: odoo/enterprise#60754
This commit moves the call for the Banxico currency update to the IAP server, where we can create a daily cache of currency rates. Part of: task-3749574 Forward-Port-Of: odoo/enterprise#61726 Forward-Port-Of: odoo/enterprise#58685
Original PR description
This commit moves the call for the Banxico currency update to the IAP server, where we can create a daily cache of currency rates. Part of: task-3749574 Forward-Port-Of: odoo/enterprise#61726 Forward-Port-Of: odoo/enterprise#58685
`Net profit/Loss for the Year` report.line has now an aggregation expression[1] which cannot have a groupby. But as the groupby field was removed instead of set to `eval=False`. The groupby is still there and blocking upgrades to 16.0 and 17.0 [1] https://github.com/odoo/enterprise/pull/52157 ``` File "/home/odoo/src/odoo/17.0/odoo/tools/convert.py", line 567, in _tag_root raise ParseError(msg) from None # Restart with "--log-handler odoo.tools.convert:DEBUG" for complete traceback
Original PR description
`Net profit/Loss for the Year` report.line has now an aggregation expression[1] which cannot have a groupby. But as the groupby field was removed instead of set to `eval=False`. The groupby is still there and blocking upgrades to 16.0 and 17.0
[1] https://github.com/odoo/enterprise/pull/52157
```
File "/home/odoo/src/odoo/17.0/odoo/tools/convert.py", line 567, in _tag_root
raise ParseError(msg) from None # Restart with "--log-handler odoo.tools.convert:DEBUG" for complete traceback
odoo.tools.convert.ParseError: while parsing /home/odoo/src/enterprise/17.0/l10n_no_reports/data/profit_loss.xml:3
Groupby feature isn't supported by aggregation engine. Please remove the groupby value on 'Net profit/Loss for the Year'
View error context:
'-no context-'
```
Forward-Port-Of: odoo/enterprise#61445[IMP] l10n_mx : Update master data with new Exento tax and fix the XML reader issues Add a new tax, Exento, to the master data of the module l10n_mx, change the fiscal position 'Foreign Customer' and add a new tax group for Exento. Add the Exento tax recognition for the XML reader for vendor bills. task id: 3774996 Forward-Port-Of: odoo/enterprise#61701 Forward-Port-Of: odoo/enterprise#60107
Original PR description
[IMP] l10n_mx : Update master data with new Exento tax and fix the XML reader issues Add a new tax, Exento, to the master data of the module l10n_mx, change the fiscal position 'Foreign Customer' and add a new tax group for Exento. Add the Exento tax recognition for the XML reader for vendor bills. task id: 3774996 Forward-Port-Of: odoo/enterprise#61701 Forward-Port-Of: odoo/enterprise#60107
The `send as message` macro for the template/clipboard block is only supposed to open and edit the message composer on the target form view, then discard it. The form view does not become dirty because of that. However it has been observed that on some Odoo versions, the form view sometimes becomes dirty (indeterministic factor), which is unrelated to the successful macro operation. Therefore it has been decided to always attempt to discard the form so that the test does not fail no matter
Original PR description
The `send as message` macro for the template/clipboard block is only supposed to open and edit the message composer on the target form view, then discard it. The form view does not become dirty because of that. However it has been observed that on some Odoo versions, the form view sometimes becomes dirty (indeterministic factor), which is unrelated to the successful macro operation. Therefore it has been decided to always attempt to discard the form so that the test does not fail no matter if the view is dirty or not during the test. runbot error 62459 Forward-Port-Of: odoo/enterprise#61705 Forward-Port-Of: odoo/enterprise#61682
Added bold formatting to the header text in the template preview to help users distinguish it from the body text. A new line is added between the header and body text in the template preview for the same reason. Task - 3605612 Forward-Port-Of: odoo/enterprise#59143
Original PR description
Added bold formatting to the header text in the template preview to help users distinguish it from the body text. A new line is added between the header and body text in the template preview for the same reason. Task - 3605612 Forward-Port-Of: odoo/enterprise#59143
As seen in support tickets, other errors can be raised by PyPDF2 when trying to compute pages count on corrupted files. As we are not going to do any kind of handling and must not crash because of this, we'll simply log and discard any non-exit exception raised. Task-3614532 Forward-Port-Of: odoo/enterprise#59026
Original PR description
As seen in support tickets, other errors can be raised by PyPDF2 when trying to compute pages count on corrupted files. As we are not going to do any kind of handling and must not crash because of this, we'll simply log and discard any non-exit exception raised. Task-3614532 Forward-Port-Of: odoo/enterprise#59026
**Version:** - saas-16.3 **Step to reproduce:** - Create a subscription product with the type set to 'product' - Create a BOM for that product with the BOM type set to 'kit' - In the component, add any product with the type 'product' - Create a sale order with the products that are created and generate an invoice - Upon creating the next invoice for the subscription product, the picking was not being generated. **Issue:** Currently, if the product type is set to 'product' and
Original PR description
**Version:** - saas-16.3 **Step to reproduce:** - Create a subscription product with the type set to 'product' - Create a BOM for that product with the BOM type set to 'kit' - In the component, add any product with the type 'product' - Create a sale order with the products that are created and generate an invoice - Upon creating the next invoice for the subscription product, the picking was not being generated. **Issue:** Currently, if the product type is set to 'product' and recurring_invoice is true, and the product has a bill of materials (BOM) with the type 'kit' the picking was not created after the first invoice. **Solution:** If the product has a subscription, the quantity for BOM kits will not be updated. task-3681597 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/enterprise#61610 Forward-Port-Of: odoo/enterprise#56121
Steps to reproduce ================== - Open studio on a form view - Edit something - Click on "Restore default view" => Nothing visually happens and the changes stays Forward-Port-Of: odoo/enterprise#61236 Forward-Port-Of: odoo/enterprise#60009
Original PR description
Steps to reproduce ================== - Open studio on a form view - Edit something - Click on "Restore default view" => Nothing visually happens and the changes stays Forward-Port-Of: odoo/enterprise#61236 Forward-Port-Of: odoo/enterprise#60009
Currently, it's not possible to create a form on `event.event` because website_studio doesn't check whether `/event` already exists. Steps: - Install `website_studio` and `website_event` - Open `Events` - Open `Studio` - Click on `Website` tab - Try to add a new form by clicking on `New Form` - Studio doesn't create a new form because it points to /event which already exists (created by `website_event`). This commit verifies that the route doesn't exist before creating it.
Original PR description
Currently, it's not possible to create a form on `event.event` because website_studio doesn't check whether `/event` already exists. Steps: - Install `website_studio` and `website_event` - Open `Events` - Open `Studio` - Click on `Website` tab - Try to add a new form by clicking on `New Form` - Studio doesn't create a new form because it points to /event which already exists (created by `website_event`). This commit verifies that the route doesn't exist before creating it. Pages are served as a fallback when Python routing (`@route`) doesn't match and there is no attachment matching that url. For simplicity and performance, we only check that our new page doesn't collide with an `@route` controller, because we assume that attachments url won't collide. see `website/models/ir_http.py` `Http::_serve_fallback` opw-3778543 Forward-Port-Of: odoo/enterprise#60752 Forward-Port-Of: odoo/enterprise#58504
This is a backport of odoo/enterprise#58479 This commit adds the bidimensional code on the receipt, it also adds to the receipt header the requirements for considering the receipt as a valid electronic document. task-id: 3747828 Community PR: odoo/odoo#161342 Forward-Port-Of: odoo/enterprise#60561 Forward-Port-Of: odoo/enterprise#60451
Original PR description
This is a backport of odoo/enterprise#58479 This commit adds the bidimensional code on the receipt, it also adds to the receipt header the requirements for considering the receipt as a valid electronic document. task-id: 3747828 Community PR: odoo/odoo#161342 Forward-Port-Of: odoo/enterprise#60561 Forward-Port-Of: odoo/enterprise#60451