Hi, On Jan 28, 8:58 pm, boson <[email protected]> wrote: > I think the problem was that the Django "User" and ragendja "User" > were conflicting somehow and causing strange problems with the > runtime. > > For my custom backend I'm now creating my own "User" and ignoring both > of those (neither of which I could get to work properly).
What exactly was the problem? Could you please post the settings backend code here? Did you try to add a few logging.info() calls into your backend in order to verify that the code gets executed, at all, and in order to check which line fails? > My Users don't persist in the DB (auth is done remotely), and I have > been warned this may cause problems for the admin site due to > messaging issues, but we don't use the admin site anyway. I'm sure it > will cause other problems too. We shall see. It's probably better to have a proxy user in the DB or at least fake a user entry (not saved in DB) with a faked key_name, so other code can store ReferenceProperties to that fake user. Bye, Waldemar Kornewald --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
