-
Notifications
You must be signed in to change notification settings - Fork 879
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
Failed to execute 'postMessage' on 'Worker' error when adding image to FAQ block #20924
Comments
Imagine your website is like a busy city. You have the main street where everything happens (the main thread), and you also have hidden alleys where specific tasks are done without slowing down traffic (web workers). YoastSEO uses these alleys to analyze your website and give you helpful tips. But sometimes, it tries to send a special guest (a React element) through the alley, which is a bit like sending a fancy car down a narrow path. The alley gets stuck because it can't handle the guest! This is what the error message means: YoastSEO tried to send something called a "React element" to a web worker, but it couldn't because it's not allowed. Here's what you can do: Find the alley entrance: Look for where YoastSEO is sending the guest. It's probably trying to tell the web worker something about your website. Remember, the goal is to help the web workers do their job without causing traffic jams. By finding the right way to send information, you can keep your website running smoothly and get the best tips from YoastSEO! I hope this makes it a bit easier to understand! Don't worry if you're not a tech expert, just think of it like a city with different areas and ways to get things done. |
Very much like https://github.com/Yoast/wordpress-seo-premium/issues/4207 - we should be able to apply a similar solution. |
Please give us a description of what happened
To Reproduce
Step-by-step reproduction instructions
Expected results
Actual results
Screenshots, screen recording, code snippet
If possible, please provide a screenshot, a screen recording or a code snippet which demonstrates the bug.
![image](https://private-user-images.githubusercontent.com/88657898/288783235-6c4e29d2-1d4c-4f15-8047-9a9a32031666.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjA1NzQwMDMsIm5iZiI6MTcyMDU3MzcwMywicGF0aCI6Ii84ODY1Nzg5OC8yODg3ODMyMzUtNmM0ZTI5ZDItMWQ0Yy00ZjE1LTgwNDctOWE5YTMyMDMxNjY2LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA3MTAlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNzEwVDAxMDgyM1omWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWViYjg4OGJiOTA4M2UwNjAyZTVkZGM4MWExZDMxZjg3Y2E0NjNlMzI5NjM4NWVkZjU3YjkwMmRmYWZmYjVjMzcmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.rWwGOBjin1Bt0a7aNwhO5BDp2dqqCDvEmypPfq6tDpo)
Technical info
Used versions
The text was updated successfully, but these errors were encountered: