When ECP saves a recurring event the saveEvents function saves a _EventStartDate row in wp_postmeta for each date that the event recurs. The function saves these rows in date order, starting with the earliest date. But, when a program retrieves these values with get_post_meta(), the database query doesn’t always return them in the same order. (There is no ORDER BY clause in the query that get_post_meta runs.)<\/p>\n
This causes three problems in Events Calendar Pro:
\n1. The instance with the first-retrieved _EventStartDate (not always the earliest instance) is the only instance that appears in List view (or list widget) if the “Recurring event instances–Show only the first instance of each recurring event” setting is checked.<\/p>\n
2. The instance with the first-retrieved _EventStartDate is the instance displayed if a visitor’s requests the URL of the event without specifying a date. For example, “\/event\/buzzards-bay\/” instead of “\/event\/buzzards-bay\/2013-08-05\/”.<\/p>\n
3. If the first-retrieved _EventStartDate is not the earliest instance of the event, and the earliest instance of the event is edited and saved (choosing “All events” from the “Saving Recurring Events” dialog), then the first-retrieved _EventStartDate will disappear from wp_postmeta and the event will no longer appear on that date in the various calendar views. The recurrence rule will not change, and ECP will still treat all the remaining instances as part of one recurring event.<\/p>\n
I understand that you may have difficulty reproducing this problem, because it depends on the behavior of your database, which you cannot control directly. If I edit\/update the event a few times, it always appears for me eventually, usually within 2-3 tries; it’s easiest to see by watching the database table in phpMyAdmin after each update.<\/p>\n","protected":false},"template":"","class_list":["post-56356","topic","type-topic","status-closed","hentry"],"yoast_head":"\n