Daily updates from Odoo
Tuesday, April 16, 2019
9 changes · master
Enhancements to existing features
This update makes it easier for developers and partners to customize how product pricelist items are searched. It reduces the need to duplicate or bypass existing pricing logic when extending pricelist behavior, supporting safer and more maintainable customizations.
Original PR description
Description of the issue/feature this PR addresses: If you want extend the pricelist system by adding `applied_on` or any other idea, you need to by pass all the code. With this PR you can just inherit the search of items. @nim-odoo -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The website shop setup tour now points to a snippet that appears near the top of the list, making the drag-and-drop instruction easier to notice. This helps users follow the onboarding flow more smoothly when building or editing an online shop page.
Original PR description
related to task: 1942742 Description of the issue/feature this PR addresses: step to drag snippet is not enough visible. Current behavior before PR: step to drag snippet is not enough visible Desired behavior after PR is merged: step to drag snippet is now visible Task: https://www.odoo.com/web?#id=1942742&model=project.task&view_type=form&menu_id=4720 Pad: https://pad.odoo.com/p/r.931c7ff1b3a5a3ce63f0a716ee633aac -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Demo barcode data for stock locations was moved out of the demo file and into regular data setup. This makes barcode-related examples and tests more consistent without changing day-to-day business workflows.
Original PR description
**Description of the issue/feature this PR addresses**:
- Task: https://www.odoo.com/web#id=1947320&action=333&active_id=131&model=project.task&view_type=form&menu_id=4720
- Pad: https://pad.odoo.com/p/r.78fd07890eda2e9557392580503602dc
**Description:**
-Removed demo data of stock.location from demo file and added it into data file.
--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-prThis change introduces a reusable way to test Belgian payroll calculations against specific payslip scenarios. It helps the payroll team validate more cases consistently, reducing the risk of incorrect salary computations over time.
Original PR description
In order to ensure that we compute correctly all the payslips, we need to test specific cases. This commit aims at facilitating the writing of such tests
Resolved issues and error corrections
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
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.
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
Code cleanup and technical improvements
Several internal fields named "type" were renamed to more specific names across Odoo modules. This reduces conflicts with standard Python behavior, making the platform easier to maintain and less prone to technical issues without changing day-to-day user workflows.
Original PR description
**Description of the issue/feature this PR addresses:** Follow-up of https://github.com/odoo/odoo/pull/27262. **Current behavior before PR:** Many models have the selection field `type`, which overwrites the python method [type](https://docs.python.org/3/library/functions.html#type). **Desired behavior after PR is merged:** Some `type` fields of several models have been renamed to _something_type_. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update standardizes several internal field names across accounting, product, CRM, document sharing, attachments, and partner records. It mainly improves maintainability and consistency for future development, with little expected direct impact on day-to-day users.
Original PR description
Follow-up of https://github.com/odoo/odoo/pull/27599. I have not tested it, so maybe I left few cases to adapt, but once the community PR is merged, then it will be fast and easy to detect the remaining cases and adapt them.