You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Version, Operating system
Win64 24H2 26100.4652 UK International
Describe the bug
Tested Latex & Non-Latex Cherrytree 1.1.4, 1.40 & 1.50 - bug occurs in all, pointing to a recent change in Win11?
I installed 1.50 Non-Latex first, & then installed other 5 builds in turn over top as problem emerged, if relevant
I've been mainly using PDFs & jpgs to test, but all file types affected.
I'm new to Cherrytree so am not ruling out user error, but I can't currently see how I might be going wrong.
Drag & Drop of any (single or multiple) file type from Windows file explorer or Directory Opus into an open Cherrytree note, or onto a tree node, fails silently without error or result.
Copy-paste of multiple files (e.g. PDFs, jpgs) into an open note, fails silently without error or result.
Copy-paste of individual file into open note succeeds but with a very old-school shortened file name (e.g. "R283_Readme.pdf" becomes "R283_R~1.pdf"
Menu>Insert>Insert File works normally, embedding files correctly with correct fullname
To Reproduce
Should be pretty self-explanatory, but just in case, here's an affected unencrypted ctb, pdf and jpg, to rule out any weirdness
Curiosity got the better of me, and I wanted to rule out the dirty-downgrades potentially carrying-over something from 1.50 back to 1.40 & 1.1.4. So I did a full uninstall, reboot, check \program files\cherrytree has been properly Sarlacc'd, fresh-install 1.1.4-latex, check behaviour, repeat, fresh install 1.40-latex, check behaviour, reapeat, fresh-install 1.50-nolatex.
No change, behaviour still consistent with original bug report. Cheers.
I just came on to report the same issue - with one caveat being I'm not actually seeing the shortened filenames. However, seems like no way to bulk-attach files (drag and drop doesn't work in all cases, copy-paste only on individual files). thanks for looking into it :)
Thank you, Giuseppe! I can confirm this is now, as above:
Drag & Drop of single or multi-files: WORKING properly to embed files in notes
Copy-paste of multi-files into note: WORKING
Copy-paste single files into note without truncating filename: WORKING
Insert-File: CONTINUED WORKING as expected.
Additionally, I tested:
A) Previously-embedded files properly surviving renaming/deletion of original: WORKING
B) Embedded files being opened from inside Cherrytree note>updated/edited in external program>saved in external program>Cherrytree automatically bringing that edited version back in to update the version embedded in the note: WORKING
The only vague anomaly / vaguely unexpected behaviour I managed to find was that the node tree is mouse-pointer-indicated as a valid target for drag-dropped file(s), but nothing happens on drop (this is a valid operation in some other node-tree based note apps I've used, for instance in the ancient copy of Info Select I still use, this is how you include a shortcut to an external file as a sub-node, rather than embedding it):
Screen.Recording.2025-08-23.135102.mp4
If the drop-on-node-tree thing is as design-intended, I believe this is now resolved, thank you very much for all your work!
Thank you very much for your detailed testing @Rab-C , that is very useful.
I see that the drop target is not properly indicating where you can and can not drop, I will pass it for another time as I have a few other things to sort out before the next release which I would like to do within two weeks, I will close this for now.
Activity
Rab-C commentedon Jul 19, 2025
Quick update:
Curiosity got the better of me, and I wanted to rule out the dirty-downgrades potentially carrying-over something from 1.50 back to 1.40 & 1.1.4. So I did a full uninstall, reboot, check \program files\cherrytree has been properly Sarlacc'd, fresh-install 1.1.4-latex, check behaviour, repeat, fresh install 1.40-latex, check behaviour, reapeat, fresh-install 1.50-nolatex.
No change, behaviour still consistent with original bug report. Cheers.
giuspen commentedon Jul 19, 2025
I can reproduce 1) and I will have a look at that.
results for me in pasting only one of the multiple files, I will see if possible to fix it to paste multiple.
I remember I was stuck with this shortened path as the only way it worked, I will try again.
JGKle commentedon Aug 10, 2025
I just came on to report the same issue - with one caveat being I'm not actually seeing the shortened filenames. However, seems like no way to bulk-attach files (drag and drop doesn't work in all cases, copy-paste only on individual files). thanks for looking into it :)
fixed drag and drop of files from windows file manager into rich text (β¦
debugging copy and paste of files from windows file manager into richβ¦
fixed copy and paste of files from windows file manager into rich text (
giuspen commentedon Aug 23, 2025
Please try the test version https://www.giuspen.net/cherrytree/#downl so-called v1.5.0+47 where this should be fixed
JGKle commentedon Aug 23, 2025
Confirmed! Both drag-and-drop and copy-paste of multiple files works - thanks! :)
Rab-C commentedon Aug 23, 2025
Thank you, Giuseppe! I can confirm this is now, as above:
Additionally, I tested:
A) Previously-embedded files properly surviving renaming/deletion of original: WORKING
B) Embedded files being opened from inside Cherrytree note>updated/edited in external program>saved in external program>Cherrytree automatically bringing that edited version back in to update the version embedded in the note: WORKING
The only vague anomaly / vaguely unexpected behaviour I managed to find was that the node tree is mouse-pointer-indicated as a valid target for drag-dropped file(s), but nothing happens on drop (this is a valid operation in some other node-tree based note apps I've used, for instance in the ancient copy of Info Select I still use, this is how you include a shortcut to an external file as a sub-node, rather than embedding it):
Screen.Recording.2025-08-23.135102.mp4
If the drop-on-node-tree thing is as design-intended, I believe this is now resolved, thank you very much for all your work!
Rab.
giuspen commentedon Aug 24, 2025
Thank you very much for your detailed testing @Rab-C , that is very useful.
I see that the drop target is not properly indicating where you can and can not drop, I will pass it for another time as I have a few other things to sort out before the next release which I would like to do within two weeks, I will close this for now.