When more than 60 locations match the location search query in the location search's "Table" view, the locations are filtered down to roughly 60 anyway and a message is shown indicating that.
This extra filter is difficult to explain and understand for people. The intent was to reduce clustering on the Map view and keep the Table view listing the exact same information as the Map. Since completion of #721, the Table isn't matching anymore so a paging feature is more intuitive.
This new paging feature will involve:
Add page_size and page_offset parameters to the URL along with appropriate defaults when they're not set. A good default page_size could be 40. A good default page_offset would be 0 or 1( such that no location is skipped).
Modify LocationSearchController.php to increase the maximum locations from 60 or whatever it is now to 5000 or more.
Test speed of the location search feature after the change to see if it works at an acceptable speed. Rating calculations tend to be fairly slow and running 5000 of them may take a few seconds. Ideally, we want a fraction of a second.
When more than 60 locations match the location search query in the location search's "Table" view, the locations are filtered down to roughly 60 anyway and a message is shown indicating that.
This extra filter is difficult to explain and understand for people. The intent was to reduce clustering on the Map view and keep the Table view listing the exact same information as the Map. Since completion of #721, the Table isn't matching anymore so a paging feature is more intuitive.
This new paging feature will involve: