Is it possible to ignore a system check error in Django 1.7+

I'm running into the following issue: I have an older (recently upgraded to Django 1.6) site that uses one-to-one relations for user profiles, but the FK references to certain models are pointing to auth.User. I'm building a site in 1.8 on a separate subdomain that uses the same database with the old one and uses two apps from the old one but has a custom auth model class. I know what I'm doing and want different tables for the users of both sites. But the system check for the new site fails with the fields.E301 error:I'm running into the following issue: I have an