Archives: Replies

All of your orders are still Processing:

Could you go to EventON > Tickets > Checkout > enable ”Enable auto complete ticket orders”?

More screenshots:

Ashan,

The same on dev2:

https://dev2.myeventon.com/test-257/

Not possible to open events:

Hello,

Thank you for your messages!

I am going to escalate this ticket to development to help in here. Please allow us some time to address this, and we truly appreciate your patience. Thank you for being a valued EventON customer!

Additionally, if your site has any IP blocking or security restrictions in place, kindly disable them temporarily to facilitate our support process.

Hello,

Sorry for the delay.

Could you check this event:

https://defiancelibrary.org/wp-admin/post.php?post=17134&action=edit

Seems to be working correctly:

”kyzer.kaiden@forliion.com” was in waitlist first and then moved to RSVPed.

Could you add your own user and then change ”asd123@gmail.com” to NO?

Also could you let us know how do you change RSVP Status? From Single Event Page or Edit Event?

I have rolled back the tickets plugin on our main website and not the stage6 one this evening to the 2.5.7 and this is fully functioning so there definitely something in the way the 2.5.8 is interacting with woocommerce that is leaving orders as processing even though that are fulyly paid in stripe or paypal 

your username for myeventon.com is ”markus.tisch” 

temp new password: ”QXumWAN3nr1ERIsyCDhm^JrL”

Hi EventON Support team,

Thank you for confirming the limitations regarding the Event API and real-time access to ticket-related data.

Following up on our requirements, I would also like to bring to your attention two additional critical operational gaps that are currently hindering our ability to use your plugin for our ticketing system:

1. Attendee Data Collection: Currently, the system allows registration without mandating attendee details at checkout, making it voluntary. This is a major compliance issue for us, as we are unable to track essential information (such as parental consent or age verification for minors) at the time of purchase.
2. Hardcoded Strings & Localization: A significant portion of the public-facing ticketing system contains hardcoded text strings that cannot be translated. This prevents us from providing a fully localized experience for our users, which is essential for our multi-language environment.

To summarize the situation, we are struggling with:

• API gaps: No real-time access to ticket-related or attendee data.
• Operational gaps: Inability to mandate attendee info (critical for security/minors).
• Localization gaps: Hardcoded strings that break our multi-language setup.

Since we are currently managing a high volume of events with multiple time slots integrated with WooCommerce, we are forced to build a custom middleware (using WordPress custom REST endpoints) to bridge these gaps. I wanted to formally communicate these limitations, as they represent significant barriers to scaling EventON within professional ticketing workflows. We hope these points are considered for future development cycles.

Best regards,

Hi EventON Support team,

Thank you for confirming the limitations regarding the Event API and real-time access to ticket-related data.

Following up on our requirements, I would also like to bring to your attention two additional critical operational gaps that are currently hindering our ability to use your plugin for our ticketing system:

1. Attendee Data Collection: Currently, the system allows registration without mandating attendee details at checkout, making it voluntary. This is a major compliance issue for us, as we are unable to track essential information (such as parental consent or age verification for minors) at the time of purchase.
2. Hardcoded Strings & Localization: A significant portion of the public-facing ticketing system contains hardcoded text strings that cannot be translated. This prevents us from providing a fully localized experience for our users, which is essential for our multi-language environment.

To summarize the situation, we are struggling with:

• API gaps: No real-time access to ticket-related or attendee data.
• Operational gaps: Inability to mandate attendee info (critical for security/minors).
• Localization gaps: Hardcoded strings that break our multi-language setup.

Since we are currently managing a high volume of events with multiple time slots integrated with WooCommerce, we are forced to build a custom middleware (using WordPress custom REST endpoints) to bridge these gaps. I wanted to formally communicate these limitations, as they represent significant barriers to scaling EventON within professional ticketing workflows. We hope these points are considered for future development cycles.

Best regards,

I am sorry about that I have gone in a placed that in again now and tested it on another profile to make sure it has worked – not sure if it is something to do with the communication between eventon and woo commerce as all of a sudden all the orders are sat as processing and not moving to competed even the payment is all confirmed inside the order itself