Support

March 5, 2019 at 4:05 am

Hi there,

What does this error mean?

It means the page has 8000+ inputs loaded but as far as EE is aware, your server is set to only allow the first 1000 so the notice is to inform you that the value needs to be increased for all of the settings to save.

However, we cache the value and looking at your PHP info output it looks like max_input_vars has been updated to 10k, so you’ll need to make sure EE pulls that latest value.

Go to Event Espresso -> General Settings -> You organization.

Make a small change, say add a character to the end of Organization name save the config. Then revert the change and save again, that will rebuild the config and recache the latest value.

Our events have a lot of datetimes, but over 8.000 inputs?

It’s not just datetimes, it’s pretty much anything that loads on the page.

We’ve seen themes load over 14,000 inputs on the EE event editor, almost all of which were unused on our outputs but still loaded.

In any case, datetimes and tickets both have multiple inputs for all of the various settings on them so yes they have multiple inputs and the more you add, the closer to your max_input_vars limit you will get.

You say you have a lot of datetimes, how many is that?

How many tickets?

March 5, 2019 at 5:14 am

I’m not sure what the backend mask is, do you mean the event editor now doesn’t load?

You say you have a lot of datetimes, how many is that?

How many tickets?

March 5, 2019 at 7:25 am

Ok, for some reason you aren’t answering my questions so I’ll ask again.

You say you have a lot of datetimes, how many is that?

How many tickets?

If you have a lot of datetimes and times you may be hitting a query limit on the server, check the servers errors logs around the time the event editor fails to load, any errors?

March 11, 2019 at 6:32 am

Ok, that would be considered a high number of datetimes and is likely causing the page to time out.

When you say the ‘event editor mask’ doesn’t load, what do you see, a white screen?

Have you checked the servers error logs for any errors around the same time that you try to load the event editor?

March 11, 2019 at 7:26 am

Error 500 is a catch-all error shown to visitors, we’ll need the full error from the site’s error logs.

You will usually have a section in your host’s control panel to view the error logs, so can you check there for the full error?

With the number of datetimes you have it is likely you are hitting a limit set on the site, but there are multiple possibilities so we need the error to know more.

If you hosts error log doesn’t show anything from EE, you can add this:

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

To your sites wp-config.php files to log the errors to /wp-content/debug.log

So after adding the above, trigger the error and view the above file, does it show an error then?

March 11, 2019 at 10:13 am

That could be a file permissions issue where the server isn’t allowed to add a new file to the wp-content directory. In which case you can add a new file there using FTP. You’ll name the file debug.log

March 11, 2019 at 3:31 pm

Where exactly did you add the code above in the wp-config.php file?

It needs to be above the /* That's all, stop editing! Happy blogging. */ but definitely above require_once(ABSPATH . 'wp-settings.php');

So mine looks something like this: https://monosnap.com/file/eGdAz5tOSjacoQ9h5BiQieCGAUhiN8

If that still doesn’t work, try using just define( 'WP_DEBUG', true ); and then trigger the error… a word of warning when doing so, using WP_DEBUG in the last way I mentioned means your site will display ALL warning, notices, error, etc to everyone, so enable it, throw the error, copy it, then disable WP_DEBUG again.

March 13, 2019 at 5:40 am

Ok, I suspect that’s another limitation set on your server, but which I’m not sure.

The code that throws the above pulls the ticket_IDs POST’d to the server and checks it is an array and if not, it throws the above.

It’s likely going to be a side effect of having almost 100 datetimes within a single event which your server can’t handle with the current implementation. I tested a similar event with 5 tickets, each with 15 datetimes and didn’t have any issues when updating although I don’t recommend using this setup.

If you add another event with a couple of tickets/datetimes, does that work as expected?

March 13, 2019 at 7:36 am

Smaller events with how many datetimes/tickets?

It could be another plugin interfering with the request although it seems more likely to be a config issue.

You could try using the Health Check plugin to narrow down the cause.

You install 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 persists?