[Django] #35861: Documentation browser does not work

[Django]

#35861: Documentation browser does not work
-------------------------------------+-------------------------------------
Reporter: Franco Gidaszewski | Type: Bug
Status: new | Component:
| Documentation
Version: 5.1 | Severity: Normal
Keywords: browser search | Triage Stage:
documentation | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Hi there,

I'm submitting this ticket because I just tried to use the '''search
component in the documentation''' 'https://docs.djangoproject.com/en/5.1/'
but it does not work.

I've tried with some different words but it always returns "0 results for
''my_entry'' in version 5.1"

Hope you fix this soon :)

Amazing job, btw, with Django!

Best,
Fran
--
Ticket URL: <https://code.djangoproject.com/ticket/35861>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

[Django]

#35861: Documentation browser does not work
-------------------------------------+-------------------------------------

Reporter: Franco Gidaszewski | Owner: (none)
Type: Bug | Status: closed
Component: Documentation | Version: 5.1
Severity: Normal | Resolution: invalid

Keywords: browser search | Triage Stage:
documentation | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------

Changes (by Natalia Bidart):

* resolution: => invalid
* status: new => closed

Comment:

Hello Franco, thank you for reaching out. We are investigating this issue
since we've had a few reports a few days ago, for more details see
https://forum.djangoproject.com/t/docs-seem-to-go-missing-for-a-given-
version-when-there-are-docs-changes/35861/

This is an transient issue that is triggered when docs changes land in the
repo. The results will be back soon. I'll be closing this as `invalid`
since this ticket tracker is about issues with the Django framework, not
with djangoproject.com, but thanks again for alerting us.
--
Ticket URL: <https://code.djangoproject.com/ticket/35861#comment:1>