Hi

usync calls the Template.Import function (which is the 'old' api) - I will look and see if there are ways in which that differentiates between views and master but I think it's in the core.

the next version of usync v2.2 (ready for when v7.1 is released :) ) uses the new API packagingService.ImportTemplate() - so hopefully that will be fine, but there where issues with that in 7.0.4 so I won't be able to port it back.

ah awesome, v7.1 is but moments away!

actually looking at Template.Import in v7.0.4 that uses packageingService.ImportTemplate() so i will have to work out if that is causing the problem :(

usync does other stuff but it doesn't physically create the template files. I don't know if there is some trigger in the background creating the master pages..

looking at https://github.com/umbraco/Umbraco-CMS/blob/7.1.0/src/Umbraco.Core/Services/PackagingService.cs

umbraco checks if the page is a master page by looking for the following

return Regex.IsMatch(code, @"<%@\s*Master", RegexOptions.IgnoreCase) ||
                code.InvariantContains("<umbraco:Item") || code.InvariantContains("<asp:") || code.InvariantContains("<umbraco:Macro");

do your views contain any of that ?

if they do then the IsMasterPageSyntax() function in the importer returns true, and the files are saved to the MasterPagePath which is suspect is the masterpages folder.

Ah ha, yes, this is the issue:

Layout = "SiteMasterView.cshtml";

Actually, on second look that regex is smarter than just looking for "Master"

is working on a reply...