The customer needed to register and use Toolset on a development version of their live site. However, Toolset was showing an error due to a mismatch between the live and development site URLs, as each Toolset site key is bound to a specific URL.
Solution:
The customer was directed to Toolset's FAQ regarding registration in a development environment. Key points from the guidance included:
- Multiple Site Keys for Unlimited Accounts: For users with Unlimited Sites or Lifetime accounts, Toolset allows multiple site keys. They can create separate keys for development and production environments to avoid URL conflicts.
- Manual Installation for Single Site Accounts: For customers with a Single Site account, which only provides one site key, it is recommended to skip registration on the development site. Instead, they should download the necessary Toolset plugins directly from their Toolset Account page and manually install them on the development site. This approach maintains automatic updates exclusively on the live, production site.
The customer wanted to display a countdown for the next event date from a custom post type for a music band, using a date field as the target. Although they initially used the Spectra Pro countdown block, they encountered challenges setting a dynamic end date directly.
Solution:
The Toolset Countdown block can use dynamic data for the countdown's end date. However, to make this work with Spectra Pro or any countdown block that accepts shortcode-based data, the customer could format Toolset's date field from a UNIX timestamp to a format compatible with Spectra. The steps included:
1. Creating a View Loop: Even when displaying a single upcoming event, creating a View loop within Toolset allows the countdown block to be placed dynamically within the loop.
2. Formatting the Date for Compatibility: Toolset provides methods to convert the date field from UNIX format, ensuring compatibility with external blocks like Spectra Pro if shortcodes are required.
The customer confirmed this setup worked, with the Toolset Countdown block operating dynamically within the loop for future events.
The customer’s form at https://www.domain.com/apply-form/ was experiencing issues with the date picker and conditional logic fields, which were not functioning as expected. The issue was identified as jQuery not loading correctly on the page.
Solution:
Upon investigation, it was found that the Autoptimize plugin was preventing jQuery from loading, which affected the date picker and conditional logic functionalities. The solution steps included:
1- Disabling the Autoptimize Plugin Temporarily: The plugin was disabled, which restored the date picker functionality on the form page.
2- Recommendation for Long-term Fix: The customer was advised to reach out to Autoptimize plugin support to determine why jQuery wasn’t loading on all pages. This would allow them to keep the plugin enabled without impacting jQuery-dependent functionalities.
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.
