wagtail-generic-chooser
wagtail-generic-chooser copied to clipboard
wagtail
A toolkit for custom chooser popups in Wagtail
Hi all! We are using wagtail-generic-chooser in our project and recently upgraded our codebase to Wagtail 6.0 and since then we are getting warning: `RemovedInWagtail70Warning: The usage of `WidgetWithScript` hook...
 After upgrading my project to wagtail 5.1, all my uses of the wagtail-generic-chooser have started to look like the above. I'm not noticing this anywhere else so I'm not...
Currently the urlpatterns generated by the `ChooserViewSet` only accept integers (`d+`) as the id parameter: https://github.com/wagtail/wagtail-generic-chooser/blob/db66c35cd641cedcb3c4a771b859cfec4623ed00/generic_chooser/views.py#L732-L737 This makes it impossible to create a chooser that has UUIDs as a primary...
When I tried the Chooser with a model that contains a StreamField the StreamField wouldn't display when I wanted to create a new instance using the Chooser,
I've tried to find out how "select multiple" is supposed to work but I've failed and I had to give up. It would be really nice to have a minimal...
It looks like that when a `ChooserBlock` (or subclass) is within a `StructBlock`, the selected object's label is not able to contribute to getTextLabel (I think?) and so the next...
Why do we need an index for simple search functionality? Wouldn't it be easier to suppport simple `contains` by `field(s)` ?
Currently, I'm facing circular dependency in `AdminChooser` and solved this by importing the Model in the `__init__` like this: ```python from django.contrib.admin.utils import quote from django.urls import reverse from django.utils.translation...
This may be out of scope but in the context of rethinking chooser mosals it would be good to see if we can find a way to solve the issue...
Currently the chooser allows you to filter on linked fields. That can be useful in many situations. What I'd like to add is the ability to pass parameters to the...
