#35178: Override FORM_RENDERER for admin site
-------------------------------------+-------------------------------------
     Reporter:  Nikolay Fedorov      |                    Owner:  nobody
         Type:  New feature          |                   Status:  closed
    Component:  Forms                |                  Version:  5.0
     Severity:  Normal               |               Resolution:  invalid
     Keywords:  forms, render,       |             Triage Stage:
  template, admin, render template,  |  Unreviewed
  custom template                    |
    Has patch:  0                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------
Changes (by Natalia Bidart):

 * status:  new => closed
 * resolution:   => invalid
 * component:  contrib.admin => Forms

Comment:

 Hello Nikolay!

 As documented, the [https://docs.djangoproject.com/en/5.0/ref/settings
 /#form-renderer FORM_RENDERER] setting affects the way that forms and form
 widgets are rendered. If you wish to have only a subset of forms rendered
 with your custom renderer, you can follow
 [https://docs.djangoproject.com/en/5.0/topics/forms/#reusable-form-
 templates these docs].

 Given the lack of details for this ticket, it seems better suited to be a
 support request or a new feature request. The best place to get answers to
 your issue is using any of the user support channels from
 [https://docs.djangoproject.com/en/dev/faq/help/#how-do-i-do-x-why-
 doesn-t-y-work-where-can-i-go-to-get-help this link].

 Since the goal of this issue tracker is to track issues about Django
 itself, or new features already discussed and agreed in the forum, I'll be
 closing this ticket as invalid following the
 [https://docs.djangoproject.com/en/dev/internals/contributing/triaging-
 tickets/#closing-tickets ticket triaging process]. If, after debugging,
 you find out that this is indeed a bug in Django, please re-open with
 more/specific details and please be sure to include a small Django project
 to reproduce or a failing test case.

 Thank you!
-- 
Ticket URL: <https://code.djangoproject.com/ticket/35178#comment:1>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018d8f88b354-05050618-7a23-46d2-bfd9-23c4e868e266-000000%40eu-central-1.amazonses.com.

Reply via email to