Odoo Changelog — 2019-04-16

Tuesday, April 16, 2019

3 changes

Bug Fixes(3)

Resolved issues and error corrections

[FIX] website_sale: some quick fix odoo/odoo@1537b475b0a06b1a99b664bb…

Coremasterwebsitewebsite_sale

This update fixes small issues in the online shop experience, including incorrect labeling and iframe closing behavior. These corrections help make product pages and website sales interactions clearer and more reliable for shoppers and staff.

Original PR description

…20f9d9e21141baf6

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

#online shop#product pages#labels#iframe

[FIX] website_sale: flag tests as post_install

PR #32727

Coremasterwebsite_sale

This change adjusts when certain online shop price list checks run so they happen after installation instead of during setup. This helps avoid unrelated test failures and keeps automated validation more reliable without changing customer-facing behavior.

Original PR description

Before this commit, theme runbot-theme was red somehow for the geoip pricelist
test.
Adding post_install seems to fix the issue, anyway it is better to flag the
tests as such as it make no sense to test pricelists during module install.

#tests#online-shop#pricelists

[FIX] hr_timesheet: timesheet UoM widget restored

PR #32736

Coremasterhr_timesheet

This fixes an issue where timesheet unit fields could use the wrong display format in normal loading mode. Users should now see timesheet values shown with the correct unit format consistently, matching the intended company/session settings.

Original PR description

When the assets are loaded, the `hr_timesheet.timesheet_uom` scope is
loaded in order
to bind the `timesheet_uom` to the correct already existing widget (defined
in the session, like `float_time` or `float_factor`, ...).
The problem is that in normal mode (not debug assets), when the binding is
done, the field_registry is empty, so the correct base widget is not applied.

The fix is to add the scope filling the registry in the requirements of the
`timesheet_uom` scope. Strangely, it was working in debug assets mode.

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

#timesheets#unit-of-measure#display

…20f9d9e21141baf6 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

Before this commit, theme runbot-theme was red somehow for the geoip pricelist test. Adding post_install seems to fix the issue, anyway it is better to flag the tests as such as it make no sense to test pricelists during module install.

When the assets are loaded, the `hr_timesheet.timesheet_uom` scope is loaded in order to bind the `timesheet_uom` to the correct already existing widget (defined in the session, like `float_time` or `float_factor`, ...). The problem is that in normal mode (not debug assets), when the binding is done, the field_registry is empty, so the correct base widget is not applied. The fix is to add the scope filling the registry in the requirements of the `timesheet_uom` scope. Strangely, it was working in debug assets mode. 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