Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Gutenberg Tabs crashing on Edit with React error - unable to edit tabs or content #61773

Closed
laraght opened this issue May 17, 2024 · 1 comment
Labels
Needs Testing Needs further testing to be confirmed. [Type] Bug An existing feature does not function as intended

Comments

@laraght
Copy link

laraght commented May 17, 2024

Description

Feature crashes in Wordpress editor when trying to select Typography to edit the styles - in the browser its showing a React error TypeError: n.map is not a function or its return value is not iterable

Update: It only happens when selecting Typography

Step-by-step reproduction instructions

Wordpress.com pages, select page, select Edit, select one of the Guternberg tabs, go into styles, select 'Typography' for example, and the block will crash and no longer be displayed or editable. Prevents users editing the Tabs or any of the content inside them to edit.

Screenshots, screen recording, code snippet

error-2
error-1

Environment info

Wordpress.com - Assembler Theme - latest Gutenberg version (updated 1 week ago) and latest Gutenberg Tabs version which it says was updated 4 months ago yet the error just happened. It was working fine earlier and in last 2 days. No new plugins were added or edited.

Please confirm that you have searched existing issues in the repo.

Yes

Please confirm that you have tested with all plugins deactivated except Gutenberg.

Yes

@laraght laraght added the [Type] Bug An existing feature does not function as intended label May 17, 2024
@Mamaduka Mamaduka added the Needs Testing Needs further testing to be confirmed. label May 18, 2024
@Mamaduka
Copy link
Member

Hi, @laraght

The "Tabs" isn't a core feature; it's probably coming from a 3rd-party plugin.

I recommend reaching out to WP.com support. They'll have more details and can submit a ticket upstream to fix the issue.

@Mamaduka Mamaduka closed this as not planned Won't fix, can't repro, duplicate, stale May 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Needs Testing Needs further testing to be confirmed. [Type] Bug An existing feature does not function as intended
Projects
None yet
Development

No branches or pull requests

2 participants