Support

Home Forums Event Espresso Premium EE With Stripe Checkout No Redirect, Proceed Button Grayed Out After Payment Snt

EE With Stripe Checkout No Redirect, Proceed Button Grayed Out After Payment Snt

Posted: November 11, 2015 at 2:53 pm


Jean Sconyers

November 11, 2015 at 2:53 pm

I’m having an issue referenced in a different post (link below) but can’t get it resolved. We are using stripe test keys and test cards. When I try a test registration I get a message about redirecting or “click the “proceed to finalize registration” button. After those two messages disappear there is no redirect and the button remains grayed out. There is no console error.

In the prior thread (link below) there is reference to adding some js (SPCO.disable_submit_buttons()) but no specifics on where that goes. It also mentions that an update to the plugin was made to fix the issue. I am running EE 4.8.20.p and stripe gateway 1.0.11.p. Any ideas?

ref post:
https://eventespresso.com/topic/stripe-error-when-click-finalise-registration-before-pay-now/


Lorenzo Orlando Caum

  • Support Staff

November 11, 2015 at 3:19 pm

Hi Jean,

No coding changes should be necessary. Could you provide a link to an event so we can take a look?

Also, are there any emails that go out even though the page does not move automatically to the thank you page for Event Espresso.


Lorenzo


Jean Sconyers

November 11, 2015 at 3:30 pm

Here’s the link:

http://epc2.lelander.com/register-hidden/

I am getting event confirmation emails. Some of the recent test registrations say complete and others say pending payment.


Jean Sconyers

November 11, 2015 at 3:36 pm

Update. Our dev just switched us over to another domain so you won’t be able to test until we get that setup. Will post again with new link when ready.


Jean Sconyers

November 11, 2015 at 3:37 pm

New link:

http://epcconference.org/register-hidden/


Jean Sconyers

November 11, 2015 at 3:44 pm

I did notice that after a few minutes of doing nothing I start to get the gear, then after about 3 minutes I get a “failed to complete registration, please try again” error. It shows complete and approved on the backend.


Jean Sconyers

November 11, 2015 at 3:50 pm

Also worth noting that we don’t have a cert installed yet so testing over http only.


Josh

  • Support Staff

November 11, 2015 at 6:45 pm

Your site might be running low on memory, which will lead to the error you’re seeing. Can someone from your dev team set the WP Memory limit to a higher limit?

in wp-config.php, they’d set it with something like this:

define( 'WP_MEMORY_LIMIT', '128M' );


Jean Sconyers

November 12, 2015 at 8:56 am

Thanks Josh, I’m getting a new error now after upping the memory. After the first two messages about “payment accepted” and “Don’t refresh” disappear there is a good 4 minute lag while the gear spins then it disappears and the “proceed to finish Registration” button becomes clickable. After clicking that I get the error “the following errors have occurred: an invalid registration was received. Develop primary registration for this transaction could not be found.”. Here’s the link: http://epcconference.org/register-hidden/


Jean Sconyers

November 12, 2015 at 8:57 am

That last part was bad dictation translation. It should read “A valid Primary Registration for this Transaction could not be found”.


Jean Sconyers

November 12, 2015 at 9:11 am

Also, we do not have any caching on.


Jean Sconyers

November 12, 2015 at 9:16 am

I tried a new test event and still same result. I’m noticing that the entire server is locking up while the gear is spinning. I can’t navigate in the backend or even bring up the site.


Lorenzo Orlando Caum

  • Support Staff

November 12, 2015 at 9:36 am

Hi Jean,

The payment process should take just a few seconds.

Could you temporarily turn on WordPress debugging by adding the macro in the following link to your wp-config.php file?

https://gist.github.com/lorenzocaum/848801a1173be464fbe7#file-gistfile1-php

The wp-config.php file can be found in the WordPress root which is where the wp-admin, wp-content, and other files and folders for WordPress resides.

Then please try to trigger the a payment and allow it to run for a few minutes. Then please browse to this location using your SFTP or FTP client (e.g. FileZilla, Cyberduck):

/wp-content/debug.log

You may see an error recorded within the file. Please copy and paste that here in a reply.

Then go ahead and deactivate WordPress debugging by removing the macro that was recently added or setting it to false and saving changes:

https://gist.github.com/lorenzocaum/848801a1173be464fbe7#gistcomment-1239850


Lorenzo


Jean Sconyers

November 12, 2015 at 9:37 am

The script admin-ajax.php runs for 1min, the loads again (gear comes up), same script runs for another 2min then aborts. When I inspect the html of that script I see the thank you page.


Lorenzo Orlando Caum

  • Support Staff

November 12, 2015 at 9:43 am

Hi, could you try my earlier suggestion on enabling WP debugging?

https://eventespresso.com/topic/ee-with-stripe-checkout-no-redirect-proceed-button-grayed-out-after-payment-snt/#post-180264

Also, have you already tested with only Event Espresso 4 running and other plugins temporarily disabled?


Lorenzo


Jean Sconyers

November 12, 2015 at 9:43 am

[12-Nov-2015 16:38:34 UTC] PHP Notice: The called constructor method for WP_Widget is deprecated since version 4.3.0! Use

__construct()

instead. in /var/www/html/wp-includes/functions.php on line 3457
[12-Nov-2015 16:38:34 UTC] PHP Notice: The called constructor method for WP_Widget is deprecated since version 4.3.0! Use

__construct()

instead. in /var/www/html/wp-includes/functions.php on line 3457
[12-Nov-2015 16:38:34 UTC] PHP Notice: The called constructor method for WP_Widget is deprecated since version 4.3.0! Use

__construct()

instead. in /var/www/html/wp-includes/functions.php on line 3457
[12-Nov-2015 16:38:34 UTC] PHP Notice: The called constructor method for WP_Widget is deprecated since version 4.3.0! Use

__construct()

instead. in /var/www/html/wp-includes/functions.php on line 3457
[12-Nov-2015 16:38:34 UTC] PHP Notice: The called constructor method for WP_Widget is deprecated since version 4.3.0! Use

__construct()

instead. in /var/www/html/wp-includes/functions.php on line 3457
[12-Nov-2015 16:38:34 UTC] PHP Notice: The called constructor method for WP_Widget is deprecated since version 4.3.0! Use

__construct()

instead. in /var/www/html/wp-includes/functions.php on line 3457
[12-Nov-2015 16:38:34 UTC] PHP Notice: The called constructor method for WP_Widget is deprecated since version 4.3.0! Use

__construct()

instead. in /var/www/html/wp-includes/functions.php on line 3457
[12-Nov-2015 16:38:34 UTC] PHP Notice: The called constructor method for WP_Widget is deprecated since version 4.3.0! Use

__construct()

instead. in /var/www/html/wp-includes/functions.php on line 3457
[12-Nov-2015 16:38:34 UTC] PHP Notice: The called constructor method for WP_Widget is deprecated since version 4.3.0! Use

__construct()

instead. in /var/www/html/wp-includes/functions.php on line 3457
[12-Nov-2015 16:38:34 UTC] PHP Notice: The called constructor method for WP_Widget is deprecated since version 4.3.0! Use

__construct()

instead. in /var/www/html/wp-includes/functions.php on line 3457
[12-Nov-2015 16:38:34 UTC] PHP Notice: The called constructor method for WP_Widget is deprecated since version 4.3.0! Use

__construct()

instead. in /var/www/html/wp-includes/functions.php on line 3457
[12-Nov-2015 16:38:34 UTC] PHP Notice: The called constructor method for WP_Widget is deprecated since version 4.3.0! Use

__construct()

instead. in /var/www/html/wp-includes/functions.php on line 3457
[12-Nov-2015 16:38:34 UTC] PHP Notice: The called constructor method for WP_Widget is deprecated since version 4.3.0! Use

__construct()

instead. in /var/www/html/wp-includes/functions.php on line 3457
[12-Nov-2015 16:38:34 UTC] PHP Notice: The called constructor method for WP_Widget is deprecated since version 4.3.0! Use

__construct()

instead. in /var/www/html/wp-includes/functions.php on line 3457
[12-Nov-2015 16:38:34 UTC] PHP Notice: The called constructor method for WP_Widget is deprecated since version 4.3.0! Use

__construct()

instead. in /var/www/html/wp-includes/functions.php on line 3457
[12-Nov-2015 16:38:34 UTC] PHP Notice: The called constructor method for WP_Widget is deprecated since version 4.3.0! Use

__construct()

instead. in /var/www/html/wp-includes/functions.php on line 3457
[12-Nov-2015 16:38:34 UTC] PHP Notice: The called constructor method for WP_Widget is deprecated since version 4.3.0! Use

__construct()

instead. in /var/www/html/wp-includes/functions.php on line 3457
[12-Nov-2015 16:38:34 UTC] PHP Notice: The called constructor method for WP_Widget is deprecated since version 4.3.0! Use

__construct()

instead. in /var/www/html/wp-includes/functions.php on line 3457
[12-Nov-2015 16:38:34 UTC] PHP Notice: The called constructor method for WP_Widget is deprecated since version 4.3.0! Use

__construct()

instead. in /var/www/html/wp-includes/functions.php on line 3457
[12-Nov-2015 16:38:34 UTC] PHP Notice: The called constructor method for WP_Widget is deprecated since version 4.3.0! Use

__construct()

instead. in /var/www/html/wp-includes/functions.php on line 3457
[12-Nov-2015 16:38:34 UTC] PHP Warning: Cannot modify header information – headers already sent by (output started at /var/www/html/wp-includes/functions.php:3457) in /var/www/html/wp-content/plugins/event-espresso-core-reg/core/EE_Front_Controller.core.php on line 112
[12-Nov-2015 16:38:34 UTC] PHP Warning: session_start(): Cannot send session cookie – headers already sent by (output started at /var/www/html/wp-includes/functions.php:3457) in /var/www/html/wp-content/plugins/event-espresso-core-reg/core/EE_Session.core.php on line 398
[12-Nov-2015 16:38:34 UTC] PHP Warning: session_start(): Cannot send session cache limiter – headers already sent (output started at /var/www/html/wp-includes/functions.php:3457) in /var/www/html/wp-content/plugins/event-espresso-core-reg/core/EE_Session.core.php on line 398
[12-Nov-2015 16:38:34 UTC] PHP Notice: The called constructor method for WP_Widget is deprecated since version 4.3.0! Use

__construct()

instead. in /var/www/html/wp-includes/functions.php on line 3457
[12-Nov-2015 16:38:34 UTC] PHP Notice: The called constructor method for WP_Widget is deprecated since version 4.3.0! Use

__construct()

instead. in /var/www/html/wp-includes/functions.php on line 3457
[12-Nov-2015 16:38:34 UTC] PHP Notice: The called constructor method for WP_Widget is deprecated since version 4.3.0! Use

__construct()

instead. in /var/www/html/wp-includes/functions.php on line 3457
[12-Nov-2015 16:38:34 UTC] PHP Notice: The called constructor method for WP_Widget is deprecated since version 4.3.0! Use

__construct()

instead. in /var/www/html/wp-includes/functions.php on line 3457
[12-Nov-2015 16:38:34 UTC] PHP Notice: The called constructor method for WP_Widget is deprecated since version 4.3.0! Use

__construct()

instead. in /var/www/html/wp-includes/functions.php on line 3457
[12-Nov-2015 16:38:34 UTC] PHP Notice: The called constructor method for WP_Widget is deprecated since version 4.3.0! Use

__construct()

instead. in /var/www/html/wp-includes/functions.php on line 3457
[12-Nov-2015 16:38:34 UTC] PHP Notice: The called constructor method for WP_Widget is deprecated since version 4.3.0! Use

__construct()

instead. in /var/www/html/wp-includes/functions.php on line 3457
[12-Nov-2015 16:38:34 UTC] PHP Notice: The called constructor method for WP_Widget is deprecated since version 4.3.0! Use

__construct()

instead. in /var/www/html/wp-includes/functions.php on line 3457
[12-Nov-2015 16:38:34 UTC] PHP Notice: The called constructor method for WP_Widget is deprecated since version 4.3.0! Use

__construct()

instead. in /var/www/html/wp-includes/functions.php on line 3457
[12-Nov-2015 16:38:34 UTC] PHP Notice: The called constructor method for WP_Widget is deprecated since version 4.3.0! Use

__construct()

instead. in /var/www/html/wp-includes/functions.php on line 3457
[12-Nov-2015 16:38:34 UTC] PHP Notice: The called constructor method for WP_Widget is deprecated since version 4.3.0! Use

__construct()

instead. in /var/www/html/wp-includes/functions.php on line 3457
[12-Nov-2015 16:38:34 UTC] PHP Notice: The called constructor method for WP_Widget is deprecated since version 4.3.0! Use

__construct()

instead. in /var/www/html/wp-includes/functions.php on line 3457
[12-Nov-2015 16:38:34 UTC] PHP Notice: The called constructor method for WP_Widget is deprecated since version 4.3.0! Use

__construct()

instead. in /var/www/html/wp-includes/functions.php on line 3457
[12-Nov-2015 16:38:34 UTC] PHP Notice: The called constructor method for WP_Widget is deprecated since version 4.3.0! Use

__construct()

instead. in /var/www/html/wp-includes/functions.php on line 3457
[12-Nov-2015 16:38:34 UTC] PHP Notice: The called constructor method for WP_Widget is deprecated since version 4.3.0! Use

__construct()

instead. in /var/www/html/wp-includes/functions.php on line 3457
[12-Nov-2015 16:38:34 UTC] PHP Notice: The called constructor method for WP_Widget is deprecated since version 4.3.0! Use

__construct()

instead. in /var/www/html/wp-includes/functions.php on line 3457
[12-Nov-2015 16:38:34 UTC] PHP Notice: The called constructor method for WP_Widget is deprecated since version 4.3.0! Use

__construct()

instead. in /var/www/html/wp-includes/functions.php on line 3457
[12-Nov-2015 16:38:34 UTC] PHP Notice: The called constructor method for WP_Widget is deprecated since version 4.3.0! Use

__construct()

instead. in /var/www/html/wp-includes/functions.php on line 3457
[12-Nov-2015 16:38:34 UTC] PHP Notice: The called constructor method for WP_Widget is deprecated since version 4.3.0! Use

__construct()

instead. in /var/www/html/wp-includes/functions.php on line 3457
[12-Nov-2015 16:38:34 UTC] PHP Notice: The called constructor method for WP_Widget is deprecated since version 4.3.0! Use

__construct()

instead. in /var/www/html/wp-includes/functions.php on line 3457
[12-Nov-2015 16:38:34 UTC] PHP Warning: Cannot modify header information – headers already sent by (output started at /var/www/html/wp-includes/functions.php:3457) in /var/www/html/wp-content/plugins/event-espresso-core-reg/core/EE_Front_Controller.core.php on line 112
[12-Nov-2015 16:38:34 UTC] PHP Warning: session_start(): Cannot send session cookie – headers already sent by (output started at /var/www/html/wp-includes/functions.php:3457) in /var/www/html/wp-content/plugins/event-espresso-core-reg/core/EE_Session.core.php on line 398
[12-Nov-2015 16:38:34 UTC] PHP Warning: session_start(): Cannot send session cache limiter – headers already sent (output started at /var/www/html/wp-includes/functions.php:3457) in /var/www/html/wp-content/plugins/event-espresso-core-reg/core/EE_Session.core.php on line 398


Josh

  • Support Staff

November 12, 2015 at 9:46 am

You can turn off debugging now. The errors you saw were from an out of date theme that’s using deprecated methods to register WordPress widgets. I hesitate to say that’s causing the issue at this point.

Can you try turning off all messages in Event Espresso > Messages > Settings and check to see if that speeds up the final part of the checkout?


Jean Sconyers

November 12, 2015 at 9:52 am

I disabled the one plugin we had (regn thumbs) other than ee and stripe. Still stalling.


Jean Sconyers

November 12, 2015 at 9:55 am

Works great with all messages off! So SMTP issue?


Jean Sconyers

November 12, 2015 at 10:28 am

Looks like PHP mail function is hanging so looking into that. Seems like a server issue that’s not related to EE or stripe so we should be able to take it from here. Thanks for the help!


Tony

  • Support Staff

November 12, 2015 at 10:45 am

Hi Jean,

Another suggestion to test this is to try a transnational email service such as Mandill or PostMark to send your emails and see if they work.

We have a guide on setting this up here:

https://eventespresso.com/wiki/postmark-app-mandrill-transactional-email-handling-services/

However based on the above it does sound like an issue with mailserver you are currently using.

The support post ‘EE With Stripe Checkout No Redirect, Proceed Button Grayed Out After Payment Snt’ 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.

Event Espresso