🐛 "field_id not found", happening intermittently on prod

[LoSkana]

Bug Description

Heya, thanks a lot for the project, it's awesome! I'm having an issue with the selects throwing this exception on prod, but the problem is that I've been unable to pinpoint a pattern. On dev, the problem never occours.

For reference, I'm using it like this (I need it to be rendered without an explicit form):

        widget = EventCharacterS2Widget(attrs={"id": "char_finder"})
        widget.set_event(ctx["event"])
        ctx["char_finder"] = widget.render(name="char_finder", value="") 

and defined as:

class EventCharacterS2:
    search_fields = [
        "number__icontains",
        "name__icontains",
        "teaser__icontains",
        "title__icontains",
    ]

    def set_event(self, event):
        self.event = event

    def get_queryset(self):
        return self.event.get_elements(Character)


class EventCharacterS2WidgetMulti(EventCharacterS2, s2forms.ModelSelect2MultipleWidget):
    pass


class EventCharacterS2Widget(EventCharacterS2, s2forms.ModelSelect2Widget):
    pass

(I wanted to reuse the common configuration).

Sorry if I am unable to provide further info to reproduce it; what can I try to understand better the situation?

Steps to Reproduce

Happening intermittently, no clear pattern found

Expected Behavior

No exception thrown

[LoSkana]

Update: the problem was the timeout for the cache. Not specificying a value leaves the default of 5 minutes, meaning that if the user keeps the page open more than that, the select2 field will be cleaned and will cause the "field_id not found" to be thrown.

The issue can be closed; to avoid other users stumbling on the problem, the API documentation could be updated indicating an explicit value for timeout (something sufficiently high to cover all normal cases, like 24h): https://django-select2.readthedocs.io/en/latest/django_select2.html#module-django_select2.conf

[codingjoe]

Hi there 👋,

We have a fair bit of documentation about the cache setup. But you are certainly welcome to bring in a fresh pair of eyes. You get a little blind as a maintainer for adoption issues in the documentation.

You don't need a ticket for that. Just go ahead and open a PR with any changes you want to suggest to the documentation.

Best!
Joe