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 in my eyes this is still a bug.

Are there any known workarounds?

I think the solution should be to improve the serialiser, take the
meta-data into the process, but I haven't looked at how this can be
accomplished yet.


On 23 aug, 06:22, Andy McKay <a...@clearwind.ca> wrote:
> > However, it seems that the redirect removes the safe_marking around my
> > message! since the result I get in my browser is html-encoded!
>
> It won't work that way, safe string alters the class not the contents of the 
> string [1]. The message module turns the string into JSON and stores it. Then 
> when read it does the reverse turning it back into a string.
>
> You'll have either to alter that behaviour or find another way around.
>
> [1]https://code.djangoproject.com/browser/django/trunk/django/utils/safe...
> --
>   Andy McKay
>   a...@clearwind.ca
>   twitter: @andymckay

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Reply via email to