Support

The new release is great - we can setup different fields for differenct membership level now. But we found out that if we set the data field as Section Divider, we can't set it to be used in selective levels. Therefore the section dividers are show in all membership levels by default, althought different membership levels need to have different section dividers. Can this be fixed?

The way it works now is section dividers are shown only if there are fields within a section. So our thinking was that if a level has a section with fields which are not applicable, it will hide automatically. If it is a common section, it will stay.

Can you provide more details of what you ideally would like to do regarding section dividers so that we can analyze this for future enhancements? 

---

Dmitry Buterin, Chief Apricot

We want to create a new membership level which requires different section dividers from other membership levels ( because we don't need to collect the same info from applicants).  Since all the exsiting section dividers will show in all membership levers, we are not able to create this new membership level.

We would like to this function --  when we create a new data field and set it as a section divider, we are able to have the same options as other data field type -- Show in 1)member application; 2)own profile 3) public profile); also -- Use in 1) all levels 2) selective levels; -- this function will result our problem.

Different membership level might collect different info from applicants (therefore can't share the same section dividers ),which is more flexible.  In our opinion, other WA users might have the same requirement. What do you think?

OK, thanks for the details, we will be analyzing this further.

What you can do already now is something like:

gold section divider

   gold field 1

   gold field 2

silver section divider

   silver field 1

   silver field 2

If gold fields are only visible to Gold level members, gold section divider will automatically hide from say Silver level members since there are no fields within the section.
 

---

Dmitry Buterin, Chief Apricot