logseq
pop up for outdated format keeps coming back for the same file even after updating the filename format
Search first
- [X] I searched and no similar issues were found
What Happened?
I seem to have one file that has incorrect file format. I believe it is the euro sign.
assets/[REPLAY]_Live_Course_|_ChatGPT_&_Generative_AI_a€_1703859785518_0_1703953299605_0.mp4
This is the pop up message I see:
However even after updating the filename format, this pop up message keeps coming back. I even tried to change it myself in the assets directory but it does not seem to help. Every time I start up Logseq it keeps reporting this issue.
Let me know if you need more info or help fixing this issue.
Thank you
Reproduce the Bug
- Save file with incorrect filename format?
- update filename format
- close logseq
- open logseq => message appears again
Expected Behavior
I would expect the filename format to be fixed for ever after updating it.
Screenshots
Desktop or Mobile Platform Information
MacOS app on Macbook M2 MacOs latest version. iOS app on iPhone also has latest app version, also the iOS version
Additional Context
No response
Are you willing to submit a PR? If you know how to fix the bug.
- [ ] I'm willing to submit a PR (Thank you!)
Same thing happening here.
It seems that some of your filenames are in the outdated format. We suggest you upgrade now to avoid potential bugs.
For example, the files below have reserved characters that can't be synced on some platforms.
[Update filename format]
- 2022-08-05-destruction-of-west-29th-nicolet-blaisdell-ave-camp/22, 07:48.m4a
and five more like that. (Presumably the problem is the comma and/or the colon.)
Pressing the button resulted in a pop-up that talked about configuration options but did not give the way to change those configuration options:
Filename format
This setting configures how a page is stored to a file. Logseq stores a page to a file with the same name.
Some characters like "/" or "?" are invalid for a filename.
Logseq replaces invalid characters with their URL encoded equivalent to make them valid (e.g. "?" becomes "%3F").
The namespace separator "/" is also replaced by "___" (triple underscore) for aesthetic consideration.
But it also said:
🎉 Well done! No further action required.
But then does the same thing every startup…
On Debian testing (Trixie) desktop.
Beta sync enabled.
This has started happening to me. Same situation as the OP. Using LogseqSync as well.
Anyone found a fix or should this be reopened?
