Tuesday, October 28, 2025
5 changes · 19.0
Enhancements to existing features
This update adds end-of-day balance reporting and refund support for Six payment terminals in Point of Sale. It also improves transaction speed, receipt handling, and payment details so store teams get a smoother checkout and closing process.
Original PR description
Based on the feedback received from our partners we are missing some features in our Six terminal integration. This PR adds them 1. Send balance command to print end-of-day report 2. Adapt the code to reduce the sleep delay after each transaction 3. Refunds/payment reversals for Six + it also adds some minor code improvements like a) Card brand is now saved in pos payments instead of the card number b) Card number is still being sent to PoS and while not stored in v17 will be stored from v18 c) The code of ctypes_terminal_driver and Six Driver was improved to reuse the buffer size and improve the buffer usage d) Fixes the receipt size for the Six terminals e) updates the Six C libraries used to the latest version to get all the newest fixes Related C PR: https://github.com/odoo/worldline-lib/pull/9 Forward-Port-Of: odoo/enterprise#98132 Forward-Port-Of: odoo/enterprise#96748
The HTML editor now handles format removal more consistently for headings and other block text. This helps users clean up styled text while preserving the intended base typography, reducing confusing formatting behavior when editing website or document content.
Original PR description
Description of the issue this PR addresses: Current behavior before PR: Styles applied via typography classes such as `display-1-fs`, `display-2-fs`, etc. could not be removed from block elements. eg: `<h1 class="display-1-fs">t[es]t</h1>`. Desired behavior after PR is merged: - HTML tags (`<p>`, `<h1>`, etc.) represent the base typography. - Typography classes (display-*) should be treated like equivalent HTML tags, not as removable styles. - Only display classes (*-fs) are considered for format removal. - When removing format, the editor now restores the font style of the underlying HTML tag. eg: `<h1 class="display-1-fs">t<span class="h1">[es]</span>t</h1>` task-4981275 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The HTML editor now handles inline code formatting more reliably, including wrapping selected text when the backtick key is pressed and supporting empty inline code blocks. This prevents cursor jumps and makes navigation around code-formatted text smoother for users editing content.
Original PR description
**Purpose of this PR:** This PR includes multiple fixes and improvements related to typing and navigating around inline code elements. **Current behavior before this PR:** - Because of the change…
**Purpose of this PR:**
This PR includes multiple fixes and improvements related to typing and navigating around inline code elements.
**Current behavior before this PR:**
- Because of the change made in commit [1], the selection was not set until two backticks were detected. As a result, inserting a single backtick caused the cursor position to change unexpectedly.
- Typing two backticks (``) without any text between them did not properly create an inline code element.
Desired behavior after this PR is merged:
- The text node is merged with its siblings only when two backtick are detected, so no DOM changes occur with a single backtick, and the selection no longer needs to be updated in that case.
- Now, a zws is added as a sibling of the inline code element to ensure proper navigation outside the code element.
- Typing two backticks with nothing in between now correctly creates an empty inline code element.
- Wrap the selected text in a inline code element when the '`' key is pressed.
- Replaced ZWS with feffs around and inside inline code elements.
This improves:
- feffs are now added on editor initialization (like links) and removed during cleanForSave.
- Arrow key navigation no longer skips characters at code boundaries.
- Empty inline code elements can properly hold the cursor(via mouse or arrow keys).
task: 4585706
[1]: https://github.com/odoo/odoo/commit/f792acf0bc66fb77e25bf8a0753c6a2f4284f0e8Turkish Nilvera e-invoices now accept valid invoice numbering formats beyond a single separator style. The system also checks invoice names before sending, reducing failed submissions caused by XML generation errors.
Original PR description
Before this commit:
- When sending an e-invoice through Nilvera, the invoice name used a hardcoded `.split('/')`, assuming `/` the only valid separator for fetching prefix, year and sequence.
- Invoice name was not validated, which could raise errors during XML generation
After this commit:
- The logic now supports various valid invoice name formats rather than relying only on `/` as a separator.
- Invoice name is validated before sending the e-invoice through Nilvera to ensure they comply with the GIB format, to prevent XML generation errors.
task-5117359The HR contract timeline now shows a contract line beneath the version timeline, making it easier to understand how contract details relate to each version. This improves readability for HR users reviewing employee contract history.