I want to display the full-size featured image on desktop and a smaller size (medium or thumbnail) on mobile devices. However, there is no built-in way to modify the [wpv-post-featured-image] shortcode to serve different image sizes based on screen size.
Solution:
Use two instances of the shortcode: one for desktop and one for mobile. Wrap each instance in a DIV with specific CSS classes, then apply CSS media queries to show or hide them based on screen width. The hidden image will not significantly affect performance due to modern browser optimization.
I am trying to add a map, created with Toolset, that displays locations from a repeatable field group on a page designed with Elementor. However, when using the shortcodes, the map appears without markers.
Solution:
Create the View using Toolset's legacy mode and include the map and its markers within the View. Then, use the [wpv-view name="Name of the view"] shortcode in Elementor to display the map. Make sure to enable legacy views under "Toolset > Settings > General".
The customer was trying to create a search functionality on their website that displayed locations based on a user's input. They had built a view that showed locations within 50 miles of the user and created a nested view to display results within 350 miles if no results were found within the initial range. However, the nested view did not trigger correctly based on the user’s input, leading to issues in displaying the appropriate results.
Solution:
We confirmed the customer's setup and created a working example to demonstrate how to achieve the desired functionality. We provided guidance on setting up the main view and the nested view using the URL parameter toolset_maps_distance_center for filtering. We also suggested moving the map markers from the block directly into the content template to ensure that the markers would rebuild when the nested view was called.
Although the customer inquired about displaying the distance from each result to the user's location, we noted that this feature was under consideration for future versions of Toolset. However, a straightforward solution was not readily available.
After implementing the changes we suggested, the customer confirmed that the nested view was functioning as expected, effectively displaying the relevant markers on the map.
