Ok, I'm going to start here since the display of this content is in a view. Here's the deal: We're using a modified version of the Activity module's view to display recent activity. Basically, we pull things like who created what, who replied, etc, and we show this on the front page of the site kind of like a facebook news feed. The problem is that any posts I make from my main account (not User 1) only appear in the view until the next cron run. As soon as cron runs (about every 15 minutes on our site), all activity posted by me (and only me) since the last cron run disappears from the feed.

The posts themselves are there, just the view that shows recent activity is dropping the activity item.

This doesn't happen with any other users, including two who also have the same role as I do, and post frequently. The problem we're having here is that this doesn't happen on our dev server, only on the live site, so I really don't want to muck around with upgrading anything until we really have to. We are running a Dev version of Views: 6.x-2.x-dev (2009-Jul-26), but it's been very stable since we launched the site in November, and we're not planning to do any major upgrades until later in the spring, since the site is seasonal in nature and we're at our peak in terms of usage right now.

So I guess the question is - why would a user who had been showing up in the view for months suddenly stop showing up? Nothing on the server has changed in terms of configuration - drupal version is the same, no modules have been updated since launch. If someone can answer this or point me in the right direction, I'd really appreciate it. I hate that the user account I've been using is crippled like this. Really annoying.

Comments

dawehner’s picture

dawehner
Primary language German
commented

I don't think this is a issue of views. I think the actitivity module clears some activitity entries in the database.

Could you have a look whether the entires are there in the database?

friolator’s picture

friolator commented
Project: Views (for Drupal 7) » Activity

Interesting. thanks. I just looked at the activity table, and sure enough, the last entry under my UID was back on February 12. I'll move this over to Activity to see if they have any clue as to what's happening.

Activity folks: We're running 6.x-2.x-dev (2009-Aug-05). As I mentioned above, this has been very stable for us, and it's on a live site, so we would rather not do any updates. We can't reproduce this on our dev site (which is running the same version of everything on the live site, but is in a different database). Any clues?

Scott Reynolds’s picture

Scott Reynolds commented

Activity does indeed have an expiring method it is set up at admin/settings/activity

So my first thought is to make sure both of those settings are in sync with your dev server. Lets get it replicating on the dev server first.

friolator’s picture

friolator commented

Ahh - that explains it - I totally missed that setting. I'm the most active user on the site, and we're currently set up to save all activity records. I was over the limit of records that would be kept so it was tossing new ones on cron.

The reason I wasn't seeing it on the dev server is because there aren't as many posts by me, so I was never hitting the limit. Thanks!

friolator’s picture

friolator commented
Status: Active » Closed (fixed)
Scott Reynolds’s picture

Scott Reynolds commented
Status: Closed (fixed) » Active

Well is there a bug? did the setting not behave properly ?

friolator’s picture

friolator commented

no, no bug. the problem was that I didn't realize we had set Activity to hang onto all entries, but had set a relatively low number at which it would start tossing entries (150) for an individual user. So I have about 180 posts, 30 of which aren't in the activity log. I simply passed that 150 threshold. I've tweaked the settings so this shouldn't happen again.

Scott Reynolds’s picture

Scott Reynolds commented
Status: Active » Closed (fixed)
friolator’s picture

friolator commented
Status: Closed (fixed) » Active

Sorry to reopen this, but it occurred to me that maybe there is a problem after all.

The Activity Count Purge seems to be working in reverse. According to the description of the item in admin/settings/activity/settings:

"This is the maxium number of activity records a user can have. The old records will be deleted on cron run."

It seems that it's keeping the old records. but deleting new ones, as described in my case above (anything over 150 was being deleted, but old ones stayed around).

Scott Reynolds’s picture

Scott Reynolds commented

perfect that what I thought was happening. Good you can confirm it.

sirkitree’s picture

sirkitree commented
Status: Active » Closed (duplicate)

This is a duplicate of #606800: Remove busted count purge in favor of a minimum count