Support

July 6, 2023 at 10:42 am

QR codes are a representation of the registration number. If you import attendees to Event Espresso, it will assign them a new registration number.

July 7, 2023 at 4:34 am

Hi there,

Currently, there isn’t a way to import EE3 registrations into EE4 in a way that allows for what you are requesting for a couple of reasons.

Firstly, the details using EE4 aren’t the same as EE3, the registration_id isn’t the same in EE3 as it is for EE4 and even if you patched the code to allow imports to keep the same registration_id (REG_code in EE4) that leads onto…

—

The QR codes within an EE3 ticket are totally different to what EE4 uses.

EE3 uses this format:

{
    "event_code":"1-607d6e492ea7a",
    "registration_id":"2077-649f418782544",
    "attendee_id":"24262"
}

That’s taken directly from one of my test registration tickets within EE3. The EE3 scanner app uses that data and expects that format.

EE4 uses this form:

1-99cc1199d1eb2c670f5b7fbd15a6bc31

The data within an EE4 QR is the REC_code or REG_code_url, it’s a string that references a specific registration and then EE works out the event etc from the registration.

So you have EE3 QR codes using a completely different format AND value than what EE4 is expecting so even if you kept the same values in the EE3 database, EE would have no idea what to do with the QR when scanned unless you made basically you own version of the scanner to decipher the details and map them into EE4 somehow (I’m spitballing here, this would not be a simple task).

This is for a concert venue where they use a scanner to check in attendees.

What type of scanner?

Still querying Event Espresso database I assume? Using the EE3 app?

Any ideas / experiences on how to do this without sending every registrant a new email with a new code?

See the above, what you are trying to do is technically possible but not something we’ve done and will require careful planning and custom development to work. Note that we do not currently have the capacity to undertake custom projects at this time so you would need the help of a developer familiar with EE/WP.

Could you have two versions of the scanner app running on one system?

It depends on the specifics of what you mean by this question but the short answer to can you use the EE3 and EE4 app together on the same site, is no.

July 10, 2023 at 3:38 pm

What if we update the old site on EE3 to EE4 and then export?

Whilst technically that’s a little closer the ‘new’ registrations would still need new tickets sent over. The EE3 tickets still have the ‘wrong’ format for EE4, so scanning them with the EE4 app wouldn’t work.

This leads onto this…

By two versions of the app, I mean one that is attached to the old site and the other to a new site.

If you have both sites still accessible then yes you could do this.

So you’d scan your EE4 ticket registrations with the ‘new’ app and the EE3 registration tickets with the EE3 app. Do the devices you are using still support the EE3 app?

That gets messy when trying to do reporting though, as they are completely separate sites that don’t care about each other. Ticket limits, datetime limits etc will not be shared.

Is this for say 1 big event or do they have multiple EE3 events with registrations and now multiple EE4 events with registrations?

If it’s 1 big event, you may be ok using both EE3 and EE4 for the event and make sure that for the next one, all the registrations are made through EE4. However, check it works how you need it beforehand and that the reporting will be ok with that setup, the latest thing you need is to find out that it won’t work how you need it to on the day… and there is very little we/I can do to help with issues on scanning tickets like this on the day of the event itself.

If its multiple events that gets pretty messy and will likely be difficult to manage, which means you may be better biting the bullet, switching them over to EE4 and resending their tickets. You could then also have the EE3 site still running as a backup for those that turn up with the EE3 tickets (because you can pretty much guarantee that you’ll get some).

July 12, 2023 at 6:05 pm

Hmm, good question.

I assume you’ll be importing the registration using the Attendee Importer add-on?

https://eventespresso.com/product/eea-importer/

July 17, 2023 at 6:54 am

Then no, importing registrations will not trigger messages at the time they are imported.

You can manually trigger them afterwards but how you do that depends on the message type you want to send. We do not have a bulk option to send ticket notice emails, but it is possible t bulk trigger the ‘Registration Approved’ email (which can contain the ticket link) after they have been imported.

See my post on your other thread about how to include the details you want on each of those as that will likely determine which message type you use:

https://eventespresso.com/topic/incorporate-ticket-into-an-email/#post-345431

However, if you use the ticket notice then it will need to be manually triggered on each individual registration to send.

—

If you have registrations already on the event made with EE4 and now you want to import the EE3 registrations and ‘just’ want to trigger messages for those then I’d recommend you create a new DateTime just for the imported registrations so that you can filter them down. Otherwise, you cant easily identify which registrations were ‘created’ and which were ‘imported’.