Wysywig editor shows broken image icons

[deadlyw1re]

Preconditions

1. Magento 2.1.7
2. PHP 7.0

Steps to reproduce

1. Add image in Wysywig editor

Expected result

1. Image is shown in editor

Actual result

1. Broken image icon
2. Url is <img src="http://domain/path-to-magento/adminurl/cms/wysiwyg/directive/___directive/e3ttZWRpYSB1cmw9Ind5c2l3eWcvcGRmL3BkZi5wbmcifX0,/key/e44fd2b2430f15239de43de5a10cb958615b525bb7bca920ab2865c99ff7de7d/" data-mce-src="http://domain/path-to-magento/adminurl/cms/wysiwyg/directive/___directive/e3ttZWRpYSB1cmw9Ind5c2l3eWcvcGRmL3BkZi5wbmcifX0,/key/e44fd2b2430f15239de43de5a10cb958615b525bb7bca920ab2865c99ff7de7d/">

[hostep]

If this occurs on the product or category wysiwyg fields, then it is probably a duplicate of #6138, and this bug will be fixed in Magento 2.1.8: ba66124

[deadlyw1re]

@hostep This occures in the wysiwyg editor itself, on the frontend the images are visible.

[hostep]

@deadlyw1re: Yes, but which wysiwyg editor? The one in the CMS pages/blocks shouldn't have this bug, only the wysiwyg editor on the product and categories edit forms if I remember correctly.

[deadlyw1re]

@hostep This bug occures on CMS pages/blocks and products/categories

[PieterCappelle]

@hostep I think the bug is back in 2.1.9. We are having the same problem in CMS Pages / Blocks. When you insert image in 2.1.8, we get <p><img src="{{media url="wysiwyg/Hond.jpg"}}" width="1024" height="683" /></p> when we insert image in 2.1.9 <p><img src="http://local.magento/admin/cms/wysiwyg/directive/___directive/e3ttZWRpYSB1cmw9Ind5c2l3eWcvVmVsZC5qcGcifX0%2C/key/d3f89696a93152f6d352e5d5cb391180a27c8a7924d9fe3b583d3e9f03d00753/" width="959" height="1024" /></p>

[hostep]

@PieterCappelle: that's weird, I can't really see anything at first sight in the diff between 2.1.8 and 2.1.9 which can cause this bug to re-appear.

Can you reproduce it on a clean 2.1.9 installation?

[PieterCappelle]

@hostep Tomorrow at MM17BE? Will show you my case.

[hostep]

Confirmed, tried it on a clean 2.1.8: no problem
Then on a clean 2.1.9: and the problem you describe appears. God damned, I hoped we were finally rid of this bug, but it came back :(

(See you tomorrow at MM17BE :))

[PieterCappelle]

You should join the Slack channel of Magento. Let's fix this in the contribution day :-)

[okorshenko]

Just for info: 2.1.8...2.1.9#diff-92c32b12996a53a237ff51fa0d39d829R113