Well, it was a plugin after all. Since several activated plugins seemed to trigger the error, I thought What is a common plugin here? It turns out that admin-language was the culprit. With hindsight, that may no be a surprise: that page says: This plugin hasn’t been tested with the latest 3 major releases of … Read more
Did you try var_dump on the array_merge & avatar parameters? That would tell you if the variables are what you expect. Anyway – it looks like you have the parameter order wrong. You are using custom_comment( $comment, $depth, $args ) but it should be custom_comment( $comment, $args, $depth ) Hope that helps
Warning Before you get started, I highly recommend you to create a child theme to safely modify the current theme you’re using. That way, if you need to update your theme, your changes won’t be overwritten. Modifying your current error page If your theme already has a custom error page, look for a 404.php file … Read more
The reason of such behavior is that you’ve installed your WP in /wordpress subdirectory, so that’s exactly where it works. And since the root directory is empty (no index.php nor .htaccess files are in there) you get 403 error, when requesting domain root. So how to fix it? Connect to your ftp server and move … Read more
There are many reasons this error can occur. Those two were the most frequent for me: Session-Cookie Open the Javascript Console by pressing F12 and click on the tab “Console”. If you see some error message that goes something like cookie_nonce it’s a session cookie problem. The problem solves by just completely logging out and … Read more
REST API should always return JSON, so it’s output can be parsed as such. If it’ll return something that is not correct JSON, then your JS scripts may stop working. This is why there should be no errors printed in these requests – such messages break JSON response and make it hard to parse. And … Read more
I dug in the codex and found some interesting functions. This is how I finally did it : function api_request($api_url = null, $params=null,$method = ‘GET’){ if (!$api_url){ return new WP_Error(‘no_api_url’,”Missing API URL”); } //Create request $request = WP_REST_Request::from_url( $api_url ); //Method $request->set_method( $method ); //params switch($method){ case ‘GET’: $request->set_query_params($params); break; case ‘POST’: $request->set_body_params($params); break; } … Read more
You might just need to flush permalinks. (Navigate to Settings > Permalinks and click “Save Changes”) If you can’t navigate to the permalinks page because of the error, you could try one of the other suggestions here Obviously make a backup of your database before performing any of them. If that doesn’t work there may … Read more
Just coming back to this. Unfortunately, the client had provided us with an incorrect copy of the site and whilst all the necessary files were in place and looked OK, this was the cause of the issue.
If anyone encounters this warning and cannot hide it with changing the line in wp-config.php from true to false , replace define(‘WP_DEBUG’, false); or define(‘WP_DEBUG’, true); with this : ini_set(‘display_errors’,’Off’); ini_set(‘error_reporting’, E_ALL ); define(‘WP_DEBUG’, false); define(‘WP_DEBUG_DISPLAY’, false); It helped me, so I hope it will help you also 😉