[notifications] use non-fixed message-id for EntityUpdatedNotificationView

More than one of those can be sent for a given entity, so they shouldn't all have the same message-id. Closes #4962712.

authorJulien Cristau <julien.cristau@logilab.fr>
changesetb2f7f03f10b3
branchdefault
phasepublic
hiddenno
parent revision#0e61be7bff10 [server/test] kill remaining 3.19 deprecation warnings in undo tests
child revision#5c2a4a0a8dbd [entities] return the entity itself from notification_references if the view uses a random message-id
files modified by this revision
sobjects/notification.py
# HG changeset patch
# User Julien Cristau <julien.cristau@logilab.fr>
# Date 1424172958 -3600
# Tue Feb 17 12:35:58 2015 +0100
# Node ID b2f7f03f10b30b754a2943afbeb33ef90401c877
# Parent 0e61be7bff102390ac3f52b8e470c716711caa82
[notifications] use non-fixed message-id for EntityUpdatedNotificationView

More than one of those can be sent for a given entity, so they shouldn't
all have the same message-id. Closes #4962712.

diff --git a/sobjects/notification.py b/sobjects/notification.py
@@ -264,11 +264,11 @@
1      * set a content attribute to define the content of the email (unless you
2        override call)
3      """
4      __abstract__ = True
5      __regid__ = 'notif_entity_updated'
6 -    msgid_timestamp = False
7 +    msgid_timestamp = True
8      message = _('updated')
9      no_detailed_change_attrs = ()
10      content = """
11  Properties have been updated by %(user)s:
12