Activating the MemberPress Courses extension caused most Toolset blocks to disappear from the standard WordPress block editor because MemberPress restricted the allowed block types too broadly.
Solution:
MemberPress confirmed the issue and plans to fix it in an upcoming release. As a temporary workaround, use the provided allowed_block_types_all filter in the child theme’s functions.php file or through WPCode, then remove it after updating to the fixed MemberPress Courses version.
A Toolset Map View was not using the distance selected in the search filter. The list results respected the chosen radius, but the map still used its own hard-coded distance value, so it showed extra results.
Solution:
A custom code snippet was added using the
[php]wpv_view_settings[/php]
filter to sync the Map View distance settings from the URL parameters. The code updates the map radius, unit, and center from
[php]toolset_maps_distance_radius[/php]
,
[php]toolset_maps_distance_unit[/php]
, and
[php]toolset_maps_distance_center[/php]
. The search View also needed to use a full page refresh so those URL parameters are available to the Map View. The customer confirmed this resolved the issue.
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".
Problem:
The customer needed to filter posts in her directory by a custom taxonomy called Features, ensuring that only posts with all selected tags were displayed (using an AND operator instead of OR).
Solution:
We determined that Toolset Blocks does not natively support changing the operator from OR to AND for multiple select fields. As a workaround, we enabled legacy views and configured the custom search to use the AND operator. Additionally, we used custom code with the wpv_filter_query filter to change the operator to AND. The specific code was added to the theme's functions.php file, targeting the correct view_id:
[php]
add_filter('wpv_filter_query', 'custom_taxonomy_query_operator', 10, 3);
function custom_taxonomy_query_operator($query_args, $view_settings, $view_id) {
if ($view_id == 509) {
if (isset($query_args['tax_query'])) {
foreach ($query_args['tax_query'] as &$tax_query) {
if (isset($tax_query['operator']) && $tax_query['operator'] == 'IN') {
$tax_query['operator'] = 'AND';
}
}
}
}
return $query_args;
}
[/php]
Wir dokumentieren bekannte Probleme und ihre Lösungen in Toolset-Fehlerverzeichnissen. Sparen Sie Zeit, indem Sie zuerst dort nachsehen, ob der bei Ihnen auftretende Fehler bereits bekannt ist. Die Liste wird kurz gehalten. Wir tun unser Bestes, um bei jeder Veröffentlichung von Toolset-Plugins alle bekannten Probleme zu lösen.
Support-Richtlinie
Das Toolset-Team hilft Ihnen, die Toolset-Plugins richtig zu benutzen, liefert Ihnen alle nötigen Informationen, unterstützt Sie bei der Lösung von Problemen und gibt Ihnen Tipps zu Best Practices.
Bitte stellen Sie sicher, dass Sie nur ein Thema pro Support-Ticket eröffnen.
