Hey @petervandoorn,
Thanks for pointing this out. I tracked down the problem. Essentially, the frontend tool used to create the events, was not reporting the start time in the same timezone as the wordpress install is set to. I made an adjustment, and now both use the same timezone, which fixes this problem on events that are created after you update.
Unfortunately, these changes are not retroactive. The best way to correct those start times right now, is to manually update the postmeta that contains the start time. The name of the meta is ‘_start’. The change you would need to make to them is two fold:
1) Update the ‘time’ portion of the timestamp, so that it reflects the appropriate starting local time. For instance, if you want the event to start at 2pm London-daylight-savings-time, you would update the time portion to read ‘T14:00:00’.
2) Second, you will need to update the ‘timezone’ portion of the start time, so that it reflects your appropriate local timezone. For instance, if you want the event to start at 2pm London-daylight-savings-time, you would update the time portion to read ‘+01:00’.
*) So as a final result, if you have an event on august 4th 2016 at 2pm london-daylight-savings-time, the timestamp should read ‘2016-08-04T14:00:00+01:00’
I will be working on a tool that can be used to update the timestamps appropriately, but it will not be done today. Most likely, it will be ready sometime next weekish. If you need the immediate change though, you can follow the above instructions, and get them right before then.
Again thanks for finding this, as always.
Loushou