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

WordPress Trac noreply at wordpress.org
Sat Jul 30 23:36:49 UTC 2022

#47357: $allowedentitynames could be null
 Reporter:  doctorlai     |       Owner:  (none)
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:
Component:  Formatting    |     Version:
 Severity:  normal        |  Resolution:  wontfix
 Keywords:                |     Focuses:
Changes (by bosconiandynamics):

 * status:  reopened => closed
 * resolution:   => wontfix


 Replying to [comment:5 KnowingArt_com]:
 > FWIW I have define( 'CUSTOM_TAGS', true ); on this blog. Is that
 supposed to crash WordPress? LOL

 If `CUSTOM_TAGS` is set, WordPress expects that third-party code will
 provide a substitution for the `$allowedentitynames` global. If no
 substitution is provided, then `$allowedentitynames` will remain unset,
 triggering this error. This is an intended behavior as mentioned by @pento

 `CUSTOM_TAGS` was soft deprecated in WordPress 3.5 - it is recommended to
 use the `'wp_kses_allowed_html'` filter instead.

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

More information about the wp-trac mailing list