RenderField pipeline only called in editing mode

Hi Mike,

I have a Rich Text field on my page, where I add some additional markup for links in the renderField pipeline (e.g. adding always target_"blank" to some links). In my Razor view I added the field with an @Editable():

@Editable(m => m.Text)

This works as expected in editing mode, but not when I’m not in editing mode. In the GlassHtml class I saw, that the renderField pipeline in only called in editing mode (see here). Why don’t you call the pipeline when not in editing mode? Is there a solution/workaround I can still use the pipeline when I’m not in editing mode?

Thanks for looking into it and regards, Kevin

[mikeedwards83]

I think we added the field setting SitecoreFieldSettings.ForceRenderField which forces a string field to use the renderfield pipeline.

[cardinal252]

Ok, so … What is the goal in manipulating the RenderField pipeline?

If it is to add markup (say for example) token processing to the output (which sounds like what you are doing) then you can simply either override GlassHtml or the field mapper to do the same thing whilst not losing the performance gain that avoiding the renderfield pipeline affords. Glass by design skips this pipeline to be faster, and in certain scenarios can actually render Sitecore content faster than Sitecore can. The choice between overriding GlassHtml and the field mapper largely depends on whether you would want the same replacements to be made in non-presentation scenarios - modifying GlassHtml would usually only modify output at a view level for like @Html.Glass().Editable()

The only time this generally causes a problem is if you are mixing glass and non-glass presentation (into which you may require explicitly calling the render field pipeline). Otherwise, you are simply modifying the wrong code to achieve what you need.

Hope this helps 😄