then some where within your code you have a missing , or ' or ; .Quote:
Originally Posted by gizmo_girl
and if my last post still does not work then do a full compare of a fresh copy of your version of ZC
Printable View
then some where within your code you have a missing , or ' or ; .Quote:
Originally Posted by gizmo_girl
and if my last post still does not work then do a full compare of a fresh copy of your version of ZC
I have added a test product (virtual/zero dollars) that can be added to a cart. I'll send you the test account details. Thanks!Quote:
Originally Posted by OJ_SIMON
gizmo
long shot here.
in your admin payment screenshot it looks like both enabled modules have the same sort order; ie 0.
see if changing one of them to 10 makes a difference.
This is the problem:Quote:
Originally Posted by gizmo_girl
you have a country or currency miss match within your setting ether in ZC or at square they all need to match.Quote:
Payment Method
Sorry, we are not accepting payments from your region at this time.
Please contact us for alternate arrangements.
Nope, that was one of the first things I tried yesterdayQuote:
Originally Posted by carlwhat
Quote:
Originally Posted by OJ_SIMON
BAM!!! THAT DID IT! Thanks so so so much for your help! I had the payment zone in ZC as 'United States'.
Hello all,
I'm using ZC1.5.6c with PHP7.3, MariaDB 10.3.24, and Square WebPay 1.0.4. In Square, I am using the API version from 2022-02-16 (unchanged from when I installed the module I think), but I also switched to the latest version that does not require domain verification, with no change in behaviour.
My own browser is Firefox 125.0.1.
The last successful payment was on 23rd March 2024, since then the "Continue" button to continue to step 3 (confirmation) of the checkout page does nothing, and there is no log file generated. I see the GET in my access log with a 200 HTTP response, but there seems to be no communication to or from Square.
Looking at the Network tab in Firefox developer tools shows oddly that the beacon connection to pci-connect.squareup.com is failing with NS_ERROR. Reloading the page shows dozens of these errors, but no issues with access to other Square-related subdomains, or even to pci-connect.squareup.com when the connection is not a beacon but instead, say, a fetch.
Attachment 20592
When I do presse the "Continue" button I see the sucessful GET and then a failed beacon, after that nothing.
Attachment 20591
When I do a nameserver lookup for pci-connect.squareup.com, there is a valid response, I can even connect to that domain via HTTPS, although it redirects to my local (Japan) Square site immediately.
Searching online I see this problem might be related to access control and/or CORS (cross-origin resource sharing) settings in my browser, but I have no idea at the moment how to solve this. Also I have seen articles on beacon issues with other browsers, such as Safari and Chrome.
Is this something I need to investigate further on the browser side - and potentially educate customers, since there have been complains that "nothing happens" when trying to go to Step 3 of checkout - or is this something I can fix on the server side?
It might be that the above is a red herring, and that the issue is entirely somewhere else, but I have no logs to go on, and no changes have been made to the webshop.
Any advice/insights appreciated.
Addendum: I have realized that in NS_ERROR_FAILURE the "NS" stands for namespace, and not nameserver.
please provide your website url.Quote:
Originally Posted by gernot
Hello Carl,
https://www.proteawines.jp/shop/