Support

July 21, 2016 at 4:43 am

Hi Clifford,

Do you have access to the servers error logs?

If you enable WP_DEBUG on the site and retry the export do you see any error messages?

If you navigate to Event Espresso -> Maintenance -> System Information.

Search for wp_memory in that page, what value is set there?

July 29, 2016 at 1:40 am

We prefer not to enable WP_Debug as our site is live. We’d like to try other alternatives if possible first.

We need to know if any errors are being thrown to be able to fix them, if you have access to the servers error logs (and error logging is enabled) you can view them either through your control panel, or by viewing the error_log (or similar) file on your server.

You can enable WP_Debug but prevent the errors from being displayed on your site using:

define( 'WP_DEBUG', true ); // Or false
if ( WP_DEBUG ) {
    define( 'WP_DEBUG_LOG', true );
    define( 'WP_DEBUG_DISPLAY', false );
    @ini_set( 'display_errors', 0 );
}

Which will then log the errors to a debug.log file within /wp-content/

However my host increased the PHP memory to 1g.

That’s fine, WordPress will use the high value for the memory limit so wp_memory will be ignored.

Do you need a login to check this? if so, let me know if it’s safe to post it directly here and if i need to put it in some < tag >?

Currently we don’t need login details and no, it is not safe to post login details on the forum.

Can you check with your host and confirm if the request is being blocked by some form of security server side (possibly a mod_sec rule)?

August 1, 2016 at 3:05 am

If you add this line of code to wp-config.php:

define( 'EE_USE_OLD_CSV_REPORT_CLASS', true );

Does the export work then?

August 2, 2016 at 4:59 am

So basically what that code does is switch the CSV reports to use the ‘older’ version of the exports we have in place (same output but created differently within EE)

The new system creates a temporary folder within /wp-content/ and writes the CSV in smaller sections to a file within that directory. The reason for this is to allow for batch processing of large registrations. Lets say you have 200 registrations, we export say 50 registrations 4 times and write each section to the file, when ready EE directs you to download the file.

The old system grabs all 200 registrations and creates the file in one go.

This isn’t a problem from smaller registration numbers but will be for larger numbers.

As you’ve already disabled all plugins and switched themes it looks like something on your server is preventing the request from creating a new directory and blocking the request so if you want to switch back to the new CSV reporting (you don’t need to if your not running large events) I’d recommend discussing this further with your host to see if they can provide any feedback.

August 2, 2016 at 9:48 am

You’re most welcome, Clifford.

If you have any further problems please do let us know 🙂