I have been able to create a block which displays only the Activity stream of the user profile currently being viewed. I have achieved this by using the default all_activity view and creating a block, which I then assign an argument, which is User:Uid. Make sure that you select User instead of Node for the Relationship.

Action to take if argument is not present... select Provide default argument... and then select User ID from URL. Click update. I then go to ADVANCED PROFILE KIT and assign the block to the APK inside one of the panels. No problems.

Everything is working great after this. BUT... I am running into 1 problem. The requester activity stream does not show up in this block. The user sending the relationship request will not have a activity stream message displayed after the request has been approved. The requestee activity stream on the other hand, shows up without any problems. Simply put, the user requesting the relationship does not receive the stream output in the block on ttheir own profile page. However, the user that approves the relationship receives the activity stream inside the block on their own profile page. All activity streams show up without any problems on the all_activity page.

Can somebody please help? Is there something wrong with my VIEWS arguments or is this something wrong inside Activity? I can't seem to be able to figure it out!

Thanks again in advance!

Comments

mmachina’s picture

mmachina commented
Status: Active » Closed (fixed)

Very strange phenomenon... the problem seems to have corrected itself...

Has anyone else experienced this problem?

mmachina’s picture

mmachina commented
Status: Closed (fixed) » Active

problem is back... :-(

mmachina’s picture

mmachina commented

sorry... the problem is the requester activity... user relationship friend request approval does not display on requester profile... only on requestee profile and on all_activity page view.

_shy’s picture

_shy
Primary language Ukrainian
Location Ukraine, Lutsk 🇺🇦
commented
Status: Active » Closed (outdated)

D6 reached its EOL back in February 2016, and there is no active release for D6 for this module anymore.
Development or support is not planned for D6. All D6-related issues are marked as outdated in a bunch.

If the issue remains relevant for D10+ versions, merge requests with proposed solutions for a new module version (D10+) are welcome in a new follow-up issue.

Thanks!

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.