Daily updates from Odoo
Thursday, June 28, 2018
3 changes · master
Enhancements to existing features
Updating quantity on hand now opens a fuller inventory adjustment when products use lot or serial tracking, or when companies manage multiple locations. This helps users enter quantities more accurately by choosing locations and tracking details, while adding safeguards to avoid duplicate lines or unintended product creation.
Original PR description
task:https://www.odoo.com/web#id=30921&view_type=form&model=project.task&action=333&active_id=131&menu_id=4720 pad:https://pad.odoo.com/p/r.0eae263fbdb52658839fc928b4aed57f 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
Resolved issues and error corrections
Some screens included settings that accidentally hid content needed for pop-up dialogs and accessibility tools. This update removes those incorrect settings so affected dialogs can open properly and visible content remains available to users.
Original PR description
Some aria-hidden are present on some elements that must be visible. Some dialogs don't open correctly with this. This PR removes these aria-hidden attributes.
This fix ensures related customized views are removed correctly when their parent views or fields are deleted. It prevents crashes after uninstalling and reinstalling modules that had been customized, improving reliability for users of Studio or custom view changes.
Original PR description
Revert of e5f7b5673505d8df3951075e486add96de045650 The aforementioned commit was done at a time when Studio did not exist, before this commit it was possible to break views in the following manner: *…
Revert of e5f7b5673505d8df3951075e486add96de045650
The aforementioned commit was done at a time when Studio did not exist,
before this commit it was possible to break views in the following
manner:
* Install module A, studio
* Add a field to any view of module A with studio
* Uninstall module A
* Reinstall module A
* Try to access the view that was modified using Studio
=> BOOM! The view will crash
This happens because the field created with studio is properly deleted,
however the studio view referencing the field is never properly deleted,
and when the module is reinstalled the inheritance is re-applied and
since the field doesn't exist, it goes boom-boom
Also applies to custom non-studio views and fields, however for this case commit e5f7b5673505d8df3951075e486add96de045650 implies that this is not the desired behavior which is arguable.
An OK, non-destructive alternative would be to set this field to `ondelete='set null'`, in which case the custom view would not be deleted but the inheritance wouldn't be automatically applied (=no crash)
Task 1858158