View Issue Details

IDProjectCategoryView StatusLast Update
5666Composrcorepublic2024-08-12 22:29
ReporterPDStig Assigned ToPDStig  
PrioritynormalSeveritytrivial 
Status assignedResolutionwon't fix 
Product Version10.0.47 
Summary5666: 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
Attach Tags
Time estimation (hours)
Sponsorship open

Sponsor

Date Added Member Amount Sponsored

Activities

PDStig

2024-04-12 18:58

administrator   ~8575

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.

PDStig

2024-06-07 03:32

administrator   ~8824

Last edited: 2024-06-07 03:33

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.

PDStig

2024-08-12 22:29

administrator   ~9159

Won't do in v10; too involved.

Add Note

View Status
Note
Upload Files
Maximum size: 32,768 KiB

Attach files by dragging & dropping, selecting or pasting them.
You are not logged in You are not logged in. This means you will not get any e-mail notifications. And if you reply, we will not know for sure you are the original poster of the issue.

Issue History

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