Anonymous website visitors can now start livechat conversations even when they do not have an email address. The fix ensures the conversation has a valid sender address fallback, preventing livechat from failing for public users.

The public user doesn't have an email address.
To start a livechat conversation, the email of the user that start the
conversation is used. As the conversation was started in sudo,
the system user's email address was used.

But, since changes with sudo() and with_users(),
the public user is not able to start a livechat conversation
as the system email is not used anymore in this case as sudo is not
changing the user but only skip the user's access right.

To start a livechat conversation, the user must be the system.

Pre-required for task ID: 2028059
Fix Task : 2037048

This update resolves several customer-facing issues, including incorrect company details in portal and checkout forms, wrong credit note due dates, and misleading payment confirmation messages. It also improves email links for multi-website setups and updates reporting precision for Belgian Intrastat compliance.

This fixes a small spelling mistake in configuration used by several Odoo screens, so the intended option now works correctly. Users should see more consistent behavior when creating related records from affected accounting, maintenance, and country views.

In https://github.com/odoo/odoo/commit/8514ef827e1fcc2224aa0f4e6c2849819005c27d
noCreate should have been spelled as no_create to work this commit fixes
that

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 missing sharing controls on website slide pages, restoring the options to send a slide by email and embed it on another website. It helps users share course or presentation content as intended without needing technical workarounds.

…by email and Slide sub-template: share: embed in your website

Current behavior before PR: https://drive.google.com/file/d/1B9S704WzltwTLc1qQSdWDMp4fb8rfhEM/view

Desired behavior after PR is merged: http://www.awesomescreenshot.com/image/3578805/9294e09681484d57cbfcbee076894f5c




--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

The IoT test flow no longer triggers the scan range action during automated checks. This prevents repeated requests during testing, making validation more stable without changing normal user features.

During the test we try the scan range button.
Now we remove this step to avoid multiple request

This update brings forward a set of fixes from earlier versions, improving reliability in manufacturing work orders, accounting follow-ups, documents, shipping, and Mexican localization. Business users should see fewer interface issues, better translated customer messages, and more accurate shipment and invoice data handling.