PR greatly appreciated. :-) On Sat, Apr 23, 2016 at 1:53 AM, Melarish Ish <[email protected]> wrote:
> In http://mezzanine.jupo.org/docs/user-accounts.html it says "Profiles > are implemented via Django’s AUTH_PROFILE_MODULE setting." However, > that's deprecated since Django 1.7 ( > https://docs.djangoproject.com/en/dev/releases/1.5/#auth-profile-module). > Current implementation of custom profiles is: > https://docs.djangoproject.com/en/dev/topics/auth/customizing/#extending-the-existing-user-model > And where it says Django docs for profiles > <https://docs.djangoproject.com/en/1.4/topics/auth/#storing-additional-information-about-users> > ( > https://docs.djangoproject.com/en/1.4/topics/auth/#storing-additional-information-about-users) > - that link is a 404. > > It might also affect the following part "Mezzanine will expose all > relevant user and profile fields available in the signup and update profile > forms", as it doesn't seem to expose anything from the extended user model. > Not sure if that's already been noted anywhere. > > -- > You received this message because you are subscribed to the Google Groups > "Mezzanine Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- Stephen McDonald http://jupo.org -- You received this message because you are subscribed to the Google Groups "Mezzanine Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
