Support

Home Forums Event Espresso Premium 410 Gone Error when using filtered CSV Report

410 Gone Error when using filtered CSV Report

Posted: November 7, 2018 at 4:05 am


rachel@harrisonsmith.me.uk

November 7, 2018 at 4:05 am

Hello,

I am getting this error when using the Filtered CSV Report:
Gone

The requested resource
/wp-admin/admin.php
is no longer available on this server and there is no forwarding address. Please remove all references to this resource.

This stopped working this morning (I have already pulled off some reports successfully earlier today). I have not upgraded any plug ins or WP and not made any changes to any code anywhere. The only difference between successfully creating the report and this error message was registering some people for events. I can still create the unfiltered CSV successfully.

I’m not technical, so I’m not going to be able to delve into code unless I get very explicit instructions on where to look! Can anyone help?

Thanks in advance


Tony

  • Support Staff

November 7, 2018 at 5:10 am

Hi there,

It sounds like you are hitting either a limit or some form of security rule on the server.

How many options are you filtering on the registration list?

If you go to Event Espresso -> Registrations.

Set only the status filter to ‘Approved’ (or another status that has registrations) and click filter – http://take.ms/4CGqw

Now run a filtered CSV, does it work then?


rachel@harrisonsmith.me.uk

November 7, 2018 at 5:50 am

Tony,

I cleared all filters, applied the Approved filter and can successfully create the filtered report.

I tried the same again, clearing all filters, then trying to filter by ‘This Month’ and I get the 410 error. I also get the error when I select this month (November). Before doing both these searches, I closed the window and launched the page again.

Thanks

Rachel


Tony

  • Support Staff

November 7, 2018 at 9:29 am

Ok, thanks for checking.

So you can consistently export using just the status filter, but anything other fails?

I’d recommend creating a ticket with your host to confirm the request is not triggering a mod_sec rule or similar that is canceling the request.

410 errors are thrown by the web server itself when it doesn’t know what to do with the request so it sounds like something on the server side.

You must be logged in to reply to this support post. Sign In or Register for an Account

Support forum for Event Espresso 3 and Event Espresso 4.
Documentation for EE3 and EE4
Documentation for Event Espresso 3

Documentation for Event Espresso 4

Status: publish

Updated by  Tony 1 week, 5 days ago ago

Topic Tags

Tagged: 

Notifications

This topic is: not resolved
Do NOT follow this link or you will be banned from the site!
[i]
[i]