Updating Event no longer hits Activity Stream?
By Andy on Thursday, 10 November 2016
Posted in Technical Issues
Likes 0
Views 221
Votes 0
I've noticed since ES2 when an event is updated, it no longer hits the activity stream.

Was that an intentional change?

I did think it was very good to have it showing on the stream and would like it back if possible! Only downside often encountered was often people would make several edits within a minute or two to get it looking how they wanted it and it would appear multiple times on the stream within that short timeframe.
Hi Andy,
Yes the event update stream is no longer available in ES2.0.
The reason we removed this is as you have stated regarding the disadvantage of having that stream. Multiple update streams can be generated, so much so that it can make it look like some sort of "spam", causing difficulty for users to look at other stream items.
Raymond
·
Thursday, 10 November 2016 12:35
·
0 Likes
·
0 Votes
·
0 Comments
·
OK understood. That does explain it. Thanks!
Andy
·
Thursday, 10 November 2016 20:57
·
0 Likes
·
0 Votes
·
0 Comments
·
Are there any reasons for having these kind of stream details being displayed on the stream eh?
Mark
·
Thursday, 10 November 2016 21:26
·
0 Likes
·
0 Votes
·
0 Comments
·
Only to draw attention to the event and the fact something has changed.. might be new important details about the event for example... but I did experience that issue all the time of multiple stream instances when event authors were updating, then refining their events and saving several times.... so I can understand why it's been taken away.
Andy
·
Thursday, 10 November 2016 23:44
·
0 Likes
·
0 Votes
·
0 Comments
·
I see, yes and the reason that we took it out is simply because when we were testing this on our test site, people who update events are somewhat spamming the stream with tons of similar activities and it really doesn't make sense to display these activities.
Mark
·
Thursday, 10 November 2016 23:46
·
0 Likes
·
0 Votes
·
0 Comments
·
Yes not sure if it's technically possible but the ideal best of both worlds solution would be to bring it back but only post to stream if the same hadn't already been posted to the stream within the past 30 minutes (or whatever time period would seem sensible)
Andy
·
Friday, 11 November 2016 00:03
·
0 Likes
·
0 Votes
·
0 Comments
·
Anything and everything is possible but the question would most certainly be "at what cost?" If we are going to add in another 20 lines of SQL queries or run additional 5 queries just for this, I don't think it makes sense to have this at all.
Mark
·
Friday, 11 November 2016 00:19
·
0 Likes
·
0 Votes
·
0 Comments
·
Sure thing. Understood. You're the expert - Thanks as always for our EasySocial miracle!
Andy
·
Friday, 11 November 2016 00:22
·
0 Likes
·
0 Votes
·
0 Comments
·
You are most welcome Andy
Mark
·
Friday, 11 November 2016 00:26
·
0 Likes
·
0 Votes
·
0 Comments
·
View Full Post