Hi Jakob, This rearranging of imports solved a (separate?) issue I was seeing where OrderTaxDetail could not be imported. This had the mysterious effect of eliminating the large number of OrderPayment import errors, even errors I was seeing in sites using an unmodified Satchmo in a separate virtualenv.
I think Chris M was suggesting that you try Hynek's strategy mentioned above. One simple thing would be to comment out admin.autodiscover() and see if the problem goes away. That doesn't tell us much, but if this is a live site that you need to get back up in a rush, this may be a stop gap. I may have to take part of this conversation over to the modwsgi group, but there is definitely something specific about Satchmo and/or some of its depencies (keyed-cache, threaded-multihost, etc) since I do not have this problem with any other non-Satchmo projects (even on the same server using the same virtualenv, just no satchmo in INSTALLED_APPS). Cheers, John-Scott On Thu, Jan 13, 2011 at 11:03 AM, Jakob H <[email protected]>wrote: > Hi, > > Not yet, but I will try this tonight. So, the change I will try is: > > 1. Move class definition of OrderTaxDetail above class definition of > Order > 2. Put the FK model reference (Order) within single quotation marks > ('Order') to make it load lazily (did not know you could do that) > > Does this seem correctly understood? > > I will try it and let you know. > Cheers, > Jakob > > On Jan 13, 10:34 am, Chris Moffitt <[email protected]> wrote: > > Did you try the solution that was posted earlier in this thread? I > haven't > > tried it yet to see if it fixes it for me. > > > > -Chris > > > > > > > > On Thu, Jan 13, 2011 at 9:15 AM, Jakob H <[email protected]> > wrote: > > > Hi, > > > > > I now get this error on basically every request to the website. > > > However, I'm not sure it is specifically Satchmo related, but I really > > > need to get this fixed. > > > > > The problem does not seem to occur on the runserver on my local > > > machine, but does happen every time on my shared host deployment > > > server using WSGI. > > > > > Here is my traceback:http://dpaste.com/313255/. > > > > > I have Python 2.6.1 on my local machine and Python 2.6.2 on my > > > deployment server if that matters. > > > > > Cheers, > > > Jakob > > > > > On Jan 12, 10:20 pm, John-Scott <[email protected]> wrote: > > > > Thanks for your thoughtful and thorough reply, Hynek. > > > > > > Unfortunately I have been swamped by other projects for the moment > and > > > > haven't had a spare moment to rigorously troubleshoot (fortunately > the > > > > errors are rare and as mentioned below do not seem to be triggered by > > > human > > > > visitors). > > > > > > As mentioned in my other thread [1], my issues have* mostly > *vanished. I > > > > still occasionally see an import error, although much less > frequently. > > > For > > > > instance, I had to restart Apache and memcached recently and the > first > > > > requests to my 3 Satchmo sites each generated a single error email > with > > > the > > > > import error as the cause. After that, everything was fine. I've also > > > seen > > > > more random errors where searchbots hit a completely invalid url on > my > > > sites > > > > (scratching my head where they've come up with .aspx and .htm urls on > a > > > site > > > > that has only been Django based and has only had Django-style > 'pretty' > > > > urls). Don't know that it's cause/effect...sadly the majority of > traffic > > > is > > > > probably from searchbots to begin with, but the error messages always > > > have > > > > googlebot, bingbot or Yahoo! Slurp (gross) as the user agent and the > > > > majority of the time they are hitting urls that have never been > valid. > > > > > > Again, haven't hide the time to do another deep dive, but thought I'd > > > toss > > > > these anecdotes onto the pile. > > > > > > Cheers, > > > > John-Scott > > > > > > [1] > > >https://groups.google.com/d/topic/satchmo-users/4nMkBFw7oGQ/discussion > > > > > -- > > > You received this message because you are subscribed to the Google > Groups > > > "Satchmo users" group. > > > To post to this group, send email to [email protected]. > > > To unsubscribe from this group, send email to > > > [email protected]<satchmo-users%[email protected]> > <satchmo-users%2Bunsubscribe@googÂlegroups.com> > > > . > > > For more options, visit this group at > > >http://groups.google.com/group/satchmo-users?hl=en. > > -- > You received this message because you are subscribed to the Google Groups > "Satchmo users" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<satchmo-users%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/satchmo-users?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Satchmo users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/satchmo-users?hl=en.
