Closed (fixed)
Project:
Activity Stream
Version:
5.x-1.1
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
9 Aug 2008 at 20:59 UTC
Updated:
16 Aug 2008 at 19:34 UTC
I'm using this module to pull in content from my Google Reader shared items feed, and I generally want to edit the item once it gets posted. However, activitystream doesn't just pull in the items the first time, it also rebuilds them on subsequent cron runs, clobbering my edits.
I can see the value in that behavior, but I'd like to be able to turn it off. Currently, I've just commented out the else { node_save($node); } in _activitystream_save(), but I could provide a patch to turn this into a setting, if there's a chance it would get committed.
Comments
Comment #1
akalsey commentedThere's really no good reason to ever overwrite a local edit. If you edit a node in Drupal, it should stay that way, regardless of what happens at the source stream.
The 5.x-dev version now keeps track of when the item was imported or updated. If a node changes after import or update, the module will stop updating the node in the future.
Dev now also only updates an item if it's changed (it doesn't call node_save if the node title and body are the same as the item title and body) and it only sets the sticky, published, and status flags when the item is created, not when it is updated.
Comment #2
akalsey commentedIn 5.x-1.2