we have a problem with Courier deployment.
On content page we have a macro which has a reference to another node and collects childrens Title, Text and show them in an accordian. When editor changes one of the childrens property and deploys it with Courier, nothing happens in frontend. In Backend the updated node is shown.
Since the backend have shows the updated node, but not the front-end, then it sounds to me that the XML file in /App_Data/umbraco.config is not updated with the latest XML. Did you save and publish the node with the new value?
If not, then try publish the node or nodes, and see if the front-end is updated with the new values.
We tested almost everything, but nothing worked.
We published node on Staging, then deployed with Courier and for testing published node on Production again. But this didnt work.
At least we did a recycle of Application Pool and the Content was displayed correct.
We dont want to recycle AppPool everytime.
Sounds like Umbraco is not notified to clear its internal cache. So based on past issues, this is either because you use an outdated version of courier that doesn't know it is supposed to tell umbraco about the cache invalidation, or there is a missing dll
So what version of umbraco and courier are you using? and does your bin contain a umbraco.courier.eventhandlers.dll file?
after a bit research I found some strange behavior in deployment with courier.
We have about 6 Websites in one Umbraco instance. Everything is great with the first Website in this instance. We can deploy with Courier and the changes occur on the live Website.
But when we want to deploy other Websites in this instance, we have to do app recycle. Only after this recycle, changes occur on live Websites.
Can anybody explain this behavior?
Courier deployment Cache problem
Hi everyone,
we have a problem with Courier deployment. On content page we have a macro which has a reference to another node and collects children
s Title, Text and show them in an accordian. When editor changes one of the childrens property and deploys it with Courier, nothing happens in frontend. In Backend the updated node is shown.This are entries of CourierTraceLog:
Umbraco Version: 7.2.4 Courier Version: 2.50.1 , also tested with 2.51.2
Hi Heiko,
Since the backend have shows the updated node, but not the front-end, then it sounds to me that the XML file in /App_Data/umbraco.config is not updated with the latest XML. Did you save and publish the node with the new value?
If not, then try publish the node or nodes, and see if the front-end is updated with the new values.
/Dennis
Hi Dennis,
thank you for your reply.
We tested almost everything, but nothing worked. We published node on Staging, then deployed with Courier and for testing published node on Production again. But this didn
t work. At least we did a recycle of Application Pool and the Content was displayed correct. We dont want to recycle AppPool everytime.Heiko
Hi Heiko,
Okay, next question did some of your macros have cache turn on, so that why you are seen old content, until you are recycle the app pool?.
If you have added cache to this macro, could you try switch it off temporarily, so we can see if this the problem.
/Dennis
Hi Dennis,
we have no macro Cache turned on. Any other ideas?
Heiko
Hi heiko
Sounds like Umbraco is not notified to clear its internal cache. So based on past issues, this is either because you use an outdated version of courier that doesn't know it is supposed to tell umbraco about the cache invalidation, or there is a missing dll
So what version of umbraco and courier are you using? and does your bin contain a umbraco.courier.eventhandlers.dll file?
Hi Per,
we use Umbraco 7.2.4. Since last week we use Courier 2.51.2, before 2.50.1. We hoped that the Problem disappear with updating to the newest Version.
/Heiko
Hi everybody,
after a bit research I found some strange behavior in deployment with courier. We have about 6 Websites in one Umbraco instance. Everything is great with the first Website in this instance. We can deploy with Courier and the changes occur on the live Website. But when we want to deploy other Websites in this instance, we have to do app recycle. Only after this recycle, changes occur on live Websites. Can anybody explain this behavior?
/Heiko
@Heiko
I've asked Byte5 to provide details on the support ticket they opened for this and we will update here once the cause and/or solution is known.
is working on a reply...