Comments on: $name in your Sitecore content

By: Hishaam Namooya

Hishaam Namooya — Tue, 08 Mar 2016 08:17:37 +0000

Hi there,

I’ve also experienced this issue where all our contents were displaying $name. The root cause is as follow:

1. The item does not have a version.
2. Template is version in other language.
3. Invarient Language is present in the Language list.

Thanks

By: boro

boro — Tue, 27 Mar 2012 19:53:16 +0000

In reply to John West. Cheers for the feedback! You are correct, there are other tokens which this wouldn't catch. In previous projects I've never needed to use any tokens apart from $name. To catch all, the expandInitialFieldValue pipeline or the MasterVariablesReplacer would be better option. I don't think you could end up with $name in the name of an item after template inheritance is changed. The reason being an items name isn't related to data stored in its template or __standard values, instead it's setup when an item is created. Fields differ since they can be added to an item over time. Please correct me if I'm wrong!!!! :)

By: John West

John West — Mon, 12 Mar 2012 17:20:53 +0000

Thanks for the post. I didn’t check the code very closely, but couldn’t other tokens than $name appear, such as $id? Couldn’t $name appear in the middle of the field? Is there any chance that $name could appear in item names (such as those created from branch templates), or only in field values? I wonder if you could use the class specified by the MasterVariablesReplacer setting in the web.config file, maybe through the Sitecore.Configuration.Factory.GetMasterVariablesReplacer() method, to handle more cases with less code.