Time bug found in plugin

Ah, I guess I *HAVE TO* select the next day for the end date? and then select 00:00.

Is this a must? Or is this customizable to add 00:00 to the end time part? even 59:00 would be good

what do you guys suggest?

Many thanks

Kristian

Apart from selecting from the drop-down, you can also enter the time manually.
I usually enter 23:59 for end of day, to prevent the event showing up on “events tomorrow”.

You and I can do that, most other developers too have that mind… ??

But what about our end users ??

The guys behind this really are less so end user focused.

I disagree. 00:00 Is officially the beginning of the next day. Everybody I know agrees with that, even my 84-year old grandmother.

So for an end user that should be clear.

I agree that it is not really clear that you can enter the time manually, and it’s a bit cumbersome, this could do with some UI improvements.

Not sure if this is a bug since I think 00:00 is officially the next day, however, you can still override the time picker interval using the following steps. (not yet upgrade proof at the moment)

1. go to events-manager/includes/js/events-manager.js
2. go to function em_setup_timepicker(){} then add step:10

From:

	wrap.find(".em-time-input").timePicker({
		show24Hours: EM.show24hours == 1,
		step:15
	});

To:

	wrap.find(".em-time-input").timePicker({
		show24Hours: EM.show24hours == 1,
		step:10
	});