Daily updates from Odoo
Wednesday, January 15, 2020
5 changes
Resolved issues and error corrections
This fixes an issue where edited custom text on product pages could block future website template updates. Product page custom text is now handled in a way that preserves update compatibility, reducing maintenance issues for online stores.
Original PR description
Custom text on a product was not an oe_structure thus preventing who modifies it to receive updates on the view. oe_structure save method wasnot saving the tag text. task-2040764 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Portal users can now post comments on demo project tasks without encountering an access-related error. This helps keep customer-facing collaboration smooth in demo or sample project environments.
Original PR description
When a portal user was commenting on a project task, the ir.rule `mail.message: portal/public: read published messages` was preventing the method _notify_record_by_email to get the messages's parent_id on the demo data. This commit aims to define a default value in such cases. task: 2009615 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
The mail emoji button now appears only once when multiple languages are enabled. This avoids duplicate controls and keeps the emoji button aligned with the language button, making multilingual message editing cleaner and easier to use.
Original PR description
Bug === When we have 2 languages activated, `this.$el` contains 2 elements 1. The input text element 2. A `div.o_field_translate` element So, when we do `this.$el.after([...])` we add the button to 2 elements Fix === If we have multiple element in `this.$el` - Add a CSS class on the emojis button (this CSS class add some right margin) - Add the button on the last element in `this.$el`, so we have only one emojis button Adjust vertical position, so the button is aligned with the language button. Task #2168338
This fixes an internal purchase/manufacturing workflow error where the system could return the wrong type of value when no linked purchase line existed. The change helps prevent downstream processing issues in affected purchasing and manufacturing operations.
Original PR description
Commit e923058 aims to ensure the key 'created_purchase_line_id is
returned only if the move as this field filled. The issue is due to
the way python compare falsy object.
a = b and c will return b if b is falsy
will return c if neither b nor c are falsy.
If move_raw_id passed in the method doesn't have created_purchase_line_id
iterate_key = purchase.line.id() or 'created_purchase_line_id'
= purchase.line.id()
which is not correct as the method should return a string.
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-prFixes dropdown actions on financial report lines so options like Journal Items receive the needed account reference. This helps users navigate from reports to the underlying accounting entries without errors or broken actions.
Original PR description
The actions in the dropdown of a financial report line needs an id to work. For example, the "Journal Items" action needs a valid account.account id.