|
ccarlson
|
February 29, 2016 at 4:21 pm
We just migrated over to EE4. The migrated registrations created duplicate columns in the .csv file. (i.e. fname, Lname,etc). I was told not to delete them out of the database, but to exclude them from the export. How do I do that? Also, can I query out only the completed registrations in the same process?
|
|
Tony
|
March 1, 2016 at 4:51 am
Hi there,
Were are you running the CSV export from?
Is it Event Espresso -> Registrations -> All Registrations CSV Report?
Or are you viewing the registrations for a single event and then exporting?
Event Espresso -> Events -> *Hover over event name* -> Registrations -> Event Registrations CSV Report.
|
|
ccarlson
|
March 1, 2016 at 5:21 am
I am running the download from the single event. I either hover over the event or I click on the number of registrations and download it from there.
|
|
Tony
|
March 1, 2016 at 5:30 am
There is a filter to remove additional fields from the CSV, we have an example of hot to use that here:
https://github.com/eventespresso/ee-code-snippet-library/blob/master/admin/tw_registration_report_exclude_fields.php
You can set the fields to be excluded from the CSV and all other fields will then be allowed through.
However before changing the output, could you send me a copy of the export? I don’t need real values within the export but I just want to make sure we are not covering up a bigger problem as you shouldn’t see duplicate fields.
If so please send the csv to support[at]eventespresso.com so I can take look (I would also recommend including a link to this thread so we know what the email is for)
|
|
ccarlson
|
March 1, 2016 at 5:38 am
I just emailed it to you. Thanks for your help!
|
|
Tony
|
March 1, 2016 at 6:09 am
Ah ok, I see.
So the additional fields are custom questions, without seeing how your EE events were setup I can’t be 100% but I’m guessing you had additional questions for first name, last name and so on. Those have been imported over but looking at your events your using the system questions within EE now so this shouldn’t cause problems.
|
|
ccarlson
|
March 1, 2016 at 7:51 am
Thanks! Can you tell me where the export file is that needs this update? I knew where it was in EE3, but I can’t find it in EE4.
|
|
Tony
|
March 1, 2016 at 7:54 am
Please do not edit Event Espresso core files, there’s usually no need as we have hooks placed throughout EE to allow you to modify the details.
The function I provided above should go within your child themes functions.php file or within a Site Specific Plugin. It hooks in and alters the details without the need to modify any of the core files 🙂
|
