Posted: September 11, 2023 at 6:26 pm
Can you please advise on what to do to fix this error? It was running fine last week. Now no one can register. Please help |
|
https://mnvc.org/ |
|
Plus registration is not rendering correctly on mobile |
|
I did try to register and was able to proceed till i need to checkout the event. Can you give me the link of registration where you experience this problem? Please send me recordings too. you can use loom to do it. thanks |
|
This reply has been marked as private. | |
That was with a real credit card for a dummy event for $1. |
|
This reply has been marked as private. | |
This reply has been marked as private. | |
September 12, 2023 at 12:30 am Hi there, “This registration step could not be completed…” errors are generally thrown when there is a fatal error on the request and there isn’t another error to display. Does the transaction show as paid in Event Espresso? Go to Event Espresso -> Messages -> Settings. What is the ‘generate and send messages’ option set to currently? |
|
User receveid a Failed Payment Message – Your payment FAILED for the following transaction and ticket purchases: Payment Details: Payment Status: Abandoned It is showing in EE as Abandoned. |
|
Generate and send messages is set to send on a separate request |
|
September 12, 2023 at 11:29 am Hmmm, I think I need to check the payment logs to see what is going on, can I take a look in the admin? If so send temp login details over using this form: |
|
September 12, 2023 at 12:16 pm Thank you! I will set you up a temp login |
|
This reply has been marked as private. | |
Ok, the last time I saw this it was an issue with the Stripe connection. When did you connect Stripe to the site? Go to Event Espresso -> Payment methods -> Stripe. Click the disconnect button and wait a few seconds for that to process. Refresh the page to be sure. Then go back to the Stripe payment and reconnect it to your Stripe account, following the onscreen instructions to connect. |
|
This reply has been marked as private. | |
This reply has been marked as private. | |
When you disconnect with Stripe, that’s what happens, you clear the connection between your site and your Stripe account. So yes you need to reconnect to Stripe using the Stripe account you want to connect to the site. Or ask the user managing the account to do it, if they are already logged into Stripe on their browser and then click the connect button it will use their current session.
I can’t give you better instructions than clicking the connect button and following the on screen instructions, those are from Stripe themselves and the steps you need to take depends on what details they want based on your account. |
|
This reply has been marked as private. | |
Yes, I logged into the site and checked the Stripe checkout process. The error being thrown is stating there is no Payment/Intent ID and that happens when the connection between the site and Stripe is invalid, which is why I suggested the above. I can test reconnecting Stripe with my test account in the meantime (I’ll do it now) but either way you’ll need those Stripe credentials to reconnect the correct afterwards. |
|
This reply has been marked as private. | |
Thank you! I’ll contact our server. If not, do you think if we downgraading PHP to 7.4 it would still work? OR eventually will we be required to upgrade to PHP 8 anyway? |
|
If it worked previously then it was likely enable already within the version of PHP7.4 installed on your server but isn’t within the version of PHP8 they have installed. PHP7 is now EOL so ultimately everyone ‘should’ be updating to PHP8 ‘soon’, how soon that actually is I can’t tell you 🙂 |
|
This reply has been marked as private. | |
This reply has been marked as private. | |
Poor excuse tbh, I have server shared hosting packages and have the option to enable/disable functions, including the above. But… that’s their setup so up to them.
EE itself works fine with PHP7.4, that’s our minimum required version.
Connect Strie in debug/sandbox mode. Event Espresso -> Payment methods -> Stripe If you have the account connected you need to disconnect again. Then set “Sandbox Mode On? (AKA: debug mode)” to Yes and save the settings. Then reconnect again, now your account is connected in test mode. When you use Stripe in debug mode the checkout page will show you test card numbers you can use. When finished, disconnect again, set sandbox mode to No, save, reconnect. |
|
This reply has been marked as private. | |
This reply has been marked as private. | |
September 13, 2023 at 10:26 am
Thats not how this all works. You NEED a Stripe account connected in either live mode or test mode (sandbox mode tells your Stripe account to connect in test mode). You can’t test payments WITHOUT a Stripe account connected. If you want to test this separately you can create your own dev/test account with Stripe: It takes minutes to set up and you only need the test account. Then you can connect to your own account in sandbox mode to confirm.
Thats expected if there is no Stripe account connected.
Again, that’s not how this works. It could event work with my/your test account connect and still fail once they reconnect. I can’t give you a guarantee that it will work as its based on your server and your account.
The issue is from your server’s config, we can’t stop them from changing things on the server and causing issues. Have you reverted to PHP7.4? |
|
This reply has been marked as private. | |
This reply has been marked as private. | |
September 13, 2023 at 10:50 am Awesome.
PHP7 is end of life and has been for almost a year so I can’t say how long your host will support it. I’ll create a ticket to investigate if we can use a version of the Stripe SDK that doesn’t use php_uname() which will prevent the current fatal error you are getting, but there’s also no guarantee that your host hasn’t disabled some other function required elsewhere within the SDK which then throws a fatal after that so then I can’t guarantee that will work. |
|
This reply has been marked as private. | |
September 13, 2023 at 11:05 am I run PHP7.4, PHP8.0.XX, PHP8.1.XX and PHP8.2.XX across multiple different servers and hosting platforms including shared hosting (to test against what people will be using with EE) and so far I’ve not run into this issue. The problem here is from the host blocking the above function on the version of PHP installed on their servers with no option to enable them again. We can work around that within our code but the Stripe SDK/library isn’t one we control, its one we use, so it’s a slightly more tricky as technically its not our code. But the same issue can come up with pretty much any function a host decides to block, if PHP includes X function and then a host blocks that function, anywhere trying to use it throws a fatal error. So yes, other folks could run into this, if their host decides to block that PHP core function. |
|
This reply has been marked as private. | |
Once you click pay you are waiting for the request to be sent, processed and returned from Stripe, that should be fairly quick. Unless its the processing taking place after that, when exactly is it slow? |
|
The support post ‘This registration step could not be completed. Please refresh the page’ 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.