Skip to main content

Timeline for Diagnosing plugin conflicts

Current License: CC BY-SA 3.0

6 events
when toggle format what by license comment
May 4, 2012 at 21:29 vote accept Pete
May 4, 2012 at 18:05 comment added Jeremy Jared Also, if you're using the DeBug feature you might consider using: if ( isset($_GET['debug']) && $_GET['debug'] == '1' ) { define('WP_DEBUG', true); } elseif ( isset($_GET['debug']) && $_GET['debug'] == '2' ) { define('WP_DEBUG', true); define('WP_DEBUG_DISPLAY', true); } elseif ( isset($_GET['debug']) && $_GET['debug'] == '3' ) { define('WP_DEBUG', true); define('WP_DEBUG_LOG', true); } instead of define('WP_DEBUG', true);. You can then see the errors by adding ?debug=1, or ?debug=2, or ?debug=3 to the end of the current pages URL.
May 4, 2012 at 18:00 comment added Jeremy Jared It shouldn't create a "big" performance drop, but it will cause more work on your server. If you have plenty of bandwith and processor speed you won't notice a difference. If you are already borderline on either, it could cause a noticeable change in performance. I'd be sure to monitor it closely at first.
May 4, 2012 at 17:30 comment added Pete Jeremy - would you say this is okay to run on a production site? Is it likely to cause a big performance drop?
May 4, 2012 at 13:03 comment added Pete That's great. I didn't realise you could log the errors without echoing them to the user. There's no error log in my WP directory, so I'll turn in on in wp-config like you suggest and give it a try, thanks.
May 4, 2012 at 12:46 history answered Jeremy Jared CC BY-SA 3.0