If you are still in early development and a bug here and there doesn't lead
http://github.com/digi604/django-cms-2.0/. Patrick Lauber committed Django
1.2 compatibility code a couple of days ago. I'm using it to develop a site
hit has a fairly simple workaround).
Post by Michael McCoy ÏBenjamin,
I think you are onto something.. I'm using a fairly recent (02-15-10)
root:/usr/lib/django/django-trunk# svn info
Path: .
URL: http://code.djangoproject.com/svn/django/trunk
Repository Root: http://code.djangoproject.com/svn
Repository UUID: bcc190cf-cafb-0310-a4f2-bffc1f526a37
Revision: 12438
Node Kind: directory
Schedule: normal
Last Changed Author: lukeplant
Last Changed Rev: 12438
Last Changed Date: 2010-02-15 12:54:13 -0500 (Mon, 15 Feb 2010)
As for django-cms, I'm using: django_cms-2.0.2-py2.5.egg
What is the best course of action here, is there a development trunk of
django-cms that I can checkout that will not have this issue?
Thanks very much!
-mm
PS, Yes I would never use static.serve in a production environment, I'm
still building this site out -- its in early development.
Hi,
Post by Benjamin Wohlwendare you using either Django 1.1 and Django-CMS 2.0.x or a prerelease of
Django 1.2 and a very recent checkout of Django-CMS? If the version of
Django-CMS that you are using is older than a couple of days, it will not
work together with a prerelease of Django 1.2 and lead to the problem you
are seeing.
BTW: don't use django.views.static.serve to serve media in a production
environment. See
http://docs.djangoproject.com/en/dev/howto/static-files/#the-big-fat-disclaimer
Regards,
Benjamin
Post by Michael McCoy ÏThanks for the reply..
I'm definitely doing that now.. i'm using django.views.static.serve to
serve the media.. And anyways, this problem only crops up once I POST the
form to create a new 'Page' object in the cms.. other than the, the media is
serving fine.. etc.. I can also successfully make changes to 'User' and
'Site' objects.. (ie, models outside of the cms app).
-mm
On Wed, Feb 24, 2010 at 11:11 AM, Grant Callaghan <
Post by Grant CallaghanOne thing I've found is I have to serve my media from the same domain,
ie *example.com/media* *not* *media.example.com. *This relates to
javascripts same origin policy<http://en.wikipedia.org/wiki/Same_origin_policy>
Post by mmccoyHi folks,
Love the package, it was pretty easy to setup and seems very well
designed.
I've got everything up and running, except anytime I try to create a
page I'm getting a 403 (CSRF verification failed. Request aborted.),
presumably generated by the django.middleware.csrf.CsrfViewMiddleware
package.
This is when I'm using the 'manage.py runserver' development
environment.
Can anyone help me with this? I tried simply commenting out the
package from 'MIDDLEWARE_CLASSES', but that didn't help.
Thanks!
-mm
--
You received this message because you are subscribed to the Google
Groups "django-cms" group.
To unsubscribe from this group, send email to
.
For more options, visit this group at
http://groups.google.com/group/django-cms?hl=en.
--
Regards,
Grant Callaghan
--
You received this message because you are subscribed to the Google
Groups "django-cms" group.
To unsubscribe from this group, send email to
.
For more options, visit this group at
http://groups.google.com/group/django-cms?hl=en.
--
You received this message because you are subscribed to the Google Groups
"django-cms" group.
To unsubscribe from this group, send email to
.
For more options, visit this group at
http://groups.google.com/group/django-cms?hl=en.
--
You received this message because you are subscribed to the Google Groups
"django-cms" group.
To unsubscribe from this group, send email to
.
For more options, visit this group at
http://groups.google.com/group/django-cms?hl=en.
--
You received this message because you are subscribed to the Google Groups
"django-cms" group.
To unsubscribe from this group, send email to
.
For more options, visit this group at
http://groups.google.com/group/django-cms?hl=en.