WYSIWYG mode: Images not shown

okoetter · 2020-05-22T10:19:23.393Z

Version: 1.0.214 Windows

I have some local embedded images that are not shown in WYSIWYG mode:

Markdown editor:

![f90cd8c69ed7a6b9d456d978878829be.png](:/f034e6ffd05f4503b9a3bb25b3afbd7b)

Markdown view:
grafik

WYSIWYG view:
grafik

Any ideas?

laurent · 2020-05-22T11:33:11.089Z

In the Help menu, could you open the development tools and inspect the broken tag on the WYSIWYG view?

To do that you would click on the small arrow in the top left corner, and select the image in the viewer. You should then see the <img> tag and its attributes (as below). If you could send a screenshot of it that would be great.

image1194×574 97.2 KB

okoetter · 2020-05-22T11:42:21.273Z

Here it is:

grafik695×218 9.16 KB

Maybe I should mention that I use the portable edition (sorry for not mentioning that earlier).

laurent · 2020-05-22T12:00:09.734Z

Thanks, at first sight the path seems valid but maybe there’s some encoding issue. I’ll check with the portable app to see if I can replicate the issue

dpoulton · 2020-05-22T14:19:05.891Z

@okoetter

I have seen this with the portable version. I have previously reported that image linking does not seem to work in the portable version (at least I cannot get it to work )

Feature Feedback: Pre-release 1.0.207

PORTABLE VERSION - Using the toolbar attach file tool, inserting an image results in a broken image link icon and the image file name. Using the markdown editor it can be seen that the file path for the image is stored as:
![picture.png](file://C:%5CUsers%5Cvbox%5CDesktop/JoplinProfile/resources/ae13dcd073834856ac09e3efe36f8bff.png)
rather than
![picture.png](:/ae13dcd073834856ac09e3efe36f8bff)
which is valid in the markdown viewer pane but still does not work in the WYSIWYG editor.

Trying drag and drop and copy/paste gives similar results.

However image handling seems to work correctly in the desktop version…

Actually this has been happening for me since 1.0.194 however only just realised that this does not appear to affect the installed desktop version.

dpoulton · 2020-05-22T14:55:31.966Z

@laurent

Don’t know if this will help but this GitHub post has screenshots I took as I tested the portable version and found it appeared to modify links to full, but non-working, paths.

StefanM · 2020-06-03T17:08:00.718Z

I have the same issue with the portable Windows Version 1.0.216
I use
<img src=:/3318be9563a44fcc954e13e25610c476>
as a work arround. This works in MD- and WYSIWYG-view