Skip Navigation

[Resolved] Toolset Blocks Breaks WP 5.8’s Gutenberg Widget Screen

This thread is resolved. Here is a description of the problem and solution.

Problem:
The problem here is that the user is experiencing a few issues with the previous version of Toolset and wordpress 5.8

Solution:
We recently released our Latest version of Toolset which should resolve this issue.
The plugins can be downloaded from the link below.
https://toolset.com/download/toolset-blocks/

This support ticket is created 3 years, 4 months ago. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

Sun Mon Tue Wed Thu Fri Sat
- 9:00 – 12:00 9:00 – 12:00 9:00 – 12:00 9:00 – 12:00 9:00 – 12:00 -
- 13:00 – 18:00 13:00 – 18:00 13:00 – 18:00 14:00 – 18:00 13:00 – 18:00 -

Supporter timezone: America/Jamaica (GMT-05:00)

This topic contains 2 replies, has 2 voices.

Last updated by tenseg 3 years, 4 months ago.

Assisted by: Shane.

Author
Posts
#2121283

I am trying to:
Use the new Gutenberg block-based Widget settings screen in WP 5.8. I am currently only testing WP 5.8 on local development copies of sites, not live websites.

I expected to see:
The new Widget screen appear as normal.

Instead, I got:
A blank Widget screen. If I deactivate Toolset Blocks the Widget screen appears as I expect to see it. Therefore, I believe there is some incompatibility in Toolset Blocks with the Widget screen introduced in WP 5.8.

#2121427

Shane
Supporter

Languages: English (English )

Timezone: America/Jamaica (GMT-05:00)

Hello,

Thank you for getting in touch. Can you update to the latest version of our Blocks plugin and let me know if the issue still remains.

The latest version was released today.
https://toolset.com/download/toolset-blocks/

Thanks,
Shane

#2121433

That update to Toolset Blocks did resolve the incompatibility bug I reported.