Thursday, September 26, 2024
9 changes · saas-17.4
Resolved issues and error corrections
Website administrators can once again find and select shop page links in autocomplete when editing restricted website content, even if public ecommerce access is disabled. This prevents editors from being blocked when linking to shop pages intended for non-public or controlled areas of the site.
Original PR description
Finetuning of #176391, when ecommerce access was disabled to public users, the admin were unable to reference /shop urls even in restricted parts of the website if needed, because autocomplete didn't suggest those links anymore.
The language selection dropdown in the editor toolbar now has a height limit and scrolls when many languages are available. This prevents it from extending beyond the screen, making translation workflows easier to use.
Original PR description
Description of the issue this PR addresses: Current behavior before PR: When many languages were installed, the translate dropdown would become too large and overflow out of the screen. Desired behavior after PR is merged: The translate dropdown has a maximum height of 40vh and scrolls if the content overflows, ensuring it stays within the viewport. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The product attribute value list no longer shows a deletion confirmation for items that have not yet been saved. This prevents an error when users try to delete a new, unsaved value and keeps the product setup flow smooth.
Original PR description
Steps to reproduce: 1) Create new attribute value (do not save) 2) Click on delete 3) Confirm deletion in the dialog Reason: When the record is new it does not have resId. But `unlink` only accepts list of type 'number' otherwise it throws an error.
When users add documents to a bill of materials, the attachment list now refreshes right away instead of requiring a page reload. This prevents confusion and makes document uploads feel reliable in manufacturing workflows.
Original PR description
In https://github.com/odoo/odoo/pull/152286, we changed the documents that are added to the chatter of a BoM to be added to the product_product directly (or the template if there are no product on the BoM). However, some changes in mail made the just-added document not appear untill reload. This commit fixes it by reloading the chatter when adding an attachment. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Fixes an issue where removing a previously set markup did not properly reset the related discount to zero. This helps keep product pricing accurate when users adjust pricelist rules.
Original PR description
If markup is set to a value then reset to 0, the discount is not properly reset to 0. This commit removes `if item.price_markup` as it was wrong. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update fixes an issue in Point of Sale where adding some products to the cart could fail if they did not have an archived variant. It helps ensure cashiers can add valid products smoothly without unexpected checkout interruptions.
Original PR description
Before this commit, attempting to add a product to the cart that did not have an archived variant would result in an error. opw-4212973 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Event badge printing has been adjusted so more information fits cleanly on badges, with smaller text and reduced margins. Long event or ticket names are now shortened automatically, and printer positioning can be managed directly on the printer for more reliable output.
Original PR description
- Reduced the side margins to allow more text to fit - Decreased the font sizes slightly for the event name and ticket name - Removed the printing offset commands so that offsets can be configured on the printer - Added a text length limit when printing the event name, that will truncate with a '...' - Used `markupsafe.Markup` to stop characters from being escaped when sent to the printer --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Fixed an error that appeared when users opened the signed documents view from a Sign template with no related records. This prevents a disruptive traceback and keeps the Sign workflow usable from the kanban view.
Original PR description
**Version:** - saas-17.4 **Steps to reproduce:** - activate debug mode - go to template with no sign record - click on the "signed document" state button or option from the template kanban **Issue:** - it was giving traceback when clicking on "signed documents". **Cause:** - an UncaughtPromiseError was triggered due to an undefined 'noContentHelp' prop in the SignActionHelper component. **Solution:** - removed the 'noContentHelp' prop from the SignActionHelper component to prevent the validation error as it is not used at anywhere. task-4098729
The Sign app no longer shows the “Request Signature” option when viewing existing signature requests. This prevents users from triggering an error from an action that is not supported in that context.
Original PR description
Versions: ------------ saas-17.4 Steps to Reproduce: --------------------------- 1. Go to the All Documents menu. 2. Click on "Details" from the kanban dropdown. 3. Select "Request Signature" from the cog menu. Issue: --------- A `ValueError` occurs: `Wrong value for sign.request.reference_doc: 'sign.request,1'`. Cause: --------- The `reference_doc` field restricts the `sign.request` model in the `selection_target_model`. Solution: ----------- Hide the "Request Signature" option in the cog menu. task: 4175789