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.
I have designed a toolset map using a view loop output in the WordPress blocks editor. I want to insert this map into pages designed with the Divi page builder, but I am unsure how to do this since the Divi Toolset Views module only allows selecting the view providing data to the map.
Solution:
Enable the legacy views which are shortcode-based to add the map and view to the Divi builder. Go to "Toolset > Settings > General", check "Show both the legacy and Blocks interface and let me choose which to use for each item I build", reload the page, then go to "Toolset > Views" to edit the views.
I am building a recruitment agency website using the DIVI theme and Toolset. I want to add Toolset elements to the homepage, which is built with the DIVI builder. I see that the DIVI builder has a Toolset views module, but I am unsure if using the legacy Toolset Views is the best approach.
Solution:
Enable the legacy views mode to add Toolset elements to the DIVI builder. Go to "Toolset > Settings > General", check "Show both the legacy and Blocks interface and let me choose which to use for each item I build", reload the page, and then go to "Toolset > Views" to edit and use views shortcodes in the DIVI builder.
The customer wanted to update their website locally using Toolset and then migrate it to the live environment. They encountered issues with Toolset recognizing the site due to the different URL during the migration, and later faced a problem where the site key did not match, blocking communication with Toolset servers.
Solution:
We advised the customer to mark the local site as a copy of the live site when prompted by Toolset. When the issue with the site key mismatch occurred, we recommended removing the old site key from the Toolset account, creating a new one, and registering Toolset again with the new key. This resolved the issue. We also suggested ensuring the correct URL format is used when generating the new key.
Problem:
The customer is trying to display the date a business started on every supplier page. Instead of seeing the date, they see the shortcode [calculate_date_diff].
Solution:
We identified that the template for displaying the supplier's page is configured within Divi. The shortcode [calculate_date_diff] was replaced with the correct Toolset shortcode for displaying the custom field. Specifically, we used the custom field slug 'started-business' to show the date.
Steps followed:
Go to Divi > Theme Builder.
Locate All Diverse Suppliers > Custom Body and click on Edit.
Replace [calculate_date_diff] with [types field='started-business'][/types].
The date is now properly displayed on the supplier's page.
Problem:
The customer is unable to view their form on a mobile device. They expected to see the form on the page but instead, the form is not visible.
Solution:
We tested the form on a mobile device and found that the form is visible when logged in but not visible when logged out. This indicates that the issue might be related to form visibility settings for non-logged-in users.
Problem:
The customer is concerned about what will happen to their custom types, fields, and templates if their Toolset license expires after one year. They want to know if these elements will stop working or be lost.
Solution:
We informed the customer that the existing Toolset plugins will continue to work on their site, and their data will not be affected. However, they will lose access to updates and support for the plugins. We emphasized the importance of updates, as they include new features and hot fixes. Although no immediate issues will occur, using outdated Toolset plugins may eventually cause bugs or site crashes due to updates in other software like WordPress, PHP, and themes.
