|
Michael
|
July 14, 2015 at 9:35 am
Hi. As the subject says, after selecting tickets for an event, iphone users get directed to registration questions, but encounter “no valid registrations” message, and can’t proceed. This only happens on iphone safari, not any other platform/browser that I’m aware of.
Can I share my url privately?
Thanks
|
|
Michael
|
July 14, 2015 at 9:42 am
event queue empty
|
|
Josh
|
July 14, 2015 at 10:59 am
Hi Michael,
Do you have any security plugins activated? If so, can you let us know the name of them?
|
|
Michael
|
July 14, 2015 at 11:06 am
We’re on WPEngine, no other security beyond that.
|
|
Josh
|
July 14, 2015 at 11:33 am
Hi Michael,
I checked your site and it looks like there’s a countdown timer set to 3 minutes. When the countdown timer expires, does it wipe the session? If so, someone using an iphone may not be able to fill out all the required fields within the 3 minutes.
If they still get the error while submitting the form within 3 minutes, you can check with them to see if they’re blocking cookies in their Safari settings.
|
|
Michael
|
July 14, 2015 at 12:25 pm
Josh, the error occurs even with the timer disabled. Just on Iphone Safari, not OSX safari.
|
|
Josh
|
July 14, 2015 at 2:12 pm
Hi Michael,
Can you check with them to see if they’re blocking cookies in their iOS Safari settings? The platform isn’t relevant if they’re blocking cookies, it’s not going to work either way.
|
|
Michael
|
July 14, 2015 at 2:53 pm
Josh, I compared two iphones on ios 8.0.4 just now. Interestingly, registration fails on the mobile network. When I connect to wi-fi, both devices can proceed.
I don’t know where to go next.
|
|
Josh
|
July 14, 2015 at 3:37 pm
When you’re connected to the mobile network, can you try logging into the website via wp-login.php?
|
|
Michael
|
July 15, 2015 at 11:14 am
Hi, I started talking to WPEngine about this, but nothing so far.
The user can login via wp-login on at&t/iphone5/ios804/safari. But can’t register to events. So I’m thinking about the ssl cert that protects registration, which is a different cert from the admin page. The registration page doesn’t receive data from the event page. This might be just at&t. It doesn’t happen on sprint or tmobile.
WPEngine might need to fix their DNS redirection? Or?
|
|
Josh
|
July 15, 2015 at 12:18 pm
Why do you have two different certs for the front end and WP admin?
With the phone that’s on the AT&T network, does the same issue happen if they connect to the site using wifi?
|
|
Michael
|
July 15, 2015 at 12:26 pm
I was assuming they are different certs, because we had a secure admin area before we added the cert that we purchased additionally for EE. But I could be wrong.
No, on wi-fi, that same iphone has no problem.
|
|
Josh
|
July 15, 2015 at 12:54 pm
I don’t have an account with At&t to verify whether this would help or not, but you can try opting out of At&t’s data collection browser tracking by following these steps for that account:
Here’s how to opt out of the tracking:
Go to http://att.com/cmpchoice
Login to your account
Opt-out and logout of your account.
|
|
Michael
|
July 15, 2015 at 1:57 pm
That’s a good idea, but I think even if it would work, we could not ask our customers to do that.
Hopefully WPE can help with this. I posted here but since then it’s looking like this doesn’t have anything to do with EE.
FYI–they recently moved us to a new server, new IP addy, in order to provide php5.5, and they accomplished this via redirection on their end. They didn’t ask us to make any DNS changes with our provider. I’m guessing that they didn’t also follow through with our SSL cert, but I don’t know about these things. I’m wondering about how at&t’s dns handles the kind of redirection they are doing, vs other network dns.
|
|
Josh
|
July 15, 2015 at 2:17 pm
I didn’t say to ask your customers to do that, but it will help to narrow down the cause of the issue instead of just guessing.
|
|
Michael
|
July 16, 2015 at 8:56 am
Josh,
Thanks again for your help. WPE suggested forcing all /events/ pages to https, to ensure that the cookie can pass to the buying page.
This solved the issue, but I don’t understand why it was specific to at&t. I also don’t know if this was an issue on our old server; it could have just flown under the radar the whole time.
Maybe it would make sense to recommend that EE users put /events/ on ssl, along with registration, transactions, etc.
|
|
Josh
|
July 16, 2015 at 9:43 am
We do recommend putting /events/ on SSL, along with any page that has the ticket selector shortcode if using SSL on checkout.
|
|
Michael
|
July 16, 2015 at 10:06 am
I want to suggest adding that recommendation to this page:
https://eventespresso.com/wiki/espresso-sslhttps/
|
|
Josh
|
July 16, 2015 at 12:06 pm
We already do. We have specific instructions on that page that say any page that has a ticket selector should also be secured. Please note that since you’re on WPEngine, the instructions are a bit different in that you tell them which pages you need to serve as https (and not use the WP HTTPs plugin). This is also noted before Step 1.
|
