Tuesday, April 15, 2025
3 changes · saas-18.2
Resolved issues and error corrections
Fixed an issue that could cause errors when selling event tickets through the point of sale. The change ensures sale date checks use the event information correctly, helping staff complete event sales without interruption.
Original PR description
Before this commit, the event's `end_sale_datetime` and `start_sale_datetime` fields were being deserialized to check whether the event could be sold. However, these fields were already in `datetime` format. opw-4719436 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The web client now removes a startup event listener automatically after it runs once. This is a small internal fix that helps avoid unnecessary repeated listener activity and keeps session startup handling tidy.
Original PR description
Since the web_client is started only once, we can safely add the `once`[1] parameter to the `WEB_CLIENT_READY` event listener. [1]: https://developer.mozilla.org/en-US/docs/Web/API/EventTarget/addEventListener#once --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fixes an issue where spreadsheet cell threads could fail when no related record existed. The change helps avoid errors in affected spreadsheet views and keeps the user experience stable in edge cases.
Original PR description
After https://github.com/odoo/odoo/pull/195203/commits/b9adcae95d406f8960a24fadb586d5e362e8a2f9, we were getting error in _compute_display_name, as self._get_spreadsheet_record() sometimes returns False. This commit fixes such cases. [runbot_error 115365](https://runbot.odoo.com/odoo/error/115365)