Tony’s “journal template” solution is slightly out-of-date with the current TWCore implementation for $:/core/ui/Actions/new-journal
and $:/core/ui/Actions/new-journal-here
actions.
Specificially, the TWCore versions now use textFieldTags
(contents of $:/config/NewJournal/Tags
) as well as continuing to support the backwards-compatible use of tagsFieldTags
(contents of $:/config/NewJournal/Tags!!tags
.
However, the $:/ControlPanel setting for “Tags for new journal tiddlers” only sets the text field in $:/config/NewJournal/Tags
. As a consequence, if you are using a newer TWCore, there is no value stored in $:/config/NewJournal/Tags!!tags
.
The problem is that Tony’s journal actions don’t apply the tag that is stored in the $:/config/NewJournal/Tags
text field, leaving the resulting journal tiddler without any tag set.
Also note that Tony’s solution saves the date stamp in a field named journal-date
, while my TiddlyTools Calendar, which has a similarly enhanced journal creation handler uses a field named journaldate
(without the hyphen). We should coordinate both methods to use the same field name. Obviously, I prefer using the field name without the hyphen.
Another minor difference: the value Tony saves in the journal-date
field uses a date format of YYYY0MM0DD0hh0mm0ss000
(i.e., milliseconds is hard coded to “000”), while my TiddlyTools Calendar code uses YYYY0MM0DD0hh0mm0ss0XXX
(i.e., milliseconds is included as a zero-padded value).
@TW_Tones … could you please consider updating your “journal template” actions accordingly so that they match the TiddlyTools Calendar implementation?
-e