Friday, April 19, 2024
5 changes · master
Resolved issues and error corrections
The preparation display is now shown in the main menu when the restaurant point-of-sale module is installed. This makes the kitchen display easier for restaurant staff to find and access during daily operations.
Original PR description
In this commit: =============== The `pos_preparation_display` (preparation display) will be visible in the main menu if the `pos_restaurant` module is installed." task-3725031
The Mail app now tells the web interface which chat types support seen-status tracking. This avoids unnecessary work for chats where the feature does not apply, providing a small performance improvement without changing user workflows.
Original PR description
This info was only available to python/server code. This is now provided to JS/client code, so that it can avoid computing fields related to seen feature on threads that do not support this feature. This very slightly helps performance. https://github.com/odoo/odoo/pull/162445
This fixes an issue where cancelling an appointment too close to the allowed cancellation deadline could fail instead of showing the expected result. The appointment flow now keeps the needed customer information during cancellation, improving reliability for website bookings.
Original PR description
Fix following up : https://github.com/odoo/enterprise/pull/17141
When users open Studio from a form with multiple tabs, the same tab now stays open instead of switching back to the first one. This makes editing smoother by preserving the user's context and avoiding extra navigation.
Original PR description
currently, When enabling studio on a form view, it reset the notebook page and activate the first page instead of the currently activated page. this commit fixes the issue by adding autofocus on the activated node and therefore enabling studio on a form view, it will display the currently activated page instead of the first page. TaskID-2416755
Creating a custom stat button in Studio no longer fails because of invalid generated field names. This restores the expected ability for users to add stat buttons without encountering a naming error.
Original PR description
currently, when try to create state button, it raise error 'Custom field names cannot contain double underscores' this is happening because, we give explicitly '__' while creating field_name in commit- 3ee34f4b869998d8a6f5f29b1792bc70add9da00 and before we did not check for '__' in field_name so error does not raise. we start to check for '__' after Task-2060257. after this commit, replace '__' with '_' so now The stat button is created. Task - 2475554