TC.GetCurrentOrder never completes when run from UmbracoApiController
Hello,
We are having an issue with TC.GetCurrentOrder(1) where this call never actually completes whenever it is called from an UmbracoApiController. Specifically there is no error and no timeout when called in this context. It works perfectly whenever called from a razor though, so we are thinking WebApi/UmbracoApi has something to do with this. We just don't know what or how.
Does anyone have any ideas?
We are using version 2.2.3 on an umbraco 6.1.6 installation if that helps.
A REST API is stateless by design - and Tea Commerce needs to use session cookies for the cart. So I dont think that you can use an ApiController for what you are doing. What you properly want to do is use /base in umbraco which has state/session.
Thanks for the reply and the reasoning. Was a great help :).
Since we can still fetch orders by id we found a way to get the id and use that within the webapi (since webapi is nonoptional for this).
TC.GetCurrentOrder never completes when run from UmbracoApiController
Hello, We are having an issue with TC.GetCurrentOrder(1) where this call never actually completes whenever it is called from an UmbracoApiController. Specifically there is no error and no timeout when called in this context. It works perfectly whenever called from a razor though, so we are thinking WebApi/UmbracoApi has something to do with this. We just don't know what or how.
Does anyone have any ideas? We are using version 2.2.3 on an umbraco 6.1.6 installation if that helps.
Thanks in advance, Anders
Hi Anders
A REST API is stateless by design - and Tea Commerce needs to use session cookies for the cart. So I dont think that you can use an ApiController for what you are doing. What you properly want to do is use /base in umbraco which has state/session.
Kind regards
Anders
Thanks for the reply and the reasoning. Was a great help :). Since we can still fetch orders by id we found a way to get the id and use that within the webapi (since webapi is nonoptional for this).
is working on a reply...