I've updated the docs and the zip to add dbltoe's points around upgrading.
I've updated the docs and the zip to add dbltoe's points around upgrading.
.
Zen Cart - putting the dream of business ownership within reach of anyone!
Donate to: DrByte directly or to the Zen Cart team as a whole
Remember: Any code suggestions you see here are merely suggestions. You assume full responsibility for your use of any such suggestions, including any impact ANY alterations you make to your site may have on your PCI compliance.
Furthermore, any advice you see here about PCI matters is merely an opinion, and should not be relied upon as "official". Official PCI information should be obtained from the PCI Security Council directly or from one of their authorized Assessors.
Sorry for what is probably a seemingly dumb question
When updating the Square App to the one that matches the latest ZC square plugin, there is a checkbox
Should that box be checked or unchecked?
Change my webhook endpoints to use this API version
Rick
RixStix (dot) com
aka: ChainWeavers (dot) com
If I recall, it will fail if you do.
A little help with colors.
myZenCartHost.com - Zen Cart Certified, PCI Compatible Hosting by JEANDRET
Free SSL & Domain with semi-annual and longer hosting. Updating 1.5.2 and Up.
Thanks, I'll try to make a note to self so that I don't check that box. Based upon the last couple of weeks, I'll be uninstalling and reinstalling square a few times soon.
Still get myDEBUG-adm when refunding. Seems that there were questions regarding your fix... Did that end up being the official fix to eliminate the debugs?
Code:[09-Apr-2020 16:41:43 America/Los_Angeles] Request URI: /ADMINFOLDER/orders.php?selected_box=customers&status=2&page=1&oID=920123&action=doRefund, IP address: 98.146.xxx.yyy #1 square->_doRefund() called at [/home/chainwea/public_html/ADMINFOLDER/orders.php:254] --> PHP Warning: count(): Parameter must be an array or an object that implements Countable in /home/chainwea/public_html/includes/modules/payment/square.php on line 1110.
Rick
RixStix (dot) com
aka: ChainWeavers (dot) com
I was never told if the code to repair the warning would work or not. An on-line tester said that should have taken care of the PHP 7.2 warning. I have not had an occasion to see if the correction stops the warning
The refund that brought up the warning worked just exactly as it should.
Hopefully you'll find an answer.
A little help with colors.
myZenCartHost.com - Zen Cart Certified, PCI Compatible Hosting by JEANDRET
Free SSL & Domain with semi-annual and longer hosting. Updating 1.5.2 and Up.
Had some issues using 1.1.
Seemed to authorize transactions but in admin it would just load a blank page on capture; and not actually capture. Server php is 7.0, zen cart version is 1.5.6c, and the square API is set to 2020-3-25.
Gives me a warning then a error:
Code:PHP Warning: Missing argument 2 for SquareConnect\Api\PaymentsApi::completePayment(), called in /public_html/includes/modules/payment/square.php on line 1158 and defined in /public_html/includes/classes/vendors/square/connect/lib/Api/PaymentsApi.php on line 266. PHP Fatal error: Uncaught InvalidArgumentException: Missing the required parameter $body when calling completePayment in /public_html/includes/classes/vendors/square/connect/lib/Api/PaymentsApi.php:292
I cant remember which version I tried to upgrade from, But 1.1 will not capture transactions. To get 1.1 to function at all I had to uninstall and reinstall the module.
I uninstalled 1.1 module -I downloaded 1.0, overwrote all files and its working.
I'm not sure what is going on between to two versions, But Ill keep a eye out for this token refresh bug for now.
A little help with colors.
myZenCartHost.com - Zen Cart Certified, PCI Compatible Hosting by JEANDRET
Free SSL & Domain with semi-annual and longer hosting. Updating 1.5.2 and Up.
.
Zen Cart - putting the dream of business ownership within reach of anyone!
Donate to: DrByte directly or to the Zen Cart team as a whole
Remember: Any code suggestions you see here are merely suggestions. You assume full responsibility for your use of any such suggestions, including any impact ANY alterations you make to your site may have on your PCI compliance.
Furthermore, any advice you see here about PCI matters is merely an opinion, and should not be relied upon as "official". Official PCI information should be obtained from the PCI Security Council directly or from one of their authorized Assessors.