Databases
StackOverflow2013
Postsdbo
PODjango CMS Blog error 'No module named date_based'
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PODjango CMS Blog error 'No module named date_based'
    text
    copied!<p>I'm using django CMS with the django cms blog plugin, but getting the following error:</p> <pre><code>ImportError at /en/ No module named date_based </code></pre> <p>settings.py</p> <pre><code>MIDDLEWARE_CLASSES = ( 'django.middleware.common.CommonMiddleware', 'django.contrib.sessions.middleware.SessionMiddleware', 'django.middleware.csrf.CsrfViewMiddleware', 'django.contrib.auth.middleware.AuthenticationMiddleware', 'django.contrib.messages.middleware.MessageMiddleware', 'django.middleware.doc.XViewMiddleware', 'cms.middleware.page.CurrentPageMiddleware', 'cms.middleware.user.CurrentUserMiddleware', 'cms.middleware.toolbar.ToolbarMiddleware', 'cms.middleware.language.LanguageCookieMiddleware', 'cmsplugin_blog.middleware.MultilingualBlogEntriesMiddleware', } </code></pre> <p>urls.py</p> <pre><code>from django.conf.urls import patterns, include, url from django.conf.urls.defaults import * from django.conf.urls.i18n import i18n_patterns from django.contrib import admin from django.conf import settings admin.autodiscover() urlpatterns = i18n_patterns('', url(r'^admin/', include(admin.site.urls)), url(r'^', include('cms.urls')), ) if settings.DEBUG: urlpatterns = patterns('', url(r'^media/(?P&lt;path&gt;.*)$', 'django.views.static.serve', {'document_root': settings.MEDIA_ROOT, 'show_indexes': True}), url(r'', include('django.contrib.staticfiles.urls')), ) + urlpatterns </code></pre> <p>have tried importing the views:</p> <pre><code>from django.views.generic import * </code></pre> <p>and also tried extending the patterns from the view:</p> <pre><code>urlpatterns = i18n_patterns('django.views.generic.date_based', </code></pre>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload