Project

General

Profile

Actions

Task #3638

closed

Extensions list by date is not consistent

Added by Jean-Francois Nifenecker almost 2 years ago. Updated over 1 year ago.

Status:
Closed
Priority:
Normal
Category:
-
Target version:
-
Start date:
Due date:
% Done:

0%

Tags:

Description

Hello,

the default extensions list is by descending dates. This default is very useful as one can easily find the newest extensions or updates in the very first pages.

Unfortunately, the list seems to be "polluted". When sequentially browsing the extension pages, one quickly find that many extensions seem to not be at their right place (this appears starting from page 3-4). This causes recent extensions to be randomly buried deep down the pages, among older ones, when one would expect them to be closer from the list start (and grouped). Thus, this forces browsing ALL the pages, which is inconvenient and contrary to the wanted list usability.

The cause of this mishap seems to come from an automated process of sorts used for the website management, that arbitrarily changes the last edition time. I see that many extensions have the "last edited: 2022-11-23" date. Such a number of extensions changed at the same date (by humans) seems highly improbable.

Please check the internal processes and don't let them change the last edited date. Otherwise, insert a new date field to store the actual extensions publication/update dates, that won't be unexpectedly modified.

This will make the list actually browsable by date. Thanks.

Actions #1

Updated by Jean-Francois Nifenecker almost 2 years ago

  • Description updated (diff)
Actions #2

Updated by Jean-Francois Nifenecker almost 2 years ago

  • Description updated (diff)
Actions #3

Updated by Jean-Francois Nifenecker almost 2 years ago

  • Description updated (diff)
Actions #4

Updated by Florian Effenberger almost 2 years ago

  • Assignee set to Christian Lohmaier
Actions #5

Updated by Christian Lohmaier over 1 year ago

  • Status changed from New to Resolved

there was some error in a maintenance script that caused timestamps to be modified - should be fixed now/for future.

Actions #6

Updated by Christian Lohmaier over 1 year ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF