Hello all,
I think I have found a bug, but this time I am not completely sure, so
I post it first in this group.
What I want to do is set an error message in the message-queue and
show this to the user after a redirect. Something pretty common I
guess. So I have the following code:
m
Thanks Andy
that explains why I experience this issue. However doesn't it suppose
to work like this; Why should a safe string become unsafe again after
deserialisation? I understand this is a current limitation of the
serialisation process, but this is not exactly what you would expect,
is it. So
performing the testing if it is
safe, to set the extra flag, and when presenting I have to test for
this flag again as well), but at least it is allowed when marked safe!
On 23 aug, 16:48, Andy McKay wrote:
> On 2011-08-23, at 1:08 AM, Leon van der Ree wrote:
>
> > that explains why I
Hi all,
First a short intro, since this is my first post
Last few years I have been working on and with Symfony (Php) a lot,
but since I am done with the ugly bugs within Php I decided to switch
to another development environment. I have always been interested in
other languages and frameworks an
Thanks for your response Matias,
Unfortunately some things have come in between, but I will definitely
take another look at social-auth once I've get some time and let you
know about the result!
Regards
Leon
On 20 mei, 17:52, MatÃas Aguirre wrote:
> Excerpts from Leon van der Ree's message of F
once I have some more time.
Regards
Leon
On 23 mei, 14:32, Leon van der Ree wrote:
> Thanks for your response Matias,
>
> Unfortunately some things have come in between, but I will definitely
> take another look at social-auth once I've get some time and let you
> know about the
6 matches
Mail list logo
