Printable View
You're more than welcome to add me to you ignore list.
I would like to point out though,
If the old jscript had nothing in it but a beginning and closing PHP tag, it's merely being required by some other file SOMEWHERE during the process would break the chain if it were not present.
You can consider that possibility or not.
I will have to disagree with that. I have several clients using this plugin (Square WebPay) with OPC and it works like a charm out of the box with the jscript_square_webPay.php provided with the plugin.Quote:
Originally Posted by dbltoe
@dbltoe - did you go through the tokenization (authentication) process with the new Square WebPay module after installing it? Updated the callback URL in your Square dashboard etc? Did you get the white page that just says "token set" or something like that, can't remember the exact wording now?
+1Quote:
Originally Posted by carlwhat
First of all, thanks for a civil discourse.Quote:
Originally Posted by balihr
About Square. I have been using and setting up Square even before it was part of Zen Cart. I was the one that confirmed WebPay's operation with 1.5.6c and PHP 7.3. See thread Post #2
Even, the required use of a possibly obsolete API Version, was also entered as mentioned in the docs.
As I stated, we have had no problem running WebPay with 1.5.8. However, with the addition of OPC, we were getting the result below as soon as the confirm order was clicked. This site had never had Square before. 1.5.8 was brought in without anything but old images, old define pages, and the old DB. As a totally wild thought, I added the jscript from drByte's mod to the checkout_one folder for lat9's OPC. It is still mentioned in the compatibility ortion of his install notes. Instant and continuing success from then on.
Again, last night after things setttled down on the new site, we again renamed the old file and got the same error when trying through OPC. While not familiar with the intricacies of code, I can recognize the cause and effect we are getting without the file and with. We have noticed this morning that Edit Orders does not seem to be playing nice (maybe the new languages setup) but I have never known edit orders to affect front-end ordering.
I went as far with it as I was capable and brought it to the forum in an attempt to see if someone else was experiencing it and possibilty some direction to look for a fix. I also placed the same info in the OPC forum.
I agree with Carlwhat in that there is no code in the file that should be needed. Yet, as I mentioned later, if the file is in a require somewhere else, it's absence could easily create the fatal error. This is the first time I have ever seen this error message in all of our setups. I have seen others and spinners that turn for days if you let them but, never this. If the fix works for one other person, that's reaason enough for me to mention it.
Any thoughts on adding a Square hosted payment page option? The new PCI changes are heavy....
~Melanie
i have no idea what you mean.Quote:
Originally Posted by mprough
i am not a lawyer. i do not claim to be an expert on PCI-DSS compliance. nor should anything i write be construed as legal advice; or that one is in or not in pci compliance.
square webPay makes use of the square web payments sdk. i would suggest reading a bit here.
all field inputs (and in fact the form) are handled by square, in a PCI compliant manner (according to them).
using the square checkout api (their hosted payment page solution) does not make you any more or less compliant with the PCI-DSS requirements.
best.
I looked all over for that LOL, thank youQuote:
Originally Posted by carlwhat
apparently square could do a better job with their SEO....Quote:
Originally Posted by mprough
Installed the module back in October. I haven't been able to edit the customer's orders. When I clicked "edit" on a previous order today I got the following in the error log:
/admin/index.php?cmd=orders&page=1&oID=729&action=edit, IP address: xx.xxx.xxx.xx
#1 require() called at [/includes/modules/payment/square_webPay.php:508]
#2 square_webPay->admin_notification() called at [/admin/orders.php:731]
#3 require(/admin/orders.php) called at [/admins/index.php:11]
--> PHP Warning: require(/includes/modules/payment/square_support/square_admin_notification.php): failed to open stream: No such file or directory in /includes/modules/payment/square_webPay.php on line 508.
[07-Jan-2023 14:38:57 America/Boise] PHP Fatal error: require(): Failed opening required '/includes/modules/payment/square_support/square_admin_notification.php' (include_path='.:/opt/cpanel/ea-php74/root/usr/share/pear') in /includes/modules/payment/square_webPay.php on line 508
I should I changed this to not show the name of my admin page or ip address. Any ideas?
(i'm assuming you are running v157...)Quote:
Originally Posted by pazdar
look at this link:
https://github.com/zencart/zencart/t...square_support
there are 2 files inside a directory. those files are either missing or they have the wrong permissions on them.
best.
Ver. 1.5.7c Square Web Payments Module 1.0.1 [using SDK: 17.2.0.20220216]
Square does not process the customer purchase unless I go to the "Click for Additional Payment Handling Options" (our admin section), then
Capture Transaction
You may capture previously-authorized funds here:
After I hit "Do Capture" the process is finalized and Square emails me the confirmation of the transaction (Payment received). I did not have to do that while using the old Square module. Is it supposed to work this way now, or I am missing something in the setup? TIA