| Age | Commit message (Collapse) | Author |
|---|
|
Purpose of this commit is to give description more "business oriented"
because those descriptions appears in Odoo Studio which is supposed to be used by end users, not only by developers.
Related Task ID : 37311
|
|
As this class has grown a lot some methods have been put a bit anywhere
in the file. To prepare future improvements it is easier to regroup
them a bit.
remove_accent from mail_alias is also moved to tools in order to separate
tools from business or class specific code.
|
|
You could try to check followers on a model not inheriting from mail alias
mixin. In that case current code would check followers on a void mail
alias mixin record, meaning no followers found. Instead we now
differentiate the class method from the method checking record properties.
|
|
Mesage should be message otherwise it is not displayed in the logs.
|
|
|
|
Currently check of alias security is directly embedded in mail.thread
routing method. In this commit we move this check in the mail.alias.mixin
class itself. Doing this allows models to extend or improve the behavior
depending on how inheriting models use aliases.
|
|
|
|
Remove unrestricted "read" access. To make code internally using `ir.model`
work, add a private method `_get` on `ir.model` to retrieve the record
corresponding to a model name, without access rights issue.
Change signature of method `get_authorized_fields` to make it use a model name
instead of a model id. This removes the necessity of a search on `ir.model`.
|
|
Add `base.group_system` on existing parameters:
- `auth_signup.allow_uninvited`,
- `auth_signup.reset_password`,
- `auth_signup.template_user_id`,
- `google_redirect_uri`,
- `mail.bounce.alias`,
- `mail.catchall.alias`,
- `mail.catchall.domain`.
|
|
Specifically: do not import `safe_eval` as `eval`, keep it explicit instead.
|
|
|
|
|
|
When only a message argument is given to the crash manager, the popup display
"Error while validating constarint" and "None" with the warning message
which does not make any sense for the common user.
|
|
|
|
|
|
Do not restrict followers-based alias to members of non public channels.
Otherwise you may have issues defining a public mailing list with a
subscription step. People still wouldn't be able to post on a public
channel using a restricted alias.
|
|
Now that channels can follow documents, restricted aliases are a bit too
restricted. We consider that followers-based aliases accept emails from
the direct followers (message_partner_ids) or member of non public
channels (message_channel_ids, filetered public field). This way we avoid
having public channels added by mistake, leading to information leak.
|
|
Missing spaces, typos, rephrase unclear text
Courtesy of Eric Geens
|
|
otherwise it is not correctly computed on new records inheriting
from mail.alias class.
|
|
|
|
|
