Membership Pro version 2.17.3 released

1. Improve Custom Fields

- Added a new option called Populate Data From Previous Subscription. If you don't want data for that field is populated by data from previous subscription, set that setting to No (it's Yes by default)

This is a great feature.

Could you add another additional option called Populate Data From the field mapped profile . If you don't want data for that field is populated by data from field you have mapped (the Community Builder, Joomla, etc..) , set that setting to No (it's Yes by default)

Thanks

Lionel

Hi Lionel

Actually, that's the same setting. If you set that option to No, the field won't be auto-populated (by data from mapped extension or by data from previous subscription)

Regards,

Tuan

Hi Tuan, agreed however I would like to have the choice of the source at renewal, on a customized field basis.

For field that are allowed to be populated, I would like to have the field populated by the contents of it's mapped field in Community Builder not only at first subscription but also at renewal.
When populate the field is set to Yes, I notice that
1) At first subscription, Membership Pro populates the field from the mapped field in CB profile.
2) At renewal, Membership Pro populates the field from previous subscription and not from mapped field in Community Builder.

To do that, it needs two parameters :
1) Populate or not
2) Populate source from subscription if any ou from CB profile.

BR
Lionel

This is something I won't be able to support for field basic. If I can, I think I will only add a new setting called Always populate data from mapped extension....

If that set to Yes, the extension will ignore data from existing subscriptions while populating data (have seen some requests from customers for that option before)

Tuan
-

That would be fine of course we would have therefore 3 option :

Do not populate
Populate from previous subscription
Populate from mapped fields.

Thank's.

Adding that option is easy. I will just have to find a way to handle this change (if implemented) in backward compatible way. The reason is because right now:

- The system always get data from previous subscription if it exists
- If no previous subscriptions, then data from mapped fields will be used

I don't want to introduce something which change existing behavior, that's why I think that adding an option to always get data from mapped field (No by default) would be OK

Anyway, I will have to think more about it before coming up with final decision

Tuan