New bugs with filters and object locations

[windharp1]

Several features are not working any more since ... at least last week.

1. Filtering files of a user by date does not work. if you do Select Files / Start timestamp you can input a date but the list still has all files afterwards.
2. Setting object location is bugged in several ways. If you use the same coordinates you used for the last one (Copy&Paste or clicking the same spot), the button doesn't get activated. Both reading and setting coordinates seems to only work sporadically, in most cases clickiing the button does not do anything.

SInce both started approximately at the same time, I assume they result from the same change?

[simon04]

Hi @windharp1, thank you for your detailed report. Yeah, the application errors come from a recent code refactoring (migration to Vue).

I've tried to tackle both problems and I've released a new version. The save button should become active after either (a) a click on the map, (b) pasting coordinates from the clipboard, or (c) typing latitude/longitude manually and focusing another element (e.g. by pressing the tabulator key).

Please let me know, if this fixes the issues. Thanks!

[windharp1]

Oh, I hate when I need to move stuff to a different platform at work. There are so many problems hidden deep in the code...

Now it is a lot better, as the basic functions seem to work again. If you don't mind, I'll use this issue for the things I notice still could need fixing

1. When I paste coordinates into the object location field, the coordinates appear twice.
2. When I start from my userpage on commons it starts with https://locator-tool.toolforge.org/#/geolocate?user=User%3AWindharp and does not show any hits. When I add a date, it works again. To me it seems like now it won't work without a date for userStart?
3. Show user files on map / as gallery does not work, both show no images.

(PS: A really great tool, as you may already know. Big thumbs up for creating this! )

[simon04]

Hi, issues 1+2+3 should be addressed. I was testing on Firefox previously which did not reveal issue 1. :)

[windharp1]

Thanks a lot!