-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Multiple extensions for tiddlers on the filesystem with NodeJS #2647
Comments
More specifically, after digging a bit in
This looks, to say the least, confusing. |
Ok, got it. |
Hmmm, I see that this bug has already been fixed on |
To be precise, this was fixed in f1090d7 as part of #2572 (and the bug is present in the latest release 5.1.13). I am seeing some strange behavior with tiddlers not being saved that I suspect is caused by this bug. It sounds critical enough to issue an update on npm or a new patch release to address it (pretty please) |
I have 5.1.13 installed and I am facing with the same behavior.
Running through |
Ping @Jermolene !! |
Hi there,
I'm getting a behavior that seems weird and looks like a bug to me: I run TiddlyWiki on NodeJS, and my tiddlers get saved to the filesystem with multiple duplicate extensions.
E.g. for the Story tiddler: every time I start up TiddlyWiki, one more level of
.tid
gets added to the filename. Thus currently, I have the following Story tiddler files in mytiddlers
folder:As for the other tiddlers, same story, every time I modify a tiddler, it gets saved with one more level of
.tid
(starting with 2), e.g.:This is also causing me
ENOENT
unlink errors with drafts, since TiddlyWiki tries to removeDraft_of_'blah'.tid
which doesn't exist (Draft_of_'blah'.tid.tid
does). Hence when I restart the wiki, all drafts that I committed/cancelled previously are back again.All imported files/images have multiple extensions as well, e.g.
some_pic.png.png
andsome_pic.png.png.meta
.May be related to #2558 and #1570.
I should also mention that I'm accessing the wiki through an Apache proxy (for HTTPS), and that the wiki is hosted in a subfolder (non-empty
pathprefix
).Any thoughts?
I'd be happy to provide more details as needed.
The text was updated successfully, but these errors were encountered: