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

Broken links in HTML output with SHOW_FILES=NO (Origin: bugzilla #770747) #6056

doxygen opened this Issue Jul 2, 2018 · 0 comments


None yet
1 participant

doxygen commented Jul 2, 2018

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

Original attachment names and IDs:

On 2016-09-02 11:54:14 +0000, wrote:

Created attachment 334635
Example to reproduce bug.

When SHOW_FILES=NO, broken links are generated in the HTML output for module summary pages.

In the attached example, when you navigate from the index.html page to "Modules" and then to module "Foo", the module file (group___foo.html) contains a link labeled "test.cpp" to the non-existent page test_8cpp.html.

I do not know what is preferable: Removing the "Files" section from modules, or generating the HTML-ified source files. Possibly there should be an option to choose either option.

On 2016-09-02 13:33:07 +0000, Dimitri van Heesch wrote:

Confirmed. Should be corrected in the next GIT update.

When a file is documentation and added to a group, it should still appear as part of the group (and have a documentation page) even though SHOW_FILES is disabled. SHOW_FILES is for navigating to the files via the file list/index.

On 2016-09-05 13:46:03 +0000, Dimitri van Heesch wrote:

This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.12. 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 (preferably in the form of a self-contained example).

@doxygen doxygen closed this Jul 2, 2018

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