-
-
Notifications
You must be signed in to change notification settings - Fork 436
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Syntax error or access violation: 1064" when placing an order with 19.5.0-rc3 #3213
Comments
I used the latest version of OpenMage (main branch) with Magento Sample Pack. I placed the order and looked in the logs. Apart from those reported here #3184, I did not find any of those reported by you. We cannot investigate particular cases that appear in custom installations, with extensions. It is known that major changes have been made in OpenMage to make it compatible with the latest version of PHP and certain extensions can no longer work. As you can see from you report, there are most likely errors in the extensions (custom SQL queries., Try to disable all of them except those related to OpenMage and analyze if the errors still occur. If no one else confirms this report we will close it within a week from now. |
mmmm the only thing I see is a tax_class_id = 2, maybe we should check with real tax amounts just to be sure :-\ |
Thanks @ADDISON74. The stack trace doesn't appear to be running through any extensions, and I'm not aware of any on this installation relating to taxation. I've checked the only other mention of third party code, which is the theme, and that doesn't appear to be a culprit. However, I'll try disabling some extensions and see what happens. Thanks for investigating.
|
It could be an observer, it wouldnt be visible in the stack in some cases |
I think this is that. |
Most likely originating from the line below. Try wrapping the sql code in a
|
Thanks @elidrissidev. This fixed the issue.
|
@elidrissidev No, I simply wrapped the line you suggested in Data.php with a new Zend_DB_Expr. Your PR doesn't make any changes to that file. |
Could you try that fix instead? If it solves the issue it will make it to a new RC release soon. |
Preconditions (*)
Steps to reproduce (*)
Expected result (*)
Actual result (*)
The text was updated successfully, but these errors were encountered: