Plugins in Debug Feed vs Updater?

1

It seems plugins are not used in the same way when updating feeds via the updater vs. when doing a Force refetch in the “Debug feeds” menu item.

Starting with the docker-compose setup (so the latest version of tt-rss as of now), I have added the Feediron plugin and some configuration for it. I added a feed that should match, waited a minute or so, and the feed items show up, but they haven’t been filtered according to the Feediron config. When I right-click the feed to go into the “Debug feed” page, and run it with “Force refetch”, the items are updated with the correct filtering applied.

Is there something that would influence plugin filters being applied differently during debug and during regular feed updates?
Or maybe some debug setting I can turn on to tell if this plugin is being called during feed updates?

The Feediron config I’m using is:

{
    "explosm.net": {
        "type": "xpath",
        "xpath": "div[contains(@id,'comic-wrap')]"
    }
}

against the feed http://feeds.feedburner.com/Explosm

2

most likely you checked force rehash which forced all articles in the feed to be processed again. alternatively this was related to origin server reaction to http if-modified-since not being supplied.

generally, in case of a properly functioning feed/web server, there’s no difference between feed debugger and normal feed update wrt plugins, it’s the same code after all.

if you bothered to check filters wiki page, you’d know that filters are guaranteed to run on new articles only. you shouldn’t use feed debugger unless you have a reason to do so.

3

I just figured out the issue, it turns out I’m a silly and it was likely to do with permissions.

I had the plugin directory on the host and was mounting it in as a volume, but have since changed the startup script to clone/pull the plugin repo in the same way as the core tt-rss code, and now everything is working perfectly.