Daily updates from Odoo
Thursday, April 18, 2019
6 changes
Resolved issues and error corrections
This change updates the project's requirements list, likely restoring a missing update from an earlier maintenance change. It helps keep the system setup consistent for installations and deployments, with no direct functional change expected for everyday users.
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 change reduces unnecessary warning messages during installation when a database view is temporarily dropped and then recreated as expected. It helps avoid false alarms in automated checks while keeping the installation process behavior unchanged.
Original PR description
This problem appears when the module l10n_be_hr_payroll_fleet is installed. This module inherits from hr.contract and will create and modify some fields. By modifying contract's table, PostgreSQL will drop the view from hr_contract_employee_report. At the end of the installation, PostgreSQL will check if tables exist, it isn't the case for the view from hr_contract_employee_report, so it will recreate it. It's the normal behavior. But when a table is missing, a warning is logged and create problem with Runbot. For this reason, it's better to log an Info and not a Warning message. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The stock product form now calculates quantity on hand using the same logic as the detailed stock list. This prevents mismatched inventory figures between the summary button and the underlying records, improving confidence in stock data.
Original PR description
On the product form view, the stat button computing the quantity on hand
doesn't give the same result as the quants list triggered by this button
- What's displayed in the stat button of the quantity on hand ?
1 get the view location of all the warehouses
2 built the generation tree from the view locations
3 get all the quants for those locations
- What's displayed in the quants list of the quantity on hand ?
1 get all the quants stored in internal locations
This commit share the same logic for those two views, by building the
generation tree for the view location then filter on internal locations
Task : 1929515
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-prThe Indian localization demo data no longer changes the main company’s country. This prevents conflicts that caused errors when using other localization demo data, such as Italy, making demo setups more reliable.
Original PR description
Description of the issue/feature this PR addresses: Current behavior before PR: Italian demo data gives errors because of the main company being set to Indian. We should avoid doing that. Desired behavior after PR is merged: No errors and no country being set on the main company in the demo data. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
A typo in a Belgium payroll settings file was corrected to prevent settings pages from crashing when opened. This helps users access configuration screens reliably across apps.
Original PR description
The clickEverywhere test crashes when clicking on the crm/configuration/settings menu. 41a8e9b58 cherry-picked an xml with a typo. Unfortunately, even if the xml is valid, it crashes the form renderer when accessing the settings from any app.
The Indian payroll module was updated to use the correct payroll structure setting name. This prevents installation errors so businesses can enable Indian payroll without being blocked by a setup issue.
Original PR description
This gave errors installing the Indian payroll module.