Display the default name (the one displayed in the kanban view) for followers replacing the False value for "other address" partners, this way the user won't get confused, furthermore, this fix won't require the name to be mandatory for this type of contacts. Task-2514244 closes odoo/odoo#70391 X-original-commit: 4c1271738daa039e79a11646fef3f4264e4d96d2 Signed-off-by: Thibault Delavallee (tde) <tde@openerp.com>
task-2391334 closes odoo/odoo#62956 Signed-off-by: Alexandre Kühn (aku) <aku@odoo.com>
PURPOSE Currently it does two RPCs to refresh followers on thread: 1) To get follower ids 2) To get followers detail SPECIFICATION While refreshing followers on the thread, perform only one RPC call. LINKS Task-2243180 PR https://github.com/odoo/odoo/pull/54437 closes odoo/odoo#55989 X-original-commit: 1fd445fb55810b97ed7a6dfe694e471891c6a3bc Signed-off-by: Alexandre Kühn (aku) <aku@odoo.com>
Improve mock server: - add support for mocked `fetch` - add support for `active_test` - add support for x2m `in` in domains - add support for default values computed from a function - implement a more natural "next id" compute - allow initial data without ids - ensure write and x2m commands integrity - improve bad data/bad commands error messages - always warn for failing RPC, not only in debug mode - fix all existing tests that had inconsistency data Other changes done in mail (or dependents) that are not just related to tests: - remove `direct_partner` from formatter result ->`correspondent` can be computed from other keys, especially `members` - fix `livechat_visitor` convertData -> only process if there is value - add `current_partner` and `current_user_id` as `init_messaging` result -> easier to mock than session - remove usage of `need_moderation` -> that was just a search indirection to `moderation_status` - adapt `partner_id` -> `res_partner_id` key in `_notification_format` -> to be consistent with field name - add name in result of `mail_partner_format` -> sometimes display_name is not the same - remove usage of `is_moderator` -> that was just an indirection to `moderation_channel_ids` Enterprise counterpart: https://github.com/odoo/enterprise/pull/11523 task-2287171 closes odoo/odoo#55854 X-original-commit: 7ba3fecb3377a720d1eb70e7515a0c45da73836d Related: odoo/enterprise#12391 Signed-off-by: Sébastien Theys (seb) <seb@odoo.com>
The logs should all be in the same language, s.t. one does not need to understand multiple languages when browsing/reading the server logs. closes odoo/odoo#53984 Related: odoo/enterprise#11615 Signed-off-by: Victor Feyens (vfe) <vfe@odoo.com>
The superuser is already used to check whether modules are installed with demo data and create the notification. It was not used for accessing the admin partner though, so in the case where a user is logging in with the password "admin" and with no access to `partner_admin` it's going to blow up the login process despite no reason to. Admittedly this is somewhat difficult to achieve in "standard" odoo, it was only discovered because 2FA (odoo/odoo#33928) can reach this point without having a "proper" session set up as that set up is delayed until after the MFA step has succeeded while `_admin_password_warn` is part of the redirection flow from the initial login (user/password input). closes odoo/odoo#53244 X-original-commit: d18d226084a8b47f2858d8a271886115b29d7b2f Signed-off-by: Xavier Morel (xmo) <xmo@odoo.com>
Using a few regex like \((_\(.*%s.*)(\) % )([\w\[\]][\w .\[\]\(\)'"]*)\) ($1, $3)) Old syntax is still compatible but starts the migration to the new syntax that catches error.
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>
The route is no longer used but was still present in the code. Processing email should be the job of the fetchmail server and they should not be injected directly from outside (even if emails are unauthenticated by design, mail servers may still have some say in the process). Courtesy of Alexandre Díaz closes odoo/odoo#50084 X-original-commit: ab70afb3963b0952e938ab39ef3dcb47ecc01f61 Signed-off-by: Thibault Delavallee (tde) <tde@openerp.com>
The point is to warn admins of production and public-facing databases. However it is not necessary to nag users of demo databases, even when connecting non-locally (e.g. on runbot). Updates #37580 (manual) forward-port of #48689 closes odoo/odoo#48691 Signed-off-by: Olivier Dony (odo) <odo@openerp.com>