Mail holds a "Pay Now" notification template holding notably customized links to portal for records like sale orders or invoices. It allow to give a more personalized button than a plain simple "View document" link. Currently frontend / backend links are not always correctly computed in this template. This commit fixes that behavior. Task ID-2513724 COM PR #69607 ENT PR odoo/enterprise#17849 closes odoo/odoo#69714 X-original-commit: odoo/odoo@a55f125f5420797a9378925da5626e43d002b9b0 Related: odoo/enterprise#17889 Signed-off-by: Thibault Delavallee (tde) <tde@openerp.com>
Actually, We don't want to distract the admin with an unnecessary notification on General Channel. The main focus should be on odoobot's tour, not on the general channel's welcome message. And it is also not a good idea to remove the general channel as it would reduce the discoverability of the feature. So, we are marking the first message as read for at least admin user. therefore admin can not distract over unnecessary welcome notification and focus more on the rest of the functionality. Task : 2442023 closes odoo/odoo#65440 Signed-off-by: Sébastien Theys (seb) <seb@odoo.com>
task-2282334 closes odoo/odoo#56584 Signed-off-by: Alexandre Kühn (aku) <aku@odoo.com>
Some demo messages have a grey background because they have the subtype_id set to NULL. The subtype should be `mail.mt_comment`, like other messages inside the general channel. task-2278438 closes odoo/odoo#54261 X-original-commit: 9be1079cc62699d119b9c2acc6282bd72f71f9af Signed-off-by: Sébastien Theys (seb) <seb@odoo.com>
This commit is a significant rewriting of client-side discuss, chatter, chat window, and messaging menu using OWL. The behavior should be broadly the same, with some slight functional changes here and there. From a technical standpoint, the code of messaging is mainly organized in 2 main groups of modules: - models, which are logical entities that depict the client-side state of messaging as a whole. - components, which are in charge of displaying information from models. This refactoring also introduces new JS guidelines regarding folder structure (/static) and naming rules for JS modules. Community PR: https://github.com/odoo/odoo/pull/39023 Enterprise PR: https://github.com/odoo/enterprise/pull/6249 Task-1914207 This PR is a collaborative work by Alexandre, Julien, Sébastien and Xavier, with the precious help of Lucas to speed it up towards the end. closes odoo/odoo#39023 Related: odoo/enterprise#6249 Signed-off-by: Alexandre Kühn (aku) <aku@odoo.com> Co-authored-by: Alexandre Kühn <aku@odoo.com> Co-authored-by: Julien Giannone <jgi@odoo.com> Co-authored-by: Lucas Perais <lpe@odoo.com> Co-authored-by: Sébastien Theys <seb@odoo.com> Co-authored-by: Xavier Dubuc <xdu@odoo.com>
Task ID 2265592 PR #
Before this commit, when starting a new database with demo data, the default channel `#general` had no messages initially. The demo data defines default messages in this channel, but were incorrectly linked to this channel, resulting in this channel containing no messages initially. The messages did not define `channel_ids`, so it was considered empty. This field is essential for displaying the message in channel, so by being omitted these messages are not properly linked to channels. This commit fixes the issue by correctly linked this demo messages to this demo channel, so that `#general` now contains some messages initially. This commit also removes unused context `mail_notify_noemail`. Task-Id 2186300 closes odoo/odoo#49539 Signed-off-by: Alexandre Kühn (aku) <aku@odoo.com>
For some specific report (i.e account followup report) the mail_message sent will contains no company informations because it will be sent on the partner context, so when generating the template the logo will be retrieved from the route /logo.png?company=False which yield back the odoo company logo. Adding a default 0 allow to retrieve the company logo for the current user opw-2232184 closes odoo/odoo#49787 X-original-commit: eea99fe1e00eb2dbd2bbeaca3e2f09845b426267 Signed-off-by: Nicolas Martinelli (nim) <nim@odoo.com>
PURPOSE When incoming emails bounce due to alias security bounce email is quite generic. Purpose of this task is to ease its customization and update. SPECIFICATIONS In order to improve the flexibility of alias, add a customizable html field on the alias model. This html content will be send as bounce email core content in case of bounced/unauthorized mail received for this alias, Obviously it has no effect on 'everyone' security setting as no email will bounce due to that issue. If it is not set a default generic mail will be send depending on security setting. It allows to keep void html fields when no specific bounce content is required In HR, an old template allowing some light customization for employee based security option is removed as it is completely replaced by the new feature. Also add references message-id of the mail received to the answer so that threads are correctly set. LINKS Task ID 2126509
Currently, 'Exception' ativity type is visible in dropdown list of schedule activity. It is used by the system to generate warning activities on records. It is not meant to be used by the user when scheduling activities manually. By, giving active=false on mail.mail_activity_data_warning, we can hide 'Exception' activity type in dropdown list for user but available for the system to generate warning. task-2168569 closes odoo/odoo#43549 Signed-off-by: Alexandre Kühn (aku) <aku@odoo.com>