#14825: LocaleMiddleware should store language preferences if possible
---------------------------------------------+------------------------------
Reporter: vzima | Owner: nobody
Status: new | Milestone:
Component: Internationalization | Version: 1.2
Resolution: | Keywords:
Stage: Design decision needed | Has_patch: 1
Needs_docs: 1 | Needs_tests: 1
Needs_better_patch: 0 |
---------------------------------------------+------------------------------
Comment (by vzima):
Replying to [comment:1 rasca]:
> Marking this as Design Decision Needed, cause despite I understand your
use case when the session is flushed one might argue that the chosen
language is sensitive data that needs to be flushed.
>
> Another solution to your problem would be to render the "logged out"
template before flushing the session.
So it does not have to be the same middleware.
I do not see the point in rendering "logged out" page, because if you
refresh it (GET request) you get different result (with default language)
and any other page where you go from there will also have default
language.
Only reasonable thing, I can think of, is call set_language after logout
so it sets language to default before rendering the "logged out" page.
--
Ticket URL: <http://code.djangoproject.com/ticket/14825#comment:2>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
