Try adding define( 'SCRIPT_DEBUG', true ); to wp-config.php, it worked for us. I’d appreciate it if you could let me know if it worked for you.
Added but not working. What could be wrong?
Maybe you also need to turn on debug mode by adding define('WP_DEBUG', true);
Your code should be like this:
define('WP_DEBUG', true);
// Enable Debug logging to the /wp-content/debug.log file
define( 'WP_DEBUG_LOG', false );
// Disable display of errors and warnings
define( 'WP_DEBUG_DISPLAY', false );
// Use dev versions of core JS and CSS files (only needed if you are modifying these core files)
define( 'SCRIPT_DEBUG', true );
If you want to see logs you also should set true WP_DEBUG_LOG or WP_DEBUG_DISPLAY to see errors on page. Documentation – https://developer.wordpress.org/advanced-administration/debug/debug-wordpress/
I used the code you suggested, and now I can post again. It’s working, but I don’t understand why, as this code is meant for error logging. Where would the errors be displayed? Can I leave the code like this permanently?
Debugging mode loads the ‘dev’ versions of core CSS and JavaScript files instead of the minified versions. Thus, the conclusion is that the bug appeared during minification.
I use WP Rocket for caching, so could it be that the plugin is causing a conflict?
On the other hand, should I change the code you provided? If so, how can I reapply it to test if disabling WP Rocket resolves the issue?
I don’t think the plugin is the cause here. But to check, you can use a guide – https://wordpress.org/support/topic/read-this-first-wordpress-master-list/#post-14157464. Also, make sure to set false to disable debug mode.
My solution is temporary, so we must wait for a new version of WordPress to fix this bug.
So, I understand that the code to revert it to how it was before would be the following?
define('WP_DEBUG', false);
// Enable Debug logging to the /wp-content/debug.log file
define( 'WP_DEBUG_LOG', false );
// Disable display of errors and warnings
define( 'WP_DEBUG_DISPLAY', false );
// Use dev versions of core JS and CSS files (only needed if you are modifying these core files)
define( 'SCRIPT_DEBUG', false);
All false? Thank you for your help!!!
Thank you very much, this trick saved my life too with the same blank editor page problemn after 6.7 update. Nor plugin turning off or default theme helped but this line in wp-config:
define( ‘SCRIPT_DEBUG’, false);
I’m glad this trick helped you too! I hope an update fixes this issue soon. Is there any report on this problem?
Hello, I have the same problem and I don’t know how to solve it 🙁
@westzonetm Did you try the code shared earlier in the post?
