[wp-trac] [WordPress Trac] #53076: Press This: Add filters to allow custom Press This plugins

WordPress Trac noreply at wordpress.org
Tue Oct 21 00:00:58 UTC 2025


#53076: Press This: Add filters to allow custom Press This plugins
-------------------------------------------------+-------------------------
 Reporter:  kraftbj                              |       Owner:
                                                 |  westonruter
     Type:  enhancement                          |      Status:  closed
 Priority:  normal                               |   Milestone:  6.9
Component:  Editor                               |     Version:
 Severity:  normal                               |  Resolution:  fixed
 Keywords:  has-test-info has-patch has-dev-     |     Focuses:
  note reporter-feedback                         |
-------------------------------------------------+-------------------------
Changes (by desrosj):

 * keywords:  has-test-info has-patch has-dev-note => has-test-info has-
     patch has-dev-note reporter-feedback


Comment:

 Replying to [comment:21 desrosj]:
 > Right now the reasoning is a bit unclear. Does this change unblock
 something for the plugin? Is there actual A/B testing going on? Are these
 theoretical scenarios, or are users actually doing this?

 I think it’s still worth getting additional clarity around the value this
 provides to users. I’m not convinced that this benefits a large number of
 users, never mind the 80/20 rule. While that’s not a steadfast rule,
 understanding the reasons behind the request would help to better
 understand the rationale.

 This was a feature that was moved to a canonical plugin in 4.9, so it’s
 been 20 releases now without much demand to add it back (6,000+ installs).
 Is there no way to accomplish this through an early filter in the plugin
 itself instead?

 I also disagree that this is worthy of a dev note at all. The new hook
 should be mentioned in a list of new hooks, or in the miscellaneous
 developer focused changes note. It’s important that we carefully consider
 which changes deserve their own post to avoid too much noise that offers
 very little value which can result in developers unsubscribing entirely.

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


More information about the wp-trac mailing list