Profile page

Hi Tuan,

I am wondering if this is normal behavior or if this is undesired behavior.

We have Membership Pro set up so that members have to renew every year on 1/1 and we are not using simlizing renewals, so every renewal creates a new record (so that we can track historical data).

Unfortunately, when I log into my profile, it allows me to edit my profile from two records ago, not my current record. I would expect it to only allow me to make updates to my latest record.

Is this normal?

Thanks,
Elliot

Hello Elliot

Yes. That's normal. When you access to your profile, the system allows you to update your profile data, which is basically, your first subscription record

There is a config option called Syncronize Data, If you set it to Yes, the updated data will be used to update to all other subscription records in you account when you update

Regards,

Tuan

Hi Tuan,

Thanks for the response.

Any thoughts about changing the way this behaves. We would really like to keep the different records for each member separate to collect historical information.

Can it be changed so that it displays only the latest record please?

Thanks,
Elliot

Tuan

Am I correct in thinking we may be able to achieve this using PHP Script settings to change the record which has the is_profile set to 1 without needing a change to the base code?

Alan

This appears to be correct... It would sure be nice if this was built in and we didn't have to hack around though.

Thanks!
E

I agree Elliot

In fact I cant see the logic behind the current use of the first subscription being the profile record as it appears to mean that the data held on the subsequent records is redundant.

I need to keep an audit trail of one particular field which is to signify whether UK Gift Aid is claimable for that years subscription.

Tuan - are there any issues with me updating the is_profile to 1 on the latest active subscription record (and setting others to 0)?

I know that there is the minor issue of multiple active subscriptions when the member renews that would need to be catered for

Regards
Alan

Hello Alan

Please don't do that. The reason is because it affect other subscription records of same users. So until I found a solution for this requirement, please use it as how it is or you will get some unepected behavior

Tuan

Hi Tuan,

Any new news on this?

Thanks,
Elliot

Hello Elliot

I still could not figure out a solution for this requirement yet due to profile_id is used in different places in the extension. Changing the way it works would be dangerous

In the next two days, I will try to spend sometime to review the current code to see whether I can send you a safe modified code for your usage purpose at the moment.

For a change like that, honestly, I am not ready to implement in the extension

Regards,

Tuan

Thanks Tuan,

What if, instead of changing the way that the data is stored, changing how the profile page works?

I.e. I assume that currently, the profile page determines which record to display based on is_profile == 1.

What if, instead, the profile page displayed the information correlating to the user id's membership record with the latest to_date?

I realize it may not be easy to do, but that's just an idea that I had.

Thanks,
Elliot