#22246 closed defect (bug) (fixed)
PHP Notice On _remove_theme_support() function
| Reported by: | alex-ye | Owned by: | ryan |
|---|---|---|---|
| Priority: | normal | Milestone: | 3.5 |
| Component: | Warnings/Notices | Version: | 3.4.2 |
| Severity: | normal | Keywords: | has-patch |
| Cc: | Focuses: |
Description
Hi Guys , I just found this PHP Notice on _remove_theme_support() function , Tested On :
1 - WordPress 3.5 Beta 2
2 - PHP 5.4
To get this notice on just add child theme to TwentyTwelve and add this simple code on functions.php :
add_action ( 'after_setup_theme', 'Nash_setup' , 11 );
function Nash_setup() {
remove_theme_support ( 'custom-background' );
remove_theme_support ( 'custom-header' );
} // end Nash_setup()
Attachments (5)
Change History (18)
#4
@
14 years ago
- Resolution fixed
- Status closed → reopened
Rather than papering over the notices in [22274], we can bail in the particular situation where this occurs: When the "just in time" initialization hasn't occurred yet, we don't need to do anything beyond unsetting the item from the global array. See 22246.diff (made against pre-[22274]).
#9
@
14 years ago
- Resolution fixed
- Status closed → reopened
- Version 3.4.2
As I test the PHP notice is still exists even after Nacin patch .
I just add isset() function to check the array :)
![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png)
Using isset() to fix the bug