Issue background
During a recent WordPress site migration, the Freshy development team encountered an error while importing event data from a live site to its staging environment. The import process failed with an error message similar to:
“Error: Import failed – invalid post type or missing taxonomy reference.”
This issue prevented the migration tool from transferring event posts created by a WordPress events plugin into the staging database.
Diagnosis
Our developers identified that the problem was related to plugin dependencies and custom post type registration timing. Many event management plugins—such as The Events Calendar or Modern Events Calendar—register their custom post types using WordPress hooks.
When the import script runs before those hooks are fully registered, WordPress doesn’t yet recognize the event post type (for example, tribe_events), resulting in an import failure.
We also verified:
- The events plugin was installed and active on both environments.
- Plugin versions matched between live and staging sites.
- Database credentials and permissions were properly configured.
Resolution steps
Here’s how the issue was resolved:
- Activate event plugins first
The import script was delayed until after the event plugin was fully activated, ensuring that custom post types and taxonomies were available during import. - Flush rewrite rules
After activating plugins, we refreshed permalink structures with:flush_rewrite_rules();
This helped prevent URL conflicts related to custom post types. - Use WP-CLI for manual import
Instead of running the import through the WordPress dashboard, we used WP-CLI for better control and error visibility:wp import events.xml --authors=create - Recreate missing taxonomies
If the import referenced categories or tags that didn’t exist yet (for example,event_categoriesorevent_tags), we manually created them before retrying the import. - Verify event data and links
Once the import completed successfully, we confirmed that events appeared correctly in the WordPress dashboard, metadata was preserved, and permalinks resolved properly on the front end.
Final outcome
After following these steps, the event data was imported successfully and displayed correctly in the staging environment. The migration proceeded smoothly, ensuring data consistency and a stable pre-launch review process.
This workflow can be applied to any WordPress site using custom post types—especially those running event or directory plugins—when moving between environments.
Need help with a complex WordPress migration or plugin issue?
The Freshy development team can diagnose and resolve problems with custom post types, imports, and plugin conflicts.
Contact Freshy to get expert help today.
