Odoo Changelog — 2025-12-07

Sunday, December 7, 2025

2 changes · 18.0

Bug Fixes(2)

Resolved issues and error corrections

[FIX] frontdesk: ensure company logo is always displayed on the kiosk

Enterprise18.0frontdeskMEDIUM

This update resolves an issue where the Frontdesk kiosk URL wouldn't display the correct company logo when switching companies. The fix ensures the kiosk always accesses the correct company record, allowing the logo to load properly. This improves the user experience and visual consistency of the Frontdesk station.

Original PR description

When switching companies in a Frontdesk station and opening the kiosk URL, the company logo does not appear.

**Steps to produce:**
- Install the `frontdesk` module.
- Ensure the database has at least two companies, each with a logo configured.
- `Enable multi-company` access (user has access to all companies).
- Open any Frontdesk station configuration and change the company to one different from the currently active company.
- Copy the kiosk URL and open it in an incognito/private window.
- The kiosk opens, but the company logo is missing.

**Issue:**
- Company logo not comes on frontdesk kiosk.

**Root cause:**
- When the kiosk URL is accessed, Odoo logs an `Access Denied by record rules`.
- This happens because the selected company on the station is not included in the `Public User’s companies`.
- As a result, the public user cannot read the company record, so the logo does not load.

**Solution:**
- Added an `onchange` on `company_id` to automatically include the selected
 company in the Public User’s `company_ids` if it is not already present.
- This ensures the kiosk always has access to correct company record and logo.
- Also added an XML-side fix to prevent an access error that occurs when
  a company is not activated and we attempt to select it in the company field.

**Before:**
<img width="500" height="500" alt="frontdesk_image_before" src="https://github.com/user-attachments/assets/b002ac6e-5271-4561-bf03-542a3feeefd1" />

**After:**
<img width="500" height="500" alt="frondesk_image_after" src="https://github.com/user-attachments/assets/7b5bffe4-ccbf-48f5-ad9c-d5e6d2e7678e" />

**opw-5138980**

Forward-Port-Of: odoo/enterprise#100300

#frontdesk#kiosk#logo#multi-company

[FIX] account, account_peppol: prevent invalid XML characters from blocking Peppol sending

PR #236836

Core18.0accountaccount_peppolMEDIUM

This update resolves an issue where invalid characters in invoices prevented successful sending to Peppol, causing system errors. The fix ensures that only compatible XML characters are used during invoice conversion, preventing crashes and guaranteeing proper Peppol integration. This improves the reliability of the Peppol sending process.

Original PR description

## Issue:
When a character that's not compatible with XML is in an invoice, and you send it to Peppol, a traceback was raised: `ValueError: All strings must be XML compatible: Unicode or ASCII, no NULL bytes or control characters`

## Cause:
`dict_to_xml` converts each invoice field into XML, but certain control characters (e.g., `\x02`) are not allowed in XML according to the specification: https://www.w3.org/TR/xml/#charsets
If such a character appears in the data (e.g., imported through a product CSV), the XML generation crashes

## Steps to produce:
- Install `account_peppol` and `l10n_be` (to get the BE Company CoA)
- Import a product containing a control character:
`echo -e "name,default_code\nTest\x02Product,ABC123" > products.csv`
- Create an invoice for the BE company using the product `Test\x02Product`
- Send it via Send > by Peppol
- A traceback is raised

opw-5114648

#peppol#invoice#xml#error

When switching companies in a Frontdesk station and opening the kiosk URL, the company logo does not appear. **Steps to produce:** - Install the `frontdesk` module. - Ensure the database has at least two companies, each with a logo configured. - `Enable multi-company` access (user has access to all companies). - Open any Frontdesk station configuration and change the company to one different from the currently active company. - Copy the kiosk URL and open it in an incognito/private window. - The kiosk opens, but the company logo is missing. **Issue:** - Company logo not comes on frontdesk kiosk. **Root cause:** - When the kiosk URL is accessed, Odoo logs an `Access Denied by record rules`. - This happens because the selected company on the station is not included in the `Public User’s companies`. - As a result, the public user cannot read the company record, so the logo does not load. **Solution:** - Added an `onchange` on `company_id` to automatically include the selected company in the Public User’s `company_ids` if it is not already present. - This ensures the kiosk always has access to correct company record and logo. - Also added an XML-side fix to prevent an access error that occurs when a company is not activated and we attempt to select it in the company field. **Before:** <img width="500" height="500" alt="frontdesk_image_before" src="https://github.com/user-attachments/assets/b002ac6e-5271-4561-bf03-542a3feeefd1" /> **After:** <img width="500" height="500" alt="frondesk_image_after" src="https://github.com/user-attachments/assets/7b5bffe4-ccbf-48f5-ad9c-d5e6d2e7678e" /> **opw-5138980** Forward-Port-Of: odoo/enterprise#100300

## Issue: When a character that's not compatible with XML is in an invoice, and you send it to Peppol, a traceback was raised: `ValueError: All strings must be XML compatible: Unicode or ASCII, no NULL bytes or control characters` ## Cause: `dict_to_xml` converts each invoice field into XML, but certain control characters (e.g., `\x02`) are not allowed in XML according to the specification: https://www.w3.org/TR/xml/#charsets If such a character appears in the data (e.g., imported through a product CSV), the XML generation crashes ## Steps to produce: - Install `account_peppol` and `l10n_be` (to get the BE Company CoA) - Import a product containing a control character: `echo -e "name,default_code\nTest\x02Product,ABC123" > products.csv` - Create an invoice for the BE company using the product `Test\x02Product` - Send it via Send > by Peppol - A traceback is raised opw-5114648