Liquid web app custom field tag bug.
If you have a web app custom field named "Intro Text" and you try to render it there is an issue.
{{this}} on a web app item list will reveal the target data for the web app. For this custom field the name is as follows and gives the following:
[Intro Text, Eu mei lorem probatus. Diceret molestiae at sed. Ne pro erant quando quodsi, vim affert blandit ullamcorper at. Ad impedit facilis pro. Nullam phaedrum per cu, possim discere recteque ad sit.]
Another Custom field is as follows:
[Image, <a href="/news/ad-impedit-facilis"><img border="0" alt="" src="/burgundy_01.jpg"></a>]
[Image_nolink, <img border="0" alt="" src="/burgundy_01.jpg">]
[Image_value, /burgundy_01.jpg]
To get the image you can do the following:
{{this.image}}
{{this.Image}}
{{this.Image_nolink}}
{{this.Image_value}}
These all render.
BUT
If you do:
{{this.Intro Text}} Or {{this.intro text}} or {{this.intro_text}}
None of these will render.
Issue with current liquid render:
One thing with the current liquid data render for web apps is that it is basically a carbon copy of the tags currently. If this is staying as is it would be a bit of a shame as I hoped we would have direct access to data a bit more.
For a custom data field it renders:
[Author_id, 4815023]
[Author, <a href="/staff/john-smith">John Smith</a>]
I was hoping that these would be true objects so you could be doing..
{{this,author.id}} and {{this.author.text}} and {{this.author.url}}
And for an image:
{{this.customimage.value}}
Will this not be something that is happening with the liquid rendering engine from BC?