TinyMCE actually has little to do with this: once your content has been saved, and it contains the site-relative URL of images, if you change the structure of the site by moving it under a different virtual directory, yes, your images will be broken. To
fix that, we'd have to save tokens representing the path instead of the path, and have post-processing of the output to replace those tokens at runtime with the actual path. It's doable but it's not implemented currently.
In the meantime, the workaround is to configure your dev environment to reflect the structure of prod.
Thanks bertrandleroy. I'm still curious though why it couldn't use the Base URL property as is without the tokens. The rest of the site already operates like this where ~/url is http://domain.com/url or http://domain.com/subsite/url based on
the root of the application itself. That includes images that are part of my theme, menu's links etc. Why are images in content types any different?
So when you say "and it contains the site-relative URL of images," I would expect the concept of sit-relativity be from the base application URL as defined by IIS or BaseURL setting in the properties. Perhaps you can help me better understand
the value of the BaseURL property?
Sorry, not trying to be difficult, just trying to understand what is so unique about images and anything I could do to assist.