Make profile model configurable? about drum HOT 5 CLOSED

I think that's already the purpose of the AUTH_PROFILE_MODULE Django setting. So we could certainly remove hard-coded references to the Profile model in Drum, in fact Mezzanine already has a function mezzanine.accounts.get_profile_model.

The other aspect is the creation of the database table for Drum's profile model - which I don't believe you can avoid due to the fixed nature of DB migrations.

from drum.

Hm, AUTH_PROFILE_MODULE is deprecated since Django 1.5. It's no longer mentioned in the settings documentation for 1.7 - https://docs.djangoproject.com/en/1.7/ref/settings/. I take it that that will live on as a Mezzanine-specific setting though?

I can get a branch ready with the changes to update the references to that model.

from drum.

That's the plan for now - so go right ahead, thanks a lot.

from drum.

Hey @stephenmcd - curious what your thoughts are about the changes I proposed in the pull request.

from drum.

Merged it now, thanks again.

from drum.