As I previously mentioned, those two files do not resolve the issue for me. I still get the same syntax errors as I previously posted.
Even if I disable the custom fields, I still get syntax errors when trying to edit an order?
If anyone has a solution for this 'bug' please feel free to 'chip' in. Thanks.
Using OC Version 3.0.3.2
Upgrade Service | OC 2.3.0.2 PHP 8 | My Custom OC 3.0.3.8 | Buy me a beer
Attachments
catalog/controller/api/customer.php
Using OC Version 3.0.3.2
Upgrade Service | OC 2.3.0.2 PHP 8 | My Custom OC 3.0.3.8 | Buy me a beer
A quick update on this bug/error for any OC devs who may, or may not be trying to fix this issue.....
I previously tried to get round this problem by disabling the custom fields. However, this didn't work for me.
Today I tried turning off the 'required field' in the custom fields preferences, which enabled me to get past the first 'tab' (Customer Details) when editing an order. However, it still failed at the third 'tab' (Payment Details). I've attached the syntax error message for any OC devs who are interested in attempting to fix the issue.
Thanks.
Attachments
Using OC Version 3.0.3.2
Upgrade Service | OC 2.3.0.2 PHP 8 | My Custom OC 3.0.3.8 | Buy me a beer
When I go to edit orders, and click on 'continue', it just says 'loading' for a second and then turns blue again, nothing happens.
At first, indeed, I had a custom field, that was giving me errors about being required.
But this problem persists with custom field disabled.
Based on the advice in this forum, I went to github, and replaced shipping, payment and customer php files.
I also cleared caches. But still, no change.
Can anybody help me please? I'd really appreciate it.
In the Developers Kit of your browser > console tab with XHR option enabled, do you notice any error messages after seeing the loading message?zengalaxy wrote: ↑Tue May 12, 2020 6:04 pmHi guys, I'm running 3.0.3.2.
When I go to edit orders, and click on 'continue', it just says 'loading' for a second and then turns blue again, nothing happens.
At first, indeed, I had a custom field, that was giving me errors about being required.
But this problem persists with custom field disabled.
Based on the advice in this forum, I went to github, and replaced shipping, payment and customer php files.
I also cleared caches. But still, no change.
Can anybody help me please? I'd really appreciate it.
Dedication and passion goes to those who are able to push and merge a project.
Regards,
Straightlight
Programmer / Opencart Tester
So why the heck you don't make another topic/post?
Upgrade Service | OC 2.3.0.2 PHP 8 | My Custom OC 3.0.3.8 | Buy me a beer
For me, there's no errors showing in XHR, json 200 POST was all ok as far as I could tell. Just the syntax error in OC as previously explained...thanks.
Using OC Version 3.0.3.2
SyntaxError: JSON.parse: unexpected character at line 1 column 1 of the JSON data
Using OC Version 3.0.3.2
Please check your error / server access logs for those errors. Additionally, you can also check for your Developers Kit > console tab with HXR enabled (F12 function) to track further error messages.ihateusernames wrote: ↑Mon May 18, 2020 10:53 amOK, my mistake, I found this error in the 'response' column...
SyntaxError: JSON.parse: unexpected character at line 1 column 1 of the JSON data
Dedication and passion goes to those who are able to push and merge a project.
Regards,
Straightlight
Programmer / Opencart Tester
I also had a look at the OC error_log & although there are 1000's of errors in that file, I couldn't find anything that related to this particular error?
If I did though, what are you asking me to do with them? Thanks.
Using OC Version 3.0.3.2
I am experiencing the exact same problem in OC 3.0.3.3 (latest to this date). First step of order edit there was the custom field required error, resolved with this posts answers. Now at step 3 the exact syntax error you got. Did you get it work afterall? Thanks.ihateusernames wrote: ↑Tue May 19, 2020 11:43 amOK, I had a look at server errors & couldn't find anything relating to that syntax error. There was only one error in there, so not sure what that means?
I also had a look at the OC error_log & although there are 1000's of errors in that file, I couldn't find anything that related to this particular error?
If I did though, what are you asking me to do with them? Thanks.
Dedication and passion goes to those who are able to push and merge a project.
Regards,
Straightlight
Programmer / Opencart Tester
still can't go to step two on order edit on OC Version 3.0.3.3 after changing api files customer/payment/shipping/orderstraightlight wrote: ↑Tue Jun 09, 2020 5:43 amThe pre-release version contains bug-fixes about the custom fields validation. I may not have completely done the patching as we speak. However, I would invite you to visit the official bug reports topic about the pre-release to be up-to-date on the subject and furthermore.
when disabling the custom field it works fine
1.Custom Field Input Field is not shown on Customer Details tab on Order Edit
2.The API Return that the custom field is required " It know it's required but i can't even edit/read it because the input field is missing
3.Can't go to step 2 while the custom field is enabled once it's disabled everything works like a charm
4.Tried to copy customer edit form catalog/customer/edit to admin/sale/order_form but did not work
5.Tried the api files on github and it didn't work
6.Removed the custom field validation from the api/customer.php it worked but it's just a workaround not the fix
Yep, this hasn't worked since I installed OC over a year ago. I can disable the custom field validation in the api/customer.php too, but you still can't edit or add to the order, which makes OC unusable at the moment (at least in terms of Invoicing customers). Hopefully someone will fix the code soon?
Using OC Version 3.0.3.2
I didn't edit any files but the continue button in order edit still doesn't work in v3.0.3.6 either. Anyone know of the fix?Lembo wrote: ↑Fri Jul 03, 2020 8:30 pmstill can't go to step two on order edit on OC Version 3.0.3.3 after changing api files customer/payment/shipping/orderstraightlight wrote: ↑Tue Jun 09, 2020 5:43 amThe pre-release version contains bug-fixes about the custom fields validation. I may not have completely done the patching as we speak. However, I would invite you to visit the official bug reports topic about the pre-release to be up-to-date on the subject and furthermore.
when disabling the custom field it works fine
ELEV8TE Website Development
Available for hire - please send email to hello@elev8your.com
https://www.elev8your.com
Users browsing this forum: No registered users and 60 guests