Yarr's incompatibilty with Django "custom User model" about django-yarr HOT 3 CLOSED

Ok, I tested the solution and it doesn't fully work.
It allows you to actually start the migration process, but errors are raised by the migration files (they all still use references to "auth.User").

A more deep code refactoring is needed to support Django custom User model...

from django-yarr.

Thanks for letting me know about this! I've not used custom user models before, but have had a read around the subject and it looks like your solution should work nicely.

However, you're quite right about the migrations not working with a custom model; this seems to be a problem with South, but it looks like a few people have come up with solutions which I'll try out as soon as I get the chance:

• http://kevindias.com/writing/django-custom-user-models-south-and-reusable-apps/
• ixc/django-guardian@369c168

In the meantime, you could either try one of those solutions, or you could manually change yarr's migrations to use your custom user model, by changing orm['auth.User'] and the auth.User definition in the models dict (maybe copy it from a migration in another app).

from django-yarr.

I still haven't had a chance to set up a test project with a custom user model, but I have made some untested changes on an experimental branch, custom_user. This should add support to the model, migrations and import_opml management command.

I will test this when I get a chance, but I've pushed it here in case anyone is brave enough to give it a try. If anyone does, do let me know how you get on.

You can do a clean yarr install using it with:

pip install -e git+https://github.com/radiac/django-yarr.git@custom_user#egg=django-yarr

Or if you've already installed it, you could switch to your pip src dir, and pull and check out the new custom_user branch.

Once you've got this branch, make sure your settings.AUTH_USER_MODEL before you first run the migrations.

If you have already installed yarr and set up the database with auth.User, and now want to switch to a custom user model, you will probably need some custom migration voodoo to replace the fk field in Yarr's tables. Exercise left to reader.

from django-yarr.