Hello Christopher,
Le 07/01/2011 18:02, Christopher Schultz a écrit :
> Johan,
>
> On 1/7/2011 5:45 AM, Johan Cwiklinski wrote:
>> Le 07/01/2011 11:24, Laurent Medioni a écrit :
>>> Strictly match, at the beginning of the pipeline, "" (or "/", I never
>>> remember...) and call the LocaleAction o
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Johan,
On 1/7/2011 5:45 AM, Johan Cwiklinski wrote:
> Le 07/01/2011 11:24, Laurent Medioni a écrit :
>> Strictly match, at the beginning of the pipeline, "" (or "/", I never
>> remember...) and call the LocaleAction only there. Then end the matcher j
Le 07/01/2011 11:24, Laurent Medioni a écrit :
> Strictly match, at the beginning of the pipeline, "" (or "/", I never
> remember...) and call the LocaleAction only there. Then end the matcher just
> after without response.
> This will work if your users always start browsing your application thr
Strictly match, at the beginning of the pipeline, "" (or "/", I never
remember...) and call the LocaleAction only there. Then end the matcher just
after without response.
This will work if your users always start browsing your application through
".../myapp/", typically just after login as a hom
Hello,
Le 07/01/2011 09:59, Laurent Medioni a écrit :
> Hi,
> You should only set the cookie when responding to "/myapp/" level and then it
> will be available to all subpathes (for the same domain of course).
Yes, but I don't know how to achieve that.
Cookie is setted when calling the locale a
Hi,
You should only set the cookie when responding to "/myapp/" level and then it
will be available to all subpathes (for the same domain of course).
Laurent
• This email and any files transmitted with it are CONFIDENTIAL and intende
Hello,
I'm currently working on i18n for our apps. I've put on the pages a
simple form with a select element for useres to change language
themselves, sending à 'locale' attribute in the URL.
Doing that, I had to enable language storage in a session
(store-in-session and create-session true) or i
