Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PDF generation fails on Scientific Programme once a relative URL is used #5042

Closed
vaclavstepan opened this issue Aug 14, 2021 · 0 comments · Fixed by #5044
Closed

PDF generation fails on Scientific Programme once a relative URL is used #5042

vaclavstepan opened this issue Aug 14, 2021 · 0 comments · Fixed by #5044
Assignees
Labels
Projects
Milestone

Comments

@vaclavstepan
Copy link
Contributor

Describe the bug
In the Scientific programme, the tracks are described in Markdown. When a relative URL is used for an included image, using a HTML img tag, generation of a PDF version of the document fails with:

<img src="/event/2/images/12-MariaZankl-small.png"/></para>' caused exception fileName='/event/2/images/12-MariaZankl-small.png' identity=[ImageReader@0x7fed8f2fbdc0 filename='/event/2/images/12-MariaZankl-small.png'] Cannot open resource "/event/2/images/12-MariaZankl-small.png"

You only find this, when you try to generate the PDF for the Scientific Programme page, in HTML view it shows fine.

To Reproduce
Steps to reproduce the behavior:

  1. Go to Management area
  2. Upload an image and copy its URL somewhere
  3. Add an img tag as follows into the description of some of a track in the Programme part of the Management area
  4. In the Display part, go to the Scientific Programme page and click the PDF icon on the top left of the page.
  5. See error

Expected behavior
It should accept the relative URL.

@ThiefMaster ThiefMaster added this to the v3 milestone Aug 14, 2021
@ThiefMaster ThiefMaster added this to To do in Release 3.0 via automation Aug 16, 2021
@ThiefMaster ThiefMaster self-assigned this Aug 17, 2021
@ThiefMaster ThiefMaster linked a pull request Aug 17, 2021 that will close this issue
Release 3.0 automation moved this from To do to Done Aug 18, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
No open projects
Release 3.0
  
Done
Development

Successfully merging a pull request may close this issue.

2 participants