Error in Customizer Mode

QuestionsCategory: Error MessagesError in Customizer Mode
Stacey Allison asked 4 years ago

***

I have resolved this issue!!! My wp-config.php file had the debugging option set to “true”. I”m not sure how or why it was set to that but I set it to false and it’s all lovely now. 🙂

 

 

 

When I am using the Customizer, the top of my view shows the following error:
WP_Customize_Image_Control::add_tab is deprecated since version 4.1.0 with no alternative available
Then it lists the following file: functions.php in line 3899
I have tried deactivating all of my plugins to see if that was the issue but still get the message. I just switched to Hello Boho after using StudioPress’ Minimal Theme. I did not have the problem with the StudioPress theme. I have decent hosting, memory, permissions, and the most up-to-date php version on my server.
Any help would be appreciated.

Here is the WordPress code the error is referring to:

if ( WP_DEBUG && apply_filters( ‘deprecated_function_trigger_error’, true ) ) {
if ( function_exists( ‘__’ ) ) {
if ( ! is_null( $replacement ) ) {
/* translators: 1: PHP function name, 2: version number, 3: alternative function name */
trigger_error( sprintf( __(‘%1$s is <strong>deprecated</strong> since version %2$s! Use %3$s instead.’), $function, $version, $replacement ) );
} else {
/* translators: 1: PHP function name, 2: version number */
trigger_error( sprintf( __(‘%1$s is <strong>deprecated</strong> since version %2$s with no alternative available.’), $function, $version ) );
}
} else {
if ( ! is_null( $replacement ) ) {
trigger_error( sprintf( ‘%1$s is <strong>deprecated</strong> since version %2$s! Use %3$s instead.’, $function, $version, $replacement ) );
} else {
trigger_error( sprintf( ‘%1$s is <strong>deprecated</strong> since version %2$s with no alternative available.’, $function, $version ) );
}
}
}
}

Thank you!

Support Team Staff replied 4 years ago

Can you email your URL and a login to support@helloyoudesigns.com Who are you currently hosting with?

Support Team Staff replied 4 years ago

Oh awesome! Very happy this is resolved.