AttributeError: 'module' object has no attribute 'tieredweight'

[Alessandro Ronchi]

When trying to check a new 0.9 installation I get this error:

http://dpaste.com/121919/

What's the possible cause?

--
Alessandro Ronchi

SOASI
Sviluppo Software e Sistemi Open Source
http://www.soasi.com
http://www.linkedin.com/in/ronchialessandro

[Alessandro Ronchi]

If I comment both

#'shipping.modules.tieredweight',

#'satchmo_ext.satchmo_toolbar',

I can go further but I get this error:

http://dpaste.com/121945/

[Chris Moffitt]

What version of Django are you using?

--

You received this message because you are subscribed to the Google Groups "Satchmo users" group.
To post to this group, send email to satchm...@googlegroups.com.
To unsubscribe from this group, send email to satchmo-user...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/satchmo-users?hl=.

[Alessandro Ronchi]

On Wed, Nov 18, 2009 at 4:09 PM, Chris Moffitt <ch...@moffitts.net> wrote:

What version of Django are you using?

 I solved this two problems (I think I had some import problems).

Now I'm stuck with:

http://dpaste.com/121971/

[Alessandro Ronchi]

On Wed, Nov 18, 2009 at 4:42 PM, Alessandro Ronchi <alessand...@soasi.com> wrote:

On Wed, Nov 18, 2009 at 4:09 PM, Chris Moffitt <ch...@moffitts.net> wrote:

What version of Django are you using?

 I solved this two problems (I think I had some import problems).

Now I'm stuck with:

http://dpaste.com/121971/

I'm using the latest django version: 1.1.1.

 

satchmo_check says I have no conf problem.

SettingNotSet('%s config group does not exist' % group)

the last line is, in source code:

SettingNotSet: <unprintable instance object> 

how can I know what's the setting I have to do without the name?

[Leonig Mig]

I'm having the same issue - did you find a solution?

SettingNotSet: <unprintable instance object>

On 18 Nov, 17:14, Alessandro Ronchi <alessandro.ron...@soasi.com>
wrote:
> On Wed, Nov 18, 2009 at 4:42 PM, Alessandro Ronchi <

[Leonig Mig]

Ah, in my case I was being a fool. I had not run:

python manage.py syncdb