U4-10269 - Partial View endless loop - possible feature

Created by tim 08 Aug 2017, 12:47:55 Updated by tim 08 Aug 2017, 18:47:36

What did you do? created a partial view that referenced itself by accident. I had written the partial view and included it in the homepage to check it worked. I then copied the div it was in from the homepage as I wanted the layout it was sitting in for the partial view and I forgot to remove the reference to the partial. Saved the view and deleted the div from the homepage and put my reference instead (@Html.Partial("foo");.So now...it gets called from the homepage, but the voiew still had my original test @Html.Partial("foo") in it.

What did you expect to happen? The page to load with my partial displayed

What actually happened? It crashed the app pool, with no other errors being found in the logs, after checking the eventlog (on the server) this took me off down a terrible route of changing the app pool to allow 32bit and followed by a bunch of other errors.

So my suggestion would be, could the umbraco admin check for stupid human errors like this when the view is saved? (I know I'm a tool, but thought I'd ask anyway) Thanks tim

Comments

Priority: Normal

Type: Feature (request)

State: Submitted

Assignee:

Difficulty: Normal

Category:

Backwards Compatible: True

Fix Submitted:

Affected versions: 7.5.6

Due in version:

Sprint:

Story Points:

Cycle: