在我自己的项目中使用Django All Auth有困难-url/迁移问题

正如标题所示，在我自己的项目中使用Django AllAuth有困难。我正在使用south，但我对south很陌生，所以这可能是我问题的根源。下面我将详细介绍我采取的步骤以及我现在的位置

首先，我将allauth文件夹移动到项目的根目录下。 然后，我将示例代码的模板移动到我们的启动应用程序中——我将“plain/example/index.html”模板作为启动模板（127.0.0.1:8000）

在我们项目的URL中，我添加了：

#Allauth stuff:
url(r'^accounts/profile/$', TemplateView.as_view(template_name='plain/example/profile.html')),
url(r'^accounts/', include('allauth.urls')),

项目设置如下所示：

# Django settings for penguin project.
import os

DEBUG = True
TEMPLATE_DEBUG = DEBUG

ADMINS = (
# ('Your Name', 'your_email@example.com'),
)

MANAGERS = ADMINS

db_path = os.path.abspath(os.path.join(os.path.abspath(__file__),'..','..','..','db','peng.db'))

DATABASES = {
    'default': {
        'ENGINE': 'django.db.backends.sqlite3', # Add 'postgresql_psycopg2', 'mysql', 'sqlite3' or 'oracle'.
        'NAME': db_path,# Or path to database file if using sqlite3.
        'USER': '',                      # Not used with sqlite3.
        'PASSWORD': '',                  # Not used with sqlite3.
        'HOST': '',                      # Set to empty string for localhost. Not used with sqlite3.
        'PORT': '',                      # Set to empty string for default. Not used with sqlite3.
    }
}

# Local time zone for this installation. Choices can be found here:
# http://en.wikipedia.org/wiki/List_of_tz_zones_by_name
# although not all choices may be available on all operating systems.
# In a Windows environment this must be set to your system time zone.
TIME_ZONE = 'America/Chicago'

# Language code for this installation. All choices can be found here:
# http://www.i18nguy.com/unicode/language-identifiers.html
LANGUAGE_CODE = 'en-us'

SITE_ID = 1

# If you set this to False, Django will make some optimizations so as not
# to load the internationalization machinery.
USE_I18N = True

# If you set this to False, Django will not format dates, numbers and
# calendars according to the current locale.
USE_L10N = True

# If you set this to False, Django will not use timezone-aware datetimes.
USE_TZ = True

# Absolute filesystem path to the directory that will hold user-uploaded files.
# Example: "/home/media/media.lawrence.com/media/"
MEDIA_ROOT = ''

# URL that handles the media served from MEDIA_ROOT. Make sure to use a
# trailing slash.
# Examples: "http://media.lawrence.com/media/", "http://example.com/media/"
MEDIA_URL = ''

# Absolute path to the directory static files should be collected to.
# Don't put anything in this directory yourself; store your static files
# in apps' "static/" subdirectories and in STATICFILES_DIRS.
# Example: "/home/media/media.lawrence.com/static/"
STATIC_ROOT = ''

# URL prefix for static files.
# Example: "http://media.lawrence.com/static/"
STATIC_URL = '/static/'

# Additional locations of static files
STATICFILES_DIRS = (
    # Put strings here, like "/home/html/static" or "C:/www/django/static".
    # Always use forward slashes, even on Windows.
    # Don't forget to use absolute paths, not relative paths.
    os.path.abspath(os.path.join(os.path.dirname(__file__),'..', '..', 'static')).replace('\\','/'),
    )

# List of finder classes that know how to find static files in
# various locations.
STATICFILES_FINDERS = (
    'django.contrib.staticfiles.finders.FileSystemFinder',
    'django.contrib.staticfiles.finders.AppDirectoriesFinder',
    #    'django.contrib.staticfiles.finders.DefaultStorageFinder',
    )

# Make this unique, and don't share it with anybody.
SECRET_KEY = ''

# List of callables that know how to import templates from various sources.
TEMPLATE_LOADERS = (
    'django.template.loaders.filesystem.Loader',
    'django.template.loaders.app_directories.Loader',
    #     'django.template.loaders.eggs.Loader',
    )

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',
    # Uncomment the next line for simple clickjacking protection:
    # 'django.middleware.clickjacking.XFrameOptionsMiddleware',
    'penguin.libs.utilities.import_middle.ImportXMLMiddleware',
    )

ROOT_URLCONF = 'penguin.urls'

AUTHENTICATION_BACKENDS = (
    "allauth.account.auth_backends.AuthenticationBackend",
)

# Python dotted path to the WSGI application used by Django's runserver.
WSGI_APPLICATION = 'penguin.wsgi.application'

TEMPLATE_DIRS = (
    #absolute path, use / even on Windows
    os.path.abspath(os.path.join(os.path.dirname(__file__),'..','..')).replace('\\','/')
    )

INSTALLED_APPS = (
    'django.contrib.auth',
    'django.contrib.contenttypes',
    'django.contrib.sessions',
    'django.contrib.sites',
    'django.contrib.messages',
    'django.contrib.staticfiles',
    # Uncomment the next line to enable the admin:
    'django.contrib.admin',
    # Uncomment the next line to enable admin documentation:
    # 'django.contrib.admindocs',
    'penguin.apps.royal',
    'penguin.apps.blackboard',
    'penguin.libs.topic',
    'penguin.libs.sidebar',
    'penguin.libs.module',
    #'penguin.libs.users',
    'penguin.apps.messages',
    'penguin.apps.profiles',
    'penguin.libs.users',
    'south',

    'allauth',
    'allauth.account',
    'allauth.socialaccount',
    #'allauth.socialaccount.providers.dropbox',
    'allauth.socialaccount.providers.facebook',
    #'allauth.socialaccount.providers.google',
    #'allauth.socialaccount.providers.github',
    #'allauth.socialaccount.providers.linkedin',
    #'allauth.socialaccount.providers.openid',
    #'allauth.socialaccount.providers.persona',
    #'allauth.socialaccount.providers.soundcloud',
    #'allauth.socialaccount.providers.stackexchange',
    #'allauth.socialaccount.providers.twitch',
    #'allauth.socialaccount.providers.twitter',
    #'allauth.socialaccount.providers.vimeo',
    #'allauth.socialaccount.providers.weibo',

    )

TEMPLATE_CONTEXT_PROCESSORS = (
    "django.contrib.auth.context_processors.auth",
    "django.core.context_processors.debug",
    "django.core.context_processors.i18n",
    "django.core.context_processors.media",
    "django.core.context_processors.static",
    "django.core.context_processors.request",
    "django.contrib.messages.context_processors.messages",

    "allauth.account.context_processors.account",
    "allauth.socialaccount.context_processors.socialaccount",
)

# A sample logging configuration. The only tangible logging
# performed by this configuration is to send an email to
# the site admins on every HTTP 500 error when DEBUG=False.
# See http://docs.djangoproject.com/en/dev/topics/logging for
# more details on how to customize your logging configuration.
LOGGING = {
    'version': 1,
    'disable_existing_loggers': False,
    'filters': {
        'require_debug_false': {
            '()': 'django.utils.log.RequireDebugFalse'
        }
    },
    'handlers': {
        'mail_admins': {
            'level': 'ERROR',
            'filters': ['require_debug_false'],
            'class': 'django.utils.log.AdminEmailHandler'
        }
    },
    'loggers': {
        'django.request': {
            'handlers': ['mail_admins'],
            'level': 'ERROR',
            'propagate': True,
            },
        }
}

我是syncdb，我运行这个项目

但是，当我尝试在admin上转到社交帐户时，我遇到以下错误：

DatabaseError at /admin/socialaccount/socialaccount/

no such table: socialaccount_socialaccount

我相信这个问题是由南方的问题引起的。当我同步数据库时，我得到以下响应：

Syncing...
Creating tables ...
Installing custom SQL ...
Installing indexes ...
Installed 0 object(s) from 0 fixture(s)

Synced:
 > django.contrib.auth
 > django.contrib.contenttypes
 > django.contrib.sessions
 > django.contrib.sites
 > django.contrib.messages
 > django.contrib.staticfiles
 > django.contrib.admin
 > penguin.apps.royal
 > penguin.apps.blackboard
 > penguin.libs.topic
 > penguin.libs.sidebar
 > penguin.libs.module
 > penguin.apps.messages
 > penguin.apps.profiles
 > penguin.libs.users
 > south
 > allauth
 > allauth.account

Not synced (use migrations):
 - allauth.socialaccount
 - allauth.socialaccount.providers.facebook

由于我是南方的新手（但必须在这个项目中使用它），我不知道如何准确地解决这个问题。我在网上读到我可以做到：

migrate socialaccount 0007 --fake

但这样做之后，问题依然存在

---

有没有人知道如何解决这个问题，或者是什么原因造成的？如果有任何人还有任何问题，我可以提供所需的任何信息。

我相信它的工作方式应该是：（1）为核心应用程序/south设置执行syncdb；然后（2）执行非伪“迁移”，以（a）获取数据库中定义的应用程序模型，以及（b）更新south自己的应用程序/模型/数据库状态的数据库记录。那么，如果您尝试非伪“迁移”，会发生什么？这就是说，allauth的socialaccount应用程序和south migrations显然还有其他错误——请看，对于新的项目案例，它还有一个潜在的解决办法（强制syncdb——全部，然后迁移——伪造）。