Thanks for help.
I've found the old template.
I've asked server administrator to remove it and now it works.
Best regards
On 19 Sie, 13:06, Karen Tracey wrote:
> On Thu, Aug 19, 2010 at 5:33 AM, Aspontus wrote:
> > It seems I haven't expressed myself clearly enough.
> > The template django/contr
On Thu, Aug 19, 2010 at 5:33 AM, Aspontus wrote:
> It seems I haven't expressed myself clearly enough.
> The template django/contrib/admin/templates/admin/auth/user/
> change_password.html You point me to is rendered when I use the
> password change form from user change form.
> The one that seem
It seems I haven't expressed myself clearly enough.
The template django/contrib/admin/templates/admin/auth/user/
change_password.html You point me to is rendered when I use the
password change form from user change form.
The one that seems to be missing CSRF token is rendered when I try to
change p
On 19/08/10 09:32, PieterB wrote:
> I'm doing none of the above.
> I just deployed django 1.2 on python 2.4 on RHEL
> no changes in the admin code...
> Maybe It's due to some plugin in Firefox ? I will test again with
> another plugin showing my session/POST variables :-)
>
I've seen some strange
On Aug 19, 2:09 am, Russell Keith-Magee
wrote:
> * Your TEMPLATE_DIRS setting is pointing to a directory with pre-1.2
> templates
> * Your Django install is running pre-1.2 code, or using stale pyc
> files (which might mean you're loading templates from the wrong app
> directory)
> * You have
2010/8/18 Aspontus :
> Sorry, I haven't thought it through.
> Server is running:
> - Debian GNU/Linux 5.0 with 2.6.32.2 kernel
> - Python 2.5.2
> - Django 1.2.1
> - MySQL 5.0.51 (with MySQLdb 1.2.2) - default engine InnoDB
> - Apache2 with mod_python 3.3.1
> Browsers are in default polish confi
Sorry, I haven't thought it through.
Server is running:
- Debian GNU/Linux 5.0 with 2.6.32.2 kernel
- Python 2.5.2
- Django 1.2.1
- MySQL 5.0.51 (with MySQLdb 1.2.2) - default engine InnoDB
- Apache2 with mod_python 3.3.1
Browsers are in default polish configuration and I've tested it with
Fir
> I have run into a consistent CSRF error in admin.
> It occurs when user tries to change his/her password.
> Every single time it returns CSRF error.
> My admin templates are not modified.
Hi,
I'm not sure what your specific problem might be, but I experienced
CSRF problem in admin in 2 situ
On Wed, Aug 18, 2010 at 3:05 PM, Aspontus wrote:
> Hi.
> I have run into a consistent CSRF error in admin.
> It occurs when user tries to change his/her password.
> Every single time it returns CSRF error.
> My admin templates are not modified.
You're going to need to provide more detail than tha
On Wed, Aug 18, 2010 at 2:32 PM, James Saxon wrote:
> I've run into a similar situation where I'm getting CSRF errors
> inconsistently. I made sure I had the token and that I was using
> RequestContext. I haven't found out exactly what's wrong yet...
> I have not run into the situation in the ad
On Wed, Aug 18, 2010 at 2:20 PM, PieterB wrote:
> No I did not.
> I've only a modified (created) admin.py for each app in the project.
>
> Maybe this is also important: we use a proxy, maybe it's something
> with the cache?
> What can cause csrf verification to go crazy?
Depends on the operation
On Wed, Aug 18, 2010 at 3:22 PM, PieterB wrote:
> Can it be disabled globally?
If you have a Django 1.1 project that you have upgraded to 1.2, then
CSRF protection will *not* be enabled by default. In order to enable
it, you need to follow the migration instructions in the 1.2 release
notes.
The
Hi.
I have run into a consistent CSRF error in admin.
It occurs when user tries to change his/her password.
Every single time it returns CSRF error.
My admin templates are not modified.
Best regards
On 18 Sie, 08:32, James Saxon wrote:
> I've run into a similar situation where I'm getting CSRF e
Can it be disabled globally?
I tried some middleware code I found on the web, but I get
ImproperlyConfigured: CsrfMiddleware isn't a middleware module
(but this is probably me doing something wrong?)
http://johnmc.co/llum/disable-csrf-protection-for-django-1-2/
http://stackoverflow.com/questions/
I've run into a similar situation where I'm getting CSRF errors
inconsistently. I made sure I had the token and that I was using
RequestContext. I haven't found out exactly what's wrong yet...
I have not run into the situation in the admin but I have not tried it much
but I haven't changed any a
No I did not.
I've only a modified (created) admin.py for each app in the project.
Maybe this is also important: we use a proxy, maybe it's something
with the cache?
What can cause csrf verification to go crazy?
On 17 aug, 15:58, Alex Robbins wrote:
> Have you done any admin template customizat
Have you done any admin template customization? If you copied a
template from django before 1.2, then upgraded, your admin template
might be missing the csrf_token template tag.
Alex
On Aug 17, 7:55 am, PieterB wrote:
> For an internal application, I constantly receive CSRF verification
> failed
For an internal application, I constantly receive CSRF verification
failed" errors... most of the times when using the admin interface
It doesn't happen with the local dev version (dev http server) but
happens with the deployment version (custom port, cherokee web server)
I can only use the admin
18 matches
Mail list logo
