Saturday, February 8, 2025
3 changes · saas-17.4
Miscellaneous changes
If a user has an appointment in an appointment type they may not read. They should still be able to sync it to their calendar. Related to this fix: e52b13c9fc9cb309351f527bfbe961fcb0fb961e task-4526059 Forward-Port-Of: odoo/enterprise#78849
Original PR description
If a user has an appointment in an appointment type they may not read. They should still be able to sync it to their calendar. Related to this fix: e52b13c9fc9cb309351f527bfbe961fcb0fb961e task-4526059 Forward-Port-Of: odoo/enterprise#78849
In [1] the `params` section was refactored, but removing the `]` was missed. This caused an error, always returning "No encontrado". [1] https://github.com/odoo/enterprise/commit/14c1b2f8b36ade09be021d2ae202da19f88c0b78 Forward-Port-Of: odoo/enterprise#78891
Original PR description
In [1] the `params` section was refactored, but removing the `]` was missed. This caused an error, always returning "No encontrado". [1] https://github.com/odoo/enterprise/commit/14c1b2f8b36ade09be021d2ae202da19f88c0b78 Forward-Port-Of: odoo/enterprise#78891
During testing of the "new" Chrome's headless mode (by default since version 128), a concurrency issue arise at the end of those tours: a last request to the server is actually sent during the unload of the view (cf. save). This request actually reach the server even if Chrome is already closed and results into a SQl constraint error. Indeed, the (very basic) form views created for those tours are based on the "res.partner" model and only display the "name" field. This field isn't marked as "
Original PR description
During testing of the "new" Chrome's headless mode (by default since version 128), a concurrency issue arise at the end of those tours: a last request to the server is actually sent during the unload of the view (cf. save). This request actually reach the server even if Chrome is already closed and results into a SQl constraint error. Indeed, the (very basic) form views created for those tours are based on the "res.partner" model and only display the "name" field. This field isn't marked as "required" neither in the model, nor the view BUT has a SQL constraint attached to it... which makes it implicitly "required". This commit fixes it by properly marking them as such in the arch to let the client-side validation prevent the ultimate "save" request made during the unload. Forward-Port-Of: odoo/enterprise#78810