Daily updates from Odoo
Monday, January 27, 2020
4 changes
Resolved issues and error corrections
The calendar date picker now uses fixed column widths, preventing dates from appearing unevenly spaced. This makes date selection clearer and more predictable for users across screens.
Original PR description
task : https://www.odoo.com/web#id=2166438&action=327&model=project.task&view_type=form&menu_id=4720 pad : https://pad.odoo.com/p/r.338243c755ae834f4f672c2bb0b8aa4b In this commit , we have statically fixed the column width of datepicker-calendar. task - 2166438 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 a web compatibility component from interfering with the framework's normal rendering process. It reduces the risk of display or behavior issues when older web widgets are used inside newer screens.
Original PR description
In Owl, 'render' is a (async) function of Component. It should not be overriden in Component specifications, especially to do something else (in this case, rendering the sub widget), without calling _super. 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
Users can now create mass mailings normally when debug mode is not enabled. The form no longer blocks creation because of a hidden internal name field, reducing confusion and avoiding unnecessary warnings.
Original PR description
Task : https://www.odoo.com/web?#id=2178214&action=327&model=project.task&view_type=form&menu_id=4720 Pad : https://pad.odoo.com/p/r.bdbb73aa77f5325c159b6ed2ca9e3b2f 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
Searches on related one-to-many fields now correctly honor settings that include inactive records. This prevents valid records from being missed when a field is configured to look beyond only active related items.
Original PR description
Consider an x2many field `foo_ids` with `context={'active_test': False}`
in its definition, and a comodel with an active field. The value of the
field includes inactive records.
Now consider a search with a domain like `[('foo_ids.bar', op, value)]`.
The search should return all the records with corecords that satisfy the
domain `[('bar', op, value)]`, including inactive corecords, because the
field's context explicitly disables filtering on the active field.