I have a problem. I have two different registration pages. One for a specific membership role and one for a different membership role. They are custom roles I created, but basically clones of the subscriber role with different names. I created a specific set of fields for one role’s registration page and another different set of fields for the other role’s page. Also each registration page has it’s own set of required fields.
Now here is the problem. When I (the Administrator) go into a user’s page on the WordPress Backend to edit any of the info, when I click the “Update User” button it won’t let me proceed because of all the required fields that weren’t filled out. Basically, what I did was I went into the User Meta Pro settings/Backend Profile tab and added ALL of the custom fields to the Backend Profile so that when I edit a user the appropriate fields would be there regardless of which Role the user has. So if I’m editing a user with the custom role of “A” all of the fields are also there for the other custom role “B”. But when the user signed up for role “A” non of the required fields for role “B” were present on the registration form. But they are there in the backend profile when I’m viewing or editing it. Why am I not able to proceed with those required fields blank? I thought as the administrator I could override things like required fields.
OK I just tried what you suggested but this did not work. I made the meta_key identical to the other field and made the new (duplicate) field NOT required. Does the field name also have to be identical?
I just created an admin account for you and sent the login info (via the WordPress Admin) to support@user-meta.com. My site is nextstar.net. Let me know if you need anything else.
I got your login data. As I said at post #6135, You will need to create duplicate field with same meta_key, don’t mark those fields as required and drag them to backend profile.
For example, I have created Title/Position (ID:108) as a duplicate field of ID:66 with same meta_key “title-position”. But for new field (108), I uncheck required checkbox and checked admin-only, so that, an admin can only see this field.
Now, if you go to http://example.net/wp-admin/profile.php, you can let the field empty, as it is marked as not required.
Optionally, you can change title of newly created field to distinguished between normal and admin only field.
Obviously, you will need to drag out field 66 from backend admin 🙂
Hope it works for you.
Thanks.
Author
Posts
Viewing 11 posts - 1 through 11 (of 11 total)
You must be logged in to reply to this topic.
This website uses cookies to improve your experience. We'll assume you're ok with this, but you can opt-out if you wish.AcceptRead More
Privacy & Cookies Policy
Privacy Overview
This website uses cookies to improve your experience while you navigate through the website. Out of these, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may affect your browsing experience.
Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.
Any cookies that may not be particularly necessary for the website to function and is used specifically to collect user personal data via analytics, ads, other embedded contents are termed as non-necessary cookies. It is mandatory to procure user consent prior to running these cookies on your website.