OpenCart Community

Assuming you don't want anything to do with the API thing.

Is there some code edit that will just let you bypass the API,to just to let you update orders, and add history to orders, without getting the error?

tom327 wrote:Assuming you don't want anything to do with the API thing.

Is there some code edit that will just let you bypass the API,to just to let you update orders, and add history to orders, without getting the error?

Quite on the contrary. I really like the API. Although, the methodology used to manipulate the API is what I am deeply concerned.

As for adding history to orders without errors, this step has been proven as errorless: http://forum.opencart.com/viewtopic.php ... 20#p626278

Although, you still need to add an API.

Sorry but I added the api did all that and still get the error, so it is NOT errorless.

labeshops wrote:Sorry but I added the api did all that and still get the error, so it is NOT errorless.

Which OC version are you using?

2.2 as I have said before and as it says in my signature.

Do you have any extensions installed?

Yes, but nothing that affects the order page or does anything to the api.

labeshops wrote:Anyone know if any of the order history mods bypasses this error? Like the popup order history, mass order history updator, etc? Getting kinda desperate here as I know I'm going to mess up someone's order or forget to ship something.

Oh goodness, I found my fix. I changed the fraud setting from cancelled to processing and now I am able to reset the status back to a processing (couldn't change it from canceled.)

It annoying that we have this issue. I consider it to be a biggie as customers are wondering why their order is canceled. Especially when they have paid.

Anyways, I hope this helps.

Unbelievable. All this to unlock an order while all this could be avoided by simply relying on the CSRF protection form. Thanks for posting the instructions mysite10.

Mysite10 wrote:

labeshops wrote:Anyone know if any of the order history mods bypasses this error? Like the popup order history, mass order history updator, etc? Getting kinda desperate here as I know I'm going to mess up someone's order or forget to ship something.

Oh goodness, I found my fix. I changed the fraud setting from cancelled to processing and now I am able to reset the status back to a processing (couldn't change it from canceled.)

It annoying that we have this issue. I consider it to be a biggie as customers are wondering why their order is canceled. Especially when they have paid.

Anyways, I hope this helps.

I don't use any of the fraud systems. They are not installed so this isn't my issue.

labeshops wrote:

Mysite10 wrote:

labeshops wrote:Anyone know if any of the order history mods bypasses this error? Like the popup order history, mass order history updator, etc? Getting kinda desperate here as I know I'm going to mess up someone's order or forget to ship something.

Oh goodness, I found my fix. I changed the fraud setting from cancelled to processing and now I am able to reset the status back to a processing (couldn't change it from canceled.)

It annoying that we have this issue. I consider it to be a biggie as customers are wondering why their order is canceled. Especially when they have paid.

Anyways, I hope this helps.

I don't use any of the fraud systems. They are not installed so this isn't my issue.

What about the installed extensions?

extensions I have installed:

adv products puchased report
coupon on checkout page
date added for products
facebook og tags
gearbox modules
guest order view
manufacturer description
opencart shortcodes
product model in autocomplete
rhythm opencart theme framework
shopencart news/blog
size chart
to top (scrolling)
viethemes all layouts

vqmods:

extended save buttons
fix-google-analytics-oc2.2
gaecommerce
option to products
uksb google merchant
vqmanager
latest product rss feeds


That is all. No fraud ones, no openbay. Nothing that I know of that affects api or the admin orders pages. All are working properly. All were written specifically for v2.2

BTW, I had this problem before I had even installed any mods or vqmod

One symptom have may have discovered which may only cover the minimum in this topic is the IP address tracking which minimal rates of providing chances that may be restricted from the browser but may cause to create an error popup on screen.

If it may help anyone, on that end, here's the XML file for Opencart v2.2.0.0 release. This will restrict the merchant on adding API IDs and Passwords if the IP address could not be tracked in the first place. If the account has already been added and the IP address has been restricted after that time period, the IP address will also be verified.

If you encounter XML file errors, please use the VQMod Manager to track the source lines in order to guide you to the right answer before posting the already problematic and encountered issues with lines conflict by using VQMod.

If more solutions are coming on, I will post them accordingly.

The vqmod didn't fix my problem but not clear from your post which one it was addressing. tried it anyway.

labeshops wrote:The vqmod didn't fix my problem but not clear from your post which one it was addressing. tried it anyway.

My post clearly indicates that the XML file is for IP addresses validations from the server. If it does not address your issue, as mentioned above, if I do find other possible symptoms, I will post them accordingly.

Opencart Beta 2.3.0.0 released and announced on this topic: http://forum.opencart.com/viewtopic.php?f=2&t=164930 . The API login has been modified on this version. As Heather mentions, however, do NOT use for production purposes until the final release has been officially released by the team.

** Store ID from the admin/controller/sale/order.php file.

The store ID has been added into the controller in order to be used rightfully in the API URL.

** Order delegation content form **

The $json['code'] has been replaced with value.

** Shipping Address Method **

The button shipping address method property has been replaced with loading and reset case.

** jQuery Parent to closest method replaced **

parent() has now been replaced with closest().

** Postal code **

The postal code validation has been modified in the admin order API.

** Store URL over Catalog link over API **

The Store URL link has been changed for the Catalog link over API instead.

** Currency **

The admin currency has been fixed on this version over the API.

straightlight wrote:

labeshops wrote:The vqmod didn't fix my problem but not clear from your post which one it was addressing. tried it anyway.

My post clearly indicates that the XML file is for IP addresses validations from the server. If it does not address your issue, as mentioned above, if I do find other possible symptoms, I will post them accordingly.

"clearly" except I have no idea what "Ip addressess validations" are - I don't speak code, just have learned how to modify it during the 10+ years I've been workng with php carts.

Looking forward to the update and hopefully it will fix my issue when it's ready for live stores.

Looking forward to the update and hopefully it will fix...

better don't bet on it, more and more, I feel like a motherless child.
opencart-2.3.0.0_b1\upgrade.txt
the good old mess-up info still exists, and the 'upgrader'-saga probably will continue:
/// OpenCart V1.5.x TO 1.5.x ///
/// Upgrade Instructions ///

IP_CAM wrote:

Looking forward to the update and hopefully it will fix...

better don't bet on it, more and more, I feel like a motherless child.
opencart-2.3.0.0_b1\upgrade.txt
the good old mess-up info still exists, and the 'upgrader'-saga probably will continue:
/// OpenCart V1.5.x TO 1.5.x ///
/// Upgrade Instructions ///

Well now that I've been maintaining the upgrade script it should at least be better... tho I haven't touched the upgrade.txt file...

BTW, just discovered return history updates fine - apparently it does not use the api??