Monday, December 2, 2019
6 changes · master
Resolved issues and error corrections
This fixes an outdated automated tour used in the website eLearning area so it matches the current code. The change helps keep publishing course content reliable by preventing test failures caused by obsolete test steps.
Original PR description
Fine tunning of 07f70e3c1 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 fix restores the mobile viewport setting used by Odoo's web client test pages. It helps ensure mobile tests reflect real phone and tablet behavior, reducing the risk of layout issues being missed before release.
Original PR description
After commit odoo/enterprise@8a38a60b1ff03836d0029bfec6c50ca777817146 mobile tests didn't run correctly because of missing viewport META in HEAD. This commit add the missing META. This META must be before all JavaScript file to ensure that JavaScript also know that we work in a viewport. Note that "runbot" run tests in a chromium headless with a size screen reduced and so it worked without this fix. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This change reverts a recent logging configuration adjustment that could cause command-line log level settings to override configured log handlers unexpectedly. It helps preserve predictable logging behavior for deployments and troubleshooting.
Original PR description
Configuring the non-root logger based on --log-level had the side-effect (unclear whether it was intended or not as none of the relevant commits really documented the idea) that log-level could…
Configuring the non-root logger based on --log-level had the side-effect (unclear whether it was intended or not as none of the relevant commits really documented the idea) that log-level could override log handlers being set on the root logger e.g. if `log_handler = :INFO` is set in the config file, `--log-level=warn` on the CLI will override it. This could be replicated by swapping `pseudo_config` and `logconfig`, *however* it would also make the sub-loggers override differently (currently on an exact logger match log-handler overrides log-level). The ideal fix would likely be to sequence log-level from the configuration file, log-handler from the configuration file, log-level from the CLI and log-handler from the CLI. However that doesn't really work with the current structure. 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 a duplicate setup entry in the Accounting module for the same responsible user field. Removing the duplicate reduces confusion and helps keep the system configuration consistent without changing user workflows.
Original PR description
Description of the issue/feature this PR addresses: The field user_id was created twice in the model with the same values and options, only a different help message. This removes the duplicated one. Fixes https://github.com/odoo/odoo/issues/40521 Current behavior before PR: `user_id` is defined twice. The second time (which is the best definition) at https://github.com/odoo/odoo/blob/3e1c5b3f4417d0f3b2d6e1f605f2c66d3ce96869/addons/account/models/account_move.py#L190 Desired behavior after PR is merged: `user_id` is just defined once. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
A small typo in the Indian payroll module was corrected so the related form view validates properly. This prevents installation failures for the module and helps ensure payroll setup can proceed as expected.
Original PR description
Task:https://www.odoo.com/web#id=2146360&action=333&active_id=1251&model=project.task&view_type=form&menu_id=4720 Pad: https://pad.odoo.com/p/r.a0e94250cd8b3cddc672f54b6c5399e3
The settings screen now provides a clearer explanation for the Firebase URL field in the mobile app configuration. This helps administrators enter the correct information and reduces setup confusion.
Original PR description
Related to https://github.com/odoo/enterprise/pull/6414