Wednesday, May 27, 2020
6 changes · master
Resolved issues and error corrections
This update improves the web module’s internal request handling used during testing, helping new visual components such as the map view behave correctly. It also prevents certain renderers from being initialized twice, reducing the chance of display issues and unnecessary processing.
Original PR description
This commit adds httpRequest in test_env because the new map renderer needs it. Task: 2230976
This update corrects a previously misapplied fix in the invoice analysis report. It helps ensure accounting reports reflect the intended behavior and reduces the risk of misleading invoice analysis data.
Original PR description
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 fixes an error that could occur when changing an attendee's status on a calendar event. It helps ensure calendar responses can be updated reliably without disrupting users.
Original PR description
Coming from the calendar refactoring at https://github.com/odoo/odoo/commit/39aef65f37a8ae969527b31a680eb27fddbc5710 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 fixes an issue where a previously invisible line at the top of the website footer could become visible in some situations. The change keeps footer editing behavior working while removing the unwanted visual artifact for visitors and editors.
Original PR description
The footer of Odoo is composed of 3 main elements: a `<footer/>` with a .oe_structure and the footer copyright inside. The footer had a transparent top border which was there for technical reason: making sure the .oe_structure content was "1px" below the end-of-page content so that dropping a snippet at the end of page but also in the footer was possible (otherwise the dropzones would be at the exact same position). This border which was invisible at the time may now become visible in more cases so we have to remove it. Another hacky solution is made to replace the old one, while remembering the footer usability is being reviewed anyway. task-2197038
This update corrects a small typo in the Studio approvals area. It helps keep the interface or related behavior polished and avoids confusion from incorrect wording.
This fix removes outdated internal access-related entries in Odoo Studio. It helps prevent obsolete configuration data from lingering and reduces the chance of confusing or incorrect behavior when Studio-managed models are updated.
Original PR description
Cf odoo/odoo#50661