Ticket #50 (closed defect: fixed)

Opened 6 years ago

Last modified 15 months ago

MyChanges won't sort by timestamp

Reported by: anonymous Owned by: BrianKoontz
Priority: high Milestone: 1.3.1
Component: actions Version: 1.1.6.0
Severity: normal Keywords:
Cc:

Description (last modified by BrianKoontz) (diff)

The mychanges action does not properly sort by timestamp.

Status

draft of new action contributed by user - to be checked for security

Ref

 http://wikkawiki.org/MyChangesAction

Change History

Changed 6 years ago by dartar

  • milestone changed from 1.1.6.1 to 1.1.6.2

Changed 6 years ago by DarTar

  • owner changed from unassigned to DarTar
  • status changed from new to assigned

Changed 6 years ago by DarTar

  • priority changed from low to high
  • description modified (diff)
  • milestone changed from 1.1.6.2 to 1.1.6.3

Code contribution available.

To do:

Changed 6 years ago by DarTar

While trying to see if I could add the proposed code to the 1.1.6.2 codebase I bumped into an important issue. The code contributed by TimoK relies on MySQL methods (like DATE_FORMAT() that are incompatible with Wikka's minimal requirements (MySQL 3.23.X). So if we want to preserve backward-compatibility we'll need to find another solution.

Changed 5 years ago by BrianKoontz

I'm confused as to what this ticket refers to. The mychanges action appears to sort by timestamp correctly in trunk. Is the proposal to replace the current mychanges action code with that in  http://wikkawiki.org/UserChanges?

Changed 5 years ago by JavaWoman

  • description modified (diff)

It sorts by timestamp (correctly, if teh whole timestamp is take); what was intended (see  http://wikkawiki.org/MyChangesAction !) is a sort by day (without time) and within that by page name, and then by time within pagename: otherwise, if there are a lot of changes on a date, finding a particular page in that list isn't easy. With the proposed sorting pages are grouped together per day.

The trick is to find a workaround for DATE_FORMAT...

Then, UserChanges should implement the same method (it has the same problem MyChanges now has).

Changed 5 years ago by JavaWoman

Oh, and RecentChanges of course has the same problem - only more so!

Changed 3 years ago by DarTar

  • milestone changed from 1.2 to 1.3

Retargeting to 1.3. Code for this ticket may have already been committed to trunk, from which 1.3 will be branched. Consider backporting urgent issues to 1.2.X

Changed 2 years ago by BrianKoontz

(In [1617]) Sort by timestamp works as expected. Refs #50.

Changed 2 years ago by BrianKoontz

  • status changed from accepted to testing
  • description modified (diff)

Changed 2 years ago by BrianKoontz

  • status changed from testing to assigned

Changed 2 years ago by BrianKoontz

  • owner changed from DarTar to BrianKoontz

Changed 2 years ago by BrianKoontz

  • status changed from assigned to testing

Changed 2 years ago by DotMG

Testing, I'm lost at the spirit of this ticket, regarding comments by JavaWoman. If the intended behaviour is to sort by date (Y-M-D) then by Pagename, it's not yet what's happening.

Changed 2 years ago by BrianKoontz

  • status changed from testing to commit

JavaWoman's original assertion is invalid, because currently LoadRecentlyChanged() only returns pages that have 'Latest'=='Y'...this implies only one instance of a given page tag will ever be returned. I believe the description of this ticket was very straightforward: For whatever reason, pages weren't being sorted by timestamp. Now they are. I don't believe there's anything more to read into this. (The same argument applies to the MyChanges action.)

If, down the road, someone wants to change the functionality such that X latest edits are returned, and are sorted by day/tag/time, then a new enhancement ticket should be submitted.

Since the two lists of pages appear to be correctly sorted by timestamp, I'm closing this.

Changed 2 years ago by BrianKoontz

  • status changed from commit to closed
  • resolution set to fixed

Changed 15 months ago by BrianKoontz

  • milestone changed from 1.3 to 1.3.1

Updated milestone to 1.3.1

Note: See TracTickets for help on using tickets.