Articles: Illogical sorting by size
- Status
- Open
- Subject
- Articles: Illogical sorting by size
- Version
- 18.x
- Category
- Less than 30-minutes fix
- Bug
- Easy for Newbie Dev
- Feature
- Article
- Resolution status
- New
- Submitted by
- hman
- Lastmod by
- hman
- Rating
- Related-to
- Description
When you sort a listing of articles, you can have the results sorted on the size of the articles. But the result is illogical, which is more visible when sorting descending, but in principle ascending is affected as well: The sorting is done NOT numerical (which you would expect on a numerical value like size), but by string representation.
The result is e.g. that "456 bytes" is being considered larger than "1.2 kBytes"...
- Importance
- 5
- Easy to solve?
- 10 easy
- Priority
- 50
- Demonstrate Bug (Tiki 19+)
-
This bug has been demonstrated on show2.tiki.org
Please demonstrate your bug on show2.tiki.org
Version: Create show2.tiki.org instanceAbout show2.tiki.orgTo help developers solve the bug, we kindly request that you demonstrate your bug on a show2.tiki.org instance. To start, simply select a version and click on "Create show2.tiki.org instance". Once the instance is ready (in a minute or two), as indicated in the status window below, you can then access that instance, login (the initial admin username/password is "admin") and configure the Tiki to demonstrate your bug. Priority will be given to bugs that have been demonstrated on show2.tiki.org.
- Ticket ID
- 7958
- Created
- Tuesday 30 November, 2021 14:30:00 GMT-0000
by hman - LastModif
- Tuesday 30 November, 2021 14:33:07 GMT-0000
Attachments
| filename | created | hits | comment | version | filetype | ||
|---|---|---|---|---|---|---|---|
| No attachments for this item | |||||||
;){kind=link}
;){kind=link}
- Threaded comment listing sort order
- fresh opening of tiki home page tiki-index (I removed a warning) is it OK
- Tracker with field type "Numeric" won't
- tiki 25.1 Database 'xxxx'. Unable to connect to database (when 25.0 will connect)
- Kanban plugin; the Swimlane field throw an error if using a category field type
;){kind=link}
;){kind=link}