On Oct 31, 2017 11:02 AM, "fábio andrews rocha marques" <fabioandrewsrochamarques@gmail.com> wrote:
How did you use the never_cache? Because if i just put @never_cache before the def of my view: def cadastrarprofessor(request):, it's like it doesn't do anything (i am on the login page, I go to the registration page, inform a name of a user that already exists, click "register", the system refreshes the page telling me that the user already exists and when i press the "back button" from the browser, it goes back to the registration page with empty fields, which is not what iwant. I want to go back to the login page, the page before the registration). Do I have to use @never_cache and remove all the return render from my function? What should i return instead?
I would recommend you remove any modifications related to caching. Caching is not your issue, and in most cases should only be tuned in specific circumstances, and after your intended functionality is implemented and working. Refer to my other thread for a different direction.
-James
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CA%2Be%2BciWmyNJNu7Uq%3DE0wnnwygoOJ3r5Uh8D1KTNt6MOYHMe8qg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
No comments:
Post a Comment