I should elaborate even further.. The 'do something' does not show, instead
the 'do something else' shows.
--
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
Thanks, I probably should elaborate on that. I determine the user does not
get logged in through the logic of my template language. I have {% if
user.is_authenticated %} do something {% else %} do something else {% endif
%} where user is passed through the context dictionary of my
On dinsdag 15 mei 2018 00:55:38 CEST pieceofkayk2...@gmail.com wrote:
> My code
> returns the print statement 'User is active' when I sign in with a user on
> my project page; however, my user never gets logged in during the next
> step.
How did you determine the user doesn't get logged in?
--
Hey, Tonghua.
Could you elaborate more on the shared set of databases? So yes, the login
session is stored in the database. But wouldn't my two applications have
two distinct database files? My reasoning would be due to having two
distinct locations for my in-development copy and
Hello there, I think the reason is that your login session is stored in the
database. The two programs share a set of databases, so the login status is
synchronized. The corresponding solution, then copy a set of databases, and
clear the current login session. Hope you can solve your problem.
Hey All,
So I have a django project in a directory for production. I have the same
exact project in a separate repository for development. I literally have
copied and pasted my project over and the only changes I have made are
switching debug from false to true. So my project has the same
6 matches
Mail list logo