Opened 5 years ago

Closed 5 years ago

Last modified 4 years ago

#14066 closed (invalid)

Shouldn't ModelFormMetaclass be public for inheritance issues?

Reported by: rm4dillo Owned by: nobody
Component: Core (Other) Version: 1.2
Severity: Keywords:
Cc: && Triage Stage: Unreviewed
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: UI/UX:

Description

Hi,

I'm trying to override the ModelForm class in order to create a Form with dynamic fields.
My new class (that inherits from ModelForm) needs a meta class which should be a child of ModelFormMetaclass but this class is not in the all list of the admin.forms.modules module.

Is there a reason for this? If not could you please add the ModelFormMetaclass symbol to admin.forms.modules._ _all_ _?

Thanks in advance.

Rm4dillo

Change History (3)

comment:1 Changed 5 years ago by anonymous

  • Cc && added
  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset

comment:2 Changed 5 years ago by mariarchi

  • Resolution set to invalid
  • Status changed from new to closed

You can still import it, _ _ all _ _ does not impose restrictions on importing.

comment:3 Changed 4 years ago by jacob

Milestone 2.0 deleted

Note: See TracTickets for help on using tickets.
Back to Top