Changes between Version 1 and Version 2 of Ticket #30577, comment 9


Ignore:
Timestamp:
Jun 10, 2024, 3:53:52 AM (4 months ago)
Author:
ldeluigi

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #30577, comment 9

    v1 v2  
    55The interesting part is in the `example` app admin.py file: [https://github.com/ldeluigi/django-poc-20240610/blob/master/example/admin.py]
    66
    7 I'd like to be able to do the same without having to write that ugly and cumbersome code which as a side effect has to alter the field names of the model admin disruptively.
     7I'd like to be able to do the same without having to write that ugly and cumbersome code which as a side effect has to alter the field names inside the model admin `field` and `fieldsets` lists disruptively, breaking the rest of the code not aware of the renaming of those from `something` to `something_local`.
    88In my PoC I can't take advantage of the read_only field on widgets because I can't define an abstract admin form class that works for every subclass, because its subclass define DateTimeFields with different names and not every one of them is read only potentially.
    99What I need is something that allows me to customize the display of readonly field based on their type that is only used if they are read only for whatever reason, including permissions.
Back to Top