Re: user profile is not getting saved in admin
2008/6/23, Karen Tracey <[EMAIL PROTECTED]>: > newforms-admin WILL be merged before Django 1.0, a recent discussion on the > developer's list showed broad consensus that 1.0 without newforms-admin > doesn't make any sense. > > I encourage anyone having this problem to try the newforms-admin branch and > see if it solves the problem. The branch is quite close to being ready for > merge, and regularly updated with trunk changes. Quite possibly the problem > will just not exist over there, but if there is still an issue, you'll get > more interest in fixing it on that codebase. Testing in the new admin-newform branch is good before updating it on 1.0, but we're dealing with production applications, so a working solution is necessary. I'm happy because mine works with the modification of the core=True. -- Alessandro Ronchi Skype: aronchi http://www.alessandroronchi.net SOASI Soc.Coop. - www.soasi.com Sviluppo Software e Sistemi Open Source Sede: Via Poggiali 2/bis, 47100 Forlì (FC) Tel.: +39 0543 798985 - Fax: +39 0543 579928 Rispetta l'ambiente: se non ti è necessario, non stampare questa mail --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re: user profile is not getting saved in admin
On Mon, Jun 23, 2008 at 6:40 AM, Deniz Dogan <[EMAIL PROTECTED]> wrote: > From what I've heard it will be easier to do what we all seem to want > in the newforms-admin branch, which should be merged by the time of > the release of Django 1.0. > newforms-admin WILL be merged before Django 1.0, a recent discussion on the developer's list showed broad consensus that 1.0 without newforms-admin doesn't make any sense. I encourage anyone having this problem to try the newforms-admin branch and see if it solves the problem. The branch is quite close to being ready for merge, and regularly updated with trunk changes. Quite possibly the problem will just not exist over there, but if there is still an issue, you'll get more interest in fixing it on that codebase. Karen --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re: user profile is not getting saved in admin
>From what I've heard it will be easier to do what we all seem to want in the newforms-admin branch, which should be merged by the time of the release of Django 1.0. On Jun 21, 2:49 am, ristretto <[EMAIL PROTECTED]> wrote: > You'd think, indeed. I'm wondering if there's a work around or best > practice way to handle it. I noticed in the docs stating to wrap > access to the user.get_profile() call around a try: except: and create > it if you get an error. But, I don't see how to do that simply in the > Admin system. > > On Jun 21, 3:03 am, Deniz Dogan <[EMAIL PROTECTED]> wrote: > > > On 20 Juni, 05:26, <[EMAIL PROTECTED]> wrote: > > > > I have looked through the docs and search the group and web. Seems > > > other's > > > are asking the question, but I haven't seen an answer yet. > > > > class UserProfile(models.Model): > > > country = models.ForeignKey(Country, core=True) > > > user = models.ForeignKey(User, unique=True, > > > edit_inline=models.TABULAR, > > > core=True) > > > > When Isavea User in theAdminpage, the country (from this UserProfile) is > > > not getting saved. > > > > The list of Countries are shown in the menu, there are no errors, but the > > > DB > > > table userprofile is empty, and when I come back to the Useradminpage, no > > > country is selected. > > > > Seems that thesaveis getting dropped on the floor. > > > > I have > > > > AUTH_PROFILE_MODULE = 'app.userprofile' > > > > set. The system doesn't throw any errors. Just doesn'tsave. > > > > I saw a post suggesting subclassing User and overriding saving tosavemy > > >profile But, I can't find this recommended in the docs. The documented way > > > to do this is has nothing to do with subclassing > > > > Please clarify. > > > I have the exact same problem. You'd think Django would have a neat > > way of handling this, but it seems to me that it doesn't. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re: user profile is not getting saved in admin
2008/6/21 ristretto <[EMAIL PROTECTED]>: >> > I have looked through the docs and search the group and web. Seems other's >> > are asking the question, but I haven't seen an answer yet. I have the same problem, but with every edit_inline foreign key. -- Alessandro Ronchi Skype: aronchi http://www.alessandroronchi.net SOASI Soc.Coop. - www.soasi.com Sviluppo Software e Sistemi Open Source Sede: Via Poggiali 2/bis, 47100 Forlì (FC) Tel.: +39 0543 798985 - Fax: +39 0543 579928 Rispetta l'ambiente: se non ti è necessario, non stampare questa mail --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re: user profile is not getting saved in admin
You'd think, indeed. I'm wondering if there's a work around or best practice way to handle it. I noticed in the docs stating to wrap access to the user.get_profile() call around a try: except: and create it if you get an error. But, I don't see how to do that simply in the Admin system. On Jun 21, 3:03 am, Deniz Dogan <[EMAIL PROTECTED]> wrote: > On 20 Juni, 05:26, <[EMAIL PROTECTED]> wrote: > > > > > I have looked through the docs and search the group and web. Seems other's > > are asking the question, but I haven't seen an answer yet. > > > class UserProfile(models.Model): > > country = models.ForeignKey(Country, core=True) > > user = models.ForeignKey(User, unique=True, edit_inline=models.TABULAR, > > core=True) > > > When Isavea User in theAdminpage, the country (from this UserProfile) is > > not getting saved. > > > The list of Countries are shown in the menu, there are no errors, but the DB > > table userprofile is empty, and when I come back to the Useradminpage, no > > country is selected. > > > Seems that thesaveis getting dropped on the floor. > > > I have > > > AUTH_PROFILE_MODULE = 'app.userprofile' > > > set. The system doesn't throw any errors. Just doesn'tsave. > > > I saw a post suggesting subclassing User and overriding saving tosavemy > >profile But, I can't find this recommended in the docs. The documented way > > to do this is has nothing to do with subclassing > > > Please clarify. > > I have the exact same problem. You'd think Django would have a neat > way of handling this, but it seems to me that it doesn't. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re: user profile is not getting saved in admin
On 20 Juni, 05:26, "Gene Campbell" <[EMAIL PROTECTED]> wrote: > I have looked through the docs and search the group and web. Seems other's > are asking the question, but I haven't seen an answer yet. > > class UserProfile(models.Model): > country = models.ForeignKey(Country, core=True) > user = models.ForeignKey(User, unique=True, edit_inline=models.TABULAR, > core=True) > > When I save a User in the Admin page, the country (from this UserProfile) is > not getting saved. > > The list of Countries are shown in the menu, there are no errors, but the DB > table userprofile is empty, and when I come back to the User admin page, no > country is selected. > > Seems that the save is getting dropped on the floor. > > I have > > AUTH_PROFILE_MODULE = 'app.userprofile' > > set. The system doesn't throw any errors. Just doesn't save. > > I saw a post suggesting subclassing User and overriding saving to save my > profile But, I can't find this recommended in the docs. The documented way > to do this is has nothing to do with subclassing > > Please clarify. I have the exact same problem. You'd think Django would have a neat way of handling this, but it seems to me that it doesn't. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
user profile is not getting saved in admin
I have looked through the docs and search the group and web. Seems other's are asking the question, but I haven't seen an answer yet. class UserProfile(models.Model): country = models.ForeignKey(Country, core=True) user = models.ForeignKey(User, unique=True, edit_inline=models.TABULAR, core=True) When I save a User in the Admin page, the country (from this UserProfile) is not getting saved. The list of Countries are shown in the menu, there are no errors, but the DB table userprofile is empty, and when I come back to the User admin page, no country is selected. Seems that the save is getting dropped on the floor. I have AUTH_PROFILE_MODULE = 'app.userprofile' set. The system doesn't throw any errors. Just doesn't save. I saw a post suggesting subclassing User and overriding saving to save my profile But, I can't find this recommended in the docs. The documented way to do this is has nothing to do with subclassing Please clarify. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
