-
Notifications
You must be signed in to change notification settings - Fork 0
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
Fatal error: Uncaught TypeError: explode() in class-wp-dependencies.php:187 #84
Comments
Updating to Gutenberg 14.4.0 seemed to resolve the issue. |
I retested after updating to WordPress 6.1-RC5.
|
The stack trace for the first warning C:\apache\htdocs\wordpress\wp-content\plugins\oik-bwtrace\includes\bwtrace-actions.php(286:2) bw_trace_error_handler(1) 219 24 2022-10-31T21:19:52+00:00 2.758449 0.023853 cf=block_editor_settings_all 76280 168 10266 18874368/18874368 512M F=1303 err Array
is most likely related to the fact that the
and
In WP 6.1-RC5 if In WP 6.1-RC3 it called I believe I've found the original issue. WordPress/gutenberg#45301 |
compared with the logic in
|
Today, while updating the block docs for WordPress 6.1 I got a Fatal error when attempting to edit
https://blocks.wp.a2z/block/no-results-core-query-no-results/
Gutenberg version: 14.1.1.
Latest version of Gutenberg is 14.4.0
Warning: Array to string conversion in C:\apache\htdocs\wordpress\wp-content\plugins\gutenberg\lib\compat\wordpress-6.0\client-assets.php on line 76
Warning: Array to string conversion in C:\apache\htdocs\wordpress\wp-content\plugins\gutenberg\lib\compat\wordpress-6.0\client-assets.php on line 76
Fatal error: Uncaught TypeError: explode(): Argument #2 ($string) must be of type string, array given in C:\apache\htdocs\wp-a2z\wp-includes\class-wp-dependencies.php:187
The text was updated successfully, but these errors were encountered: