Please check this support thread:
https://toolset.com/forums/topic/when-i-try-to-edit-an-archive-page-i-receive-an-white-page-or-a-page-broken/
I am reopening this ticket with an important update. Following up on our previous discussion, I reported the editor crash to the Kadence support team. They have responded, stating that they do not officially support Toolset's templating and dynamic content system. They believe the issue is a fundamental incompatibility and are not planning to issue a fix from their side. Their recommendation was to migrate my templates to their own system. I have pasted their full, official response below for your review.
Given that Kadence is a very popular block editor, could you please provide some guidance from Toolset's perspective?
- Is this a known issue, and what is Toolset's official stance on compatibility with the latest versions of Kadence Blocks?
- Do you have a recommended best practice or workaround to ensure stability when using Kadence blocks within Toolset Archives?
- What are Toolset's future plans regarding this integration?
I appreciate your help in navigating this compatibility issue.
Thank you.
Answer from the Kadence support team:
Thanks for sharing access to your website. I brought this issue to our development team for review, and I’ve been reassured that since Toolset uses its own dynamic content system, which differs from how Kadence Blocks handles dynamic data, it isn’t officially supported. Because of that, issues like this can sometimes occur when the two systems interact.
Have you tried using Kadence Hooked Elements for your templates instead of the Toolset template method? In the past, we’ve seen users run Toolset and Kadence together successfully, but results vary. Based on your report, I suspect the problem is tied to Toolset’s templating engine. Using Kadence Hooked Elements to take over post or page templates may help you work around the issue.
You can learn about Template Elements in general here.
We also have a guide on creating a Single Post Template for Custom Post Types here. This guide can be useful if you decide to use ACF/Metabox over Toolset or if you would like to see if the same issue is bypassable using Hooked Elements.
For clarification, we did have a feature request related to Toolset support in the past. However, I wanted to share a quote directly from our Lead Developer for context:
To be clear here, we don’t recommend Toolset. They have added support for their dynamic content to be available in Kadence Blocks. We have not found that support to be stable, and we have our own dynamic source tools now. We will continue to work with toolset to the extent that they want to but can not recommend them.
I hope this helps. Please let me know if you can achieve this using Kadence Hooked Elements or if there is anything else I can help with.
-----
