Re: ModelAdmin

[Mike Dewhirst]

Satyajit

I'm speaking for myself here.

I'm not comfortable with dilution of list content with what appears to 
be a competing Whatsapp group.


In particular, this thread is one to which I have contributed and if you 
kidnap the thread you cut me out of my conversation.


In general, if you take conversations away from the list you hide them 
from core Django devs who are then deprived of information coming from 
users. Django users are exactly equal to customers of an enterprise and 
if an enterprise doesn't hear customer feedback it risks becoming 
irrelevant and possibly going out of business.


I think Whatsapp, Slack etc are all very appropriate places for private 
conversations. Not so much for a user mutual-support mailing list like 
this one.


 Thanks for understanding

Cheers

Mike

On 5/01/2023 3:31 pm, Satyajit Barik wrote:
Yes. It does. ModelAdmin classes can define list filters that appear 
in the right sidebar of the change list page of the admin.
For more reference: 
https://docs.djangoproject.com/en/4.1/ref/contrib/admin/filters/


For this topic related join our WhatsApp group: https://bit.ly/3oJtfcf

Regards,
Satyajit

On Thu, Jan 5, 2023 at 9:09 AM Mike Dewhirst  
wrote:


On 5/01/2023 5:43 am, Mario St-Gelais wrote:

Hello group, first post here.
Quick question.  Can capabilities of ModelAdmin such as
list_filter or search_fields be used outside of the admin interface?


Have you looked at htmx?

https://www.simplecto.com/htmx-and-the-list_editable-in-django-admin/

htmx is very sweet. Essentially, you can replace a named  on an existing page by calling whatever view
you care to write. Your view might have to borrow from the Django
code if you really like what it does.

Digressing slightly, I discovered that you can make a link in html
using the  entity and just replace href="/search" with
hx_trigger="/hx_search", for example, so that the existing css
works and it looks like an ordinary link.

Cheers

mike



I want a view that would allow non logged users to search a site
through checkboxes and some search fields possibly and obviously,
the way this is implemented in the admin view is rather good.

Alternatively, what approach can be used in django?

Thanks
Mario
-- 
You received this message because you are subscribed to the

Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to django-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit

https://groups.google.com/d/msgid/django-users/CAFmF6_vLzivA3Y-sskqmcZzsuLc27opP6xW3m3wvmV7nepu%3D-A%40mail.gmail.com

<https://groups.google.com/d/msgid/django-users/CAFmF6_vLzivA3Y-sskqmcZzsuLc27opP6xW3m3wvmV7nepu%3D-A%40mail.gmail.com?utm_medium=email_source=footer>.



-- 
Signed email is an absolute defence against phishing. This email has

been signed with my private key. If you import my public key you can
automatically decrypt my signature and be sure it came from me. Just
ask and I'll send it to you. Your email software can handle signing.

-- 
You received this message because you are subscribed to the Google

Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to django-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit

https://groups.google.com/d/msgid/django-users/6b16042c-dd2b-9757-2edc-1bbae0e7d911%40dewhirst.com.au

<https://groups.google.com/d/msgid/django-users/6b16042c-dd2b-9757-2edc-1bbae0e7d911%40dewhirst.com.au?utm_medium=email_source=footer>.

--
You received this message because you are subscribed to the Google 
Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send 
an email to django-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CANd-%2BoD5Nrj1OxsSHvy8nVru5u1Hw1yWzJ19k7tAoEZOoovQBg%40mail.gmail.com 
<https://groups.google.com/d/msgid/django-users/CANd-%2BoD5Nrj1OxsSHvy8nVru5u1Hw1yWzJ19k7tAoEZOoovQBg%40mail.gmail.com?utm_medium=email_source=footer>.



--
Signed email is an absolute defence against phishing. This email has
been signed with my private key. If you import my public key you can
automatically decrypt my signature and be sure it came from me. Just
ask and I'll send it to you. Your email software can handle signing.

--
You received this message because you are subscribed to the Google Groups "Django 
users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/83079885-1bb7-81a1-75d9-753d195af702%40dewhirst.com.au.


OpenPGP_signature
Description: OpenPGP digital signature

Re: ModelAdmin

[Satyajit Barik]

Yes. It does. ModelAdmin classes can define list filters that appear in the
right sidebar of the change list page of the admin.
For more reference:
https://docs.djangoproject.com/en/4.1/ref/contrib/admin/filters/

For this topic related join our WhatsApp group: https://bit.ly/3oJtfcf

Regards,
Satyajit

On Thu, Jan 5, 2023 at 9:09 AM Mike Dewhirst  wrote:

> On 5/01/2023 5:43 am, Mario St-Gelais wrote:
>
> Hello group, first post here.
> Quick question.  Can capabilities of ModelAdmin such as list_filter or
> search_fields be used outside of the admin interface?
>
>
> Have you looked at htmx?
>
> https://www.simplecto.com/htmx-and-the-list_editable-in-django-admin/
>
> htmx is very sweet. Essentially, you can replace a named  id="whatever"> on an existing page by calling whatever view you care
> to write. Your view might have to borrow from the Django code if you really
> like what it does.
>
> Digressing slightly, I discovered that you can make a link in html using
> the  entity and just replace href="/search" with
> hx_trigger="/hx_search", for example, so that the existing css works and it
> looks like an ordinary link.
>
> Cheers
>
> mike
>
>
> I want a view that would allow non logged users to search a site through
> checkboxes and some search fields possibly and obviously, the way this is
> implemented in the admin view is rather good.
>
> Alternatively, what approach can be used in django?
>
> Thanks
> Mario
> --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-users/CAFmF6_vLzivA3Y-sskqmcZzsuLc27opP6xW3m3wvmV7nepu%3D-A%40mail.gmail.com
> <https://groups.google.com/d/msgid/django-users/CAFmF6_vLzivA3Y-sskqmcZzsuLc27opP6xW3m3wvmV7nepu%3D-A%40mail.gmail.com?utm_medium=email_source=footer>
> .
>
>
>
> --
> Signed email is an absolute defence against phishing. This email has
> been signed with my private key. If you import my public key you can
> automatically decrypt my signature and be sure it came from me. Just
> ask and I'll send it to you. Your email software can handle signing.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-users/6b16042c-dd2b-9757-2edc-1bbae0e7d911%40dewhirst.com.au
> <https://groups.google.com/d/msgid/django-users/6b16042c-dd2b-9757-2edc-1bbae0e7d911%40dewhirst.com.au?utm_medium=email_source=footer>
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CANd-%2BoD5Nrj1OxsSHvy8nVru5u1Hw1yWzJ19k7tAoEZOoovQBg%40mail.gmail.com.

Re: ModelAdmin

[Mike Dewhirst]

On 5/01/2023 5:43 am, Mario St-Gelais wrote:

Hello group, first post here.
Quick question.  Can capabilities of ModelAdmin such as list_filter or 
search_fields be used outside of the admin interface?


Have you looked at htmx?

https://www.simplecto.com/htmx-and-the-list_editable-in-django-admin/

htmx is very sweet. Essentially, you can replace a named id="whatever"> on an existing page by calling whatever view you 
care to write. Your view might have to borrow from the Django code if 
you really like what it does.


Digressing slightly, I discovered that you can make a link in html using 
the  entity and just replace href="/search" with 
hx_trigger="/hx_search", for example, so that the existing css works and 
it looks like an ordinary link.


Cheers

mike



I want a view that would allow non logged users to search a site 
through checkboxes and some search fields possibly and obviously, the 
way this is implemented in the admin view is rather good.


Alternatively, what approach can be used in django?

Thanks
Mario
--
You received this message because you are subscribed to the Google 
Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send 
an email to django-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CAFmF6_vLzivA3Y-sskqmcZzsuLc27opP6xW3m3wvmV7nepu%3D-A%40mail.gmail.com 
<https://groups.google.com/d/msgid/django-users/CAFmF6_vLzivA3Y-sskqmcZzsuLc27opP6xW3m3wvmV7nepu%3D-A%40mail.gmail.com?utm_medium=email_source=footer>.



--
Signed email is an absolute defence against phishing. This email has
been signed with my private key. If you import my public key you can
automatically decrypt my signature and be sure it came from me. Just
ask and I'll send it to you. Your email software can handle signing.

--
You received this message because you are subscribed to the Google Groups "Django 
users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/6b16042c-dd2b-9757-2edc-1bbae0e7d911%40dewhirst.com.au.


OpenPGP_signature
Description: OpenPGP digital signature

ModelAdmin

[Mario St-Gelais]

Hello group, first post here.
Quick question.  Can capabilities of ModelAdmin such as list_filter or
search_fields be used outside of the admin interface?

I want a view that would allow non logged users to search a site through
checkboxes and some search fields possibly and obviously, the way this is
implemented in the admin view is rather good.

Alternatively, what approach can be used in django?

Thanks
Mario

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CAFmF6_vLzivA3Y-sskqmcZzsuLc27opP6xW3m3wvmV7nepu%3D-A%40mail.gmail.com.

Curious about ModelAdmin internals.. how the hell does it work

[Michal Plsek]

Hello, I would like to know about this (although I hacked around it, but I 
am still curious):

if I have model which contains ForeignKey attribute and I am using 
autocomplete_fields on it, where is the found FK of foreign object saved on 
ModelAdmin page?
Numerical ID of foreign object represented by usual SELECTBOX is marked 
using **. I understand reasons why this is not 
done with autocomplete_fields, but I would presume the found value of FK 
would be saved in some* * or something like that, 
which is obviously not.

So, using autocomplete_fields, how can I get the found FK value on page?

(q on SO: 
https://stackoverflow.com/questions/69016647/where-is-id-saved-in-django-modeladmin-autocomplete-fields
 
)

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/b12187f2-af5c-4631-a20e-b7648c97e89bn%40googlegroups.com.

Re: How to hide/disable ModelAdmin

[zvo...@seznam.cz]

Seems I know the answer:

class HiddenAdmin(admin.ModelAdmin):
has_module_permission = lambda self, req: False

https://stackoverflow.com/questions/2431727/django-admin-hide-a-model
https://stackoverflow.com/questions/49293901/hide-model-from-main-admin-list-but-allow-creation-in-inline-editor
Dne čtvrtek 4. března 2021 v 21:22:41 UTC+1 uživatel zvo...@seznam.cz 
napsal:

> I want use Django 2+ autocomplete_fields.
> Adding them into (source) ModelAdmin will give lot of errors (see bellow).
> So I must add a (target) ModelAdmin with search_fields=...
>
> After that everything works.
> However I don't want to have such new ModelAdmin's visible/accessible.
> I have data of their models already much better accessible in Inlines.
>
> Is there a way how to give search_fields=.. and not show the new 
> ModelAdmin?
>
> Thank you.
>
> ```
> ERRORS: 
> : (admin.E039) An admin for model 
> "PartVariant" has to be registered to be referenced by 
> PartCodeInline.autocomplete_fields. 
> : (admin.E040) PartCodeTypeAdmin 
> must define "search_fields", because it's referenced by 
> PartCodeInline.autocomplete_fields. 
> : (admin.E039) An admin for model 
> "Size" has to be registered to be referenced by 
> PartSizeInline.autocomplete_fields. 
> : (admin.E039) An admin for 
> model "Size" has to be registered to be referenced by 
> PartSubGroupInline.autocomplete_fields.
> ```
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/98a443b2-15f7-4172-bd8e-1635dc98f30an%40googlegroups.com.

How to hide/disable ModelAdmin

[zvo...@seznam.cz]

I want use Django 2+ autocomplete_fields.
Adding them into (source) ModelAdmin will give lot of errors (see bellow).
So I must add a (target) ModelAdmin with search_fields=...

After that everything works.
However I don't want to have such new ModelAdmin's visible/accessible.
I have data of their models already much better accessible in Inlines.

Is there a way how to give search_fields=.. and not show the new ModelAdmin?

Thank you.

```
ERRORS: 
: (admin.E039) An admin for model 
"PartVariant" has to be registered to be referenced by 
PartCodeInline.autocomplete_fields. 
: (admin.E040) PartCodeTypeAdmin 
must define "search_fields", because it's referenced by 
PartCodeInline.autocomplete_fields. 
: (admin.E039) An admin for model 
"Size" has to be registered to be referenced by 
PartSizeInline.autocomplete_fields. 
: (admin.E039) An admin for 
model "Size" has to be registered to be referenced by 
PartSubGroupInline.autocomplete_fields.
```

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/2d5c4536-9e1f-49f6-93a9-31802a80e12cn%40googlegroups.com.

Re: ModelAdmin Not work

[John Rajesh]

First correct email to email
On 24 Sep 2020 00:33, "coolguy"  wrote:

> either use admin.site.register
> OR
> *@*admin.register(User)
>
> On Wednesday, September 23, 2020 at 11:01:43 AM UTC-4 kkwaq...@gmail.com
> wrote:
>
>> *models.py*
>>
>> [image: 1.jpg]
>>
>> *admin.py*
>>
>> *[image: 2.jpg]*
>>
>> *errors*
>>
>>
>> *[image: 3.jpg]*
>>
>> *Object is not callable*
>>
>> *Please any body solutions *
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/django-users/00354cdd-5478-4ee5-9e44-95098e393c83n%
> 40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CA%2BbM%2BwDz86eHRda1fXb4DHRjipVu7xJsqmWHKEaThpRsdMP5VA%40mail.gmail.com.

Re: ModelAdmin Not work

[coolguy]

either use admin.site.register
OR
*@*admin.register(User)

On Wednesday, September 23, 2020 at 11:01:43 AM UTC-4 kkwaq...@gmail.com 
wrote:

> *models.py*
>
> [image: 1.jpg]
>
> *admin.py*
>
> *[image: 2.jpg]*
>
> *errors*
>
>
> *[image: 3.jpg]*
>
> *Object is not callable*
>
> *Please any body solutions *
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/00354cdd-5478-4ee5-9e44-95098e393c83n%40googlegroups.com.

ModelAdmin Not work

[kkwaq...@gmail.com]

*models.py*

[image: 1.jpg]

*admin.py*

*[image: 2.jpg]*

*errors*


*[image: 3.jpg]*

*Object is not callable*

*Please any body solutions *

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/4e4ddd71-1b26-4976-a2a3-a19cf04f568an%40googlegroups.com.

ModelAdmin Media assets with django 1.8

[Amirouche Boubekki]

Using Django 1.8, I do not understand what is the behavior of `Media` [0] 
inside a `ModelAdmin` subclass.

In particular, whether the default behavior of form's media is applied in 
`ModelAdmin` that is: `extend=True` [1]

I am under the impression that the behavior is implemented in 
`options.ModelAdmin.media` property [2], maybe there is more to it than 
that since it has a custom metaclass.


Thanks in advance !

[0] 
https://docs.djangoproject.com/en/1.8/ref/contrib/admin/#modeladmin-asset-definitions
[1] https://docs.djangoproject.com/en/1.8/topics/forms/media/#extend
[2] 
https://github.com/django/django/blob/6a0dc2176f4ebf907e124d433411e52bba39a28e/django/contrib/admin/options.py#L636-L649

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/1235108b-e561-4866-970e-f899c3c3acf3o%40googlegroups.com.

Overriding change_list_results template per ModelAdmin

[Luka Jančin]

I have a model which is registered to two different admin sites with two 
ModelAdmins. 
I would like to override the template for change_list_results for each 
ModelAdmin independently. Currently it's not possible the same way you can 
do it for add_form_template, change_form_template etc. by overriding the 
appropriate member.
Is it possible to achieve this some other way?

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/d2dcfd18-9fc2-4789-9ab3-28754fc144dd%40googlegroups.com.

Re: How to override the ModelAdmin "change" form ?

[Mike Dewhirst]

On 2/03/2019 2:08 am, karim.at...@gmail.com wrote:

Hi Mike,

I tried what you wrote by overriding the *self.change_form_template* 
but the form does not appear.
Would you please provide me the content of your model admin 
*billing_payment_view ?*


Sure. I recently asked for assistance here and posted most of the code ...

https://groups.google.com/forum/#!topic/django-users/809HBmPa9vk

You are right, my application is different. My template contains a 
script provided by Stripe which calls their API to collect a credit card 
payment. But overall it isn't much different than any other template 
called by any other view. The view just takes a different path depending 
on whether it is a POST or a GET request. My view looks complex because 
when the user clicks [Pay now] it happens in the Stripe js embedded in 
the template and the Stripe API - in turn - hits my view with the actual 
POST containing the result of the credit card transaction. I had to seed 
the form/template with hidden data so it travelled across the Stripe 
boundary and back to me so I could complete the processing. If you can 
see past that complication it should be clear that I'm using the form to 
clean the data and the view to interface with the ORM/database.


It is working well for me now and I'm in the middle of writing unit tests.

Good luck



Thanks.

Karim

Le vendredi 1 mars 2019 00:06:40 UTC+1, Mike Dewhirst a écrit :

On 28/02/2019 9:46 pm, karim...@gmail.com  wrote:

Hi,

I'm currently struggling with a custom ModelAdmin.


Karim

I haven't tried to fully understand your use case. However, this
is what I think your process could be if you do not wish to ajax
it ...

1. Override the model save() method to call a model method which
detects your trigger scenario and calls the code you wish to
execute to collect all the data you wish to display. This might be
in the parent model or the m2m 'through' model. Unlikely to be in
the child model.

2. Write a Form to reveal the data you wish to display. It
probably needs to be a ModelForm

3. Write a template for the data including any hidden fields for
object pks and additionally consider calling {{ block.super }} to
display inherited stuff if you are extending another template and
using the same block. When I first started to work all this out I
was able to get my form to appear at the top of the ModelAdmin
form using block.super and spent a bit of time hiding the big red
[Delete] button because it was too close to my big blue [Pay now]
button. However, as I got deeper into it I somehow lost that and
never got it back. I was so pleased with getting it working
eventually that I persuaded myself I didn't really want it on the
same page anyway. Your mileage may vary :) I think you need to
hard-code the form in the ModelAdmin to get it appearing above
everything else.

4. Write any necessary urls

5. Write a view to manipulate your data, based on the request and
your form

6. Get the Admin to display it on demand. The first line of the
change_view() method below initialises the ModelAdmin to do
absolutely nothing different than usual. Nothing will happen
unless the trigger is detected. Then finally call to super to
resume the normal course of events when your code is complete.
What follows is my own recent experience. The comments should tell
you more than the code

def change_view(self, request, object_id, form_url='', extra_context=None):

     """ self = SubstanceAdmin
 request = wsgi request object
 object_id = substance
 form_url = no idea!
 extra_context = dict of apps, models, admin_urls and permissions

 https://docs.djangoproject.com/en/1.11/ref/contrib/admin/#django  
<https://docs.djangoproject.com/en/1.11/ref/contrib/admin/#django>.
 contrib.admin.ModelAdmin.change_view

     """
 # Let the ModelAdmin resume normal operations with its own template
 self.change_form_template = None
 # queryset of m2m records from the 'through' table
 ingredients = 
Substance_Ingredients.objects.filter(substance_id=object_id)
 subscription = None
 for sm2mi in ingredients:
 # sm2mi.fee_payable() is the detector which triggers the process
 payable, fee_type = sm2mi.fee_payable()  # eg., True, PAID_DATA
 if payable:
 # generate a subscription record with blank token field or
 # if one exists with a non-blank token, return None
 subscription = billing_subscribe(sm2mi, fee_type)
 if subscription:# collect money for the owner
 # switch the ModelAdmin to the new template
 self.change_form_template = 'payment.html'
 # assemble

Re: How to override the ModelAdmin "change" form ?

[karim . atiki]

Hi Mike,

I tried what you wrote by overriding the *self.change_form_template* but 
the form does not appear.
Would you please provide me the content of your model admin  
*billing_payment_view 
?*

Thanks.

Karim

Le vendredi 1 mars 2019 00:06:40 UTC+1, Mike Dewhirst a écrit :
>
> On 28/02/2019 9:46 pm, karim...@gmail.com  wrote:
>
> Hi, 
>
> I'm currently struggling with a custom ModelAdmin.
>
>
> Karim
>
> I haven't tried to fully understand your use case. However, this is what I 
> think your process could be if you do not wish to ajax it ...
>
> 1. Override the model save() method to call a model method which detects 
> your trigger scenario and calls the code you wish to execute to collect all 
> the data you wish to display. This might be in the parent model or the m2m 
> 'through' model. Unlikely to be in the child model.
>
> 2. Write a Form to reveal the data you wish to display. It probably needs 
> to be a ModelForm
>
> 3. Write a template for the data including any hidden fields for object 
> pks and additionally consider calling {{ block.super }} to display 
> inherited stuff if you are extending another template and using the same 
> block. When I first started to work all this out I was able to get my form 
> to appear at the top of the ModelAdmin form using block.super and spent a 
> bit of time hiding the big red [Delete] button because it was too close to 
> my big blue [Pay now] button. However, as I got deeper into it I somehow 
> lost that and never got it back. I was so pleased with getting it working 
> eventually that I persuaded myself I didn't really want it on the same page 
> anyway. Your mileage may vary :) I think you need to hard-code the form in 
> the ModelAdmin to get it appearing above everything else.
>
> 4. Write any necessary urls
>
> 5. Write a view to manipulate your data, based on the request and your form
>
> 6. Get the Admin to display it on demand. The first line of the 
> change_view() method below initialises the ModelAdmin to do absolutely 
> nothing different than usual. Nothing will happen unless the trigger is 
> detected. Then finally call to super to resume the normal course of events 
> when your code is complete. What follows is my own recent experience. The 
> comments should tell you more than the code
>
> def change_view(self, request, object_id, form_url='', extra_context=None):
>
> """ self = SubstanceAdmin
> request = wsgi request object
> object_id = substance
> form_url = no idea!
> extra_context = dict of apps, models, admin_urls and permissions
>
> https://docs.djangoproject.com/en/1.11/ref/contrib/admin/#django.
> contrib.admin.ModelAdmin.change_view 
>
> """
> # Let the ModelAdmin resume normal operations with its own template
> self.change_form_template = None
> # queryset of m2m records from the 'through' table
> ingredients = Substance_Ingredients.objects.filter(substance_id=object_id)
> subscription = None
> for sm2mi in ingredients:
> # sm2mi.fee_payable() is the detector which triggers the process
> payable, fee_type = sm2mi.fee_payable()  # eg., True, PAID_DATA
> if payable:
> # generate a subscription record with blank token field or
>     # if one exists with a non-blank token, return None
> subscription = billing_subscribe(sm2mi, fee_type)
> if subscription:# collect money for the owner
> # switch the ModelAdmin to the new template
> self.change_form_template = 'payment.html'
> # assemble all the necessary data for the view
> context = billing_collect_context(
> sm2mi,
> subscription,
> )
> # get everything into the payment_view context
> if not extra_context:
> extra_context = dict()
> extra_context.update(self.admin_site.each_context(request))
> extra_context.update(context)
> # wrap the view to protect it with Admin permissions
> self.admin_site.admin_view(
> # call the view with request and context
> billing_payment_view(
> request,
> sm2mi,
> subscription,
> context=extra_context,
> )
> )
> # only one sm2mi at a time
> break
> return super(SubstanceAdmin, self).change_view(
> request, object_id, form_url, extra_context
> )

Re: How to override the ModelAdmin "change" form ?

[karim . atiki]

Hi Mike,

Thanks a lot for your feedback.
Your situation is quiet different from mine, BUT the way you override 
change_view and the related template will certainly help me to achieve what 
I need.
...and getting rid of dirty and unnecessary ajax calls.

I keep you posted.

Thx.

Karim

Le vendredi 1 mars 2019 00:06:40 UTC+1, Mike Dewhirst a écrit :
>
> On 28/02/2019 9:46 pm, karim...@gmail.com  wrote:
>
> Hi, 
>
> I'm currently struggling with a custom ModelAdmin.
>
>
> Karim
>
> I haven't tried to fully understand your use case. However, this is what I 
> think your process could be if you do not wish to ajax it ...
>
> 1. Override the model save() method to call a model method which detects 
> your trigger scenario and calls the code you wish to execute to collect all 
> the data you wish to display. This might be in the parent model or the m2m 
> 'through' model. Unlikely to be in the child model.
>
> 2. Write a Form to reveal the data you wish to display. It probably needs 
> to be a ModelForm
>
> 3. Write a template for the data including any hidden fields for object 
> pks and additionally consider calling {{ block.super }} to display 
> inherited stuff if you are extending another template and using the same 
> block. When I first started to work all this out I was able to get my form 
> to appear at the top of the ModelAdmin form using block.super and spent a 
> bit of time hiding the big red [Delete] button because it was too close to 
> my big blue [Pay now] button. However, as I got deeper into it I somehow 
> lost that and never got it back. I was so pleased with getting it working 
> eventually that I persuaded myself I didn't really want it on the same page 
> anyway. Your mileage may vary :) I think you need to hard-code the form in 
> the ModelAdmin to get it appearing above everything else.
>
> 4. Write any necessary urls
>
> 5. Write a view to manipulate your data, based on the request and your form
>
> 6. Get the Admin to display it on demand. The first line of the 
> change_view() method below initialises the ModelAdmin to do absolutely 
> nothing different than usual. Nothing will happen unless the trigger is 
> detected. Then finally call to super to resume the normal course of events 
> when your code is complete. What follows is my own recent experience. The 
> comments should tell you more than the code
>
> def change_view(self, request, object_id, form_url='', extra_context=None):
>
> """ self = SubstanceAdmin
> request = wsgi request object
> object_id = substance
> form_url = no idea!
> extra_context = dict of apps, models, admin_urls and permissions
>
> https://docs.djangoproject.com/en/1.11/ref/contrib/admin/#django.
> contrib.admin.ModelAdmin.change_view 
>
> """
> # Let the ModelAdmin resume normal operations with its own template
> self.change_form_template = None
> # queryset of m2m records from the 'through' table
> ingredients = Substance_Ingredients.objects.filter(substance_id=object_id)
> subscription = None
> for sm2mi in ingredients:
> # sm2mi.fee_payable() is the detector which triggers the process
> payable, fee_type = sm2mi.fee_payable()  # eg., True, PAID_DATA
> if payable:
> # generate a subscription record with blank token field or
>     # if one exists with a non-blank token, return None
> subscription = billing_subscribe(sm2mi, fee_type)
> if subscription:# collect money for the owner
> # switch the ModelAdmin to the new template
> self.change_form_template = 'payment.html'
> # assemble all the necessary data for the view
> context = billing_collect_context(
> sm2mi,
> subscription,
> )
> # get everything into the payment_view context
> if not extra_context:
> extra_context = dict()
> extra_context.update(self.admin_site.each_context(request))
> extra_context.update(context)
> # wrap the view to protect it with Admin permissions
> self.admin_site.admin_view(
> # call the view with request and context
> billing_payment_view(
> request,
> sm2mi,
> subscription,
> context=extra_context,
> )
> )
> # only one sm2mi at a time
> break
> return super(SubstanceAdmin, self).change_vi

Re: How to override the ModelAdmin "change" form ?

[Mike Dewhirst]

  
  
On 28/02/2019 9:46 pm,
  karim.at...@gmail.com wrote:


  
  Hi,


I'm currently struggling with a custom ModelAdmin.
  


Karim

I haven't tried to fully understand your use case. However, this is
what I think your process could be if you do not wish to ajax it ...

1. Override the model save() method to call a model method which
detects your trigger scenario and calls the code you wish to execute
to collect all the data you wish to display. This might be in the
parent model or the m2m 'through' model. Unlikely to be in the child
model.

2. Write a Form to reveal the data you wish to display. It probably
needs to be a ModelForm

3. Write a template for the data including any hidden fields for
object pks and additionally consider calling {{ block.super }} to
display inherited stuff if you are extending another template and
using the same block. When I first started to work all this out I
was able to get my form to appear at the top of the ModelAdmin form
using block.super and spent a bit of time hiding the big red
[Delete] button because it was too close to my big blue [Pay now]
button. However, as I got deeper into it I somehow lost that and
never got it back. I was so pleased with getting it working
eventually that I persuaded myself I didn't really want it on the
same page anyway. Your mileage may vary :) I think you need to
hard-code the form in the ModelAdmin to get it appearing above
everything else.

4. Write any necessary urls

5. Write a view to manipulate your data, based on the request and
your form

6. Get the Admin to display it on demand. The first line of the
change_view() method below initialises the ModelAdmin to do
absolutely nothing different than usual. Nothing will happen unless
the trigger is detected. Then finally call to super to resume the
normal course of events when your code is complete. What follows is
my own recent experience. The comments should tell you more than the
code

def change_view(self, request, object_id, form_url='', extra_context=None):
    """ self = SubstanceAdmin
request = wsgi request object
object_id = substance
form_url = no idea!
extra_context = dict of apps, models, admin_urls and permissions

https://docs.djangoproject.com/en/1.11/ref/contrib/admin/#django.
contrib.admin.ModelAdmin.change_view 

    """
# Let the ModelAdmin resume normal operations with its own template
    self.change_form_template = None
# queryset of m2m records from the 'through' table
ingredients = Substance_Ingredients.objects.filter(substance_id=object_id)
subscription = None
for sm2mi in ingredients:
# sm2mi.fee_payable() is the detector which triggers the process
payable, fee_type = sm2mi.fee_payable()  # eg., True, PAID_DATA
if payable:
# generate a subscription record with blank token field or
# if one exists with a non-blank token, return None
subscription = billing_subscribe(sm2mi, fee_type)
if subscription:# collect money for the owner
    # switch the ModelAdmin to the new template
self.change_form_template = 'payment.html'
# assemble all the necessary data for the view
context = billing_collect_context(
sm2mi,
subscription,
)
# get everything into the payment_view context
if not extra_context:
extra_context = dict()
extra_context.update(self.admin_site.each_context(request))
extra_context.update(context)
# wrap the view to protect it with Admin permissions
self.admin_site.admin_view(
# call the view with request and context
billing_payment_view(
request,
sm2mi,
subscription,
context=extra_context,
)
)
# only one sm2mi at a time
break
return super(SubstanceAdmin, self).change_view(
request, object_id, form_url, extra_context
)



 
7. Call super in the model save() method *or* raise an exception to
prevent saving. I'm actually not sure about this bit. It may go
against the Django flow. However, I do use a BusinessRuleViolation
exception which inherits from ValidationError and therefore lets me
include a human readable message which appears in the Admin and
*seems* to prevent saving. You would need to test this especially
with m2m side-effects and atomicity consequences.

I 

Re: How to override the ModelAdmin "change" form ?

[Nelson Varela]

You maybe want a model admin view where you can send the user to and 
collect the data you want to comare and show warnings

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/2b4e6166-2f8a-40f0-9f0d-a5c7c8df494e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

How to override the ModelAdmin "change" form ?

[karim . atiki]

Hi,

I'm currently struggling with a custom ModelAdmin.

Considering the following model:


# Bloc fonctionnel
class Assembly(Item):

product = models.ForeignKey(to='ProductFamily', on_delete=models.CASCADE
, null=True, verbose_name=_('Famille Produit'))
functions = models.ManyToManyField(Function, verbose_name=_('Fonctions'
))
*performances* = models.ManyToManyField(Performance, verbose_name=_(
'Performances'), related_name='performances')

def _get_type(self):
return ItemType.ASSEMBLY

class Meta:
verbose_name = _('Bloc Fonctionnel')
verbose_name_plural = _('Blocs Fonctionnels')



I have a custom AssemblyAdmin related to it and also a custom AssemblyForm 
for customizing some fieds.

The *performances* m2m field is critical.  
The performances are captured in the form with a dynamic_raw_id field, 
which works fine.

But when this field is modified, some updates/deletions might be applied in 
other tables of the database.
For this purpose, I need to collect the "performance" pk captured in the 
html form and compare them with those currently in the database.

Basically, when the user clicks on the regular "Save" or "Save and 
continue" button, I would need to display an alert form (like when you 
click on the delete button) to explain what would happen.

I struggled with some ajax routines but it does not work as expected. 

I don't know if it's really doable and how to achieve it.

Any suggestion is welcome.

Cheers.

Z.







-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/88135218-a965-46c8-a454-c0376a5682f1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Django ModelAdmin ignores has_delete_permission

[Daniel Germano Travieso]

Hello!

Ordinary staff users on the main django admin module are just standard 
django users that can access the admin site.

Setting the has_add_permission, has_change_permission and 
has_delete_permission via the ModelAdmin should be done to customize the 
permissions for specific object instances (as stated on the documentation 
https://docs.djangoproject.com/en/1.11/topics/auth/default/#topic-authorization 
)

The propper way to set the default permissions for a ordinary staff user 
should be either by assigning user/group permissions via 
- the superuser user on the admin site 
- via command line using the myuser.user_permissions.set([permission_list]) 
or myuser.user_permissions.add() or .remove() or using 
myuser.groups.set([group_list]) and myuser.groups.add(group1, group2) / 
.remove(group1, group2).
- programatically on specific staff user creation, using the same methods 
as the above

Either option should give the staff user the propper permissions to a 
specific model. The default permissions for a specific model always are 
named, for a app with app_label foo, as follows: foo.add_bar, 
foo.change_bar and foo.delete_bar where bar is the lowercase name for the 
specific model.

I encourage you to read on the Official Django Documentation for the topic 
of authorization as it provides these and other insights.

Hope it helps!

On Friday, May 18, 2018 at 4:36:07 AM UTC-3, Vitaly Trifanov wrote:
>
> I have simple project on Django 1.11.13, that uses ordinary Django's admin 
> module. Staff user can not delete object while is permitted 
> (has_delete_permission returns always true).
>
> models.py:
>
>
> class MyModel(models.Model):
> name = models.IntegerField("Value", blank=True, null=True)
>
> admin.py:
>
>
> @admin.register(MyModel)class MyModelAdmin(admin.ModelAdmin):
> def has_add_permission(self, request):
> return True
>
> def has_change_permission(self, request, obj=None):
> return True
>
> def has_delete_permission(self, request, obj=None):
> return True
>
>
> I created user and logged in. He can create MyModel object (as expected), 
> can edit (as expected), but can not delete!!
>
> That's what I see if I try to delete it:
>
> Deleting the selected my model would result in deleting related objects, 
> but your account doesn't have permission to delete the following types of 
> objects:
>
> my model
>
> What am I doing wrong? How should I give permissions to delete MyModels to 
> ordinary staff user?
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/35bafb48-34c8-418a-9f70-10dbb6f54868%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Django ModelAdmin ignores has_delete_permission

[Vitaly Trifanov]

I have simple project on Django 1.11.13, that uses ordinary Django's admin 
module. Staff user can not delete object while is permitted 
(has_delete_permission returns always true).

models.py:


class MyModel(models.Model):
name = models.IntegerField("Value", blank=True, null=True)

admin.py:


@admin.register(MyModel)class MyModelAdmin(admin.ModelAdmin):
def has_add_permission(self, request):
return True

def has_change_permission(self, request, obj=None):
return True

def has_delete_permission(self, request, obj=None):
return True


I created user and logged in. He can create MyModel object (as expected), 
can edit (as expected), but can not delete!!

That's what I see if I try to delete it:

Deleting the selected my model would result in deleting related objects, 
but your account doesn't have permission to delete the following types of 
objects:

my model

What am I doing wrong? How should I give permissions to delete MyModels to 
ordinary staff user?

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/f2a89d70-b488-4584-8fad-0d5b7a5d20e5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Add extra fields to a ModelAdmin form

[Mark Phillips]

James,

I was finally able to add extra fields to a ModelForm dynamically! Check
out the answer to this post -
https://stackoverflow.com/questions/32335349/how-do-i-create-and-save-dynamic-fields-in-django-modeladmin

It worked for me in django 2. I have not tried it in django 1.11.

I hope this help!

Mark

On Wed, May 2, 2018 at 9:12 AM, 'James Foley' via Django users <
django-users@googlegroups.com> wrote:

> Hey Mark,
>
> I've not actually found a solution yet, I've just sort of put it at the
> bottom of my pile of problems...
>
> Here is the post that I used to get where I am https://stackoverflow.com/
> a/35797311/3173119
>
> It just doesn't feel very Django like, and I feel that there must be an
> easier way to simply add a non-model field to a model admin form. My fields
> are also added at run time which is whats causing me issues.
>
> My actual goal is to convert a flat JSON string stored in a JSON field,
> into fields for each key. Then once saved it coverts them all back into a
> JSON string and stored them back on the one JSON field.
>
> James.
>
> On Wednesday, 2 May 2018 16:02:51 UTC+1, mark wrote:
>>
>> James,
>>
>> Did you ever get a response to this issue? I am having a devil of a time
>> adding some extra non-model fields to an admin inline form. My added
>> complication is that the fields are only defined at run time, so I have to
>> have a loop that creates them based on a different model in my app.
>>
>> Would you be willing to share your code with me? In particular, I am not
>> sure where and how you are using self.form.declared_fields.
>>
>> I am running django 1.11.
>>
>> Thanks!
>>
>> Mark
>>
>> On Mon, Apr 30, 2018 at 1:41 AM, 'James Foley' via Django users <
>> django...@googlegroups.com> wrote:
>>
>>> So, I have a ModelAdmin that I need to add extra fields to. These fields
>>> do not exist on the model, but will be dynamically added to a custom
>>> ModelForm through the __init__ method, and logic inside clean will handle
>>> the returned data on save.
>>>
>>> I can't seem to find any solid information related to adding custom
>>> non-model fields to a ModelAdmin form. The closest I have come is by
>>> overriding get_fields on the ModelAdmin class and updating
>>> self.form.declared_fields with the new fields I'd like to add.
>>>
>>> This just doesn't feel very clean to me and I was curious if there was a
>>> better way to add new fields to a ModelAdmin dynamically?
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Django users" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to django-users...@googlegroups.com.
>>> To post to this group, send email to django...@googlegroups.com.
>>> Visit this group at https://groups.google.com/group/django-users.
>>> To view this discussion on the web visit https://groups.google.com/d/ms
>>> gid/django-users/a590e54f-1f36-497b-b508-cba339c5f2fc%40googlegroups.com
>>> <https://groups.google.com/d/msgid/django-users/a590e54f-1f36-497b-b508-cba339c5f2fc%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>> --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-users+unsubscr...@googlegroups.com.
> To post to this group, send email to django-users@googlegroups.com.
> Visit this group at https://groups.google.com/group/django-users.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/django-users/9889680c-d447-4217-bc37-fc394772b512%40googlegroups.com
> <https://groups.google.com/d/msgid/django-users/9889680c-d447-4217-bc37-fc394772b512%40googlegroups.com?utm_medium=email_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CAEqej2Oac8tc2Nv7ozE4eV6p%3DF5%3DagPhSaExxtGqQXwoEXZeDw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Admin site and ModelAdmin

[Mike Dewhirst]

On 4/05/2018 7:02 AM, jt.oldn...@gmail.com wrote:

Thanks for the response Mike.

I generally don't like it when a design has to change to fit a framework,


I agree. My design is almost entirely in the models. I want an API to be 
able to work without Django forms.


however, in this case I decided to try your solution. I ran into a 
couple of problems though :-(
 1) The fields that I'm looking up were required fields. Validation 
failed and error messages were displayed until I changed my model to 
not require those fields (which creates other problems I'd need to 
fix). Is there a way to hook in before validation?


Maybe but not in the model. I think you should be able to intercept form 
validation. But see below.


I over-road the model save function. Would the pre-save signal method 
fix this problem?

No

Or maybe ModelAdmin.save_model?

Don't know. Possibly.

Django forms automatically do all the python-wise cleaning of data prior 
to the model's save() being called by the form If you are putting data 
independently from the form into fields inside the save() method (or via 
a pre_save hook) you have to be certain it is valid data.


I might be wrong but I don't think there is any effective difference 
between pre and post save signals and my approach. Maybe transaction 
management. Maybe not. This is my exact substance.save() method ...


    def save(self, *args, **kwargs):
    links = self._pre_save()
    super(Substance, self).save(*args, **kwargs)
    self._post_save(links)
    self._post_post_save()

Stuff which occurs in _pre_save() happens before the record is saved to 
the database. For example, the record may not yet have a primary key 
because it is new and hasn't ever been saved to the database. Stuff in 
_post_save() and _post_post_save() happens afterwards. I use those to 
create related records if required because by then (under normal circs) 
I can guarantee self.id is no longer null.


The last thing which happens prior to save() is the model's clean() 
method (if it exists) is called by the form. I put checks in there to be 
certain data in whatever fields I care deeply about is valid and raise a 
ValidationError if not. If that happens, the save() is aborted and the 
user has to fix the problem before trying again. Here is an example ...


    def clean(self):
    if self.physical_state is None:
    raise ValidationError('Physical form is required')

If you are getting external data you have no choice but to be certain it 
is good data. You need to validate it Python-wise en route to the 
destination model fields, perhaps in _pre_save() and business-rule-wise 
in Employee.clean()


The actual validation checks can be factored out and called from clean() 
or anywhere else such as save().


The actual sequence of events (form calls model.clean() before 
model.save()) indicates to me that Employee.clean() ought to be able to 
insert (clean) data into Employee fields before running its own business 
rule validation. However, whenever I have tried this I haven't been 
successful. Therefore I'm missing something. Maybe transaction 
management. Maybe someone can enlighten me?


A side note is that if you are not using a form, clean() does not get 
called. This matters for unit testing where there is no form. You have 
to deliberately call clean() to get the benefit of any checks.


 2) The desired result of the lookup would be to display the change 
form so that the information could be verified.


Sorry but that implies javascript and an API to fetch the data for 
verification if you want to do it all at once.


OTOH maybe you could save the Employee model without the external data 
and use a separate 1:1 model to carry it. That could be fetched 
separately after the Emplyee.save() has run. In my scenario it would be 
fetched in the _post_save() method and verified python-wise in there 
before adding the 1:1 model if it didn't already exist. The Employee 
would need to be saved again so the 1:1 model gets saved. The 1:1 model 
could check the business rule logic in its clean() method. Maybe the 
advantage here would be splitting the activity into separate atomic 
transactions and a 1:1 model validation error wouldn't interrupt the 
preceding Employee.save()


In other words, if doing the lookup, 'SAVE' (and 'Save and add 
another') should behave as if 'Save and continue editing' had been 
selected.


There is no save/clean difference between any of those. Just what 
happens next in the Admin.





--
You received this message because you are subscribed to the Google 
Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send 
an email to django-users+unsubscr...@googlegroups.com 
.
To post to this group, send email to django-users@googlegroups.com 
.

Visit this group at https://groups.google.com/group/django-users.
To view this 

Re: Admin site and ModelAdmin

[jt . oldnews]

Thanks for the response Mike.

I generally don't like it when a design has to change to fit a framework, 
however, in this case I decided to try your solution. I ran into a couple 
of problems though :-(
 1) The fields that I'm looking up were required fields. Validation failed 
and error messages were displayed until I changed my model to not require 
those fields (which creates other problems I'd need to fix). Is there a way 
to hook in before validation? I over-road the model save function. Would 
the pre-save signal method fix this problem? Or maybe ModelAdmin.save_model?
 2) The desired result of the lookup would be to display the change form so 
that the information could be verified. In other words, if doing the 
lookup, 'SAVE' (and 'Save and add another') should behave as if 'Save and 
continue editing' had been selected.


-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/26f88b4c-b2dd-4bce-aea7-d885295aa609%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Admin site and ModelAdmin

[Mike Dewhirst]

On 3/05/2018 10:33 AM, Mike Dewhirst wrote:

On 3/05/2018 7:00 AM, jt.oldn...@gmail.com wrote:
I'm new to Django and web development in general (C++ background) and 
I've got amazingly far very quickly, but there's one thing I've been 
struggling with for a couple days now :-(. Forgive me if I screw up 
the lingo.


I've got a ModelAdmin page for registrants of a conference which has 
fields for Employee ID, Name, email etc. The registrant does not have 
to be an employee, but if they are I could lookup their name, email 
etc. from an external source (already have the Python code for this). 
I'd like to have a button next to the employee id field which would 
lookup the employee's details and fill in the appropriate fields. 
This seems to me that it shouldn't be too hard but I am spinning my 
wheels here.  Do I need to ditch ModelAdmin?  Can someone please 
point me in the right direction.


You may not need a button which, in the Admin, implies javascript and 
an API. In your model you can intercept the save() method to visit 
another database/system to fetch the detail before the record is 
saved. There are probably many ways to do this. One uses a pre-save 
signal [1] but I prefer to override save() [2].


class Employee(models.Model):

    ... all the fields etc

    fetchdata = models.BooleanField(default=False, blank=True)

    def save(self, *args, **kwargs):
    if self.fetchdata:
    self.fetchdata = False
            try:
        self.this, self.that = self.fetch_data()
    except Exception:
    # avoid losing other changes
    pass

 super(Employee, self).save(*args, **kwargs)

Sorry - should have read what I pasted in


super(Substance, self).save(*args, **kwargs)

    def fetch_data(self):
        #call external database with employee ID and return necessary 
detail

    return this, that

[1] https://docs.djangoproject.com/en/1.11/ref/signals/#pre-save
[2] 
https://docs.djangoproject.com/en/2.0/ref/models/instances/#saving-objects


hth



Thanks,
JT
--
You received this message because you are subscribed to the Google 
Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, 
send an email to django-users+unsubscr...@googlegroups.com 
<mailto:django-users+unsubscr...@googlegroups.com>.
To post to this group, send email to django-users@googlegroups.com 
<mailto:django-users@googlegroups.com>.

Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/1324e38c-ed15-4f3c-8e1e-cd7df220b96e%40googlegroups.com 
<https://groups.google.com/d/msgid/django-users/1324e38c-ed15-4f3c-8e1e-cd7df220b96e%40googlegroups.com?utm_medium=email_source=footer>. 


For more options, visit https://groups.google.com/d/optout.




--
You received this message because you are subscribed to the Google Groups "Django 
users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/88249111-78d2-5076-0ea9-b0cb5d5d5ae6%40dewhirst.com.au.
For more options, visit https://groups.google.com/d/optout.

Re: Admin site and ModelAdmin

[Mike Dewhirst]

On 3/05/2018 7:00 AM, jt.oldn...@gmail.com wrote:
I'm new to Django and web development in general (C++ background) and 
I've got amazingly far very quickly, but there's one thing I've been 
struggling with for a couple days now :-(. Forgive me if I screw up 
the lingo.


I've got a ModelAdmin page for registrants of a conference which has 
fields for Employee ID, Name, email etc. The registrant does not have 
to be an employee, but if they are I could lookup their name, email 
etc. from an external source (already have the Python code for this). 
I'd like to have a button next to the employee id field which would 
lookup the employee's details and fill in the appropriate fields. This 
seems to me that it shouldn't be too hard but I am spinning my wheels 
here.  Do I need to ditch ModelAdmin?  Can someone please point me in 
the right direction.


You may not need a button which, in the Admin, implies javascript and an 
API. In your model you can intercept the save() method to visit another 
database/system to fetch the detail before the record is saved. There 
are probably many ways to do this. One uses a pre-save signal [1] but I 
prefer to override save() [2].


class Employee(models.Model):

    ... all the fields etc

    fetchdata = models.BooleanField(default=False, blank=True)

    def save(self, *args, **kwargs):
    if self.fetchdata:
    self.fetchdata = False
            try:
        self.this, self.that = self.fetch_data()
    except Exception:
    # avoid losing other changes
    pass
    super(Substance, self).save(*args, **kwargs)

    def fetch_data(self):
        #call external database with employee ID and return necessary 
detail

    return this, that

[1] https://docs.djangoproject.com/en/1.11/ref/signals/#pre-save
[2] 
https://docs.djangoproject.com/en/2.0/ref/models/instances/#saving-objects


hth



Thanks,
JT
--
You received this message because you are subscribed to the Google 
Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send 
an email to django-users+unsubscr...@googlegroups.com 
<mailto:django-users+unsubscr...@googlegroups.com>.
To post to this group, send email to django-users@googlegroups.com 
<mailto:django-users@googlegroups.com>.

Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/1324e38c-ed15-4f3c-8e1e-cd7df220b96e%40googlegroups.com 
<https://groups.google.com/d/msgid/django-users/1324e38c-ed15-4f3c-8e1e-cd7df220b96e%40googlegroups.com?utm_medium=email_source=footer>.

For more options, visit https://groups.google.com/d/optout.


--
You received this message because you are subscribed to the Google Groups "Django 
users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/add76f8e-b999-e9df-be5f-01bd2de26c3f%40dewhirst.com.au.
For more options, visit https://groups.google.com/d/optout.

Admin site and ModelAdmin

[jt . oldnews]

I'm new to Django and web development in general (C++ background) and I've 
got amazingly far very quickly, but there's one thing I've been struggling 
with for a couple days now :-(. Forgive me if I screw up the lingo.

I've got a ModelAdmin page for registrants of a conference which has fields 
for Employee ID, Name, email etc. The registrant does not have to be an 
employee, but if they are I could lookup their name, email etc. from an 
external source (already have the Python code for this). I'd like to have a 
button next to the employee id field which would lookup the employee's 
details and fill in the appropriate fields. This seems to me that it 
shouldn't be too hard but I am spinning my wheels here.  Do I need to ditch 
ModelAdmin?  Can someone please point me in the right direction.

Thanks,
JT

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/1324e38c-ed15-4f3c-8e1e-cd7df220b96e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Add extra fields to a ModelAdmin form

['James Foley' via Django users]

Hey Mark,

I've not actually found a solution yet, I've just sort of put it at the 
bottom of my pile of problems...

Here is the post that I used to get where I 
am https://stackoverflow.com/a/35797311/3173119

It just doesn't feel very Django like, and I feel that there must be an 
easier way to simply add a non-model field to a model admin form. My fields 
are also added at run time which is whats causing me issues.

My actual goal is to convert a flat JSON string stored in a JSON field, 
into fields for each key. Then once saved it coverts them all back into a 
JSON string and stored them back on the one JSON field.

James.

On Wednesday, 2 May 2018 16:02:51 UTC+1, mark wrote:
>
> James,
>
> Did you ever get a response to this issue? I am having a devil of a time 
> adding some extra non-model fields to an admin inline form. My added 
> complication is that the fields are only defined at run time, so I have to 
> have a loop that creates them based on a different model in my app. 
>
> Would you be willing to share your code with me? In particular, I am not 
> sure where and how you are using self.form.declared_fields. 
>
> I am running django 1.11.
>
> Thanks!
>
> Mark
>
> On Mon, Apr 30, 2018 at 1:41 AM, 'James Foley' via Django users <
> django...@googlegroups.com > wrote:
>
>> So, I have a ModelAdmin that I need to add extra fields to. These fields 
>> do not exist on the model, but will be dynamically added to a custom 
>> ModelForm through the __init__ method, and logic inside clean will handle 
>> the returned data on save.
>>
>> I can't seem to find any solid information related to adding custom 
>> non-model fields to a ModelAdmin form. The closest I have come is by 
>> overriding get_fields on the ModelAdmin class and updating 
>> self.form.declared_fields with the new fields I'd like to add. 
>>
>> This just doesn't feel very clean to me and I was curious if there was a 
>> better way to add new fields to a ModelAdmin dynamically?
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Django users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to django-users...@googlegroups.com .
>> To post to this group, send email to django...@googlegroups.com 
>> .
>> Visit this group at https://groups.google.com/group/django-users.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/django-users/a590e54f-1f36-497b-b508-cba339c5f2fc%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/django-users/a590e54f-1f36-497b-b508-cba339c5f2fc%40googlegroups.com?utm_medium=email_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/9889680c-d447-4217-bc37-fc394772b512%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Add extra fields to a ModelAdmin form

[Mark Phillips]

James,

Did you ever get a response to this issue? I am having a devil of a time
adding some extra non-model fields to an admin inline form. My added
complication is that the fields are only defined at run time, so I have to
have a loop that creates them based on a different model in my app.

Would you be willing to share your code with me? In particular, I am not
sure where and how you are using self.form.declared_fields.

I am running django 1.11.

Thanks!

Mark

On Mon, Apr 30, 2018 at 1:41 AM, 'James Foley' via Django users <
django-users@googlegroups.com> wrote:

> So, I have a ModelAdmin that I need to add extra fields to. These fields
> do not exist on the model, but will be dynamically added to a custom
> ModelForm through the __init__ method, and logic inside clean will handle
> the returned data on save.
>
> I can't seem to find any solid information related to adding custom
> non-model fields to a ModelAdmin form. The closest I have come is by
> overriding get_fields on the ModelAdmin class and updating
> self.form.declared_fields with the new fields I'd like to add.
>
> This just doesn't feel very clean to me and I was curious if there was a
> better way to add new fields to a ModelAdmin dynamically?
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-users+unsubscr...@googlegroups.com.
> To post to this group, send email to django-users@googlegroups.com.
> Visit this group at https://groups.google.com/group/django-users.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/django-users/a590e54f-1f36-497b-b508-cba339c5f2fc%40googlegroups.com
> <https://groups.google.com/d/msgid/django-users/a590e54f-1f36-497b-b508-cba339c5f2fc%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CAEqej2NFGCaTbL2%3Dp8mBGbQfYGqjM4RbRYE5WOxK90zZL-ArsA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Add extra fields to a ModelAdmin form

['James Foley' via Django users]

So, I have a ModelAdmin that I need to add extra fields to. These fields do 
not exist on the model, but will be dynamically added to a custom ModelForm 
through the __init__ method, and logic inside clean will handle the 
returned data on save.

I can't seem to find any solid information related to adding custom 
non-model fields to a ModelAdmin form. The closest I have come is by 
overriding get_fields on the ModelAdmin class and updating 
self.form.declared_fields with the new fields I'd like to add. 

This just doesn't feel very clean to me and I was curious if there was a 
better way to add new fields to a ModelAdmin dynamically?

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/a590e54f-1f36-497b-b508-cba339c5f2fc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: How to get ModelAdmin given a Model

[Edouard C.]

'type(v)' is model..instead of 'v is model' works,
in case not too late for someone else...
thanks Matt..

def get_admin(model):
for k,v in admin.site._registry.iteritems():

if type(v) is model:
return v


On Monday, January 11, 2010 at 9:37:47 PM UTC, Matt Schinckel wrote:
>
> On Jan 12, 4:11 am, Tomasz Zieliński
> <tomasz.zielin...@pyconsultant.eu> wrote:
> > On 11 Sty, 16:23, Marco Rogers <marco.rog...@gmail.com> wrote:
> >
> > > I'm reposting this from earlier to see if I have better luck. I need
> > > to be able to get the ModelAdmin associated with a model at runtime.
> > > Similar to how django.db.models.get_model allows you to retrieve a
> > > model.
> >
> > > admin_class = get_admin(Model)
> >
> > > Is this possible?
> >
> > > The original post has more info.
> >
> > >http://groups.google.com/group/django-users/browse_thread/thread/0cd0.
> ..
> >
> > Maybe something like this:
> >
> > 1. Write something like django.contrib.admin.autodiscover, to get all
> > ModelAdmins
> > 2. Iterate those ModelAdmins, retrieve models they are attached to and
> > store this mapping in a dict.
> > 3. def get_admin(model):
> > return admin_to_model[model]
>
> You should be able to iterate through admin.site._registry, and pull
> out the one you need.
>
> from django.contrib import admin
> def get_admin(model):
> for k,v in admin.site._registry.iteritems():
> if v is model:
> return v
>
> Written in a browser.
>
> Matt.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/8f5d1af4-3792-44f6-b8a4-f0fc1dbf8b6d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: ModelAdmin Media JS file order issue in Django 2.0

[Andréas Kühne]

Checking through the documents I found the following reference:

https://docs.djangoproject.com/en/2.0/topics/forms/media/#order-of-assets

Changed in Django 2.0:

In older versions, the assets of Media objects are concatenated rather than
merged in a way that tries to preserve the relative ordering of the
elements in each list.


I'm guessing that this is your problem.

>From what I understand in this context, the:

**
import seems to be added in a previous dependent form and therefore is not
added again - you should probably check if the file is added somewhere else?

Best regards,

Andréas

2017-12-10 15:47 GMT+01:00 Marc R :

> because they are specific to only a few models, particularly the loading
> scripts, and options, etc.  this worked great in Django 1.11
>
>
> On Sunday, 10 December 2017 09:36:56 UTC-5, Etienne Robillard wrote:
>
>> Why don't you simply put the javascripts into your base template without
>> using Python ?
>>
>> Etienne
>>
>> Le 2017-12-10 à 09:30, Marc R a écrit :
>>
>> I have this in my model:
>>
>> class Media:
>> js = (
>>* '/static/plugins/codemirror/lib/codemirror.js',*
>> '/static/plugins/codemirror/mode/htmlmixed/htmlmixed.js',
>> '/static/plugins/codemirror/addon/fold/foldcode.js',
>> '/static/plugins/codemirror/addon/fold/foldgutter.js',
>> '/static/plugins/codemirror/addon/fold/brace-fold.js',
>> '/static/plugins/codemirror/addon/fold/indent-fold.js',
>> '/static/plugins/codemirror/addon/fold/comment-fold.js',
>> '/static/plugins/codemirror/addon/fold/xml-fold.js',
>> '/static/plugins/codemirror/addon/comment/comment.js',
>> '/static/plugins/codemirror/addon/edit/matchbrackets.js',
>> '/static/plugins/codemirror/addon/edit/matchtags.js',
>> '/static/plugins/codemirror/mode/javascript/javascript.js',
>> '/static/plugins/codemirror/mode/xml/xml.js',
>> '/static/plugins/codemirror/mode/htmlmixed/htmlmixed.js',
>> '/static/plugins/codemirror/addon/display/fullscreen.js',
>> '/static/js/admin/syslog/syslog_change_form.min.js'
>> )
>>
>> which used to work as it was included in the model admin page in the
>> order it appears. However, now in Django 2.0, it appears in this order:
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> *> src="/static/plugins/codemirror/lib/codemirror.js">*
>> 
>> 
>> 
>>
>> The issue is that the First file MUST be first as the remainder rely upon
>> it!  I'd rather not override a template file as if i change the admin
>> backend with a package i'd like this to "just work" as it did in Django 1.11
>> Is this a bug in the new way that Django includes these files (docs say
>> they made a change in how this is done, clearly it broke something that
>> worked!).
>>
>> Thanks
>>
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Django users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to django-users...@googlegroups.com.
>> To post to this group, send email to django...@googlegroups.com.
>> Visit this group at https://groups.google.com/group/django-users.
>> To view this discussion on the web visit https://groups.google.com/d/ms
>> gid/django-users/5ad93160-05c2-4251-84ad-6f8a1574b675%40googlegroups.com
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>>
>> --
>> Etienne Robillardtka...@yandex.comhttps://www.isotopesoftware.ca/
>>
>> --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-users+unsubscr...@googlegroups.com.
> To post to this group, send email to django-users@googlegroups.com.
> Visit this group at https://groups.google.com/group/django-users.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/django-users/8493b435-1574-4187-88f6-7f45f5dbaba6%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CAK4qSCfTd0BBjYQsovHPx%2BS40U_dA1RA%3DYDNtBdYS3GJJFbKpA%40mail.gmail.com.
For more options, visit 

Re: ModelAdmin Media JS file order issue in Django 2.0

[Marc R]

because they are specific to only a few models, particularly the loading 
scripts, and options, etc.  this worked great in Django 1.11

On Sunday, 10 December 2017 09:36:56 UTC-5, Etienne Robillard wrote:
>
> Why don't you simply put the javascripts into your base template without 
> using Python ? 
>
> Etienne
>
> Le 2017-12-10 à 09:30, Marc R a écrit :
>
> I have this in my model: 
>
> class Media:
> js = (
>* '/static/plugins/codemirror/lib/codemirror.js',*
> '/static/plugins/codemirror/mode/htmlmixed/htmlmixed.js',
> '/static/plugins/codemirror/addon/fold/foldcode.js',
> '/static/plugins/codemirror/addon/fold/foldgutter.js',
> '/static/plugins/codemirror/addon/fold/brace-fold.js',
> '/static/plugins/codemirror/addon/fold/indent-fold.js',
> '/static/plugins/codemirror/addon/fold/comment-fold.js',
> '/static/plugins/codemirror/addon/fold/xml-fold.js',
> '/static/plugins/codemirror/addon/comment/comment.js',
> '/static/plugins/codemirror/addon/edit/matchbrackets.js',
> '/static/plugins/codemirror/addon/edit/matchtags.js',
> '/static/plugins/codemirror/mode/javascript/javascript.js',
> '/static/plugins/codemirror/mode/xml/xml.js',
> '/static/plugins/codemirror/mode/htmlmixed/htmlmixed.js',
> '/static/plugins/codemirror/addon/display/fullscreen.js',
> '/static/js/admin/syslog/syslog_change_form.min.js'
> )
>
> which used to work as it was included in the model admin page in the order 
> it appears. However, now in Django 2.0, it appears in this order:
>  src="/static/plugins/codemirror/addon/fold/foldcode.js">
>  src="/static/plugins/codemirror/addon/fold/foldgutter.js">
>  src="/static/plugins/codemirror/addon/fold/brace-fold.js">
>  src="/static/plugins/codemirror/addon/fold/indent-fold.js">
>  src="/static/plugins/codemirror/addon/fold/comment-fold.js">
>  src="/static/plugins/codemirror/addon/fold/xml-fold.js">
>  src="/static/plugins/codemirror/addon/comment/comment.js">
>  src="/static/plugins/codemirror/addon/edit/matchbrackets.js">
>  src="/static/plugins/codemirror/addon/edit/matchtags.js">
>  src="/static/plugins/codemirror/mode/javascript/javascript.js">
>  src="/static/plugins/codemirror/mode/xml/xml.js">
> * src="/static/plugins/codemirror/lib/codemirror.js">*
>  src="/static/plugins/codemirror/mode/htmlmixed/htmlmixed.js">
>  src="/static/plugins/codemirror/addon/display/fullscreen.js">
>  src="/static/js/admin/syslog/syslog_change_form.min.js">
>
> The issue is that the First file MUST be first as the remainder rely upon 
> it!  I'd rather not override a template file as if i change the admin 
> backend with a package i'd like this to "just work" as it did in Django 1.11
> Is this a bug in the new way that Django includes these files (docs say 
> they made a change in how this is done, clearly it broke something that 
> worked!).
>
> Thanks
>
>
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Django users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to django-users...@googlegroups.com .
> To post to this group, send email to django...@googlegroups.com 
> .
> Visit this group at https://groups.google.com/group/django-users.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/django-users/5ad93160-05c2-4251-84ad-6f8a1574b675%40googlegroups.com
>  
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>
>
> -- 
> Etienne robillardtka...@yandex.com 
> https://www.isotopesoftware.ca/
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/8493b435-1574-4187-88f6-7f45f5dbaba6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: ModelAdmin Media JS file order issue in Django 2.0

[Etienne Robillard]

Why don't you simply put the javascripts into your base template without 
using Python ?


Etienne


Le 2017-12-10 à 09:30, Marc R a écrit :

I have this in my model:

class Media:
        js = (
*'/static/plugins/codemirror/lib/codemirror.js',*
'/static/plugins/codemirror/mode/htmlmixed/htmlmixed.js',
'/static/plugins/codemirror/addon/fold/foldcode.js',
'/static/plugins/codemirror/addon/fold/foldgutter.js',
'/static/plugins/codemirror/addon/fold/brace-fold.js',
'/static/plugins/codemirror/addon/fold/indent-fold.js',
'/static/plugins/codemirror/addon/fold/comment-fold.js',
'/static/plugins/codemirror/addon/fold/xml-fold.js',
'/static/plugins/codemirror/addon/comment/comment.js',
'/static/plugins/codemirror/addon/edit/matchbrackets.js',
'/static/plugins/codemirror/addon/edit/matchtags.js',
'/static/plugins/codemirror/mode/javascript/javascript.js',
            '/static/plugins/codemirror/mode/xml/xml.js',
'/static/plugins/codemirror/mode/htmlmixed/htmlmixed.js',
'/static/plugins/codemirror/addon/display/fullscreen.js',
'/static/js/admin/syslog/syslog_change_form.min.js'
        )

which used to work as it was included in the model admin page in the 
order it appears. However, now in Django 2.0, it appears in this order:
src="/static/plugins/codemirror/addon/fold/foldcode.js">
src="/static/plugins/codemirror/addon/fold/foldgutter.js">
src="/static/plugins/codemirror/addon/fold/brace-fold.js">
src="/static/plugins/codemirror/addon/fold/indent-fold.js">
src="/static/plugins/codemirror/addon/fold/comment-fold.js">
src="/static/plugins/codemirror/addon/fold/xml-fold.js">
src="/static/plugins/codemirror/addon/comment/comment.js">
src="/static/plugins/codemirror/addon/edit/matchbrackets.js">
src="/static/plugins/codemirror/addon/edit/matchtags.js">
src="/static/plugins/codemirror/mode/javascript/javascript.js">
src="/static/plugins/codemirror/mode/xml/xml.js">
*src="/static/plugins/codemirror/lib/codemirror.js">*
src="/static/plugins/codemirror/mode/htmlmixed/htmlmixed.js">
src="/static/plugins/codemirror/addon/display/fullscreen.js">
src="/static/js/admin/syslog/syslog_change_form.min.js">


The issue is that the First file MUST be first as the remainder rely 
upon it!  I'd rather not override a template file as if i change the 
admin backend with a package i'd like this to "just work" as it did in 
Django 1.11
Is this a bug in the new way that Django includes these files (docs 
say they made a change in how this is done, clearly it broke something 
that worked!).


Thanks


--
You received this message because you are subscribed to the Google 
Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send 
an email to django-users+unsubscr...@googlegroups.com 
.
To post to this group, send email to django-users@googlegroups.com 
.

Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/5ad93160-05c2-4251-84ad-6f8a1574b675%40googlegroups.com 
.

For more options, visit https://groups.google.com/d/optout.


--
Etienne Robillard
tkad...@yandex.com
https://www.isotopesoftware.ca/

--
You received this message because you are subscribed to the Google Groups "Django 
users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/36e6755b-ed27-9a77-9bdd-77a9bd4bf429%40yandex.com.
For more options, visit https://groups.google.com/d/optout.