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

Wrong path to graph_legend figure in graph_legend.html when CREATE_SUBDIRS = YES (Origin: bugzilla #708806) #5301

doxygen opened this Issue Jul 2, 2018 · 0 comments


None yet
1 participant

doxygen commented Jul 2, 2018

status VERIFIED severity normal in component general for ---
Reported in version 1.8.5 on platform Other
Assigned to: Dimitri van Heesch

Original attachment names and IDs:

On 2013-09-26 09:05:37 +0000, Ruey-Shi Rau wrote:

Created attachment 255796
Simple source file and Doxyfile

Reproducing step:

  1. Untar the attached bug.tgz
  2. doxygen

Then, the generated html/graph_legend.html refers to "../../graph_legend.png".
However, the correct path is "./graph_legend.png".

If I change the CREATE_SUBDIRS flag back to NO, then it works fine.

On 2013-09-28 15:21:16 +0000, Dimitri van Heesch wrote:

Confirmed. Should be fixed in the next GIT update.

On 2013-12-19 02:21:10 +0000, Michael Stangeland wrote:

Could this be related to my @ref problems? I have a mainpage that has a @ref another_page. In the tree on the left the URL path is correct, but the link directly in mainpage is missing 2 directories...

expected .../doxygen/html/d0/d0b/a00004.html
bit it has .../d0/d0b/a00004.html

Almost like instead of "html" there was a ".."

On 2013-12-24 18:59:55 +0000, Dimitri van Heesch wrote:

This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.6. Please verify if this is indeed the case. Reopen the
bug if you think it is not fixed and please include any additional information
that you think can be relevant (preferrably in the form of a self-contained example).

@doxygen doxygen closed this Jul 19, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment