The customer inherited a site using an older version of Toolset with the legacy Views editor for the directory page's search and layout. When trying to export the settings and data from the old site to a new one, the Views were not available on the new site, and the Professional Profiles data was missing. The customer wanted to know how to add Views or use another method to easily set up the new site using Astra and Beaver Builder.
Solution:
The legacy Views editor was likely disabled by default on the new site. To resolve this, it was suggested to enable the legacy editor in Toolset > Settings, which allows the Views menu to be displayed. The customer was then guided to use the Toolset Module Manager plugin to properly export and import the Types and Views configurations from the old site. This process successfully restored the Views on the new site. The customer was also advised on how to use Beaver Builder for designing content templates for their directory using Toolset.
I am experiencing an error when trying to save a content template in Toolset, despite not making any changes. The error appears randomly and persists even after duplicating the template.
Solution:
The issue was traced back to a custom code snippet added in Toolset's settings, which caused a fatal error during the save process. By modifying the custom code to apply only when viewing specific post types , the issue was resolved, and the template can now be saved without errors.
The customer has two custom post types: "Providers" and "Offers," where each "Offer" is linked to a "Provider." After editing some Offers, they noticed that these Offers were no longer visible to the original Providers in their front-end accounts and appeared under the customer's admin account instead. The original Providers could no longer edit their Offers without accessing the WordPress backend. The customer wanted to know how to make the Offers appear again in the original creators' front-end accounts and whether it was possible to edit Offers from other Providers without changing the Offer ownership.
Solution:
When editing the posts in the backend, the post author was being overwritten with the current user (the customer's admin account). To prevent this, it was suggested to go to Toolset > Post Types, edit the "Offer" custom post type, and enable the "Post author" option in the Supports section. This change would allow setting the post author when editing, ensuring the original author remains unchanged, and maintaining proper ownership visibility on the front end.
The customer created a content template and set up custom fields to display within this template. However, the content template is not being displayed on the front end as expected.
Solution:
The issue likely stems from the theme's compatibility. The customer's theme may be a block-based theme (such as Twenty Twenty-Four), which does not utilize PHP templates. As a result, Toolset content templates cannot override the theme's default display settings. It was suggested to switch to a traditional PHP-based theme to ensure that Toolset content templates are displayed correctly on the front end.
I am trying to use the default_label attribute with the [wpv-control-postmeta] shortcode to display a default "All" option for a checkbox custom field. Despite following the documentation, the default_label attribute isn't functioning as expected, and adding the option through jQuery is proving complex.
Solution:
Checkbox fields do not natively support a "select all" option via the default_label attribute. Instead, add a custom checkbox labeled "All" manually and use the wpv_filter_query hook to modify the query when this option is selected. Check the $_POST object to identify when "All" is selected and update the query args accordingly.
I am trying to resolve an issue where the 'Favorites' (Bookmark) button appears multiple times on the same page, instead of just once at the top as expected. The button seems to appear whenever a 'Single Field' dynamic data block is used.
Solution:
The issue occurs because the 'Favorites' plugin likely injects the Bookmark button via the "the_content" filter, which also affects WYSIWYG fields. To prevent this, insert the WYSIWYG fields via a shortcode with the suppress_filters='true' attribute to stop third-party filters from applying.
The customer encountered a message related to a Toolset license key and needed assistance to understand how to manage site registration and the use of the key.
Solution:
We explained that if the site is registered as a development site, it must be "published" to convert it to a production site. This can be done from the WordPress dashboard or the Toolset account page. The license key is used to validate the Toolset license and can be entered via the WordPress admin under Plugins > Add New > Commercial tab > (Un)Register Toolset link. The green check marks indicate that the plugins are up-to-date, while red checks signify that updates are needed.
