Wednesday, November 28, 2018
4 changes
Resolved issues and error corrections
This fix ensures notification-related tests clean up the extra page element they create. It helps keep automated tests reliable by preventing leftover test artifacts from affecting later checks.
Original PR description
The NotificationService has a side effect: it adds a div inside document.body. We could implement a cleanup mechanism for services, but this seems a little overkill since services are not supposed to be destroyed anyway. 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
Purchase users can now confirm a request for quotation linked to an exclusive purchase agreement even when manager approval is required. The agreement is closed only after the order is approved, preventing an incorrect blocking error and keeping the approval workflow intact.
Original PR description
…pprove Task ID : https://www.odoo.com/web?#id=1884410&action=333&active_id=131&model=project.task&view_type=form&menu_id=4720 Pad link : https://pad.odoo.com/p/r.e5e7435456e1ca31053ac3a88134c41b 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
This fixes an issue where editing translated XML or HTML text could accidentally remove translations in other languages. Businesses using multilingual content will have more reliable translations after synchronization, reducing rework and inconsistent customer-facing text.
Original PR description
Modifying a source term in an XML/HTML translated field can lose translations if the same term is translated in several languages.
This fixes an issue that could prevent a unit of measure form from opening when the Mexico electronic invoicing module is installed. The change helps users access the affected configuration screen without encountering a view loading error.
Original PR description
Fixed error when try loads the view. `Element '<xpath expr="//form/group">' cannot be located in parent view Error context: View view.uom.uom.form.inh.l10n.mx [view_id: 887, xml_id: n/a, model: uom.uom, parent_id: 184]`