Hi sir. Thanks for the response but I did not get this. Can you please send
me any example resource
On Mon, Apr 19, 2021 at 11:20 AM boyuanl...@gmail.com
wrote:
> You can do that by calling an endpoint in JavaScript. So when the field's
> been changed, automatically called the endpoint in Djang
You can do that by calling an endpoint in JavaScript. So when the field's been
changed, automatically called the endpoint in Django and store it into the
database. When a user's logged back in, just render the existing data if
there's any.
On Sunday, April 18, 2021, 10:09:29 PM PDT, Salima
Hi all,
Here we are trying. While user enters a value in form input fields the
value should not clear if user logout the session and navigate from one
page to other. After filling the form in django if user fills some form
fields and suddenly user logout and if user login again then it should
sav
and is your db on the same machine as the app server? If not, did you
include the django_session table when moving the db?
--
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 a
what's your session engine?
在 2017年11月28日星期二 UTC+8上午11:43:49，dk.danny...@gmail.com写道：
>
> Hello,
>
> I used django login() in some code and it worked now in current server.
>
> Odd enough that in new server (migrated), the login session gone when i
> check with @logi
Hello,
I used django login() in some code and it worked now in current server.
Odd enough that in new server (migrated), the login session gone when i check
with @login_required. Keep asking to login.
The server have the same apache config with old server. Please help. Thank you
--
You
Hello all,
I'm not sure if you discovered the problem, but if you have different
types of authentication backends, maybe the problem is on the session
objects. Did you do a delete?.
See the NOTE in this chapter:
https://docs.djangoproject.com/en/1.6/topics/auth/customizing/#specifying-authenti
Den 10/06/2014 kl. 09.08 skrev Juergen Schackmann
:
> I do have the same issue with django admin, and definitely no custom js
> there. any other ideas???
You need to reduce the problem. Scale down to only one app server and re-run
your tests. If the problem disappears, it's a concurrency issue
I do have the same issue with django admin, and definitely no custom js
there. any other ideas???
Am Freitag, 6. Juni 2014 13:50:31 UTC+2 schrieb Juergen Schackmann:
>
> none of my js is fiddling with sessions/cookies. but there are numerous
> third party js packages included (for ads etc). so a
none of my js is fiddling with sessions/cookies. but there are numerous
third party js packages included (for ads etc). so any of those could do
strange things, this would also explain why it broke all of a sudden. could
you provide more details on the underlying issue that you had. this would
I know this may sound silly but is there some kind of JavaScript code that
may be messing things up? Had a similar issue before and it was related to
JavaScript stupidity.
On 05/06/2014 10:39 pm, "Juergen Schackmann"
wrote:
> - all app servers are running the same code with same settings.
> - DNS
- all app servers are running the same code with same settings.
- DNS load balancing was never used
- just did a htop, no unexpected or old processes
Am Donnerstag, 5. Juni 2014 11:37:30 UTC+2 schrieb Erik Cederstrand:
>
> Den 04/06/2014 kl. 13.55 skrev Juergen Schackmann >:
>
> > The production
Den 04/06/2014 kl. 13.55 skrev Juergen Schackmann
:
> The production site is served via a load balancer and 8 application servers.
> Even stranger: if I test the same code (with the same settings) on a test
> server, that is not load balanced and basically has not traffic, everything
> is work
*PLEASE HELP: I am not sure if this is a bug or caused by my code. But this
is a serious issue for my production site.*
To get some more debug information, I have created this Middleware:
from django.conf import settings
class SessionDebugMiddleware(object):
def process_response(self, req
*PLEASE HELP: I am not sure if this is a bug or caused by my code. But this
is a serious issue for my production site.*
To get some more debug information, I have created this Middleware:
from django.conf import settings
class SessionDebugMiddleware(object):
def process_response(self, req
*PLEASE HELP: I am not sure if this is a bug or caused by my code. But this
is a serious issue for my production site.*
To get some more debug information, I have created this Middleware:
from django.conf import settings
class SessionDebugMiddleware(object):
def process_response(self, req
Hi all,
this question refers to this previous
question: https://groups.google.com/forum/#!topic/django-users/8IXEvfU72S4.
However, it seems like the problem is slightly different, I decided to open
a new question:
After my site has been up and running for a while in production, I suddenly
hav
You can simple use inbuilt user authentication provided by django.
What problem are you facing with it?
Any way if you are interested in building your own authentication
engine you need to do the following:
you can do this in several way one way is
1) Store cookie in user browser (you can store
18 matches
Mail list logo
