After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 607432 - Todo list via navigation tree gives not found error
Todo list via navigation tree gives not found error
Status: RESOLVED FIXED
Product: doxygen
Classification: Other
Component: doxywizard
1.6.2
Other Windows
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
: 608002 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2010-01-19 10:33 UTC by AJ Visser
Modified: 2010-02-21 12:57 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Contains doxyfile and code to reproduce above error (21.86 KB, application/x-zip-compressed)
2010-01-19 12:16 UTC, AJ Visser
Details

Description AJ Visser 2010-01-19 10:33:35 UTC
On Windows (XP SP3), I had installed doxygen 1.6.1.
I just added a few todo in my source code (C++) and after recreating the HTML output, I saw a Todo List in the navigation tree. I use the Output option HTML only with frames and a nagivation tree. It works.

Than I installed doxygen 1.6.2 right on top of 1.6.1. Made a few adjustments to my code and let doxywizard regenerate the HTML docs. It works as normal, except the Todo list via the navigation tree gives an 'Not found' error in my browser (Chrome 3.0).

If I navigate to one of the function, which contains a @todo and from there I try to access the Todo List, it works.

To see whether the upgrade from 1.6.1 to 1.6.2 was the problem, I removed the complete HTML tree and let doxywizard generate the HTML output. Still no luck.
Even in different browsers (Firefox 3.5.7) and IE8, the Todo List is not available.

The whole doxyfile project, contains currently about 8 cpp files (7 class implementation, 1 main file) and a diversity of header files (classes and abstract classes)
Comment 1 Dimitri van Heesch 2010-01-19 11:45:20 UTC
Do you have SHORT_NAMES enabled? If so then please retry with this option disabled, let me know if that makes a difference. If you already had it disabled, then please attach a self-contained example (source+config file) that allows me to reproduce the problem.
Comment 2 AJ Visser 2010-01-19 12:14:21 UTC
SHORT_NAMES has not effect, whether it is enabled or disabled. It had been disabled though.

I have attached a zip file, which contains a few code classes I am using. This is the minimal set, I was able to reproduce this error.
It also contains the doxyfile. All have been testen in C:\SeaConf.

The function SerialDevice::Create contains the @todo note.

Hopefully this is enough for you.
Comment 3 AJ Visser 2010-01-19 12:16:27 UTC
Created attachment 151754 [details]
Contains doxyfile and code to reproduce above error

This zip file, contains a doxyfile and sourcecode to reproduce the bug that has been described here.
Comment 4 AJ Visser 2010-01-21 09:14:38 UTC
According to Chrome: This is the link that is used from the navigation tree:
file:///.../html/dd/da0/todo.html (Note the dd/da0)

Using the Todo links in functions, the link is:
file:///.../html/todo.html (Is correct).

The dd/da0 is first link, may be different is attached example. This is because this comes from the complete html generated by the project doxyfile instead of test doxyfile.
Comment 5 Jan Humpl 2010-01-21 11:08:11 UTC
I found, that this issue also causes that eclipse search does not work (GENERATE_ECLIPSE_HELP feature). This is because eclipse stop searching when it founds non-valid link. If I manualy correct links in toc.xml then eclipse search works OK.
Comment 6 Dimitri van Heesch 2010-01-23 11:53:16 UTC
Confirmed. So it seems that setting CREATE_SUBDIRS to YES can also cause this issue. Should be fixed in the next subversion update.
Comment 7 Dimitri van Heesch 2010-01-30 10:42:04 UTC
*** Bug 608002 has been marked as a duplicate of this bug. ***
Comment 8 Poul-Erik Hansen 2010-02-08 19:02:57 UTC
(In reply to comment #1)
> Do you have SHORT_NAMES enabled? If so then please retry with this option
> disabled, let me know if that makes a difference. If you already had it
> disabled, then please attach a self-contained example (source+config file) that
> allows me to reproduce the problem.

I have the same error, but the bug decipher when "SHORT_NAME" is disabled.
Comment 9 Dimitri van Heesch 2010-02-21 12:57:32 UTC
This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.6.3. 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.