[
https://issues.apache.org/jira/browse/SLING-7840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16586001#comment-16586001
]
Bertrand Delacretaz commented on SLING-7840:
--------------------------------------------
Prefixing relative image paths with ./ fixes this for me,
[https://github.com/apache/sling-site/pull/20] , but it looks like more pages
are affected.
I saved a diff of the website generation between the old and new jbake,
attached to SLING-7776 -I attach a quick analysis of those diffs,
broken-images.txt where we missed the "img src" changes that cause this.
It looks like that's a dozen pages to fix, by prefixing relative image paths
with ./ so we might just do that manually, or [~kwin] maybe you have a
different suggestion, a jbake option maybe?
> Image rendering broken on sling.apache.org
> ------------------------------------------
>
> Key: SLING-7840
> URL: https://issues.apache.org/jira/browse/SLING-7840
> Project: Sling
> Issue Type: Bug
> Components: Site
> Reporter: Robert Munteanu
> Priority: Critical
> Attachments: broken-images.txt
>
>
> While reviewing https://github.com/apache/sling-site/pull/19 we discovered
> that image links are rendered:
> 1. always with the sling.apache.org domain ( so images added locally will not
> be considered )
> 1. with a wrong path, no longer appending the parents of the current page
> So the image links at both
> * http://localhost:8820/documentation/development/ide-tooling.html
> * https://sling.apache.org/documentation/development/ide-tooling.html
> are broken, being rendered as
> http://sling.apache.org/ide-tooling/new-server.png, whereas they should be
> * http://localhost:8820/documentation/development/ide-tooling/new-server.png
> *
> https://sling.apache.org/documentation/development/ide-tooling/new-server.png
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
