31 Jul
2013
31 Jul
'13
3:06 p.m.
On 07/31/2013 02:05 PM, Vincent Massol wrote:
Ah, so it would be the opposite approach; instead of having the activity stream know
what to filter, one passes this information into the stream when creating the entry.
Are there any pointers how one could hook into the creation of the ActivityStream
elements?
I guess I could replace / inherit from the ActivityStreamImpl event listener,
but I guess this is not the best way to do it ...
Clemens
On Jul 31, 2013, at 1:53 PM, Clemens Klein-Robbenhaar <c.robbenhaar(a)espresto.com>
wrote:
[...]
So the only
way to make sure unpublished blog entries do not show up in the
activity stream would be to inspect the blog post directly for each entry
after querying the activity stream, or make a big join over the activity stream
and the corresponding pages (which might be blog entries, or not, and if they are,
have an "is published" flag set, and a publication date either not set or in
the past)
... duh, this sounds quite inefficient,
Note that it's also possible to pass custom parameters to the activitystream storage,
so it should be possible to add some "display in AS UI" boolean and modify the
AS UI to not display those.