• Has the _eventorganiser_event_schedule array changed for events since the last update?

    When comparing reoccuring events made in the past the array includes a part called “_occurrences”. Recently made reoccuring events don’t seem to have that part.

    Example old array:
    a:8:{s:7:”all_day”;i:0;s:8:”schedule”;s:6:”custom”;s:13:”schedule_meta”;s:0:””;s:9:”frequency”;i:1;s:7:”exclude”;a:0:{}s:7:”include”;a:2:{i:0;s:19:”2016-03-20 14:00:00″;i:1;s:19:”2016-03-27 14:00:00″;}s:12:”duration_str”;s:55:”+0 year +0 month +0 days +2 hours +0 minutes +0 seconds”;s:12:”_occurrences”;a:3:{i:815;s:19:”2016-03-06 14:00:00″;i:816;s:19:”2016-03-20 14:00:00″;i:817;s:19:”2016-03-27 14:00:00″;}}

    Example new array:
    a:7:{s:7:”all_day”;i:0;s:8:”schedule”;s:6:”custom”;s:13:”schedule_meta”;s:0:””;s:9:”frequency”;i:1;s:7:”exclude”;a:0:{}s:7:”include”;a:2:{i:0;s:19:”2016-03-26 17:00:00″;i:1;s:19:”2016-03-27 17:00:00″;}s:12:”duration_str”;s:55:”+0 year +0 month +0 days +1 hours +0 minutes +0 seconds”;}

    https://www.ads-software.com/plugins/event-organiser/

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Stephen Harris

    (@stephenharris)

    That’s correct – since 3.0.0 that array has been removed because of the performance impact it was having. You can use this function instead: https://codex.wp-event-organiser.com/function-eo_get_the_occurrences_of.html

    Thread Starter tifcc

    (@tifcc)

    ah okay, I am using the post-meta to parse the data to a JSON feed. I now switched to using includes i.s.o. occurrences. That works for custom occurrences. Problem is that using the array with repeating occurrences on monthly or weekly basis are a bit hard to return a correct date.
    Using date.js to check wether or not the next or previous weekday should be picked based on the ammount of days between original eventday (say Su 17 Apr) and the next occurring eventday (say Su 15 Mei).

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘changes in _eventorganiser_event_schedule array’ is closed to new replies.