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.
The customer faced an issue where a conditional block in Toolset was not displaying the expected information on the live site, even though it appeared to work correctly in the admin view. The block was designed to show information from a custom field if the field was populated and to hide it if the field was empty. This issue occurred specifically on the "profile pages" of therapists under the "Where I offer therapy" section.
Solution:
We suggested enabling debugging on the conditional block to gather more information. The debug data revealed that the condition was incorrectly testing if the custom field's value equaled a specific string, rather than checking if the field had any value. We recommended configuring the condition to test for an empty field instead. After applying this adjustment, the customer confirmed that the issue was resolved.
The customer wanted to know if Toolset could be used to create an online shop that allows customers to buy products directly from the pages created with the plugin.
Solution:
We explained that while Toolset can handle basic e-commerce features such as creating product listings and a simple checkout form, it does not support advanced functionalities like payment processing, tax calculations, and order management on its own. For a fully-featured online shop, it is recommended to integrate Toolset with WooCommerce, which provides all necessary e-commerce capabilities. We provided resources for creating custom WooCommerce sites with Toolset to guide the customer in building their desired online shop.
The customer is working on a website with two different types of listings—one created using another plugin and the other using Toolset. They wanted to know if it is possible for both custom post types (CPTs) to share the same fields and taxonomies, which are currently attached only to the custom post type created by the other plugin.
Solution:
We clarified that if the customer wants to have identical CPTs in both Toolset and another plugin, it might be best to convert the existing types and fields so that Toolset manages them, ensuring everything is centralized in one place. We provided a link to the relevant documentation for converting existing types and fields to Toolset control. Additionally, we mentioned that in some cases, it is possible to use custom fields in Toolset even if they are not managed by Toolset, but this would need to be checked on a case-by-case basis.
