#22246 closed defect (bug) (fixed)
PHP Notice On _remove_theme_support() function
Reported by: | alex-ye | Owned by: | ryan |
---|---|---|---|
Milestone: | 3.5 | Priority: | normal |
Severity: | normal | Version: | 3.4.2 |
Component: | Warnings/Notices | Keywords: | has-patch |
Focuses: | Cc: |
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)
#2
@
12 years ago
- Component changed from Themes to Warnings/Notices
- Milestone changed from Awaiting Review to 3.5
#3
@
12 years ago
- Owner set to ryan
- Resolution set to fixed
- Status changed from new to closed
In [22274]:
#4
@
12 years ago
- Resolution fixed deleted
- Status changed from closed to 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
@
12 years ago
- Resolution fixed deleted
- Status changed from closed to reopened
- Version 3.4.2 deleted
As I test the PHP notice is still exists even after Nacin patch .
I just add isset() function to check the array :)
Note: See
TracTickets for help on using
tickets.
Using isset() to fix the bug