harnor17
Forum Replies Created
-
I have checked if there could be a quick fix to this issue, but there’s none.
The problem is the way the database records are written when the recurring main event and the child events are created. Repeating events, repeating master events and Recurring master events will all get an even_id and post_id in the em_events table, however recurring child events will get an NULL post_id value.
The tables for term_taxonomy / term_relationships are handling the mapping of events with specific categories, and the object_id in the relationships table is then a reference to the post_id in the em_events. Hence, with a null value for those child events, there isn’t any link.I don’t know is this is just a glitch when creating a recurring event (forget to add post_id and term_relationship records) or if this is more a major design issue.
In the code of Em_event.php I found this comment under the function save():// not repeated event, but a recurrence of a recurring event - no post saving done hereThis seems to be design issue rather than a glitch. We will have to wait for Marcus to take a look at this code.
- This reply was modified 2 months, 2 weeks ago by harnor17. Reason: spelling issue
I just cleaned up my site with this process:
1) removed any orphaned events (about 10 disappeared) – at this point I had 3 left.
2) Permanently deleted 2 thrash events
3) Modified one draft event with a bad date (1/1/1970)
All 3 gone.During the process I also did the following (that didn’t help):
Delete all old bookings (about 6-8 – only used when testing it)
Checked for recurring events (we don’t use recurring events since it doesn’t go well with polylang) – nothing there.I hope this helps anyone out there…