[MAGNOLIA-573] customizable change notification Created: 12/Oct/05  Updated: 04/Nov/15  Resolved: 04/Nov/15

Status: Closed
Project: Magnolia
Component/s: admininterface, core
Affects Version/s: None
Fix Version/s: None

Type: New Feature Priority: Minor
Reporter: Boris Kraft Assignee: Philipp Bärfuss
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MAGNOLIA-574 User preferences Closed
is related to MGNLFORUM-64 Notification Closed
Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

Request to add change notification mechanisms for users

Users should be able to request change notifications for any page or tree they like, and be able to customize the delivery time - common are things like once a week, once per day or on every change (unlikely). Notification format should be email. RSS would also be nice.

The issues depends on scheduling capabilities (they would be there once workflow is integrated) and user preferences.



 Comments   
Comment by Boris Kraft [ 12/Oct/05 ]

The email sent should contain links to all pages that changed in the requested period (e.g. changed last week). Thus it is easy to keep up to date with new information.

Comment by Philipp Bracher [ 17/May/06 ]

the metatemplates are poviding a similar facility

Comment by Jan Haderka [ 04/Sep/08 ]

Observation module is already able to send emails. It should be trivial to write more event listeners to for example store the infos from events in data module and make weekly digests or rss from there.

Comment by Michael Mühlebach [ 04/Nov/15 ]

Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes.
Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog for some time now with very little movement.
I'm going to close this to set expectations so the issue doesn't stay open for years with few updates. If the issue is still relevant please feel free to reopen it or create a new issue.

Generated at Mon Feb 12 03:18:46 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.