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.
| Sun | Mon | Tue | Wed | Thu | Fri | Sat |
|---|---|---|---|---|---|---|
| 8:00 – 12:00 | 8:00 – 12:00 | 8:00 – 12:00 | 8:00 – 12:00 | 8:00 – 12:00 | - | - |
| 13:00 – 17:00 | 13:00 – 17:00 | 13:00 – 17:00 | 13:00 – 17:00 | 13:00 – 17:00 | - | - |
Supporter timezone: America/New_York (GMT-04:00)
This topic contains 15 replies, has 2 voices.
Last updated by 4 years, 2 months ago.
Assisted by: Christian Cox.
Hello, it is possible the addresses for these posts are not mappable as entered. For example, this post:
hidden link
The address seems to be:
60594 Frankfurt, Metzlerstraße 19
However, when I enter this address in an address field in wp-admin, the Google Maps API suggests the following address:
Metzlerstraße 19, 60594 Frankfurt, Germany
In this case, you must select the suggested address as shown in these screenshots.
Please check the post editor in wp-admin and edit the address field for this post. Try selecting a suggested address, then test the search function once again, searching within 50km of the address Metzlerstraße 19, 60594 Frankfurt, Germany to see if this post is shown in the results as expected. If not, there could be another problem. Please go to Toolset > Settings > Maps and click "Check API". Copy the response and paste it in your next reply.
Then edit this post in wp-admin once more:
hidden link
Take a screenshot of the address field and map, then share that screenshot in your next reply.
I will review everything and give you some additional feedback. Thank you!
I am unable to access the login for this site, I see an error "This site can’t be reached - wetzlar.grashuepfer.uixandy.com’s server IP address could not be found." Do you have a custom host file entry for this site, or is it restricted by IP somehow?
Okay no problem. I can see the issue now. It seems that Divi was configured to load the Google Maps API scripts in Divi > Theme Optionen > Allgemeines. Only one of these scripts is required, and Toolset Maps loads one for you automatically. Loading the script twice causes problems like you have experienced. I have disabled this option for now, and I am able to see suggestions in the Adresse field now when I type an address. Can you confirm this is working as expected now?
Okay I was just testing this and I found out that your server runs MySQL version 5.5.5, while distance calculations require MySQL 5.6+: https://toolset.com/toolset-requirements/
I suspect this is the main cause of the problem with the View results. You can confirm this by removing the Distance Query Filter from the View editor screen temporarily. At that point, the View should return results as expected when the other filters are used (not the distance filter).
Other features of the software work well in MySQL 5.5.5, but distance calculations specifically require MySQL 5.6+. Without this upgrade, Views that include a distance filter will not return any results. You may need to ask your hosting provider to perform this update for you. Be sure to make a backup of your database before upgrading to MySQL 5.6+.
I also suggest you clear the Toolset Maps address cache in Toolset > Einstellungen > Karten. Each cached address should contain a latitude/longitude coordinate, like the one I created for Metzlerstraße 19, Frankfurt, Germany (see the screenshot here). However, since most of these addresses were entered without selecting a suggested address, the latitude and longitude values were not cached correctly. You can begin re-entering Adresse field values and selecting suggested addresses in the address input field, even before the MySQL upgrade. This process will add each address into the cache so you can then query them successfully with the Distance filter you have already created, once the upgrade is complete.
After the upgrade and cache update, I'll be glad to take a closer look if things aren't working as expected.
