I've read over all the recent issues with the activity stream being blank and still am unable to get mine to populate. I am updated to the following versions:

  • Activity_log - 6.x-2.x-dev
  • Rules - 6.x-1.4
  • Token - 6.x-1.18
  • Facebook Style Statuses - 6.x-2.0

When I type a message into some ones wall (or my own) and hit share it looks like it is processing but I get the message: "There is no activity here yet.". I refresh the page and see the same message, clear the cache and the same message. However, if I use the Facebook-style Statuses: All Statuses block, it displays all the statuses that I can't see in my user-profile stream.

Any ideas what might be causing this issue?

Thanks for the help.

Comments

sylvaticus’s picture

hello, I'm using Activity log 6.x-2.x-dev (2011-Dec-22) on a Drupal Commons 2.3 site.
Even if I unistalled all previous versions, it worked for me only after I went on /admin/settings/activity_log and "plaied" a little bit with it, restoring defaults and regenerating activity. I got a message that 42 activity log templates was generated.
I also went to triggered rules and copied for each rule action labelled activity_log the text under "English" in "Italian", but I'm not sure this is needed.

icecreamyou’s picture

Status: Active » Postponed (maintainer needs more info)

Activity Log only works with FBSS 3.x, so I'm assuming the OP meant FBSS 6.x-3.0.

Is this an upgrade from previous versions of Activity Log or FBSS? Are you using Commons?

bryceray1121’s picture

I did mean fbss 3.x (i've tried both the recommended version and the dev version), sorry for the typo. I am not using commons.

I'm not sure exactly what did it, but playing around with the admin panel / clearing the message cache seems to have fixed the problem. We will have to wait and see if it was a one-time glitch or weather its going to come back or not.

icecreamyou’s picture

Status: Postponed (maintainer needs more info) » Fixed

Okay, well feel free to reopen if it comes back.

Status: Fixed » Closed (fixed)

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