Download the 7.0.0 User Guide in PDF User Guide
Version 7.0 is a complete rewrite of Event Registration. It’s faster and more secure, and it brings your 6.x events, registrations, and payments with it. Your 6.x data is never changed or deleted unless you choose to remove it.
Before you update
- Back up your site, including the database. Most hosts offer backups, or use a backup plugin.
- Check your PHP version. 7.0 needs PHP 8.2 or later and WordPress 6.9 or later. See Tools → Site Health → Info → Server.
- Online payments: 7.0 includes offline payments (check, cash, pay at the door). The 6.x PayPal, Authorize.Net, and other gateway integrations are not part of 7.0; online payments are planned as add-ons.
- The Location and Coordinator modules from 6.x are not compatible with 7.0. Their features are planned as new add-ons.
Update the plugin
- Update Event Registration from Plugins or Dashboard → Updates.
- If the old Location or Coordinator module is active, a notice explains that it isn’t compatible, with a button to deactivate it. Click the button. Nothing is deactivated until you do.
Import your 6.x data
When 6.x data is found, a notice links to Event Registration → Import from 6.x.
- Review What was found (how many events, registrations, and payments) and Things to know (for example, events whose date couldn’t be read).
- Click Start import. A progress bar shows each step. If you close the page or the connection drops, come back and click Continue import; nothing is imported twice.
- When it finishes, check the summary. Download the full report (CSV) lists anything that was skipped or adjusted, and why.
| From 6.x | Comes across as |
|---|---|
| Company settings | Organization details and sales tax rate (Settings) |
| Categories and their colors | Event categories |
| Events | Events with their dates, times, capacity, venue, and categories. A limit of 999 becomes unlimited. |
| Location module venues | The event’s location |
| Fees and items | Ticket types |
| Questions and answers | Registration questions and each registration’s answers |
| Attendees | Registrations, including each person’s name and waitlist status |
| Payments | Payment history, with balances matching what 6.x showed |
Not imported: payment gateway settings, and your 6.x email templates. Review the new emails in Settings → Emails.
Events whose dates couldn’t be read are imported as drafts. Open each one, fix the date, and publish it.
Your existing pages
Pages built for 6.x keep working after the import:
| On your 6.x page | In 7.0 |
|---|---|
{EVRREGIS} | Your upcoming events, each linking to its registration page |
{EVR_CALENDAR}, {EVR_MINI_CALENDARS}, [[EVR_CALENDAR]] | The events calendar |
{EVR_UPCOMING}, [[EVR_EVENTS]] | The upcoming events list |
[[EVR_SINGLE event_id="5"]] | That event and its registration form |
[[EVR_CATEGORY event_category_id="youth"]] | Upcoming events in that category |
[[EVR_PAYMENT]] | A note directing people to their confirmation email and your contact details |
[[EVR_ATTENDEE]], [[EVR_CUSTOM_ATTENDEE]] | Nothing (public attendee lists aren’t part of 7.0). Only administrators see a note. |
Old event links (such as ones in past emails) go straight to the event’s new page.
When you’re ready, you can replace the old codes with the new blocks or shortcodes described in Showing Events on Your Site. The event, calendar, and payment pages you created for 6.x are no longer required: every event now has its own page.
Remove the old 6.x data
After you’ve checked your events and registrations, you can delete the old 6.x tables from Import from 6.x: type DELETE and click Remove 6.x data permanently. This can’t be undone, so keep a backup. Your 7.0 data isn’t affected.
Questions
Is my 6.x data safe during the import?
Yes. The importer only reads your 6.x data. Nothing is changed or deleted until you choose Remove 6.x data permanently.
Can I run the import again?
Yes. Items already imported are skipped, so running it again only brings in anything new.
Why were some registrations skipped?
Usually because they belonged to an event that had been deleted in 6.x. The report (CSV) lists each skipped item with the reason.
Why should I update from 6.x at all?
Version 6.x has known security problems and doesn’t run on current versions of PHP. Version 7.0 was rebuilt to fix them.