Support

February 8, 2018 at 4:28 am

Hi there,

1) Is there any way to know what exactly happened that made those messages appear? WP_DEBUG was not true as this is our live website.

If your server logs errors (it should) then you may find the error within that.

Usually, your host will have a section to view the error logs within your control panel, or if you have FTP access look for an error_log file within the root directory for your site.

2) How do I find out if there is an actual problem with the database tables that will cause issues down the road?

We need the error to know if there is actually a problem but EE will attempt to fix any issues with the DB as it finds them anyway, if there is a problem that couldn’t be fixed you would see an error on each request made.

If your server is not logging error you can temporarily add this snippet:

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

To your wp-config.php file and re-run some tests on the system (try exporting the registrations again), any errors will be logged to /wp-content/debug.log and not shown directly on the site.

(Note don’t leave that enabled on your live server, just run some tests and see if you find any errors from EE in the log, then remove it again or set WP_Debug back to false)

3) Checking the exported CSV file, it was found that the UTF8 encoding bytes are missing. The resulting file opens up in Excel but all unicode characters are rendered as ‘garbage’. Manually adding the UTF8 encoding bytes into the file makes it open properly. What would cause this?

Are you filtering the CSV using the FHEE__EE_CSV__begin_sending_csv__start_writing at all?

The first output sent to the CSV uses this:

echo apply_filters('FHEE__EE_CSV__begin_sending_csv__start_writing', "\xEF\xBB\xBF" );

Which should set the file to UTF-8, what are you adding to the beginning of the CSV to force it to work?

4) Regarding the same exported CSV file, a custom column I added is missing it’s header name now. It worked perfectly before upgrading but now the header name refuses to show up. The data for the custom (post meta) column is still exported just fine, though.

I’d recommend you set the column on each row regardless of whether or not you actually assign a value to it.

$reg_csv_array[ 'Course ID' ] = '';
$my_course_id = get_post_meta( $event_id, 'my_course_id', true );
if ( $my_course_id != '') {
$reg_csv_array[ 'Course ID' ] = $my_course_id;
}

Have you confirmed that get_post_meta() is pulling in a value?

February 8, 2018 at 7:30 am

I’ve had a look at the error_log file and the last entry seems to be in Nov 2017 so I’m not sure if it is actively logging or not.

Unfortunately, without the error, we don’t know what happened. You can check over the database to confirm all of the required tables/columns have been created, but, as mentioned EE will attempt to fix it anyway so its unlikely any will be missing otherwise you’d still be getting the errors above.

I have not added anything to the CSV at all.

You mentioned above you’re manually adding the amending the CSV to make it work, I’m assuming you’re adding the same as the filter above?

I don’t understand this part of your reply. Can you explain it?

In your code, you only set $reg_csv_array[ ‘Course ID’ ] if you have a value for $my_course_id;

In 4.8.25 EE pulled all of the registrations in a single request and then built the CSV, this is fine for smaller registrations but not larger groups, so we introduced a ‘batch’ method that pulls in smaller groups (default 50) of registrations into a temp file and build out the CSV as we go.

So let’s say the first batch of registrations don’t have a value for $my_course_id, you’ve just built out the temp file containing all of the details without a Course ID header. The next batch doesn’t know where to include the data. Whereas if you use the code example I gave you above, the column is always created for each registration row, but it’s empty if you don’t have a value.

Try this code:

https://gist.github.com/Pebblo/5c829126cdc85ab942db3d880e84cc91

February 12, 2018 at 2:19 pm

Hmm, yeah you’re right.

We’ll need to do some investigating into this, but for the time being what you can do is switch EE back to the ‘old’ export system.

To do that you just need to add:

define('EE_USE_OLD_CSV_REPORT_CLASS', true);

To your wp-config.php file, somewhere above the /* That's all, stop editing! Happy blogging. */ line. Having that in your config file tells EE to use exactly the same process you were using before and ignores the batch method (your new custom code above should still work absolutely fine).