WPIntell

Source evidence

DebugThis not working – Fatal error

Debug This · support · 2014-08-27T20:31:00+00:00

complaintsentiment
highseverity
1.0relevance
4replies
Evidence linked to opportunitycommercial context

Proof Health

Open evidence

Commercial opportunities need traceable source links before they are treated as build-worthy.

6 / 35 rows with source links

17.1% of this page's analysis has direct source links.

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

29 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support
Paddy Duncan unresolved
DebugThis produces the following when ANY debug option is selected: Fatal error: Cannot use object of type WP_Error as array in /home2/llnews/public_html/wp-content/plugins/debug-this/debug-this.php on line 183 Site is http://leasidelifenews.com running latest version of WP and Thesis. https://wordpress.org/plugins/debug-this/ I’ve removed the plugin as it wasn’t working at all – but would still like to see an answer as this issue has come up before and I haven’t seen satisfactory responses. I’m getting the same error, using nginx and php-fpm if that makes any difference: PHP message: PHP Fatal error: Cannot use object of type WP_Error as array in /var/www/free/wp-content/plugins/debug-this/debug-this.php on line 183 There is a message in this forum from a year ago where the developer said he would look into it, but i don’t see a fix and that thread was closed. Hi guys, I’m the new maintainer of Debug This. I have been unable to reproduce this error though I do see it around various support forums which seems to indicate a variety of possible causes. I suspect this is a conflict with another plugin that applies filters to the various parts of the WordPress Http object; filters that can be accounted for once they are known. If you are interested in helping, I will create a version that catches the error and logs the object and filters. You can then send that log to me for examination. If not, I understand. Please let me know if you are using another debugging plugin so I can see if and how they handle things. Chris Chris… I really appreciate you reaching out and trying to get this fixed. I don’t have a huge amount of time to spend on this, but I want to be a good community member, so I will assist as much as I can. The issue I ran into was actually with Permalinks, where I just had to re-save the Permalinks setting in WP Admin (even though it looked okay), but it was difficult to debug since I couldn’t even tell what queries were running. I don’t have much WP coding experience, but mostly manage deployment, a programming team, and client relations. The server we used 6 months ago has been rebuilt and no longer uses nginx, so it may not be that easy to replicate. I have other servers that run nginx though so we can at least see if that’s the issue. Get me a copy of the plugin to test with and some basic tests to run through and I’ll see if I can recreate the issue.

Comments

4 shown
Paddy Duncan 2014-08-28T04:24:00+00:00

I’ve removed the plugin as it wasn’t working at all – but would still like to see an answer as this issue has come up before and I haven’t seen satisfactory responses.

joe hobson 2014-09-19T18:28:00+00:00

I’m getting the same error, using nginx and php-fpm if that makes any difference: PHP message: PHP Fatal error: Cannot use object of type WP_Error as array in /var/www/free/wp-content/plugins/debug-this/debug-this.php on line 183 There is a message in this forum from a year ago where the developer said he would look into it, but i don’t see a fix and that thread was closed.

cdillon27 2015-04-17T12:15:00+00:00

Hi guys, I’m the new maintainer of Debug This. I have been unable to reproduce this error though I do see it around various support forums which seems to indicate a variety of possible causes. I suspect this is a conflict with another plugin that applies filters to the various parts of the WordPress Http object; filters that can be accounted for once they are known. If you are interested in helping, I will create a version that catches the error and logs the object and filters. You can then send that log to me for examination. If not, I understand. Please let me know if you are using another debugging plugin so I can see if and how they handle things. Chris

joe hobson 2015-04-17T15:11:00+00:00

Chris… I really appreciate you reaching out and trying to get this fixed. I don’t have a huge amount of time to spend on this, but I want to be a good community member, so I will assist as much as I can. The issue I ran into was actually with Permalinks, where I just had to re-save the Permalinks setting in WP Admin (even though it looked okay), but it was difficult to debug since I couldn’t even tell what queries were running. I don’t have much WP coding experience, but mostly manage deployment, a programming team, and client relations. The server we used 6 months ago has been rebuilt and no longer uses nginx, so it may not be that easy to replicate. I have other servers that run nginx though so we can at least see if that’s the issue. Get me a copy of the plugin to test with and some basic tests to run through and I’ll see if I can recreate the issue.