You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
See #3240 for context. That issue is the final fix for this, this issue is toward graceful failure.
If a collection of markdown documents have images from multiple directories in their document body, the CMS can only properly handle one of those directories.
Images from outside that directory are shown in the CMS with src set to the media_folder, except in the case of an absolute media_folder, the opening slash is removed, resulting in a relative path.
Example scenario:
combined media_folder for collection: /static/Images/docbook/images/api_mgmt
Describe the bug
See #3240 for context. That issue is the final fix for this, this issue is toward graceful failure.
src
set to the media_folder, except in the case of an absolute media_folder, the opening slash is removed, resulting in a relative path.Example scenario:
media_folder
for collection:/static/Images/docbook/images/api_mgmt
![API Gateway features](/Images/docbook/images/concepts/api_server.png)
img
tagsrc
in the CMS editor:static/Images/docbook/images/api_mgmt/api_server.png
To Reproduce
An entry in a deploy preview for a site implementing Open Authoring shows this behavior:
https://deploy-preview-203--axway-open-docs.netlify.com/admin/#/collections/apimgr_concepts/entries/apigtw_introduction
The Axway open docs site can be forked and run locally for testing:
https://github.com/Axway/axway-open-docs
Expected behavior
img
tagsrc
in the CMS editor should fall back to the URL provided in the content:/Images/docbook/images/concepts/api_server.png
The text was updated successfully, but these errors were encountered: