Tuesday, October 31, 2023
2 changes · 17.0
Enhancements to existing features
The website event pages have been redesigned to look more modern and consistent across event listings, registration, agendas, exhibitors, sponsors, locations, meetings, and booth selection. The update also improves mobile usability with responsive filters, dropdown menus, and a ticket selection modal that better handles events with many ticket options.
Original PR description
This PR improves the overall design of all the views in the Frontend side of the module Event. The design was outdated and was not consistent between the different pages. List of changes: - events: cleaning of scss, filters consistency and responsive (with off-canvas). - submenu: design and responsive behavior (dropdown) - registration page : overall design and the ticket list is inside a modal, to help with cases like having a lot of tickets. To be improved, on a separate page instead of a modal. - talks and agenda: design, cleaning of scss, filters consistency and responsive (with off-canvas). - sponsor template: minor design modification - exhibitors: design, cleaning of scss, filters consistency and responsive (with off-canvas). - location: minor design modification to be consistent with others pages, but need improvement in the near future. - meet: design, cleaning of scss - booth selection: overall design task-3083658
Resolved issues and error corrections
This update fixes a critical issue in Knowledge where multiple users editing articles simultaneously could lose changes without warning. The fix ensures that when one user saves changes while another user hasn't synced their edits, the system detects this conflict and prevents data loss. Additionally, it stops unnecessary data from accumulating in article files after each save, improving system performance.
Original PR description
Collaborative html_field should all use `handle_history_divergence` during `write`, to ensure that someone cannot save content if another user saved and they did not sync their change together (diverging steps would overwrite previously saved changes without informing the user). See [1]. Without this fix, the `data-last-history-steps` attribute of the first node in the article body would grow indefinitely after each write. After this fix, only the required id is kept. [1]: https://github.com/odoo/odoo/pull/112099 When writing on articles created from a template, encode the string in `unicode` as `handle_history_divergence` does a regex on the body value and it does not work with `bytes`. task-3572449 Forward-Port-Of: odoo/enterprise#49647