#django

ok, thank you

unicodedata.normalize

That sounds like it.

mattmcc: so you would say in django it's common practices/idiomatic to just go hog wild with model methods in a template?

AntelopeSalad: It depends on the data.

does that work in 2.7.6 ?

HowardwLo: Of course.

mattmc: so far i've only been accessing the absolute url method directly but even that felt dirty

HowardwLo: unicodedata.normalize('NKFD', unicode(content)).encode('ascii', 'ignore') is the code I see in https://bitbucket.org/schinckel/django-sms-gate...

AntelopeSalad: I'd suggest getting past that, this isn't MVC.

(Neither is anything else on the web)

schinckel: what is that for?

schinckel: I'm not…fluent enough :O

NFKD ;)

That's getting data ready to send via SMS, I can't remember what NFKD stands for. No F*cKing iDea, I guess. :)

Normalized form common and NF.. something

mattmcc: ok, fair enough

I'm confused now lol

hay ther

i guess the only thing that matters is being able to change the implementation of the method without it breaking the template

HowardwLo: There's more than one way to normalize unicode characters into ascii equivalents.

mattmcc: if i only want to change https://dpaste.de/pqbJ

what would you suggest?

AntelopeSalad: Right, exactly. And that's perfectly achievable with models and methods. I mean, you could swap the model out with a dictionary and the template wouldn't have to care.

its replacing a non ascii "/" to a ascii "/"

mattmcc: yeah, ok you convinced me

does it even matter which type to use?

in my case.

I'm not sure that can be normalized. http://www.scarfboy.com/coding/unicode-tool%3Fs...

I have an issue with CSRF, can anyone help?

Not without more specifics.

I have created a pastebin entry

I hope this describes my problem

I am working on a tutorial and this problem keeps coming up

did I provide enough information?

{$ crsf_token $} should be {% csrf_token %}

I wrote an auth backend that works... except both in the view that authenticates and logs in, and the redirect chain that the view triggers, the user isn't in the request. Do I need to manually put the user in the session? Shouldn't the redirect cause the middleware to put it in the session, like it does on subsequent requests?

on the template?

Yeah.

ryanhiebert: Assuming you're using the default auth middleware and login view, you should be fine.

I corrected that

but still have same error message

I'm using a particularly different authentication, so I've written my own login view. Default auth middleware

mattmcc: how would you go about removing the non ascii slash and replacing with regular slash?

or rather, I'm using a different view to do this _kind_ of login

I use the default login view elsewhere

ryanhiebert: So I'd compare your view to what the default login view does, and see what's missing.

HowardwLo: Well, since it doesn't normalize, you're probably stuck just doing a replace()

ok, that sounds like a good idea. thanks for the pointer

right, i have that now. the replace is throwing me an error. saying how no encoding is declared

mattmcc, did you see my response, I made that change but still am getting the same error message

Mattmcc, are you still here?

Can anyone help me with a CSRF problem?

Does anyone know enough about the CSRF to help me with a problem on a tutorial?

Sam99: sure

i think i detailed out everything

1 thing though the error on the html page has been corrected but still get the error message

Sam99: so in the rendered html, is the csrf hidden input being added?

im not sure what you mean, I am new at this programming

but the create_article.html is included on the pastebin

Sam99: view the source in your browser

ah, i see

You're doing {$ rather than {%

try fixing that :)

I fixed that but still get the same error message

did you go back to the rendered view, refresh that, and then submit your form again?

in any case, go back to the url for that view and refresh

s/rendered view/rendered template/

if you tried to just refresh the post request, it still wouldn't contain the csrf token in the form, hence you'd get the same errror

it removed the error message

but something is not working

thanks for your help, I am gonna go back to the tutorial and find out what is not working

np

Thank you very much Chris for helping me. I htought that PHP is hard, but Django is really hard.