I'm using Forms 4.1.4 with Umbraco 7.2.8, in a webfarm.
As the form definitions are now stored as JSON files in \App_Plugins\UmbracoForms\Data\forms, I have set up file replication for this directory, to copy from my primary CMS server to the other servers in the webfarm, the same as I already have for \media.
But I also have to get the other servers in the webfarm to notice changes to the JSON files when I edit a form. If I do nothing, the other servers continue to serve the old version of the form.
I have found that one way to resolve this is by re-publishing the content node where the form is used, but this has an annoying side-effect that I have reported here: http://issues.umbraco.org/issue/CON-861
So my question: Is there some other correct way to prompt all servers in a webfarm to pick up changes to a form?
In my case, setting
<setting key="DisableFormCaching" value="True" />
on all servers does work, and I no longer need to publish something for form changes to show up on all servers.
Correct way to publish form changes to a webfarm?
I'm using Forms 4.1.4 with Umbraco 7.2.8, in a webfarm.
As the form definitions are now stored as JSON files in \App_Plugins\UmbracoForms\Data\forms, I have set up file replication for this directory, to copy from my primary CMS server to the other servers in the webfarm, the same as I already have for \media.
But I also have to get the other servers in the webfarm to notice changes to the JSON files when I edit a form. If I do nothing, the other servers continue to serve the old version of the form.
I have found that one way to resolve this is by re-publishing the content node where the form is used, but this has an annoying side-effect that I have reported here: http://issues.umbraco.org/issue/CON-861
So my question: Is there some other correct way to prompt all servers in a webfarm to pick up changes to a form?
Thanks
Ok I found this discussed elsewhere: https://our.umbraco.org/forum/umbraco-pro/contour/69489-best-practice-usage-usage-of-umbraco-forms-on-load-balanced-environment
In my case, setting
<setting key="DisableFormCaching" value="True" />on all servers does work, and I no longer need to publish something for form changes to show up on all servers.is working on a reply...