> One solution would be to store user_names as '[EMAIL PROTECTED]' (and making > sure that user and company don't contain @ signs). Your login template
Yes my temporary solution is compagny/user_name for user's name. And don't allow '/' sign in username/compagny_name. > could have a javascript that joins the two fields. This way you wouldn't > need to change much. Otherwise I fear you cannot evate monkey patching Yes, but the application is not usable without javascript. I'm saying that.. but my application isn't usable without JS even without you proposition... :) > turbogears.identity.visitor.IdentityVisitPlugin. I think this is one of > the weak points of Identity that should be improved. I think too.. > > -- Christoph Guillaume --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" 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/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
