There aren't too many alternatives to either (a) you haven't defined SECRET_KEY in your settings.py or (b) django isn't loading the settings.py module you think it is.
I guess you might try throwing a debugger in django/conf/__init__.py before that error and introspecting your settings module if you can. Also, is this issue only in production? On Fri, Sep 4, 2015 at 9:03 PM, James Lewis < [email protected]> wrote: > Thankyou I have looked into that and found nothing that will help; I got > this response from webfaction: > > Hello James, > > > > Sorry I should have mentioned, my key is set in > both settings and local_settings.py? > > Normally, when Django generates a settings.py > file, it adds a comment at the top of the file that mentions the > Django version which was used to generate it. More generally, the > "manage.py startproject" command generates a project which > is compatible with the version of Django used when that command is > run. > > > Your application is now using the Django library > located at: > > > /home/jameslewis/lib/python2.7/django > > > There's nothing inherently wrong with that, but > because you erased the comments in settings.py that indicate > compatibility, I haven't been able to confirm that the django library > version you're using is actually compatible with your application. I > do see that you're using Django 1.8.4: > > > > [jameslewis@web451 myshop]$ pwd > > /home/jameslewis/webapps/myshop > > > [jameslewis@web451 myshop]$ python2.7 > > Python 2.7.9 (default, Dec 14 2014, 05:14:54) > > [GCC 4.4.7 20120313 (Red Hat 4.4.7-11)] on > linux2 > > Type "help", > "copyright", "credits" or "license" for > more information. > > import > django > > django > > <module 'django' > from '*/home/jameslewis/lib/python2.7/django/*__init__.pyc'> > > django.VERSION > > (1, 8, 4, 'final', 0) > > > > Did you actually generate your application using > Django 1.8, or are you sure that it's compatible with Django 1.8? > I've seen these types of problems arise in the past, and the solution > is as simple as installing a matching Django version for your > application. > > > Can you tell us more about your application? Is > it running successfully locally or on another host? If so, which > Django version is being used there? > > > Next, if you are sure that your application is > compatible with Django 1.8.4, then the next step is to determine why > Django doesn't see your SECRET_KEY, since you're clearly setting it > in /home/jameslewis/webapps/myshop/myapp/myapp/settings.py . To do > that, I'd just work back from the error message, logging the value of > settings.SECRET_KEY at various points until you worked back to the > point at which you set it (with a binary search). > > Regards, > > > Ryan S. > > > > I am not sure what to make of this; I am trying to work out what is wrong; > if there is anything you could recommend I would be very grateful. > > > > Regards > > > James > > On Sat, Sep 5, 2015 at 1:06 AM, Ryne Everett <[email protected]> > wrote: > >> https://docs.djangoproject.com/en/1.8/ref/settings/#std:setting-SECRET_KEY >> >> On Thu, Sep 3, 2015 at 9:45 PM, James Lewis < >> [email protected]> wrote: >> >>> Thankyou everso much, think I've had too many hours at this and my brain >>> is working at half pace :-) >>> >>> I got rid of that error and now I am getting this: >>> >>> File "/home/jameslewis/lib/python2.7/django/conf/__init__.py", line 44, >>> in _setup >>> >>> self._wrapped = Settings(settings_module) >>> >>> File "/home/jameslewis/lib/python2.7/django/conf/__init__.py", line 113, >>> in __init__ >>> >>> raise ImproperlyConfigured("The SECRET_KEY setting must not be empty.") >>> >>> django.core.exceptions.ImproperlyConfigured: The SECRET_KEY setting must >>> not be empty. >>> >>> >>> Do you know what this could be? >>> >>> >>> Thanks >>> >>> >>> James >>> >>> On Fri, Sep 4, 2015 at 2:11 AM, Danny <[email protected]> wrote: >>> >>>> On 4/09/2015 10:24 AM, James Lewis wrote: >>>> >>>> Hi Danny thanks for replying so quickly, I am not sure what the name of >>>> my form is. Would I already have an order form within cartridge or would I >>>> have to build one specifically to work with stripe? >>>> >>>> >>>> Hang on, you've (previously) updated SHOP_CHECKOUT_FORM_CLASS and yet >>>> you don't know what the name of your form class is? >>>> It's whatever you used to have under SHOP_CHECKOUT_FORM_CLASS. >>>> >>>> As for using Stripe as your payment processor, you'll either have to >>>> find any existing implementation or write one yourself. >>>> >>>> If you're using https://github.com/readevalprint/cartridge-stripe >>>> then you can see that the name of the class is >>>> "cartridge_stripe.forms.OrderForm" so that would be your reference for >>>> urls.py, >>>> >>>> e.g >>>> >>>> from cartridge_stripe.forms import OrderForm >>>> >>>> url("^shop/checkout/$", "cartridge.shop.views.checkout_steps", >>>> name="shop_checkout", kwargs=dict(form_class=OrderForm)), >>>> >>>> Your original email never mentioned what you'd set >>>> SHOP_CHECKOUT_FORM_CLASS to, so I'd assumed you'd written your own Order >>>> Form class in your own app >>>> and were doing it that way... >>>> >>>> Seeya. Danny. >>>> >>>> >>>> Many Thanks >>>> >>>> James >>>> >>>> On Fri, Sep 4, 2015 at 1:23 AM, Danny <[email protected]> wrote: >>>> >>>>> On 4/09/2015 9:51 AM, James Lewis wrote: >>>>> >>>>> Hi Danny, I have made the changes you mentioned and now I am getting >>>>> the following error: >>>>> >>>>> >>>>> File "/home/jameslewis/webapps/myshop/scooter/scooter/urls.py" in >>>>> <module> >>>>> >>>>> 33. name="shop_checkout", >>>>> kwargs=dict(form_class=MyOrderForm)), >>>>> >>>>> >>>>> Exception Type: NameError at / >>>>> >>>>> Exception Value: name 'MyOrderForm' is not defined >>>>> >>>>> >>>>> >>>>> Is that the name of your Form, though? Have you done "from ... import >>>>> MyOrderForm" in urls.py? >>>>> >>>>> I'll need some more context. >>>>> >>>>> I am sure it's something silly, but I've checked stackoverflow and >>>>> can't find anything? >>>>> >>>>> >>>>> Many Thanks >>>>> >>>>> >>>>> James :-) >>>>> >>>>> >>>>> Seeya. Danny. >>>>> -- >>>>> You received this message because you are subscribed to a topic in the >>>>> Google Groups "Mezzanine Users" group. >>>>> To unsubscribe from this topic, visit >>>>> <https://groups.google.com/d/topic/mezzanine-users/DQX3K3jdojE/unsubscribe> >>>>> https://groups.google.com/d/topic/mezzanine-users/DQX3K3jdojE/unsubscribe >>>>> . >>>>> To unsubscribe from this group and all its topics, send an email to >>>>> [email protected]. >>>>> For more options, visit https://groups.google.com/d/optout. >>>>> >>>> >>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups "Mezzanine Users" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to [email protected]. >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>>> >>>> -- >>>> You received this message because you are subscribed to a topic in the >>>> Google Groups "Mezzanine Users" group. >>>> To unsubscribe from this topic, visit >>>> https://groups.google.com/d/topic/mezzanine-users/DQX3K3jdojE/unsubscribe >>>> . >>>> To unsubscribe from this group and all its topics, send an email to >>>> [email protected]. >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Mezzanine Users" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> -- >> You received this message because you are subscribed to a topic in the >> Google Groups "Mezzanine Users" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/mezzanine-users/DQX3K3jdojE/unsubscribe >> . >> To unsubscribe from this group and all its topics, send an email to >> [email protected]. >> For more options, visit https://groups.google.com/d/optout. >> > > -- > You received this message because you are subscribed to the Google Groups > "Mezzanine Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Mezzanine Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
