Notification sent for attached files even when they are not changed [#1282212]

If one or more files are attached to a node (e.g. a blog) and the node is updated, one notification is sent for the node update and one notification per attachment is sent even if the attachments themselves are not changed.

The best workaround is to uncheck "Attachment notifications" on admin/settings/file/attach page but this is deficient in that notification for a blog with an attachment has no indication that a file was uploaded (or maybe updated)

The desired behavior, to be explicit, would be when a node is updated, check if any of the attached files are new files to decide if a notification is warranted.

Comments

Comment #1

johanneshahn commented 5 December 2011 at 19:30

Status:

Active

» Postponed (maintainer needs more info)

hi suleyman,
i cant see any checkbox "Attachment notifications" under "admin/settings/file/attach"
is this fileframework version 6.x-1.x-dev ?

Comment #2

jvieille commented 6 December 2011 at 08:28

I think that this FF feature is misunderstood or misused

FF gives the choice by configuration of sending a notification for changes in attached nodes or not when they are affected by the attaching node.
The notification normal behavior would be to fire as many notifications for the attaching node and all attached files when the attaching node update changes something in the attached files. For example, if you change a taxonomy term at the attaching node level, the attached files might get updated as well, firing as many notifications for the same thing.

FF is smart enough for offering the possibility of only notifying once.

This particular case "The desired behavior, to be explicit, would be when a node is updated, check if any of the attached files are new files to decide if a notification is warranted." is correctly handled: if a node is updated, a notification is always sent for the node. The notification for the updated files occurs when they are updated as well.