registration

I'm creating a web app that requires registration/authentication, and I'm considering using an email address as the sole user id. Here are what I see as the pros and cons (updated with responses): PROS One less field to fill out during registration (it would just be email address, password, and verify password). I'm a big fan of minimalistic registration. An email address is easier to remember. (thanks Mitch , Jeremy ) You don't have to worry about your favorite username being taken already - you're the only one who uses your email address. (thanks TStamper ) CONS User has more to type every

I have a stupid question, I am exploring these things so I may not be able to formulate my question using technical terms, but I want to know How can one check in which country a domain name is registered? and Does it matter? Lets say I am in Singapore but I register a domain name in Germany for my website does it matter? Thanks ALL! You can do a simple " whois " on the domain name" : whois abc.com or check this website http://www.whois.net/ , that should do the trick. It does not matter where you register the domain, as most likely you will be pointing this to your IP scheme wherever you have

i can't registration of user work, just relog the page, someone can help me form.py class RegistroUserForm(forms.Form): username = forms.CharField(min_length=5,widget=forms.TextInput(attrs={'class': 'form-control'})) email = forms.EmailField(widget=forms.EmailInput(attrs={'class': 'form-control'})) password = forms.CharField(min_length=5,widget=forms.PasswordInput(attrs={'class': 'form-control'})) password2 = forms.CharField(min_length=5,widget=forms.PasswordInput(attrs={'class': 'form-control'})) def clean_username(self): """Comprueba que no exista un username igual en la db""" username =

New .net identity system uses email and password as registration pair. I would like to change it as it was before and use username for loging users to my webapp. Also I'd like to keep somme additional information during registration as email, phone number. Can You help me and point where I should look for information for solving the problem. I cant find usefull information. Actually the old identity framework system (v 1.0) registration UI different to the new version. You can easily understand what exactly happening in the registration code. New out of the box registration code is: [HttpPost]

I wanna insert 0 to some db table's fields but can't get it work. The piece of code from my signup php script looks like that. ... if (isset($type)) { if($type==1) { $region=$data['region']; $school=$data['school']; $class=$data['class']; $group='NULL'; $subject='NULL'; $university='NULL'; $profession='NULL'; } if($type==2) { $group=$data['group']; $region=$data['region']; $school=$data['school']; $class=$data['class']; $subject='NULL'; $university='NULL'; $profession='NULL'; } if($type==3) { $group='NULL'; $region='NULL'; $school='NULL'; $class='NULL'; $subject='NULL'; $university=$data[

Using .NET 4.0, I have made a COM-enabled DLL (let's call it example.dll), and I have registered it and generated the respective type library using regasm.exe (regasm.exe /tlb /codebase example.dll); the type library is called example.tlb. The assembly is strongly named. This works so far, and I can use the DLL and the TLB from within VBA. But for certain reasons, I need to make my own utility which does the DLL registration and TLB generation. Basically, this utility will be in the same directory as the DLL and should register the DLL which it finds in that directory as well as generate the

I've come across a few SO questions on this topic, but all seem out of date or simply bad coding practice. Problem: I am signing up a user as part of a checkout flow. I want to collect the user's address when they sign up. I have a user model and an address model. I can't seem to figure out how to properly override Devise's registration's controller to allow the additional params. Here's what I've started with: class User < ActiveRecord::Base # Include default devise modules. Others available are: # :confirmable, :lockable, :timeoutable and :omniauthable devise :database_authenticatable,