-
Notifications
You must be signed in to change notification settings - Fork 9.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Magento 2.1.9 wysiwyg upload images broken in frontend #11131
Comments
@Ayaname0330, thank you for your report. |
I have the same issue when editing Content -> Pages. After inserting image via the editor -> Insert Image -> browse, the link looks like |
@Ayaname0330, thank you for your report. |
@magento-engcom-team @PieterCappelle this happens when you copy paste content from wysiwyg A to wysiwyg B where is image, the image url in this case is special url that requires to be logged in into admin to be able to see the image. At least this was our case. After we inserted/replaced image manually using the insert image in wysiwyg B, the image started working. |
Experiencing the same issue here. The image is saved with a backend url that is not visible to anyone outside of the admin account that "placed" the image using wysiwyg. I've tried uploading again and placing each image (no copy + paste) and the problem still occurs. Running 2.1.10 |
I fixed this problem in 2.1.11 by overriding the class Magento\Framework\Event\ObserverInterface\CatalogCheckIsUsingStaticUrlsAllowedObserver I added a verification on the store id to set it to 0 if it is an empty string and it works correctly now. It will only works if you have the setting "Use Static URLs for Media Content in WYSIWYG for Catalog" set to yes in Configuration -> General -> Content Management.
|
Preconditions
1.Magento 2.1.9
Steps to reproduce
1.click the Insert/Edit image
2.choose a image
3.save
Expected result
1.the image show in frontend
Actual result
1.the image broken
2.the url contains '/cms/wysiwyg/directive/___directive'
The text was updated successfully, but these errors were encountered: