Support

June 5, 2023 at 2:47 am

Hi there,

Can you please post up the steps you took to migrate the site?

June 5, 2023 at 3:07 pm

I need way more details on what you have actually done during the migration here.

You’re saying it works on the staging site, but not on the live site after you have ‘migrated’ (which people use very loosely) your changes over.

What changes specially?

Could you please be more descriptive while responding to my query? I really don’t want to wait that longer since its on the live site.

You want me to be more descriptive when asking how you migrated the site?

I can’t give you a detailed response on what the issue is I have no idea what’s been done and what the difference between live and staging is, the only change I’m aware of is the ‘migration’/copying files, which files?

No database changes included in that migration? The domain name changes from stating to live but I don’t know if you’ve copied the database over as there isn’t enough details in your response.

Later, I updated the key of event espresso (with a new key on the new server since I had a few unused keys).

The key doesn’t do anything other than provide support and updates, so ignore that for now as the key won’t cause any issues.

You can check this here: https://principleskills.com/events/emotion-coaching-bootcamp-colorado-springs-june-10-2023/

When do you get the mentioned error? I’m not getting any errors up until arriving at PayPal.

June 7, 2023 at 11:19 am

Thanks for not helping me out. Somehow I figured it out.

I can only help you out when there’s enough information to know what to help you with.

You ‘migrated’ a site? Right ok, so what exactly do you consider a migration because in your next response, you basically copied over some files from one server to another which isn’t a migration… it’s copying files. Nothing is stored within the files, it’s all in the sites own database.

No mention of the database being migrated? If you migrated the database, did you run a script to update the database correctly, taking into account any serialized data which will need to be addressed with a domain name change? (Becuase yes, that ‘could’ have caused the error mentioned… no point advising you fix that if you didn’t migrate the DB or have already done it correctly)

The error you were getting can be caused by a whole host of issues so I needed to know ‘how’ the site get to where it was at to throw that error. I have no idea what you have done so I need to ask for more details because none of that was included in your opening post.

I’m sorry if you consider that not helping, but can’t help without details.

Now, could you please tell me the way to import list of registrations from the old website to the new one? Bascially, I have created a new website and I was assuming there would be a way to export and import events and registration details in a CSV file or something like that but that I couldn’t find. Again, if you need more specific details:

EE does not have the option to export data from one site to another in the way I think you are looking for.

We do have an attendee importer add-on:

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

You could use it to import registrations onto the site on a per event basis by first exporting the registration CSV from the original event and then using the add-on to import those onto the ‘new’ event (on the other site).

There’s no way to do this in bulk with all of the data.

So on the original site go to Event Espresso -> Events -> {hover over the event} -> Registrations.

Click the button to export registrations at the bottom of the table. You’ll download a CSV of that events registrations.

Now on the ‘new’ site with the Importer add-on enabled, go to Event Espresso -> Importer.

Search for your new event, select and work through the steps to import the CSV you just download using that add-on.

Now you have the registrations from the original event on the ‘new’ event.

Repeat for each event.