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

[RompePC]

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.).

The exception throwed is (line 28):


coercing to Unicode: need string or buffer, NoneType found

18 
19 {% if field|is_checkboxselectmultiple %} 
20 {% include 'bootstrap3/layout/checkboxselectmultiple.html' %} 
21 {% endif %} 
22 
23 {% if field|is_radioselect %} 
24 {% include 'bootstrap3/layout/radioselect.html' %} 
25 {% endif %} 
26 
27 {% if not field|is_checkboxselectmultiple and not field|is_radioselect %} 
28 {% if field|is_checkbox and form_show_labels %} 
29  
30 {% crispy_field field %} 
31 {{ field.label|safe }} 
32 {% include 'bootstrap3/layout/help_text_and_errors.html' %} 
33  
34 {% else %} 
35  
36 {% crispy_field field %} 
37 {% include 'bootstrap3/layout/help_text_and_errors.html' %} 
38 


-- 
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/65bdca52-beba-4e02-a39a-5694ccbfbd66%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Parent initialization don't working

[RompePC]

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 super()

class SonAdmin(ParentAdmin):
# Boring stuff

If I set up *list_filter* in *SonAdmin*, it shows the filter and all goes 
well. But, if I set up it instead in *ParentAdmin*, it just doesn't show. 
And its weird because it works when setting list_display the same way. No 
errors throwed, and no other part of the code is the problem. I think that 
Django overrides it in some moment, but that wouldn't make sense. Any ideas?

-- 
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/e74c0eca-d417-4914-ab4c-df5b67bae618%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Trying to use Django 1.9.5, django_pyodbc, MS SQL Server 2012 on 64bit Windows 7

[John Fabiani]

Prove to yourself that the pyodbc connection is working correctly without
django.

On Wed, Aug 10, 2016 at 6:37 PM, Mike Dewhirst 
wrote:

> On 11/08/2016 5:11 AM, Evan Roberts wrote:
>
>> I'm struggling to get a project going. I'm new to python and django.
>>
>> Is django_pyodbc supported on Python 3.5.1 and django 1.9? If not could
>> you suggest a combination of python & django that is known to work with
>> MS SQL Server 2012?
>>
>
> Not an answer to your specific question but a recommendation to use
> PostgreSQL instead. It works brilliantly on Windows and makes life serene.
> Much easier to gain python and django experience when the environment isn't
> fighting back. You can dump and pump later when you really need SQL Server.
>
> Mike
>
>
>>
>> Here are the details of my virtual environmentÂ
>>
>> windows 7 64 bit,Â
>>
>> python 3.5.1 64 bit,Â
>>
>> packages installed:
>>
>> |Django (1.9) django-pyodbc (0.4.1) pip (8.1.2) pyodbc (3.0.10) pywin32
>> (219) setuptools (19.1) wheel (0.26.0) |
>>
>>
>>
>> The database definition in settings.py:
>>
>> |DATABASES = { 'default': { 'ENGINE': 'django_pyodbc', 'HOST':
>> '192.168.10.47', 'PORT': '1433', 'USER': '*', 'PASSWORD':
>> '***', 'NAME': 'my_db', 'OPTIONS' : { 'driver' : 'SQL Server Native
>> Client 11.0', 'MARS_Connection' : True, 'driver_supports_utf8' : True,
>> }, } } |
>>
>>
>>
>> When I try to run the development server I'm getting these errors:
>>
>> |(my_db) PS F:\my_db\my_db> python .\manage.py runserver Performing
>> system checks... System check identified no issues (0 silenced).
>> DRIVER={SQL Server Native Client
>> 11.0};SERVER=192.168.10.47;PORT=1433;UID=*;PWD=**;
>> DATABASE=my_db;MARS_Connection=yes
>> Unhandled exception in thread started by > check_errors..wrapper at 0x04000D90> Traceback (most
>> recent call last): File
>> "C:\Users\eroberts\AppData\Local\Programs\Python\Python35\
>> lib\site-packages\django\utils\autoreload.py",
>> line 226, in wrapper fn(*args, **kwargs) File
>> "C:\Users\eroberts\AppData\Local\Programs\Python\Python35\
>> lib\site-packages\django\core\management\commands\runserver.py",
>> line 117, in inner_run self.check_migrations() File
>> "C:\Users\eroberts\AppData\Local\Programs\Python\Python35\
>> lib\site-packages\django\core\management\commands\runserver.py",
>> line 163, in check_migrations executor =
>> MigrationExecutor(connections[DEFAULT_DB_ALIAS]) File
>> "C:\Users\eroberts\AppData\Local\Programs\Python\Python35\
>> lib\site-packages\django\db\migrations\executor.py",
>> line 20, in __init__ self.loader = MigrationLoader(self.connection) File
>> "C:\Users\eroberts\AppData\Local\Programs\Python\Python35\
>> lib\site-packages\django\db\migrations\loader.py",
>> line 49, in __init__ self.build_graph() File
>> "C:\Users\eroberts\AppData\Local\Programs\Python\Python35\
>> lib\site-packages\django\db\migrations\loader.py",
>> line 176, in build_graph self.applied_migrations =
>> recorder.applied_migrations() File
>> "C:\Users\eroberts\AppData\Local\Programs\Python\Python35\
>> lib\site-packages\django\db\migrations\recorder.py",
>> line 65, in applied_migrations self.ensure_schema() File
>> "C:\Users\eroberts\AppData\Local\Programs\Python\Python35\
>> lib\site-packages\django\db\migrations\recorder.py",
>> line 56, in ensure_schema with self.connection.schema_editor() as
>> editor: File
>> "C:\Users\eroberts\AppData\Local\Programs\Python\Python35\
>> lib\site-packages\django\db\backends\base\base.py",
>> line 604, in schema_editor 'The SchemaEditorClass attribute of this
>> database wrapper is still None') NotImplementedError: The
>> SchemaEditorClass attribute of this database wrapper is still None|
>>
>> --
>> 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/90dab5d0-2f51
>> -4bab-8b93-bdb6e507d6c6%40googlegroups.com
>> > 1-4bab-8b93-bdb6e507d6c6%40googlegroups.com?utm_medium=email
>> &utm_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/ms
> g

Re: Trying to use Django 1.9.5, django_pyodbc, MS SQL Server 2012 on 64bit Windows 7

[Evan Roberts]

>
> Hi Mike,


Thanks for the suggestion.  Yes, postgres would be a good answer, but not 
really a possibility at this point.  Let me give you the back ground. 
I inherited this project.  The original project is written using django 
0.95 and SQL Server 2003. The project that was written by a long departed 
employee in 2009.  Several other systems have started using the data in 
this database. Unless I want to update all of them to use the postgres, I'm 
stuck with MS SQL Server 2012.  

I'm also a big fan of not fighting your tools...

-- 
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/6df5929e-48b0-4b04-98ac-9f56f309330f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Trying to use Django 1.9.5, django_pyodbc, MS SQL Server 2012 on 64bit Windows 7

[Evan Roberts]

>
> Hi John,
>

Excellent suggestion.  Using python shell and pyodbc I was able to connect 
and perform several simple queries.  Just worked,  no heroics needed. I'm 
fairly sure my problem lies in django_pyodbc,  it is making sure the 
connection to the database is sane. I'm not sure the support for django 1.9 
is fully incorporated.

Here is my session with pyodbc:
PS F:\my_db\my_db> .\env\Scripts\Activate.ps1
(env) PS F:\my_db\my_db> python
Python 3.5.1 (v3.5.1:37a07cee5969, Dec  6 2015, 01:54:25) [MSC v.1900 64 
bit (AMD64)] on win32
Type "help", "copyright", "credits" or "license" for more information.
>>> import pyodbc
>>> cnxn = pyodbc.connect('DRIVER={SQL 
Server};SERVER=***;PORT=1433;DATABASE=my_db;UID=*;PWD=*')
>>> cursor = cnxn.cursor()
>>> cursor.execute("select name,siteid from cpd_customer")

>>> row=cursor.fetchone()
>>> row
('A***, *', '0001')
>>> row=cursor.fetchone()
>>> row
('A**', '00111')
>>> row = cursor.fetchone()
>>> row[0]
'A**'
>>> row[1]
'00111'
>>> row.name
'A**'
>>> row.siteid
'00111'
>>>


-- 
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/6bbc3cdb-61e6-4c12-af4f-fdb7e1ee1d66%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Trying to use Django 1.9.5, django_pyodbc, MS SQL Server 2012 on 64bit Windows 7

[Evan Roberts]

Thanks for the help and guidance.  I found a solution. I installed these 
libs and was able to connect:
Django (1.9.9)
django-pyodbc-azure (1.9.9.0)
pip (8.1.2)
pyodbc (3.0.10)

I connected using these settings:
DATABASES = {
'default': {
'ENGINE': 'sql_server.pyodbc',
'HOST': '192.168.**.**',
'PORT': '1433',
'USER': '***',
'PASSWORD': '**',
'NAME': 'mydb',
}
}

-- 
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/d138baf7-f035-4b28-b6ab-0c279dbf5c0a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Constantine Covtushenko]

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 at 1:11 PM, RompePC  wrote:

> 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.).
>
> The exception throwed is (line 28):
>
>
> coercing to Unicode: need string or buffer, NoneType found
>
> 18
> 19 {% if field|is_checkboxselectmultiple %}
> 20 {% include 'bootstrap3/layout/checkboxselectmultiple.html' %}
> 21 {% endif %}
> 22
> 23 {% if field|is_radioselect %}
> 24 {% include 'bootstrap3/layout/radioselect.html' %}
> 25 {% endif %}
> 26
> 27 {% if not field|is_checkboxselectmultiple and not field|is_radioselect
> %}
> 28 {% if field|is_checkbox and form_show_labels %}
> 29 
> 30 {% crispy_field field %}
> 31 {{ field.label|safe }}
> 32 {% include 'bootstrap3/layout/help_text_and_errors.html' %}
> 33 
> 34 {% else %}
> 35 
> 36 {% crispy_field field %}
> 37 {% include 'bootstrap3/layout/help_text_and_errors.html' %}
> 38 
>
>
> --
> 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/65bdca52-beba-4e02-a39a-5694ccbfbd66%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/CAK52boVK5TA1z6g0L68KFwzNtw8nTtXf6%3DQ49YSzgrW_wy-Dsw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Parent initialization don't working

[Constantine Covtushenko]

Hi Rompe,

As for your admin models it seems like they should extend:
`admin.ModelAdmin`, see django documentation


I am not sure that this is a problem you have encountered.
But to move further please do like said in the documentation firstly.

Regards,


On Thu, Aug 11, 2016 at 1:06 PM, RompePC  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 piece of code (take it as an example):
>
> class ParentAdmin(object):
>def __init__(self):
>  # Boring stuff
>  self.list_filter = ["name"]
>  # Calling super()
>
> class SonAdmin(ParentAdmin):
> # Boring stuff
>
> If I set up *list_filter* in *SonAdmin*, it shows the filter and all goes
> well. But, if I set up it instead in *ParentAdmin*, it just doesn't show.
> And its weird because it works when setting list_display the same way. No
> errors throwed, and no other part of the code is the problem. I think that
> Django overrides it in some moment, but that wouldn't make sense. Any ideas?
>
> --
> 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/e74c0eca-d417-4914-ab4c-df5b67bae618%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/CAK52boVa%2Byekd2U5sEHtnQj_Sdmyv%2B-qC6GRdT4RwByUpxx%2BWw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Trying to use Django 1.9.5, django_pyodbc, MS SQL Server 2012 on 64bit Windows 7

[Constantine Covtushenko]

Great job done.

You welcome!

Regards,

On Thu, Aug 11, 2016 at 8:46 PM, Evan Roberts 
wrote:

>
> Thanks for the help and guidance.  I found a solution. I installed these
> libs and was able to connect:
> Django (1.9.9)
> django-pyodbc-azure (1.9.9.0)
> pip (8.1.2)
> pyodbc (3.0.10)
>
> I connected using these settings:
> DATABASES = {
> 'default': {
> 'ENGINE': 'sql_server.pyodbc',
> 'HOST': '192.168.**.**',
> 'PORT': '1433',
> 'USER': '***',
> 'PASSWORD': '**',
> 'NAME': 'mydb',
> }
> }
>
> --
> 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/d138baf7-f035-4b28-b6ab-0c279dbf5c0a%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/CAK52boX07%2BBV9wndgRzK49V%3DnuBvXePri3FBUZhsq42znErpMQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

"add another" for inline in admin disappeared in 1.10

[Chris Gray]

After upgrading from 1.9 to 1.10, I noticed that the "add another" link for 
inline elements in the admin interface no longer displays.  I reverted to 
1.9 and the links came back.  It looks like the code embedded in the page 
is totally different between 1.9 and 1.10.

-- 
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/4d2ba65e-2f90-46c6-9f76-0dd27c1af65b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: "add another" for inline in admin disappeared in 1.10

[Tim Graham]

Are you using any third-party enhancements that might need to be updated? I 
see "Add another Choice" at a page like /admin/polls/question//change/ 
for the tutorial. More specifics about how to reproduce the issue are 
needed.

On Thursday, August 11, 2016 at 4:55:04 PM UTC-4, Chris Gray wrote:
>
> After upgrading from 1.9 to 1.10, I noticed that the "add another" link 
> for inline elements in the admin interface no longer displays.  I reverted 
> to 1.9 and the links came back.  It looks like the code embedded in the 
> page is totally different between 1.9 and 1.10.
>

-- 
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/4120ee73-cf88-48dc-ae96-025906b8a29f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[RompePC]

Hi there,

I apprecciate the help, but the models' code is secret (I'm not allowed to 
show it anywhere).
It is like it sends a non-existent field to the form, and don't know why. 
And the model is the same as the previous version, its very weird. And 
didn't found anything about that error 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 at 1:11 PM, RompePC  > wrote:
>
>> 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.).
>>
>> The exception throwed is (line 28):
>>
>>
>> coercing to Unicode: need string or buffer, NoneType found
>>
>> 18 
>> 19 {% if field|is_checkboxselectmultiple %} 
>> 20 {% include 'bootstrap3/layout/checkboxselectmultiple.html' %} 
>> 21 {% endif %} 
>> 22 
>> 23 {% if field|is_radioselect %} 
>> 24 {% include 'bootstrap3/layout/radioselect.html' %} 
>> 25 {% endif %} 
>> 26 
>> 27 {% if not field|is_checkboxselectmultiple and not field|is_radioselect 
>> %} 
>> 28 {% if field|is_checkbox and form_show_labels %} 
>> 29  
>> 30 {% crispy_field field %} 
>> 31 {{ field.label|safe }} 
>> 32 {% include 'bootstrap3/layout/help_text_and_errors.html' %} 
>> 33  
>> 34 {% else %} 
>> 35  
>> 36 {% crispy_field field %} 
>> 37 {% include 'bootstrap3/layout/help_text_and_errors.html' %} 
>> 38 
>>
>>
>> -- 
>> 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/65bdca52-beba-4e02-a39a-5694ccbfbd66%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/7dd1434a-da42-441b-a471-30e7db9c47d7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Parent initialization don't working

[RompePC]

Thanks for the response, but I tried that before and didn't helped. In 
xadmin you inherit from object (yeah, weird), and there you've your model 
panel.
The matter is that some set up works in that parent class (like 
*form_layout*), but others not, and raising and exception to see their 
values show me that all are setted up well, but later doesn't shows 
anything. That *super* has to be doing something with they, but I don't 
know what.

El jueves, 11 de agosto de 2016, 21:26:50 (UTC+2), Constantine Covtushenko 
escribió:
>
> Hi Rompe,
>
> As for your admin models it seems like they should extend:
> `admin.ModelAdmin`, see django documentation 
> 
>
> I am not sure that this is a problem you have encountered.
> But to move further please do like said in the documentation firstly.
>
> Regards,
>
>
> On Thu, Aug 11, 2016 at 1:06 PM, RompePC  > 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 piece of code (take it as an example):
>>
>> class ParentAdmin(object):
>>def __init__(self):
>>  # Boring stuff
>>  self.list_filter = ["name"]
>>  # Calling super()
>>
>> class SonAdmin(ParentAdmin):
>> # Boring stuff
>>
>> If I set up *list_filter* in *SonAdmin*, it shows the filter and all 
>> goes well. But, if I set up it instead in *ParentAdmin*, it just doesn't 
>> show. And its weird because it works when setting list_display the same 
>> way. No errors throwed, and no other part of the code is the problem. I 
>> think that Django overrides it in some moment, but that wouldn't make 
>> sense. Any ideas?
>>
>> -- 
>> 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/e74c0eca-d417-4914-ab4c-df5b67bae618%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/e50f93fc-b540-4c02-9a66-feddf2638f65%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.