Date range imports

[jamacon36]

Overview

This reworks logging, replaces the giant query that happens in upserting POIs, and adds a date range field to the dashboard and supporting server logic.

Notes

This has been well tested and needs a look at the code to make sure it's sound and a check for things like forgotten console logs.

Locations of Note

• Line 447 of Otis_Importer.php (for loop that replaces the while loop that's commented out below)
• Line 365 of Otis_Importer.php (new logic to look for modified date vs date range and new Otis date formatting)
• Line 61 of Otis_Dashboard.php (logic for modified_start and end params)

[BrendanJercich]

This looks good to a quick review. To your point about line 447 of Otis_Importer, how do you feel about the performance impact of making a WP_Query for every single listing, as opposed to the old method of grouping UUIDs for a single query? Is the goal there to minimize the possibility of timeouts? @jamacon36

[jamacon36]

@BrendanAdkins exactly re: the for vs while loop, meta queries are notoriously slow and taxing so my thought was to reduce the size of the query to make the look up more efficient. I could be really on the wrong path but things seem happier

[BrendanJercich]

I'm wavering on this. It'd be one thing if we were replacing a meta query with a non-meta query, but this is breaking one big meta query into a series of smaller meta queries, and I don't have good insight into the performance impact there. Still, if it's working acceptably in production and not blocking site operations it's probably okay for now. I'll log an issue to compare performance when we have more time.