You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Which Umbraco version are you using? (Please write the exact version, example: 10.1.0)
14.3.1; 15.0.0
Bug summary
Inserting a Partial View in a template results in "An unhandled exception" when visiting the view of the published page, caused by a wrongly formatted Partial View name.
Specifics
When a Partial View with the name Empty.cshtml is selected for insertion in a template, @await Html.PartialAsync("%2FEmpty%25dot%25cshtml") line is being added to the template which doesn't work. Instead, the Partial View name should be formatted correctly, like @await Html.PartialAsync("Empty")
Steps to reproduce
In the Settings section, create a Partial View from any snippet and give it a name of your choice;
Create a content type with template;
Visit the template and insert the Partial View you just created;
Create and publish a content node from that content type;
In the Info tab of the content node, access the link.
Expected result / actual result
Expected: The partial view to be rendered correctly;
Actual:
The text was updated successfully, but these errors were encountered:
Which Umbraco version are you using? (Please write the exact version, example: 10.1.0)
14.3.1; 15.0.0
Bug summary
Inserting a Partial View in a template results in "An unhandled exception" when visiting the view of the published page, caused by a wrongly formatted Partial View name.
Specifics
When a Partial View with the name
Empty.cshtml
is selected for insertion in a template,@await Html.PartialAsync("%2FEmpty%25dot%25cshtml")
line is being added to the template which doesn't work. Instead, the Partial View name should be formatted correctly, like@await Html.PartialAsync("Empty")
Steps to reproduce
Expected result / actual result
Expected: The partial view to be rendered correctly;
Actual:
The text was updated successfully, but these errors were encountered: