Skip Navigation

[Resolved] White screen when try to edit content template

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

Problem:
The customer reported that it is not possible to edit the existing content templates and a particular WordPress archive, as the edit screen just shows the white blank screen.

Solution:
Guided that since WordPress 5.9, if using non-Toolset blocks (including core blocks) with dynamic sources in templates, Views, or custom archives, errors are thrown and it may not be possible to edit the page.

This will be fixed in the future release and a quick fix is to set the 'SCRIPT_DEBUG' constant to 'false' in the website's 'wp-config.php' file.

As for the archive, some of the data needed for its proper functioning was no longer available in the database, so it was unrecoverable, and suggested creating a new one.

Relevant Documentation:
https://toolset.com/errata/errors-when-using-3rd-party-blocks-with-dynamic-sources-since-wp-5-9-update/

This support ticket is created 2 years, 10 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: Asia/Karachi (GMT+05:00)

This topic contains 4 replies, has 2 voices.

Last updated by Rostislav Avtodiychuk 2 years, 10 months ago.

Assisted by: Waqar.

Author
Posts
#2294479

I am trying to:
Hello, I'm trying to edit an existing content template and see white screen. But this turned out to be a problem, I was already re-creating, disabling plug-ins, leaving only the toolset, but I could not edit. I did not find a solution on the forum, I decided to write to you, all plugins and themes are actual and have the latest version. Help solve the problem, unfortunately for me it is urgent. I am sending you the last debug log in wp-conten/debug.log

Link to a page where the issue can be seen:
hidden link
hidden link
hidden link in this case a can't see and can't edit my loop view.
Thank you for help!
p.s. on ftp use TLS/SSL
I expected to see:

Instead, I got:

#2295221

Hi,

Thank you for contacting us and I'd be happy to assist.

I've tested your website's clone on my test server and was able to see the issue mentioned about those specific content templates and WordPress Archive.

This report is now shared with the concerned team for further investigation and I'll keep you updated on the progress.

Thank you for your patience.

regards,
Waqar

#2296433

Thank you for waiting.

During troubleshooting, we were able to narrow down the issue and this will be fixed in future releases.

Since WordPress 5.9, if using non-Toolset blocks (including core blocks) with dynamic sources in templates, Views, or custom archives, errors are thrown and it may not be possible to edit the page.
( ref: https://toolset.com/errata/errors-when-using-3rd-party-blocks-with-dynamic-sources-since-wp-5-9-update/ )

A quick fix is to set the 'SCRIPT_DEBUG' constant to 'false' in the website's 'wp-config.php' file:
( on your website it is set to 'true' )


define( 'SCRIPT_DEBUG', false );

After that, you'll be able to edit those content templates.

I'll keep you updated on the WordPress Archive issue too.

#2296479

I've received an update about the WordPress Archive issue too.

For this particular WordPress Archive ( 'Archive for Оголошень (archive-for-ogoloshen)' ), some of the data needed for its proper functioning is no longer available in the database. I'm afraid, it is not recoverable so you'll need to delete this WordPress Archive and create a new one.

In our tests, a new WordPress Archive can be created without any error, once the 'SCRIPT_DEBUG' constant is set to 'false'.

#2296917

My issue is resolved now. Thank you!
Thank you very much for your help! I noticed that when using a dynamic field on standard blocks there was a problem with a white screen, but I redid them using toolset blocks, it is also sometimes impossible to link to the container, it was disabled immediately when adding a custom field.