#2372 closed defect (fixed)
[patch] manage.py runfcgi seems to ignore LANGUAGE_CODE
| Reported by: | Owned by: | Adrian Holovaty | |
|---|---|---|---|
| Component: | Tools | Version: | |
| Severity: | normal | Keywords: | |
| Cc: | mir@… | Triage Stage: | Unreviewed |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
Running an app under apache+fcgi using manage.py FastCGI support, the LANGUAGE_CODE variable in settings is ignored and all translations are displayed using 'en-us'. The same settings file used with 'manage.py runserver' on the same system shows the correct translations.
Attachments (2)
Change History (8)
comment:1 by , 18 years ago
| Cc: | added |
|---|
by , 18 years ago
| Attachment: | management.py.diff added |
|---|
comment:2 by , 18 years ago
| Summary: | manage.py runfcgi seems to ignore LAANGUAGE_CODE → [patch] manage.py runfcgi seems to ignore LANGUAGE_CODE |
|---|
Quick fix to management.py.
comment:3 by , 18 years ago
I'm attaching a revised patch which doesn't use absolute paths to a Django install.
by , 18 years ago
| Attachment: | 3382-fcgi-translation.diff added |
|---|
Activates translation when running as FCGI.
comment:4 by , 18 years ago
Thanks for the patch, but do you have any idea why this problem is happening in the first place? I'm hesitant to commit it without knowing exactly what it's fixing.
comment:5 by , 18 years ago
Adrian, from what I could gather (I only started working with Django last week), using 'manage.py runfcgi' the language defined in settings.LANGUAGE_CODE is never activated, and as a result your app uses the default 'en-us' language. This is different from what happens in development using 'manage.py runserver'. It may be the desired effect, but it sure got me confused me when I deployed my first app.
comment:6 by , 18 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
quick fix