mocomizuki
Forum Replies Created
-
The AdBlock setting remains the default.
I turned on AdBlock again and for some reason it showed up fine.
I got it!
It was caused by an ad blocker called “AdBlock”.
Thank you so much for taking the time to answer so many questions!The order has been confirmed.
However, when I delete the cache, I can’t enter the card number.
I’m currently using Chrome, and when I tried to view it in Safari, it worked. However, it doesn’t show up well in Chrome.I set it up, but it doesn’t change.
The same error message is being displayed.No other errors or warnings are shown.
The page where the problem is occurring is here.
https://moco-chan-sub.com/stripe-test/Thank you for your understanding.
I’ve tried it in the production environment as well, not in the test, but I can’t enter the card number. It is the same symptom.
I was able to settle with the legacy API. Can the new API be used in the first place?
Thank you!
There are no errors in “Site Health”.
I ran it with the legacy API and got a log. It seems to have been handled correctly. However, the new API does not show the log.
I had a cache plugin set up, but I removed it.
The server is also set to not delete the cache.- This reply was modified 6 years ago by mocomizuki.
I deleted the plugin and tried running it, but no change.
I don’t think the cache has been deleted.I recorded a debug log, but nothing was recorded because I couldn’t hit the buy button.
「Failed to execute ‘postMessage’ on ‘DOMWindow’: The target origin provided (‘https://js.stripe.com’) does not match the recipient window’s origin (‘null’)」 when a modal to enter a name or email address is displayed. error message will appear in the console. Is this relevant?
The version is 2.0.29.
Is it possible to do a test settlement at this stage?
Thank you for your reply.
I’ve checked the contents of the link and I’m sure there are no problems with the settings.
The legacy API can do test settlement, but not the new API.