|
Chris Stambaugh
|
February 10, 2014 at 5:39 pm
Hi,
Just got started and testing and ran into a couple of issues:
1. If I enable HTTPS on the Registration Checkout page, I get this error upon trying to pay: (Set up with PayPal Payments Pro)
An error has occurred:
Your form data could not be applied to any valid registrations.
SNGPGCHC-DSNGPGCHC-PROATTINF-1269
2. Without HTTPS the payment goes through fine to PayPal, but that is obviously not acceptable in production. How can we fix this?
3. Also, when I get to the payment screen, I have to re-enter the registration data in the billing information. Couldn’t this be copied over by default or at least be an option?
Thanks,
Paul
|
|
Josh
|
February 10, 2014 at 7:27 pm
Hi Paul,
There’s a workaround for the SSL issue. If you’re using the WordPress HTTPS plugin, you can check the box next to “Always use HTTPS while in the admin panel. This setting is identical to FORCE_SSL_ADMIN.” in the HTTPs settings. This will force the WordPress ajax handle to load as https (we’ll likely need to hook into the WP Https plugin and to make it load the ajax handler as https for checkout pages without setting the whole admin as https)
With the re-entering registration data into the payment forms, this is something that was found in testing and fixed earlier, but I’m afraid there were some recent changes made to the checkout scripts that affected the copy over feature.
The dev team will be looking into both this and the SSL issue. Thank you for reporting this.
|
|
Chris Stambaugh
|
February 11, 2014 at 10:27 am
Hi,
Okay, that works for HTTPS, one thing you forgot to mention is that I have to specifically call the page with the event short code via HTTPS. Once I did that it seems to work fine.
Any guesses on when the copy over feature will be updated again? Not the end of the world but it is annoying and not client friendly.
Paul
|
|
Josh
|
February 11, 2014 at 12:15 pm
Hi Paul,
I don’t know the exact cause of why the fields aren’t getting copied just yet, but the developer that’s going to work on this tells me it should be a simple fix. This was all working before but something in the registration process is getting disrupted now. We’ll post an update here when we have a solution.
|
