New to the community? Welcome! Please read our Community Rules and Guidelines
Join the live Q&A with our Community moderator team Wednesdays, 1-2pm PT (4-5pm ET) and Fridays, 4-5pm GMT. Learn more in Community Events
So this one specifically looks to have gone back to the legacy flow due to inconsistent parameters. The two variables have flags raised:
"country" - Value was blank
"night_phone_b" - Value was passed on its own, blank. This is 1 of three variables, if passing 1, the others need to be passed
But, previously you told me for you all works good?
Could you please be kind and point me a bit more precisely, how is it for some browsers/users ok and some not?
Thanks a lot!
So when I went through the checkout it worked fine, and I couldnt see any info in our logs related to fallbacks, but the specific example you shared above definitely did fallback.
Based on the variables that caused the fallback, its possible that they are being populated correctly or not being passed at all in the tests I carried out on the site, but in this case, the reason for the fallback to the legacy checkout was due to the incorrect variables. Given the type of variables (user input) it's more than likely that users are not setting the data correctly during the checkout.
Hi MTS_Ciaran, would you mind helping me on this as well? On http://ginzahub.com/ we have 4 paypal buttons and 4 more in the Japanese version, but they are all button codes directly copied from Paypal's button tool. I also don't see any variable fields in them except the usual 'cmd' and 'hosted_button_id"...
When clicking on the buttons, it seems that the subcribe button in the middle goes to the classic layout while the others go to the enhanced version...
Your help would be greatly appreciated...!
The subscription flow is not yet on the new checkout experience so classic will remain for everyone for the time being, its coming but not ready yet. The other buttons look good as you mentioned.
Thanks a lot for your help,
but I am quite confused, only JP got a warning, and then apparently all was ok, and now is not (only in Chrome it doesn't work).
With this new information you have now, could you please be kind and re-test all the stores? So I would know what and where to fix.
we were told by paypal that our existing site button isn't ok for jan 18th, but they didn't tell us which parts might be wrong. Can i send you a user somehow, to log in so you can see the button process? thanks
we have the paypal express gateway being made by a developer but we're worried we might miss the january deadline on this!