Legacy recurring events (child posts) remain published in DB after migration.
-
Tried submitting a ticket at https://my.theeventscalendar.com/my-account/support/ but Gravity Forms is throwing a 403…
Developer question regarding legacy recurring events after migration,Are legacy recurring “child posts” supposed to get deleted after data migration now that the new data structure only needs just one post?
In my case they’re all still in the DB, so wanted to ask to make sure I didn’t have a conflict during migration as I completed it back in April. I suspect there isn’t a delete process for these since you’re able to “undo” the migration or it’s possible I had a cron not fire after a week? You won’t see these posts in the WP admin nor on the event pages. However, they are showing up in Yoast’s XML sitemap as well as returning in the global WP search. You can only find them in the admin by using the ID and going directly to the edit.php screen. e.g. /wp-admin/post.php?post=###&action=edit
Events that are still upcoming will redirect to the proper series page just fine, but the issue is with one’s that have already passed and are now just 404’s and do not get trashed or deleted by the action scheduler (since now it’s the new data structure).
This is only happening to recurring events that existed prior to migration… And unless manually removed, will remain obscurely in the DB. Looks like the scheduler is intentionally skipping child posts in https://docs.theeventscalendar.com/reference/classes/tribe__events__event_cleaner_scheduler/select_events_to_purge/
You can run this statement to check if there are lingering child posts in the DB:
SELECT ID FROM wp_posts WHERE post_type = "tribe_events" AND post_parent != 0;
Everything else seems to be working as it should.
Is this the intended functionality or is it possible I have a scheduled task not firing or something? I can clean up these legacy posts but wanted to check if there was any intention behind this.
Let me know,
Thanks!The page I need help with: [log in to see the link]
- The topic ‘Legacy recurring events (child posts) remain published in DB after migration.’ is closed to new replies.