Daily updates from Odoo
Monday, February 10, 2020
5 changes · master
Enhancements to existing features
This update enhances the website editor's media dialog with better image optimization, filtering, and preview behavior. It helps content editors manage and adjust images and videos more smoothly when building pages, though some storage and cleanup work is still in progress.
Original PR description
@qsm-odoo when you've got an hour or three, this is the current state of the media dialog / image optimization and filter. There is still quite a bit of work to do in particular in terms of saving images in DB and deleting old ones. If there is a `FIXME` comment, it means I plan to rewrite a good bit of the code there, so I'm less looking for comments on the current state of the code and more for suggestions on ways to approach the problem. Thank you for your time!
This update corrects an internal file reference in Odoo's base language component. It helps ensure the system points to the intended file, reducing the chance of incorrect behavior in related language functionality.
Original PR description
Follow-up on https://github.com/odoo/odoo/commit/22f02af6bf002324ebafc38d4eefeda60063247a Use the correct reference for the file. Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Website editors can now apply a parallax background effect to any section that uses a background image, instead of being limited to specific snippets. This gives teams more design flexibility while keeping the older parallax snippet available for existing layouts.
Original PR description
* web_editor See sub-commits for details. task-34648
Empty live chat sessions are no longer shown in counts or session views, keeping reports focused on conversations where visitors actually sent messages. Old empty sessions are cleaned automatically, reducing database clutter and avoiding misleading live chat metrics.
Original PR description
Purpose ======= Whenever a visitor start a livechat session but finally close the session without sending any messages, the livechat session is empty and stay in DB. Livechat session counter counts…
Purpose
=======
Whenever a visitor start a livechat session but finally close the session
without sending any messages, the livechat session is empty and stay in DB.
Livechat session counter counts all the sessions (with and without message)
but when opening the sessions tree view, the view is filtered by default on
session with messages. There is no reason to keep the empty sessions as it
does not give any information (except "the visitor hesitated to start
livechat and finally did not' which is quite useless info)
The goal is to keep only sessions with messages.
When the visitor is closing the livechat window, if the session is empty,
the session should be deleted. But what happens if a visitor start a livechat
session, send no message and just leave the website without closing the
livechat window ? --> empty live chat session will remains in database.
Specifications
==============
- Add cron to clean the empty livechat session everyday (older that one day)
- Apply 'with messages' domain on session count in the livechat channel view
- Apply 'with messages' domain on session count in the lead view
- Apply 'with messages' domain on livechat session view
- Remove With message filter
- Remove Without message filter
- If send message on a deleted session :
just tell the visitor that operator is not available anymore
AND delete livechat session cookie (as he waited 1 day to send a message)
Empty sessions becomes invisible : not possible for users to see empty session
(in count or in views) and cron is cleaning empty sessions every day.
Task ID: 2146962The web test suite has been updated to use browser-native event handling, making automated tests closer to real user behavior. This helps improve confidence in the reliability of web and Studio features without changing day-to-day functionality for users.