Thursday, November 7, 2024
9 changes · 17.0
Resolved issues and error corrections
The website editor now remembers a user's selected custom gradient color when they reopen the background color picker. This prevents confusion and saves time when editing page snippets, because the picker no longer falls back to the default color.
Original PR description
Steps to reproduce: 1. Take any snippet and select any custom gradient color. 2. Reopen the background color - The selected custom gradient color is not retained as expected. Before version 16, we used wysiwyg, which called the start function to set selected colors easily. In version 17, we switched to OwlJS. Now, color picker always setting the default color as selected color. Therefore, it displays the default color instead of the selected color.  After this PR, the selected color will be set in the start function by replacing the default color, and updating RGBA values accordingly.  Task-3631963
The signup form now prevents users from choosing passwords that are shorter than the company’s configured minimum length. This avoids failed account creation flows after purchases, reducing customer frustration caused by invalid signup tokens on retry.
Original PR description
When trying to sign in (for a new user) after making a purchase (existing token), we can choose a password of less than the minimum length allowed in the configuration. The _check_password_policy method prevents the save of the password to the user but arrives too late in the flow as the initiation of the user creation is half done leading to an Invalid token issue at the next attempt (no partner found for the existing token with _signup_retrieve_partner). By adding the minlength attribute in the form of the sign up, we force the respect of the password policy minimum length in the front end and minimize the risk to encounter the issue. opw-4182543
The data obfuscation command now masks the stored full partner name instead of trying to mask a non-stored display field. This removes a misleading warning from logs and helps ensure partner names are consistently anonymized when preparing databases for non-production use.
Original PR description
before this commit, for obfuscating data in the res.partner model, the display_name field is used, which is non stored field and thus in the log, an error/warning is shown as follows while running obfuscate command odoo.cli.obfuscate: Invalid fields: res_partner.display_name the invalid warning is raised as the field is not a stored field and thus removing it from the obfuscation even though, the res.partner name field is obfuscated, the same data is remaining in the complete_name field, so adding this field to obfuscating field list after this commit, the log will not show the invalid field warning and complete name also will be obfuscated --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fixes an issue in Point of Sale payments using Adyen where a callback could be processed even after the related pending payment line was no longer available. The change helps avoid payment processing errors and improves checkout reliability for staff and customers.
Original PR description
Add a check on adyen callback when paying. Verify if the pending payment line exist before processing the callback. opw-4242322
This fix prevents an error when renaming taxes that share the same translated name in another language. It helps accounting setup and upgrades complete more reliably in multilingual environments.
Original PR description
Since the unique name constraint only works for the active language, it's possible to have more than one tax with the same name in another language. If that's the case, a `ValueError: Expected singleton` error will occur while retrieving the fields in `unique_tax_name_key`. Found in upg-2077316.
Pressing Escape while renaming a chat thread now exits rename mode without closing the chat window. This prevents accidental chat closures and makes the messaging experience smoother for users.
Original PR description
Before this PR, pressing `Escape` while renaming a thread in the chat window closed the entire chat window instead of simply exiting the rename mode. This PR ensures that pressing `Escape` only exits the rename action, keeping the chat window open. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update corrects broken links within the Helpdesk Team form view, ensuring users can easily access relevant documentation. The fix resolves inaccuracies in links to E-learning, Visibility, Email Alias, and Community Forum resources. This improves the user experience and facilitates proper Helpdesk setup and usage.
Original PR description
This PR corrects incorrect documentation links in the Helpdesk Team form view. Steps to reproduce: 1) Install the Helpdesk module. 2) Open any Helpdesk Team or create a new one. 3) Check the documentation links in the following sections: - E-learning - Visibility - Email Alias - Community Forum 4) Notice the incorrect or broken links. **Note**: We do not need to update the .pot file. task-4266660
This update resolves a test failure in the Amazon integration (sale_amazon) caused by a dependency on data that isn't available in the no-demo testing environment. The fix ensures that tests run correctly without relying on this unavailable data, maintaining the stability of the integration.
Original PR description
test_sync_pickings depends on street value, which does not exist in no-demo mode, thus breaking tests. This commit fixes the issue. [broken test](https://runbot.odoo.com/web#id=73283&view_type=form&model=runbot.build.error&menu_id=405&cids=1)
This update fixes an issue where the app logo wasn't immediately updated after a user changed its icon or image. Now, the logo updates dynamically when a user confirms the change, providing a more consistent and user-friendly experience. This ensures users always see the correct branding.
Original PR description
Before this commit: The logo is not updated when users change the icon or image and click the confirm button. The updated logo appears after refreshing the page. After this commit: When users change the icon or image and click the confirm button, the logo is now updated Task-4219545