|
raffy
|
October 14, 2019 at 6:53 am
The maximum number of inputs on this page has been exceeded. You cannot make edits to this page because of your server’s PHP “max_input_vars” setting.There are 1105 inputs and the maximum amount currently allowed by your server is 1000.Please contact your web host and ask them to raise the “max_input_vars” limit.
I got this warning when I started making an event where I have around 15 datetimes for 9 ticket bundles. I ignored the warning and finished up setting up
the event.
I made a second similar event. I got the same warnings.
I started testing the registration and the site started slowing down.
Would you have an idea if the events that I created hard to execute or should I look into my server for errors? Any insights?
|
|
Tony
|
October 14, 2019 at 7:50 am
Hi Raffy,
The notice is telling you that the value for max_input_vars on the server is 1000 but the editor has more than 1000 inputs on the page.
max_input_vars tells your server how many inputs to read on the page before ignoring the rest, so if you continue to add more tickets/datetimes etc to the page you’ll eventually find that they are ignored and disappear when you save (because your server ignored them, meaning they can’t actually save).
So, in short, if you’re getting that notice you have more inputs on the page than your server allows and you need to increase the max_input_vars setting.
I made a second similar event. I got the same warnings.
As soon as you go over the max_input_vars value, EE will throw that warning.
I started testing the registration and the site started slowing down.
What is slowing down on your site?
Would you have an idea if the events that I created hard to execute or should I look into my server for errors? Any insights?
Do you need that number of datetimes within a single event?
Ideally, you would break the event down some so you don’t have so many datetimes/tickets in a single event.
Can you link me to the event in question so I can take a look?
|
|
raffy
|
October 14, 2019 at 8:04 am
https://incognitus.ph/macquarierun-internal/macquarie-charity-fun-run-2020-3k-5k-10k-pairs/
I am not sure why the site slowed down. I have not quantified the slow down. But coincidentally, my site started timing out.
The event is a fun run that requires us to produce a race kit that will go through packing and delivery. After the run, the participants will be checked-in through a maximum of 10 stations. The check-in will help us track if a person already availed.
We are trying to use the event app to
- track the status of the package – 2 statuses
- check-in participants to 10 stations during the event – 10 stations
- check-in 4 datetimes for the 4 event categories (perhaps we can do away with this)
|
|
Tony
|
October 14, 2019 at 9:22 am
I can’t see any slowdown on the site?
Each page load is rather snappy and I didn’t see any issues during the registration.
|
|
raffy
|
October 14, 2019 at 4:43 pm
Hi, Tony.
Yes. It seems to have improved. The thing about it is I don’t know why the slowdown and why it picked up again. I’ll monitor.
I suppose it was just coincidental then.
That said, what are your thoughts on the way intend to use the app and how it might impact performance on event day? We expect 2000 participants, using the app and hence the website within 3-hour window. Any tips, warnings.
If I were to temporarily bump up my VPS service, what should I get more CPUs or more memory or both? Something else?
|
|
Tony
|
October 15, 2019 at 4:19 am
15 datetimes and 9 tickets are not huge numbers it’s just getting a little high for a ‘normal’ event that can often be managed a little better.
So nothing right now is jumping out to me to say you would have a problem, the apps use the REST API and only pull in the specific date they need/use so those requests are a little more efficient than say loading the event page.
What recourse do you have available on your VPS now?
Is this the first event you’ve run with this setup? Will you likely be running more?
If I were to temporarily bump up my VPS service, what should I get more CPUs or more memory or both?
It’s your database that is going to to be doing most of the heavy lifting here (as usual), personally I’d go for both and monitor to see if it was needed.
If this is your first event, use it as a test and monitor the server during peak usage, your betting having more resources and paying slightly more during your test than having the site go down due to lack of memory for example and you scramble to fix it in that peak time, make sense?
If you see that the requests hardly made a dent in the server, you know for the next similar setup you don’t need as many resources and so on.
|
|
raffy
|
October 16, 2019 at 6:53 am
I just upgraded my plan from 1 vCPU to 2 vCPU and 2GB to 4GB Memory
This is the first time I am running this setup. I usually have 3 tickets, 1 datetime each
If I can make the multiple station check-in work both on EE4, our Internet connection, and actual event flow, yes I will have more events on EE4 like this.
I am currently on Ubuntu NGINX, PHP, MariaDB. I do have to upgrade all of them.
So I am working on setting up a new server and start fresh on another VPS on Linode and migrating my site there.
I read that OpenLiteSpeed is even better than NGINX. So I am trying that on DigitalOcean with another domain. What are your thoughts on EE4 running on OpenLiteSpeed?
Thanks for all the advise.
|
|
raffy
|
October 16, 2019 at 6:55 pm
The system started hanging each time we tried downloading reports. When we tried downloading 1-3 filtered reports the system would hang. We would reboot the server and it would hang again when we downloaded reports for our 15 date time per ticket event.
The reports we got to downloads have date times that were all zero despite having information assigned to them in the event.
I want to share that we resolved this by using an ee4-snippet from Github that allows us to exclude certain fields/column. As soon as we removed the datetimes we could “stress-test” the system by downloading 15 reports consecutively.
|
|
Tony
|
October 17, 2019 at 3:12 am
What are your thoughts on EE4 running on OpenLiteSpeed?
I’m not a sysadmin and don’t have much experience with it, so I can’t give you any useful comments here.
I want to share that we resolved this by using an ee4-snippet from Github that allows us to exclude certain fields/column. As soon as we removed the datetimes we could “stress-test” the system by downloading 15 reports consecutively.
There’s a loop for each registration for datetimes, so each of your registrations will be pulling those 15 datetimes and then looping over them to get the datetime values, sounds like your server is failing with that loop.
Are you using the batch export? Meaning when you click to export it shows something like this:
https://monosnap.com/file/WInYnS7r6Nchqab6gE7D58VPWqZyPW
|
|
raffy
|
October 17, 2019 at 4:02 am
Yes, we are using the batch report. It usually hangs for the filtered batch report.
Oh and just now, we just experienced a 414 Request-URI Too Large error. I tried to replicate the 414, I just end up hanging the WP when I do the batch report even with the excluded columns plugin.
When I filter I get this in the URI
/wp-admin/admin.php?s&_wpnonce=2c4aa32c55&_wp_http_referer=%2Fmacquarierun-internal%2Fwp-admin%2Fadmin.php%3Fpage%3Despresso_registrations&action=-1&month_range&EVT_CAT=-1&_reg_status=RAP&page=espresso_registrations&route=default&perpage=10&approve_registrations_nonce=5e53509b46&approve_and_notify_registrations_nonce=27b363aad2&decline_registrations_nonce=377c1020c4&decline_and_notify_registrations_nonce=acb2e4cf67&pending_registrations_nonce=82446fdd03&pending_and_notify_registrations_nonce=be61991e42&no_approve_registrations_nonce=cd9e698976&no_approve_and_notify_registrations_nonce=43791af72b&cancel_registrations_nonce=c3119f5730&cancel_and_notify_registrations_nonce=f8cbc0483f&trash_registrations_nonce=85fd7e2ce3&paged=1&action2=-1&default_nonce=1e480f6f7d
And this when I download a filtered report
/wp-admin/admin.php?page=espresso_batch&use_filters=1&return_url=%2Fwp-admin%2Fadmin.php%3Fs%3D%26_wpnonce%3D2c4aa32c55%26_wp_http_referer%3D%252Fmacquarierun-internal%252Fwp-admin%252Fadmin.php%253Fpage%253Despresso_registrations%26action%3D-1%26month_range%3D%26EVT_CAT%3D-1%26_reg_status%3DRAP%26page%3Despresso_registrations%26route%3Ddefault%26perpage%3D10%26approve_registrations_nonce%3D5e53509b46%26approve_and_notify_registrations_nonce%3D27b363aad2%26decline_registrations_nonce%3D377c1020c4%26decline_and_notify_registrations_nonce%3Dacb2e4cf67%26pending_registrations_nonce%3D82446fdd03%26pending_and_notify_registrations_nonce%3Dbe61991e42%26no_approve_registrations_nonce%3Dcd9e698976%26no_approve_and_notify_registrations_nonce%3D43791af72b%26cancel_registrations_nonce%3Dc3119f5730%26cancel_and_notify_registrations_nonce%3Df8cbc0483f%26trash_registrations_nonce%3D85fd7e2ce3%26paged%3D1%26action2%3D-1%26default_nonce%3D1e480f6f7d&filters=a%3A5%3A%7Bi%3A0%3Ba%3A1%3A%7Bs%3A6%3A%22STS_ID%22%3Bs%3A3%3A%22RAP%22%3B%7Ds%3A4%3A%22caps%22%3Bs%3A10%3A%22read_admin%22%3Bs%3A24%3A%22default_where_conditions%22%3Bs%3A15%3A%22this_model_only%22%3Bs%3A8%3A%22order_by%22%3Ba%3A2%3A%7Bs%3A8%3A%22REG_date%22%3Bs%3A4%3A%22DESC%22%3Bs%3A6%3A%22REG_ID%22%3Bs%3A4%3A%22DESC%22%3B%7Ds%3A5%3A%22limit%22%3Ba%3A2%3A%7Bi%3A0%3Bi%3A0%3Bi%3A1%3Bi%3A10%3B%7D%7D&action=default®istrations_report_nonce=cb82b3c71e&return=-1&batch=file&job_handler=EventEspressoBatchRequest%5CJobHandlers%5CRegistrationsReport&default_nonce=1e480f6f7d
What info do you need to help figure this one out and where should I look for it?
-
This reply was modified 5 years, 1 month ago by
 Tony. Reason: Remove domain
-
This reply was modified 5 years, 1 month ago by Tony.
|
|
raffy
|
October 17, 2019 at 4:04 am
Should I edit the link the next time and not share the whole URL? 😉
|
|
Tony
|
October 17, 2019 at 4:48 am
Should I edit the link the next time and not share the whole URL?
It shouldn’t matter, but I’ve edited the post anyway.
What info do you need to help figure this one out and where should I look for it?
Just from Googling the above error on NGINX:
https://stackoverflow.com/questions/1067334/how-to-set-the-allowed-url-length-for-a-nginx-request-error-code-414-uri-too
|
|
raffy
|
October 29, 2019 at 4:16 am
Thank you, Tony.
|
