Archives: Replies

Helen, I think the problem might be that ajax is running out of memory when trying to export all the event data from 2000+ events.

Loom video for more info: https://www.loom.com/share/a91eab84da4e44d1870c1b39b532c8b4?sid=6c141c63-8345-4dc7-b4d9-30317b8240e9

It’s not causing any front-end issues.  I just get this crash notification whenever I update something.  I just want to ensure that it’s not affecting functionality somewhere I don’t see.

Trust me.  I’ve done all the iterations you’re talking about.  It shouldn’t matter if both options and variations are listed above.  The checkboxes below should properly enable or disable those functions.

But yes, this is a dummy event so feel free to remove the options and check the math on the variations.

Ok

But I deleted the new repeated date (2023/11/26 – 13:00), because I cannot wait the solve this issue. To get a solution, I created a additional event for the extra date.

Please try to get a solution for next update, a solution to link the ticket to the “repeat interval date” and not to his index. Ticket must follow the right event date in case of extra date added.

Sorry, this is my shortcode: [add_eventon eventtop_style=’2′ event_past_future=”future” ux_val=’3′]

 

Thankl you

please if you can help me to find a solution it will be wonderfull… I tried all day long but nothing… if you can help me setting this It will be a super elegant success… so I can save as a sample for future event…

Thanks Thanks …

 

Erik Messori – Photojopurnalist

I also added Seat Number and removed Asiento estándar.

About the duplicate. Are you sure that this custom code is the only one?

https://arsmagna.live/wp-admin/admin.php?page=edit-snippet&id=7

Ashan,

The same on dev2:

https://dev2.myeventon.com/wp-admin/post.php?post=51612&action=edit

I removed Nov 3 and purchased Nov 4th:

Then I added Nov 3 back and then purchased ticket from the 4th moved to the 3rd: