Updated from 5.8.2 to 6.8 and now my stripe page does not work

Wappler Extensions Bugs
1

This is what I get now when I run the page that was working using 5.8.2.:

{"code":"42000","file":"/home2/estatej/public_html/dmxConnectLib/lib/db/Connection.php","line":112,"message":"SQLSTATE[42000]: Syntax error or access violation: 1064 You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '))' at line 1","trace":"#0 /home2/estatej/public_html/dmxConnectLib/lib/db/Connection.php(112): PDO->prepare('SELECT PID, ...')\n#1 \/home2\/estatej\/public_html\/dmxConnectLib\/modules\/dbconnector.php(96): lib\\db\\Connection->execute('SELECT PID, ...', Array, true, '', Array)\n#2 /home2/estatej/public_html/dmxConnectLib/lib/App.php(223): modules\dbconnector->select(Object(stdClass), 'query', Array)\n#3 /home2/estatej/public_html/dmxConnectLib/lib/App.php(195): lib\App->execSteps(Object(stdClass))\n#4 /home2/estatej/public_html/dmxConnectLib/lib/App.php(163): lib\App->execSteps(Array)\n#5 /home2/estatej/public_html/dmxConnectLib/lib/App.php(152): lib\App->exec(Object(stdClass), false)\n#6 /home2/estatej/public_html/dmxConnectLib/lib/App.php(113): lib\App->exec(Object(stdClass), false)\n#7 /home2/estatej/public_html/dmxConnect/api/cart_checkout.php(7): lib\App->define(Object(stdClass))\n#8 {main}"}

Obviously I'm stuck now - and after all the help Teodore had given me to make the page wok. Any help would be appreciate.
Access: Estate Jewelry Liquidations

2

You have an error in the SQL syntax of a database query. The error is triggered in the cart_checkout server action. You can first try to open the action in Wappler and check for any errors in the queries, then save the file again and test it. If you have multiple queries, you can disable them one-by-one until the error is gone to find which query is causing the error.

If you can't figure out what is wrong, then post the query that is causing the problem here in the forum and perhaps we can help you solve it.

I don't think it is a bug in Server Connect code but will need some more information first about which query is causing the error to be sure.

1 Like