I just got home from vacation and our customer wrote a quite odd error, that im trying to figure out.
Its about the order confirmation mail, and when its being sent out.
We have setup so that everytime an order is placed our customer recieves a copy of the order confirmation, that their customer gets.(standard setup in my head)
This weekend some(not all the mails that they received failed) of the order confirmation mails that our customer got throws an XSLT error :
Something went wrong when requesting a xslt with invokeXSLT(): An attempt was made to
reference a CacheDependency object from more than one Cache entry.
But when we log in to teacommerce and just clicks the order and resends the order confirmation its working fine. So in my head the XSLT is parsing just fine since its the same XSLT file thats being used. But my theory was that the mail would be sent out to early in the process ?
That confirmation mail is sent just after the order have been finalized. That means after the payment have been confirmed.
It's the first time I have seen that error and don't think Tea Commerce could create it on itself. Do you have some custom code running that might be messing around with the order?
Hmm okay. No so far its pretty straight forward order flow, we have no special code in the flow. The order/payment is going through and we resend it, it just works which is the wierdest thing.
I have also seen this error It happens once or twice a week in the shop where I am having problems. I did spend some time trying to figure out what was wrong and found this forum post, which seems to describe the same behaviour. I tried to upgrade the installation to 4.7.2, hoping the patch mentioned in the post made it into that release, but I still get this error.
Since codeplex was cleaned up I couldn't find the patch, maybe I should check the new issuetracker to see if it was migrated.
Great you found what cause the issue! I think that Umbraco watch the issue tracker all the time. If you want to you can write Sebaastian at twitter and let him know that the bug is still active. His twitter alias is @cultiv
When is order conf sent in the order process?
Hey Guys :)
I just got home from vacation and our customer wrote a quite odd error, that im trying to figure out.
Its about the order confirmation mail, and when its being sent out.
We have setup so that everytime an order is placed our customer recieves a copy of the order confirmation, that their customer gets.(standard setup in my head)
This weekend some(not all the mails that they received failed) of the order confirmation mails that our customer got throws an XSLT error :
But when we log in to teacommerce and just clicks the order and resends the order confirmation its working fine. So in my head the XSLT is parsing just fine since its the same XSLT file thats being used. But my theory was that the mail would be sent out to early in the process ?
Or do you have any other ideas ? :)
its running teacommerce 1.4.3.1
Hi Rasmus,
That confirmation mail is sent just after the order have been finalized. That means after the payment have been confirmed.
It's the first time I have seen that error and don't think Tea Commerce could create it on itself. Do you have some custom code running that might be messing around with the order?
/Rune
Hey Rune
Hmm okay. No so far its pretty straight forward order flow, we have no special code in the flow. The order/payment is going through and we resend it, it just works which is the wierdest thing.
So far i havnt been able to force the bug myself.
Hi Rasmus and Rune,
I have also seen this error It happens once or twice a week in the shop where I am having problems. I did spend some time trying to figure out what was wrong and found this forum post, which seems to describe the same behaviour. I tried to upgrade the installation to 4.7.2, hoping the patch mentioned in the post made it into that release, but I still get this error.
Since codeplex was cleaned up I couldn't find the patch, maybe I should check the new issuetracker to see if it was migrated.
/Carsten
Found the issue on the new tracker http://issues.umbraco.org/issue/U4-552
Do is your umbraco installation also post 4.7.1?
Yea its actually same as yours 4.7.2
I have just bumped the Issue. is there anything else we can do to get it higher up in line, but dunno how much they watch stuff like this.
Great you found what cause the issue! I think that Umbraco watch the issue tracker all the time. If you want to you can write Sebaastian at twitter and let him know that the bug is still active. His twitter alias is @cultiv
Kind regards
Anders
I usually tweet the link out there and try to get others to bumb it as well.
/Rune
just posted a tweet for Seb asking about this case.
There has been posted a patch for this issue and will MAYBE make it into 4.11 based on a quick tweet conversation with Seb (@cultiv)
Sweet Rasmus!
Please tell if any of you can get it to build for a 4.7.2 since im new to the whole building of the umbraco project
http://issues.umbraco.org/issue/U4-552
is working on a reply...