Skip Navigation

[Resolved] white page instead of Backend with block editor on single page.

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
- 10:00 – 13:00 10:00 – 13:00 10:00 – 13:00 10:00 – 13:00 10: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/Kolkata (GMT+05:30)

This topic contains 10 replies, has 2 voices.

Last updated by Minesh 5 months ago.

Assisted by: Minesh.

Author
Posts
#2708019

I am trying to open a page in editor.

Link to a page where the issue can be seen:
hidden link

I expected to see:
The page opend in Editor
Instead, I got:
a white page without any content. Online view of these page still works an in database table of page all looks normal. Other pages could also still opened normal.
And when i deactivate the Toolset plugins (type, Blocks, access) the editor also opens normal.
We work with new Blocks Version 1.6.16
WordPress in actual version

Errormessage in Console: TypeError: Cannot read private member #e from an object whose class did not declare it at get text (rich-text.min.js?ver=dd125966cf6cc0394ae0:2:9520) at get length (rich-text.min.js?ver=dd125966cf6cc0394ae0:2:9401) at WI.isEmpty (block-editor.min.js?ver=868d782fcb169133c92b:41:51967) at VI (block-editor.min.js?ver=868d782fcb169133c92b:41:43290) at B (element.min.js?ver=cb762d190aebbec25b27:9:6435) at Z (element.min.js?ver=cb762d190aebbec25b27:9:7430) at Y (element.min.js?ver=cb762d190aebbec25b27:9:6890) at B (element.min.js?ver=cb762d190aebbec25b27:9:6189) at Z (element.min.js?ver=cb762d190aebbec25b27:9:7430) at Y (element.min.js?ver=cb762d190aebbec25b27:9:6890) ar @ react-dom.min.js?ver=18.2.0:10 react-dom.min.js?ver=18.2.0:10"

#2708075

Minesh
Supporter

Languages: English (English )

Timezone: Asia/Kolkata (GMT+05:30)

Hello. Thank you for contacting the Toolset support.

This issue seems to be related to the following errata:
- https://toolset.com/errata/block-editor-failing-to-open-for-some-pages/

But that issue is already fixed with the latest Blocks and Views version.

What if you deactivate and delete the current view's plugin and then install and activate the latest views plugin manually from the plugins page.

You can download the latest views plugins from your account's download page:
- https://toolset.com/account/downloads/

#2708132

We work with actual version of types and blocks. But i deactivate it and replace it with the actual versions from your download-page.
But it still have the problems.

#2708133

Minesh
Supporter

Languages: English (English )

Timezone: Asia/Kolkata (GMT+05:30)

That is strange.

In order to minimize the cause of the issue as well as to ensure there is no conflict between the plugins/theme you use:

Could you please try to resolve your issue by deactivating all third-party plugins as well as the default theme to check for any possible conflicts with any of the plugins or themes?
- Do you see any difference? If no:

I will require duplicator copy of your site and exact steps I will have to follow that should help me to see the issue.

*** Please make a FULL BACKUP of your database and website.***

Can you please send me duplicator copy of your site:
- https://toolset.com/faq/provide-supporters-copy-site/

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

#2708307

Minesh
Supporter

Languages: English (English )

Timezone: Asia/Kolkata (GMT+05:30)

I've installed and activated the Debug Log manager plugin and enable the error log and when I checked:
- hidden link

I can see fatal error. Can you please deactivate the plugin:

Postman: wp_mail has been declared by another plugin or theme, so you won't be able to use Postman until the conflict is resolved.
Plugin Name: WP STAGING Optimizer

Does that helps?

#2708329

I deactivate PostMan on Staging system - but that made no difference.
The information from WP Staging comes, because on Staging Pages are the mail-transport blocked .

#2708453

Minesh
Supporter

Languages: English (English )

Timezone: Asia/Kolkata (GMT+05:30)

Well - I see you reported another ticket where custom fields are missing.

Can you please try to fix that issue first as it could be dependent problem if custom fields are missing.

#2708468

Hi Minesh,

As i wrote in the other ticket - the fieldgroups are recreated. But still, we cannot edit the page.
In these page, we only work with normal Blocks and no Toolset element was on that page?

#2709142

Minesh
Supporter

Languages: English (English )

Timezone: Asia/Kolkata (GMT+05:30)

I found that when I deactivate the plugin "Kadence Blocks – Gutenberg Blocks for Page Builder Features" the page does loaded successfully in admin:
- hidden link

There must be some configuration issue or conflict but to ensure what conflict it does, do you know what Kadence Blocks you added or there could be misconfiguration or corrupted settings for that block as other pages on the site works as expected.

#2709147

I activate on staging site the Kadence Blocks again - and we get white page.
And then i deactivated Toolset Blocks - and I could edit the page without problems.
I checked it and found no specific block, which looks like a possible the reason, for that issue.

I open hidden link and edit it.
It has the same structure of blocks - with one exclusion! In the "problematic" page for tegernsee, was a empty row block, with two sections, without any content.
I delete these row - and all works well.
After it, i add again a empty row - and it still works now.
Crazy - and worrying because it means that in the combination of Toolset Blocks and Cadence Blocks, something like this could happen again at any time.:-)

#2709204

Minesh
Supporter

Languages: English (English )

Timezone: Asia/Kolkata (GMT+05:30)

Glad to know that you spot the different and removed the problematic block.

That is what I said that there must be something corrupted and not saved accurately. If you have any issue in future, you're welcome to open a new ticket.