WordPress.org
Get WordPress

Make WordPress Core

Opened 3 weeks ago

Last modified 2 weeks ago

#62432 new defect (bug)

Switching beteween editing modes breaks blocks

Reported by: cokertmek's profile cokertmek Owned by:
Milestone: Awaiting Review Priority: normal
Severity: normal Version: 6.7
Component: Editor Keywords: needs-screenshots reporter-feedback
Focuses: Cc:

Description

After updating to WordPress 6.7, if I switch between the "edit" and the "preview" mode in the block-editor, the block breaks stateing "This block has encountered an error and cannot be previewed."

This happens to all blocks.

I'm getting a JS error "Uncaught TypeError: this.tabs is undefined" and "The above error occurred in the component:"

Change History (5)

#1 @mayanktripathi32
3 weeks ago

  • Component changed from General to Editor
  • Keywords needs-screenshots added
  • Version set to 6.7

Hello, and thank you for reporting this issue!

Could you share a recorded video of the issue? I’m currently unable to replicate it. Also, please remember to open any issues related to Gutenberg at GitHub Issues - ​https://github.com/WordPress/gutenberg/issues/new/choose

Thanks!

Last edited 3 weeks ago by mayanktripathi32 (previous) (diff)

This ticket was mentioned in ​Slack in #core by desrosj. ​View the logs.
2 weeks ago

#3 @desrosj
2 weeks ago

  • Keywords reporter-feedback added
  • Summary changed from WordPress 6.7 problem to Switching beteween editing modes breaks blocks

@cokertmek When you refresh the page, are all of the blocks preserved and still working?

#4 @cokertmek
2 weeks ago

Hello, sorry for the late reply. As of WordPress 6.7 "SCRIPT_DEBUG, true" enables the React StrictMode. This caused an js-error which breaks the block(s). I just set define "SCRIPT_DEBUG', false" in wp-config.php as a temporary workaround. Not sure now that if it is about ACF block.

#5 @desrosj
2 weeks ago

@cokertmek Could you paste the full text of the error you are seeing? Also, could you share more why you think ACF blocks may be causing the issue?

Note: See TracTickets for help on using tickets.