Friday, February 21, 2025
6 changes · saas-18.1
Resolved issues and error corrections
The Mailbot now sends the correct command when triggering a saved automated response. This prevents the wrong response action from being used, making automated chat assistance more reliable for users.
Original PR description
Before this commit, the mailbot was sending the wrong command to trigger the canned response. This commit fixes the command to be sent and updates the translations accordingly. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The restaurant point-of-sale setup is now included with standard data instead of depending on demo data. This makes restaurant configurations available in non-demo environments, reducing setup issues for real deployments.
Original PR description
In this commit, The restaurant scenario loads in data instead of the demo. related PR: https://github.com/odoo/odoo/pull/194777 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Editing messages in Chatter now follows the same shortcut used when posting new Chatter messages: Ctrl-Enter saves, while Enter adds a new line. This prevents accidental saves and makes editing longer business notes more consistent and predictable.
Original PR description
Before this commit, editing a message was always saving it with `Enter`, including in Chatter. This is a unintentional regression of https://github.com/odoo/odoo/pull/186084 that made improvements to…
Before this commit, editing a message was always saving it with `Enter`, including in Chatter. This is a unintentional regression of https://github.com/odoo/odoo/pull/186084 that made improvements to composer. Sending messages in chatter uses `Ctrl-Enter`, and `Enter` is used to make new lines. In discuss channels, this is the opposite: `Enter` to send a message, and `Shift-Enter` to make new lines. This difference looks strange, but it makes actually sense: `Enter` is the fastest for quick chat messages, whereas `Ctrl-Enter` is more appropriate when making long formatted message, which is generally the case in chatter. The editing of message in chatter should also use `Ctrl-Enter`, for consistency with posting a new message and also chatter messages are still long when editing them. This commit fixes this issue. Task-4593105 Before <img width="854" alt="Screenshot 2025-02-20 at 16 40 22" src="https://github.com/user-attachments/assets/9e9153a5-f67d-492b-9cac-ff74150f2873" /> After <img width="841" alt="Screenshot 2025-02-20 at 16 40 00" src="https://github.com/user-attachments/assets/e879d0d9-223b-45df-8111-517b02f30377" />
Starting the Furniture Shop scenario now completes successfully instead of showing an error. The fix ensures the demo user has an email when posting setup messages, so setup logs can be recorded properly.
Original PR description
Steps to reproduce: -------------------------- - Start db without demo data. - Click on furniture shop. Issue: -------- - There will be a TB while loading the furniture scenario. Cause: --------- - The user used in demo data doesn't have an email and it tries to post message in chatter. Fix: ----- - We have assigned a demo email to the user to avoid TB and also have the logs in chatter. Task: 4486094
Pressing Tab in the live chat window now prioritizes active conversations instead of reopening ended ones. This prevents confusion for operators and keeps their focus on the relevant chat when a conversation has already ended.
Original PR description
**Current behavior before PR:** When a user had an open live chat window and pressed the Tab key, it resulted in an ended chat window being opened. **Desired behavior after PR is merged:** This fix ensures that pressing the Tab key will open active live chats first, then the ended chats. It also keeps the focus on the chat window if the live chat has ended. Task-4507082 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fix makes the customer selection button visible again when using Point of Sale on mobile devices with only the standard POS app installed. It ensures cashiers can assign customers to orders without needing the restaurant add-on, reducing checkout disruption.
Original PR description
Steps: ========== - Install only the point_of_sale module. - Open the PoS Register in mobile view. - Click on the cart button. Issue: =========== - The partner button is not visible. Cause: =========== - The `currentOrder` getter was defined in `pos_restaurant`, making it unavailable when only `point_of_sale` is installed. Fix: - Moved the `currentOrder` getter from `pos_restaurant` to `point_of_sale`, ensuring availability in all cases.