Is there anything about the vBulletin/aMember integration that causes the profile fields in vBulletin to be bypassed? If so, is there a workaround? I would like my vBulletin customers to be able to fill out some customized profile information (fields) after signing up/logging in via aMember.
vBulletin profile will work still. Only "update password" will be redirected to aMember profile page. So user can change his profile in vBulletin, and if he want to change password he will be redirected to amember profile page.