Daily updates from Odoo
Friday, September 16, 2022
5 changes
Resolved issues and error corrections
Financial reports now keep popup icons visible even when a leading value is zero or otherwise appears empty. This prevents users from losing access to actions such as carryover details or cell editing while still preserving the report layout behavior.
Original PR description
When rendering the report, we remove some empty column values in order to let space to stretch the line name further. When doing that, we didn't check whether the line contained a popup icon or not (for carryover or cell edition, for example), causing them to disappear on 0-balanced leading cells.
The phone number input now uses the correct standard field type, improving consistency with browser behavior. This helps ensure phone fields work as expected across devices and avoids relying on an invalid input setting.
Original PR description
This pr is the enterprise counter part of odoo/odoo#100388 where we set the input type to "tel" in PhoneField, instad of "phone", which simply doesn't exist.
This fixes missing styling for PDF previews in manufacturing work orders and Sign after an internal field name changed. Users should see PDF documents displayed with the expected layout again, improving readability and consistency.
Original PR description
The class for the pdf_viewer field changed from `o_field_pdfviewer` to `o_field_pdf_viewer`
This fixes the appearance of certain dropdown fields in salary contract pages after the Bootstrap 5 migration caused them to display with mismatched styling. Users should see a more consistent and familiar form experience while a longer-term library upgrade remains for the future.
Original PR description
Due to the migration of Bootstrap 5, `form-control` was converted into `form-select` to `select` tag. This made was due to a caret missmatch with the previous version due to a change in Boostrap 5. But in some case the `select` input used Select2. Actually our Select2 is an old version (3.5.4 the last release is 4.0.13) and we have a `CSS` file alongside Select2 to match the style of Boostrap, but it is for Boostrap 3. We restore the old class in these case to restore the old styling (with little hiccup but better than actual). The good fix, will be to upgrade the lib, and its Bootstrap theming (for BS5) to the last version.
Shipments with no insurance amount will no longer trigger an unnecessary insurance request to EasyPost. This prevents failed shipping operations caused by EasyPost rejecting insurance amounts of zero.
Original PR description
Before this commit, we call the `/insure` endpoint even when it is null. this leads to the following error: `Easypost returned an error: Insurance amount must be greater than 0` With this commit, we avoid calling the insure endpoint whenever the insured amount is 0.0 .