Changes between Initial Version and Version 3 of Ticket #20113


Ignore:
Timestamp:
Apr 15, 2016, 11:44:32 AM (9 years ago)
Author:
Tim Graham
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #20113

    • Property Resolution → duplicate
    • Property Status new → closed
    • Property Component Uncategorized → Documentation
    • Property Type Uncategorized → Cleanup/optimization

  • Ticket #20113 – Description

    initial v3  
    22
    33If I use instance data from that model in a template, and want to render the fields myself, I need that name, as described in "Using the formset in the template":
    4 
     4{{{
    55<form method="post" action="">
    66    {{ formset.management_form }}
    … …  
    1212    {% endfor %}
    1313</form>
    14 
     14}}}
    1515Confusingly, the name which should be used here is "place_ptr", not "place_ptr_id", which it is in the database (using "place_ptr_id" in the template gives a MultiValueDictKeyError). Since this is not documented (or I haven't found it, though I did search!), I suggest adding something to the "Multi-table inheritance" documentation which explains how the auto-generated field can be used in templates as "place_ptr".
Back to Top