There's always a 'newer' version

Question

There's always a 'newer' version

Opened this issue 6 years ago · 4 comments

j0hannes commented 6 years ago

The template page says Update: New version 2017-06-20 is available.

Answer 1 · 2018-10-04T14:15:18.000Z

You can address this by opening template.info.txt and changing the date field to 2017-06-20.

Answer 2 · 2018-10-04T17:34:37.000Z

Thanks!

Shouldn't this be done best by the maintainer in the repo?

Answer 3 · 2018-10-04T18:14:12.000Z

Yes, although I'm not sure if it would then be necessary to make the date current to reflect that the date was changed.

Answer 4 · 2018-10-08T10:25:47.000Z

This is the only template that always appeared as outdated (before I made the changes manually), no matter how often the update was performed, which is comprehensible if the new version holds the data of an our version and this date is used to determine upgradable templates (and plugins).