Just to clarify, the "idea of [your] own and FrD's suggestion" just did not 

I was relay smart because I decided to use a subtiddler such as 
task/template to indicate it was a template tiddler so task no longer held 
the removeme field and would not be cloned. This is a good idea but 
somewhere I decided this was a useful tip for creating templates for 
subTiddlers, and I returned it the above method only to be reminded it does 
not work again.

I am using the following to clone tiddlers I am using as templates;

<$button message="tm-new-tiddler" param=<<currentTiddler>> tooltip="Clone 
this 'template'" aria-label="Clone this 'template'" class=<
<tv-config-toolbar-class>> >
<$action-setfield $field=template-source $value=<<currentTiddler>>/>

So to restate the problem

*This works nicely except I have to remove a field from the new Tiddler eg 
*<$action-deletefield $field=removeme/>*

*Unfortunately if I use this in the above tiddler it removes the field from 
the source tiddler before the cloning.*

As Mark suggested I may need resort to the ActionCreateTiddler so a Final 
call to see if anyone knows a workaround or has build a clone tool using 


On Friday, 3 August 2018 12:46:30 UTC+10, TonyM wrote:
> Folks/Team,
> I am creating a tool to create tiddlers from template tiddlers and will 
> share today (if I resolve this).
> However to do so I am using the following to clone the tiddler to a new 
> tiddler name eg "task 1" and open for edit (which the user then modifies)
> \whitespace trim
> <$button message="tm-new-tiddler" param=<<currentTiddler>> tooltip="Clone 
> this 'template'" aria-label="Clone this 'template'" class=<<tv-config-
> toolbar-class>> >
> <$action-setfield $field=template-source $value=<<currentTiddler>>/>
> *<$action-deletefield $field=tiddler-template-caption/**>*
> {{$:/core/images/clone-button}}
> </$button>
>    - I identify which tiddlers are templates by the existence of the 
>    field *tiddler-template-caption*
>    - During the clone which works perfectly the tiddler-template-caption also 
>    gets cloned
>    - Unfortunately this means the new tiddlers now appear in the list of 
>    tiddler templates
>    - In the above code *<$action-deletefield 
>    $field=tiddler-template-caption/*> deletes the field from the template 
>    tiddler not the new one.
>    - How can I delete this field from the new tiddler with the yet to be 
>    determined name?
> I believe I need to use message="tm-new-tiddler" param=<<currentTiddler>> 
> rather than ActionCreateTiddlerWidget to clone the tiddler, where I would 
> use the $savetitle.
> I want the clone to work regardless of the fields and their content so I 
> do not want to explicitly create the fields, I just want them to come from 
> the template tiddler except for *tiddler-template-caption.*
> Note: <$action-setfield $field=template-source 
> $value=<<currentTiddler>>/> updates the template tiddler before the clone, 
> this saves the user doing it.
> How can I trigger *<$action-deletefield $field=tiddler-template-caption/**> 
> on the new tiddler after it is named/created without an additional 
> "trigger"*
> Thanks
> Tony

You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
To post to this group, send email to
Visit this group at
To view this discussion on the web visit
For more options, visit

Reply via email to