[Resolved] Map 1.8.3 still not working right with MariaDB
This thread is resolved. Here is a description of the problem and solution.
Problem:
In the Toolset Maps plugin version 1.8.3, if remove the the toolset_maps_distance_radius field from search form, it will return results only within 5 km.
Solution:
This issue is fixed in the latest version of Toolset Maps plugin 2.0.1, you can download it here:
This support ticket is created 5 years, 2 months ago. There's a good chance that you are reading advice that it now obsolete.
This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.
Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.
No supporters are available to work today on Toolset forum. Feel free to create tickets and we will handle it as soon as we are online. Thank you for your understanding.
Yes, I am using MariaDB 10.2.14 in my localhost, in your post view "Test Installer Finder", there is a missing filed "toolset_maps_distance_radius"
please try these:
Edit post view "Test Installer Finder", ID 18450
in section "Search and Pagination", replace the distance shortcode from:
[wpv-control-distance default_distance="30" default_unit="mi" compare_field="partner-location-address" distance_center_url_param="toolset_maps_distance_center" distance_radius_url_param="toolset_maps_distance_radius" distance_unit_url_param="toolset_maps_distance_unit" inputs_placeholder="Show some results within %%DISTANCE%% of %%CENTER%%"]
And test again, it works fine in my localhost, see screenshot distance-filter3.JPG
When you say it works fine, how many results do you get if you search for 01460 (Littleton, MA)?
On the 1.7.4 Maps on the live site I get 10 partners which is what the search is limited to and that are within the 30 mile radius. This is the correct and expected result.
On the 1.8.x Maps on staging, I get 2 partners. The search radius shortcode parameter for the search radius URL parameter is set properly in both the test installer finder and the new view I created at your instruction. Not sure why it was missing on your end. Maybe you deleted it when troubleshooting at some point?
Screenshots below. Note that they should be identical and the one with more results is the correct one using Maps 1.7.4.
Yes, I get 10 results in my localhost, the problem source is there is an URL parameter missing in your website "toolset_maps_distance_radius", the input box "DISTANCE" is missing too.
You can try this URL: hidden link
You should be able to see 10 results in your staging website.
In above page, you are using another post view (ID 19181), it is not in the duplicator package you provided.
Please try these:
Dashboard-> Toolset-> Views, find and edit the post view (ID 19181)
in section "Search and Pagination", replace the distance field shortcode as I mentioned above:
[wpv-control-distance default_distance="30" default_unit="mi" compare_field="partner-location-address" distance_center_url_param="toolset_maps_distance_center" distance_radius_url_param="toolset_maps_distance_radius" distance_unit_url_param="toolset_maps_distance_unit" inputs_placeholder="Show some results within %%DISTANCE%% of %%CENTER%%"]
As you can see, in the attribute "inputs_placeholder", there is a text "%%DISTANCE%%", which is missing in your website, but it is required, it will be able to output the radius range input.
If the problem is fixed, you can use CSS codes to hide it too.
Luo, we do not want to show an input for the radius. We want to always use 30 miles. Do we have to add it in the filter and then hide it in order to get what we want and not break the distance search? And why did this work in 1.7.4 but not in 1.8.x? Can they fix whatever changed so that we can set the radius with the default distance parameter and not have to show the radius input which is what we had working for a long time with 1.7.4 and, apparently, what broke with 1.8.x? Seems like a bug to me.
Your solution works technically but I cannot use it on the site because we don't want the user changing the search radius.
Thanks for the feedback, there should be something changed in Maps plugin 1.8.x, but tomorrow is my day off, I need to double check it with Maps plugin 1.7.4, and will update here in Monday.
Currently, please try to use CSS codes to hide that radius input. Do you agree?