[wp-trac] [WordPress Trac] #47357: $allowedentitynames could be null

[WordPress Trac]

#47357: $allowedentitynames could be null
-------------------------------------+-----------------------
 Reporter:  doctorlai                |       Owner:  (none)
     Type:  defect (bug)             |      Status:  reopened
 Priority:  normal                   |   Milestone:  6.1
Component:  Formatting               |     Version:
 Severity:  normal                   |  Resolution:
 Keywords:  has-patch needs-testing  |     Focuses:
-------------------------------------+-----------------------

Comment (by bosconiandynamics):

 I think that this is a very beneficial change.

 I'm not positive, but I think that the immediately previous confusion may
 have been the result of a third-party plugin having previously required
 the end-user to set `CUSTOM_TAGS`, then later updating to implement their
 functionality to leverage a `'wp_kses_allowed_html'` filter instead and
 not implementing an end-user notice to relay the importance of removing
 the `CUSTOM_TAGS` definition, or any backwards-compatibility functionality
 to assist the transition.

 The changes in the diff remove a lot of burden from third-party developers
 who might as of yet still be relying on the `CUSTOM_TAGS` constant and
 significantly improves the experience and troubleshooting capabilities for
 end-users.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/47357#comment:11>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform