Friday, March 15, 2019
6 changes · master
Enhancements to existing features
This update improves the customer portal experience for sales and deliveries by showing delivery tracking information more clearly and making return labels available beyond a single carrier. It also allows more precise delivery margin percentages, helping businesses manage shipping costs with finer control.
Original PR description
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
FedEx delivery return labels now rely on the standard delivery module setup instead of separate FedEx-specific fields. This reduces duplicate configuration and makes return label handling more consistent across delivery providers.
Original PR description
As generation of return label is now managed through the delivery module, we removed the specific fields that are set in fedex module to use the one created in delivery
Resolved issues and error corrections
Restaurant point-of-sale users can edit table layouts again after a compatibility issue caused by the jQuery 3 update. The outdated drag-and-touch handling was replaced so table editing works reliably across desktop and mobile browsers.
Original PR description
[FIX] pos_restaurant: fix table editing broken after jQuery update The table edition feature of pos_restaurant was using an old lib that was never updated to newer versions of jQuery by its author. For unknown reason, this library went unnoticed when we updated our codebase to jQuery 3. Since this library is impossible to update per se, I decided to remove it entirely and replace it by calls to jQuery.ui. However, the point of this lib was to handle touch events, which jQuery.ui does not. For this, this commit introduces a new library which translates touch events to their click counterparts. Tested on: - Chrome (Windows, MacOS, Linux, Android, iOS) - Firefox (Windows, MacOS, Linux, Android, iOS) - Safari (MacOS, iOS) - Edge (Windows, iOS) - IE11 (Windows) - Samsung Internet (Android)
This fixes an issue where filters or grouping removed in one view could still affect another view after switching back and forth. Users will now see records that match the currently displayed search settings, reducing confusion and inconsistent results.
Original PR description
Let's assume the following scenario on an action with two multi records views (e.g. kanban and list). In the kanban view, activate a domain or groupby, switch to list view, remove the domain or groupby, switch back to kanban: the domain or groupby is still applied (even though it's no longer displayed in the search view). This is due to the jQuery update (ab56e637b7f9) and the use of native Promises (always async) instead of old jQuery 1.11 Deferreds (which where sync when already resolved). In the new version, the domain/context/groupby were added to the params a 'tick too late', so the view was updated without that information (and thus the old domain/context/groupby were kept). Issue reported on the jquery update pad. 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
Quotation templates now use the correct product description language when products are selected. This helps sales teams send quotes with product details that match the customer’s language, reducing confusion and manual edits.
Original PR description
Description of the issue/feature this PR addresses: Task : https://www.odoo.com/web?#id=23249&view_type=form&model=project.task&action=327&menu_id=4720 Pad:https://pad.odoo.com/p/r.65636c71be35f6e1c47704ff254b09bb 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
Updates shipping carrier tests so they match the current packing workflow and avoid incorrect success checks when no package is created. This helps keep delivery integrations for DHL, EasyPost, FedEx, and UPS stable by preventing false test failures or misleading test results.
Original PR description
The signature of the method `_put_in_pack` has changed, which was causing some tests to fail. That's why we should use `put_in_pack` for the `choose.delivery.package` wizard which is in the end more representative of what happens.In addition to this some assertions needed to be corrected since they were wrong when no package were created.