1. macstalker
  2. General
  3. Tuesday, September 15 2020, 09:19 PM
  4.  Subscribe via email

  • Add nested Field Groups to generate fieldset inside fieldset. This will allow to make complex forms.

  • Add to Conditions ability to hide/show entire nested Field Group. After adding new field we don't have to update parent condition each time to show/hide that field, as we can do it only once for entire group.

  • Ability to edit hidden fields in backend. I'm using similar scenario as in famous student-teacher example to hide/show different fields in registration form by including ?usertype=teacher. The problem is when student becomes a teacher I need to change his/her usertype in the backend without editing database directly. This will allow to reveal teacher's field to that user on the profile page.

  • It would be great to have a dedicated module where we can include just certain Field Groups to fill in and show it to specific user groups. Sometimes forcing user to fill the form inside profile page is not an option.



Thanks
admin Accepted Answer
Admin
Hi,
thanks for your suggestions.

Ability to edit hidden fields in backend. I'm using similar scenario as in famous student-teacher example to hide/show different fields in registration form by including ?usertype=teacher. The problem is when student becomes a teacher I need to change his/her usertype in the backend without editing database directly. This will allow to reveal teacher's field to that user on the profile page.
This is something of easy, and does not have a big impact to the structure of Easy Profile, so we can consider to add this also in next release. In the meantime we can suggest you another way, instead using a hidden field type you can use a select type with 2 options (student and teacher). You can set this field:
- Available in registration : Yes
- Available in edit : No
- Available in backend : Yes
With this the field will not be available in edit profile page (so the user will not be able to change it).
To hide the fields in registration page you can simply add following CSS rule to your template:
.fieldalias-group {display:none !important}
, so for example if the alias of the field is "usertype":
.usertype-group {display:none !important}
  1. more than a month ago
  2. General
  3. # 1
macstalker Accepted Answer
Basic
Thanks for your suggestion!
  1. more than a month ago
  2. General
  3. # 2
  • Page :
  • 1


There are no replies made for this post yet.
However, you are not allowed to reply to this post.