@Charlie_Veniot the date format is very flexible so the following will do the job
{{{ [<now YYYY0MM>]}}} but for readability we can also to this {{{ [<now YYYY-0MM>] }}} when a set of characters does not get replaced eg YYYY with 2023 it just gets included as a literal as in the -. In these examples there is no spaces in the now parameter.
This means the date format is a good place to concatinate strings around a date format of any kind.
The forum is not about “who knows what” but what the community knows and can share. Others will come to this topic after a search or reading the title and if they find relavant and related info all the better. I think we should avoid censoring ourselves or others in favor of supporting the comunity.
despite this it could be argued I presented an improved method. I addressed you because It was your solution I extended and thought you may appreciate it.
there was nothing to indicate you knew what I shared, in fact to the contrary, and I am not a mind reader.
Nah, I didn’t appreciate. Total distraction from the help Stefan was looking for. Part and parcel of the things I don’t like about this forum: lack of OP focus.
Stefan’s filter in the OP was good enough. It did not need fixing. Sometimes, it is good to leave things well enough alone.
Now if you had looked upon the thread and decided: I’m going write a “wiki” article (wiki article: rofl) about “now”, that would have been very cool. Something deserving of a full blown discussion in a dedicated thread.
Sometimes, less is more. Like sticking to the problem/question in the OP without clutter.
With URLS and other cases you may want to use the encodeuri[] operator to convert illegal characters eg space to %20 or the reverse decodeuri[] but it is often unnecessary.
If the literal text portion of the <<now ...>> macro parameter contains any date formatting syntax (e.g., “dd”, “mm”, “am”, “pm”, etc.) then those characters will be substituted with their corresponding date/time values. Thus, if you were to use <<now 'MyTiddlers/YYYY 0MM'>>, “MyTiddlers” would be changed to something like “MyTi01lers” because of the “dd”.
Fortunately, the text portion of your specific example use-case doesn’t contain any date formatting syntax, so it works OK. However, if in the future you were to change that text, you might want to completely avoid this substitution issue by splitting the filtered tranclusion syntax into separate parts, so that the text portion is not included in the <now '...'> macro formatting parameter, like this: