No answer? I'm having same issue right now for a contact form, I rather not have the editor type label field each time?
I'm guessing the backoffice language is not the same thing as the frontend language?
Just came across this problem as well, it's actually the same issue you get using WebAPI where it loses the current culture and therefore the dictionary doesn't know which language to return.
It should probably be added to the core files, but for now adding this should work as long as the your top level node has a culture set:
if (!Lecoati.LeBlender.Extension.Helper.IsFrontEnd())
{
var cultureAlias = umbraco.cms.businesslogic.web.Domain.GetDomainsById(Helper.GetCurrentContent().AncestorOrSelf(1).Id)[0].Language.CultureAlias;
Thread.CurrentThread.CurrentCulture = new System.Globalization.CultureInfo(cultureAlias);
Thread.CurrentThread.CurrentUICulture = new System.Globalization.CultureInfo(cultureAlias);
}
Render in grid is not rendering Umbraco dictionary items
It seems that "Render in grid" is not rendering Umbraco dictionary items.
If I go like this:
It won't render in the grid, but it does so, on the frontend.
No answer? I'm having same issue right now for a contact form, I rather not have the editor type label field each time? I'm guessing the backoffice language is not the same thing as the frontend language?
Just came across this problem as well, it's actually the same issue you get using WebAPI where it loses the current culture and therefore the dictionary doesn't know which language to return.
It should probably be added to the core files, but for now adding this should work as long as the your top level node has a culture set:
is working on a reply...