balihr:
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.
@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?
+1First of all, thanks for a civil discourse.
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.