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
The WYSIWYG editor breaks all existing images from a Markdown note. It adds the full local path to images previously added through Markdown.
For example, the image was 63545214c69fcaff3f19afd2b0e0e651 and correctly placed with Markdown, when going to WYSIWYG, it changed to a full local path. It is possible to see the change in the attached log.
!\[63545214c69fcaff3f19afd2b0e0e651.png\]([file://C:/Users/1545](file://C:/Users/1545) IRON
V4/.config/joplin-desktop/resources/40270689124e42cbb6ac2fddbcf621d8.png)
On May 25, 2020 12:51:10 AM GMT+02:00, Laurent Cozic ***@***.***> wrote:
Is that the portable version?
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
#3267 (comment)
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
The WYSIWYG editor breaks all existing images from a Markdown note. It adds the full local path to images previously added through Markdown.
For example, the image was
63545214c69fcaff3f19afd2b0e0e651
and correctly placed with Markdown, when going to WYSIWYG, it changed to a full local path. It is possible to see the change in the attached log.Environment
Joplin 1.0.216 (prod, win32)
Client ID: 88172fdc238748cabba691cc30d18a14
Sync Version: 1
Profile Version: 29
Revision: 4eb680d (master)
Windows 10
Steps to reproduce
Describe what you expected to happen
Do not break the images when going to WYSIWYG and back, i.e. keep as relative path:
Logfile
debug.log
The text was updated successfully, but these errors were encountered: