Conflict with Jetpack

Can you provide a stacktrace of the error?

I installed and activated Jetpack but don’t see any errors.

• This reply was modified 1 year ago by Andy Fragen.

Sorry, I don’t know what a stacktrace is.
I have deactivated Add Custom Header Images on my site, so it currently functions. If I reactivate it when Jetpack is also activated, I see a “Critical Error” message when I check on my phone. Luckily I can still access the back end on my laptop (which is how I tested the plugins).

Can you install and activate the WP Debugging plugin. You should be able to see a stacktrace.

• This reply was modified 1 year ago by Andy Fragen.

I have installed and activated the WP Debugging plugin, but I still don’t know what a stacktrace is, or what it looks like, or where to look to find it.

Any error will generate a stack trace and it should display on screen. You might need to change the WP Debugging setting to set the WP_FATAL_ERROR_HANDLER to true.

Sorry Andy, but your level of tech knowledge is way beyond me and means that I have no idea what to do or how to do it. It’s like you are speaking a different language. I’m a tech numpty and you will have to explain in the simplest of terms what you want me to do and how to go about doing it. Sorry to be so dense.

OK, I have gone into the settings for WP Debugging and set the WP_FATAL_ERROR_HANDLER to true. But I still don’t know how to get the information you require re: the stacktrace, because I still don’t know what a stacktrace is, or what it looks like, or how to find it / generate it.

The stacktrace should show as an on screen error with the error handler bypassed.

Here’s an example of a stacktrace. https://gist.github.com/afragen/284554b229dd9cb93b2fed344d99fb55

Hopefully this is what you need! I have copied the stacktrace information below:
Fatal error: Uncaught ValueError: Unknown format specifier “C” in /home2/modflowe/public_html/wp-includes/theme.php:1394 Stack trace: #0 /home2/modflowe/public_html/wp-includes/theme.php(1394): sprintf(‘https://i0.wp.c…’, ‘https://www.mod…’, ‘https://www.mod…’) #1 /home2/modflowe/public_html/wp-includes/theme.php(1412): _get_random_header_data() #2 /home2/modflowe/public_html/wp-includes/theme.php(1440): get_random_header_image() #3 /home2/modflowe/public_html/wp-includes/theme.php(1204): is_random_header_image() #4 /home2/modflowe/public_html/wp-content/themes/forever/inc/custom-header.php(44): get_header_image() #5 /home2/modflowe/public_html/wp-includes/class-wp-hook.php(324): forever_header_style(”) #6 /home2/modflowe/public_html/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(NULL, Array) #7 /home2/modflowe/public_html/wp-includes/plugin.php(517): WP_Hook->do_action(Array) #8 /home2/modflowe/public_html/wp-includes/general-template.php(3052): do_action(‘wp_head’) #9 /home2/modflowe/public_html/wp-content/themes/forever/header.php(35): wp_head() #10 /home2/modflowe/public_html/wp-includes/template.php(790): require_once(‘/home2/modflowe…’) #11 /home2/modflowe/public_html/wp-includes/template.php(725): load_template(‘/home2/modflowe…’, true, Array) #12 /home2/modflowe/public_html/wp-includes/general-template.php(48): locate_template(Array, true, true, Array) #13 /home2/modflowe/public_html/wp-content/themes/forever/nosidebar-page.php(11): get_header() #14 /home2/modflowe/public_html/wp-includes/template-loader.php(106): include(‘/home2/modflowe…’) #15 /home2/modflowe/public_html/wp-blog-header.php(19): require_once(‘/home2/modflowe…’) #16 /home2/modflowe/public_html/index.php(17): require(‘/home2/modflowe…’) #17 {main} thrown in?/home2/modflowe/public_html/wp-includes/theme.php?on line?1394

It seems that your theme has some ability to set a header image and that there is some conflict between this theme and the plugin.
The stacktrace doesn’t even show that the plugin code is being accessed.

That’s strange… I’ve had the plugin installed for ages and everything worked perfectly. The theme does allow me to set a header image, but I installed the plugin because when I installed one using the theme, the header image was always blurry. Using your plugin allowed me to upload a sharp, good quality image.

Also, there is no problem with Add Custom Header Images when Jetpack is deactivated, so I think the conflict must be with Jetpack, not the theme. I haven’t changed the theme but Jetpack periodically gets updated, so my guess is that the conflict has arisen because they have changed something about Jetpack in a recent update.
I guess I will have to choose between Add Custom Header Images and Jetpack!

It’s strange as the stacktrace only really references core and your theme.

I’m sorry I really don’t know what the issue is if I am unable to reproduce on my end.

• This reply was modified 12 months ago by Andy Fragen.

Ah well, thank you for trying. At least I now know what a stacktrace is!

I’m sorry. I wish I had a better answer.