TranslatorReader doesn't identify the end of the plugin markup correctly if there's another plugin nested within its body. I don't think this would come up with any of the existing plugins - but any wiki markup should be allowed in a plugin body, even other plugins.

I have attached a patch which works for us.

--DaveSB

Well, nested plugins have never been supported (or recommended), so this is not really a bug, but a feature request :-)

-- JanneJalkanen

Well, I vote for this one then :-)
I'm actually running against this limit with the Form Plugin.
I want to create pages with some plugins already defined (Query Plugin for example).

--MP

....and there's nothing to stop users from trying to nest plugins - even if it isn't recommended. I guess the real "bug" isn't so much that nested plugins aren't possible (although that's the only time this comes up) - just that the parser doesn't delimit the plugin text quite right if there's an extra }] in the plugin body. I have a niggling worry that nested plugins would ultimately lead to a ReallyComplexWiki whose content looks more like code than plain text, which goes against the whole wiki concept, but at the moment it seems like a good change.

-- DaveSB

related IdeaSupportNestedPluginsInsideTheBodyOfAPlugin

Implemented in 2.3.44