Closed (fixed)
Project:
Activity Log
Version:
6.x-2.x-dev
Component:
Code
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
26 Jan 2012 at 12:56 UTC
Updated:
17 Apr 2012 at 16:31 UTC
While any activity [ especially for acting user ] happens related to user relationship then rules in tokens don't get replaced in activity stream, while it works for other two activities [activity for user relationship & content ] while if I enable log grouping it doesn't work for any case. This is the case with both email and web type logs. I don't see either duplicate tokens or any unusual thing in database either.
Using drupal commons 2.x.
Not sure it's a bug or what so opened support request.
So need help around it.
Thanks.
Comments
Comment #1
icecreamyou commentedIs this a new installation or upgrade? I'm not sure I follow exactly what's happening -- can you attach screenshots?
Also, are you sure this is against 6.x-2.0-beta1?
Comment #2
nmudgal commentedIt's drupal commons 6.x-2.x installation, didn't upgrade it. You can check the activity stream here in wall [for e.g.]
http://petitions.halabol.com/users/dhruvarora
http://petitions.halabol.com/users/kubersharma
http://petitions.halabol.com/users/anshultewari
Also these are being generated with default rules that comes up with installation.
Well I couldn't find any version info in .info file of activity log module in default drupal commons installation so I guess it should be this, though not sure, if you can tell how to check this ...
Comment #3
icecreamyou commentedThe version should be visible at admin/build/modules. I'm not sure why you'd be seeing this problem, I'm certainly not seeing it locally
Comment #4
nmudgal commentedVersion info is not visible at admin/build/modules as they are not in .info file of activity log which comes with drupal commons, here is screenshot http://www.webpagescreenshot.info/img/720817-1272012103924AM
Comment #5
icecreamyou commentedThat's weird. That usually means it's a version with local modifications. I'm going to push this over to the Commons queue and see if we can gain any insight.
Comment #6
gargsuchi commentedSome more info regarding the same issue. This issue is not happening just for user relationships, but for other types of activity logs as well.
On further debugging I found that in the events table, the id_map column seems to be the culprit. In the specific messages I looked at, the id_map was not complete. By not complete I mean that the serialized data was incomplete as it was overshooting the limit applied by the column type (text) and naturally this was resulting in the tokens not being parsed.
The reason behind this was that I am using RPX module as well. This results in the $user object being very large as it contains the "friends" data for the user as well. So if a user is logging in using facebook and he has 500 friends, the $user object will have the full friends list as well, which finally results in the id_map being too big.
Hope I am making sense here. Can give you sample DB records if needed.
Thx
Suchi
Comment #7
nmudgal commentedComment #8
notasheep commentedAny more progress here? I'm also having this issue, which started after an upgrade from Commons 2.3 -- also noticed that Activity Log is missing any version info.
Checked out id_map data in activity_log_events, and they're huge -- up to 20,000 characters. I don't have RPX installed, though, so I'm not sure what's causing this. However, I do notice it's including all or most of the user's data, and including it twice. Hmm... any tips on digging into this more?
UPDATE:
It seems I may have fixed this by simply hitting "Clear All Message Caches" at admin/settings/activity_log.
Comment #9
Enideo commentedI've had the same problem since updating to Commons 2.6 earlier today.
notasheep's suggestion works for default rules, but not custom ones. To fix this, I've had to 'delete' (actually this means reset) these rules and then re-customise them. Part of the 'dev' lifestyle I guess..
If IceCreamYou's happy to tolerate such faults for this dev version, I'd suggest marking this issue as closed.
Comment #10
ezra-g commentedUsers upgrading from Commons 2.3 or below should follow the 2.4 release note upgrade steps for reverting Triggered rules.
Commons uses the dev version of Activity log because it depends on fixes committed since the last Activity log release in July, along with #1306252: Duplication of messages about node creation in group for acting user. I suppose we could add Git Deploy to better track this, but I'd rather see a new Activity log release :).