Thanks! Now at least the "why" is answered, only the "how" remains. 😉 I guess there is no workaround in WinSCP itself.
Ok, indeed before 6.4.1, the <*2024-11-09* was interpreted the same way as <2024-11-09 – i.e. as a time constraint – not the way you want.
This unwanted and undocumented behaviour (which I didn't even know about until now) was lost with upgrade to a new compiler/IDE in 6.4.1.
Now the <*2024-11-09* is correctly considered invalid. As it should have always been.
Sorry for double posting, but I cannnot edit as a guest. I just checked WinSCP version 6.3.6 and I do not get an error message there! So there was a change in any way.
I knew this reply would come. 😉
I can guarantee that I used this file mask without an error message for years. I even have it dozens of times in my history for that input field. I can only imagine that the asterisks were ignored a few versions ago, which means <*2024-11-09* was identical to <2024-11-09 (and that would mean that I always filtered for the file date).
And it's about the GUI.
Is there any other way to achieve my goal (with WinSCP)?
It is not possible and it never was.
Is this about GUI or scripting?
I always used this as a file mask for filtering files on an SFTP storage: <*2024-11-09*
This showed me all the files whose filenames (not dates!) were before *2024-11-09*, e.g. backup_2024-11-08.tar.
Now this does not work anymore, the mask is invalid and I get an error message. The documentation also tells me that is is not possible.
First question: When did this behaviour change? There is nothing in the changelog.
Second question: How do I achieve what I'm trying to do? I need to delete a lot of files. I cannot use the date, because the upload date is not always the backup date (due to errors on my server's side).