I wanted to do some tracking on the post purchase page. GTM is installed in checkout.liquid and I've added it on the post purchase page via Settings. But the problem is that I'm getting DOMException: Blocked a frame ... from accessing a cross-origin frame.
From what I understand, post purchase scripts (under Settings) run on sandbox and maybe that's what is causing the issue.
How to properly install gtm in Shopify post purchase page?
Related
My purpose is to automate (as buyer) login into PayPal Sandbox(1) and confirm payment(2) using REST requests (with Postman) after being redirected from third-party payment service.
From there a got a link like: https://www.sandbox.paypal.com/cgi-bin/webscr?cmd=_express-checkout&token=EC-5AU897953H105581R
I have login and password for buyer account.
I was able to import request from devtools network and it leads me to confirm form, but I cannot make it generic. I found out that the minimum body values are (on screen), but there are some changes in cookies at headers. I am not sure if my approach is even correct. Do you have any ideas?
If you find out the first very easily, maybe you will also have some tips for confirming payment.
I already searched a lot for answers. There are some instructions for sandbox API, but it looks like it needs clientId and secret(?). See those on the PayPal Sandbox development page, but I do not have credentials for dev dashboard, only for my test customer.
I am trying to integrate PayU payment gateway on my website, referring their documentation.
They are recommending to use merchant key as a hidden input field but should i really put my merchant key on the frontend as a educated user can easily find it out. I tried making the payment request from my backend and sending the HTML recieved to the user but the script file is not loading is stuck on the loading page. What can i do to load the script file so that it redirects to the payment page.
We develop our first app and use Shopify gem. It works fine and all functionality (including installation flow) is working well.
We've sent the app for a review and received an answer with following comment from their QA:
After installing the app from the Shopify App store, the app is redirecting to the website where the app is hosted. When accessing the app from a shop's app dashboard, the app is redirecting to the embedded version. This occurs when an initial OAuth request redirect fails to escape the iframe. Please refer to our embedded app OAuth documentation (https://help.shopify.com/en/api/embedded-apps/embedded-app-sdk/oauth) for further information.
Has anybody faced with this problem?
Shopify QA doesn't answer our e-mails and we couldn't find any useful requirements or information on shopify forums.
I have a problem with BigCommerce installation process.
According to documentation (https://developer.bigcommerce.com/api/callback) I receive GET request, do exchange for OAuth info via POST request and return HTML page to user.
App seems successfully installed, I can see it in left panel, but it don't send request to LoadCallback with signed payload. When I click to application's icon it just hides/shows HTML page that I send during intallation.
Seems like the only way to make BigCommerce do LoadCallback request is to open app after relogin.
Did I do something wrong during installation process?
No, this is intended behavior. Most apps have a sign up process that cause a frame reload of the app. You can force a reload after installation or use a form submission action via javascript. Alternatively, you can reload the control panel and reopen app or relogin and open.
We created the user-photos app published in the Shopify app store.
But it suddenly stopped working on all our clients stores, we have not made any changes.
The issue we see relates to the URL forwarding from Shopify. For exmaple this URL
http://www.jurawatches.co.uk/apps/userphotos/photo/index/jurawatches.myshopify.com/82247292
Should go to this URL: http://userphotos.78e.co.uk/photo/index/jurawatches.myshopify.com/82247292
But we are getting this error: We're experiencing a technical problem and we are doing everything we can to resolve it as soon as possible.