U4-4851 - Umbraco.Field("pageName") Broken in 6.2.0 with inbuilt fields

Created by Dan Booth 09 May 2014, 11:13:07 Updated by Stephan 12 May 2014, 10:59:09

In an MVC view in 6.2.0 if I call:


Then nothing is rendered. In versions prior to 6.2.0 then this would render the page name eg. Model.Content.Name

Custom properties still do render, so @Umbraco.Field("bodyText") still works, as before.

What is weird is that the overload where you can pass in an alternate field alias does work eg.

@Umbraco.Field("heading", "pageName")

This works! So if "heading" has a value it will render the contents of heading, but if heading doesn't exist then it will render the page name. In fact, this works fine too:

@Umbraco.Field("pageName", "pageName")

So something weird is going on...


Bfi 09 May 2014, 11:39:44

I can confirm this issue in 6.2.0

Shannon Deminick 12 May 2014, 03:52:40

pretty sure this is resolved in this rev: 4e5019d5af2f0785e95fd1bc885e62da2e2c2448

@zpqrtbnk ?

Stephan 12 May 2014, 10:59:09

Yes it's fixed now (was fixed in 7 in fact, not in 6), could not close the issue because YouTried looked down from here.

Priority: Major

Type: Bug

State: Fixed

Assignee: Shannon Deminick

Difficulty: Normal

Category: Architecture

Backwards Compatible: True

Fix Submitted:

Affected versions: 6.2.0

Due in version: 6.2.1


Story Points: