minified react error 200 "Target container is not a DOM element"

[tsdexter]

• [x ] I've read and understood the contribution guidelines.
• [x ] I've searched for any related issues and avoided creating a duplicate issue.

Please give us a description of what happened.

When I activate the yoast plugin and load the page/post editor (gutenberg) it crashes with a react error "Target container is not a DOM element"

Please describe what you expected to happen and why.

I expect the editor to load and work as normal

How can we reproduce this behavior?

1. install PublishPress Permissions and revisions plugins (https://publishpress.com/permissions/)
2. install yoast
3. create a "subscriber" user and use permissions to assign additional 'revisor' roles to the user and permissions to revise some pages
4. login with the user and load the page editor (gutenberg)
5. gutenberg crashes, cannot recover and error console contains a minified react error 200 "Target container is not a DOM element"

I am assuming since the permissions plugins add/remove capabilities/UI from the editor view for lesser permissioned users Yoast is trying to render some react to a DOM element that does not exist on the page. @agapetry any ideas what could cause this and whether or not the underlying issue is on your end or Yoast's?

Technical info

• If relevant, which editor is affected (or editors):

• [ ] Classic Editor
• [x ] Gutenberg
• [ ] Classic Editor plugin

• Which browser is affected (or browsers):

• [x ] Chrome
• [x ] Firefox
• [x ] Safari
• [ ] Other

Used versions

• WordPress version: 5.8.1
• Yoast SEO version: 17.5
• Gutenberg plugin version:
• Classic Editor plugin version:
• Relevant plugins in case of a bug: PublishPress Permissions, PublishPress Revisions

• Tested with theme: 2019

[tsdexter]

This is still occurring with the latest plugin versions except it looks like the yoast plugin added some error handling and doesn't crash the editor anymore.

PublishPress Permissions 3.7.9 PublishPress Revisions 3.1.1 Yoast 19.2

[agapetry]

The PublishPress team is not able to reproduce this error with the current plugin versions.

[tsdexter]

Thanks @agapetry I will do the updates and confirm on this end as well

[jeroenrotty]

Closing due to inactivity & the PublishPress team mentioning it wasn't reproducible. If the issue still occurs, please feel free to reopen.