Support

Home Forums Pre-Releases TIcket for Unknown and reg form errors

TIcket for Unknown and reg form errors

Posted: July 21, 2015 at 7:03 pm


Warhol Revisited

July 21, 2015 at 7:03 pm

Hi,

We just upgraded to 4.8pr, had migration issues due to memory, fixed the memory issue, then proceeded with the migration.

Everything seemed to work fine, but when trying to purcahse a ticket, on the registration form, we are getting “ticket for unknown” displayed by the ticket type on the page before entering personal info, and the page after.

Then when trying to proceed with registration after selecting payment type (stripe gateway), the following error appears instead of the strip popup:

To further compound the problem, our pre-update database backup is corrupt, stopping us from being able to rollback.

Is this fixable? So far we’ve tried deactivating and reactivating the plugins, re-saving events, and various settings, to no avail.

Here’s an example event: http://warholrevisited.com/events/andy-warhol-revisited-july-28th

Also, our account currently shows as EE3 support license, due to it being temporarily switched from 4 to 3 in relation to this ticket: http://eventespresso.com/topic/need-to-restrict-card-types-with-stripe-gateway/

Could this please be switched back to 4?


Josh

  • Support Staff

July 22, 2015 at 7:21 am

Hi there,

I checked your account and it turns out you have access to Event Espresso 4.

Please, do not run beta software from the pre-release channel with the expectation that there will not be any bugs. We’re still working on Event Espresso 4.8, it is not finished yet. You can get the very latest version of 4.8 beta from github and it has fixes for the bugs you reported here.

https://github.com/eventespresso/event-espresso-core/tree/BETA-4.8-CORE

Once 4.8 is officially released, please install the official release version by removing the beta and installing the .p version.


Warhol Revisited

July 22, 2015 at 12:27 pm

Hi Josh,

Thanks for getting back to us, and thanks for the link. We didn’t expect there not to be bugs, we were just asking for assistance with the one we had as we were in the unfortunate position of not being able to roll back.

The main version on github did solve the issue, but caused another bug. Should we report this somewhere?

THe bug is when in live mode, after payment is made, it gives the messages, payment accepted, and please wait while we process the registration, then instead of going to the thank you page, it pops up another message saying “this registration step could not be completed. Please refresh the page and try again”.

Refreshing the page takes you to the thank you page.

This only happens in live mode when a payment is processed. In debug mode with stripe in test mode, it processes fine and goes to the thank you page after dummy payment is made.


Josh

  • Support Staff

July 22, 2015 at 12:43 pm

Can you let me know which version numbers of the core plugin (EE4), Promotions add-on, and Stripe add-on you currently have activated?


Warhol Revisited

July 22, 2015 at 1:04 pm

Hi Josh,

Core – Version 4.8.1.beta.000
Promotions – Version 1.0.0.beta.065 – currently deactivated
Stripe – Version 1.0.7.p

Also:

Social Sharing – Version 1.0.p
Ticketing – Version 1.0.3.p
Barcode scanner – Version 1.0.4.p

Let me know if you want me to try deactivating any of them.


Josh

  • Support Staff

July 22, 2015 at 1:52 pm

When your Stripe account is in live mode, with Debug turned off, which of the two pairs of keys are set in EE > Payment Methods > Stripe? Are they the Test Keys or the Live Keys?


Warhol Revisited

July 22, 2015 at 2:25 pm

Live keys are set when not in debug mode.

The payment processes, and the ticket email gets sent, payment is confirmed in our stripe dashboard, it’s just the screen that doesn’t advance to the thank you page without the refresh.

The tickets are sent before you hit refresh and get the thank you page, so it seems everything is working right in the background, it’s just not taking the user to the thank you page without the manual refresh.


Josh

  • Support Staff

July 22, 2015 at 2:55 pm

Is there a reason why you’re running 4.8 beta on a live production site instead of 4.7 stable? Can you run Event Espresso 4.7 instead?

I’ll see if I can find out what’s going on with the Stripe gateway + 4.8 beta, but since the dev team is pushing untested code throughout the day to the 4.8 beta branch, it may take some time to iron this out.


Warhol Revisited

July 22, 2015 at 2:59 pm

Hi Josh,

We installed the beta to use the promotions beta, as trying to activate it asked for a higher version than 4.7 when we tried to activate it. We intended to test it with 4.8, and back out to 4.7 if there were issues. However, when we tried to reinstall the 4.7 version database backup, the backup was corrupt and couldn’t be installed, leaving us stuck at 4.8.

We’ve since made several backups for each stage we’ve changed, and ensured that they work, so we don’t end up in thee same pickle again.


Warhol Revisited

July 22, 2015 at 3:00 pm

Is it possible to roll back to 4.7 after updating to 4.8 and running the migration?


Josh

  • Support Staff

July 22, 2015 at 3:25 pm

I’m not sure if changing to 4.7 will fix this for you, and if you try to revert to 4.7, the line items will not work as expected due to the changes to the database that were made in 4.8 to accommodate promtional discounts. The other thing is, I have 4.8 loaded up with Stripe and live credit card payments go through without any errors. The issue you’re seeing on your site may be unique to your set up.

You may be able to find out what’s specifically causing the “this registration step could not be completed, or at least something that points us in the right direction by going to the Event Espresso > Payment Methods > Logs tab and check the logs at the times the error was thrown.

If your server logs errors to an error log file, that’s another place to check as well.


Warhol Revisited

July 22, 2015 at 4:29 pm

Hi Josh,

There are no errors logged in the logs tab, only the purchases relating to the transactions in question, and the server log doesn’t have anything for that site either (server log is working, there are other errors on other sites).

I did narrow it down though:

I created a test ticket, and ran some tests:

test ticket – works fine

test ticket with percentage surcharge – works fine

test ticket with dollar surcharge – causes the error (payment is still processed and tickets get sent, refresh takes you to the thank you page)

test ticket with tax – causes the error (payment is still processed and tickets get sent, refresh takes you to the thank you page)

test ticket with tax and dollar surcharge – causes the error (payment is still processed and tickets get sent, refresh takes you to the thank you page)

Our live tickets use a dollar surcharge and tax. I could get around the surcharge by working out the percentage surcharge for the same amount, but I can’t get around the tx, we have to charge it.


Warhol Revisited

July 22, 2015 at 10:43 pm

We found the problem. We had this in our theme’s function.php to only show the price without tax and processing fee (dollar surcharge) in the ticket price table.

When we removed this, it all works.

Is there any way to replace this so we can still display the price without tax nad surcharges?

// display the base price of the ticket in the ticket selector without Price Modifiers.

add_filter( ‘FHEE__ticket_selector_chart_template__ticket_price’, ‘change_ee_ticket_selector_base_price_display’, 10, 2 );

function change_ee_ticket_selector_base_price_display( $ticket_price, $ticket ) {

$x = $ticket->base_price();

$y = $x->get(‘PRC_amount’);

return $y;
}


Josh

  • Support Staff

July 23, 2015 at 8:54 pm

We’ll have to look into why using the filter hook in the ticket selector is even affecting the Stripe Checkout after payment, specially when the attendee record is updated. It really shouldn’t!

In the meantime, we’ve pushed an update to the EE4 Stripe integration add-on (1.0.8) This fix just makes sure that the Checkout Page form submission doesn’t happen until Stripe is done everything it needs to do.


Josh

  • Support Staff

July 23, 2015 at 9:19 pm

One other thing: You will likely need to clear your browser’s cache before you test the update because the update includes updates to the add-on’s JavaScript.


Warhol Revisited

July 23, 2015 at 10:01 pm

Hi Josh,

Thank you for all your time and help.

We just installed the strip plugin update, cleared the cache, and firewall cache, and gave it a test. All seemed to work fine. Payment processed, and went straight through to the thank you page.

Yeah, the hook causing the error was a surprise. I was just going through everything like deactivating plugins, and changing everything back to as vanilla as possible to try and identify the cause, and testing after each step. When I removed that hook, it worked. We put everything else back except for that, and it still works fine, so it definitely seems to be what was causing the issue.


Josh

  • Support Staff

July 24, 2015 at 9:37 am

We will look into why using the filter hook in the ticket selector had an effect on the Stripe Checkout after payment.

The support post ‘TIcket for Unknown and reg form errors’ is closed to new replies.

Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.

Beta test upcoming software through the pre-release channel. Learn more about the pre-release channel.

Status: closed

Updated by  Josh 5 years ago ago

Topic Tags

Notifications

This topic is: not resolved
Do NOT follow this link or you will be banned from the site!