Daily updates from Odoo
Wednesday, February 28, 2018
4 changes · master
Enhancements to existing features
This update avoids clearing the selected task on a timesheet entry when the chosen project is still the same as the task's project. It also ensures a default employee passed into the timesheet form is saved properly, reducing unnecessary re-entry and preventing missing employee information.
Original PR description
…t task_id.project_id Task: https://www.odoo.com/web?#id=35414&view_type=form&model=project.task&action=333&active_id=131&menu_id=4720 Pad: https://pad.odoo.com/p/r.b1dc522b35958704f06bb1fa664bed91 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Resolved issues and error corrections
Demo customers and selected products are no longer automatically tied to the main company, so they can be used correctly in multi-company demo and test scenarios. This helps prevent incorrect warehouse and product combinations and keeps automated checks reliable in multi-company setups.
Original PR description
**Description of the issue/feature this PR addresses:** This PR fixes demo data to have the tests executed correctly as it should if having multicompany in mind. For example, tests that use the…
**Description of the issue/feature this PR addresses:** This PR fixes demo data to have the tests executed correctly as it should if having multicompany in mind. For example, tests that use the Chicago company and Chicago Warehouse doing pickings with products that have the main company should not be possible, just with products without company (or with Chicago company). **Current behavior before PR:** When creating the demo partners, they have the main company by default. When creating demo products, they have the main company by default. **Desired behavior after PR is merged:** When creating the demo partners, they won't have any company by default. When creating some demo products, they won't have any company by default. Note: I didn't put `company_id = False` to all demo products, just I did to the products used in `stock` by Chicago company. I know that some of you may not bother about demo data, but if merged this PR, it will make the travis green in a multicompany environment that have all multicompany constrains like the explained [here](https://github.com/odoo/odoo/pull/20508). Please, be considerate. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fix prevents Odoo's logging setup from failing when running in environments that do not fully support terminal checks, such as notebook-style consoles. Instead of stopping with an error, the system safely treats those outputs as non-terminal and continues initialization.
Original PR description
The current method checks if the handler stream has a `fileno()` method and assumes that it is callable if exists. This may not true as the stream may actually has `fileno()` method which raises an exception. For example, iPython Notebook default handler has a `fileno()` method that raises `io.UnsupportedOperation` exception. With this fix, `is_a_tty()` will return `False` instead of propagating the exception.
This fixes how manufacturing bill of materials details are returned so the correct product information is included for each line. It helps ensure manufacturing processes and related reports use accurate component data.
Original PR description
Description of the issue/feature this PR addresses: Current behavior before PR: bom product in bom_lines, it should be bom_line product Desired behavior after PR is merged: ## I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr should return bom data, and bom lines data