userAdmin | This file will be packaged with your application

You can user following code for creating tabular inlines:

There's no "proper" way to do so, but... To achieve what you want you can pick any method that accepts obj argument. Like has_view_permission or get_forms or get_formset or get_extra...

Note that you will not receive a QuerySet of the related manager, but instead will get the obj that is requested in the non-inline admin.

Example:

You can use '__str__' as field:

When you register a model with ModelAdmin, the URLs will be formed from the app name ('users' here) and the model name ('user'), so /admin/users/user is expected. However, in this case Wagtail already provides a user management area (available from the Settings submenu) that exists under the /admin/users/ URL namespace - these URLs end up colliding with the ones you add through ModelAdmin.

It looks like your UserAdmin definition is more or less duplicating the functionality already provided by Wagtail, so you may not need this at all. If you do, one thing that might work is editing the INSTALLED_APPS setting in your project's settings to move your users app above wagtail.contrib.users - that way, the URL patterns for your own app will take precedence over Wagtail's built in /admin/users/ area, and it will correctly interpret anything under /admin/users/user/ as belonging to your own app (while letting all other URLs under /admin/users/ fall back to the Wagtail built-in area).

If that doesn't work, you'd need to either rename your users app (easier said than done for an established project...) or customise the ModelAdmin setup to use an alternative URL path. It doesn't look like ModelAdmin currently provides an official mechanism to do that, but overriding the AdminURLHelper object ought to work - within users/wagtail_hooks.py:

Add this code to CustomeUserAdmin:

Your Question model needs a def __str__(self) function like your Account model. If you want to represent it with question ID it should look like this:

You need to override the default form that is being used by UserAdmin and add your field like so:

The username field is still part of the search_fields and the add_fieldsets. You thus should remove the username field there:

Change the name of your image_file = forms.ImageField() to be image_file_w200_png. What you are doing there currently is defining a new field rather than changing your existing field because the names are not the same.

You could also define it in a different way in your class Meta: section. You can add a dictionary called widgets and write it like this: