Daily updates from Odoo
Saturday, December 6, 2025
3 changes · saas-18.4
Resolved issues and error corrections
This update resolves an issue where the automatic generation of PEPPOL endpoints for Belgian companies was failing due to invalid characters in the company registry. The fix adds specific validation rules to ensure only valid Belgian VAT identifier characters are used, improving the accuracy of PEPPOL endpoint creation.
Original PR description
When company registry contains characters such as dots (.), automatic fill-up of peppol_endpoint field fails because dots are valid peppol identifier characters, but are clearly not part of belgian VAT identifier. The solution is therefore to add an EAS-specific set of valid characters to prevent this situation no-task Forward-Port-Of: odoo/odoo#238356
This update resolves an issue where the server logger was experiencing excessive logging activity, leading to potential performance slowdowns. The change reverts a recent update that increased the logging frequency, restoring a more stable and efficient logging process. This ensures data is recorded reliably without impacting system performance.
Original PR description
Based on this review of https://github.com/odoo/odoo/pull/238740 this pr reverts the flush interval to 0.5s introduced in https://github.com/odoo/odoo/pull/238648 to avoid queue saturation. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#238912
This update fixes an issue where time off calendar events weren't accurately reflecting the start and end times, particularly when time zones differed from UTC. The change ensures that calendar event times are correctly aligned with the employee's time zone, improving the accuracy of time off scheduling.
Original PR description
**Steps to reproduce** - Have all timezones (browser, employee, working schedule...) aligned on an diffrent timezone than UTC (normal flow). - Take a time off for a half day, or in custom hours and validate it. Issue: the associated calendar event created doesn't match the time off start/end. **Cause** Commit 8c8c38b1d57971aa5ef220f720d4aeea86b6de98 converts the times from the time off (in UTC) to the leave's timezone, this is an issue because `start` and `stop` of `calendar.event` should be in UTC. **Change** The conversion makes sense for allday events, as the `start`/`stop` are not in UTC (see `_inverse_dates` in `calendar_event.py`, they represent a date used for the display of the event, but for non-allday events we have to make sure the `start`/`stop` are the actual times of the leave. opw-5225375 Forward-Port-Of: odoo/odoo#237818