Monday, May 4, 2020
5 changes · master
Enhancements to existing features
This update simplifies the main control panel by keeping search filters visible, removing extra dropdown indicators, and moving import into the favorites menu. It also adjusts export visibility so users only see it when no records are selected, reducing clutter and making actions clearer.
Original PR description
PURPOSE 1) show export button only when no records are selected. 2) remove advanced search option from controlpanel searchbar. 3) remove dropdown caret from controlpanel and change the icon of action buttons 4) remove import button and add it in favorites dropdown. SPECIFICATIONS 1) export button should only show when no records are selected. 2) searchbar should only show normal search icon. And filters, groupbys should always show. 3) dropdown icon should be removed from filters, groupbys, etc.., and change the icon of action buttons 4) import button should be removed and add it in to the favorites dropdown. LINKS PR https://github.com/odoo/odoo/pull/49793 Task 2234547 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update lets Odoo create purchase order lines, sales order lines, and CRM leads in batches across related apps. This improves consistency between modules and can make high-volume operations smoother and more efficient.
Original PR description
Ensure main Odoo models supports batch record creation. * `purchase.order.line` supports multi creation in `purchase`, but not anymore when `purchase_stock` is installed. * `sale.order.line` supports multi creation in `sale`, but not anymore when `sale_purchase` is installed. * `crm.lead` doesn't support batch creation atm, but it doesn't cost anything to support it. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The control panel search area has been simplified by removing the advanced search option from the sample interface and hiding dropdown carets on search menus. This makes filters, grouping, and favorites feel cleaner and more consistent, with added mobile coverage for the import action in favorites.
Original PR description
PURPOSE 1) remove advanced search option from controlpanel searchbar sample UI. 2) remove dropdown caret from controlpanel sample UI. SPECIFICATIONS 1) removed advanced search option from sample UI. 2) dropdown icon removed from sample filter, groupby and favorite etc.. 3) added a mobile testcase for import button in favorite dropdown. LINKS PR https://github.com/odoo/enterprise/pull/10059 Task 2234547
Resolved issues and error corrections
This fix stops users from saving an action configuration that lists the same view type more than once. It prevents a web client crash that could make the interface unusable when opening affected Inventory transfer screens.
Original PR description
Description of the issue/feature this PR addresses: * connect to runbot with debug mode enabled * go to Inventory -> Operations -> Transfers * using the debug mode, edit the action and set the view mode to "tree,kanban,calendar,tree" * go back to the main menu, press Ctrl-F5 to force reload * go to Inventory -> Operations -> Transfers Current behavior before PR: You get a crash and the web client becomes unusable (can't click anywhere) Desired behavior after PR is merged: It is not possible to save the action with twice "tree" in view_mode. This is reported as OPW 2241415 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Fixed an issue where interface views loaded from files in developer XML mode could appear untranslated. This keeps the user experience consistent across normal and developer modes, while avoiding accidental storage of translated view definitions.
Original PR description
When computing the `arch` from the arch_db, the field gets translated as a matter of course as `arch_db` is a stored field with a translation method. This means `arch` is assumed to be in the proper…
When computing the `arch` from the arch_db, the field gets translated as a matter of course as `arch_db` is a stored field with a translation method. This means `arch` is assumed to be in the proper language in the cache. However when reading from the filesystem this is not the case, and the view XML ends up untranslated:  (left is without dev=xml, right is with) Fix the issue by applying the translation function from arch_db onto the stuff we got from the filesystem. Note: under the assumption that we *do not* want to store translated archs in arch_db, explicitly set the lang to None when resetting views. For `_compute_arch_diff` however I left it in place, such that the diff is in whatever language the user has selected as other `arch` fields are accessed directly. That aside, I don't know how well the view reset thing deals with not being in the default language as arch_prev and friend don't really seem to take language into account. Second half of task 2059557