TitleTranslatorReader doesn't allow nested plugins
Date27-Oct-2005 19:46:17 EEST

Version2.2.33
SubmitterDaveSB
Bug criticalityEnhancementRequest
Browser versionFirefox 1.0.7
Bug statusClosedBug
PageProvider used
Servlet ContainerTomcat 5.0.25
Operating SystemWindows XP/Linux
URL
Java version1.4.2_04-b05

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

Add new attachment

Only authorized users are allowed to upload new attachments.

List of attachments

Kind Attachment Name Size Version Date Modified Author Change note
txt
TranslatorReader-patch.txt 1.2 kB 1 27-Oct-2005 19:47 DaveSB
« This page (revision-10) was last changed on 19-Jul-2007 02:27 by David Au