The customer reported two issues with their search function on the page: (1) when clicking the "apply" button, the view jumps back to the beginning of the website instead of staying at the current position; (2) the search function only searches by post title, but they want it to search all content, including cities in a specific column.
Solution:
We checked the page and confirmed that the issue with the search redirecting to the home page was not reproducible, suggesting it may have been resolved. For the search to include text from custom fields (such as cities), we recommended using the "Relevanssi" plugin. The customer integrated Relevanssi, configured it, and confirmed that the search functionality now works as intended.
The customer reported an issue where, when opening a post for editing in two of their custom post types, they receive a message: "Missing script for creating a new template. Not able to create one." This message only appears when the editor section is disabled for those post types. The other two custom post types are functioning normally without this message.
Solution:
We attempted to recreate the issue on a fresh WordPress installation with Toolset, but we could not replicate the error, even with the editor disabled. We suggested that the issue might be caused by another plugin or a custom function in the theme. We recommended the customer test with all non-Toolset plugins disabled and a default theme. The customer found a workaround by enabling the editor and then hiding it in the Admin interface. The customer decided to monitor the situation and indicated they might open another ticket if further assistance is needed.
The customer encountered an accessibility error "Missing form label" when running an accessibility check using WAVE on a search filter created with Toolset Views. The issue was due to the text search input field missing an id attribute, which caused the WAVE tool to flag the error. The customer attempted to add a label with the for attribute but still encountered the issue.
Solution:
We initially suggested including both the label and the wpv-filter-search-box shortcode within the
The customer reported an issue where a filter they created worked fine, but the sorting by "vintage" on the results page was not functioning properly. The issue was observed after clicking on the sorting option by "vintage."
Solution:
We identified that the issue was related to the "vintage_post" field, which was created and managed by ACF (Advanced Custom Fields). The sorting issue did not occur when using a Toolset custom field. As a workaround, we advised the customer to manage the "vintage_post" field with Toolset by following these steps:
- Go to Toolset > Custom Fields and click on the "Post Field Control" button.
- Search for the "vintage_post" field and click on "Manage with Types."
- Edit the Toolset View "ADVANCE FILTER" and change the column field from
This workaround allowed the sorting to function correctly using the ACF field within the Toolset View. The customer confirmed that the solution worked perfectly on the staging site.
I am trying to create a membership-based site for alumni where members can register and display their profiles. I have set up custom fields for "Contractor" (simple profile) and "Showcase" (detailed profile) but the showcase list is not displayed properly in the contractor template.
Solution:
Use the Toolset relationship feature to create a connection between the Contractor and Showcase post types. Then, display the related posts using a content template following the steps provided in the Toolset documentation.
The customer was unable to save their content template and encountered JavaScript errors when updating the Kadence Pro plugin, which prevented access to the content templates. The customer reported issues that seemed to stem from changes in WordPress 6.6, affecting Toolset dynamic sources.
Solution:
We escalated the issue to our second-tier support, who identified that the problem was due to changes in WordPress 6.6 affecting Toolset dynamic sources and resulting in JavaScript errors. We applied a workaround on the customer’s development site, which involved several steps:
- Deactivated Toolset Blocks.
- Registered a temporary custom post type for viewing templates.
- Made a minor edit to the affected template titles to enable the Update button.
- Saved the templates and then unregistered the custom post type.
- Reactivated Toolset Blocks and attempted to edit the repaired templates.
After applying these steps, the customer was able to access and edit the content templates successfully. A video was provided to demonstrate the process.
The customer confirmed that the workaround worked, resolving the issues with saving and accessing their content templates.
I created a form to update user data on a client portal site, but the form does not display on the page when it loads.
Solution:
The issue was related to access control settings for front-end user forms. Ensure that the access control settings are correctly configured to allow the appropriate user roles to view and interact with the form. Once these settings were adjusted, the form displayed correctly for non-admin users as well.
I am attempting to update a Custom Post Type's custom fields using the WP Rest API with the toolset-meta object, but I cannot find documentation on how to perform a PUT operation.
Solution:
The Toolset wrapper for custom fields does not support editing via the Rest API. Use native WordPress functions to access and update the custom fields, just like any other native WordPress field.
