For many years we were running Contour 3.0x on Umbraco 4.10.11. Our Contour forms are fairly straightforward, not particularly large, and ran fine under on 4.10.11. Almost all our forms write fields out to the Umbraco back end which is one of the strong features in the package.
About six months ago, we upgraded to Umbraco 6.26. We also updated our server environment to from WS 2008 to Windows Server 2016.
Since we upgraded to 6.26, the performance of Contour has suffered in several ways. First is the speed. We have some forms that only write two fields out (Save as Umbraco Document). Previously on Umbraco 4.10.11, A, these forms would post in about 10 seconds after pressing submit and then return a new screen where there user could enter another form. This process now takes up to a full minute. This is a dramatic slowdown and renders the process nearly useless because users are abandoning the form.
The second issue is that on every other keypress of the Submit button, all of the fields are emptied of data, and the user is presented with the screen below, empty fields with a pink backdrop and an error message generated the field is mandatory even though it had been filled out. Essentially the user must enter the data twice, and lose all his/her data on the first pass.
Can anyone offer a suggestion on how we might investigate this.
Umbraco Contour 3.0.31 Anomalies and Slowdowns
For many years we were running Contour 3.0x on Umbraco 4.10.11. Our Contour forms are fairly straightforward, not particularly large, and ran fine under on 4.10.11. Almost all our forms write fields out to the Umbraco back end which is one of the strong features in the package.
About six months ago, we upgraded to Umbraco 6.26. We also updated our server environment to from WS 2008 to Windows Server 2016.
Since we upgraded to 6.26, the performance of Contour has suffered in several ways. First is the speed. We have some forms that only write two fields out (Save as Umbraco Document). Previously on Umbraco 4.10.11, A, these forms would post in about 10 seconds after pressing submit and then return a new screen where there user could enter another form. This process now takes up to a full minute. This is a dramatic slowdown and renders the process nearly useless because users are abandoning the form.
The second issue is that on every other keypress of the Submit button, all of the fields are emptied of data, and the user is presented with the screen below, empty fields with a pink backdrop and an error message generated the field is mandatory even though it had been filled out. Essentially the user must enter the data twice, and lose all his/her data on the first pass.
Can anyone offer a suggestion on how we might investigate this.
is working on a reply...