Closed (outdated)
Project:
Event
Version:
5.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
12 Aug 2007 at 09:25 UTC
Updated:
13 Apr 2018 at 20:57 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
Gabriel R. commentedHi Gunnar,
I have the same issue on my installation. Did you manage to fix the problem?
Thanks.
Comment #2
hanskuiters commentedAlmost a year later and I also have this issue. Are the dev versions stable enough or is this issue being fixed for this 5.x-1.0 release?
Comment #3
pathogen commentedFYI this is an issue on the latest 6.x release as well.
Comment #4
smccabe commentedThis bug is present in all versions of the event module, 5.x-1.0, 5.x-1.x-dev, 5.x-2.x-dev and 6.x-2.x-dev. It only happens if the hour value is lower than 10 and the time is set to 24hrs, it will also happen to the minutes field if it is under 10 on either 12 or 24 hour time. It happens because the default value is set in 2 digits '05', while the select option value is set as 1 digit '5'.
Attached is a patch for 5.x-1.0, the same patch should be easy enough to modify for 1.x-dev and 2.x-dev as the code is quite similar. The 6.x branch is quite different but the bug is still present and the same fix should work.
Comment #5
wdrout commentedHere's what I did to patch the 6.x version. It's very similar, but I needed to account for 12/24 hour conversion issue as well.
Comment #6
hanskuiters commentedI needed to change another thing in my installation. Can't make a patch file but I changed
// $hour_format = t('H');to this:
$hour_format = 'H';in line 1469.
Developers: why date and time code in the t-function?
edit: added line number.
Comment #7
japerryEvent for Drupal 8 is unrelated to older versions. If an issue similar to this one exists, please open a new issue with the 8.x branch.