TabularInline header not visible after update to django trunk (1, 2, 0, 'alpha', 1)

[GoogleCodeExporter]

What steps will reproduce the problem?
1. update to django trunk

What is the expected output? What do you see instead?
The same app doesn't show the headers of the TabularInline with django trunk, 
but work with 
django 1.1.1

What version of the product are you using? On what operating system?
Grappelli Revision: 731 - Django (1, 2, 0, 'alpha', 1)

Original issue reported on code.google.com by mauro.de...@gmail.com on 26 Jan 2010 at 10:55

Attachments:

• tabularInline.png

[GoogleCodeExporter]

I am also having this problem with trunk version 1.2 alpha 1 SVN-12311

Original comment by gravesit@gmail.com on 28 Jan 2010 at 3:19

[GoogleCodeExporter]

yep. it´s because the javascripts with the original admin-interface have 
changed with
the current trunk. don´t really know how to solve this ... we´re thinking 
about
decoupling grappelli totally, making it a standalone-app (including all 
.py-files).
then we don´t have to deal with every change within the original 
admin-interface.

Original comment by sehmaschine on 28 Jan 2010 at 3:27

[GoogleCodeExporter]

That's how I solved this for myself. It may have broken something, I haven't 
tested
this much yet.

Original comment by dmitry.medvinsky@gmail.com on 3 Mar 2010 at 2:59

Attachments:

• grappelli.patch

[GoogleCodeExporter]

Thanks for the patch.  Seems to work OK for me.  

As for the idea of making this standalone, I really must say that nothing would 
make me run away faster...  I 
understand it's hard keeping up with trunk, but you don't really need to.  
Django develops on cycles, and not 
too many people keep their production sites updated daily to trunk.  You really 
could just keep a point release 
for every Django release (2.1 = Django 1.2,  2.0 = Django 1.1) and keep trunk 
updated twice a month (or 
less)...  I hardly doubt that Django will have wide-sweeping Admin changes 
during the months of mostly 
bugfix work on 1.2.  But of course the rush for features for 1.3 may or may not 
have a lot of admin changes.   
But even with 1.2, the admin changes I could count on my hands... maybe even 
one hand.. And is it really that 
hard to keep semi-updated with them? 

I just feel that nothing could be worse, and make it less appealing, than 
making such a good add-on for the 
admin break off from the django contrib admin...   I feel that the longer they 
stay apart, the less interested you 
guys will become in porting over the newer admin features,  until the point 
where they diverge so greatly that 
they don't even provide the same basic experience anymore.  Anyway... while 
developing I DO keep current to 
trunk,  and nothing would sadden me more than to see such a nice admin app 
punish me and anyone else by 
going standalone.

I would like to commend you on your 2.1 work, however.  It is quite fantastic 
even though a lot of stuff is 
currently still broken against trunk.  I can only use it in my development 
stuff though, because of these issues, 
but I will try my best to report every bug I come across (which have been 
numerous).  I would like to do 
anything possible to see that this stays coupled to the official admin.  

Original comment by jon....@gmail.com on 5 Mar 2010 at 3:57

[GoogleCodeExporter]

first, please post stuff like this to the google-group. otherwise people won´t
find/read it.

second, 2.1 won´t ever be an official release - so finding bugs with that 
version
doesn´t make much sense. 2.1 is an internal and temporary branch. it´s only 
there for
maxime (working on 2.2, integrating jquery).

regards,
patrick

Original comment by sehmaschine on 5 Mar 2010 at 4:05

[GoogleCodeExporter]

To quote you (from a recent Groups post): 

"2.1 introduces the html/css framework - but will be released together 
with 2.2 which replaces all original javscripts with jquery and 
implements some additional features."

So I'm pretty sure any bugs found while I'm playing with 2.1 (since 2.2 doesn't 
exist yet) will end up in 2.2, and 
whenever that actually exists I will try to report bugs when I can.  Unless 
every one of them gets squashed by 
the time there's a 2.2, which would of course be nice, but impossible.

Anyway, what I'm seeing in 2.1 so far is quite fantastic, so I look forward to 
2.2 as well.

As for my comments about this project's future,  I don't care about my 
comments' visibility. I knew that at 
least the admins of this project would see it,  and I happened to be on this 
page to confirm that the patch was 
working nicely.  But if I do ever have more to add I will certainly be posting 
it to Google Groups.

Thank you.

Original comment by jon....@gmail.com on 5 Mar 2010 at 4:43

[GoogleCodeExporter]

don´t get me wrong ... after 2.2 is released, feedback is very much 
appreciated. that
said, your assumption about our workflow is wrong. bugs you find in 2.1 won´t
necessarily end up in 2.2.

so, instead of posting bugs you might wanna consider posting your comments to 
the
google-group ...

Original comment by sehmaschine on 5 Mar 2010 at 4:50

[GoogleCodeExporter]

fixed with grappelli 2.1

Original comment by sehmaschine on 11 May 2010 at 2:39

• Changed state: Fixed