Make WordPress Core

#56801 closed defect (bug) (fixed)

array_key_exists error in wp_apply_custom_classname_support

Reported by: spacedmonkey's profile spacedmonkey Owned by:
Milestone: 6.1 Priority: normal
Severity: normal Version: 6.1
Component: Editor Keywords:
Focuses: Cc:



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.

17 months ago

#2 @desrosj
17 months ago

  • Keywords close added

This should be fixed in [54498]. Adding close awaiting confirmation.

#3 @hellofromTonya
17 months ago

  • Keywords needs-patch close removed
  • Resolution set to fixed
  • Status changed from new to 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.

Note: See TracTickets for help on using tickets.