Hi Karen, Thanks for your immediate reply!
I will extract problematic app into separate project and get in touch with you later this day. Many thanks! On Aug 26, 4:48 pm, "Karen Tracey" <[EMAIL PROTECTED]> wrote: > On Tue, Aug 26, 2008 at 11:35 AM, vv2 <[EMAIL PROTECTED]> wrote: > > > I am running my app on latest trunk (r8580 at the moment of writing > > this post) and I have nothing but problems while trying to deploy my > > stuff over mod_wsgi. > > > Exception I am receiving is generic " 'str' object has no attribute > > '_default_manager' " which shows up when something goes wrong with > > admin.autodiscover() at urls.py. > > > My first thought was that I probably missed over something while > > porting my bits to newforms-admin from pre 1.0-alpha trunk, but after > > a while I realized that gremlins are coming out only while WSGIHandler > > is used - this means running Django through cherrypy, spawning and > > mod_wsgi. Dev server, mod_python and FCGI (through lighttpd) works > > perfectly fine with same code. > > > The source of problems is one - very simple app which contains one > > model, one ModelAdmin and one view. After trying to narrow source of > > problems to find out which portion of code is causing the problems I > > found out that everything is running fine when I comment out fieldsets > > definition in my ModelAdmin. > > > That's pretty weird and I believe there is nothing wrong with my code > > (it works through interfaces other than WSGI!). > > > Any kind of lead that I could follow to make my code working through > > WSGI would be highly appreciated! > > Your problem description (minus the fact that it is specific to mod_wsgi, > which sounds like a significant Clue) is reminiscent of this old thread: > > http://groups.google.com/group/django-users/browse_thread/thread/6ef7... > ? > > I believe I also had another person email me privately saying they were > seeing this error message, but no one was ever able to provide a small test > project that demonstrated the error (and the original poster on that thread > stopped hitting the error after updating & splitting out the admin > definitions into admin.py). > > It sounds like there is likely a bug hidden somewhere here, but we need a > reliable way of recreating it in order to figure out what is going on. If > you can help out with providing a small testcase that demonstrates the > problem I'm sure it would be appreciated. > > Karen --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
