On Jul 19, 8:33 am, bkline wrote:
> Thanks for the tip, Andre. I'll keep digging and see if I can
> extricate myself from this mess.
Bingo! That was the problem. After clearing out the offending copied
admin templates I was able to restore the CSRF code and I'm back o
On Jul 18, 5:25 pm, Andre Terra wrote:
> Perhaps you have a replica of the old admin templates on your
> project's folder which might be overriding the files shipped with
> core, so take a look at that first.
This looks like a very useful clue. I set this up years ago to handle
my company's fin
On Jul 19, 1:13 am, Andre Terra wrote:
> Like I said, installing python-django isn't canonical, but no body said it's
> inherently wrong.
Actually, I just paid a visit to Django's installation guide [1],
which advises installing Django using the package management system of
your OS distro, as th
On Jul 18, 5:25 pm, Andre Terra wrote:
"Installing the python-django package is not the canonical way of
using
django, let alone running production servers."
Really? It would be better if I went back to the days where we all
built everything from the source? Do all Django users running on
I just upgraded my Debian server, which brought the python-django
package up to version 1.2, and now any attempt to post to the database
tables results in a CSRF failure. I'm using the admin pages to do
just about everything, so it not clear how to apply the instructions
in the Django CSRF docs [1
5 matches
Mail list logo
