AJAX auto-update for Toolset View search filters (update results when inputs change) was not working on an archive page. The search worked only when using a Search button (non-AJAX submit), even though the View’s Custom Search settings and AJAX pagination settings appeared correct.
Solution:
The issue was caused by the theme deregistering WordPress’ jQuery using wp_deregister_script('jquery') and loading its own jQuery directly. This removed the jquery script handle that Toolset depends on. As a result, Toolset’s frontend.js was not initialized and AJAX events did not fire when filter inputs changed.
Fix: remove the deregister logic and restore the standard WordPress approach by using wp_enqueue_script('jquery'). After that, Toolset AJAX filtering worked normally.
The client was unable to save a Toolset Content Template on a new local/staging WordPress installation after importing older blog posts. The Content Template editor would not save changes, blocking further setup of archived content.
Solution:
The issue was caused by Toolset Blocks not being installed. While Toolset Types was active, the Blocks plugin—required for creating and saving Content Templates—was missing. After installing Toolset Blocks, the Content Template saved correctly and the issue was resolved.
The client wanted users to view, edit, and delete their own posts from a “My Account” page and expected the View/Browse link to go directly to a specific Content Template. Attempts to link directly to the Content Template using Toolset’s link options and View shortcodes did not work as expected.
Solution:
In Toolset, Content Templates cannot be linked to directly. A Content Template is applied automatically when a visitor opens a post’s permalink. The correct approach is to link to the post URL itself. When the post is opened, Toolset renders it using the assigned Content Template for that post type.
For edit and delete actions, Toolset Forms’ built-in edit and delete post links should be used, as they correctly handle post IDs and permissions.
The client could not create a new Toolset View or Content Template from the Toolset admin screens. When clicking Add New View or creating the first Content Template, WordPress showed “You have no permission to access this page” and redirected to the CT editor. This happened even when logged in as an admin and with default Toolset settings.
Solution:
After testing by deactivating plugins did not resolve the issue, the client reinstalled the website. Following the reinstall, the permission errors disappeared and Views / Content Templates could be created normally again.
The root cause was most likely a rogue plugin or corrupted permissions that had altered user capabilities in the original installation.
User created a classifieds site and wants to charge users for posting an “ad” (1 month / 6 months / 12 months) using Toolset Post Forms + Toolset Forms Commerce + WooCommerce.
The form redirects to the WooCommerce cart after submission, but the cart is empty (no product/billing info shows). The setup used “product based on custom field”, however no custom field was selected/mapped, so Toolset had no product to add to the cart.
Solution:
Connect the Toolset form submission to a WooCommerce product by mapping a Toolset custom field to WooCommerce Product IDs:
On a legacy Toolset site using Layouts + Views, several Views were ordered by a custom number field. Recently, posts stopped displaying in the expected numeric order. In the View editor, the “As a number” ordering option appeared greyed out. Disabling all non-Toolset plugins did not resolve the issue, indicating a Toolset-side regression or incompatibility.
Solution:
The numeric ordering was enforced programmatically using the wpv_filter_query hook. A custom PHP snippet was added via Toolset → Settings → Custom Code to explicitly set meta_key and meta_value_num ordering.
Because multiple Views were affected, the code was adapted to apply to a list of specific View IDs, restoring correct numeric sorting across all impacted Views.
In a Toolset Block View with multiple search filters, the client wanted one specific filter (“Nur freie Zimmer anzeigen” / Available Room) to remain visible at all times, even when other filters were selected in ways that would normally hide it. Additionally, the client asked how to translate the “No items found” message.
Solution:
Toolset’s option “Show only filter options that would produce results” applies to the entire View and cannot be controlled per individual filter. Therefore, it is not possible to keep only one specific filter visible while others dynamically hide.
For translating “No items found,” the text can be edited directly in the View’s [wpv-no-items-found] output. When using WPML, the text can be wrapped in a [wpml-string] shortcode so it becomes available in String Translation
