• ResolvedPlugin Author Peter Hardy-vanDoorn

    (@petervandoorn)


    I’m not sure when this happened – sometime during the last 6 months, is all I can say – but a recent update has resulted in the wrong times being displayed on the printed tickets.

    On 2 completely separate sites, both of which are properly configured in WP settings with a “daylight savings” time zone (namely Europe/London) I am seeing the times output on the tickets in non-savings time (ie, an hour earlier – 10am when it should be 11am). The times in the backend are displaying correctly.

    It’s easily fixable by adding date_default_timezone_set('Europe/London'); to the copy of the event-meta.php file in my theme.

    Thanks

    https://www.ads-software.com/plugins/opentickets-community-edition/

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author quadshot

    (@quadshot)

    @petervandoorn thank you for bringing this to our attention. We’ll pass this on to dev.

    As usual, thank you for being so helpful and providing us another bug fix!

    Plugin Author loushou

    (@loushou)

    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

    Hello,

    I am using version 2.4.4 which should have this fix but I am seeing the same issue currently on newly created events. Any advice?

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Wrong times on tickets’ is closed to new replies.