Umbraco 13 - 17 Upgrade No Physical Template was found

[MattGitUmbraco]

I have tried following the guide here: Version Specific Upgrades | CMS | Umbraco Documentation

But it seems that each different ModelsMode I try the error “No Physical Template was found” is generated.

The code for the project is old v7 code (written by a former colleague) upgraded to v13 (by a third party) and now I am trying to get this to run on v17. Does anyone have any suggestions?

[sebastiaan (Sebastiaan Janssen ⚓)]

I’d suggest to start with this thread

Upgrading to V17.0.0 No physical template file was found for template

ensure the following settings are removed from your .csproj file: <RazorCompileOnBuild>false</RazorCompileOnBuild> <RazorCompileOnPublish>false</RazorCompileOnPublish> From: Version Specific Upgrades | Umbraco CMS So in short: Models Builder mode Install Umbraco.Cms.DevelopmentMode.Backoffice Remove <RazorCompileOnBuild> & <RazorCompileOnPublish> InMemoryAuto Yes No Source-code modes (SourceCodeAuto, SourceCodeManual, AppData) No Yes

[MattGitUmbraco]

Thanks for the reply. I have it set to SourceCodeAuto and have removed the two RazorCompile settings from the .csproj file, but I still get the same error, it may be another setting is causing a problem somewhere.

[jacob (Jacob Overgaard 🚀)]

Make sure to go to Settings → Models Builder → and click “Generate models” after changing the models mode. After that, make sure you restart the server, and it should now work.

If it still does not work, please try to re-select the template for a document and hit “Save and publish”.

Hope that helps.

[MattGitUmbraco]

Thanks, I have tried generating the models a few times from settings, and restarting the PC and Visual Studio but I am still getting the same error. I have also saved and published the website and re-saved the template files but no change in error message.

[jacob (Jacob Overgaard 🚀)]

Could it be a case-sensitive issue with the file names? Do they exist in the correct folder (/Views)? They must match the template alias in the file name as well.

If you create a brand new template (Settings → Templates –> New) and assign that to a document type and a document, does that work?

[wpowell97 (Will Powell)]

1. Check that the physical .cshtml template files actually exist in the /Views folder.
   Umbraco needs a file on disk for the template — it won’t render just because the template is in the back office.
2. Ensure the file name exactly matches the template alias (including letter case).
   On case-sensitive systems (e.g., Linux / Docker), Home.cshtml and home.cshtml are not the same.
3. Try creating a brand-new template in the back office, assign it to a doc type and a content node, and see if that renders correctly.
   If a new template works, that usually confirms the issue is with the original template files (path/name mismatch).

[MattGitUmbraco]

Thanks. I have created a new Doc Type and template called Basic, have created a new node and tried saving and publishing (and previewing) but still get the error, I am on Windows 11 so I don’t believe the issue is due to case sensitivity.

[jacob (Jacob Overgaard 🚀)]

You could try and install the Umbraco.Cms.DevelopmentMode.Backoffice package, which ordinarily should not be necessary, but I’m not sure in which state your Razor compilation is in at the moment.

Someone had luck fixing the problem that way:

Page Not Found after upgrading from 16.1.1 to 17.1.0

I read some other threads here at the Forum where several people gave me the advice to install Umbraco.Cms.DevelopmentMode.Backofficeand so I did. It now works and I can reach all the pages, but will this also work in production when I deploy the upgrade of Umbraco 17? Or is this package just solving my issue when I’m working locally in development environment?