CB Activity - auto update and duplicated items

Hello, I can't figure it out why activity stream auto update duplicates items. How to prevent this?
best regards,
r.

It's timestamp based. Regardless it checks for the activity id in the rows data attributes to see if it already exists to determine if it needs to be ignored or not. Are you sure you don't just have duplicate activity? Seams to all be working ok in my tests.

I don't have duplicated activities for sure. I checked once more. When auto update is off, every item is displayed just once.

I'm think that problem is with Auto Actions. I see that you've made some changes lately so I used "Reinstall System Actions" and unpublished all my Actions and turned on auto update feature.

All old activities are displayed just once.

New (and old one with new comments) are doubled after comment is added - I see the (I think) original one, and additional with "log?"/notification. In original item, comments are displayed twice and I don't see menu in top right corner of entry.
In doubled items I see comments displayed once, with menu in right top corner.

If you will have couple of minutes I can add a user to front end for you.

Everything looks a little better that some time ago. Lets look at the screenshots:

1. after comment is added by test user


notification is displayed, which is cool but if, it is possible, it would be great if source post could be displayed at the bottom at once with this notification and with new comment under the post (everything without refreshing site).

2. after refreshing a site


source post is under notification, there is the new comment, and I like it (but why only after refreshing site? ;( )
and there are two the same posts - with notification and without. In this without notification comments are doubled.

That's working as intended. You have comment activity enabled. It generates an activity entry and embeds the activity that was commented on inside of it. You'll see this same behavior with Facebook time to time as well as it uses replication. I don't really have a solution for it at this time beyond maybe adding a condition so it won't create the activity if the comment was made too close to the date of the activity being commented on.

Notifications should not be disabled anywhere except on notifications. If it's displaying then the asset is probably set wrong for that notification. Example asset for a notification as follows.

Wrong: notification.42
Correct: notification.42.comment.1

The "notification.USER_ID" is always a prefix to whatever the actual asset is. This won't really be an issue once I've rewritten the notification API as they'll have separate storage.

previously assets were like notification.451.comment.
now is like activity.193.comment
I think I don't understand this part well... let's leave it for a while.

So... Posts must replicate right? I tried to delete old ones wit AA but those tries was probably a cause of previous problems. If with not AA I have a hope you will find a way to prevent this in situation when commented is some of recent posts.

But what about doubled comments in original post?

The double comment looks like a bug and was able to confirm.

forge.joomlapolis.com/issues/6847

As for the duplicate activity it's not a bug and working exactly as it's supposed to. There's not really a way to improve that any further, but it's still on my mind for future releases to see if I can without destroying SQL performance.