After updating Toolset Blocks to version 1.6.21, Toolset dynamic blocks (Featured Image, Post Title, Post Categories with dynamic source) stopped working or disappeared in the editor, especially inside View templates.
With the previous version (1.6.16), everything worked correctly.
The issue occurred in a setup using the Kadence theme and only appeared after updating Toolset Blocks.
Solución:
The issue was identified as a plugin/theme conflict involving Toolset Blocks 1.6.21. To work around and diagnose the problem, the following steps were taken:
Downgrade Toolset Blocks to a previous stable version (e.g. 1.6.16 or 1.6.20) downloaded from the Toolset account.
Isolate the conflict by:
Deactivating all plugins except Toolset.
Switching temporarily to a default WordPress theme (e.g. Twenty Twenty).
Test which Toolset Blocks version introduces the issue before updating on a production site.
Using these steps, the site remained functional by staying on a stable Toolset Blocks version while confirming the source of the conflict.
Ultimate Member profile pages displayed only header and footer when Toolset Views was active. Disabling caching did not resolve the issue.
Solution:
An empty Toolset Content Template (“Template for Pages”) was assigned to all pages and overrode the Ultimate Member profile output.
Go to Toolset → Content Templates and remove/unassign the “Template for Pages” template from Pages. After removing it, the Ultimate Member profile content displayed correctly.
The date picker was displaying a date one day earlier than the date selected in the calendar (e.g., selecting Feb 4 showed Feb 3 in the input field), even though the WordPress timezone was set correctly. The issue occurred both on localhost and on the production site.
Solution:
The issue was caused by a global date_default_timezone_set('Asia/Manila') call introduced by the QuickBooks PHP SDK. Setting the PHP default timezone to a non-UTC value affected the JavaScript/PHP date handling used by the date picker, resulting in an off-by-one-day shift. Removing this call or keeping the default timezone as UTC resolved the issue and restored correct date selection behavior.
