Changes between Initial Version and Version 1 of Ticket #15779, comment 4


Ignore:
Timestamp:
Sep 20, 2011, 7:21:59 PM (13 years ago)
Author:
Ramiro Morales

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #15779, comment 4

    initial v1  
    1 I'm going to call this ticket fixed in [16857]. After that revision, it is possible to implement a custom URL scheme in the admin app because it uses named URLs when resolving hthe URLs in the model CRUD workflow. There is an example of a model with a CharField PK and with an instance with an `'add'` value for it in the test case added in such commit: https://code.djangoproject.com/browser/django/trunk/tests/regressiontests/admin_custom_urls/models.py?rev=16857
     1I'm going to call this ticket fixed in [16857]. After that revision, it is possible to implement a custom URL scheme in the admin app because it uses named URLs in the model CRUD workflow. There is an example of  an instance of a model with a CharField PK with an `'add'` value in the test case added in such commit: https://code.djangoproject.com/browser/django/trunk/tests/regressiontests/admin_custom_urls/models.py?rev=16857
    22
    3 The customziation process isn't completely straightforward because the named URL entry one is replacing needs to be removed from the !ModelAdmin URL map to force the admin app to take in account the one we are installing (see the `remove_url()` method in the example linked above). Patches to make this easier are welcome.
     3The customization process isn't completely straightforward because the named URL entry one is replacing needs to be removed from the !ModelAdmin URL map to force the admin app to take in account the one we are installing (see the `get_urls()`/`remove_url()` methods in the example linked above). Patches to make this easier are welcome.
Back to Top