doytch

I assume that’s you in another guise, Jonathan? =)

When WP RSS Aggregator fetches a feed, it saves the feed items into the WordPress database. So yes, even when the feed stops containing a story, it’ll still be in the DB unless it was deleted according to the plugin settings.

Does that answer your question? I’ll confess, I’m a little confused by your wording.

Hey Jonathan, your filter makes sense and the only caveats I would identify would be the obvious one of relying on what appears to be a bit of a quirk in the way WordPress handles post creation.

Regarding your question about targeting the query: bad news. We create the aggregated list by performing a single WP_Query with all the feed sources at once. As a result, any argument you add is applied on all the feed sources.

Based on your questions, I’ll take a stab in the dark and guess that you’re trying to only apply the “post_status = future” to that one jewishinstlouis.org feed so that that feed’s future content gets shown alongside other feeds’ published content. In that case, using something like $args['post_status'] = array('publish', 'future'); would solve the problem. (And yes, any ordering will be applied globally on all the feed items.)

Does that help at all?

Hi michalberg, thanks for the bug report.

I’m fairly certain I know what the issue is so I’ve gone ahead and fixed the bug and released a new update, version 1.1.

I hope that fixes your problem but a word of advice. I believe the bug is caused by an old version of PHP on your host that doesn’t support some newer features in the language. I’d recommend asking them to update (or updating yourself if you can) to avoid future problems and have maximum compatibility.

Have a great day!
Mark Hurst Deutsch