Vikrant Sant
Forum Replies Created
-
@hagentertainment,
Thank you for taking the time to leave this detailed feedback.PeachPay supports a broad range of payment gateways and checkout configurations, and occasionally gateway-side changes or store-specific callback conditions can impact how certain payment methods behave.
In Square’s case, their connection requirements have changed over time, which is why recent versions now rely on direct API credentials rather than the previous OAuth-based setup.
As for the pending payment status you mentioned with redirect-based methods, we would want to review the exact transaction flow on your store before making any assumptions, as completed customer payments should normally return a finalized order status in WooCommerce.
Please feel free to contact me directly at [email protected] with your store details and a few affected order examples. I would be glad to take a closer look with our engineering team.
Hi there @digitaltreecompany ,
Thank you for reporting this, and I sincerely apologize for the experience here.
You’re absolutely right that the update was not smooth. The requirement to reconnect Square and manually enter API keys should have been communicated much more clearly in the changelog.
To provide some context (not as an excuse), when reviewing this change on our end, the Square partner portal did not show any active merchants connected. Based on that, we did not expect this to impact existing users in this way, but clearly that assumption was incorrect, and we’ll keep this in mind for future updates and migrations.
We are working on investigating the fix and will update you accordingly.
Best,Vikrant
Our team is investigating this issue soon. Generally, a callback failure of this nature occurs when the hosting provider (Kinsta) blocks the incoming request, preventing the order status from updating to “Processing.”
We are currently moving all integrations to be client-side to bypass these types of server-side handshake issues. This update will be live in a couple of weeks and will provide a more stable environment for third-party methods.
We will get back to you as soon as we have more information from our investigation.
Forum: Plugins
In reply to: [Related Products for WooCommerce] PHP Warning: filemtime(): stat failedHey @gerche
Thank you for flagging this and for taking the time to investigate the root cause. Really appreciate the detailed breakdown.You’re absolutely right about
filemtime()requiring a filesystem path and the issue being triggered byplugin_dir_url(). We’ll be updating the plugin to useplugin_dir_path()as suggested.We’ll get a fix pushed out soon.
Thanks again for bringing this to our attention!
Let me know if you notice anything else.Hi Arp,
Thank you for bringing this issue to our attention. We will have it fixed soon!
👍