I'm running Tea Commerce 2.2.3 (Umbraco 6.1.6), and I'm having an issue when calling TC.GetAllFinalizedOrdersForCustomer()
It's coming back with "Sequence contains more than one matching element" errors, which I can only clear by touching the web.config file to recreate the cache.
I see there was a legacy error when saving a finalized order would create a duplicate in the cache, but that was supposedly fixed in version 2.1.3.
My site does do a fair amount of saving finalized orders as there is a saved basket feature among other things, but this doesn't happen consistantly, so not sure it's the same issue.
Anyone have any thoughts at all, I know there's not a lot to go on without getting in to lots of detail..
Busy few days... I'll have to get back to you with if this works or not at a later date.. I can make the update locally, but the problem never seems to occur there so may not confirm if it fixes the issue or not. Will have to wait a while before I can update the live site though, lots of other changes going on first.
Thanks, I thought this was probably going to be necessary anyway..
Are there any database changes from v. 2.2.3 to v. 2.3.2?
There's nothing explicitly mentioned in the revision history, but wanted to check anyway. If not then I should be able to just upload the changed files to my live server when ready, is that correct?
Normally I would install the package on a local site with local DB - see everything is working and change the things I need. Then when going live. Install Tea Commerce as a package online so DB changes will happen if there is any. Then upload the files that is changed from local. The is the most secure way.
TC.GetAllFinalizedOrdersForCustomer() finding duplicate orders
Guys,
I'm running Tea Commerce 2.2.3 (Umbraco 6.1.6), and I'm having an issue when calling TC.GetAllFinalizedOrdersForCustomer()
It's coming back with "Sequence contains more than one matching element" errors, which I can only clear by touching the web.config file to recreate the cache.
I see there was a legacy error when saving a finalized order would create a duplicate in the cache, but that was supposedly fixed in version 2.1.3.
My site does do a fair amount of saving finalized orders as there is a saved basket feature among other things, but this doesn't happen consistantly, so not sure it's the same issue.
Anyone have any thoughts at all, I know there's not a lot to go on without getting in to lots of detail..
Thank you!
Mark
Hi Mark
Could you upgrade to 2.3.2 and see if you still have the bug? Please see the revision history for breaking changes.
http://documentation.teacommerce.net/revision-history/
Kind regards
Anders
Hi Anders,
Busy few days... I'll have to get back to you with if this works or not at a later date.. I can make the update locally, but the problem never seems to occur there so may not confirm if it fixes the issue or not. Will have to wait a while before I can update the live site though, lots of other changes going on first.
Thanks, I thought this was probably going to be necessary anyway..
Mark
Just a quick one..
Are there any database changes from v. 2.2.3 to v. 2.3.2?
There's nothing explicitly mentioned in the revision history, but wanted to check anyway. If not then I should be able to just upload the changed files to my live server when ready, is that correct?
Many thanks,
Mark
Normally I would install the package on a local site with local DB - see everything is working and change the things I need. Then when going live. Install Tea Commerce as a package online so DB changes will happen if there is any. Then upload the files that is changed from local. The is the most secure way.
Kind regards
Anders
is working on a reply...