This is the error i'm getting from my log, hope this helps.
PHP Warning: Illegal string offset 'cost' in /home/pkpoker/public_html/includes/classes/order.php on line 355
Thank You DrByte
This is the error i'm getting from my log, hope this helps.
PHP Warning: Illegal string offset 'cost' in /home/pkpoker/public_html/includes/classes/order.php on line 355
Thank You DrByte
This is a mod. There's no such field in vanilla Zen Cart.
That Software Guy. My Store: Zen Cart Support
Available for hire - See my ad in Services
Plugin Moderator, Documentation Curator, Chief Cook and Bottle-Washer.
Do you benefit from Zen Cart? Then please support the project.
.
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.
in v1.5.1 the line reads:
in v1.5.7 it's using the following, which you can safely use in v1.5.1 as well:Code:'shipping_cost' => $_SESSION['shipping']['cost'],
While this isn't technically a "bug", there have been some bugs fixed in various Zen Cart versions associated with mixed ways of representing that $_SESSION['shipping'] array.Code:'shipping_cost' => !empty($_SESSION['shipping']['cost']) ? $_SESSION['shipping']['cost'] : 0,
If you're going to stay on v1.5.1 then you should also keep watching for all bugs fixed in newer versions and backport them to your old version.
That said, this "PHP Warning" is just a warning. Warnings sometimes do point to underlying issues. I don't think this one is affecting/causing your CURL issues or the issue of orders not completing. I would expect that a "PHP Fatal error" is happening somewhere to cause the issues you were reporting.
.
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.
Hi, jumping in here as I also have the same issue since start of July,
Connecting to PayPal Express/Pro Server ... Error 28: Connection timed out after 5000 milliseconds
Connecting to PayPal TLSTest Server ... Error 51: SSL: no alternative certificate subject name matches target host name 'tlstest.paypal.com'
Apart from hosting issues, I'm wondering if this has got anything to do with Paypal's NVP deprecation to REST?
The "tlstest.paypal.com" host was retired awhile back.
The latest curltester script doesn't check it anymore.
The paypal servers still respond from all parts of the world that I've been able to check.
Error 28 means a timeout happened, either during DNS lookup (a hosting configuration issue) or during attempting to connect (no response, which could be a firewall issue with your server/hosting-company, a server-overload (ie: slow) on the destination server, or the destination server is down, affecting everyone globally).
.
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.