Tuesday, June 24, 2025
4 changes · saas-18.1
Resolved issues and error corrections
This fix ensures chart trendline settings are correctly carried from Odoo charts into spreadsheets. Users should no longer see incorrect or missing trendline options when working with line or scatter charts.
Original PR description
This commit fixes a UI bug in chart trendlines by ensuring 'AxisType' is properly passed from Odoo charts to the spreadsheet. Task: [4743602](https://www.odoo.com/odoo/2328/tasks/4743602) --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The POSBox homepage now immediately shows the option to disconnect from the current database after a connection is made, without requiring a page reload. The disconnect flow also shows the loading indicator sooner, making the process feel more responsive for users.
Original PR description
We store the server url in `store.base`, which was made unreactive by using owl `toRaw` method. This made the `disconnect from current` button not being displayed right after connecting to a database, without reloading the page. We removed this call to fix this behavior. We also called `waitRestart` before calling the disconnect method from the back end, in order to remove the delay before displaying the loader.
This fix ensures spreadsheet chart trendlines receive the correct axis information when charts are created or edited. Business users get more accurate chart visuals, reducing confusion when reviewing spreadsheet reports and dashboards.
Original PR description
This commit resolves a UI bug in chart trendlines by ensuring AxisType is properly passed from the web client to Odoo charts. Task: [4743602](https://www.odoo.com/odoo/2328/tasks/4743602)
The YouTube posting form now keeps the selected video category when a post is published. This prevents category information from being accidentally lost and helps ensure uploaded videos are saved with the intended classification.
Original PR description
If not specified, the field `youtube_video_category_id` was treated as readonly by default. This commit explicitly sets readonly: false, ensuring that the field is editable. This prevents the value from being lost during posting, as it will now be correctly written to the database. Part of PR: #83571 opw-4646432