Hi,

Please copy searchindex.js and files under the html/_sources/.
Our search script uses searchindex.js for searching at first, and also
uses sources files to display the search result.

Thanks,
Takeshi KOMIYA



2017-05-02 6:00 GMT+09:00 'Erin Kelly' via sphinx-users
<[email protected]>:
> I'm trying to figure out whether I can update my published HTML
> documentation a few files at a time - one of the problems I have with this
> approach is that any new files or search terms won't be found by the old
> search.
>
> Is it possible to swap in the new searchindex.js file to fix this problem?
> Or some combination of html/searchindex.js, html/search.html, and maybe
> html/_static/searchtools.js ?
>
> What are all these search-related files and what do they do?
>
> For example, say I have published an HTML doc set with 100 html articles. I
> add a new rst file and build it into a new doc set with new_feature.html. I
> don't really want to replace all 100 pages when only a few of them have
> changes, so I just add the new_feature.html and maybe swap out the index
> page for a new one that includes a link to it. Is there a way to also swap
> in new search metadata from the new build so that items in new_feature.html
> are found on search?
>
>
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "sphinx-users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To post to this group, send email to [email protected].
> Visit this group at https://groups.google.com/group/sphinx-users.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"sphinx-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/sphinx-users.
For more options, visit https://groups.google.com/d/optout.

Reply via email to