The Item1422 fix to allow nested evaluation of NOP{} has been reverted. This breaks now registrations: They contain text within NOP{}. For example, in test registration Main.FooBar2, the administrator note and text below should not be carried over into the user topic.

Possible workaround is to avoid MAKETEXT and to move the part between NOP{} to a document topic.

-- PTh

---

The alternative is to deprecate the overloaded NOP syntax in favour of a better solution. For example,

<templateonly>
....
</templateonly>

which is not only consistent with other TML block tags (such as verbatim and noautolink), it is also more intention-revealing.

CC

I like the sound of CCs suggestion for templates - a mild deprecation will help clean the parser as well, later on.

-- SP

I think the templateonly tag is OK. We are so short before release, is it safe to change the code for this? For Dakar it might be better to externalize the NOP{} with MAKETEXT into the docs.

If the templateonly tag gets implemented we should follow the TWiki:Codev.ProcessToDocUndocumentedStuff process to deprecate NOP{}.

-- PTh

Actualy I think <templateonly> is pretty safe, but in the interests of minimising changes before the release, I suggest we defer that until Edinburgh and fix the NOP usage in the new user template.

Can someone do that please? Get the NewUserTemplate working properly?

CC

After reviewing the template, that's bloody hard to do. Also, the XML-like tag is not a good idea for various complex reasons. So I added:

%TEMPLATEONLY% ... %ENDTEMPLATEONLY% (c.f. SECTION..ENDSECTION). The %TEMPLATEONLY% appears as normal in the template topic when viewed, but when the topic is used to create a new topic, it is removed.

SVN 8402

CC