Toolset lets you develop truly custom sites, including WooCommerce, Membership and Directory/Classifieds sites.
Visit our dedicated tutorials to learn how to build each of these sites using Toolset:
The customer wanted to locate and manage specific Toolset archive data in the database via phpMyAdmin and sought clarification on whether deleting a Toolset archive would also remove the associated data from the WordPress database.
Solution:
It was clarified that Toolset archives are not stored as separate database entries. Instead, they are dynamically generated using WordPress custom post types, taxonomies, and fields. Therefore, there is no specific database table labeled as a "Toolset archive." Key points addressed included:
1- Toolset Archive Location: Archives are generated on-the-fly based on Toolset settings rather than being stored as standalone entries in the MySQL database. Users should adjust or review archives through the Toolset interface under Toolset > WordPress Archives in the WordPress admin area.
2- Data Deletion: Deleting Toolset items (like custom post types or fields) from the WordPress backend will remove the associated data from the database. The customer was advised to refer to forum guidance on this topic and to back up their site before proceeding with deletions.
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.
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 created WooCommerce archive pages using Toolset and wanted to display a widget in those archive pages only. They used the is_product_category() conditional wrapper, but the widget content did not appear on the front end. The customer was unsure if a different conditional wrapper was needed because the WooCommerce archive was created using Toolset.
Solution:
We suggested using the woocommerce_page_title hook to add the conditional, which worked in a similar setup. Additionally, we provided an alternative solution involving the creation of a custom shortcode [is_tax_sc] to check if the current page is an archive page of a specific taxonomy (in this case, 'product_cat'). This shortcode could then be used with Toolset’s conditional shortcode to display the widget only on the product archive pages. The customer later confirmed that the issue was resolved after switching from a Genesis page hook to a WooCommerce hook.
Problem:
The customer wants to add a JSON-LD script with schema.org/Movie structure to their single movie page. This JSON-LD should include information from the single post and custom fields created with Toolset, for better SEO and to help search engines understand the content.
Solution:
We suggested using Toolset Views to create a JSON output. This involves using the classic version of the view editor to structure the JSON output according to the schema.org/Movie structure. Steps include:
Enable the classic view editor in Toolset settings.
Create a new view in Toolset -> Views.
Replace the default wpv-loop tags with the necessary JSON structure in the view loop editor.
Ensure the "Disable the wrapping DIV around the View" option is selected for correct JSON formatting.
An example structure was provided to illustrate how to format the JSON output within the view.
Additionally, the customer can use the view's API function get_view_query_results to build and display the JSON output with PHP if more customization is needed.
Problem:
Customer was having issues after building the site for the desktop and checking how it looked on mobile it didn't look responsive. Solution:
We oriented the customer about techniques that can be used to adapt the site for mobile devices:
- Responsive Adjustments: Toolset allows you to check how pages look on various devices and offers solutions for common responsive design issues, such as adjusting text sizes, column widths, and gaps between elements.
- Typography and Color Adjustments: You can control typography and color settings for different screen sizes within any Toolset block. This feature lets you optimize text for readability across devices.
- Grid Control: For layouts that use columns, Toolset’s Grid block lets you set different column sizes and control the spacing between columns and rows for each screen size.
- Element Visibility: Toolset also provides options to hide specific elements (like large images) on mobile devices to improve loading times and user experience. Relevant Documentation: https://toolset.com/course-lesson/creating-responsive-designs/
Problem:
I need advice choosing a translation plugin for my website. I usually work with Polylang, but I would like to know if there's a better option working with Toolset, like WPML. Solution:
We told the customer that gor getting the most compatibility out of Toolset with a multilingual plugin we'd recommend WPML. This plugin is also part of Toolset's family and it is developed by the same company and highly tested with Toolset.
