Error migrating - db_table 'django_redirect' is used by multiple models

[carderm]

Hi - not sure if I'm missing something, but if there are already redirects in the db then this fails. Should it use a separate table?
Cheers.

ERRORS:
django_redirect: (models.E028) db_table 'django_redirect' is used by multiple models: djangocms_redirect.Redirect, redirects.Redirect.
djangocms_redirect.Redirect.site: (fields.E304) Reverse accessor for 'Redirect.site' clashes with reverse accessor for 'Redirect.site'.
	HINT: Add or change a related_name argument to the definition for 'Redirect.site' or 'Redirect.site'.
redirects.Redirect.site: (fields.E304) Reverse accessor for 'Redirect.site' clashes with reverse accessor for 'Redirect.site'.
	HINT: Add or change a related_name argument to the definition for 'Redirect.site' or 'Redirect.site'.

[yakky]

Yes currently djangocms-redirect share the same table as django redirect, for historical reason

We can lift this restriction, but I don't think we can apply if django redirect has already been added

[carderm]

Yeah - it looks like this is impossible to install except on a brand new system, or with django_redirects table completely removed.
Even doing --fake-intial migration doesn't work as you miss out on the 'response_code' field.
I would suggest blanking out the first 3 migrations and adding a new djangocms_redirects table migration > followed by another migration copying over any existing rows and matching columns... sorry I haven't got time to fix this, otherwise I'd help out. :)