Bulk importing with with PI Event Master Plugin from Ticketmaster API saves time, but it also magnifies mistakes. A wrong post status, field mapping, category, or location filter can create dozens of unwanted posts in seconds. PI Event Master records each bulk import as a session so the posts created by that run can be identified and rolled back together.
What an import session records
After a bulk import, the Import History tab records a session ID, date and time, number of imported events, and the WordPress post IDs created in that session. Version 1.8.14 retains the most recent 20 sessions.
A session is a deletion boundary, not a full database snapshot. Rollback permanently deletes posts created during that import; it does not restore unrelated edits, theme settings, or posts that existed before the session.
Use a small validation import first
Before importing a large city or category:
- Open Import Settings and verify post type, post status, featured-image behavior, categories, and selected fields.
- Review event-expiry and noindex behavior.
- Run a narrow search and import only a few events.
- Inspect a resulting post on the front end and in the WordPress editor.
- Check date, venue, city, image, ticket URL, category, and any mapped custom fields.
Only expand the query after the sample post is correct. Rollback is a safety tool, not a substitute for staging and validation.
How to roll back a session
- Go to Settings → PI Event Master → Import History.
- Find the session by its time, count, and displayed post IDs.
- Confirm that it represents the unwanted run.
- Select Rollback.
- Read the confirmation carefully and approve the permanent deletion.
When rollback succeeds, the session row is removed and all posts associated with that session are deleted. The action cannot be undone through PI Event Master.
Before you click Rollback
- Create a current database backup if the site is important or the posts have been edited since import.
- Check whether editors have added original content to any imported posts.
- Check whether external pages, newsletters, or social posts already link to them.
- Record the original import query if you intend to rerun it.
- Make sure you selected the correct session; similar imports can have similar counts.
What rollback should—and should not—fix
Rollback is appropriate when the wrong events were imported, a test batch reached production, or a mapping error affected every post in one run. It is usually excessive when only one title, image, or category is wrong. In that case, edit the individual posts or correct the mapping and use a targeted editorial workflow.
If a scheduled Business-tier rule is responsible, disable or correct the rule before rolling back. Otherwise the same events may be imported again on the next hourly, twice-daily, daily, or weekly run.
Duplicate protection and rerunning
PI Event Master identifies imported Ticketmaster events using stored event IDs and skips events already present. After a rollback deletes those posts, a corrected import can create them again. Recheck post status and field settings first, then run another small sample before restoring the full batch.
Clear stale output after a large rollback
Imported listing caches are automatically invalidated when imported event posts are saved or deleted. If a page cache or CDN sits in front of WordPress, purge that layer as well. Use the plugin’s Flush Imported Cache control if a listing still shows removed cards; there is usually no reason to flush unrelated live API caches.
A safer bulk-import operating procedure
- Back up the database.
- Validate settings with three to five events.
- Record the search parameters.
- Run the full import.
- Note the session ID and count.
- Quality-check a sample from the beginning, middle, and end of the batch.
- Keep the session until the content has passed review.
Import History makes bulk operations auditable and recoverable within a clear boundary. Combined with small test batches and backups, it turns rollback into a controlled exception instead of an emergency habit.
