Tuesday, December 20, 2022
5 changes · master
Resolved issues and error corrections
Opening calendar provider settings in Studio no longer triggers a crash. The change replaces a fragile click handler with a dedicated widget, making configuration forms more reliable for users customizing their calendar setup.
Original PR description
Remove the t-on-click used in form view as it crashes when opened with studio. Instead we use a dedicated `<widget/>` task-3090960
Payment screens now correctly show the currency symbol after a recent interface change caused it to disappear in grouped views. This helps users quickly understand payment amounts and currencies without confusion.
Original PR description
With recent JS change on "group" the currency symbol was missing. By adding the currency_id field invisible in the arch the problem is solved. Task-id:3089285 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The mass mailing editor no longer shows a duplicate option for changing button background colors. This reduces confusion for users by keeping button color customization in the intended place only.
Original PR description
Commit [1] introduced a "custom" type of button as the only type of button whose background color we are allowed to change. But the option to change any button's background color exists in mass_mailing so we end up with the same option in two different places. This removes that previously existing default option. [1]: https://github.com/odoo/odoo/commit/a010c91b5ee119cf54ed1a68a6ea06b2bc5f3978 task-3096806 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The appointment invite form now avoids a crash when opened through Studio by replacing the problematic click handling with a dedicated widget. The update also improves invite link behavior and presentation, including support for links without a specific appointment type.
Original PR description
Remove the t-on-click used in form view as it crashes when opened with studio. Instead we use a dedicated `<widget/>` task-3090960
This fixes a crash that could occur in Studio when displaying formatted social post content. The field now uses the correct read-only behavior, improving reliability without changing how users edit or publish posts.
Original PR description
There's no reason to inherit from TextField here as the PostFormatterField only t-out a formatted value, and does not allow edition. Worse, inheriting from TextField produces a crash in studio. TextField expects to have the ref to its textarea, but that extension does not set that ref. This has been detected by the clickbot test.