Philip, your wsgi.py is also good.
1)
Try my advice about e-mail
ADMINS = (('Your Name', '[email protected]'), )This should be sufficient for you to get a report and to continue in dialog about fixing images. 2) Unfortunately this would not be sufficient for users if other unexpected error occurs later. I had not got time for more. I am trying to give a small support only occasionally for Satchmo and for unclear cases but not if it is clear that the same problem would be for all Django applications for someone. Verify that error reporting is functional for some "Hello world" Django application with "DivisionZero", or fix it but without asking help for it on this forum. -- Hynek On 23 lis, 04:11, "Philip M. White" <[email protected]> wrote: > Hynek, > > My wsgi.py is questionable. I am not familiar with WSGI, so I did some > research online and ended up with this:http://www.qnan.org/~pmw/tmp/wsgi.py > > It's based on > <http://blog.dscpl.com.au/2010/03/improved-wsgi-script-for-use-with.html>. > > It does reference django.core.handlers.wsgi.WSGIHandler, and I do get > exceptions the usual way when Satchmo exceptions happen -- I see them in > the web browser through Django. > > If my wsgi.py is incorrect, please kindly tell me what to use -- I did > not find a ready-made WSGI file in the sample store that Satchmo > produced. Other than this one issue related to product images, Satchmo > works very well. > > So you believe that Satchmo encounters an exception that doesn't make > its way into the logs? I guess seeing my wsgi.py will tell you whether > that's a possibility or not. > > You are welcome to use my satchmo.log for any purpose you want. > > Thank you. -- 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.
