Toolset Maps is a WordPress plugin that allows you to add address fields to any content type or users and display any content on Google Maps.
Toolset Maps User Guides include detailed documentation for creating these special address fields, adding pointers to them and displaying them on maps.
When you ask for help or report issues, make sure to tell us the versions of the Toolset plugins that you have installed and activated.
Viewing 15 topics - 136 through 150 (of 214 total)
Problem: I would like to use shortcode attributes to pass arguments into a View's Query Filter.
Solution: You can configure taxonomy filters and custom field filters to respond to separate shortcode attributes, and add those shortcode attributes to the view shortcode.
Problem: Toolset Maps are not initialized correctly when the Google Translate plugin is active on the same site. If I set a breakpoint in the code, I can see that the google object is defined when the code expects it to be undefined. The logic should be updated to test more explicitly for the maps object.
Solution: Update to the latest versions of Toolset plugins to receive the fix for this issue.
Problem: I have a View of custom posts that displays a map with markers, using a distance filter and sorting results by distance. In some cases the distance center is set by a URL parameter, and in others, it is set by a shortcode attribute. I have implemented some custom code in a wpv_view_settings filter to toggle between the shortcode attribute and the URL parameter. In the cases where distance center is set by a shortcode attribute, I am using another custom shortcode to get the User's predicted zip code. That shortcodes an external service to get a predicted zip code based on the User's IP address. The custom zip code service seems to be working correctly, and the results of the View seem to be accurate.
However, in the cases where this zip code shortcode is used to set the View's distance Query Filter by shortcode attribute, the View consistently causes the page generation time to jump by 3 or more seconds. I would like to try to optimize the page load time as much as possible.
Solution: In this case, testing revealed that using the custom zip shortcode inside a wpv_view_settings filter callback was the source of the delay in page generation, for some reason not fully understood. Replacing that shortcode with a hard-coded zip code resulted in a page generation time just a fraction of a second higher than the page without the View present at all.
Optimization of the zip code shortcode is necessary to prevent the latency seen in page generation time.
