Notification Fixes required in ES 1.4
By Sunny on Wednesday, 10 June 2015
Posted in General Issues
Replies 13
Likes 0
Views 1.6K
Votes 0
Hi Mark,

There are a few bugs in the stream notification system in the current ES series (Possibly language or maybe usage of same language string multiple times), which i would like to bring to your notice, hoping they would be ironed out in ES 1.4.

these can be replicated on your ES demo as well.

1) Updating Self Status
If i update my own status on my profile page --> the dashboard stream header says "darius 1 minute ago"
Ideally the header should say "darius updated status -1 minute ago"

2) Post an status update on some else's profile --> the dashboard stream header says "darius>yasser 1 minute ago"
Ideally the stream header should say "darius commented on yasser's page -1 minute ago"

(The above two have common language string (APP_USER_STORY_STREAM_SHARED_LINK), i.e if we define this string in language override with 'Updated status' , then currently the stream header for above two examples would be:
a) darius updated status 1 minute ago
b) darius updated status>yasser 1 minute ago

So ideally "Status Update Self" and "Status Update on other users" should have their own individual language string.


2) Commenting, liking, reposting on someone else's old status, or old shared link, or old photo
If we do the above, the old post jumps onto the top of all recent posts, it seems odd on the main dashboard stream page.

Notice the current time stamps:
1st Stream header: mark shared a file on the site 8 months ago
2nd stream header: darius yasser 15 seconds ago
3rd stream item: sam 9 months ago
4th stream item: ridhwan shared a link 9 months ago
5th stream item: darius 30 seconds ago

To a normal visitor visiting dashboard the stream looks stale ( i.e he is seeing 8-9 month old posts in the most recent updates)

An ideal situation would be that the stream just display the activity
1st Stream Header: darius commented on marks sahred file - 5 seconds ago
2nd stream item: darius commented on yasser's page - 15 seonds ago
3rd stream item: darius commented on sam's status 40 seconds ago
4th stream item: darius likes ridhwan's status 3 minutes ago
and so on
nice stream with descending time stamps

This happens throughout profile, group & events.

regards
Sunny
Subscribe.

I think there's a few notification tweaks that they are working on; we hit one with Loading more comments. Would be nice to compile any other oddities.
Austin Ramsdale
·
Thursday, 11 June 2015 04:50
·
0 Likes
·
0 Votes
·
0 Comments
·
Hello Sunny,

I am sorry for the delay of this reply.

Thank you for your kind input. I will add the ticket to our developers regarding on this issue and hopefully they will consider to change the notification wording in the future release of easysocial.
Ezrul Fazwan
·
Friday, 12 June 2015 12:27
·
0 Likes
·
0 Votes
·
0 Comments
·
Yes, we came across the same/similar issues. Mark is aware of some...

Looking forward to 1.4 and with these fixes included it would be even better.
Andrew
·
Wednesday, 08 July 2015 18:05
·
0 Likes
·
0 Votes
·
0 Comments
·
I'll disagree with the "darius commented on yasser's page -1 minute ago" considering that when talking about the past, we do not use negative values. However I do like the points mentioned about stream age ordering and how ancient posts can be higher than new ones.
Josh Lewis
·
Thursday, 09 July 2015 01:51
·
0 Likes
·
0 Votes
·
0 Comments
·
@josh sorry i think the point was not correctly typed by me, there are no negative values the - is a - (dash)

Secondly there is no problem in ancient posts being higher, if there is recent comment on that stream item, the only issue is that the title (heading) currently just re-posts the old title i.e the time & action of the old post, instead of the latest action. This results in an improper ageing stream. Ideally the stream heading should show the latest action which was taken on that item, with the corresponding timestamp.

regards
Sunny
·
Thursday, 09 July 2015 13:48
·
0 Likes
·
0 Votes
·
0 Comments
·
One more point/request/advise i have after posting my previous reply @mentions, #hastags should be made available throughout the components of ES/ED/EB commenting.
Sunny
·
Thursday, 09 July 2015 13:50
·
0 Likes
·
0 Votes
·
0 Comments
·
Hello Guys,

Thanks for the heads up. Let's hope everything can be done with the release of easysocial 1.4 anytime soon.
Ezrul Fazwan
·
Thursday, 09 July 2015 16:16
·
0 Likes
·
0 Votes
·
0 Comments
·
We Hope and pray as well
Sunny
·
Thursday, 09 July 2015 17:35
·
0 Likes
·
0 Votes
·
0 Comments
·
Thanks Sunny.
Ezrul Fazwan
·
Friday, 10 July 2015 12:07
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi Ezrul,

Also just noticed that #hastags mentioned in comments or on other members rofiles do not consolidate or auto populate, i.e if enter an existing #hastag in a comment to a stream item, it does not show the result (Although it does populate correctly if i type the same hashtag in my profile page).

Is this default behaviour or there is a setting whereby hashtags in comments can be also entered. (In your demo #tags works all across)

Sorry my subscription For ES has just expired, so posting in an open existing thread.
regards
Sunny
·
Saturday, 11 July 2015 21:31
·
0 Likes
·
0 Votes
·
0 Comments
·
Hello Sunny,

I am sorry for the delayed response of this.

I've tested it in my local and indeed the hashtag that are being mentioned inside the hashtag is not being populated correctly throughout the stream and the comment itself. I will create the ticket in our codebase so our developer can do something about it and hopefully the fix will be included in the next release of easysocial.
Ezrul Fazwan
·
Tuesday, 14 July 2015 12:54
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi Ezrul,

Thanks for confirming, unfortunately my subscription is expired. And i'm delaying my renewal so that my next renewal covers ES2.0 release (its cheeky, but i'm trying to elongate my limited budget).

So if you would be kind enough to tell me where the corrections have to be done, so that i can do it manually.

regards
Sunny
·
Tuesday, 14 July 2015 18:14
·
0 Likes
·
0 Votes
·
0 Comments
·
Hello Sunny,

I am sorry for the delay of this reply.

The fix is not made available yet and I will share it to you once the fix is available. Thank you for your kind understanding.
Ezrul Fazwan
·
Wednesday, 15 July 2015 13:47
·
0 Likes
·
0 Votes
·
0 Comments
·
View Full Post