Posted: April 13, 2023 at 7:24 pm
Hello my payment page has stopped working on my site – I use an older version Version 3.1.37.14.P at the moment and my site says I need to update but need a valid support liscense – which I have – it is auto updating but why isn’t updating to the new version? Do I need to upgrade to EE4 since my support liscense is called “EE4 everything?” thx |
|
The event side seems to work I still get an email that someone tried to register for my event but the error I get when I click the payment gateway is https://checkout.globalgatewaye4.firstdata.com/collect_payment_data?ant=9966fcef75c05dd0e53969f9c7f2b925&merchant=WSP-VERNO-eSZ%26egC%26Ig&order=c2bd71690505ff10c9fd3e0a82f71843e10112e77c161ab9a5444583489b6191&t=1 |
|
Maybe the error is on the global gateway side since it is mainly the payment page not working. But not my license key was reset and I’m not sure where to start and getting things back in order. Maybe I should just make the move to EE4 all together |
|
Hi there, First, a quick explanation on EE3 and EE4. EE3 is now considered our ‘legacy’ product, it’s no longer receives updates other than for security and will likely be phased out over the next 12 months. EE4/EE5 is our latest produce and replaces EE3, but currently doesn’t not support event use case that EE3 is used for (we are getting close to support the majority of use cases, hence the 12 months). The license you have is for EE4, it does not provide updates for EE3 and we do not force an EE3 -> EE4 update which is why EE3 isn’t updating for you. So:
EE3 will only update to the latest version of EE3 (when you license has access) EE4 will only update to the latest version of EE4 from EE4, because they are very different systems we do NOT update EE3 to EE4 automatically through the one click updates.
‘Need to’, well, no… you ‘could’ continue to use EE3 and I can give you account access to EE3 os you get the latest version of it so you can see if that fixes you payment issue. However, knowing that EE3 will be phased out I would recommend you start looking into switching over. We usually recommend you test EE4 on a development copy of the site first. Do you have a staging/dev site?
This is what I see on that link: https://monosnap.com/file/75zMXHSM5EqRDB9cHFwuqPYW5nbZku I assume that’s not the error and its showing me that as its a checkout page that has now expired?
I can send you the latest version of EE3 to see if that gets your back up and running but I do still recommend looking into switching over to EE4, but again, we recommend testing that on a stagng/dev copy of the site first to confirm it works. |
|
Thanks very much! Appreciate all your replies- Ok let’s do this if you think its ok….if you can send me the latest EE3 that will hopefully fix my problem for today. But then I will continue to set up EE4 since I know now that the next 12 months I will have to. WIll you email me the EE3 update file or how do I get it? Will my support liscense reactivate though also or maybe I need a new EE3 liscence code? thank you so much Can I migrate ee3 info into EE4? |
|
This reply has been marked as private. | |
Got the EE3 installed thanks…… any progress with the EE3 license code though? Updating EE3 didn’t fix my payment page …I’ll try to work with the First Data global gateway to see if the error is on their side …thanks |
|
I’ve sent it over to sales but likely won’t hear anything until Monday. What is it it about the EE3 license you are concerned about? The license key has no effect on Event Espresso itself, its used for support and updates only so if it’s not working now it won’t with an EE3 license.
Can you add a screenshot of the payment error? https://eventespresso.com/wiki/troubleshooting-checklist/#screenshots |
|
Here is the payment error |
|
The email I get after it fails shows this error –something with a form maybe value in the integration side? How could I address this The following error was found: x_fp_hash : Could not validate the integrity of the payment from the transaction key, x_fp_hash, x_fp_sequence, x_fp_timestamp, x_amount, and (optionally) x_currency_code and x_fee_amount values of the request. |
|
I turned the relay response link on and mapped it on the first data side to the EE3 but still no luck hmmmm maybe getting closer |
|
I changed the HMAC Calculation |
|
Are still running into an issue after this change or is it working now? The integration within EE3 uses the MD5 hash so it will need to be HMAC-MD5. |
|
The support post ‘how to install Event Espresso new version 3.1.37.18.P’ 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.