Support

July 4, 2018 at 10:00 am

Also, what I found, is that if you look at this list, there’s all sorts of weird country names in the list

That can happen when the EE3 country question was repurposed to something else, there’s phone numbers as countries in your list so as an example the country question may have been swapped out for phone number at one point (or the user just entered the phone number in that section).

Is the solution to revert this back to a dropdown via db? Only problem then would be that I would have to know the db value that contains all countries.

There isn’t a single DB value for this, EE knows that questions of type COUNTRY pull the values from the _esp_country table in the DB. The problem is going to be with how your current country questions relate to the ‘correct’ country question type.

Are you comfortable editing the DB?

Do you have a development copy of the site? If not I recommend creating one from the current version and testing any fixes on this there as you may find registrations/contacts throw fatal errors anywhere they pull the country details in once this is fixed.

If you are comfortable editing the database you can try changing the QST_type of Country - System Question to COUNTRY in the esp_question table.

Then confirm that you can view registrations and contacts within the admin and run a test registration to confirm that also works.

I highly recommend creating a database backup before you make any changes just to be safe.

July 9, 2018 at 2:50 pm

What I noticed was inside of the existing Attendees, the Country field was empty anyway (for all the contacts I checked).
This could be mainly because we switched from Text to Country. It can’t convert back to a dropdown field.

Based on this you have a couple of choices, if you are not concerned with trying to pull in the current contacts country you can test what happens if you start with a fresh esp_country table.

The way I would do that is to rename the current table to something else (do this on the test site, not live).

So if your table prefix is wp_, rename wp_esp_country to wp_esp_country_temp

Visit a page in the admin and EE should automatically regenerate the default country table for you. Now test some contacts and confirm you’re not getting fatal errors and that contacts that DO display a country (if any) display the correct one.

July 18, 2018 at 2:22 am

With the exception of row 70, that table looks correct, but as your simply renaming a table for EE to recreate, there is no harm in testing it (as you can always delete the ‘new’ table EE creates and go back to the original, so give it a shot by all means.

I’ve ask one of our developers for some further feedback on the above to see if they can think of a reasons for the error.

July 19, 2018 at 4:47 am

Hmm, strange.

I’m glad it’s working for you now but really sure why, I recreated the same setup and added another row without values and it worked fine, it was obviously an issue with the state table but the above doesn’t really point to what that issue was.