Odoo Changelog — 2025-12-06

Saturday, December 6, 2025

2 changes · saas-18.2

Bug Fixes(2)

Resolved issues and error corrections

[FIX] hw_drivers: fix flush interval for server logger

Coresaas-18.2hw_drivers

This fix restores a shorter log flush interval for Odoo hardware drivers. It helps prevent the server logging queue from filling up, reducing the risk of delayed or blocked hardware-related logs.

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

#hardware#logging#stability

[FIX] l10n_es_edi_verifactu: add read access rights

PR #238914

Coresaas-18.2l10n_es_edi_verifactu

Users with read-only Accounting access can now open invoices when the Spain VeriFactu module is installed. This prevents an access error and ensures all accounting users can view the invoices they are permitted to see.

Original PR description

In the Accounting app (with the *Spain - Veri\*factu* module installed), when a user who is **not** part of the *Accounting / Invoicing* (`account.group_account_invoice`) group would be blocked by an Access Error when trying to open an invoice. Among the Accounting groups, only  *Accounting / Read-only* does not inherit from *Accounting / Invoicing*, which means that only the users in *Accounting / Read-only* could not access the invoices.

By granting read rights to both *Accounting / Invoicing* and *Accounting / Read-only*, we ensure that any user belonging to an Accounting group can see the invoices from the Veri\*factu module.

### Steps to reproduce:
1. Install *Accounting* (`accountant`) and *Spain - Veri\*Factu* (`l10n_es_edi_verifactu`).
2. Go to Settings > Users & Companies > Users and select a user.
3. In the *Access Rights* tab, set the user's *Accounting* access right to *"Read-only"*.
4. Log out, then log back in as the user selected in step 2.
5. Go to Accounting > Customers > Invoices and select any invoice.
6. An access error pops up.

opw-5343391

Forward-Port-Of: odoo/odoo#238749
Forward-Port-Of: odoo/odoo#238291

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

In the Accounting app (with the *Spain - Veri\*factu* module installed), when a user who is **not** part of the *Accounting / Invoicing* (`account.group_account_invoice`) group would be blocked by an Access Error when trying to open an invoice. Among the Accounting groups, only *Accounting / Read-only* does not inherit from *Accounting / Invoicing*, which means that only the users in *Accounting / Read-only* could not access the invoices. By granting read rights to both *Accounting / Invoicing* and *Accounting / Read-only*, we ensure that any user belonging to an Accounting group can see the invoices from the Veri\*factu module. ### Steps to reproduce: 1. Install *Accounting* (`accountant`) and *Spain - Veri\*Factu* (`l10n_es_edi_verifactu`). 2. Go to Settings > Users & Companies > Users and select a user. 3. In the *Access Rights* tab, set the user's *Accounting* access right to *"Read-only"*. 4. Log out, then log back in as the user selected in step 2. 5. Go to Accounting > Customers > Invoices and select any invoice. 6. An access error pops up. opw-5343391 Forward-Port-Of: odoo/odoo#238749 Forward-Port-Of: odoo/odoo#238291