Support

May 16, 2018 at 1:54 pm

Hi TKT,
I can advise to rule out a plugin conflict.

You can rule out a plugin or theme conflict is by installing the Health Check plugin, then go to WP → Dashboard → Heath Check → Troubleshooting. There you’ll Enable Troubleshooting Mode, then once that’s activated you’ll reactivate Event Espresso only via the Health Check’s Troubleshooting item in the WP admin bar. At that point, can you check to see if the issue with the CSV persists?

May 18, 2018 at 6:51 am

Were you able to export a CSV previously?

You could check with your host to see if there’s a mod-security rule being triggered when you try to export the CSV. They may be able to remove that rule so you’ll be able to export the CSV.

May 22, 2018 at 2:56 am

We are able to execute non-Event Espresso CSV file previously. So I don’t think it has to do with the host (Siteground) and I just did double check that with them.

It actually has almost nothing to do with the CSV itself as it’s not the CSV that is failing, it’s the method used to generate the link for the batch job to generate the CSV so its before the CSV has even started to generate.

It does sound like the request is hitting some kind of mod_sec rule on the server, when you say you checked may I ask what you asked them specifically, and their response?

With WP_DEBUG enabled and that error is triggered, are there any other errors? For example:

Warning: Cannot modify header information – headers already sent by….

The only way I can reproduce the error you are getting is to send headers to the page before they are expected – http://take.ms/rH9DR

May 22, 2018 at 5:08 am

The headers already sent error is the only way I’ve been able to reproduce this, but the odd part is that it’s not working for you even with WP_Debug disabled and Health Check troubleshooting mode (which is why I suspect something on the hosts side) so I don’t know if this is going to fix the problem for you.

As for the error your getting:

Warning: Cannot modify header information – headers already sent by (output started at /home/lertops2/public_html/wp-includes/functions.php:3903) in /home/lertops2/public_html/wp-includes/pluggable.php on line 1216

Looking at the line numbers, it looks like something is throwing ‘The called constructor method for’ notice, that’s usually something like:

Notice: The called constructor method for WP_Widget is deprecated since version 4.3.0! Use __construct() instead.

Do you see anything like that on the page? Or in the error logs?

Are you 100% sure you test troubleshooting mode with only EE active? The reason I ask is you wont get the above notice on a default install with just EE activated.

May 22, 2018 at 9:38 am

Ok, with WP_DEBUG enabled can you use the Health Check plugin, enter troubleshooting mode and enabled only Event Espresso.

Now test a registration and see what happens, if any errors are thrown on the page please post those here.

May 22, 2018 at 10:16 am

Notice: The called constructor method for WP_Widget in GFWidget is deprecated since version 4.3.0!

Are you running gravity forms? If so are you using the latest versions?

You could temporarily disable GF and see if the export works.

Notice: Trying to get property of non-object in /home/lertops2/public_html/wp-content/plugins/easy-social-share-buttons3/lib/core/essb-adminbar-menu.php on line 12

Same with the easy social share buttons plugin, temporarily de-activate that (at the same time as Gravity Forms, assuming it is gravity forms) and see if the export works then.

May 22, 2018 at 10:45 am

Notice: WC_Cart::get_cart_url is deprecated since version 2.5! Use wc_get_cart_url instead. in /home/lertops2/public_html/wp-includes/functions.php on line 3840

Unfortunately, I have no idea what that error is from.

You need to test EE without any additional plugins running and using a default theme, using the Health Check troubleshooting mode is the easiest way to do that without affecting your site’s users but sometimes it doesn’t work.

If you prefer you can try once again with WP_Debug disabled, enable troubleshooting mode in Health Check and then double check that it has disabled all plugins and switched to a default theme, then enable EE and test again. You mentioned you’ve already tested this but it would be good to double check that all plugins were indeed disabled.

The other option is to temporarily deactivate all other plugins and retest, switch to a default theme and retest. If it works then it’s a plugin/theme conflict, re-enable each plugin one by one and test between each one to see which one causes the problem again…

If it still doesn’t work with no plugins and a default theme, its something on your host’s side blocking the request.

We have some documentation on this here: https://eventespresso.com/wiki/troubleshooting-checklist/

May 22, 2018 at 11:17 am

It could be a setting in any one of those plugins that for some reason isn’t active right now, but I’m just guessing as I don’t know.

Flush your permalinks (Settings -> Permalinks -> Save) just for good measure and retest but why it would work after de-activating then re-activating I have no idea.