Activity Story Stream caching

I'm implementing a customisation where certain posts have to be editable directly from the Activity Story Stream widget via a new link in the story menu that opens a modal editor. That process is working fine, however I've been unable to figure out how to get the widget to recognise the changes straight away. If, for example, I edit a listed blog post and then navigate to the post or the containing blog, the changed details are immediately visible. Returning to the stream widget, the original content continues to be displayed until the cache expires or is manually flushed. Is there any way to force the widget to pick up the change immediately, at least for the authoring user?

Parents
  • Hi . What you're doing sounds like it should already work, since the blog post activity story type already handles blog post update events. Does an edit and publish of a blog post in a traditional fashion (directly in its editor) also not immediately update its activity stream story without manually clearing the cache? What APIs are you using to update the post in a modal? And are any exceptions being logged when the post updates that may indicate its event handlers are not processing?

Reply
  • Hi . What you're doing sounds like it should already work, since the blog post activity story type already handles blog post update events. Does an edit and publish of a blog post in a traditional fashion (directly in its editor) also not immediately update its activity stream story without manually clearing the cache? What APIs are you using to update the post in a modal? And are any exceptions being logged when the post updates that may indicate its event handlers are not processing?

Children