Support

May 29, 2018 at 6:59 am

Hi there,

One way to address this would be to delete the EE4 data from the Event Espresso 4 Maintenance page (it’s the bottom option on the Reset/Delete tab), then reactivate EE3 and change the email system question back to be an email question (it should be ID 3) and set it to the personal information group. Then you deactivate EE3, reactivate EE4 and re-run the migration.

May 30, 2018 at 3:28 am

Hmmm, is there an Option B here? We want the system question for email to be assigned to a non-system question group. That would give us the functionality/appearance that we had in EE3, which is what we ideally want. Is that not possible with EE4?

The Email address system question must be assigned to the system group ‘Personal Information’ as EE expects the 3 fields used in that group by default (FName, LName & EMail) to be constant throughout the checkout, you can add additional fields to the group but EE needs those 3.

However, you can have an additional email question in another question group and then use the answer to that question for the emails if that is what you are looking for?

If you let us know the use case for the above we can advise how/if you can do that in EE (or the closest setup).

If that’s not possible, is there a way to programmatically “check” the system email question and set it to the personal information group WITHOUT having to rerun the migration? I see the field, but that boxed is grayed out, so there’s no way to select anything.

There’s no UI that will let you change the system questions so the only way to do that is by manipulating the database directly. The problem with that is that we don’t know the exact changes that need to be made as the EE3 setup ‘confused’ the migration so there may be multiple locations in the DB that need to be updated.

May 30, 2018 at 10:01 am

The current version of EE3 is compatible with PHP 7 and is available to download on Github here:

https://github.com/eventespresso/event-espresso-legacy/archive/master.zip

May 30, 2018 at 10:42 am

I’m OK if the system email question is assigned to the personal information question group. That’s not ideal, but we’ll work with it. A little frustrated that this wasn’t included in the migration documentation; you allowed this in EE3, and in searching the threads on this forum, it appears that this isn’t an uncommon process for folks to use in EE3. As a side note, it would probably be helpful for others if you updated your documentation to include a note/warning about this for people migrating from EE3 to EE4.

We didn’t allow for this in EE3, the 3 system questions in EE3 did not have checkboxes – http://take.ms/brwbb

Meaning your not supposed to remove those questions from the group. EE has always expected the questions to remain in the group. If the questions were somehow removed from the group and placed in another it would likely still work for a lot of cases as they are pulled by the ID, but then EE4 can’t rely on the expected relationship between those questions and migrating that data over to EE4 causes issues, like now.

It’s a similar situation to users who were ‘repurposing’ EE3 address questions to something completely different (for example changing the state question to be DOB). EE3 allows the field to be edited to allow for translations, not completely repurposing the question itself.

Right now, the system email question is hanging out in cyerspace… users don’t see it, we can’t assign it to the system personal info group (where it supposedly belongs), and there’s no way for the user to populate that field when filling out a registration. So basically you’re saying we’re stuck, and need to let that field just hang out there unused?

No, that isn’t what I said.

Josh advised a method to fix the question by fixing it within EE3 and re-migrating the data over, you ask if it was possible to work around that which I replied with (in short) not without editing the database directly and confirming that all relationships are edited correctly. Your options are to re-migrate with EE3 setup to use the personal info questions as expected, or manually update EE4’s database and confirm all of the question relationships are as expected, I do not recommend leaving that question in limbo as it will cause issuses further down the line.

Can you advise how to do the above? Right now the primary registrant notifications are being sent to [PRIMARY_REGISTRANT_EMAIL]. How do I change this to point to my new custom email field?

That’s not a fix/workaround to the current problem, it’s a possible workaround to allow you to use EE4 with an additional email field, not a method to work around a ‘missing’ EE email system question.

To answer your question you would use the [PRIMARY_REGISTRANT_ANSWER_*] shortcode, that shortcode takes the question text of a custom question and outputs the answer for it. So if you question text on a question was ‘attendee email’ the shortcode would be [PRIMARY_REGISTRANT_ANSWER_*attendee email].

However, if you continue to use EE4 with a missing system question, your creating registrations that a rely on ‘broken’ relationships which then may need fixing. For example, say you wanted to use the MailChimp Add-on… that’s not going to work as your questions are not what it expects and it will send the wrong values (at the very least the wrong email). You are much better off fixing this now before you’ve ran events/registration etc on EE4 rather than later when you then also have data that needs to be updated.