Please Log in to join the conversation.
Yes and no, at registration; yes. At subscription upgrade, no; user would need to visit their profile edit page. For registration set the field to display on registration, then set it as required. You then need to edit your plans (Plan A and Child Plan (ii)) to hide the field on registration (see workflows tab). When the user selects Child Plan (i) the field will then fade in for them to complete (and will be required for registration).Is there a way to have those fields filled out and required at the time of the registration/upgrade when a child Plan is selected.
Please Log in to join the conversation.
Please Log in to join the conversation.
Correct, Child plans assume hierarchy of the Parent plan. This means anything the Parent plan protects it will also affect the Child plan. Thus hiding the field with the parent plan will too hide it for the child plan. You should make both plans parent plans.it seems that when the parent plan A hide the field selecting the child plan (i) does not make the field fade in.
However if I have another parent Plan B (which does not hide the field) when this Plan B is selected the field fade in
Please Log in to join the conversation.