Version: 2.1.3 Reporter: Blue State Digital —
This is an archived bug report. If you are experiencing a similar issue, upgrade to the latest release and if that does not solve the problem, submit a new bug report
In mod.channel.php there is a section where the parsing is prefaced by
// This hurts soo much. Using custom fields as pair and single vars in the same
// channel tags could lead to something like this: {field}...{field}inner{/field}
// There’s no efficient regex to match this case, so we’ll find the last nested
// opening tag and re-cut the chunk.
We found an issue where it was not recognizing the following patter, which is slightly different than noted:
{test}{test_a}{/test}
Where the child tag is a substring of the parent tag. The output is
{test_a}{/test}
We worked around the problem by making sure that the inner tag names (this is using the Matrix plugin) doe not include the name of the Matrix field in them.
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);
}
```