-
-
Save dannberg/9056b89437110e62766689772437fe46 to your computer and use it in GitHub Desktop.
| --- | |
| date: <% tp.file.creation_date() %> | |
| type: meeting | |
| company: | |
| summary: " " | |
| --- | |
| tags: [[🗣 Meetings MOC]] | |
| Date: [[<% tp.date.now("YYYY-MM-DD-dddd") %>]] | |
| <% await tp.file.rename(tp.date.now("YYYY-MM-DD") + " " + tp.file.title) %> | |
| # [[<% tp.date.now("YYYY-MM-DD") + " " + tp.file.title %>]] | |
| **Attendees**: | |
| - | |
| ## Agenda/Questions | |
| - | |
| ## Notes | |
| - |
@dannberg Somehow when I created the button for "new meeting", my meeting template got moved out from the template folder to the meeting folder in my timestamps. Is there anything I did not do or steps that I've missed as I just copied and paste your code.
@jasonchuasg Did you follow the instructions on my blog in order to create the button? Check out the section "Creating new meeting button (continued)" at the bottom. It sounds like it might be an issue with the button, rather than the template.
@jasonchuasg Did you follow the instructions on my blog in order to create the button? Check out the section "Creating new meeting button (continued)" at the bottom. It sounds like it might be an issue with the button, rather than the template.
I follow every step that was given. Tried a few more times, somehow, my meeting template got moved to the timestamps folder and the meeting template name was changed to the title of a new meeting that render the button useless.
@jasonchuasg It sounds like what's happening is that when you press the button, it's running the templater code on your template file, rather than making a new copy from the template and running templater code on that. I'm not sure at what step in that process it's happening, but make sure you're not expanding the templater code in the template file. The template file is only used to create new documents.
@jasonchuasg It sounds like what's happening is that when you press the button, it's running the templater code on your template file, rather than making a new copy from the template and running templater code on that. I'm not sure at what step in that process it's happening, but make sure you're not expanding the templater code in the template file. The template file is only used to create new documents.
How do I ensure that my Templater code did not get expanded in the template file?
It's impossible for me to tell without looking at your entire setup. But my guess based on what you're saying it that it's something that's happening with the button. Make sure you're using the button maker interface to make the button (not copy/pasting), the button is in a different note than the template (I use a Meetings MOC file), and that you're using the same settings I'm using in the screenshot in my blog post.
I'm planning to record a video at some point soon showing how I set everything up, too. So hopefully one of those can help you get it working.
I'm facing the same issue, even when I copy-paste your exact files. There must be something wrong with the settings. I'll keep looking. Thank you so much for sharing your templates and your workflow!
I'm facing the same issue, even when I copy-paste your exact files. There must be something wrong with the settings. I'll keep looking. Thank you so much for sharing your templates and your workflow!
It's an awesome workflow. I spent the wholeday trying to figure out the settings to make it right. If you manage to find the solution, please let me know!
@antoineallard @jasonchuasg Hm, I'm not sure why both of you are having issues. I just filmed a quick video to test making a new button, and it still works for me. Is this the same as what you two are doing? https://youtu.be/YeyARTXBzTo
Thank you for the video. I'm doing the same this as you. I wonder if there is something in the settings that is interfering with Templater?
This is an issue with the latest version of the buttons plugin. Check out the issue here - shabegom/buttons#207
@horuscoding deus ex machina right here. thank you for helping solve this problem!!
Thank you. Moving the "moving" part to the button was the workaround I was considering. I'm glad we now know where the error was. Thanks again to all of you!
Replacing the button by this looks promising.
The template stops moving! But I have another issue: I can't find the dropdown for the template from my Templater despite of the fact that I've put that template folder in the Templater settings. Do you happen to know why?
I think you also need to indicate the folder in the (core) template settings.
I think you also need to indicate the folder in the (core) template settings.
Got it! Can you share your updated code for the meeting template and button code with me?
The meeting template does not need to be updated. The button object in the Meeting MOC needs to be replaced by a button from the Meta Bind plugin that should be similar to this
```meta-bind-button
style: primary
label: New Meeting
actions:
- type: templaterCreateNote
templateFile: "Templates/Template, Meeting.md"
folderPath: "Timestamps/Meetings"
fileName: "TKTK"
openNote: true
You should probably use the Meta Bind Button Builder instead of copy-pasting the code above. Let me know how it goes!
The meeting template does not need to be updated. The button object in the Meeting MOC needs to be replaced by a button from the Meta Bind plugin that should be similar to this
```meta-bind-button style: primary label: New Meeting actions: - type: templaterCreateNote templateFile: "Templates/Template, Meeting.md" folderPath: "Timestamps/Meetings" fileName: "TKTK" openNote: trueYou should probably use the Meta Bind Button Builder instead of copy-pasting the code above. Let me know how it goes!
I can create the first note. But the next time I click on the button, it says "Templater Error: Template parsing error, aborting. Check console for more information."
Any idea what went wrong here?
Is there already a note with the same name as the target one (either TKTK or the name that your template renamed itself to)?
I also had success with the Meta Bind plugin - thanks @antoineallard !
Is there already a note with the same name as the target one (either TKTK or the name that your template renamed itself to)?
Yes. The first note that was created has the name TKTK. If I were to click on the button again, it doesn't allow me to create a new meeting note and a little pop up of "Templater Error" will be shown.
I just updated the original post to use the Meta Bind plugin rather than Buttons. It's working wonderfully for me, too. Thanks for the tips, all!
Also, in case people prefer to follow along to a video, I just turned my meeting note system into a YouTube tutorial: https://youtu.be/Ud16HOQoS5Q
Hi @dannberg , thank you very much for your tutorials and these templates!
I noticed one weirdness with the current setup: you only temporarily create a new file at the location given by the folderPath
of the meta-bind-button, which is then moved by the templater plugin. So if you want to change this location, only the tp.file.move command needs to change location, as the folderPath is for all practical purposes ignored (but might create an then empty folder). Which seems a bit counter-intuitive.
I would suggest to replace
<% await tp.file.move("/Timestamps/Meetings/" + tp.date.now("YYYY-MM-DD") + " " + tp.file.title) %>
with
<% await tp.file.rename(tp.date.now("YYYY-MM-DD") + " " + tp.file.title) %>
Then the final location of the created note will be in the folderPath .
This also allows to create multiple buttons to different locations while using the same template.
Possibly, this is also related to the "my template is moving around" comments from above.
@JoschD Great call. This was an artifact from when I was using a different plugin to create these templates (manually with QuickAdd) but is reduntant (and as you pointed out, unnecessary) with the current Meta Bind button method.
I'll update this gist with your modification. Thanks!
I just published a new blog post about my full Meeting Note Template and system, in case anyone is interested in the finer details.