Hi,
Yep, I'm at a bit of a loss to help here, because I don;t know what your bespoke shipping provider is doing. A couple of things you could try is to set some kind of shipping in the standard NB_store shipping calculation and see if it's working...if it is then maybe you provider is not being called at all, which could be a caching issue, but I would expect a restart of the app to solve that.
Another idea, if you have the original source code of your bespoke provider is to add some debug statement which fire off a msg to the DNN log and hence try and trace the action that way.
After you've setup test rig, if you let me have access I could have a look, but to be honest without knowing what you bespkoe provider is doing, I may not be much help.
As a temporary fix you could activate the NB_store shipping with some kind of close matching shipping price, so you client doesn't lose money. But I suppose this depend on how complicated you clients shipping calcs are!
Regards,
Dave.
Yep, I'm at a bit of a loss to help here, because I don;t know what your bespoke shipping provider is doing. A couple of things you could try is to set some kind of shipping in the standard NB_store shipping calculation and see if it's working...if it is then maybe you provider is not being called at all, which could be a caching issue, but I would expect a restart of the app to solve that.
Another idea, if you have the original source code of your bespoke provider is to add some debug statement which fire off a msg to the DNN log and hence try and trace the action that way.
After you've setup test rig, if you let me have access I could have a look, but to be honest without knowing what you bespkoe provider is doing, I may not be much help.
As a temporary fix you could activate the NB_store shipping with some kind of close matching shipping price, so you client doesn't lose money. But I suppose this depend on how complicated you clients shipping calcs are!
Regards,
Dave.