Do you have django-1.10 installed per chance? Mezzanine doesn't support 1.10 yet.
On Fri, May 27, 2016 at 9:50 PM, Xuwen Fang <[email protected]> wrote: > Hello. > I want to install a Drum instance and follow the instructions on > https://github.com/stephenmcd/drum > And after "python manage.py createdb --noinput", it shows the following: > > > > /home/xuwen/workspaces/python/bbs/lib/python3.4/site-packages/mezzanine/utils/conf.py:47: > UserWarning: You haven't defined the ALLOWED_HOSTS settings, which Django > requires. Will fall back to the domains configured as sites. > warn("You haven't defined the ALLOWED_HOSTS settings, which " > /home/xuwen/workspaces/python/bbs/lib/python3.4/site-packages/django/template/utils.py:37: > RemovedInDjango110Warning: You haven't defined a TEMPLATES setting. You > must do so before upgrading to Django 1.10. Otherwise Django will be unable > to load templates. > "unable to load templates.", RemovedInDjango110Warning) > > /home/xuwen/workspaces/python/bbs/lib/python3.4/site-packages/drum/links/urls.py:39: > RemovedInDjango110Warning: django.conf.urls.patterns() is deprecated and > will be removed in Django 1.10. Update your urlpatterns to be a list of > django.conf.urls.url() instances instead. > name="link_list_tag"), > > /home/xuwen/workspaces/python/bbs/xc_bbs/xc_bbs/urls.py:12: > RemovedInDjango110Warning: django.conf.urls.patterns() is deprecated and > will be removed in Django 1.10. Update your urlpatterns to be a list of > django.conf.urls.url() instances instead. > ("^", include("mezzanine.urls")), > > System check identified some issues: > > WARNINGS: > ?: (mezzanine.core.W01) Please update your settings to use the TEMPLATES > setting rather than the deprecated individual TEMPLATE_ settings. The > latter are unsupported and correct behaviour is not guaranteed. Here's a > suggestion based on on your existing configuration: > > TEMPLATES = [{'APP_DIRS': True, > 'BACKEND': 'django.template.backends.django.DjangoTemplates', > 'DIRS': > ('/home/xuwen/workspaces/python/bbs/xc_bbs/templates',), > 'OPTIONS': {'builtins': ['mezzanine.template.loader_tags'], > 'context_processors': > ('django.contrib.auth.context_processors.auth', > > 'django.contrib.messages.context_processors.messages', > > 'django.core.context_processors.debug', > > 'django.core.context_processors.i18n', > > 'django.core.context_processors.static', > > 'django.core.context_processors.media', > > 'django.core.context_processors.request', > ' > django.core.context_processors.tz', > > 'mezzanine.conf.context_processors.settings', > > 'mezzanine.pages.context_processors.page')}}] > > ?: (mezzanine.core.W02) TEMPLATE_DEBUG and DEBUG settings have different > values, which may not be what you want. Mezzanine used to fix this for you, > but doesn't any more. Update your settings.py to use the TEMPLATES setting > to have template debugging controlled by the DEBUG setting. > > Operations to perform: > Apply all migrations: sites, django_comments, core, redirects, admin, > generic, auth, links, contenttypes, sessions, conf > Running migrations: > Rendering model states... DONE > Applying contenttypes.0001_initial... OK > Applying auth.0001_initial... OK > Applying admin.0001_initial... OK > Applying admin.0002_logentry_remove_auto_add... OK > Applying contenttypes.0002_remove_content_type_name... OK > Applying auth.0002_alter_permission_name_max_length... OK > Applying auth.0003_alter_user_email_max_length... OK > Applying auth.0004_alter_user_username_opts... OK > Applying auth.0005_alter_user_last_login_null... OK > Applying auth.0006_require_contenttypes_0002... OK > Applying auth.0007_alter_validators_add_error_messages... OK > Applying sites.0001_initial... OK > Applying conf.0001_initial... OK > Applying core.0001_initial... OK > Applying core.0002_auto_20150414_2140... OK > Applying django_comments.0001_initial... OK > Applying django_comments.0002_update_user_email_field_length... OK > Applying django_comments.0003_add_submit_date_index... OK > Applying generic.0001_initial... OK > Applying generic.0002_auto_20141227_0224... OK > Applying links.0001_initial... OK > Applying redirects.0001_initial... OK > Applying sessions.0001_initial... OK > Applying sites.0002_alter_domain_unique... OK > > Creating default site record: 127.0.0.1:8000 ... > Creating default account (username: admin / password: default) ... > > > > Then after I "python manage.py runserver", the > http://127.0.0.1:8000/admin/ shows an error page. > Please tell me how I can solve it. > > Thanks! > > -- > You received this message because you are subscribed to the Google Groups > "Mezzanine Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Mezzanine Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
