Repository navigation
Allow for multi-context sites and media sources #164
Description
Feature request
Summary
Currently, images and linked files use a relative path when selecting from the browser assuming to be the default web context. It does not work, however, with sub-domains / contexts (e.g. blog.example.com) without moving / duplicating files to a sub-folder or specifying a full-path in the source by manually pre-pending the text in after selecting it in the media browser.
Why is it needed?
Some sites use images across multiple contexts or domains / sub-domains, and it adds an extra step.
Suggested solution(s)
Add a system setting to specify the base path for files or use media source's actual path in the editor's preview.
Activity
matdave commentedon Aug 1, 2025
It currently relies on whatever the media source's baseUrl is. Have you checked your Media Source's baseUrl setting to ensure it is properly configured?
GarretOverstreet commentedon Aug 2, 2025
I have set the base URL for the context setting, and tried different media sources, but it appears to revert to the subdomain, regardless of those settings. The base URL will be https://www.example.com/, but the preview in the WYSIWYG editor points to https://blog.example.com/ regardless of media source base or context site setting using a relative path. The only way around it is by using the full path with the TLD in the source field.
matdave commentedon Aug 21, 2025
The image is adding a domain? Can you post a screenshot or share how your media source is set up?