I cloned the "activity when a node is created (not in a group)" to "activity when a Gallery Image node is created (not in a group)" and restricted it to just gallery images and set the "activity when a Gallery Image node is created (not in a group)" rule to not work with gallery images.

The rule works but after setting up the grouping similar messages I see that it works for the active user and not for the acting user's relationships. For acting user's relationships it simply lists all the gallery image posts 1 by 1 whole for the acting user it does the grouping.

See attached images. I am using Node Gallery. Can you tell me why this is the case?

Comments

icecreamyou’s picture

Project: Facebook-style Statuses (Microblog) » Activity Log
Version: 6.x-3.x-dev » 6.x-2.x-dev
Status: Active » Fixed

This might happen if you have this type of activity set to only be visible to a user's relationships and the activity occurs before you establish a relationship with the acting user. After you've created a relationship the grouping should happen correctly. This is actually a side-effect of #1259306: Re-architect activity message visibility.

doors’s picture

@IceCreamYou thanks for the quick reply.

You are right when you say the activity is set to be visible to only user's relationships, but for users that I am following and who are following me I still see the same issue. It works for the acting user but not for the acting user's relationships and the tests were done after the both users were following each other. If I am not undertanding you please let me know.

icecreamyou’s picture

For activity messages set to be grouped by "the acting user and the action performed," two messages will be grouped if the following criteria are met:

  1. The activity message template must be the same
  2. The "viewer" for the existing activity message must be in the allowed list of viewers for the new activity message
  3. The "stream owner" (i.e. the entity on whose page the stream is being viewed) must match
  4. The target entity (i.e. the created node) must be the same
  5. The acting user (i.e. the person who created the node) must be the same
  6. The activities must have occurred within a given time of each other (in your case 1 day)
  7. There must not be too many activities already grouped with the existing activity message (in your case 5)

Grouping occurs when the activity occurs, not when the activity stream is viewed, because of the issue mentioned in #1259306: Re-architect activity message visibility. So it can be the case that when an activity occurs it does not meet the criteria for grouping, but then later it does meet the criteria for grouping -- but at that point it is too late for it to be grouped.

I am not sure of the exact details in your case but my guess is that the confusion is at step 2.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.