Wednesday, August 21, 2024
5 changes · master
Resolved issues and error corrections
This fixes a reliability issue in the restaurant point-of-sale flow by ensuring the selected table is correctly confirmed before the system moves to the next step. It also makes returning to the floor plan more dependable, reducing failed clicks and test instability for restaurant POS users.
Original PR description
Before proceeding to any step after selecting a table, we make sure that the table-label corresponds to the selected table. Furthermore, to go back to the FloorScreen, the Plan button should be inactive before clicking it otherwise the click won't be taken into account because the moment it's click and it's active, the current screen is still the FloorScreen.
Website editors can once again add or remove tabs in the Tabs block without seeing an error. This keeps page editing smooth after a prior system change removed an older dependency used by this feature.
Original PR description
Since [1] when JQuery was removed from the backend assets, the `tab` bootstrap method is not availabe anymore on JQuery objects. Because of this, adding and removing tabs from a Tabs block fails. This commit adapts the calls to use bootstrap directly. Steps to reproduce: - Drop a Tabs block. - Select the Tabs block. - Add a new tab or remove a tab. => An error dialog was displayed. [1]: https://github.com/odoo/odoo/commit/b8fc93ea97b8870459063214d5cf468a6a3c6efe task-4126163
The HTML editor now prevents rounded and circular image shape settings from being applied at the same time. This avoids conflicting formatting behavior and makes image styling more predictable for users creating or editing content.
Original PR description
**Description of the issue/feature this PR addresses:** Commands `SHAPE_ROUNDED` and `SHAPE_CIRCLE` could be applied simultaneously, causing each command to cancel the effect of other. **Desired behavior after PR is merged:** Commands `SHAPE_ROUNDED` and `SHAPE_CIRCLE` are mutually exclusive. task-4072949
This fix prevents the tree editor from crashing when users enter invalid text in the number field of a time-based filter. Instead of causing an error, the input is safely handled so users can continue working while more robust validation is developed.
Original PR description
The within operator expects 2 values: - An integer - A period range (selection field) Those 2 values are then injected into a string that gets turned to an Expression. If some garbage is passed to the integer part, a traceback would occur. Waiting for a more robust error handling system, we can use the parseInt function that will either get rid of unwanted characters or returns a NaN value, which wouldn't crash as it would created a valid expression. task id 4086413
This fix ensures customer-facing text in the UrbanPiper point-of-sale order information popup can be translated properly. It helps businesses provide a more consistent localized experience for users working in different languages.
Original PR description
This commit fixes the props that pass strings to use `.translate` introduced in: [#174697](https://github.com/odoo/odoo/pull/174697) Community: https://github.com/odoo/odoo/pull/175568