[Assigned] Kadence Blocks: Editor crashes/stalls with Infobox + Toolset dynamic fields

[Author]

Posts

[kostasT]

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.
-----

[Minesh]

Hello. Thank you for contacting the Toolset support.

Here is a sandbox site and you can auto-login to it using the following link:
- hidden link

Can you please add required plugin and try to reproduce the issue and if reproduced send me exact steps that I will have to follow that should help me to reproduce the issue.

[kostasT]

Hi.
I can give you access to the staging site. You already know the problem as you are responsible for my previous ticket. Nothing change since then.

[Minesh]

Can you please share problem URL and access to the staging site.

*** Please make a FULL BACKUP of your database and website.***
I would also eventually need to request temporary access (WP-Admin and FTP) to your site. Preferably to a test site where the problem has been replicated if possible in order to be of better help and check if some configurations might need to be changed.

I have set the next reply to private which means only you and I have access to it.

[Minesh]

Just to ensure we are on the same page - can you please share details what problem URL on your staging site I should check against.

I have set the next reply to private which means only you and I have access to it.

[kostasT]

hidden link
I mentioned in my ticket that this is a follow up of the https://toolset.com/forums/topic/when-i-try-to-edit-an-archive-page-i-receive-an-white-page-or-a-page-broken/
But this applies to all archives, as the Kadence infobox is used in many archives.

[Christopher Amirian]

Hi,

Sorry for our late reply, I will continue this ticket as Minesh is not available at the moment.

The only way that I can report a compatibility issue with Kadence is to replicate the problem on a clean installation.

That way no other environmental issue might be in the way and that is what our copatibility team accept.

So I'd appreciate it if you could use the URL that my colleague shared:

hidden link

Install Kadence there and create a simple scenario that the issue shows and I will report this to the compatibility team and they will decide on what to do next.

Thanks.

[kostasT]

Hi,

I copied from what Minesh said in the relevant ticket (https://toolset.com/forums/topic/when-i-try-to-edit-an-archive-page-i-receive-an-white-page-or-a-page-broken/):

"Ok - it seems to me that the issue is due to the infobox block you added and with the infobox block there is a image field and that image seems to be not precent."
"You may want to raise this in front of Kadence blocks and they will do needful in order to fix the issue, if the issue is from their side they will fix it or they should contact us if fix is required from Toolset end. "

I posted the issue to Kadence, and, as I already mentioned, they believe it is a fundamental incompatibility and are not planning to issue a fix on their end.

I don't want to spend time reproducing the issue, as both parties have stated it is an incompatibility between Kadence and Toolset.

ChatGPT created the following script to temporarily Unregister Kadence Infobox. If you put in in the mu-plugins folder you will see that the archives open in the editor.

-----------
<?php
/**
* Plugin Name: Editor Rescue – Temporarily Unregister Kadence Infobox
* Description: Editor-only. Unregisters kadence/infobox so problematic instances don't mount; lets you open and remove them.
* Version: 1.0.0
*/
add_action( 'enqueue_block_editor_assets', function () {
$js = <<<JS
wp.domReady( function() {
try {
if ( wp.blocks && wp.blocks.getBlockType('kadence/infobox') ) {
wp.blocks.unregisterBlockType('kadence/infobox');
console.warn('[Editor Rescue] Unregistered kadence/infobox for this editor session.');
}
} catch (e) { console.error(e); }
} );
JS;
wp_add_inline_script( 'wp-blocks', $js, 'after' );
}, 1 );
----------

Please try to resolve the incompatibility, or let me know if you will not address the issue. I spent a lot of time on this, and I want to evaluate my alternatives. Either stay with Toolset and replace Kadence, or stay with Kadence and use Metabox or ACF.

[Christopher Amirian]

Hi,

I will try to replicate the issue there. May I ask if you use the pro version of Kadence? If so I wonder if you could install that plugin here:

hidden link

I will try to create the scenario myself

[kostasT]

Hi,
I installed Kadence PRO.

[Christopher Amirian]

Hi Simon,

I tried the Info Box and the images using the dynamic source for the Featured image of the posts and it works with no issues in the WordPress Archive:

hidden link

Would you please give me more information on what was added for the images on your website?

That might give a hint that what might be the problem cause.

[kostasT]

Try to open an archive page in the editor on the staging website. For example:
hidden link
The images are from various custom post types.
Please check the conversation in my relevant ticket:
https://toolset.com/forums/topic/when-i-try-to-edit-an-archive-page-i-receive-an-white-page-or-a-page-broken/

[Christopher Amirian]

Hi,

I have read the ticket in question. The problem is that I also used the dynamic sources in the sandbox and it works ok.

This identifies that something is off on your website and not the codeabse.

Would you please set the next reply as private and re-enter the login? The auto login feature does not work with the previous message shared.

Thanks.

[kostasT]

Hi,
Is there any update?