Navigation überspringen

[In der nächsten Version behoben] When adding a new post on a custom post type, the block editor doesn't load

This support ticket is created vor 2 years, 2 months. 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 13:00 – 18:00 13:00 – 18:00 -

Zeitzone des Unterstützers: America/Sao_Paulo (GMT-03:00)

Dieses Thema enthält 2 Antworten, hat 2 Stimmen.

Zuletzt aktualisiert von jeffreyS-6 vor 2 years, 2 months.

Assistiert von: Mateus Getulio.

Author
Artikel
#2693934

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 (versteckter Link)
at get length (versteckter Link)
at WI.isEmpty (versteckter Link)
at save (versteckter Link)
at versteckter Link
at ba.<computed> (versteckter Link)
at versteckter Link
at versteckter Link
at Ur (versteckter Link)
at Fr (versteckter Link)

#2693937

Nigel
Unterstützer

Sprachen: Englisch (English ) Spanisch (Español )

Zeitzone: Europe/London (GMT+01: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.

#2693938

Thank you! I reverted and that solved it.