• Resolved trevolutionary

    (@jkdsouljah)


    Hi there,

    I’ve set up a role-specific registration form (for the sake of example let’s call that role “UserRole3”, and for all intents and purposes, it works through and through.

    What I’m struggling with however, is that when I am logged in to the backend as the administrator/webmaster, the fields I set up as part of that registration for UserRole3, are applied to all users so that if I attempt to edit a user with a different role, the fields are visible and any field that was set as compulsory is enforced, making any updates to other roles impossible if those fields are not filled in, despite being irrelevant for this other role.

    I hope that makes sense. What I would like, ideally, is that those fields for UserRole3, only show up in the admin screen for anyone with those user roles, and not others. Or at least, even if they can’t be made to only appear on the relevant roles, that I can still update other roles without needing to fill these fields in with bogus info?

    Any advice would be appreciated.

    Many thanks

    https://www.ads-software.com/plugins/profile-builder/

Viewing 5 replies - 1 through 5 (of 5 total)
  • Teodor Cosofret

    (@teodor-cosofret)

    Hi,

    In Users -> All users -> Your Profile you will see all the fields from WordPress and also from Profile Builder.

    My suggestion if you want to edit profiles, as Admin, go to the Edit Profile page created with the [wppb-edit-profile] shortcode and there you will see a Select drop down field. With this field you will be able to select your users.

    Best regards,

    Thread Starter trevolutionary

    (@jkdsouljah)

    I’ll give that a try, thank you.

    Thread Starter trevolutionary

    (@jkdsouljah)

    Okay, I tried that, but basically same story. Won’t let me update without updating those fields which were meant for the other role.

    Thread Starter trevolutionary

    (@jkdsouljah)

    I don’t know how feasible this is, but currently, fields are designated as compulsory or not under Manage Fields, and not within the registration form itself. If a field could be designated as compulsory or on the registration form, but not in the underlying Manage Fields area, then theoretically, it wouldn’t then interfere in the Edit User screen?

    Teodor Cosofret

    (@teodor-cosofret)

    Hi,

    Please submit a support ticket with this issue.

    I will wait for your ticket.

    Best regards,

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Role Specific Registration and User Fields in Admin’ is closed to new replies.