I've been playing with the demo, and so far I like aMember very much. But I'm confused how the UserCP could be fully integated. In other words... If a member wants to edit his avatar or signature in vB, then he needs access to his default vB control panel. But if he needs to change his password, he needs to access the aMember control panel instead. What if he gets confused and tries to change his password in the vB CP instead of on member.php? The matter is further complicated if integrating even more plugins... for example a gallery script where he needs to access yet another control panel if he wants to upload photos. Is the only solution to this to radically customize member.php to show appropriate links to each separate CP for each separate task?
Yes, unfortunately, there is such a problem and it does not have easy solution. Any solution to this would require some customizations to vBulletin code, but it will create problems for future upgrades, and our policy is to don't do that. But in your individual case, we can show how to disable password changes from vBulletin, just contact us via helpdesk.