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

Browser based search not working in output generated by 1.7.6.1 on Windows 7 (Origin: bugzilla #666568) #4509

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.7.6.1 on platform Other
Assigned to: Dimitri van Heesch

Original attachment names and IDs:

On 2011-12-20 02:36:38 +0000, mike@ammd.com.au wrote:

Created attachment 203924
Basic config+source example including generated output on Windows

I am successfully generating Doxygen HTML output with Doxygen 1.7.6.1 on Windows 7 for a collection of C header files.

I've requested a local search facility via the following settings

SEARCHENGINE = YES
SERVER_BASED_SEARCH = NO
GENERATE_TREEVIEW = YES
GENERATE_HTML = YES
HTML_OUTPUT = html

and the HTML does display a search box when rendered. The doxygen logs do not contain any errors, and include the line

Generating search indices...

However, when displayed in a browser (IE, FF) the search functionality does not work. Examination of the Javascript code in search/search.js reveals the following code

var indexSectionsWithContent =
{
};

which causes a JS error when text is entered in the search box, and the search directory does not contain any .html index files which the code appears to expect.

On 2011-12-23 11:13:07 +0000, Dimitri van Heesch wrote:

Confirmed. The main problem was that the function was only part of group (due to SHOW_FILES=NO) and was not indexed in this case. Should be fixed in the next subversion update.

On 2012-02-25 15:37:37 +0000, Dimitri van Heesch wrote:

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