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

Search results pointing to external references not linked correctly (Origin: bugzilla #593679) #3500

Closed
doxygen opened this Issue Jul 2, 2018 · 0 comments

Comments

Projects
None yet
1 participant
@doxygen
Owner

doxygen commented Jul 2, 2018

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

Original attachment names and IDs:

On 2009-08-31 13:51:17 +0000, Jean-Marie wrote:

In release note for 1.6.1, this bug seems to be corrected. But with version 1.6.1 I have still bug.

Links generated by search engine look like this :
http://myproject/pub/doc/html/http://externalproject/myexternalclass.html

If I remove manually http://myproject/pub/doc/html/ I acces to myexternalclass documentation.

On 2009-09-02 18:51:18 +0000, Dimitri van Heesch wrote:

Please attach a self-contained example (source + config file in a zip) that allows me to reproduce the problem.

On 2009-09-03 08:31:38 +0000, Jean-Marie wrote:

Created attachment 142383
I reproduce bug with these test files

Generate doc for project1 then for project2.
Open html doc for project2, type Toto in search engine. You will have a wrong link.

On 2010-04-11 16:04:13 +0000, Dimitri van Heesch wrote:

Confirmed. Should be fixed in the next subversion update.

On 2010-06-15 11:22:14 +0000, Dimitri van Heesch wrote:

This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.7.0. 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.

@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