[Bug] Unable to open existing weekly note
See original GitHub issueHi, When opening existing periodic notes using the command palette (except for daily notes), I get the following error:
"Unable to create new file"
The same behaviour occurs for both create
and open
this is where the error is
→ If the file already exists, just open it.
Issue Analytics
- State:
- Created a year ago
- Comments:6 (1 by maintainers)
Top Results From Across the Web
Unable to open Weekly notes (hotkey) - Help - Obsidian Forum
Part A. When I press 'shift+alt+d' —> if no daily notes is exits, new daily note is created based on template settings. else...
Read more >Unable to create new file · Issue #66 - GitHub
This message only appears after a weekly note has been created. However, the weekly note created when I originally select the command "Open...
Read more >[Update: Dec. 26] YouTube bugs/issues & pending ...
Here we are tracking all the bugs and problems found on YouTube and their status as well as any pending improvements that are...
Read more >Known Issues — Pokémon GO Help Center - Niantic Support
Issue description: Some Trainers battling may see incorrect or missing visuals if their device has not yet downloaded assets after a new update ......
Read more >Capture and read bug reports - Android Developers
A bug report contains device logs, stack traces, and other diagnostic ... metadata file that contains the Android release letter.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I have this issue as well. You can’t use hotkeys or the toolbar icon to call up an existing weekly note.
I am running into the excact same issue. My configuration looks like this:
And the current weekly is already existing.