Friday, December 15, 2023
10 changes · 17.0
Resolved issues and error corrections
LATAM journals will no longer show gap warnings that do not fit how local vendor bills and customer invoices are numbered. This reduces confusing messages for accounting users and helps them focus on relevant document issues.
Original PR description
…se for LATAM journals 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 change prevents an error that could occur when processing certain Latin American accounting documents, such as withholdings. It helps users complete these transactions without interruption.
Original PR description
introduce by https://github.com/odoo/odoo/commit/1485692bb9d144375c81e353ccc3e358646fbacc Description of the issue/feature this PR addresses:  for example on `Withholding` because `move_type` = `'entry'` CC: @jco-odoo --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The POS payment screen now correctly shows the Customer label in the user's selected language. This improves the checkout experience for non-English users by removing an untranslated label.
Original PR description
### Steps to reproduce issue: 1. Select non english language 2. Open a POS session 3. Select a product 4. Got to payment UI 5. "Customer" is not translated ### Explanation: Concerned element uses a `t-out` with an `or` operator, translation can not apply to it. ### Suggested fix: Use of distinct tags with `t-if` and `t-else` instead, to make translation work. (Due to a field having the same key and the affected file already being referenced, the .pot file does not need updates.) opw-3636234
This fixes an issue where checkboxes marked as selected by default in website forms lost that setting after the page was saved. Businesses using website forms can rely on preselected checkbox options staying in place for visitors, avoiding configuration errors and inconsistent form behavior.
Original PR description
Before this commit and since PR [1], the default "checked" value set on checkboxes field on the form snippet were lost once the page is saved. This is because [1] changed the rendering engine of qweb…
Before this commit and since PR [1], the default "checked" value set on checkboxes field on the form snippet were lost once the page is saved. This is because [1] changed the rendering engine of qweb templates from our own qweb js rendering code to owl templates rendering. By doing so, `t-att-checked="'checked'"` would toggle the "internal" checkbox checked value but would not add the checked attribute on the element. It's a deliberate choice made in owl. As the checked attributed does not mean the same as the internal checked value, it makes sense. Indeed, the checked attribute is about the default value of the checkbox while the checked internal value is about the current checked state of the checkbox. In React, for instance, the same behavior can be seen. And if one wants to really set the checked attribute, they got to go with `defaultChecked`. Same apply with `value`. Maybe owl will implement the same `defaultXXX` behavior in the future as it's something that was already discussed on their side. [1]: https://github.com/odoo/odoo/pull/130467
The website page list no longer offers a duplicate action that could create pages with the same URL. This prevents hidden or confusing duplicate pages and keeps the proper cloning flow through page properties, where users are asked for a new page name and URL.
Original PR description
Before this commit and since commit [1], it was possible to clone a page in the page list view. It shouldn't be the case, cloning a page lead to bad result: a page with the same URL which is not shown in the page list view because pages are filtered by URL to remove duplicates. Cloning a page has always had to be done through the page properties > "clone page" button. Doing it this way will ask the user for a new page name (and so a new url). The page will then correctly be listed. [1]: https://github.com/odoo/odoo/commit/3192051806e0da1276604a31ad818f8768105362 opw-3591738
This update removes unnecessary extra spacing that was appearing on the right side of embedded views in the Knowledge module. The spacing was previously added but is not needed for comments in embedded views, so it has been cleaned up to improve the visual appearance and layout of the interface.
Original PR description
This PR removes the extra space on the right side of an embedded view. The extra space was added in https://github.com/odoo/enterprise/commit/3f5487f89e27, but we don't need that space for comments in the case of embedded views. Therefore, we are removing it. **Task**-3619543
A bug was fixed in the Documents module where the system was attempting to write to a display name field on attachments that doesn't have a setter function. This fix prevents errors and ensures the attachment handling works correctly without trying to modify read-only fields.
Original PR description
This field is only a getter with no setter. https://github.com/odoo/odoo/pull/146109
This update fixes a technical error that occurred when users tried to group calendar events by partner in the gantt view. The fix removes unused code that was causing the error. This was leftover from a previous feature attempt that was discontinued, so no users should be affected by this change.
Original PR description
Currently if you group the gantt view on calendar events by partner_ids you get a traceback because we try calling a method that is not named properly. As the intended feature is not supported and we don't expect anybody to have been using the method nor is it used anywhere internally we remove both the python method that should have been called and its caller in js. It was a remnant of trying to make grouping by partner_ids the default Which ended up being scrapped except for this part. Although it is being reestablished in 17.0 and up with this task task-3452277 Forward-Port-Of: odoo/enterprise#52702
This fix removes a duplicate entry of the fiscal regime information that was appearing twice in Mexican invoice reports. The fiscal regime is now displayed only once, cleaning up the invoice layout and ensuring accurate document presentation for Mexican tax compliance.
Original PR description
[FIX] l10n_mx_edi: Remove duplicated Fiscal Regime. After checking with the PO, this fix is to resolve a duplicate of the fiscal regime in the `invoice_report` as it is mentioned twice. opw-3601138 Forward-Port-Of: odoo/enterprise#52438
The reconciliation wizard now hides the 'Allow partial' option when processing a single transaction line, since partial reconciliation doesn't apply in this scenario. This streamlines the user experience by removing unnecessary options and preventing confusion during the reconciliation process.
Original PR description
Make the 'Allow partial' checkbox invisible if the wizard is opened with one and only one line. It doesn't make sense to have partials on a single line since for now the amount of the write-off is not editable/customizable (that will change in master). task-id: opw-3490136 Forward-Port-Of: odoo/enterprise#51815