Maybe download attribute is much easier

to use

I dont need a download atribute

also it's for links, not for button objects

this is my code https://pastebin.com/yWsmaN8P

request is ok, pdf gets generated but download never happens, request gets a 200 response [30/Nov/2018 06:28:33] "GET /render/pdf/?inspection=1&powerplant=Rotasol HTTP/1.1" 200 6471

also, the console prints a lot of shit but no emerging download window

maybe i have to do something in the ajax call :/

MyNotes/Python.md at master · milankathiriya/MyNotes · GitHub https://github.com/milankathiriya/MyNotes/blob/master/Python.md

still not working 😢😢

hi what software/library do you recommend for automatic pdf generation (in Django obviously)?

I tried it once, it was kinda hassle

What I had to do was send mailers with dynamically generated pdfs from html

wkhtmltopdf

it uses QT webkit rendering engine

https://github.com/wkhtmltopdf/wkhtmltopdf

help please

What I had to do was send mailers with dynamically generated pdfs from html

the issue is just downloading

MyNotes/Python.md at master · milankathiriya/MyNotes · GitHub https://github.com/milankathiriya/MyNotes/blob/master/Python.md

i tried it completely

i have to add some working javascript to download

the issue is just downloading

Downloading what?

the pdf?

how can i install through .whl file in linux???

i have to add some working javascript to download

success: function(data) { // `data` is the return of the `load_cities` view function // console.log(data); var file = new Blob([data], {type: 'application/pdf'}); var fileURL = URL.createObjectURL(file); var a = document.createElement('a'); a.href = url; a.click(); window.URL.revokeObjectURL(url); }

good night

Well, id doesn't work correctly everywhere :(

Well, id doesn't work correctly everywhere :(

You can generate downloaded link with django

You can generate downloaded link with django

well, my intent was doing it in javascript

its just a temporary file

the thing is for example that i get problems in browsers and chrome makes TWO requests POST and GET

Ok, now my problem is that i havent implemented a GET because chrome likes to make two requests

Groupe Django Pour les francophones : https://t.me/joinchat/G1el41CUUBS-YcVJHzjhNA

I am building an API with drf for my mobile client. Which is the better way of authentication to use ?? Session or token ??

I am building an API with drf for my mobile client. Which is the better way of authentication to use ?? Session or token ??

I am currently using token based authentication ( as it doesn't support multiple systems ) tried django-rest-knox is it better way also read about JWT which is the better package to proceed ??

Have a look at djoser

Hello everyone

What is the best way to confirm if user is using their own email while registrarion?

What is the best way to confirm if user is using their own email while registrarion?

sending a link to the email he is using, that redirects to a verification URL in your project to verify he is using an email he has access (high probabilities he is the owner) and continue the registration process

Yeah that is how i'm doing it

But when to expire the email token

But when to expire the email token

you have to control it in your backend, you can "expire" it when the user opens the link, or if the users doesn't open it in like 24 hours, remove it from you DB

Yes, i'm expiring it after 24 hours

hi, how do you access str in a django template? {% for failure in params.failures %} <p>{{ failure.visible_failure.__str__ }} </p> <p>{{ failure.infrared_failure.__str__}} </p> {% endfor %} not working rn

Feels good that i'm doing it right

Now, if a user comes and register with another user email with wrong first name and last namw

Then after an hour, actual user comes and register what to do then?

hi, how do you access str in a django template? {% for failure in params.failures %} <p>{{ failure.visible_failure.__str__ }} </p> <p>{{ failure.infrared_failure.__str__}} </p> {% endfor %} not working rn

https://docs.djangoproject.com/en/2.1/howto/custom-template-tags/#writing-custom-template-filters

hi, how do you access str in a django template? {% for failure in params.failures %} <p>{{ failure.visible_failure.__str__ }} </p> <p>{{ failure.infrared_failure.__str__}} </p> {% endfor %} not working rn

you can use built in template tags stringformat and use s for str()

hi, how do you access str in a django template? {% for failure in params.failures %} <p>{{ failure.visible_failure.__str__ }} </p> <p>{{ failure.infrared_failure.__str__}} </p> {% endfor %} not working rn

have you thought to make them str inside get_context_data(), so the template doesn't need to format them ? ( if u r using cbvs)

have you thought to make them str inside get_context_data(), so the template doesn't need to format them ? ( if u r using cbvs)

nice

Then after an hour, actual user comes and register what to do then?

its up to you actually but usually i'll delete unverified user with email x if its exists when user register using email x

How do you know for sure, that the second user was the real one?

How do you know for sure, that the second user was the real one?

actual user should able to see confirmation email link

But he has 24 hours to confirm

It*

But he has 24 hours to confirm

doesnt mean if its already 24h his email verified tho

nice

template filters are very useful, but as a senior django dev told me some time ago, try to make all logic stuff inside models/views as templates should just display your data without need computing

doesnt mean if its already 24h his email verified tho

Yes, i'll be deleting users older than 24 hours

template filters are very useful, but as a senior django dev told me some time ago, try to make all logic stuff inside models/views as templates should just display your data without need computing

this is so true

Yes, i'll be deleting users older than 24 hours

then you dont have any problem right?

this is so true

yeah I think so!

Problem is, what should i do if another user comes and register with same email id as an other user did

Both of them has not verified yet

Should i keep these users data in DB?

Both user data*

Now, if a user comes and register with another user email with wrong first name and last namw

the second user will see the confirmation link in his email, so... he will use that token, but get registered with the wrong name, let him change names freely 🤷🏻‍♂️

Both of them has not verified yet

the first won't be verified because when he is using another people email, he couldn't access is inbox to see the confirmation message

the first won't be verified because when he is using another people email, he couldn't access is inbox to see the confirmation message

Yes, but should i keep boths user data individualy in the database?

Problem is, what should i do if another user comes and register with same email id as an other user did

actually this is not the main problem, coz if its possible then thats mean everyone can spam your registration page

better you can create a new token for the new user and expire the old token generated for the same email

And delete the fake one once actual user verified the email

And delete the fake one once actual user verified the email

yes

yes

Okay

actually this is not the main problem, coz if its possible then thats mean everyone can spam your registration page

probabilities are high

How to save nested model? How to avoid saving any one if there errors occured?

actually this is not the main problem, coz if its possible then thats mean everyone can spam your registration page

Thats why there is throttling concept

Yes, but should i keep boths user data individualy in the database?

thats why you dont need to keep both (all) user data

thats why you dont need to keep both (all) user data

But i cant show wrong data to the acrual user after login

But i cant show wrong data to the acrual user after login

you wont, since the older user data will be deleted

Let me make you understand

User1(fake) comes and signup