Question about the creation time... should the date/time be the time CRON ran (when these items are imported) OR should they be the time the item was actually created from their original source?

I recall in past module versions the date and time of each item was the date/time they were actually created at the original source. Currently, the date/time seem to be the exact time and date CRON is run - manually or otherwise.

Please advise!

Comments

akalsey’s picture

akalsey commented
Status: Active » Postponed (maintainer needs more info)

If there's a date available in the original item AS should use it. Otherwise, it uses the cron time. What service or feed are you using that's giving you trouble?

eojthebrave’s picture

eojthebrave
he/him
Primary language English
Location Minneapolis, MN
commented

Also, make sure you're using the latest DEV version of the module. There was an issue in older versions that would have caused this problem: #296601: Activity Stream should use date from feed, not date of import

This issue was fixed in DEV on Sept. 7th, but it doesn't look like it's made it into the official release version yet.

akalsey’s picture

akalsey commented
Version: 6.x-2.x-dev » 6.x-1.x-dev

I'm assuming that since this report was made against the dev version, that's what the reporter is using.

The next production release is being held up pending an update to use the Views 2 API for D6. See #300163: Views 2.x support

Moving this issue to 6.x-1.x-dev since 6.x-2.x-dev doesn't exist. That branch was inadvertently created by a tagging typo.

spiffyd’s picture

spiffyd commented

I'd like to announce some unexpected good news (and some erratic behavior):

The stream item import times SOMETIMES work for the latest DEV build! So here is what I did (and the context).

At first, Active Stream didn't auto update even when auto cron jobs are set up on my server. Running cron manually also didn't trigger an update. To get the stream updating, I had to do was go into "My Account >> "Activity Stream" and "re-save" all the account settings/configurations. Then running cron did the trick... WITH THE RIGHT TIMES the feed items were created!

Sometimes this works, sometimes it doesn't. Can someone confirm this for me?

On a different Drupal installation, I see the same thing happening with the BETA-1 build (I had to "re-save" the account settings to permit cron updates). However, BETA-1 build did not fix the time issue- all the imported stream items still show the time Cron is run.

Hope this info may help debugging/coding efforts.

Cheers!

akalsey’s picture

akalsey commented

Could you try beta 2 and see if your issue is solved?

spiffyd’s picture

spiffyd commented
Status: Postponed (maintainer needs more info) » Fixed

No time creation issues are present with Beta-2 on cron runs. Issue seems resolved!

spiffyd’s picture

spiffyd commented
Version: 6.x-1.x-dev » 6.x-1.0-beta2
Anonymous’s picture

Anonymous (not verified) commented
Status: Fixed » Closed (fixed)

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