Why the API issue happens?
Because since OC 2 OpenCart has absolutely ugly algorithm of editing orders from admin. In my opinion, it doesn't have any excuses or really solid reasons to be implemented. Never seen anything like this in any other platform and hopefully never will.
When it happens?
Sometimes it is indeed an issue with API settings or database structure after OC upgrade, sometimes a server side issue.
How can I fix this?
There're plenty simple solutions right in this topic, which may help, if your case is wrong setup/upgrade. If none of them helped and you're pretty sure, that all settings are correct, then you're, well... fudged. Even if you disable API check, the issue may stay and pop again in different places. For example, when editing an order, a payment/shipping address may be stored in session and not retrieved right in the next API call, when payment/shipping methods are queried. This happens, because session data was lost.
I've seen it personally on a few systems and there was a discussion of StackOverflow a few years ago, where issues with particular version of CentOS (or maybe some other server OS, not sure) were reported. The only way in the case, when no other solution helped, is to get yourself an admin and start digging into the issue.
P.S.: For me this API issue ALWAYS happened on OC 2.3 only, other versions worked just fine. It appears, that OC 2.3 is the most troublesome version, when it comes to API.
Correct. v3.x releases have been mostly fixed regarding the APIs since.P.S.: For me this API issue ALWAYS happened on OC 2.3 only, other versions worked just fine. It appears, that OC 2.3 is the most troublesome version, when it comes to API.
The most generated errors being found on Opencart forum originates from contributed programming. The increased post counters are caused by redundancies of the same solutions that were already provided prior.
Opencart.com Administrator / Quality Assurance Analyst / Programmer
Users browsing this forum: No registered users and 12 guests