[Resolved] WP REUSABLE FIELDS CONFLICT WITH TOOLSET BLOCKS

[Author]

Posts

[stefanT-3]

With recent updated to WordPress and/or Toolset I have gotten a conflict between the WP built in reusable fields in the Guthenberg editor and Toolset Blocks. The result is that the post halts loading since it can't fetch the reusable fields from WordPress. By de-activating Toolset Blocks the problem goes away.

[Nigel]

Hi there

I'm not sure what you mean by "reusable fields from WordPress".

Do you mean Patterns (formerly known as Reusable Blocks)?

If so, what is the context in which they are not working?

On my test site I have no problem going to Appearance > Patterns and reviewing and editing patterns, and I have no problem editing or viewing a page that uses patterns (including patterns that use Toolset dynamic sources).

Can you describe the steps necessary to see the issue?

[stefanT-3]

Thanks for your reply.

Yes, it's "Patterns".

The problem occurs when I'm on a post which has Patterns. It's not only that the Patterns doesn't load, it can't even load the complete post if it has Patterns. As soon as a de-activate Toolset Blocks everything works perfectly.

I have used Toolset for several years and Patterns as well without any prior issues.

[Nigel]

I see from your debug info you are using PHP 8.3; I wonder if that is the cause of the issue, given that I don't experience the problem on my own site (currently using PHP 8.1.19).

Can you check your debug.log for errors?

If you haven't already, turn on the debug log by editing your wp-config.php file and change the line with WP_DEBUG like so:

define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);
define('WP_DEBUG_DISPLAY', false);

That will create a debug.log file in your /wp-content/ directory which you can examine in any text editor. Try visiting the same page with patterns that fails to load and then inspect the log.

If you are in a position to downgrade to PHP 8.2 you might also check that.

[stefanT-3]

Thanks Nigel for the help. The problem was finally resolved by re-saving the Patterns. Very strange that the problemed just appeared and that Toolset somehow created a meltdown.