We have an Umbraco 7.2.8 site with Courier 2.50.1 and UmbracoForms 4.1.4 installed.
I am able to successfully Courier new UmbracoForm forms. They show up on the destination site. When I update the forms, I am still able to courier them successfully, but I can't see the changes to the forms on the front end or in the backoffice of the destination site until I recycle the app pool. It appears that they are cached. Does anyone know of a way to configure things so that I don't have to recycle the app pool to get my forms changes after every deploy? Any neat tricks for refreshing the cache without having to recycle the app pool?
Forms are kept in /appplugins/ so even though courier can be used to transfer the files it is the Asp.Net runtime that has the /appplugins/ cached at app startup. At this point courier does not have the ability to force an app restart - which is the only way to initiate the resolvers to re-scan /app_plugins/.
Got it. Thanks, Paul. That's what I was suspecting. I just wanted to hear it from someone with more certainty. I think we'll be ok. We aren't making forms changes every day, and being able to Courier them in the first place is a step up from where we were before.
Old UmbracoForms cached after Courier deploy
We have an Umbraco 7.2.8 site with Courier 2.50.1 and UmbracoForms 4.1.4 installed.
I am able to successfully Courier new UmbracoForm forms. They show up on the destination site. When I update the forms, I am still able to courier them successfully, but I can't see the changes to the forms on the front end or in the backoffice of the destination site until I recycle the app pool. It appears that they are cached. Does anyone know of a way to configure things so that I don't have to recycle the app pool to get my forms changes after every deploy? Any neat tricks for refreshing the cache without having to recycle the app pool?
This looks like a similar problem to ours, but I'm not sure that it is the same. Courier Deployment Cache Problem
Thanks
@Mark
Forms are kept in /appplugins/ so even though courier can be used to transfer the files it is the Asp.Net runtime that has the /appplugins/ cached at app startup. At this point courier does not have the ability to force an app restart - which is the only way to initiate the resolvers to re-scan /app_plugins/.
Got it. Thanks, Paul. That's what I was suspecting. I just wanted to hear it from someone with more certainty. I think we'll be ok. We aren't making forms changes every day, and being able to Courier them in the first place is a step up from where we were before.
is working on a reply...