When adding a new post on a custom post type, the block editor doesn't load

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.

No supporters are available to work today on Toolset forum. Feel free to create tickets and we will handle it as soon as we are online. Thank you for your understanding.

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	13:00 – 18:00	13:00 – 18:00	-

Supporter timezone: America/Sao_Paulo (GMT-03:00)

This topic contains 2 replies, has 2 voices.

Last updated by jeffreyS-6 7 months ago.

Assisted by: Mateus Getulio.

Author

Posts

April 23, 2024 at 3:53 pm #2693934

jeffreyS-6

I am trying to:

Add a new post in a custom post type created with toolset.

Link to a page where the issue can be seen:
It is the admin page when you click add new.

I expected to see:
The block editor.

Instead, I got:

The editor has encountered an unexpected error. I tried disabling all plugin and switching to the 2023 theme and it still had the same error.

I clicked the copy error and I get:

TypeError: Cannot read private member #e from an object whose class did not declare it
at get text (hidden link)
at get length (hidden link)
at WI.isEmpty (hidden link)
at save (hidden link)
at hidden link
at ba.<computed> (hidden link)
at hidden link
at hidden link
at Ur (hidden link)
at Fr (hidden link)

April 23, 2024 at 4:00 pm #2693937

Nigel

Supporter

Languages: English (English ) Spanish (Español )

Timezone: Europe/London (GMT+00:00)

Hi there

Although the symptoms appear slightly different, this looks like a variant of this known issue: https://toolset.com/errata/wordpress-6-5-update-breaks-editor-if-using-core-media-block-with-dynamic-sources/

We hope to be in a position to release a fix soon, and in the meantime the best workaround would be to downgrade WordPress to 6.4.4, as described in the linked page.

April 23, 2024 at 4:14 pm #2693938

jeffreyS-6

Thank you! I reverted and that solved it.