If a user has a vBulleting userid (registered via vB) and I have the aMember vB plug, does a client need to regiser under aMember as well?
How tough would it be to intergrate the two signups? I want to have one point of signup, vB's register.php, so that clients don't have to fill out two signup forms.
When aMember Pro integration works, your member need to fill-in only aMember Pro signup form. You can disable vBulletin registration form. It is impossible to do vice-versa - our policy is to NOT change third-party application code, to keep you able to make upgrades. The changes you want would require changes in vB code, and future upgrades of vB could be impossible.
Not really...I have a nother script that uses the vB register.php and vb users table as it's own source for user access...that's more in line with what I was trying to get at...modifying aMember to use vB's user database to check for appropriate access level. User registers using register.php, then aMember looks in and check to see if member exists in vB user table, etc...but maybe I can work it other way around.
If you'd do so, then there is no place for aMember in your setup. aMember (as any complex application!) cannot work in this way. 2-3 KB script can , serious standalone script cannot.