Support

Home Forums Event Espresso Premium EE4 Country/State/Province issues

EE4 Country/State/Province issues

Posted: November 9, 2014 at 3:31 am


SWTA

November 9, 2014 at 3:31 am

Hi Support

I have just upgrade/migrated from the latest version of EE3 to the latest version of EE4 which went relatively smoothly but we’ve found an issue with the state registration question showing lots and lots of strange values.

It looks like the values have been generated from previous registration records as there are lots of dates of births followed by a county name?!

I can see how to remove the options via the general settings > countries tab but there are so many to remove is there an easier way? All we want to show is the UK.

Many thanks
Michael


Tony

  • Support Staff

November 10, 2014 at 3:46 am

Hi Michael,

So currently the Country and State/Province sections show all the available options on the front end?

It looks like the values have been generated from previous registration records as there are lots of dates of births followed by a county name?!

I do not believe the values are generated from previous registrations but will investigate this further.

Do you have access to phpMyAdmin or similar? If so you could use that to set all the countries to be inactive with a single SQL command.


SWTA

November 10, 2014 at 3:55 am

Hi Tony

Yes i do have access to phpMyAdmin
Can you send me the SQL command i would need?


Tony

  • Support Staff

November 10, 2014 at 4:12 am

Be sure to create a database backup before running any other commands.

To disabled all countries you can use something like:

UPDATE wp_esp_country SET CNT_active=0;

Edit – the forum is adding formatting, here’s a pastebin link http://pastebin.com/uxZrVVTB

Then within the wp_esp_country table, find United Kingdom and set CNT_active to 1 – http://take.ms/9NLb2

(From the browse tab you can just double click on that value to change it)

Note wp_ is the table prefix on that site, yours may be different.

  • This reply was modified 9 years, 6 months ago by  Tony.


SWTA

November 13, 2014 at 3:40 am

Hi Support

Tony – thanks for the quick fix for disabling all unwanted countries.

But we still have quite a few issues with our user data since upgrading to EE4. It appears that values for certain questions from the old EE3 site have been populated into the wrong questions in the upgraded site.

For example we had a previous question called ‘Date of Birth’, the values of which have now been populated into the ‘Country’ question. So looking at a previous registrant contact details, their date of birth appears within the country?

We would greatly appreciate your help to investigate and resolve this issue as it is preventing us from putting our upgraded site live.

Many thanks
Michael


Tony

  • Support Staff

November 13, 2014 at 4:18 am

Yeah that definitely should not be happening.

Which version of Event Espresso 3 are you upgrading from?

Have you made any modifications or had any custom development done to EE at all?


SWTA

November 13, 2014 at 4:41 am

Upgrade from the latest version of EE3 (3.1.36.6)

No modifications or custom development


SWTA

November 13, 2014 at 4:44 am

Find me on Skype (removed – Tony) and I can show you what i’m seeing

  • This reply was modified 9 years, 5 months ago by  Tony. Reason: removed skype username


Tony

  • Support Staff

November 13, 2014 at 7:18 am

Hi Michael,

Apologies for the delay getting back to you.

Rather than viewing the site through Skype would it be possible for you to create a Temporary login for us to use?

That way we can take a deeper look into why this may be happening.

If so please use this form to send login details:

https://eventespresso.com/send-login-details/


SWTA

November 13, 2014 at 7:33 am

Details sent


Tony

  • Support Staff

November 13, 2014 at 9:58 am

Hi Michael,

Do you have a database backup from before you migrated to EE4?

The reason I ask is if you go to Event Espresso -> Maintenance. You’ll see there was actually a Data migration error which means your EE3 data has not correctly been migrated to EE4.

So the next step is to restore the the database backup from before you migrated to EE4, download the lastest version of EE4 (4.4.5.p) de-activate and delete the current version you have installed. Upload the latest version and activate (be sure EE3 is de-activated before doing so).

Then re-running the migrations.

If you do not have a backup there is the option to drop all EE4 tables and retry (EE4 includes a function to do this for you) although restoring to a backup is the preferred method.

If using this method you must create a database backup of the site in its current state beforehand.


SWTA

November 13, 2014 at 10:48 am

Hi Tony

The data migration to EE4 ran without any errors, however there was an error when installing/upgrading the calendar?


Tony

  • Support Staff

November 13, 2014 at 11:00 am

If you go to Event Espresso -> Maintenance. You’ll see this – http://take.ms/6bdaw

This means at some point during the data migration scripts from EE3 to EE4 a Fatal Error was thrown, this in turn halts all remaining migrations and will not let you continue so your data will not be correctly migrated.

Do you have a backup from before the data was migrated to restore to?


SWTA

November 13, 2014 at 12:06 pm

That error occurred when i installed the events calendar add on. There were no errors shown after the initial core EE upgrade (i checked) which is why i question the solution.

Yes i do have a backup but there were lots of changes made to the event data after the upgrade which we will lose.


SWTA

November 14, 2014 at 4:45 am

Hi Tony

On a new local install i have restored the original EE 3.1.36.6 database and run through the EE4 upgrade process again as you instructed.

The process ran without any errors.

I took screenshots of an attendees registration details before and after the upgrade which clearly show the previously reported error where a question in EE3 called ‘Date of Birth’ has been populated into the ‘Country’ question in EE4. So looking at a previous registrant contact details, their date of birth now appears within the country.

I would greatly appreciate your assistance in resolving this error as a matter of urgency.


Tony

  • Support Staff

November 14, 2014 at 5:51 am

Hi Peter,

I believe I’ve found the cause of this.

Within the EE3 install, in the Address information question group, was the Country question changed to ask for DOB instead of country?

You can see if this is the case locally by disabling EE4, activating EE3 and going to Event Espresso -> Questions.

Does you DOB question have a padlock icon next to it? – http://take.ms/VJqHT

If you click on the question to edit it, does the URL contain “question_id=8”

Like this /wp-admin/admin.php?page=form_builder&action=edit_question&question_id=8


SWTA

November 14, 2014 at 6:17 am

In EE3 the DOB and County fields are two separate fields:

monosnap.com/image/sBGSFT3L9a4QttZRipq64wv4jchdM3
monosnap.com/image/LWoRoEQwD2s7Ep07WNsWA57uJdq5Dr

I checked this with on a separate install of the original site and not by disabling EE4.

You’ll see in the screenshot that DOB does have a padlock and the ID is question 8


SWTA

November 14, 2014 at 6:22 am

Both questions (DOB and Country) were part of the Personal Information question group: monosnap.com/image/jIavWQaDpbvqSlBqKWaBmAgkr6G9ws


Tony

  • Support Staff

November 14, 2014 at 6:25 am

What is the question ID for the DOB question?

You’ll find this by going to the ‘Questions’ section, then editing the DOB question, look within the URL and you will see question_id=X


Tony

  • Support Staff

November 14, 2014 at 6:26 am

Also the same question for the Country question too please.


SWTA

November 14, 2014 at 6:26 am

In EE3 it’s question_id=8

I said that in the previous comment and you can see it in the screenshots


SWTA

November 14, 2014 at 6:29 am

In EE3 for county it is question_id=7


SWTA

November 14, 2014 at 6:32 am

DOB

County

Personal Information question group


Tony

  • Support Staff

November 14, 2014 at 6:47 am

Apologies, I missed your first reply with the screenshots.

This confirms what I mentioned above.

The system question ‘Country’ within the Address Group, has been re-purposed for Date of Birth. Question_ID = 8 should be Country (not County – that’s the ‘state’ question renamed as that is question_id = 7)

Someone has altered that field to be used for Date of Birth, so during migrations EE4 is loading that value expecting it to be the Country for the attendee. This is causing both the incorrect contact info for your registrations and the added ‘date’ countries to the EE4 Countries dropdown.


SWTA

November 14, 2014 at 6:54 am

No worries about the missed replies.

It sounds like the client has changed these fields without knowing the impact it would have but ultimately what i’m looking for is a fix for the live site data without having to revert to previous backups as we will lose a lot of information.

Is it possible to fix this on the live DB (after backing up!)?

I am quite happy to pay for your time on this.


Tony

  • Support Staff

November 14, 2014 at 8:42 am

It is possible yes, although I would highly discourage modifying the database on a live/active site.

Do you currently have a development version of the site?

It is best to run a clone of the site and as a development copy that we could make changes to, then once tested and confirmed fixed apply the same fixes to the live site.


SWTA

November 14, 2014 at 1:45 pm

Hi Tony

I have purchased a support token and submitted a request with all the relevant details. My DB skills are limited hence the request for assistance!

Thanks for all your help with this…


Josh

  • Support Staff

November 17, 2014 at 5:43 pm

Hi Michael,

I saw that Tony followed up with you over email, so I’m marking this thread as Pending.

The support post ‘EE4 Country/State/Province issues’ is closed to new replies.

Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.

Event Espresso