I just recently upgraded amember and it has broken my custom code in the amember signup process. My site collects user information that is not in amember then brings the user to the amember signup process. This collected data was stored in a session. After the payment is processed I was inserting this data into a non-amember table with the amember_id as the key. This no longer works. When the payment is processed the $_SESSION variable has been emptied and only contains the username and password. Can you please tell me where the unset() (or whatever it is) happens on the $_SESSION variable so that I may change this? Or does this happen somewhere in the obfuscated code? I have not been able to find it myself. Thank you in advance. P.S. I put this in the forum instead of a ticket since it may be useful to others.
How about collecting this data as a custom field in aMember (using the standard means in admin) and a simple plugin that writes it to the 3rd party table after signup? This allows you the custom capabilities you want without being impacted by future upgrades.