SettingNotSet

[davis]

Is there any way to figure out what setting is not set when this error
comes up?

I have a project that works fine in Windows with the development
server but then doesn't on the Apache server.

Satchmo_check shows:
Using Django version 1.0.2 final
Using Satchmo version 0.9-pre-SVN-1906
Your configuration has no errors.

The last line of the traceback is:

...satchmo-trunk/satchmo/apps/livesettings/values.py", line 287, in
_value
raise SettingNotSet("Startup error, couldn't load %s.%s" %
(self.group.key, self.key))

I saw that other people had SettingNotSet troubles but didn't see any
solution.

Thanks for any help.

[Chris Moffitt]

Can you post the full error traceback to dpaste so we can look at it?

-Chris

[davis]

Here's the dpaste link:

http://dpaste.com/111213/

Thanks for looking at it.

[Chris Moffitt]

It's having a problem import the product.urls file and is hanging up on the product Category Slug config value and I'm not sure why.

Do you get the same error when you run the local dev server instead of mod python?

-Chris

[davis]

The dev server works fine, and they're both using all the same files,
including the sqlite db.

From the satchmo.log:

2009-01-21 04:24:58,782 configuration: ERROR no such table:
livesettings_setting
2009-01-21 04:24:58,783 configuration: WARNING Problem finding
settings PRODUCT.CATEGORY_SLUG, no such table: livesettings_setting

It says there's no livesettings_setting table, but there is, but it is
empty -- is it supposed to be?

[Chris Moffitt]

If you're using sqlite that might be part of the problem. I've seen issues with threading and sqlite working ok. If you try mysql or postgresql does it work?

If the table is missing, that is a problem. Can you try running a fresh syncdb to see if it gets corrected?

-Chris

[davis]

Sorry, the problem turned out to be a configuration oversight. I had
the DATABASE_NAME set in both settings.py and local_settings.py, and
the latter was overriding the former with the wrong value. So not only
was the table missing, but the whole database was as well.

I wonder if there should be an error message indicating that the
database is inaccessible?

Thanks for helping, Chris. And, by the way, thanks to you guys for
Satchmo -- it's cool.