Magento 2.2.X - WYSIWYG editor, insert image directive not replaced by actual image URL

[dverkade]

When the users adds an image in the WYSIWYG editor with the "Insert Image" option a URL is generated by Magento with a directive in it. This directive should be replaced when saving the page so that the directive URL is replaced by the correct media URL in Magento. Currently this does not happen and on the frontend the Directive URL is shown. This will result in broken images on the frontend.

Preconditions

1. Checked on Magento version 2.1.X, 2.2.0 and 2.2.1

Relations

Relates to:
#7167 2.2.0-dev - cms images are being added as __directive for path

Pull requests already fixing this issue, but closed without merging:
#12467 WYSIWYG JS - Directive URL not always properly detected

Steps to reproduce

1. Create a new CMS page in the backend of Magento
2. Open the WYSIWYG editor and use the "Insert Image" option in the toolbar to insert an image. (See screenshot below).
3. Save the page.
4. The admin user needs to logout of the backoffice.
5. Go to the CMS page on the frontend of Magento. The inserted image will be broken, when inspecting the HTML you will see that the image URL will be something like: "domain.com/admin/cms/wysiwyg/directive/___directive/e3ttZWRpYSB1cmw9Ind5c2l3eWcvQmxvZ19JbWczLnBuZyJ9fQ%2C%2C/key/4f92067f70cff318e8618a7e322e964261df0edae0581197d92cd51a93ba198d/"

To reproduce, use this dialog in order to insert the image into the editor.

Expected result

1. When switching with the "Show / Hide editor option" the directive URL should be replaced with the correct image URL.
2. The URL needs to be replaced by the correct name of the image. So that on the frontend the correct image will be loaded.

Actual result

1. The long directive URL is not replaced and is shown on the frontend resulting in broken images.

[magento-engcom-team]

@dverkade, thank you for your report.
The issue is already fixed in 2.2.2

[dverkade]

Hi @magento-engcom-team,

Thank you for your reply. We have tested this on Magento 2.2.2 on this works correct now. Please note that I could not find that this issue was resolved in the Magento 2.2.2 release notes. Searched for "directive" and "wysiwyg" and both did not mention resolving this issue.

Please also close this issue #7167 which is the same issue and is resolved in Magento 2.2.2 now. So this can be closed as well.