Moving Back from Pinax-dev to Pinax-0.7.1 today, moving from Django-trunk back to 1.1.
django.contrib.messages does not exist yet in 1.1.1. So, we need to remove those settings:
# MIDDLEWARE_CLASSES
"django.contrib.messages.middleware.MessageMiddleware"
# TEMPLATE_CONTEXT_PROCESSORS
"django.contrib.messages.context_processors.messages"
# INSTALLED_APPS
"django.contrib.messages",
MESSAGE_STORAGE = "django.contrib.messages.storage.session.SessionStorage"
We have to remove the MultiDB:
DATABASES = {
"default": {
"ENGINE": "django.contrib.gis.db.backends.postgis",
"NAME": "XX",
"USER": "XX",
"PASSWORD": "XX",
"HOST": "XX",
"PORT": "XX",
}
}
Back to the old:
DATABASE_ENGINE = 'postgresql_psycopg2'
# ...
If your onboard templates make use of some of the newer templatetag libraries, you will need to remove those:
{% load account_tags %}
{% comment %} <b>{% user_display user %}</b> {% endcomment %}
You will need to remove any csrf template tags, {% csrf_token %}.
And remove the MiddleWare, "django.middleware.csrf.CsrfViewMiddleware".
Finally, if you were using the awesome django-staticfiles app, You will have to upgrade staticfiles and change your urlpattern a bit, back to:
if settings.SERVE_MEDIA:
urlpatterns += patterns('',
(r'^site_media/', include('staticfiles.urls')),
)
instead of:
if settings.SERVE_MEDIA:
urlpatterns += patterns('',
(r"", include('staticfiles.urls')),
)
Check out the docs on getting the best csrf you can out of 1.1.1: http://docs.djangoproject.com/en/dev/ref/contrib/csrf/#upgrading-notes
protection
why did you move back?