Last modified: 2014-02-12 23:38:01 UTC
I tried entering dates which I guess is not what the form wants. It should be made clearer that you can test only against the most recent 100 edits, and that those fields are looking for a *time* (presumably server time?).
It isn't true that you can only test against the most recent 100 edits. The time format is whatever is accepted by strtotime() (i.e. most things)
(In reply to comment #1) > It isn't true that you can only test against the most recent 100 edits. The > time format is whatever is accepted by strtotime() (i.e. most things) > "This page allows you to check a filter entered in the box below against the last 100 changes. To load an existing filter, type its filter ID into the box below the edit textbox, and click the "Load" button." -- needs to be changed then, obviously.
Well, the most things idea for the creation date/time isn't working for me either. I never got any sort of log when I tried using those fields despite the fact that the filter I chose had several hits during that time.
Marking this bug as Lowest priority. I've done this in a batch to (usually enhancement request) bugs where: * It is not clear that this bug should be fixed. * It is not clear how to fix this bug. * There are difficulties or complications in fixing this bug, which are not justified by the importance of the bug. * This is an extremely minor bug that could not be fixed in a few lines of code. If you're interested in having one of these bugs fixed, your best bet is to write the patch yourself.
They dont work for me either.
