|
cprdave
|
November 19, 2020 at 7:27 am
We have a new problem. All of a sudden, the tickets for our events are appearing out of chronological order. This has never happened before. I drag and drop them into the correct order, but after updating, they are scrambled again. I looked at your 2018 answer to a similar problem, and it appears to be related to the programming of the WordPress theme. Josh’s input is here: https://gist.github.com/joshfeck/a8e28b9cfecd89308fbea4c152f546c9
Is this the solution, or is something else going on?
Thanks!
|
|
Tony
|
November 19, 2020 at 7:49 am
Hi there,
The snippet in that link is filtering the ‘next post’ and ‘previous post’ links but your thread is referring to tickets so is that the correct link?
Can you link me to an event this is happening on so I can take a look?
|
|
cprdave
|
November 19, 2020 at 7:52 am
Hi Tony. It’s only happening where we list the tickets, the tickets display correctly on the website, but they scramble on the admin page. Am I making sense?
|
|
Tony
|
November 19, 2020 at 8:37 am
Oh in the event editor, this section?
https://monosnap.com/file/wCtQf8dcBxvgiFlKWcbeAAaaoQWDeI
If so, open up Chrome Dev Tools (or similar if using another browser, most have it) on that page and look in the ‘console’ section, any errors?
|
|
cprdave
|
November 19, 2020 at 8:46 am
Ahhhh….yes, I see this error:
Uncaught TypeError: Cannot read property ‘value’ of undefined
at fusion-builder.js:1
at Function.v.each.v.forEach (underscore.min.js:2)
at Object.<anonymous> (fusion-builder.js:1)
at i (jquery.js:2)
at Object.fireWith [as resolveWith] (jquery.js:2)
at x (jquery.js:4)
at XMLHttpRequest.c (jquery.js:4)
Can you tell me what I should do about this?
|
|
Tony
|
November 19, 2020 at 9:11 am
Can you send me a copy of the theme and I assume the fusion builder plugin?
Are you using the latest versions?
|
|
cprdave
|
November 19, 2020 at 9:15 am
Hi Tony,
After digging around, I discovered that the problem was not occurring on our other events. The problematic event had TONS of residual tickets encompassing over two years. I duplicated the page. Threw out the old tickets, dragged and dropped the tickets into the proper sequence, and they seem to be okay now. Previously, the drag and drop did not hold after updating. All I can assume is that the huge number of old tickets somehow broke the sequencing function. Any other insights?
|
|
Tony
|
November 20, 2020 at 4:16 am
Yeah, that can happen if you ar hitting various limits on your server, the one that jumps to mind is max_input_vars but it could be any.
Ideally, if you have many tickets in a single event you’ll want to break those out into small events such as doing the above quarterly (or less depending on how frequently you create tickets) just to keep your event ‘lean’.
|
|
cprdave
|
November 20, 2020 at 7:20 am
Thanks again, Tony. We offer CPR classes several times a week. Each ticket is for a different date. My experience is that EE won’t let us delete them after the dates have passed, without having to go through the entire de-registration process, so they accumulate quite rapidly. I’d love it if there were a better way. But thanks again for your help. I’ll close this ticket.
|
|
Tony
|
November 20, 2020 at 8:23 am
Yeah EE won’t let you delete any entities that have related data as you then leave orphaned data in the database.
For example, if you just a ticket from within an event then the registrations, datetimes etc that link to that ticket no longer have a valid ticket object. Which means anywhere in EE that expects the ticket then breaks etc (a fair bit more to it than that, but that’s the general idea).
However, we are working on making this a little easier in a future version, I don’t have an ETA but just letting you know that we are aware of it and are working on a better solution.
|
