Active
Project:
Field formatter conditions
Version:
7.x-1.0-beta1
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
23 Jan 2013 at 08:10 UTC
Updated:
31 Jan 2013 at 16:38 UTC
Jump to comment: Most recent file
Comments
Comment #1
swentel commentedHmm so in the database, is the end date stored as 23.1.2013 23:59:59 then ? I'm just trying to figure out how I can get behind this because I'm not even sure if that's possible at all. Isn't it possible to set the end date to 24.1.2013 00:00:00 - basically at midnight, or that's maybe a ux problem ?
Comment #2
swentel commentedComment #3
werner_p commentedThe format in the database is 2013-01-24 00:00:00 for an end-date 24th of January. As I ticked off the hours and minutes setting in the date field (see attached jpg) this is the resulting database field format. I tried it with hours and minutes on - and it worked correctly. If there is no other way I can live with it - I have to set the end date to 24.1.2013 23:59 manually when entering the date . It would have been easier just to enter full days as closing dates.
Comment #4
swentel commentedI'll experiment with it a bit though, it is kind of annoying having to set that date to 23:59 :)
Comment #5
swentel commentedThis is tricker than I though it would be. Changing to feature request because the original intent works fine, it's just that date_all_day does some funky stuff in it's calculations.