5 | | I didn't think about it this way. I wrote the code the way I did because I was thinking someone would want to know how long ago a plugin was updated so they could see if it is being supported or not. For example, I have worked in agencies in the past where they would audit a client's plugins to see if any plugins should be replaced due to a lack of updates. |
| 5 | I didn't think about it this way. I wrote the code the way I did because I was thinking someone would want to know how long ago a plugin was updated so they could see if it is being supported or not. For example, I have worked in agencies in the past where they would audit a client's plugins to see if any plugins should be replaced due to a lack of updates. |
| 6 | |
| 7 | Would it make sense to have some text to say "The plugin author last updated plugin: x years ago" or some more simple variant of that copy? Then we could save the "Last update: x ago" for when the person might have updated the plugin last? |