#21515 closed defect (bug) (fixed)
No custom header support in theme == Fatal error: Call to a member function process_default_headers() on a non-object
| Reported by: | c3mdigital | Owned by: | ryan |
|---|---|---|---|
| Priority: | normal | Milestone: | 3.4.2 |
| Component: | Customize | Version: | |
| Severity: | normal | Keywords: | has-patch commit |
| Cc: | Focuses: |
Description
In 3.5 (21468).
Using the customizer on a theme without custom header support causes fatal error.
Fatal error: Call to a member function process_default_headers() on a non-object in /Users/chris/Sites/newpatch/wp-includes/class-wp-customize-control.php on line 759
Call Stack
# Time Memory Function Location
1 0.0012 287640 {main}( ) ../customize.php:0
2 0.3554 19316040 do_action( ) ../customize.php:34
3 0.3554 19317640 call_user_func_array ( ) ../plugin.php:406
4 0.3555 19317672 WP_Customize_Header_Image_Control->prepare_control( ) ../plugin.php:406
var_dump( $custom_image_header ) results in NULL when theme does not have custom header support.
Simple solution that fixes fatal error is a check on the object variable and return if empty.
Attachments (2)
Change History (9)
#6
@
14 years ago
Seems like a similar problem:
When I activate the 2011 theme and click Customize, it brings up a left-side menu column and a right-side preview of the website.
When I activate an older theme of my own that does not support the new features, it brings up a left-side menu column only, and then continuously auto-refreshes the page until I close it. There are no errors being generated.
Do you need a new ticket for that?
![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png)
Introduced in [21383].