Make WordPress Core

Opened 5 weeks ago

Last modified 2 weeks ago

#62332 new feature request

Display last update on plugins page in WordPress backend

Reported by: tonikasch's profile tonikasch Owned by:
Milestone: Awaiting Review Priority: normal
Severity: normal Version:
Component: Plugins Keywords: has-patch
Focuses: administration Cc:

Description

Hi,

I think it would be awesome that WordPress displayed the date a plugin was last updated in order to manage plugins that are not updated over versions and over several months.

I know that now a notice will appear when a plugin is classified as "not maintained" but I think many plugins take a time before they are classified as such. That is why this proposal of last plugin update.

Regards

Change History (7)

#1 @swissspidy
5 weeks ago

  • Focuses administration added; performance sustainability removed

#2 @boogah
5 weeks ago

Happy to offer up my plugin — which shows when a plugin was last updated and even offers a Site Health Check — for use here as I clearly think this is a feature worth spending dev time on. 😉

https://wordpress.org/plugins/plu-redux/

#3 @tonikasch
5 weeks ago

  • Focuses performance sustainability added; administration removed

Thanks @boogah.
Your plugin is the best approach.
I would only lower the trigger from 2 years to 6 months or otherwise add another trigger on a 6-month basis.
Glad you have created a plugin like yours.

Regards

#4 @benniledl
5 weeks ago

I don’t believe that introducing a health check based on the last updated time of plugins is beneficial. Such a security message could unnecessarily alarm users, prompting them to replace plugins and potentially waste hours of their time. The fact that a plugin hasn’t been updated for more than six months does not inherently indicate a security issue.

For example, consider the Hello Dolly plugin, which is included by default in WordPress and hasn’t been updated in 12 months. This would result in every new WordPress user encountering a "security" warning after a fresh installation, which is far from ideal. Imagine setting up WordPress for the first time and being met with a security alert.

Or consider https://wordpress.org/plugins/tinymce-advanced/ last updated 7 months ago and 2+ million active installations.

A longer threshold would be more reasonable, in my opinion, however, setting such a threshold could lead users to believe that it applies universally to all plugins, causing them to think it’s acceptable to install a plugin that hasn’t been updated for, say, 18 months, even though this is not a straightforward matter and should be assessed on a case-by-case basis.

Last edited 5 weeks ago by benniledl (previous) (diff)

This ticket was mentioned in Slack in #core-performance by mukeshpanchal27. View the logs.


5 weeks ago

#6 @mukesh27
5 weeks ago

  • Focuses administration added; performance sustainability removed

This ticket was discuss in performance bug scrub.

It's not a performance issue so removing the keywords.

This ticket was mentioned in PR #7874 on WordPress/wordpress-develop by @benazeer.


2 weeks ago
#7

  • Keywords has-patch added

Trac ticket: https://core.trac.wordpress.org/ticket/62332

### Description

This PR adds last updated details of the plugins.

### Expected behaviour

On the plugin listing page, a new column titled "Last Updated" will be displayed, showing the date of the most recent update.

### Screenshots/Screencasts

https://github.com/user-attachments/assets/5cd34b86-6785-4c0a-a28e-80d5e708f1bd

Note: See TracTickets for help on using tickets.