[wp-trac] [WordPress Trac] #65116: Feature request: On This Day dashboard widget

WordPress Trac noreply at wordpress.org
Fri Apr 24 12:56:38 UTC 2026


#65116: Feature request: On This Day dashboard widget
-------------------------+-------------------------------------------------
 Reporter:  alshakero    |       Owner:  (none)
     Type:  feature      |      Status:  new
  request                |
 Priority:  normal       |   Milestone:  Awaiting Review
Component:  Widgets      |     Version:  trunk
 Severity:  minor        |  Resolution:
 Keywords:  has-patch    |     Focuses:  ui, administration, sustainability
-------------------------+-------------------------------------------------

Comment (by alshakero):

 Replying to [comment:7 eclev91]:

 Hi there!

 > So not ''that'' much excitement.

 Well it is picked up now 😄 FWIW, I genuinely think it is cool and useful
 and I proposed it without knowing about the past discussions about it.

 > But this widget creates an additional query on the dashboard and loads
 yet another stylesheet, which is far from the experience I want on the
 dashboard if I'm making it my own.

 I hear you and I really want wp-admin to be fast. That's why the widget
 does one query per day unless you modify your posts. It's heavily cached;
 even the HTML generation is cached for the duration of the day. When it's
 cached, it doesn't do any DB connections at all.

 The CSS is 1.9 KB gzipped and is cached across days. I don't think it will
 move the needle at all.

 > It's relevant to one subset of users and contributing to a noise problem
 for the rest.

 For those who don't want it, I think the only noise is the checkbox in the
 screen options. Is that a lot? This plugin will also only register for
 those who can edit posts.

 >
 > I'm far from well plugged into core development, and the code is already
 written, but can this at least be something you opt into rather than have
 to disable on sites where it's irrelevant?

 > Can this at least be something you opt into rather than have to disable
 on sites where it's irrelevant?

 I'm totally open to both options. I did try to make it opt-in and it seems
 the architecture doesn't support that by default and I would have to do
 some trickery, still open it it nonetheless.

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


More information about the wp-trac mailing list