I just saw that today (10/1/08) I have two groupings for the same date.
In addition, the first of the two duplicates for 10/1/08 contains items that should have been grouped with items from 9/30/08 and 10/1/08. There are some items in the 9/30/08 group, but not all of them are there.
What could be causing this?
Does it have something to do with the fact that there are only 30 days in September, and it created the extra date grouping for the 31st day, which doesn't exist?
It looks like this:
10/1/08
item 20 (correct)
item 19 (correct)
item 18 (correct)
item 17 (correct)
item 16 (correct)
10/1/08
item 15 (should have been grouped with 10/1/08 items)
item 14 (should have been grouped with 10/1/08 items)
item 13 (should have been grouped with 10/1/08 items)
item 12 (should have been grouped with 10/1/08 items)
item 11 (should have been grouped with 10/1/08 items)
item 10 (should have been grouped with 9/30/08 items)
item 9 (should have been grouped with 9/30/08 items)
item 8 (should have been grouped with 9/30/08 items)
item 7 (should have been grouped with 9/30/08 items)
item 6 (should have been grouped with 9/30/08 items)
9/30/08
item 5 (correct)
item 4 (correct)
item 3 (correct)
item 2 (correct)
item 1 (correct)
| Comment | File | Size | Author |
|---|---|---|---|
| #9 | activity_stream.xls | 246.5 KB | dmetzcher |
Comments
Comment #1
dmetzcher commentedI should note that the individual Activity Stream nodes have the correct dates and times. It's just when they are displayed that they appear under an incorrect, duplicate 10/1/08 date heading.
Comment #2
akalsey commentedI can't reproduce this on a 6.x installation using the latest dev version.
The date headers have no math involved. They simply compare the date of each item to the date of the previous item and insert the header if the dates don't match.
Can you give me the node dates for the items that appear to be in the wrong place? The timestamps directly from the node table in the DB would be best.
Comment #3
dmetzcher commentedI will try to put this information together. Is there an easy way? Any tips?
Also, I upgraded to the latest dev version, just to be sure. And...uh oh...
I noticed that all my activity stream items had been duplicated (for as far back as the feeds went, which for certain feeds is farther than others).
I ran cron.php, and noticed that many had been deleted. All but Twitter, it seems.
Is this normal?
Will the Twitter duplicates go away, eventually?
I'm testing now to see if future twitter posts will also duplicate.
Comment #4
dmetzcher commentedRegarding the duplicated items...
Would it be ok to open them up right in the browser and delete them (clicking the # character in the activity stream, then edit, then delete, etc.)? Will this cause any problems? (This is all assuming that the duplicated Twitter items don't go away on their own, of course. I can give them a few hours, I guess.)
Comment #5
dmetzcher commentedToday, 10/3/08, all posts from yesterday are posted to today's date. There is no date header from yesterday at all now. It was there yesterday, however.
Comment #6
dmetzcher commentedAnd I just posted something today (10/3/08), and now I have two headings for 10/3/08. The first one contains all the posts for 10/2/08, and the second one contains the actual 10/3/08 posts.
Comment #7
dmetzcher commentedI just noticed something else, as well.
This seems to happen when an import of items crosses a date. So if I have posts from just before midnight, and posts for just after, and they are imported, they get a heading with the date of the current day. Then, if I import more items from the current day, they get a duplicate heading for that day, going forward.
I'm seeing the same thing for today that I saw for 9/30/08.
And again, all the dates of the individual Activity Stream nodes that were created are correct.
Comment #8
dmetzcher commentedIf you want to see what I'm talking about...
http://metzcher.com/stream/3
Comment #9
dmetzcher commentedI am attaching an Excel document that contains all the Activity Stream nodes on my site. I can't see this being any sort of security risk, since the nodes are all viewable to the general public, and I've already posted the URL.
It is sorted by created date, with the most-recent at the top.
Comment #10
akalsey commentedCheck to make sure the activitystream table in the db has a "changed" column.
Comment #11
dmetzcher commentedYes, the activitystream table has a "changed" column.
I see...
nid
guid
link
data
changed
...as the columns.
Comment #12
dmetzcher commentedImports have stopped now. Not sure why. I run cron manually and still nothing. It's like the Activity Stream module has just stopped working. Even updates to my blog are not appearing there (I'm using that separate module for that which has been referenced in another issue and written by another Activity Stream user).
Comment #13
eojthebraveDo you get any errors on screen or in your Watchdog table if when cron runs?
It's a long shot, but try emptying your cache_* tables just to make sure you don't have any corrupted variables in there.
Comment #14
akalsey commentedI'm afraid I'm stumped. I can't reproduce the problem at all.
Comment #15
akalsey commentedI'm thinking this is some sort of an issue with timezones.
What timezone are you in?
And what timezone is your server (the OS) set to?
What are your system-wide timezone settings in Drupal?
What's your user's timezone in Drupal?
Your tweet "Palin: Cheney's Worst Act Was "Duck Hunting Accident" (Video) - http://tinyurl.com/47nmje #wtfpalin" was published at Fri, 03 Oct 2008 04:56:00 GMT
The next item "It's really getting cold out now. Fall is here with force." was published at Fri, 03 Oct 2008 14:25:00 GMT
Depending on your timezone, those would fall on different days, but Activity Stream simply compares the day, month, and year without regard to the timezones.
Try this for me. Find the lines
And change them to
Then reload the stream page. Do the dates appear correctly?
Comment #16
akalsey commentedNo activity on this issue. Closing
Comment #17
seanreiser commentedFYI- I was having this exact issue and akalsey's patch solved the problem for me.