I believe something has changed in version 2.4.9 in regard to syncing of templates. I normally use uSync just to create the DB part of the template and on first sync it has created the .cshtml file based on the uSync .config file.
After upgrading to 2.4.9 it seems like this behaviour has changed. Now the .cshtml files seems to be overwritten by the .config content on every app pool start.
Did something change that I am not aware of, or is this a bug in 2.4.9?
this has been a change in the way changes are detected between on disk and umbraco elements, and i think this is what is causing the import to now fire every time. (fix for that coming soon).
but as you say template imports use to only create the cshtml files first time, and nothing has changed in uSync around that, so i will go look and see if i can find where that is happening.
there are a couple of template things that mean it is likely that I will be removing uSync's use of the umbraco packaging service for template imports, then we can get this fixed better.
template changes are only made when something actually changes (name or master)
the file on the disk always wins (if it is there). this is true for creates as well as updates
So if the .cshtml or .master file exists then the content from that is used over any inside the .config file (the .config file still needs something in the design bit, because that is how mvc/forms detection works)
Changed behaviour of templates in 2.4.9?
Hi,
I believe something has changed in version 2.4.9 in regard to syncing of templates. I normally use uSync just to create the DB part of the template and on first sync it has created the .cshtml file based on the uSync .config file.
After upgrading to 2.4.9 it seems like this behaviour has changed. Now the .cshtml files seems to be overwritten by the .config content on every app pool start.
Did something change that I am not aware of, or is this a bug in 2.4.9?
Carsten
this has been a change in the way changes are detected between on disk and umbraco elements, and i think this is what is causing the import to now fire every time. (fix for that coming soon).
but as you say template imports use to only create the cshtml files first time, and nothing has changed in uSync around that, so i will go look and see if i can find where that is happening.
there are a couple of template things that mean it is likely that I will be removing uSync's use of the umbraco packaging service for template imports, then we can get this fixed better.
Hi,
v2.4.10 - fixes this for you.
two issues fixed -
So if the .cshtml or .master file exists then the content from that is used over any inside the .config file (the .config file still needs something in the design bit, because that is how mvc/forms detection works)
Hi Kevin,
Thank you for the fantastic support!!!
I have tried out the latest NuGet version and it seems to work very well.
Carsten
is working on a reply...