Re: Setting FK field in list view

Ok, looks like just adding a *ModelForm* and getting that field does the work. Sorry for the noobish time. El martes, 20 de septiembre de 2016, 8:23:19 (UTC+2), RompePC escribió: > > Talking in the way of getting the HTML widget yeah, maybe. But what I > wanna do is, given a model *A*

Re: Setting FK field in list view

et_wrapper.html template and remove the > buttons. > > https://github.com/django/django/blob/master/django/contrib/admin/templates/admin/related_widget_wrapper.html > > Otherwise, I'm out of (simple) ideas. > > On Monday, September 19, 2016 at 12:58:44 PM UTC-4, RompePC wrote:

Re: Setting FK field in list view

t understand the goal. Maybe you can mock up a screenshot > and/or give a code example. > > On Monday, September 19, 2016 at 12:41:32 PM UTC-4, RompePC wrote: >> >> Nope, as I wanna the ModelChoiceField rendered in the filter list I did >> in my own (not the sided one). >&

Re: Setting FK field in list view

f/contrib/admin/#django.contrib.admin.ModelAdmin.list_editable > > On Monday, September 19, 2016 at 11:05:22 AM UTC-4, RompePC wrote: >> >> Nope, it isn't a lookup separator: for simply understanding, I wanna get >> the FK widget (the HTML, the select, all of that) that is show when adding &

Re: Setting FK field in list view

use it anywhere in my panel. El lunes, 19 de septiembre de 2016, 16:31:55 (UTC+2), Tim Graham escribió: > > Is your request https://code.djangoproject.com/ticket/10743? > > On Monday, September 19, 2016 at 10:08:59 AM UTC-4, RompePC wrote: >> >> Yep, the second one is wh

Re: Setting FK field in list view

ound a way. Best option might be a inline model > admin. > > 2016-09-19 12:24 GMT+02:00 RompePC <durillo...@gmail.com >: > > Hi again, I didn't have time to try it until now, but I just realized > that > > maybe I asked the wrong way. What I wanna do is to rend

Re: Setting FK field in list view

it. El viernes, 16 de septiembre de 2016, 13:59:26 (UTC+2), ludovic coues escribió: > > Have you tried something like author__name ? Assuming a model with an > author foreign key. > > 2016-09-16 8:56 GMT+02:00 RompePC <durillo...@gmail.com >: > > I would like to pa

Re: Setting FK field in list view

I'll try ASAP I can, thanks El viernes, 16 de septiembre de 2016, 13:59:26 (UTC+2), ludovic coues escribió: > > Have you tried something like author__name ? Assuming a model with an > author foreign key. > > 2016-09-16 8:56 GMT+02:00 RompePC <durillo...@gmail.com >: >

Setting FK field in list view

I would like to pass to the list display view a FK field of the admin form (like the ones when adding a new row). But I don't see the way of doing it, although I've searched along many properties of the model admin to get it. Anyone did something like that before? -- You received this message

Re: What is this? CASCADE clausule on DROP COLUMN???

), Erik Cederstrand escribió: > > > > Den 25. aug. 2016 kl. 17.09 skrev RompePC <durillo...@gmail.com > >: > > > > I did a migration of Django, and then applied a sqlmigrate, giving me > this output... > > > > BEGIN; > > -- > > -- R

What is this? CASCADE clausule on DROP COLUMN???

I did a migration of Django, and then applied a *sqlmigrate*, giving me this output... BEGIN; -- -- Remove field my_column from my_table -- ALTER TABLE `my_table` DROP COLUMN `my_column` CASCADE; I don't find info about it, and I've never seen something like this in my MySQL experience. And

Re: Parent initialization don't working

xadmin. > Sorry again. > > I've checked its github page. It seems like they do not have documentation > in English. > > So may be your problem should be addressed to them? > Did you try that? > > Else as for me we should go to xadmin code and check there. > > On Fri, Au

Re: Parent initialization don't working

agosto de 2016, 12:58:20 (UTC+2), RompePC escribió: > > I'll say first that I'm using *xadmin*, although it doesn't matter for > this problem. > Python 2.7.3 with Django 1.9.5 > > The problem is in this piece of code (take it as an example): > > class ParentAdmin(object)

Re: Crispy forms and its "coercing to unicode need string or buffer nonetype found"

Ok, I just did again a *unicode(..)* call to a method that before worked without it. Sincerely, I just have no idea why now I need to do it. Solved. El jueves, 11 de agosto de 2016, 12:58:20 (UTC+2), RompePC escribió: > > I was working on an admin panel, and when I try to get to the add/

Re: Parent initialization don't working

egards, > > > On Thu, Aug 11, 2016 at 1:06 PM, RompePC <durillo...@gmail.com > > wrote: > >> I'll say first that I'm using *xadmin*, although it doesn't matter for >> this problem. >> Python 2.7.3 with Django 1.9.5 >> >> The problem is in this

Re: Crispy forms and its "coercing to unicode need string or buffer nonetype found"

in a crispy-form. I'm sorry for the problems. El jueves, 11 de agosto de 2016, 21:23:59 (UTC+2), Constantine Covtushenko escribió: > > Hi Rompe, > > From you have posted I can suggest check your model. > Can you post here code of it? > > Regards, > > On Thu, Aug 11, 2016 a

Parent initialization don't working

I'll say first that I'm using *xadmin*, although it doesn't matter for this problem. Python 2.7.3 with Django 1.9.5 The problem is in this piece of code (take it as an example): class ParentAdmin(object): def __init__(self): # Boring stuff self.list_filter = ["name"] # Calling

Crispy forms and its "coercing to unicode need string or buffer nonetype found"

I was working on an admin panel, and when I try to get to the add/update view of the model, it just throws this error. I've been checking Google for all the morning, but the solutions I've just found aren't the problem I've (no problem with unicode, I check if the related object is None, etc.).