[ad_1]
Same issue on two websites here.
Can’t reproduce yet, but possibly it is related to an optimiser mu-plugin. Can you try removing the following lines in mu-plugins?rsssl_rest_api_optimizer.php?
require_once( ABSPATH . 'wp-includes/pluggable.php' );
if ( !isset($_SERVER['HTTP_X_WP_NONCE']) || !wp_verify_nonce($_SERVER['HTTP_X_WP_NONCE'], 'wp_rest') ) {
return $plugins;
}Let me know if that works.
Can you try this branch?
Thread Starter
George
(@giorgos93)
@rogierlankhorst yes, deleting these lines did help! Just in case, I returned everything back. And speaking of Github branch – I don’t know what to do there, tbh. I am not a programmer 🙂
After deleting the lines, all errors in Dev Console disappeared. And I don’t know if it has to be like that, but I have only 64% progress with this version. Last version had 95%.
@giorgos93 thanks so much for confirming the fix!
As for your progress: this has to do with our new hardening features. You can choose to enable them, or dismiss if you don’t need them.
The fix will be released as 6.0.2 within 30 minutes on WordPress.
@giorgos93 @iamjonasmarlo 6.0.2 has been released, which includes a fix for this issue. Let me know if you have any other questions.
