That's good to know. Thanks.

On Tue, Jun 23, 2009 at 6:51 PM, Christopher Hart <[email protected]> wrote:

> Oh yeah:
>
> You also need to change any links to the homepage from "{{ shop_base }}/"
> to "{{ shop_base }}/{{ LANGUAGE_CODE }}".
>
>
>
>
>
> On Tue, Jun 23, 2009 at 5:51 PM, Christopher Hart <[email protected]>wrote:
>
>> After some fussing about we were able to get django-localeurl working
>> correctly.
>>
>> Solution took a bit of searching to find:
>> http://osdir.com/ml/DjangoUsers/2009-06/msg00668.html
>>
>> Basically, localeurl.middleware.LocaleURLMiddleware should come before
>> django.middleware.common.CommonMiddleware in MIDDLEWARE_CLASSES, but
>> after everything else. If it is placed after CommonMiddleware,
>> APPEND_SLASH is broken as explained in the django-localeurl docs.
>>
>> http://django-localeurl.googlecode.com/svn/tags/release-1.3/docs/.build/html/installation.html#id1
>>
>> Here is what we have and it seems to work correctly:
>>
>> MIDDLEWARE_CLASSES = (
>>    "django.contrib.sessions.middleware.SessionMiddleware",
>>    "django.middleware.locale.LocaleMiddleware",
>>    "django.contrib.auth.middleware.AuthenticationMiddleware",
>>    "django.middleware.doc.XViewMiddleware",
>>    #The next middleware is required if you want to use satchmo
>>    #to serve multiple simultaneous shops.
>>    "threaded_multihost.middleware.ThreadLocalMiddleware",
>>    "satchmo.shop.SSLMiddleware.SSLRedirect",
>>    "satchmo.recentlist.middleware.RecentProductMiddleware",
>>    "localeurl.middleware.LocaleURLMiddleware",
>>    "django.middleware.common.CommonMiddleware",
>> )
>>
>> Using Django 1.0.2 & Satchmo 0.8.1.
>>
>
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to