Opened 4 years ago
Closed 4 years ago
#56801 closed defect (bug) (fixed)
array_key_exists error in wp_apply_custom_classname_support
| Reported by: | spacedmonkey | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | 6.1 |
| Component: | Editor | Version: | 6.1 |
| Severity: | normal | Keywords: | |
| Cc: | Focuses: |
Description
wp-includes/block-supports/custom-classname.php:48
array_key_exists() expects parameter 2 to be array, null given
Change History (3)
This ticket was mentioned in Slack in #core by desrosj. View the logs.
4 years ago
#3
@
4 years ago
- Keywords needs-patch close removed
- Resolution → fixed
- Status new → closed
Changeset [54498] resolved this ticket too. Why? Before [54498], the 2nd parameter of wp_apply_custom_classname_support() was null when a block did not declare attributes. In WP 6.1, the attributes of core/page-list were removed, highlighting this problem.
Is a fix needed for this ticket? No.
Why? wp_apply_custom_classname_support() expects an array data type, not null. The issue noted in #56799 resulted in an invalid data type being passed to it.
I'll close this ticket as fixed.
![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png)
This should be fixed in [54498]. Adding
closeawaiting confirmation.