Filtering posts by attributes such as text, postType etc

[jamesmacwhite]

What are you trying to do?

Just putting this as a potential feature request. I had a recent scenario where we wanted to filter out some Instagram post content from our feed, because some lacked any post text attribute value, this wasn't an issue with the API/plugin but the post itself made more sense on the Instagram platform, but displaying on our website with no context didn't make much sense.

The craft.socialFeeds.getPosts() variable has an options parameter but I think it only has limit and offset to use here.

It would be nice to be able to filter the API response data by post attributes before setting a limit.

While this can be done through Twig before displaying, it does mean by doing additional filtering after any original limit set may need to be padded, given the filtered results may go below the original limit critiera depending on what is filtered out.

What's your proposed solution?

Ability to filter a feed by one or more post attributes defined in the post model.

Additional context

No response

[engram-design]

Yep, I can see that being pretty useful! We'll likely introduce some sort of callback function to allow you to filter things. Indeed, you could just add a conditional for the post, but it'll be neater as a callback if we can pull that off in Twig.

[jamesmacwhite]

That would be good, or possibly an event to manipulate the results before any getPosts() options are applied?

That's the key one for my scenario. Let's say I am displaying the latest two Instagram posts with limit: 2 but I'm also filtering posts by additional criteria e.g. the text attribute being null. Because the limit option is applied before, I could in theory get fewer posts back than the desired limit, because what if one or more posts were filtered out after the returned limit.

To counter this currently we essentially request more items than needed e.g. 5 or 10 and then use array_slice to return the desired values required, but if direct filtering were available that gets applied before the options limit, that would prevent this scenario, in addition to having a callback which would make it cleaner and not having to use |filter in Twig.