|
Daniel
|
August 12, 2020 at 9:09 am
Hello!
I have 30 datetimes and 30 tickets on a single event (it’s 30 session class and we put date windows on the tickets to lower the price after each session). I created these with the API. Everything works fine (event shows and can be purchased) until I go to the Event edit UI panel and try to change anything.
The panel takes a long, long time to refresh with the new results and I see two things:
1) an error message about the wait list
An error has occurred:
The data for the “Event Wait List Settings” form, is either missing or was not submitted properly.
2) the Maximum number of tickets allowed per order for this event is set to zero and the Display Ticket Selector is set to No
This causes the ticket selector not to display on the site even though it had displayed previously (when event was created using the API and before editing in the UI).
I believe there is either an unreported timeout or a form size data size issue happening in the UI.
I am able to update the specific data points for the affected events using the events API PUT so I can recover from this issue… but it means that this type of event is not editable.
I hope you find this information useful to recreate this issue.
Please let me know if I can do anything to reveal more clearly the problem I am seeing.
TY!
|
|
Daniel
|
September 4, 2020 at 8:23 am
Hello? Any feedback on this bug report?
TY!
|
|
Tony
|
September 9, 2020 at 7:32 am
Hi Daniel,
It sounds like your hitting a limit set on your server rather than within EE itself.
The settings I can think to check are:
max_execution_time = 90
max_input_time = -1
max_input_vars = 5000
memory_limit = 2048M
post_max_size = 64M
upload_max_filesize = 8M
The values I’ve added aren’t by any means a recommendation but what I have set on one of the sites I’m testing this on.
Have you tried creating a test event with 30 datetimes/tickets manually to see if you run into the same issue?
I have a few events across different sites with higher numbers of datetimes and tickets all working fine, although a little slow when updating as the current event editor isn’t designed to higher numbers of datetimes/tickets efficiently (we are rewriting the event editor to work around that).
Whilst I can’t think of a reason for it to be different using the API if you’d like to share the code you are using I can test it on one of the sites I mentioned above to see if anything shows up there?
|
