[wp-trac] [WordPress Trac] #32544: No function exposes all supported MIME types

WordPress Trac noreply at wordpress.org
Sun May 18 00:18:19 UTC 2025


#32544: No function exposes all supported MIME types
-----------------------------------+------------------------
 Reporter:  dan.rossiter           |       Owner:  octalmage
     Type:  enhancement            |      Status:  assigned
 Priority:  low                    |   Milestone:
Component:  Media                  |     Version:  4.2.2
 Severity:  normal                 |  Resolution:
 Keywords:  close needs-test-info  |     Focuses:
-----------------------------------+------------------------
Changes (by SirLouen):

 * keywords:  good-first-bug has-patch has-unit-tests needs-testing => close
     needs-test-info


Comment:

 I'm reading this, and I can't figure out any sense: As @ipm-frommen
 suggested, the idea is flawed from the beginning; and then
 [https://core.trac.wordpress.org/ticket/32544#comment:6 reporter proposed
 a new stunt] but did not provide the exact code to prove and test that
 stunt (to me the comment is like: "do a triple reversed somersault and
 there you have it")

 The [https://core.trac.wordpress.org/attachment/ticket/32544/32544.diff
 current patch] pretends that plugin developers, start using that logic to
 permit a full display of all unfiltered mime types for any use-case that
 is not even clear. But this is not what the reporter is asking for: he
 wants full-access regardless of the decisions of individual plugin
 developers, to restructure (and potentially generate security concerns)
 the whole function, so user filtering can be completely bypassed on call.

 On top of this, johnbillion 10 years ago, believed that this was a `good-
 first-bug` which is not (in fact, as @ipm-frommen I'm also doubting if
 implementing the enhancement in this report is a good idea at all)

 Personally, I would preemptively consider this a `close` candidate for
 `wontfix` unless the reporter (unlikely, 10 years later) provides
 additional information about the full use-case (not just the flawed piece
 of code in a recursive endless loop that was provided in the OP)

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


More information about the wp-trac mailing list