This issue was supposedly fixed in the latest release was not. The following code produces the literal string “{my_custom_field}” instead of the value for the actual custom field. The custom field is spelled correctly and exists because the loop prints that string, instead of “not here”.
{exp:channel:categories style="linear"}
{if my_custom_field}
{my_custom_field}
{if:else}
not here
{/if}
{/exp:channel:categories}ExpressionEngine implements Markdown Extra and BBCode. Please see the Markdown Extra docs and the BBCode Wikipedia article for a full reference.
**bold**, __bold__, *italics*, _italics_, ~strike/del~, `code()`
bold, italics, strike/del, code()
Link: [link title](https://example.com)
Image: 
[blockquote]...[/blockquote], [quote]...[/quote], and Markdown style:
> Some quoted text. > > This is all one quote.
[code]...[/code], and you can also specify the language for syntax highlighting, [code=php]...[/code]
GitHub flavored Markdown code fences are also supported:
```
public function decoderRing($str)
{
return str_rot13($str);
}
```