As an additional note, I started a new project with the most recent
revision (1956) this weekend. That update broke the satchmo_check
command. It took me a really long time to figure that out.
Checking your satchmo configuration.
Using Django version 1.1 pre-alpha SVN-9836
Using Satchmo version 0.9-pre-SVN-1956
The following errors were found:
Locale is not set correctly. Try
Unix: sudo locale-gen en_US
If the above does not work, try
sudo localedef -i en_US -f ISO-8859-1 en_US
Windows: set LANGUAGE_CODE in settings.py to LANGUAGE_CODE
= 'us'
On Feb 16, 10:07 am, konstantin <[email protected]>
wrote:
> Latest changes fixed my issue. Alas.
> But I think it's not crucial for me now.
>
> Thanks.
>
> On 16 фев, 19:23, Chris Moffitt <[email protected]> wrote:
>
> > Yeah. just roll back. I'll remove the changes later tonight. Ahh.
> > Frustrating.
>
> > -Chris
>
> > On Mon, Feb 16, 2009 at 10:20 AM, Bob Waycott <[email protected]> wrote:
> > > Latest change to l10n/utils.py has broken my cart, too.
> > > Previous setting, via django create project was:
>
> > > LANGUAGE_CODE = 'en-us'
>
> > > Should I just roll back and stay there for now?
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
