Support

December 1, 2020 at 6:08 am

Ok, so it may be something within the custom code and/or the registration itself so the first thing I would do is try to narrow down the registration(s) causing the CSV to break.

Find your most recent registrations and find the events they are for, then view the registration list for each of those events and export. If ifs a specific registration that should help narrow it down a little as you’ll now know which event it was (assuming that all event registration reports work except one).

Once you’ve narrowed down the registration you start digging into the registrant questions to see if anything stands out there.

You could try removing the above code and commenting out the add_filter() lines to stop them hooking in, or de-activate the plugin they are within to see if the same broken export then works.

If you find a specific event causing it I can take a look at the export and see if anything stands out there if preferred?

December 1, 2020 at 7:57 am

Ok, so the first test to do is to change when the above filter runs.

Change this:

add_filter('FHEE__EventEspressoBatchRequest__JobHandlers__RegistrationsReport__reg_csv_array', 'tw_ee_espresso_reg_report_filter_columns_ordered', 10, 2);

To this:

add_filter('FHEE__EventEspressoBatchRequest__JobHandlers__RegistrationsReport__reg_csv_array', 'tw_ee_espresso_reg_report_filter_columns_ordered', 100, 2);

Retest, what happens?

December 2, 2020 at 5:31 am

When I remove the function, it works:
https://we.tl/t-5l8hpiVOYe

That CSV still looks broken to me? Its better than before but Line 1 shows ‘PHOTOBASTEI 2.0’ in the Venue column and then the row below is a column out.

I think the reason is that we newly added new fields for the users to add their instagram accounts

Possibly, its still an odd issue though.

To add those columns to the CSV you can just add:

'ig-name-de',
'ig-text-de'

After this line: https://gist.github.com/altuno/71b100d90ebaf2b8da256ecdef5f421b#file-gistfile1-txt-L46

So it looks something like:

__('Transaction Promotions', 'event_espresso'),
'ig-name-de',
'ig-text-de'

Then you’ll have the ); thats already there to close the array.

I’m not so sure that’s going to fix although it does seem to break on the ig-text-de column.

—

When you downloaded a CSV does it download when you click the button or does it redirect you to another page with a progress bar and then it downloads?

December 2, 2020 at 6:27 am

Did you try what I suggested above?

December 2, 2020 at 8:58 am

So I spent some time digging into this and I can’t reproduce, however, there have been some changes to EE since you added those snippets which may be affecting this so let’s get those updated and see what happens from there.

The fact that you click the export and wee a ‘progress bar’ means you are using the batch export system (which you should be) and that has different filters available than the ‘old’ system. It checks for any of the old filters in use and applies them into the new system but by doing that EE is having to jump through various hooks so its best to switch to using the new filters (for the most part the only change needed is the filter name itself).

Anywhere you have this: FHEE__EE_Export__report_registrations__reg_csv_array

You can change it to: FHEE__EventEspressoBatchRequest__JobHandlers__RegistrationsReport__reg_csv_array

That’ll switch you over to the new filters (not so scary 😉 ).

Next, each of the CSV rows should have the exact same rows and some of the snippets you are using check for values and/or if the row is for the primary registrant before adding the column. That means some rows may have the columns added and others not, which isn’t a great for the CSV as then commas don’t match (likely the issue here).

Fixing that involves switching the code to always add the column and rather than try to explain that further, I’ve done it here:

https://gist.github.com/Pebblo/d1ab608fac2c68450dab0f458b6baa45

Try that updated code in place of yours and see what happens then.

December 2, 2020 at 2:39 pm

It must be due to the code section where we set the array of “allowed fields” i guess, because when I remove it, the default fields seem to work.

Ok, but why all of a sudden and I can’t reproduce so something else must be going on with it.

We’ll need to see what is happening within that function for this and the easiest way to do that is using this little write_log function:

if ( ! function_exists('write_log')) {
   function write_log ( $log )  {
      if ( is_array( $log ) || is_object( $log ) ) {
         error_log( print_r( $log, true ) );
      } else {
         error_log( $log );
      }
   }
}

Add that to the top of your file and then uncomment these lines.

Next, in your sites wp-config.php file, add this:

https://eventespresso.com/wiki/troubleshooting-checklist/#wpdebug

You should already have something like define( 'WP_DEBUG', false ); and that snippet replaces that single line.

Then run an export (I recommend you filter down to the lowest number you can just to make the log easier) and export.

Then check /wp-content/debug.log and search for ‘filtered_csv_row’ you’ll see 2 arrays, one is the registration row and the other is the CSV row. Add them to a\ gist so I can view them please.

December 3, 2020 at 3:44 am

Looks like this is due to translations and thats likely why I can’t reproduce.

One more with a slight change to the code to confirm.

Change the write_log call to be:

write_log(
    array(
        'csv_row' => $csv_row,
        'allowed_fields_in_order' => $allowed_fields_in_order,
        'filtered_csv_row' => $filtered_csv_row,
        'registration_db_row' => $registration_db_row
    )
);

Then repeat the above export, please.

December 3, 2020 at 8:19 am

Yeah, its a translation issue. You said no changes were made on the site, so no plugins updates, nothing?

What are you using for translations on the site?

For your reports the initial request is not translating the CSV headers, see HERE

But then on any additional requests, they are translated to Deutsch, see HERE. You also have some fields translating and others not.

All of the combined is what is causing the problem here as the ‘allowed fields’ are valid for the first request, then they aren’t for any subsequent requests so the fields are missing. It isn’t a case of missing commas but array key fields that don’t match so the values aren’t being set.