I've checked the database contents with sqliteman and the ampersands are ok, not escaped. Also i've checked the value retrieved of the database with a custom template tag and logging the value just before sending it to template, just before sending the data to the template it's correct. Finally checked again with shell and it's showing on console the expected output, all seems ok until the result is processed on the template.
On your second remark, i'm sorry but i'm quite new on django i'm not sure how to check the pipeline process, I'll put here the variables on settings I think can alter the functionality of django: MIDDLEWARE_CLASSES = ( 'django.middleware.common.CommonMiddleware', 'django.contrib.sessions.middleware.SessionMiddleware', 'django.middleware.csrf.CsrfViewMiddleware', 'django.contrib.auth.middleware.AuthenticationMiddleware', 'django.contrib.messages.middleware.MessageMiddleware', # Uncomment the next line for simple clickjacking protection: # 'django.middleware.clickjacking.XFrameOptionsMiddleware', ) TEMPLATE_CONTEXT_PROCESSORS = ( 'django.contrib.auth.context_processors.auth', 'django.core.context_processors.i18n', 'django.core.context_processors.request', 'django.core.context_processors.media', 'django.core.context_processors.static', ) I've tried disabling all TEMPLATE_CONTEXT_PROCESSORS (except auth, needed by admin interface) and MIDDLEWARE_CLASSES with no success. Can you point me something else I can or should check? Regards, Marc Serra El dijous 4 d’octubre de 2012 1:28:23 UTC+2, Russell Keith-Magee va escriure: > > On Thu, Oct 4, 2012 at 1:17 AM, Marc Serra <mad...@gmail.com <javascript:>> > wrote: > > Laxmikant I think you didn't understand my point. I don't want it > escaped, > > and escape marks it for escaping. I want to output the contents of > database > > RAW, without escaping. Safe filter does this but I found the weird > exception > > of &, what messes with urls with parameters on them. > > Are you *absolutely* certain that the database contains & and not > &? How are you verifying that this is what the database contains? > The reason I ask is that |safe is essentially a call to Django that > says "don't do anything", so I don't see how the behaviour you > describe could be caused. > > Also - are you sure that there isn't anything else in your pipeline > between the database and your display? If part of the content is being > transformed, it has all the hallmarks of something being double > handled. > > Yours, > Russ Magee %-) > -- You received this message because you are subscribed to the Google Groups "Django users" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-users/-/a4AocuofZF8J. 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.
