Comments on: Deprecated functions and WP_DEBUG

By: Chavonne

Chavonne — Mon, 12 Dec 2011 19:16:15 +0000

Im scanning through all the tutorials and blogs I can find re why the whole WordPress website/ blog that I am looking after is throwing errors.(front-end and back end) It is rellay annoying and my php knowledge is limited. Is there in any way a solution to simple web-developer like me to understand and fix this broken site

By: bhaskar

bhaskar — Tue, 25 Oct 2011 00:41:29 +0000

You dont need debug options for fatal error.
Your website will tell that to you in most clear words

By: Ian Douglas

Ian Douglas — Fri, 02 Sep 2011 23:05:22 +0000

seems my code disappeared there. Let me try again to give the first line of header.php as an example

By: Ian Douglas

Ian Douglas — Fri, 02 Sep 2011 23:03:47 +0000

I find code hard, so please forgive this question:

What do I do with the deprecated calls your plugin reports? I seem to have around 450 across the theme (300+) and plugins (the remainder) used in my site. For example, I have the following:

Function: get_settings()
Used in wp-content/themes/wp-prosper/header.php on line 1.
Use get_option() instead.
Deprecated in version 2.1

This is line 1 of that file:

So could I replace get_settings in the above line with get_options and it would clear the warning and be more efficient? Or would this break the theme? Is this something I need the theme creator to address?

For efficiency sake, I’m trying to clean up my WordPress install.

thanks for any input

By: What Lurks in the WordPress Plugin Repository?

What Lurks in the WordPress Plugin Repository? — Wed, 10 Aug 2011 13:33:37 +0000

[...] what Nacin had to say on his blog about deprecated functions: Deprecated functions cannot be relied upon to work efficiently or correctly and may be disabled by [...]

By: Lee Grey

Lee Grey — Mon, 07 Mar 2011 01:50:28 +0000

Every site shows how to turn debugging on, but I can’t find anyplace that tells me how to emit something to the log. How can I write my own message into the log?

By: Rizal

Rizal — Wed, 23 Feb 2011 13:00:06 +0000

hi i have a problem, where is trouble :

Fatal error: Cannot redeclare username_exists() (previously declared in /home/buanacom/public_html/komputerbekas/wp-includes/registration.php:16) in /home/buanacom/public_html/komputerbekas/wp-includes/registration.php on line 22

please help me

By: Dave Donaldson

Dave Donaldson — Tue, 15 Feb 2011 19:21:36 +0000

Hi Andrew, For WP 3.0 and beyond, is the @ini_set('display_errors', 0); line needed if WP_DEBUG_DISPLAY is set to false? Just wondering because when I set WP_DEBUG_DISPLAY to false and comment out @ini_set('display_errors', 0);, I don't see a difference versus when I leave it in there. I also did a little spelunking and in the load.php file on line 264 (WP 3.0.5) there is a check on WP_DEBUG_DISPLAY that then sets 'display_errors' to 1 if true. If you added the else statement to that check, to set 'display_errors' to 0, wouldn't that eliminate the need for putting @ini_set('display_errors', 0); in wp-config.php entirely? --Dave

By: Deryk

Deryk — Thu, 10 Feb 2011 16:03:48 +0000

Is there a way to just show Fatal errors and ignore the warnings? On my development platform, whenever I suspect a fatal error, I need to turn wp_debug to true to see the error. I leave it off by default, otherwise I see too many notices I don’t need to see. Thanks.

By: Philipp

Philipp — Thu, 08 Jul 2010 13:39:45 +0000

Nice! That phrase is what made me activate it and give it a try.