My idea is to have a new column in the Filters view to show when a filter last did the action specified in the filter. This would allow you to view the filter list every few weeks and delete triggers that no longer were doing anything.
I do not know if you noticed, but I have a filter with “inverse matching”.
The filter works, but under preferences it does not show when it was last triggered.
It’s not a big deal, but just thought you should know.
I am running b96beeeda772fe087471fc9de4857702b6abe096 on mysql.
try checking feed debugger to see if the filter is actually matching. if it actually does match, the timestamp should update. i didn’t try on mysql but it should work regardless of the database.
i made a filter (set inverse) with a rule that can’t match anything, and it matched and timestamp was updated.
The filter is supposed to mark as read any article that does not contain a word in the title.
So far the word has not appeared in the feed, so every articles have been marked as read.
I was thinking that it meant the timestamp should have been updated.
If I test the filter, it returns more than 100 results, that’s why I was thinking it should have updated the time it was last run
if you have doubts always test filters with feed debugger (f D). if filter shows up in it (with &xdebug=2) and timestamp doesn’t update then it’s an issue, maybe.
filter test dialog is a convenience, not a debugging tool.
e: also, check if there’s any sql errors in event log.
See attachment. The filter shows up, because it is actually working.
Reading your previous reply, I assume the timestamp should appear only if the word that triggers the filter is in the feed. Since the word so far has not appeared, you are saying it is correct the timestamp is not updated.
My reasoning is that, since the filter has reverse matching, and the word triggering the filter has not shown up, that filter is always working, so there should be the updated timestamp.
ah right you have inverse rule, not inverse filter - wait, nvm, you don’t. hmmm.
e: i might have made this system a bit too complex, lol
going by your log, filter (id 18) is put into matched filters properly, see right below
[14:03:36/90779] matched filters:
can you check the database? i.e. select * from ttrss_filters2 where id = 18
Reading your previous reply, I assume the timestamp should appear only if the word that triggers the filter is in the feed. Since the word so far has not appeared, you are saying it is correct the timestamp is not updated.
no, that’s not how this works. if the filter is triggered, timestamp should update.
you can also try adding print_r($matched_filter_ids); right after array_map (rssutils.php:784)
As of yesterday, the timestamp keeps correctly updating.
I did nothing, except running feed debugger. Maybe that triggered something… I do not know.
The result of the sql query select * from ttrss_filters2 where id = 18 is coherent.