View Issue Details

IDProjectCategoryView StatusLast Update
0005666Composrcorepublic2024-08-12 22:29
ReporterPatrick SchmalstigAssigned ToPatrick Schmalstig 
SeverityTrivial-bug 
Status assignedResolutionwon't fix 
Product Version10.0.47 
Fixed in Version 
Summary0005666: Support seconds in Add date / Edit date metadata fields
DescriptionI just found an odd bug in Composr v10 which also likely exists in v11.

Let's say user A makes a forum post at 12:00:01 AM. User B makes a forum post at 12:00:46 AM (Note the third number is seconds). Posts show up in the correct order... A followed by B. But if B goes and edits their post, because the add/edit time does not have seconds in it, the seconds get dropped and so the effective times get changed to 12:00:00 AM. This then causes the order of the posts to be User B followed by user A. Oops!

The date/time fields for metadata add and edit times need to support seconds and maintain them on edit.
TagsRoadmap: v11
Time estimation (hours)
Sponsorship open

Activities

Patrick Schmalstig

2024-04-12 18:58

administrator   ~0008575

This would be very complicated to do; I don't think a seconds field is standard in web browsers for a time input. Would also require major API refactoring.

Patrick Schmalstig

2024-06-07 03:32

administrator   ~0008824

Last edited: 2024-06-07 03:33

View 2 revisions

Re-opening because I think this is an issue considerable enough that we need to come up with a solution. It is not practical and very unfriendly to have forum posts changing order when this happens.

Suggestion: Add / attach seconds as a hidden value on the edit screen. Maintain the seconds value on save (even if the minutes / hours are changed). Do this on all time fields, and make sure getting dates from post/get params also looks for this special hidden value.

Patrick Schmalstig

2024-08-12 22:29

administrator   ~0009159

Won't do in v10; too involved.

Issue History

Date Modified Username Field Change
2024-04-04 16:10 Patrick Schmalstig New Issue
2024-04-04 16:10 Patrick Schmalstig Status non-assigned => assigned
2024-04-04 16:10 Patrick Schmalstig Assigned To => Patrick Schmalstig
2024-04-04 16:11 Patrick Schmalstig Tag Attached: Roadmap: v11
2024-04-12 18:58 Patrick Schmalstig Status assigned => closed
2024-04-12 18:58 Patrick Schmalstig Resolution open => won't fix
2024-04-12 18:58 Patrick Schmalstig Note Added: 0008575
2024-06-07 03:32 Patrick Schmalstig Status closed => assigned
2024-06-07 03:32 Patrick Schmalstig Note Added: 0008824
2024-06-07 03:33 Patrick Schmalstig Note Edited: 0008824 View Revisions
2024-08-12 22:29 Patrick Schmalstig Note Added: 0009159