Skip Navigation

[Resolved] Grid and all page template content converted to HTML after update

This support ticket is created 4 years, 8 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 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 - - 9:00 – 13:00
14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 - - 14:00 – 18:00

Supporter timezone: Africa/Casablanca (GMT+01:00)

This topic contains 2 replies, has 2 voices.

Last updated by GeoffS1889 4 years, 8 months ago.

Assisted by: Jamal.

Author
Posts
#1634667

I was getting a blank page for one of the content templates. I looked at the forums and was able to solve the issue by going to https://toolset.com/forums/topic/blank-page-after-saving-template-2/ and updating to the most recent versions.

However, when I now load the page, I am getting a message that "Your site doesn't include support for the "generateblocks/grid" block. You can leave this block intact, convert its content to a Custom HTML block or remove it entirely"

When I created this page I used the Grid block. What happened on the upgrade? How can I fix this?

#1635435

Hello and thank you for contacting the Toolset support.

It seems that the page uses the Grid block from GeneratePress, and somehow, the block editor is not able to parse it now.
I wonder if you are able to build a similar GeneratePress grid, if you remember the design, on a new page? If yes, you can remove the erroneous block and recreate it.

Make sure that you are using the latest versions of plugins and themes.

Then, if the issue persists, check the browser console for any errors and activate PHP debugging on your server to spot any PHP errors.
- https://wordpress.org/support/article/debugging-in-wordpress/
- https://toolset.com/documentation/programmer-reference/debugging-sites-built-with-toolset/

#1635701

I just rebuilt the page but am very concerned that a simple upgrade did this....