TinyMCE showing wrong image in 6.1.6 (upgraded from 4.7.11)
One page on the site has an image in the body of the content, and when viewing the image in the editor right after inserting it, the image is correct.
When the page is saved and published, the correct image appears on the published page.
But the editor - immediately after either saving or publishing - shows another unrelated image. Media folder paths are way different. Tried uploading a fresh version of the image and even creating a fresh instance of the page where this happens, but still get same result. Republished entire site from Content on down. Hasn't shaken that bug loose.
Have seen similar issues in the forum from older versions of Umbraco, but we followed the upgrade path to get to 6.1.6 so wondering if something in the TinyMCE upgrade is a bit off. Have the Image Cropper Extended installed but not calling out a cropped version of the uploaded image in the body of the page.
Has anyone else encountered something like this, and if so, did you arrive at a workaround or locate the source of the wrong image insertion?
TinyMCE showing wrong image in 6.1.6 (upgraded from 4.7.11)
One page on the site has an image in the body of the content, and when viewing the image in the editor right after inserting it, the image is correct.
When the page is saved and published, the correct image appears on the published page.
But the editor - immediately after either saving or publishing - shows another unrelated image. Media folder paths are way different. Tried uploading a fresh version of the image and even creating a fresh instance of the page where this happens, but still get same result. Republished entire site from Content on down. Hasn't shaken that bug loose.
Have seen similar issues in the forum from older versions of Umbraco, but we followed the upgrade path to get to 6.1.6 so wondering if something in the TinyMCE upgrade is a bit off. Have the Image Cropper Extended installed but not calling out a cropped version of the uploaded image in the body of the page.
Has anyone else encountered something like this, and if so, did you arrive at a workaround or locate the source of the wrong image insertion?
is working on a reply...