The customer reported that images in a Toolset template were rendering with a distorted 2:1 aspect ratio in Chrome. Investigation revealed that this issue was caused by Chrome's user agent stylesheet adding a contain-intrinsic-size attribute after the WordPress update to version 6.7. The problem did not occur in other browsers or on a different template.
Solution:
The developers released a hotfix for the affected plugins:
Toolset Blocks 1.6.18
Toolset Access 2.9.2
Customers were advised to update these plugins to their latest versions after creating a full backup.
The customer reported a PHP error originating from views/invalidator.php on line 274. Additionally, they experienced issues with the Block Editor for CPTs and image uploading. Debugging revealed these issues could be related to cached views in Toolset and the latest WordPress update to version 6.7.
Solution:
1- Cached Views Issue:
Enabled the legacy Views interface following Toolset’s documentation on enabling legacy views. Cleared the cached views, which resolved the initial PHP error.
2- Image issue fix:
We released hotfixes for:
- Toolset Blocks 1.6.18
- Toolset Access 2.9.2
Advised the customer to update to these versions after creating a full backup.
The customer reported that images in a Toolset template were rendering with a distorted 2:1 aspect ratio in Chrome. Investigation revealed that this issue was caused by Chrome's user agent stylesheet adding a contain-intrinsic-size attribute after the WordPress update to version 6.7. The problem did not occur in other browsers or on a different template.
Solution:
The developers released a hotfix for the affected plugins:
Toolset Blocks 1.6.18
Toolset Access 2.9.2
Customers were advised to update these plugins to their latest versions after creating a full backup.
The customer tried to render embedded media for Facebook and Twitter posts using Toolset's Embedded Media custom post type, but the links were not displaying as intended. Only a simple link appeared, instead of the expected embedded content.
Solution:
We found that recent policy changes by Facebook and Twitter affect automatic embedding capabilities in WordPress. Toolset utilizes WordPress's built-in embedding function, which can no longer directly handle Facebook and Twitter embeds due to these updates. To embed content from these platforms, users need to retrieve the embed code manually:
• Twitter: Use Twitter’s Publish tool for the embed code. The embed code can be placed in a WYSIWYG custom field in Toolset for proper display: https://publish.twitter.com/
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 wanted to create a search form with drop-down options for filtering academic texts on their website, aiming to replicate a search functionality similar to that on the Jeb Dunnuck site. They faced difficulties implementing this using Toolset Views with the legacy editor.
Solution:
To achieve the desired search functionality, the customer was advised to add a select dropdown for post type filters within their view and use the following code for implementation:
The customer was unable to set image sizes in the Advanced Custom Fields (ACF) settings within the WordPress dashboard. The image size dropdown was not appearing, which hindered the ability to select a custom size for images.
Solution:
We discovered that the issue was related to resource limitations on the server. By disabling several resource-intensive plugins, the customer was able to access the image size settings properly. Additionally, we recommended increasing the PHP and WordPress memory limits to improve performance.
The customer wanted to create a slider for videos similar to an existing image slider on their site. Although the videos were set up as custom fields, they were currently displayed in a row on the page instead of a slider format.
Solution:
We advised the customer that Toolset does not have a built-in feature to directly display multiple videos from a custom field in a slider. Instead, we provided a custom HTML structure using the [wpv-for-each] shortcode to wrap the video outputs, along with custom CSS to style the videos in a slider-like format. This allowed the videos to be visually organized, improving their appearance.
You can start by wrapping your video outputs in a custom HTML structure like this:
The customer is experiencing an issue on their portfolio page where the hover image is not displaying correctly. Instead of appearing over the tile-image-logo on hover, it appears below it. The images were added using image blocks with dynamic sources and dynamic links, and custom CSS was applied to create a hover effect.
Solution:
We suggested using a different approach for implementing the hover effect in WordPress, given that the example provided by the customer used a different page builder. We provided a demo created with Toolset to illustrate a similar hover effect using two custom fields for the images. The solution involved using specific CSS classes (front-image and back-image) to control the visibility of the images on hover. The CSS was applied directly to the page using an HTML block to achieve the desired effect:
In the output of the View the back image is added first and the front image second (so the front image will cover the back image).
Please note that for this hover effect to work, the CSS targets the front image using a specific class ('front-image'), which you need to add in the View settings (please check the screenshot bellow).
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.
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.
