-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
setup perfectly but it's not working #19
Comments
Check out the Troubleshooting page in the Wiki of this repo. You will want to enable test mode and debug. There are two places with info - one is the developer console of the browser - my guess based on your issue that this is where the info needed will show up. The other is found in the Status tab of WooCommerce admin - you can find the fastspring log - thats more to debug communication between FS and Woo however. So turn test/log on, open the dev console of your browser and look at the messages. Do a fresh reload of the cart and paste the entire log here or in a gist. |
I have set up perfectly everything. double-check it. But I am getting the error Please watch this video: https://www.loom.com/share/ebf44b6dcfed42d3b50dceba734d9a2d |
In the log attached there is an error saying no access key. I see that you have it in your video but when I look at the source code of your site I see this:
Did you add the FS snippet manually as well? This may be conflicting. The WP plugin adds that code - with the access key in it. I think you have two different FS code bits happening. Remove that snippet and try again. |
yeah, another code was activated. now just remove it. but still its not working properly. please check the log file now |
You need to whitelist your domain in FS. Here's the relevant error in your log:
From wiki docs: If you have opted to use the Popup Storefront method you will need to contact FastSpring support and ask them to whitelist your store domain. |
already added my domain as whitelisted website. see the screenshot https://cl.ly/49cbc6 |
It does look correct but that error indicates something is not right with that setup. Contact FS support and tell them you get this message:
Yet your domain is whitelisted. Perhaps they need to reset something. |
got the reply from fastspring support. please check their reply https://cl.ly/eceea1 |
Calling the method as they did does not imply CORS is working. The FS file is loaded on your server so of course you can run methods against it. What doesn't work is sending a POST call to |
their last reply https://cl.ly/876ff2 |
Paste your snippet (I assume its the one from above comment) in a file and save that file as
Then open your browser console and call the URL https://www.msbacademy.com/cors.html and send me what the console says. If it says nothing then CORS is setup correctly - if, on the other hand, you see something like:
Then that implies CORS is not setup correctly by FS. If that is the case, have them escalate the issue to a senior developer (explain that you just pasted the snippet in an html file and there is no WP involved). |
I see in your logs that you have |
I have similar problem - regular payment works, but popup doesn't. Everything is setup correctly. I can see access token included in code (I changed url and access key for privacy):
And code for popup (got this form FS site):
Domain is virtual localhost and it is whitelisted. I get this error: WooCommerce status log is empty and test and logging is enabled in plugin settings... |
@kskrlinnorth2 I created a new issue - let's chat there. #21 |
How did you fixed that? |
@Manika-Kumari it sounds like an invalid access key or a conflict if you have manually added a snippet as OP did. Please open a new issue and provide the log and url as originally asked in this thread and I can take a look. |
Thanks for getting in touch, I have created a separate ticket, here is the link: |
please watch this video https://cl.ly/9a03d0
setup everything perfectly but popup button is not showing up in the checkout page and as a result i can't use fastspring.
The text was updated successfully, but these errors were encountered: