Thursday, June 14, 2018
2 changes · master
Resolved issues and error corrections
This update aligns several Odoo screens so users are not offered create or edit paths where they were not intended. It also separates Point of Sale configuration views by role and keeps manufacturing reports focused on reporting views, reducing confusion and accidental changes.
Original PR description
**Description of the issue this PR addresses:** Some views have inconsistencies: - First commit fixes some views by adding `create=False`. They should have it because the other related views…
**Description of the issue this PR addresses:** Some views have inconsistencies: - First commit fixes some views by adding `create=False`. They should have it because the other related views (normally tree view) of the model already have it. - Second commit is explained by its name. - Third commit is a special case in the pos.config views. The kanban view has the `create=False` but the tree view doesn't. But happens that exists two actions that open these views. One action (dashboard) has access the user and the manager so it makes sense to just has kanban view for that action. The other action only has access the manager, so it makes sense to has access to tree and form who could edit and create new pos configs. - Fourth commit it's not a fix but something that interested me. It just happens that there exists two actions for the same model. One action is for reports, so in theory the people accessing to this action should only see the "reports" views (calendar & pivot) and not the tree view which has link to form. So I deleted the tree fro that action although other option would be letting the tree but deleting the form from that action. **Current behavior before PR:** You can access to form view in some models when this is not intended. **Desired behavior after PR is merged:** Solved explained inconsistencies. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The web interface's date handling library has been updated so date validation works correctly. This prevents errors when checking whether a value is a date and improves reliability across localized date formats.
Original PR description
Description of the issue/feature this PR addresses: Using the function `moment.isData() ` causes the error "moment.isDate is not a function". Update the moment.js from version 2.17.1 to 2.22.2 allows you to fix this Current behavior before PR: The error "moment.Date is not a function" when using the function `moment.isDate()` Desired behavior after PR is merged: The function `moment.isDate()` work correctly -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr